Hello everyone, I am experiencing an issue with my Pixhawk Cube Orange when connecting it to a Raspberry Pi via USB. The Pixhawk is recognized on the Raspberry Pi, as I can see it listed in lsusb and the device files /dev/ttyACM0 and /dev/ttyACM1 are created. However, I cannot establish communication with QGroundControl or MAVProxy on the Raspberry Pi. When I run cat /dev/ttyACM0, I see garbled characters, indicating that some data is being sent, but it is not readable. Additionally, the Pixhawk’s LEDs light up briefly when powered on but turn off shortly after when connected to the Raspberry Pi. In contrast, the same Pixhawk works perfectly when connected to my PC, where QGroundControl detects it without any issues. I have tried multiple solutions, including testing different baud rates (e.g., 57600, 115200, 921600), stopping the ModemManager service, checking for port conflicts using lsof, using a powered USB hub to ensure sufficient power, and even reflashing the Pixhawk’s firmware via my PC. Despite these attempts, the issue persists. I suspect this could be related to a power issue with the Raspberry Pi’s USB ports, a configuration problem, or serial port interference, but I am not certain. Has anyone experienced a similar issue with Pixhawk on a Raspberry Pi? Could this be a hardware limitation, or is there a specific configuration I’m missing? Any suggestions or advice would be greatly appreciated. Thank you!
Hi @omer_1 -
It seems the device is recognized, but maybe a power, cable or driver issue is causing a disconnection. What firmware is the Pixhawk Cube Orange running? ArduSub 4.1.2 is likely the safer option for your external device - you may need to flash this by connecting it directly to your computer and QGround Control. Then when connected to the Pi after start-up, you should see it listed correctly under the autopilot firmware menu.
If it still doesn’t work, take the red-pill at the terminal and please share the output of dmesg after plugging the device in. Downloading and sharing the BlueOS system logs (from the gear icon in the lower left of BlueOS) would also be illuminating.
From there, just make sure your computer has the correct IP for the default Mavlink Endpoint, or create one directed at the IP you’re using.
Hi, @tony-white,
I found the reason, when check the blueOs interface i saw my firmware is factory. I updated 1.3.1 after installation it worked! But now when i connect the system it go back to factory firmware as picture. Do you know why? And what should i do?
A reminder,
I am using CM4 Module when i try to upload blueOS it failed so many times and i could not. Then i tried to install oldest version 1.0.1 and it worked then i upgraded the version. Could the problem be related to this?
Hi @omer_1 -
Factory and version 1.01 have a bug where they revert on restart to an earlier version. To fix this, after updating to 1.3.1, turn on pirate mode and click the yellow “update bootstrap” button under BlueOS versions - that will fix the issue for good!