MOCmaniac
Member
Hello everyone,
As part of my master thesis project, I'm using a Teensy 4.1 to communicate with devices over CAN. My first setup was on a breadboard and worked flawlessly for several months. Now that everything is validated, I've soldered the final circuit onto a protoboard, including the two CAN transceivers, a USB cable for power, decoupling capacitors to be on the safe side and other components. The Teensy is powered through a diode as recommended here because when it was still on the breadboard, it was powered with 5V from a battery while also connected to USB. When the Teensy is running and connected to a PC, it outputs quite a lot of debug on the serial monitor in the arduino IDE (115200baudrate). Lines of around 300 chars every 50ms (also logged on the SD card). It is perhaps not a lot compared to the usb port capabilities but I prefer to mention it.
After a few hours of operation in this new setup (closed enclosure), the Teensy stopped responding. Here's what I've observed so far:
For now, I can easily replace the Teensy, but I’d really like to understand why it stopped working, and more importantly, how to avoid this issue in the future. This is a critical project for me, and if the Teensy fails during the final presentation, it would be a major problem.
Since the Teensy is inside this almost closed enclosure, could a component have overheated? What could I test after this to determine the cause of the problem?
Thanks in advance for your help!
Arnaud
As part of my master thesis project, I'm using a Teensy 4.1 to communicate with devices over CAN. My first setup was on a breadboard and worked flawlessly for several months. Now that everything is validated, I've soldered the final circuit onto a protoboard, including the two CAN transceivers, a USB cable for power, decoupling capacitors to be on the safe side and other components. The Teensy is powered through a diode as recommended here because when it was still on the breadboard, it was powered with 5V from a battery while also connected to USB. When the Teensy is running and connected to a PC, it outputs quite a lot of debug on the serial monitor in the arduino IDE (115200baudrate). Lines of around 300 chars every 50ms (also logged on the SD card). It is perhaps not a lot compared to the usb port capabilities but I prefer to mention it.
After a few hours of operation in this new setup (closed enclosure), the Teensy stopped responding. Here's what I've observed so far:
- The Teensy no longer shows up in the Arduino IDE (nor in the Device Manager).
- I held the button down for about 10 seconds - the LED next to the USB port turned on, and then the Blink sketch started running.
- I tried plugging it in using a different micro USB cable, but it didn’t help. Another Teensy 4.1 works fine with the same cable and is correctly detected by my computer, and I can upload code to it without any issues.
- The board still receives 5V, and I also measure 3.3V output from the regulator.
- The same code (quite confidential - I can't post it directly here) is running without any noticeable issue on the other Teensy and was running on it before.
For now, I can easily replace the Teensy, but I’d really like to understand why it stopped working, and more importantly, how to avoid this issue in the future. This is a critical project for me, and if the Teensy fails during the final presentation, it would be a major problem.
Since the Teensy is inside this almost closed enclosure, could a component have overheated? What could I test after this to determine the cause of the problem?
Thanks in advance for your help!
Arnaud