Hello Fellow Yuneec Pilot!
Join our free Yuneec community and remove this annoying banner!
Sign up

So far, success!

Joined
Apr 5, 2025
Messages
14
Reaction score
2
Age
39
Hello ladies and gentlemen, I find myself the operator of a Typhoon H Plus with the Intel Realsense option, and have replaced a couple arms that were busted in one fashion or another.

At this point, I'm under the assumption that the arm replacement has gone relatively successfully because it powers on, is communicating with the base station, and is growling at me. I will post a video of the Typhoon powering on (following up until this point the "recommended" procedure of letting the ground station boot, then powering on the drone) to show you all where I'm at right now.

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

Where do we go from here? It's telling me to perform a compass calibration, but not giving me the option, OBS Avoidance not available, it can't acquire GPS (it couldn't when it was functional and flying, either), and the indicator lamp is pulsing red while the drone itself is beeping in the manner you heard in the video.

If it is obvious that I have re-assembled the drone incorrectly, it is my first assumption, but after having perused what resources I've been able to find after about an hour of googling, there's no indication of where specifically my reassembly may have gone wrong. If the arms are hard-coded to the drone, that's the first stop. I replaced the 2 broken arms directly with arms from a donor drone bought on e-bay.

Please note, I am not a "newbie," just new to drones. My background is in manufacturing, most recently as a Quality Engineer, and I got my start with that job title at a PCB manufacturer working on plenty of things you all would love to hear about, most of which you don't have the clearance to hear about. Replacing components up to and including BGA is not out of the question, but usually when you've gotten as far as the equipment in question booting up and chirping at you, either a particular component can simply be replaced or plugged in, or you're not understanding what it's trying to tell you.

Did I mess up from the start by replacing the broken arms with arms from another drone? If not, what is it telling me to do?
 
This is not a H Plus but normal Typhoon H (H480). The sound indicates a HW error. Check if all connections on the main board are tight, no pin is bent and all wires are OK. Maybe the GPS module is not plugged in correctly.

You can connect the Typhoon H to the PC GUI software to find the not working sensor. The best documentation for repairs and debugging is the WTFDprocect - a collection of documents here in the forum.
 
Will do, will update with what I'm able to figure out from there. First thing's first is a micro-usb cable, all of which I foolishly discarded from my kit.
 
  • Haha
Reactions: WTFDproject
Did I mess up from the start by replacing the broken arms with arms from another drone? If not, what is it telling me to do?
Not at all. Each arm is either an A or a B. Check to ensure you have the right arm in each replaced location. But it does not matter for your problem. The drone can't fly with the wrong arms in place, but it will boot up just fine unless something else is wrong. Which is where you are.

"OBS not available" is pretty normal. It doesn't work until about 20 ft off the ground.

"First thing's first is a micro-usb cable, all of which I foolishly discarded from my kit"
As mentioned by @h-elsner, the LED flashing, the beep code and the Compass warning are the symptoms you would see if the GPS is not plugged in. It might be a good idea to check the GPS connection while waiting on a USB cable.

Also as mentioned by @h-elsner, the GUI will tell you a lot more, a lot faster, than anything else if the GPS module is in fact already plugged in correctly.
If needed, a couple of hints for GUI setup:
1.) You have to use a data capable USB cord. Standard USB charging cables do not work.
2.) You may need to set the file properties to "Run as administrator" and "Windows 7" compatibility.
3.) The GUI front screen mentions the possibilities of requiring additional USB driver(s). If your PC was built any time after Moses brought the 10 Commandments down from the mountain, you're probably already good.
4.) I think the GUI only comes in Windows version, but maybe some Macs can run it? (@DoomMeister will know the real story).
4.) The instructions for connecting the GUI are on the first screen.
6.) The latest GUI version can be downloaded from:
 
Last edited:
Alright ladies and gentlemen, I should have probably clarified earlier: this is a Saturday project. I'm getting paid OT for it, but it's still a "whilst getting other things done" type of project.

Here's the progress so far:
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

I downloaded the GUI tool, and didn't get much information from it. Here is its status now:
Screenshot 2025-04-12 103636.png
Screenshot 2025-04-12 103533.png

Screenshot 2025-04-12 103602.png

Screenshot 2025-04-12 103459.png


