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

Replacement for the Typhoon H GUI

h-elsner

Premium Pilot
Joined
Mar 23, 2016
Messages
2,209
Reaction score
1,908
Location
Bavaria / Germany
Website
h-elsner.mooo.com
I'm currently working at a replacement for the Typhonn H GUI that works with LINUX too. Some functionality is already working. The interesting part is the better visibility what is going on with GPS. We can better identify a bad GPS backup battery by (indirectly) checking the almnach.

GPS_data.png
 
Take e look how the switches are handled via serial. As example NFZ. There should be more switches in FC. Commands are not encrypted (I guess).
 
As a next step you can reverse the flashing process and inject a small code, to read bootloader. Possible this or not IDK. But to read back the flash area should be possible. For sure there is a checking process after block writing.

EEPROM is a part of flash...
 
As a next step you can reverse the flashing process and inject a small code, to read bootloader. Possible this or not IDK. But to read back the flash area should be possible. For sure there is a checking process after block writing.

EEPROM is a part of flash...
The build-in read protection of the STM32 processor family is not so easy to hack. I read nowhere that someone did it.
 
Take e look how the switches are handled via serial. As example NFZ. There should be more switches in FC. Commands are not encrypted (I guess).
You need a licence file. FC checks it. Message57 uploads the licence. I don't wand to make this public because I wand not be responsible if someone makes thumb things...
 
  • Like
Reactions: Pier2162 and Vaklin
Just add an option to lock/unlock if you have license file or code as text.
 
Again strange things happen. Up to now I had the impression that the motor numbering is counterclockwise. This was also my interpretation of the motor error codes in Motor_status in flight logs. Also the error beep code support this view.
Typhoon H_Motor Reihenfolge.png

Again, this was my understanding up to now.

When I try to test the motors and send Motor Number 1 then the number 6 is rotation. The motor numbers in the Command message follows this picture:

Typhoon H_Motor Reihenfolge.png

So, what is right? Can someone confirm, that Q500log2kml motor_status interpretation is right, with other words, when it says this motor is affected, is this motor affected then?
I'm not 100% sure, but the beep codes are like in picture 1. This means the motor numbers in command message (picture2) are wrong assigned? During testing I destroyed an ESC on my Typhoon H and now I don't dare to continue.

I would like to get some help from the community to find out what is correct numbering. I tend to ignore the numbers in the command message and follow picture 1.
Looks Yuneec does SW development in the same way like assigning the wiring colors in HW....
 
View attachment 31572

Again, this was my understanding up to now.


So, what is right? Can someone confirm, that Q500log2kml motor_status interpretation is right, with other words, when it says this motor is affected, is this motor affected then?
"So, what is right? Can someone confirm, that Q500log2kml motor_status interpretation is right, with other words, when it says this motor is affected, is this motor affected then?"

All I can do is confirm the drawing and Q500log2kml are the same.
Tested by:
1,) Started a Typhoon H.
2.) Grabbed the motor indicated by the blue LED in the original image above to force a failure (should be Motor 2).
3.) Downloaded the FlightLog.
4.) Opened the FlightLog in Q500log2kml.
5.) Q500log2kml indicated a motor failure of Motor 2, which is consistent with your original understanding and matches the original drawing above.

But that only confirms the drawing and Q500log2kml agree. It does not confirm both are correct with what Yuneec intended. There does not seem to be any drawing in the Typhoon H manual that specifically identifies the motor positions by number for the Typhoon H.

However, the H Plus manual includes the image below, which is consistent with the current Typhoon H motor assignments on the drawing and in Q500log2kml.

"When I try to test the motors and send Motor Number 1 then the number 6 is rotation."
Unlike they Typhoon H manual, the H Plus manual does include an image denoting the motor numbers. The image from the H Plus manual is consistent with the current Typhoon H assignments in Q500log2kml and the Typhoon H drawing above. I was unable to do the "low tech" test on an H Plus. Without propellers mounted, the motors do not run long enough to force one to stop. Trying to hold one to prevent it from starting just resulted in a failed start and no useful information in the flight log. I don't plan to try the test on the H Plus with propellers mounted. (I like the number of fingers I currently have.)

You mentioned a Typhoon H board has already been damaged. Can you safely test with an H Plus to see if the same apparent discrepancy appears?

This is the image from the H Plus Manual:
HPlus motors.jpg
 

Attachments

  • 1737502820306.png
    1737502820306.png
    70 KB · Views: 5
  • Like
Reactions: Steve Carr

New Posts

Members online

Forum statistics

Threads
21,253
Messages
244,872
Members
28,106
Latest member
asraderm