Hello, I have another problem but this time with my Typhoon H drone and CGO3+ camera. After connecting the drone to the camera after a long while there is an image from the camera, but unfortunately I can't move the camera at all either up and down or side to side. How can this be fixed?
Image problem with the CGO3+ camera
- Thread starter polskipilot
- Start date
Does the camera stabilize level and straight forward?
Does the camera emit any repeated beeping sounds?
Does the drone respond to motor stop/start and flight mode changes from the controller?
Do you have another ST16 to see if it is a controller issue?
h-elsner
Premium Pilot
- Joined
- Mar 23, 2016
- Messages
- 2,319
- Reaction score
- 2,053
- Location
- Bavaria / Germany
- Website
- h-elsner.mooo.com
Drone not bound to ST16? All what you describe is present whe WiFi (5GHz) is connected. All you describe what is not working is controlled via ZigBee connection 2.4GHz.
I would create a new fresh model from scratch and bind drone (SR24 with 2.4GHz) and WiFi to this model and try again.
I would create a new fresh model from scratch and bind drone (SR24 with 2.4GHz) and WiFi to this model and try again.
Sorry it's been so long but I was looking for another controller and things look like this:
1. the drone's tail light blinks blue
2. a different controller after creating a new model catches the image at one time and at another time I have to manually select the camera (this takes a very long time and the camera does not always show up - but when it does, there is an image but no camera movement - neither upwards nor sideways and the LED on the back of the drone keeps blinking blue)
I have unplugged the camera and plugged it in again but without any visible effect (the camera stabilises but there is no sound).
1. the drone's tail light blinks blue
2. a different controller after creating a new model catches the image at one time and at another time I have to manually select the camera (this takes a very long time and the camera does not always show up - but when it does, there is an image but no camera movement - neither upwards nor sideways and the LED on the back of the drone keeps blinking blue)
I have unplugged the camera and plugged it in again but without any visible effect (the camera stabilises but there is no sound).
The blue blinking LED means the drone is not bound to the controller. When you create a new model you have to bind the new model to the drone. The camera upwards and sideways movements are part of the DRONE bind, not part of the camera bind.
These videos can be translated into many languages using the closed caption option at the bottom of the screen.
But unfortunately it looks like I have a camera image unfortunately still no control.
I created a new model (as in the video), then connected it (first the led on the back lit up blue and then orange) but still no control. What is still wrong?
I created a new model (as in the video), then connected it (first the led on the back lit up blue and then orange) but still no control. What is still wrong?
If the bind was successful and the flight mode switch is in the normal center position, the rear LED should either flash slow purple or go solid purple when GPS is acquired.
What color/pattern is the rear LED?
It flashes blue, then when I tilt it, it turns orange and that's it, and of course there's still an image but you can't move the camera despite the correct switch position. The camera stabilises when it starts up.
The orange flash is only the first step of the bind. There is more to it. You may be able to succeed by watching the videos closely. If that does not work you can run the full Typhoon H Binding Verification.
The verification is not just "binding instructions". It is a verification of the MANY hidden clues in the binding process. The purpose is to identify abnormal conditions that are preventing a successful bind and to identify the exact point the binding process is failing. That information can assist in determining the best course to remedy the problem.
You will need to perform every step up to the point the verification does not match what you see. Do not skip any steps. Every step must be performed. Even the steps you have no doubt are already in the correct condition. After some preparation steps, the verification falls into a routine of directing an action, then verifying the correct response to the action. When you reach a verification step that does not match what you see, or if you are unsure if it matches, STOP. Report the step number back to the forum, and what you actually saw at that step. We can then go from there.
Typhoon H Binding Verification
The verification is not just "binding instructions". It is a verification of the MANY hidden clues in the binding process. The purpose is to identify abnormal conditions that are preventing a successful bind and to identify the exact point the binding process is failing. That information can assist in determining the best course to remedy the problem.
You will need to perform every step up to the point the verification does not match what you see. Do not skip any steps. Every step must be performed. Even the steps you have no doubt are already in the correct condition. After some preparation steps, the verification falls into a routine of directing an action, then verifying the correct response to the action. When you reach a verification step that does not match what you see, or if you are unsure if it matches, STOP. Report the step number back to the forum, and what you actually saw at that step. We can then go from there.
Typhoon H Binding Verification
Welcome.
Everything is almost fine except that there is already a camera control but at the moment there is a very loud sound which is all the time (as in the video). It's the first time I've encountered something like this (besides it takes a very long time before the camera image in the drone comes on) but for now let's do something about the sound
www.dropbox.com
Everything is almost fine except that there is already a camera control but at the moment there is a very loud sound which is all the time (as in the video). It's the first time I've encountered something like this (besides it takes a very long time before the camera image in the drone comes on) but for now let's do something about the sound
Dropbox
www.dropbox.com
Attachments
Last edited:
The noise sounds like the noise caused by the right controller stick not in center position. Try moving the stick around to see if the sound clears. Or move the controller far enough away you can tell if the sound is coming from the controller or from the drone.Welcome.
Everything is almost fine except that there is already a camera control but at the moment there is a very loud sound which is all the time (as in the video). It's the first time I've encountered something like this (besides it takes a very long time before the camera image in the drone comes on) but for now let's do something about the sound
Dropbox
If the issue is the stick, we can work on that.
Unfortunately but the sound is clearly from the drone and the LED at the back lights up intermittently 4x in purple and there is a camera control so the problem so far is just the sound of the drone. After putting it outside it caught the GPS for a while and it changes 9 to 10 satellites but after a while there is AQUIRING again and all the time the sound from the drone as in the video. There is still camera control all the time i.e. the previous hint gave positive results. Question could the problem be the GPS with too low a battery or the sticks as in the photo or something else entirely?
Remind me also how the sticks are calibrated on the Typhoon H?
Remind me also how the sticks are calibrated on the Typhoon H?
Attachments
h-elsner
Premium Pilot
- Joined
- Mar 23, 2016
- Messages
- 2,319
- Reaction score
- 2,053
- Location
- Bavaria / Germany
- Website
- h-elsner.mooo.com
J4 (roll stick) is the reason for the sound. The drone warns if sticks are not centered to avoid surprises after take off.
It looks like stick calibration is not enough. Unplug and plug the connectors for the sticks inside the ST16 would be my first attempt.
Stick calibration by Steve Carr:
It looks like stick calibration is not enough. Unplug and plug the connectors for the sticks inside the ST16 would be my first attempt.
Stick calibration by Steve Carr:
The issue marked in red is causing the beep. The green also needs to be addressed. See attached image.
Calibration is not the first correction. The cause is corrosion build up. You must first clear the corrosion. Calibration with corrosion present may create dramatic issues if the corrosion suddenly clears itself during flight. After cleaning the corrosion it will probably NOT need calibration.
1.) Vigorously stir each affected stick for a short while, then ensure the hardware monitor shows the sticks are centered and return to center easily when moved.
2.) If stirring the sticks does not resolve the issue, more aggressive maintenance may be needed. Refer to:
Control Stick Gimbal Maintenance
and/or
3.) IF stick maintenance does not resolve the issue, repair/replacement may be needed.
4.) If a gimbal is replaced, the new gimbal will require calibration:
ST16 Calibration Video Links
Thank you very much for your help, fortunately the calibration helped and there was no need to open the apparatus. It is OK
If you ran the calibration without correcting the actual problem, things are not really OK.
They will certainly seem OK.
Until they are not.
If it happens while in flight, it is likely to result in an unfortunate outcome.
Hm. If that's what you're claiming, I'll actually take the controller apart and clean everything inside and sort out the wiring.
Similar threads
