I’ve been around development as a mechanical designer for a long time but first time getting the courage to build something myself. I connected everything to power and made a crucial mistake of turning the wrong dial on my Power Supply and sent 50V 1A through my system.
I am on an X650 airframe, 6S system, power in through a holybro PDB, to a PM06D and into an ADSB Cube Orange+ FC
Everything was working great on first power up until my mistake. Now I have the following and I don’t know what to do…nothing seemed to catastrophically fail but…
IOMCU reset error 0x1000
Board connects via MAVLink but won’t accept firmware flash
Force Bootloader and CLI both failing
Any thoughts/help greatly appreciate
Edit:The attached image is coming from mission planner
I’m starting to think I fried my BEC going into the ADSB carrier servo rail which, if I am correct, powers the IOMCU.
I am reading proper voltage going into the POWER1 (which is why MavLink connects) but nothing coming out of the BEC into the servo rail.
I’ve ordered a new BEC, but that’s a couple of days away. I’d still appreciate any further thoughts on this as it is unclear to me whether the IOMCU fw can be updated without power to the servo rail.
Sorry to hear that happened. Since 50V was accidentally applied, I would be very careful before continuing to power the system or repeatedly attempting firmware flashes.
From the Mission Planner message, the FMU side still appears to communicate over MAVLink, but the error is specifically related to the IO/IOMCU firmware update. ArduPilot has a documented recovery method where holding the safety switch during boot can force the IO firmware update, but I would only try this after confirming the carrier board power rails are correct and stable.
A few practical checks I would suggest:
1. Disconnect everything non-essential first:
ESCs
servos
receiver
GPS/peripherals
telemetry
any external BEC outputs
2. Check the power rails with a multimeter:
POWER1 / POWER2 voltage
servo rail voltage
any BEC output voltage
confirm no short between 5V and GND
3. If the BEC feeding the servo rail is damaged or outputting nothing, replace/test that first before assuming the Cube itself is dead.
4. After stable power is confirmed, try the documented IOMCU force update method by holding the safety switch while powering the autopilot.
5. If the IOMCU still cannot update, then the overvoltage may have damaged the carrier board, IOMCU side, or related power/protection circuitry. At that stage I would recommend contacting CubePilot or the reseller before further flashing attempts.
Also, I would avoid connecting the full 6S system again until each rail has been checked independently with a current-limited bench supply.
