It seems like the Cube might be in bootloader mode - try installing firmware without selecting a COM port in MissionPlanner.
Apart from that, the other symptoms are typical of a COM port conflict, like two devices both trying to use “COM7”
Hi Shawn,
Thanks for the guidance — much appreciated.
I tried the bootloader-mode approach you suggested.
Using the normal Load Firmware method in Mission Planner (with no COM port selected), the Cube Orange+ successfully accepted firmware and exited bootloader mode.
Windows now shows two ports:
Cube Orange+ Mavlink (COM8)
Cube Orange+ SLCAN (COM9)
At this point the Cube has no LEDs lit, which I believe is normal until it’s on a full carrier board.
Mission Planner still isn’t showing the COM ports, but the Cube itself appears to be in much better shape now.
I’ll continue testing once I have more time.
Just an update — your suggestion pointed me in the right direction. The Cube was indeed stuck in bootloader mode.
I used Mission Planner’s firmware upload (letting MP detect the board without selecting a COM port), and it successfully loaded ArduCopter onto the CubeOrange+.
Windows now shows: Cube Orange+ Mavlink (COM8) and Cube Orange+ SLCAN (COM9),
and Mission Planner connects normally, downloads parameters, and behaves as expected.
Thanks very much for your help — greatly appreciated.