Search results

  1. N

    FreqCount - Microsecond Gate Interval

    I am trying out the FreqCount function on a Teensy 4.0. I just discovered the hard way that the T4 uses microseconds not milliseconds for the gate interval. Please update the documentation on the Github README.md and on the web page to reflect this undocumented fact...
  2. N

    Teensy 4.0,4.1 web pages need a warning about INPUT_DISABLE on Analog Inputs

    The Teensy 4.0 and 4.1 analog inputs require the digital inputs to be disabled, otherwise they have a weak pullup/pulldown circuit active that causes a small glitch around the midpoint, ~1.67V. The cure is this statement in the setup() section: pinMode(<pin>, INPUT_DISABLE); The Teensy 4.0 and...
  3. N

    Teensy 3.6 USB host hangs on userial.begin() if device already plugged in

    Yes, those changes are good practice, and I have implemented them just now. However, they don't fix the userial.begin() hang problem. I suspect that the scope display drawing code is the source of the trouble, as it's a big chunk of code that is all run during one iteration of loop(). I may...
  4. N

    Teensy 3.6 USB host hangs on userial.begin() if device already plugged in

    I have done more testing and determined that the problem is a timing issue. I found that removing part of the splash screen text causes the clock to not hang in the userial.begin(baud) call. So, this leads to another question: What sort of timing issues does the Teensy USB host library have...
  5. N

    Teensy 3.6 USB host hangs on userial.begin() if device already plugged in

    Kurt, Hi. I apologize for the long response time, I've been dealing with various supply chain issues. I am glad to see that you were able to get the GPS puck and talk to it. My next question is if you have found a way to reproduce the problem that I am having, which is that userial.begin(baud)...
  6. N

    Teensy 3.6 USB host hangs on userial.begin() if device already plugged in

    Kurt, Thanks for looking into this. I have a pile of Teensys waiting for a solution. This USB chip is inside the puck. I've never seen it.
  7. N

    Teensy 3.6 USB host hangs on userial.begin() if device already plugged in

    Paul, Thanks for the quick reply. It's vid 067B pid 2303 rev 0400
  8. N

    Teensy 3.6 USB host hangs on userial.begin() if device already plugged in

    Hi, I'm using a Teensy 3.6 for my Scope Clock. I provide USB host support for a GlobalSat BU-353S4 GPS puck, using the TinyGPS and USBHost_t36 libraries. This puck uses an FTDI serial to USB chip. The source code is on my GitHub page https://github.com/nixiebunny/SCTVcode My problem is that...
  9. N

    [posted] Scope Clock displays time on 3" round CRT, plays Pong, Tetris etc.

    My latest project to use a Teensy is a reboot of my Scope Clock. This is a product hat I first made 20 years ago, to display the time on a 3" round oscilloscope CRT. It has been redesigned to use a Teensy 3.6's dual DACs instead of an analog Lissajous circle generator. There are several clock...
  10. N

    Tensy 3.6 driving GlobalSat USB GPS puck

    I am pleased to report that the USB GPS system Just Works. I received the GlobalSat BU-353S4 GPS puck and connected it to the Teensy 3.6 via a USB type A connector soldered to the board. Then I loaded the example sketch USBHost_t36 -> Serial. Then I changed the baud rate define to 4800 from...
  11. N

    Tensy 3.6 driving GlobalSat USB GPS puck

    Thanks for the suggestion. I can see that the hardware interface for either is about the same amount of work (2 pins), but the serial NMEA software interface is much easier to get working quickly than writing a USB stack for this device, especially since I don't have any experience with the...
  12. N

    Tensy 3.6 driving GlobalSat USB GPS puck

    Hi. I'm finishing up a project called the Scope Clock, which displays time on an oscilloscope CRT with a Teensy 3.6 as the controller. The last thing to add is GPS, since many customers want it. I have looked at the GPS pucks are sold these days. It seems that the GlobalSat BU-353-S4 is the one...
  13. N

    Teensy 3.6 Ethernet with other fast SPI

    Hi. I'm new here, but I know a thing or two about microcontrollers. I'm working on a new project on a Teensy 3.6 with frequent SPI accesses as well as occasional Ethernet packets using a WIZ850io (W5500 chip). Is it just fine to share the main SPI port 0 between Ethernet and another device...
Back
Top