I have updated my CGO3 to gimbal version 2.08. After that I got to following output:
CGO3 V:2.08
Temperature Offset is OK!
Motor Zero Set is OK!
Front Set is OK!
Acc Offset is OK!
MPU6050 is OK!
AIRPLANEMOD
Is this "AIRPLANEMOD" normal? Do you also get this?
Or do I have a wrong FW? The file name is: CGO3_V2.08_2016_3_16.yuneec
MD5 Checksum:
| 5C3D4F5592E43BEFD2F3C63466EB676B |
Looks OK from my point of view.
Just recently I brought my CGO3 Gimbal back to live. The controller board was dead (drawing very high current, 3.3V voltage regulators and ST32 microcontroller getting extremely hot, only 1.8V instead of 3.3V, presumably the ST32 controller being dead....). I've replaced the controller board with one taken out from a new-old-stock GB203 Gimbal and swapped also all motors and magnetic position sensors from the GB203 to the CGO3, hoping that it could then work with the calibration, already stored on the GB203 controller. But as it could be expected, it didn't work with the CGO3, as mass, lever arms and - main difference - the position and orientation of the IMU sensor board are completely different between the GB203 and CGO3, even if all single components (motors, sensors) are identical on both.
I then tried to calibrate the gimbal, hoping this would fix the problem. The software tool, I had, didn't work, as apparently the board for the GB203 are configured with a completely different firmware.
Then I found your (= h-elsner, BIG THANKS TO YOU FOR PROVIDING THIS SOFTWARE!!!!) calibration tool, which could connect to the controller after selecting GB203 and 230400 bd. I could even launch all the calibration sequences, but already during the 'Phase Cali' it became obvious, that it would not end up successfully. The gimbal was moving unstable, after calib. the pitch axis worked partly in a very limited range, but there was some strange cross-coupling between yaw and roll and I had also the impression, that the internal PID parameter settings were not matching for the CGO3.
I almost gave up, but then decided as a last resort to flash the FW CGO3_V2.08_2016_3_16.yuneec, expecting that this would totally screw up everything. The firmware download initially didn't work, I was assuming that this would be due to the different baudrate of the GB203, but after playing around I was finally succesful by first launching the download and immediately afterwards powering up the gimbal controller, after two or three attempts the download was working! After reboot, the gimbal was already stable and smooth. Then I tried again to launch the calibration software for some further fine-tuning, without success, no communication.
Once more I used the h_elsner tool - and this one worked! The controller didn't any longer identify as GB203 after boot, but as CGO3 with the correct (for the GCO3) baudrate of 115200!
And: I do not get this AIRPLANEMOD message, no idea why. My CGO3 gimbal works great again and is back to live!
THANK YOU AGAIN H. Elsner!!!
I have one more CGO3 with exactly the same problem and currenty wait for the shipment of another GB203 (they're sold for 15 EUR at the moment here in GE!) and I hope to be able to repair that one as well. This time I will only replace the gimbal controller board, not all motors and sensors, as all the disassembly and re-assembly took me more than two hours. Hopefully the calibration fixes then the magnet sensor offsets etc. of the old CGO3 motors.
. Considering another h520e now myself with 8 batteries for 550gbp or just over 600 euros
