- Joined
- Sep 14, 2016
- Messages
- 32
- Reaction score
- 13
- Age
- 41
Beagles have such a crazy sound to em...I had one named mustard. Okay yea I am going to need many betas.
Hello guy's as per the request of a member I've now moved this thread to it's own section as not to step on ERICS toes.
Recently I've had a lot of down time and I'm in the process of reverse engineering the Flight Mode App (App used to fly our Typhoon H). Today I asked several members to post changes they would like made to the app and have enough interest to invest the time into this project and perhaps piss off Yunnec a bit lol. Please add functions you would love to see. I'm almost positive yes intact positive I'm not suppose to be doing this but hey to **** with em they all copy each anyway.
Dronie
Jimmy,
Just because Yuneec has not released the API does not mean it's impossible for just about everything to be messed around with. I'm fully able to write an API and certainly qualified to do so although I'm not one to toot my own horn.
I'll enlighten you when I decide what direction I want to take this in.
Cheers,
Dronie
That don't mean you will be successful or if its possible.
You where asking users what features they wanted and even taking prices.
Hello,
great idea, I will encourage it and eventually be prone to pay it if the price range is what you are suggesting.
Well about the app itself it seems there is a bit of confusion about a flight planner and a full control app. Those are two very different things, the first being an almost easy task, while the second is a very complex, high end program. Do you have any experience on that last?
As a longtime drone (multirotors and fixed wings) firmware tester I'm prone to test something but my TH is not disposable.
I did hope that someone *really experienced* in flight controller firmware would eventually propose something more flexible than the original firmware.
I mean:
- max bank angle selectable (= max speed)
- a better yaw control, which actually is almost unuseful in what I meas to be a yaw control. First of all proportional, to be able to refine the flying path
- camera multiple shots, e.g. each 1, 2 ,5 seconds etc. Useful for mapping.
- camera will remember last settings after reboot and especially after wifi loss
- dark screen in case of wifi loss. Sometimes having the last good shot could lead to a delay, before the loss is perceived: very dangerous.
- panic condition. The copter will fly only stabilized without compass and everything that could lead to issues, in case of compass issues etc.
- obstacle avoidance with selectable trigger distance and even switchable, so only distance and warnigs are working. That could be useful while recording videos close to rocks, to know the exact distance, but could be dangerous if the avoidance is triggered and the copter flies backwards, if there are trees close at back (yes high risk task, but anyway ...)
- RTH selectable between absolute (copter return to takeoff point), or relative to controller, like now
- a clock! switchable
About flight planner would be nice to have:
- real WP navigation, with stops, trigger actions (take pictures, start/stop video, loiter, watch at ..., RTH, land etc.)
- what happens in case of control link loss: selectable between RTH and continue the mission (this could be a feature of the control firmware too)
- selectable speed
- simulator!
About camera, but that is probaly off topics here I would like a multiple exposure feature (bracketing) and eventually a HDR feature.
Will come with more as soon as I recall them.
Best regards,
Ric
First of all: it's possible and I have proven it at least for the camera connection. However, creating a custom flight mode app is much more work, much more testing and much more risk. Imagine, the app crashes during flight and the copter loses any control and crashes. I don't want to be liable for that.
YES!Are you able to change any camera settings other than what Yuneec allows
YES!
My researches found out, that it's for instance possible to set the image sharpness of JPGs with a hidden command, which is not provided by the ST16 and the ST10+. This is only one command, but it takes plenty of time to find this out. Anyway, there are more commands to find out. You are right, that it's a closed system and we need to reverse engineer the firmwares. However, in many cases it is not required to create NEW commands to create NEW features. For instance, I implemented a FPV feature for the ST10+
Further features I am working on are exposure bracketing and intervalometer. These will also work without new commands.
As I said, I do not touch the FlightMode app on the remote. This is way to risky.
We use essential cookies to make this site work, and optional cookies to enhance your experience.