Did I fry my pixhawk?

Hi folks,

Pixhawk 2.4.8.

It was working fine, but yesterday I was experimenting at the desk. I connected it via USB first to mission planner, then I plugged in my LiPo to the servo rail (Didn’t have a switch on the LiPo yet - I do now…maybe too late). When I plugged in the LiPo the Pixhawk made a crazy screeching noise and everything has been screwey ever since. I have an InternalError 0x1000000 when I initially connect. This is then replaced by different warnings, currently “PreArm: Waiting for RC” but this can vary (INS Unable to initialise driver, Bad Gyro Health etc.). Also, weirdly the DISARMED, SAFE and FAILSAFE warnings are all displayed overlapping each other, not sure if thats related, could be a software bug in mission planner.

When I try the Accel Calibration > Calibrate Accel now I get nothing, it just times out before asking me to do the first step.

I have reinstalled my ArduPlane firmware by installing ArduCopter then switching back to Plane fmuV3.

I also updated my bootloader.

I checked the servo rail with a multimeter and am getting 2.5V from MAIN OUT and AUX OUT when connected to my laptop via USB and 5.1V from MAIN OUT and AUX OUT when my lipo is also connected to AUX OUT 1 or any MAIN OUT.

Also when I try to arm I get a list of errors. Should the “Board (3.3v) out of range 4.3-5.8v” concern me?

I’m worried I fried my pixhawk. Is there a way I can check before having to splash out for another. :frowning: Any ideas?

I think you can get help on Ardupilot discourse better.