Search results

  1. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    Yeah, I'm aware that tripping is heat. That's why I wrote "not just heat". The other part I was looking at on Digikey specified its trip temperature as over 200C. So not just hot, but very hot! But my thought is that the trip point will degrade faster, not if you just hold it at a high temp...
  2. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    Thanks for that reference to the actual PTC Ken. I had found something on the internet that pointed to a different brand but otherwise same basic specs. 500 mA hold, and 1A trip point. That sounded like a good rational choice since the regulator can handle 1A, and the normal loads are all...
  3. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    Sure. First, no, we are not using the SD at all. No card in the slot. The robot where we run the teensy is FULL of heat-producing electronics and motors. The teensy itself is mounted on a PC board that is stuffed with other electronics and has an Ethernet switch board right next to the...
  4. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    With the new board, I've now added 320 mA of external load on the 3.3, with the board drawing 162 ma with no external load, overclocked at 804 Mhz, and no problems wth the PTC. Total USB load is 487 mA. PTC output is 4.6V so it's dropped some but nowhere near what it takes to crash the...
  5. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    This morning, I pulled a brand-new Teensy 4.1 out of the box and have been testing it. So far, I've seen no PTC fuse issues on the new board. I've only run at 200 mA loads so far but was getting ready to add some external load to the 5V circuit to find where a new PTC fuse will trip. I didn't...
  6. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    I did a bit more testing yesterday on a Teensy 4.1 board with the PTC fuse removed. By overclocking the CPU I could force it to draw more current and produce more heat. On a board with the fuse removed, I could overclock all the way to the max of 996 MHz without crashing. And with no heat...
  7. Curt Welch

    F1 PTC Fuse can cause heat-related reboot loops on heavily loaded Teensy 4.1 projects.

    We just had to hunt this bug down for work, and I thought I would share what I found. We have a Teensy 4.1 as a controller in our robot that recently started rebooting for no known reason. It would not just reboot once, but keep repeating every 10 seconds or so but when we shut it down and...
  8. Curt Welch

    Teensy 4.1 500 ma Fuse

    The F1 PTC fuse I suspect, is this part: https://www.digikey.com/short/5t5fjzj3 Bel Fuse Inc. 0ZCK0050FF2E PTC RESET FUSE 6V 500MA 0805 But as Paul already said two years ago, you have Q1 circled in your picture. I had to hunt this down for myself, and thought it would be helpful to have in...
  9. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    Thanks for all that Shawn! I've been a C programmer for decades but have not used C++ much so the difference between the static cast and the implicit cast was lost on me. Thanks for explaining why one worked and the other didn't! Looking into why they heck they have a poll() function and I...
  10. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    @shawn Yeah, I found some time yesterday to have a quick look at switching ArduinoWebsockets to use QNEthernet, and it wasn't hard at all. I know more now than I did when I tried it last time. First, there are two files that include NativeEthernet.h that need to be changed, I was only changing...
  11. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    Actually, now that I've dug deeper into the code and understand more, I don't know why it was having such problems compiling. I don't remember the actual errors. Because ArduinoWebSockets is set up to support a wide range of hardware, it's got a handful of different network socket abstraction...
  12. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    Thanks, yeah, I noticed. At work, I have been testing QNEthernet, and we are planning on dumping WebSockets (sort of the wrong option to begin with) for our robot, and switching to a UDP protocol. But when I see bugs, it's hard for me not to trace them down and try to fix them. At least...
  13. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    I traced this bug down to the NativeEthernet library this weekend. See my write-up and some code that seems to fix it in this issue: https://github.com/vjmuzik/NativeEthernet/issues/36 And in this issue for ArduinoWebSockets: https://github.com/gilmaimon/ArduinoWebsockets/issues/166 I think...
  14. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    I spent Sunday chasing deeper into this and learned more. The bug is (as I suspected) triggered when the WebSocket message is too large to fit in a single 1500-byte Ethernet packet and is split across two (or more) packets. The WebSocket code receives valid data from the TCP layer for all the...
  15. Curt Welch

    Teensy4.1 AuduinoWebsockets NativeEthernet or QNEthernet - WebSocket messages being received over around 1440 bytes are corrupted and crash the Teensy

    I'm running into a bug on a Teensy4.1 used in a robotics application using WebSockets to receive information from a web server. If the packets sent are over about the size of a single ethernet packet, they are corrupted. This appears to be a memory overflow bug somewhere. I've removed all our...
Back
Top