Binding issue in Q5004k

[Edward J]

I have a 9 year old q500k and a the original owner. I last used it years ago and it worked fine. I cannot get controller and drone to bind but the CG03 camera binds each time. When I turn controller on then the drone it boots up and says welcome pilot but when trying to bind and after tipping drone 45 degrees forward (except for one time) i could not get drone ready to fly. Because propellers were not on I turn off both devices and when I turned things back on I just get a red light that blinks approximately 3 times per second and has a 3 part tone.
I connected the drone to the gui and I get all 4 motors to run in the test location but I get an accelerator error and all else green check marks. I took top cover off and found no loose wires or burn
Marks or unusual signs. That was the only time the cover has been removed. I’m perplexed that I did some series of tilts or order of start up and got it to start once and simply can’t duplicate that event. Any help would be appreciated
Ed

 

[WTFDproject]

I have a 9 year old q500k and a the original owner. I last used it years ago... got it to start once and simply can’t duplicate that event. Any help would be appreciated
Ed

...got it to start once and simply can’t duplicate that event....
The controller and drone were bound that one time you got it to start. If you have not done a factory reset or created a new model, it is still bound. The drone will not initiate a new binding sequence if the controller to which it is already bound is powered on.
With all that said, the problem seems to be more that the accelerometer is out of calibration and will not allow the mainboard to initialize. The drone/controller also will not bind if the drone main board does not initialize.
You can remove the camera and try the trick of tilting the drone back onto the rear motors and turn it on to see if that will help. Not likely, but worth a try.
If you can get the drone to initialize, you can run compass and accelerometer calibrations.

 

[h-elsner]

Can you send a screenshot from GUI showing that ACC error?
Do you have telemetry data on the ST10 (distance, altitude, voltage...)? If yes, it is bound.

 

[Edward J]

So I now have partial success so thank you. I tipped the drone on its back legs and noticed it continued to initialize and never went to red with tone mode. I then tipped it forward at 45 degrees twice and got yellow blinking light. I went to bind mode and still wouldn’t bind. I then realized I had left usb stick attached which meant connector in drone wasn’t. I reconnected it and started process over. This time once I had yellow blinking light it did connect. Motors start, camera is controlled so go so far. I then placed drone north facing and rolled forward, turned 45 etc and eventually got to beeps sating calibrated. I turned off drone and controller then restarted controller then drone while drone was flat and once again got red blinking light with drone not initializing. Put drone on hind legs and got it to bind after selecting model etc.
I’m not sure what to do but I don’t know how to calibrate acceleration part. That could be the current problem.
I have to thank you for getting me this far. It means mechanically there is nothing wrong but software/controller still needs a tweak.
Ed

 

[WTFDproject]

So I now have partial success...but I don’t know how to calibrate acceleration part. ....... It means mechanically there is nothing wrong but software/controller still needs a tweak.
Ed

"I don’t know how to calibrate acceleration part"
This video is about 5 minutes long, but the part of calibrating the accelerometer is only about 30 or 40 seconds of it. Skip to about 1:40 for the accelerometer.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

"It means mechanically there is nothing wrong but software/controller still needs a tweak."
It could also mean the accelerometer is going bad. If proper calibration helps, that's great. If it doesn't, it may mean an eventual board or chip replacement will be needed.