Floppy Gimbal after Battery pull

[Microsmith]

Hi guys. A few weeks back I had a strange issue occur. I was testing my H3, i took off and hovered about 2-3 foot from the floor for a few minutes. I was about to perform a few take offs and landings, but before i could i lost control, It didn't fly off or anything like that, the drone started to slowly ascend, i tried to bring it back down but the controller didn't have any effect. It was ascending so slowly i managed to place my hand of top of the shell and push it back down, when i got it on the ground, and with my free hand i pulled the battery out. Since then the gimbal has been non responsive.

I didn't crash or land hard, so don't suspect the ribbons, the WIFI is broadcasting, and i am seeing a picture from the camera on the controller, just no Gimbal control, to rule out the ribbons i have had it apart and checked they are ok, everything looks ok, all motors are free. After putting it back together i have the same fault. (so not made it worse thank god)

I suspected a firmware issue, and trying a few different firmware's using the SD card method, i have noted the following.

Leica L1 Gimbal Update = Failed
Error message on txt file:
file size: 135790
Error: file verification failed
update gimbal failed

Leica L1 Us-Version firmware.bin = Failed, nothing happened, no text file written.

US Firmware - H3_IONL1P_C_1.0.05_BUILD573_20190927.yuneec = Flashing red light, nothing else, no txt file output.
EU Firmware - H3_IONL1P_E_1.0.05_BUILD573_20190927.yuneec = Flashing Green light, failed
Error message on txt file:
file size: 1461235
found board ID in JSON: 96
found iv
found encrypted image
.yuneec JSON parsed
base64decode compressed image len: 1053995
base64decode iv len: 16
base64decode uncompressed len: 1053664
send reboot
send reboot
send reboot
send reboot
send reboot
send reboot
send reboot
send reboot
send reboot
send reboot
failed to get reboot acknowledged at 500000, continuing anyway
could not talk to bootloader, giving up

I've also attached a photo of my controller settings, comparing to a few posts I've read on the forum from other members, I've noticed they have data in the Autopilot and Product IDs whereas both fields on my controller say N/A. Is that normal?
So i started thinking the floppy gimbal was maybe a aircraft firmware issue instead so started the process of updating it, i got as far as doing the controller and nothing else will update, i assume im on the latest firmware for everything else.

There is a H3 Gimbal board on eBay here in the Uk for £40 so might be worth a punt buying that and seeing what happens. Other than that, does anyone have an suggestions? am i on the correct / latest firmware's?

Many Thanks!
Mike.

 

[WTFDproject]

. Other than that, does anyone have an suggestions? am i on the correct / latest firmware's?

Many Thanks!
Mike.

Those are the typical messages you get when the ribbons are damaged. You should check the contact springs on the drone side of the camera mount. But there is an incomplete circuit somewhere.
Many, many bad ribbons show no sign at all of damage.
You can't fix a hardware problem with firmware. All you will do is corrupt or erase the existing firmware and then have two problems to deal with.

 

[WTFDproject]

Also note L1 is a praticularly bad camera for firmware. Yuneec issued C23 firmware by mistake for the L1 on some websites and did not correct the mistake. You have to open the zip file, read the firmware itself to ensure it does not say "C23".