CGO 3 Replacement Pitch Magnet

[JMichael]

Hello All!

I am reaching out in the hopes that someone here may have a CGO 3 Pitch Magnet for sale.
I have replaced one in the past and I am aware that this magnet has to be indexed for the system to read it correctly.

If anyone reading this has a Pitch Magnet or a used (budget) CGO 3 with a good Pitch Magnet, please PM me and I will gladly pay for the part.

Thank You!

 

[Vaklin]

Just replacing will not did the task.
Probably the present magnet is good enough but the camera should be calibrated.

 

[JMichael]

Thank you for the reply.

My magnet has turned to dust.
CGO 3 lives in Florida most it's life.

I have replaced these magnets in the past and I have found a way to get around the calibration process.
It does take time but the end result is achieved weeks sooner than sending it in.

 

[Murray Martz]

Thank you for the reply.

My magnet has turned to dust.
CGO 3 lives in Florida most it's life.

I have replaced these magnets in the past and I have found a way to get around the calibration process.
It does take time but the end result is achieved weeks sooner than sending it in.

Contact John @Yuneec Skins, good chance he can help you out.

 

[cabinfourus]

I know this is an old thread, but it may help someone in the future.

Does anyone know if the older steadygrip (gopro) gimbals use these magnets? If so, there are still some of these out there, many of which are brand new. You could strip the motors and magnets from these.

Pardon Our Interruption...

 

[h-elsner]

Does anyone know if the older steadygrip (gopro) gimbals use these magnets?

An interesting question. That makes me go down to the basement and to have a look on a defect GB203. And yes, that are the same magnet rings (Ø3,5mmm x Ø2mm x 1,5mm).
You can earn three of them per GB203 because the yaw motor has the same.

 

[cabinfourus]

An interesting question. That makes me go down to the basement and to have a look on a defect GB203. And yes, that are the same magnet rings (Ø3,5mmm x Ø2mm x 1,5mm).
You can earn three of them per GB203 because the yaw motor has the same.

I am trying to get the CGO3P UART tool to work with one of my CGO3P gimbals. It won't connect, no matter what I do. It has a beeping code, but this shouldn't stop me from connecting, should it? Two longs and one short beep.

 

[h-elsner]

Do other CGO3P connect? What OS do you use, Windows? Beep Code means gimbal is working, it should connect.
What is the message in status bar of the tool if click 'Connect'?
What happens if you double click on the port selection box? A list of available ports should appear in the text box.

 

[WTFDproject]

I am trying to get the CGO3P UART tool to work with one of my CGO3P gimbals. It won't connect, no matter what I do. It has a beeping code, but this shouldn't stop me from connecting, should it? Two longs and one short beep.

If the proper start-up sequence is observed, the GUI should connect to the dongle before the camera/gimbal is even powered on. It displays the gimbal information, shortly after the camera/gimbal is powered on.

1. Ensure the GUI is NOT RUNNING.
2. Ensure the dongle is REMOVED from the PC.
3. Plug in the dongle first.
4. Start the GUI
5. Press the GUI connect button.
6. Verify the GUI is connected to the dongle.
7. When the GUI shows connected, power on the camera/gimbal.

There are no short cuts on the start-up sequence. At least not on my system. I always have to turn off the camera/gimbal, shut down the GUI and remove the dongle prior to starting the next session.

 

[cabinfourus]

Do other CGO3P connect? What OS do you use, Windows? Beep Code means gimbal is working, it should connect.
What is the message in status bar of the tool if click 'Connect'?
What happens if you double click on the port selection box? A list of available ports should appear in the text box.

I will try a different CGO3P today, and let you know.
I can use Linux or Windows, but I am using Windows right now.
I don't see a message coming up, nothing happens at all.
If I click on the ports, I do see three separate ports. I opened Device Manager to make sure I was using the correct port with my cable.
I will try WTFD's suggestions tonight also, and post my results.
It could be my Serial to USB programmer. I ordered another one, and then found my Q500 cable (lol).
Does the FW version matter?
I may post some screenshots to better explain my problem.

 

[cabinfourus]

If the proper start-up sequence is observed, the GUI should connect to the dongle before the camera/gimbal is even powered on. It displays the gimbal information, shortly after the camera/gimbal is powered on.

1. Ensure the GUI is NOT RUNNING.
2. Ensure the dongle is REMOVED from the PC.
3. Plug in the dongle first.
4. Start the GUI
5. Press the GUI connect button.
6. Verify the GUI is connected to the dongle.
7. When the GUI shows connected, power on the camera/gimbal.

There are no short cuts on the start-up sequence. At least not on my system. I always have to turn off the camera/gimbal, shut down the GUI and remove the dongle prior to starting the next session.

When I get home, I will give this a try.
Would the firmware cause this problem?
Thanks

 

[h-elsner]

There are not so many gimbal FW versions. I think, no.
If you unplug the dongle and double click on the port list one COM port should disappear.
When you plu in the dongle and double click on the port list the COM port of the dongle should be added to the list. This is then the COM port for the dongle, usually the last in the list.

 

[h-elsner]

I have added a button to renew the port list. Download link on my homepage as usual.

 

[WTFDproject]

When I get home, I will give this a try.
Would the firmware cause this problem?
Thanks

I have had no problems with the firmware on Windows 10 PC. Beyond that, @h-elsner would know more.

 

[cabinfourus]

So, I came home and went through everything, changing up the boot sequence each time, and it seems to connect, but I don't get any readings.
I plug in the USB programmer, open the APP, click on port then connect, and power up the gimbals/camera. If I power up the camera first and let it level, with the USB already plugged in and the APP open, when I click on connect, the camera goes limp.
Should I try to calibrate one and see what happens? I tried three different cameras and got the same results.
Look at the pics I attached and you can see the empty fields.

 

[WTFDproject]

So, I came home and went through everything, changing up the boot sequence each time, and it seems to connect, but I don't get any readings.
I plug in the USB programmer, open the APP, click on port then connect, and power up the gimbals/camera. If I power up the camera first and let it level, with the USB already plugged in and the APP open, when I click on connect, the camera goes limp.
Should I try to calibrate one and see what happens? I tried three different cameras and got the same results.
Look at the pics I attached and you can see the empty fields.

"when I click on connect, the camera goes limp."
That is normal. The calibration is run with "motors off", allowing only the calibration sequence to move the motors. You must have some sort of connection. You should check the connections on your "test stand" to ensure nothing is crossed to the wrong point.

"Should I try to calibrate one and see what happens?"
I would.
But I would check the connections first.
And maybe run the power supply up to nominal voltage for the CGo3+. And make sure the amps aren't limited.

 

[h-elsner]

You have connection with the USB-Serial converter - good. No driver or Windows problem.
I think the tool sends messages (I don't see the status bar). But there is no answer from the gimbal.
My first thought is that Rx and Tx are interchanged. Swap it and try again.
Another idea is to try baud rate 230400 as GB203 has and 500000 if the board is from a H520 CGO-ET. Not a high probability but easy to test.