Yuneec's software for gimbal calibrations

[cabinfourus]

I have not tested yet but some of the functionality is already there. So it could look like when we want to calibrate the AS5600 sensors at the gimbal using I²C interface.
View attachment 29974
I will proceed develop if such a tool is needed by someone.

br HE

Yes. This is exactly what I am thinking. The encoders hold position settings. Can you put together something to read/change these values? I am very busy the next couple of days but plan on tackling some of this over the coming weekend.
Absolute encoders
Store unique position information for each point along the magnetic scale. They generate a unique digital code corresponding to each position and send this to the STM32 on the mainboard. The mainboard compares the readings to its stored settings. If I am able to get into the STM32 and read the memory, we can use this to set encoders correctly. I'd like to have a tool to read the encoder's live movements.

I am also trying to translate the firmware.

 

[h-elsner]

Here is the tool. Not fully tested but I think it works. Do not change configuration settings although it is possible.
Yuneec is not using the ZPOS and MPOS register. I think they do it through the OUT Pin. However ZPOS and MPOS register may work if magnet is totally out of calibration range. It is something just to test by try and error.

br HE

 

[cabinfourus]

Here is the tool. Not fully tested but I think it works. Do not change configuration settings although it is possible.
Yuneec is not using the ZPOS and MPOS register. I think they do it through the OUT Pin. However ZPOS and MPOS register may work if magnet is totally out of calibration range. It is something just to test by try and error.

br HE

I will give this a try over the weekend and let you know. Thank you so much.
I am still working on the stm32 readout problem also.

 

[h-elsner]

Updated the zip file in #22. There is now a possibility to read data cyclic. Means you have life data for Raw Angle and Angle values.
The latest files are now available at GitHub: GitHub - h-elsner/MPU6050-test-tool: MPU6050 test GUI for raspberry Pi

regards HE

 

[cabinfourus]

Here is the tool. Not fully tested but I think it works. Do not change configuration settings although it is possible.
Yuneec is not using the ZPOS and MPOS register. I think they do it through the OUT Pin. However ZPOS and MPOS register may work if magnet is totally out of calibration range. It is something just to test by try and error.

br HE

Does this work with linux or just raspberry pi? Rasbian?

 

[cabinfourus]

Updated the zip file in #22. There is now a possibility to read data cyclic. Means you have life data for Raw Angle and Angle values.
The latest files are now available at GitHub: GitHub - h-elsner/MPU6050-test-tool: MPU6050 test GUI for raspberry Pi

regards HE

Awesome. Will this work with linux? Nevermind, dumb question. I will need to use the Pi pins. I got it.

 

[cabinfourus]

Here is the tool. Not fully tested but I think it works. Do not change configuration settings although it is possible.
Yuneec is not using the ZPOS and MPOS register. I think they do it through the OUT Pin. However ZPOS and MPOS register may work if magnet is totally out of calibration range. It is something just to test by try and error.

br HE

I have been working on the readout protection all weekend. My st-link is a cheap knock off but I do have the Jeff Probe black magic board I am trying.
I also ordered a newer tool. The ST-Link V3Minie is priced low enough to give it a try. I was looking at the cold boot start-up and wondering if a 'snapshot' could be taken while the memory is going through its boot process. Have you tried this?
Also, I want to try sending 0x7F with even parity and a single stop bit to UART. I can't do this until I get the new board. It should open up and spill its secrets.
This is a HUGE learning curve for me as I am not great at extracting firmware but I have read in other forums that the STM32 chip has been cracked to allow the level of readout protection to be changed. I am not sure how true this is but maybe a few weeks of research will help.

 

[MobileTechSpecialists]

What chip are you talking about? The AS5600 angle sensor? It has no USB but I²C. There is a good description in the datasheet how to set bounds/angle programming. I can read raw data from it using an Raspberry Pi.
Here are the pins to access:
View attachment 29959View attachment 29958

Here are the debug ports from the gimbal main board:
View attachment 29960

The USB port on the camera is out of service. There are pads for it on the PCB but empty on nearly all boards I have seen. CGO3P only supports the UART.

br HE

I saw you mention

I have not tested yet but some of the functionality is already there. So it could look like when we want to calibrate the AS5600 sensors at the gimbal using I²C interface.
View attachment 29974
I will proceed develop if such a tool is needed by someone.

br HE

is this required? What errors would the camera throw if calibration was needed for these little encoders?

 

[h-elsner]

This is all stuff from the past as I tried to figure out what calibration means and if it stored in the sensor chip (it does not).
All you need for the calibration is in the gimbal firmware and will be activated and controlled by the calibration software tool.
No need to think about angle sensors anymore except you want to use the sensor chips for other purposes.

 

[Vaklin]

The sensor is connected via PWM lines. Not every magnet position is allowed.
@WTFDproject can explain this in deep.
I'm agreed.

 

[MobileTechSpecialists]

Say I replace an encoder, do I need to wipe the values or can I use the CGO3P calibration tool as stated above? I have about 6 cameras I’m in the process of restoring it’s slowing things down big time

The sensor is connected via PWM lines. Not every magnet position is allowed.
@WTFDproject can explain this in deep.
I'm agreed.

 

[DoomMeister]

I believe encoders can be changed without needing to recalibrate. The gimbal board, motor, or magnet will likely require a calibration.

 

[WTFDproject]

Say I replace an encoder, do I need to wipe the values or can I use the CGO3P calibration tool as stated above? I have about 6 cameras I’m in the process of restoring it’s slowing things down big time

"Say I replace an encoder, do I need to wipe the values"
If you replace an encoder and need calibration, you do not have to wipe any values. Just run the calibration.

@h-elsner provided a download page for the latest versions of his software, including the calibration programs and the associated instructions:
"Downloads"