I recently purchased a Pixhawk 1 (chinese clone 2.4.8) and fairly quickly ran in to problems with the setup…
When trying to install the firmware I often had difficulties keeping the Pixhawk connected to my PC, it would constantly disconnect and reconnect. Sometimes I would also get error messages, that my PC couldn’t recognize the USB device and it might be defect. I realized after some time, that letting the Pixhawk stand alone (I would say cool down), would fix the problem for a short time and my computer would suddenly recognize the Pixhawk as COM3 Legacy FMU.
Finally after tons of different tries, cables, and platform types, I managed to get FMV3 on it.
It also establishes a Mavlink connection. This all worked ONLY after I disconnected everything from the Pixhawk and connected it only via usb. It then was also recognized as COM4 ArduPilot
As soon as I wanted to connect the GPS, buzzer, button and receiver it would suddenly disconnect from mission planner at random or when I was trying to do a calibration. It then was also not recognizable in the device manager and the Pixhawks main LED was constant red with the buzzer staying at one tone constantly. My pixhawk would also get warm after being plugged in for just a few minutes. Thus me waiting a few minutes for it to start working properly again.
Is something fried or is something messed up software wise. I can’t imagine the setup of a Pixhawk to be this difficult normally. Could the bootloader maybe have a problem? I’m also not able to update the bootloader without it disconnecting from my PC…