Situation:
We have integrated bidirectional communication with an arduino micro into software we've created, this software also communicates with multiple other hardware components at the same time.
The arduino micro runs hardware (digital displays, heating components and temperature sensors), when using a USB connection to the computer we don't run into any issues with hardware or firmware functionality while the software is running.
When using a USB-C connection to the computer, we have run into issues with the hardware freezing (display will blank out or freeze/become non-responsive), temperatures running away and getting too hot. These failures are not immediate but there is not a specific set of conditions I can identify that cause the problems which makes it challenging to nail down what is happening.
When observing the serial monitor, the arduino still sends responses to commands but the information has no effect on the hardware/responses are not accurate indicators of what is actually happening with the hardware. It requires a re-flashing of the firmware or a hard restart of the arduino micro to fix the issue (until it happens again).
What would be the cause of such massive failure when using a USB-C cable vs a USB cable to connect to the computer? Thanks in advance for any insight you all have ![]()
Update to original post:
Complete connection path:
- Arduino Micro-USB --> Micro-B Male to USB-B Female cable
- USB-B Female port --> USB-B Male to USB-C cable
- USB-C plugs into the computer
*Note, if a USB-B male to USB-A cable is used in connection 2, and the USB-A is plugged into the computer, we do not run into any of the found issues.
I am unfortunately unable to share my sketch at this time, but will look at what failsafes I have in place and note those shortly.