The fact that as of now it is no longer blinking red and red only and squawking incessantly is progress. It is also responding to the base station being turned on and I've even managed to presumably get it to enter compass calibration mode. Which is a step further than where I was.

How I got to here from my first post:

I opened her up, re-seated anything that could have been budged by assembling the fuselage body, proceeded to specifically NOT re-assemble the fuselage body fully in order to test which connectors might or might not change her tone when reseated in case it was one of the molex connectors around the periphery of the motherboard, and didn't have to do any such testing.

Now I'm off to try and re-assemble her and see if I can preserve her current disposition once all of her bits are back in their bobs.

I'm still worried that the GUI tool is picking up the fact that she's being connected (and while in USB mode going from "Connect the drone" to the first screen shot above, but still says in the lower left that the device is not connected.
 
I'm still worried that the GUI tool is picking up the fact that she's being connected (and while in USB mode going from "Connect the drone" to the first screen shot above, but still says in the lower left that the device is not connected.
The video shows the Realsense module hanging under the drone and apparently connected. It would be best to remove the Realsense and leave the camera off until you get the basics working.
The video also shows what appears to be a normal boot while needing a compass calibration. Which might be just because of some things in the background. After you get it assembled, go outside to try a compass calibration.

" the GUI tool is picking up the fact that she's being connected ......but still says in the lower left that the device is not connected.
I tried a few combinations of wrong USB cables and several versions of FC board misaligned, and was not able to re-create that observation. That one will take some more looking.
In the meantime, obviously none of the GUI images indicate any connection between the Drone and the GUI. So ensure the USB cable is a functioning data cable. Ensure both the internal USB cable is connected on the FC board end as well as connected to the USB data cable on the side of the drone. Be sure the GUI is running first, then ensure the drone is powered up BEFORE plugging the USB into the PC. Then I'm out of ideas at the moment
 
Last edited:
  • Like
Reactions: h-elsner
She's up and running, responding to the base station, turning on and even flying. Once I got her assembled again I turned her on and did a compass calibration. I'm fairly certain the cable I'm hooking up is a Micro USB data cable, I will experiment with various Win11 compatibility settings to see if that's the problem. I would like to troubleshoot getting her all the way functional.
 
  • Like
Reactions: WTFDproject
She's up and running, responding to the base station, turning on and even flying. Once I got her assembled again I turned her on and did a compass calibration. I'm fairly certain the cable I'm hooking up is a Micro USB data cable, I will experiment with various Win11 compatibility settings to see if that's the problem. I would like to troubleshoot getting her all the way functional.
Windows 7 or Windows 8 compatibility work best on mine. Also be sure to set it to "run as Administrator".
You might also try the H480GUI created by @h-elsner. It is more capable than the original GUI, in particular you can select the COM ports and frequencies.
 

Attachments

This is what it looks like before I plug her in:
Screenshot 2025-04-12 125340.png

And After:
Screenshot 2025-04-12 125510.png
The program jumps directly to the sensor information page, and the device information page shows:
Screenshot 2025-04-12 125524.png

So it's responding to the fact that the drone is getting plugged in.

This is with Compatibility mode set to Windows 7, and run as administrator. The camera isn't plugged in at all. And the cable is plugged in to the micro-usb port directly underneath the fuselage as shown in the first screenshot.
 
Very good. Driver and data capable USB cable are in place.
I see no reason now why it does not connect. You can try to force COM8 in the connection menu of the GUI.
Have you unplugged the RealSense module?
 
Same result with RealSense module disconnected.

I have a replacement mini-usb board from the donor drone. I'm going to try replacing that to see if that fixes our predicament.
 
I have a replacement mini-usb board from the donor drone. I'm going to try replacing that to see if that fixes our predicament.
Do you also have a replacement Flight Control board from the donor drone?
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
If the STMicroelectronics Virtual COM Port appears then the HW side to the drone is OK. I do not understand why Windows is not recognize the messages from the drone to the GUI.

You can try the alternative GUI from here: http://h-elsner.mooo.com/downloads/H480GUI.zip
There we can see at least if and what messages will be sent and received. No admin or compatibility mode is needed.
 

Members online

Forum statistics

Threads
21,327
Messages
245,659
Members
28,262
Latest member
kybelvody