When Cube Orange Plus with PixHawk 4 connected to the external battery or through USB it sends just one long beep and does not load.
Help how to solve it, or update the firmware
That doesn’t make much sense they are both flight controllers. Provide more detail of the hardware.
This one.
Once again when connected through the USB controller just make one long unstopped beep signal.
In the System it is recognized as COM6 and COM7 (MavLink) but it is impossible to connect to the MissionPlaner, QGC, MavProxy, STM32CubeProgrammer also can not connect.
What else is possible to do and how is it possible to Update the BootLoader?
Disconnect all those cables and try again.
ive done it - result the same - one long beep
also i have tried the next solution:
1.Open MissionPlanner
2.Do not connect through the port
3. Go to the Setup → Install firmware
4. Chose the Plane - for question want to upload - Yes
5. Check the CubeOrange from the box (There are two options for CubeOrange - i have tried both)
6. Then press Update Firmware
7. It is dowloading from Internet and reading Hex file
8. it is showing the message to unplug, then press ok and then connect board again
9. Then program make Erase then Program, then show Update Done
10. If i unplug the board and try it again the same One Long Beep and can not connect to the MissionPlaner
There is no any devices connected,
I removed the sd card and put the clean new one
Anything is helping - after all one Long Beep and mo possibility to connect to Mission Planer and Other software
That looks like a Cube Orange, not a Cube Orange Plus.
Try different USB cables. Also try to flash it from QGC.
Yes, i also tried different USB cables and even different PCs and even Different OSs like Windows and MAC, QGC writing all time message not responding
If your computers register that a USB device is recognized, try using mission planner to “force bootloader”. If this is successful, you should see some printouts in that same screen about STDEV or something. Try loading a firmware for a whole new vehicle type after that point, you might have to manually select the firmware details. I’ve done this dance to get a cube red back.
1 Like
But i have found the solution.
- Disconnect Cube from ADS-B board (Physically)
- Connect it back to the ADS-B board
- With all disconnected devices run MissionPlanner, not connect
- In Mission Planner go Setup → Install Firmware
- In the Cube was programmed the Plane, that is why in the firmware options i have choose the Copter and updated with Copter.
- Cube Resurrected ! and i could connect in mission Planner
- Disconnected from Mission Planer and disconnetc USB
- Connect with USB and Update firmware again with Plane.
- Updated but all settings missed, when i tried to load setting from file it is sends bunch errors
manual return settings back is working and Cube again alive
So this was the problem.