New Firmware

[CraigCam]

I would also bet my life... that little of what has gone on with the FAA has anything to really do with your safety and a whole lot more to do with amazon and walmarts ideas... and the FAA just wanting to insure they get their hands in the mix. Up until august Amazon and Walmart could have moved forward with no restrictions and having to pay nothing to anyone to do so. Now... they have to get waivers and permits from the FAA. funny how that works isnt it... but yet... the average joe has been flying drones and RC stuff all over for awhile now.... but yet moments after amazon announces amazon air... FAA enacts part 107. yea... safety my rear end.

And it was out of control and still is. It was already in process and the AMA initially was not onboard because drones were already creating parameters that are completely different than typical RC piloting. Planes fly at dedicated air parks and RC pilots are very clear on flight prep and safety. It was with a lot of input from manufacturers, the AMA, and the multi rotor associations that have popped up that helped draft this set of suggested regulations. It's not that restrictive. What do you do that requires so much elevation? You've let corporate overlords dictate so much access in your life at every turn with every digital update you've ever done to any connected device you own and lost familiar set ups and preferences with every OS you own. This is no different. Good luck and I hope you don't encounter a surprise. We will have to agree to disagree.


Sent from my iPad using Tapatalk Pro

 

[Grimsin]

And it was out of control and still is. It was already in process and the AMA initially was not onboard because drones were already creating parameters that are completely different than typical RC piloting. Planes fly at dedicated air parks and RC pilots are very clear on flight prep and safety. It was with a lot of input from manufacturers, the AMA, and the multi rotor associations that have popped up that helped draft this set of suggested regulations. It's not that restrictive. What do you do that requires so much elevation? You've let corporate overlords dictate so much access in your life at every turn with every digital update you've ever done to any connected device you own and lost familiar set ups and preferences with every OS you own. This is no different. Good luck and I hope you don't encounter a surprise. We will have to agree to disagree.


Sent from my iPad using Tapatalk Pro

Um half of that doesnt make total sense. But yea were going to have to just agree to disagree. Um yea im not even sure what we are agreeing to disagree on with that last post.... LOL.

 

[Team Sheltie]

I guess I don't see it that way. This is a fledgling field with such great potential but the level of ignorance form the general public about why we fly is astounding. Every person who decided that they are above the stated and common sense parameters regarding our air space envelope is putting in my opinion all of us at risk of being grounded.
I'd hate to see self policing become real policing. Just because my car can go over 100mph does not mean it's a smart thing to do. Obviously the disregard for 400' created the new fence with the firmware update so there would be no compliance issues with the TH moving forward since the regulations came into place during H development.


Sent from my iPad using Tapatalk Pro

I couldn't have said it better myself. I totally agree with you on the 400 feet limit. Don't go blaming Yuneec for this restriction. Blame the people that don't follow the rules. You have forced Yuneec's hand. It's all about keeping it safe for everyone.

 

[Rubik]

I couldn't have said it better myself. I totally agree with you on the 400 feet limit. Don't go blaming Yuneec for this restriction. Blame the people that don't follow the rules. You have forced Yuneec's hand. It's all about keeping it safe for everyone.

As has been repeatedly pointed out, the US FAA regulations do not specifically restrict altitude for hobby UAVs. Part 107, which applies to commercial applications, restricts altitude to 400 ft above ground level without a waiver. Our $5 FAA registration "guidelines" say to fly below 400 feet. Yuneec has interpreted all this to mean 400' above the take-off altitude. If I am flying up a hill, I can easily fly much higher than 400' above take-off altitude but the drone would still be within 400' above ground level (directly below). I live in mountainous country and would like Yuneec to lift the 400' ceiling limitation. I will send this argument into Yuneec USA.

 

[Rubik]

As has been repeatedly pointed out, the US FAA regulations do not specifically restrict altitude for hobby UAVs. Part 107, which applies to commercial applications, restricts altitude to 400 ft above ground level without a waiver. Our $5 FAA registration "guidelines" say to fly below 400 feet. Yuneec has interpreted all this to mean 400' above the take-off altitude. If I am flying up a hill, I can easily fly much higher than 400' above take-off altitude but the drone would still be within 400' above ground level (directly below). I live in mountainous country and would like Yuneec to lift the 400' ceiling limitation. I will send this argument into Yuneec USA.

Here's the response I got from Yuneec, almost immediately:
"Hello,
Thank you for bringing this to our attention. This has been forwarded to our programmers to resolve. An update will follow once corrected. Please let us know if you have any other questions."

 

[Team Sheltie]

As has been repeatedly pointed out, the US FAA regulations do not specifically restrict altitude for hobby UAVs. Part 107, which applies to commercial applications, restricts altitude to 400 ft above ground level without a waiver. Our $5 FAA registration "guidelines" say to fly below 400 feet. Yuneec has interpreted all this to mean 400' above the take-off altitude. If I am flying up a hill, I can easily fly much higher than 400' above take-off altitude but the drone would still be within 400' above ground level (directly below). I live in mountainous country and would like Yuneec to lift the 400' ceiling limitation. I will send this argument into Yuneec USA.

 

[Team Sheltie]

I see your point and understand your frustration. I was only thinking of us guys that are living somewhat around sea level. For us, 400 feet should be plenty. Sounds like Yuneec has listened and will be addressing the problem in a future firmware update.

 

[CraigCam]

I see your point and understand your frustration. I was only thinking of us guys that are living somewhat around sea level. For us, 400 feet should be plenty. Sounds like Yuneec has listened and will be addressing the problem in a future firmware update.

They said a firmware update to auto pilot is coming to give us back height control in angle mode yesterday. I went up to 396' feet and stopped. Man they stole 4' from me!


Sent from my iPad using Tapatalk Pro

 

[Grimsin]

As has been repeatedly pointed out, the US FAA regulations do not specifically restrict altitude for hobby UAVs. Part 107, which applies to commercial applications, restricts altitude to 400 ft above ground level without a waiver. Our $5 FAA registration "guidelines" say to fly below 400 feet. Yuneec has interpreted all this to mean 400' above the take-off altitude. If I am flying up a hill, I can easily fly much higher than 400' above take-off altitude but the drone would still be within 400' above ground level (directly below). I live in mountainous country and would like Yuneec to lift the 400' ceiling limitation. I will send this argument into Yuneec USA.

I couldn't have said it better myself. I totally agree with you on the 400 feet limit. Don't go blaming Yuneec for this restriction. Blame the people that don't follow the rules. You have forced Yuneec's hand. It's all about keeping it safe for everyone.

I am sorry but I will never agree with the idea that i forced someone to impose restrictions on me in any industry or aspect of life. Get out of the box.

 

[wedbster]

I may be wrong, but didn't 1.3 introduce channel redundancy? That means the ST-16 can hop over to the 5.8Ghz link to control the H if the 2.4Ghz link drops. It would be very risky running the ST-16 on 3.xx if that software assumes that the FC can also be controlled on 5.8Ghz, when in fact the FC is running an older version of the firmware that does not work that way. The first thing you'd know about it would be a flyaway.

You are wrong
http://download.yuneec.com/Typhoon_...16 Firmware Update Version B25 What's New.pdf

 

[Grimsin]

You are wrong
http://download.yuneec.com/Typhoon_H/ST16/ST16_V3.1.25/ST16 Firmware Update Version B25 What's New.pdf

Do you by chance have what was in the 1.3 update just so we can see what we are lacking when running the 1.29

 

[Ralphy]

Besides... just extract the 1.3 AP from the the 3.1 update and keep both AP's on hand and you could update and rollback as needed. Anytime you need to ditch the 400ft restriction just rollback. When your done... update back to 1.3 Takes like 10 seconds. Just like the play store fix's... If you have any experience flashing android roms this is all vary easy and switching between a moded version and back to factory is a cinch.

I dont like this 400' nonsense restriction, I need to climb up to towers higher than 400'. I got 7zip the 3.0 bin and the 3.01 bin.

What exactly are the steps to override this restriction? You can PM me if youd like

thanks

 

[Rubik]

I'm not sure if this is the right place to ask this. Since the latest update, when I touch a Trim pad, I get a big message box but no place to select OK or CANCEL. It's as if my text is too large to fit everything in the box. Therefore, I am unable to use the Trim function. Has anyone else had this issue?

 

[RiverRunner]

I'm not sure if this is the right place to ask this. Since the latest update, when I touch a Trim pad, I get a big message box but no place to select OK or CANCEL. It's as if my text is too large to fit everything in the box. Therefore, I am unable to use the Trim function. Has anyone else had this issue?

Change your text size. That will solve it.

 

[Tuna]

I'm not sure if this is the right place to ask this. Since the latest update, when I touch a Trim pad, I get a big message box but no place to select OK or CANCEL. It's as if my text is too large to fit everything in the box. Therefore, I am unable to use the Trim function. Has anyone else had this issue?

Yes, they have. Your text size (Android settings) is too large and the OK button has been pushed off the bottom of the dialog. Reset to normal (go to Pad mode, Android settings...) and you'll be able to dismiss it.

 

[Grimsin]

I dont like this 400' nonsense restriction, I need to climb up to towers higher than 400'. I got 7zip the 3.0 bin and the 3.01 bin.

What exactly are the steps to override this restriction? You can PM me if youd like

thanks

Did you figure it out? Sounds like you might of? If not I can tell you how to go about it. Its fairly simple once you have the 1.29 file extracted from the 3.0 bin plug your H into your computer and use the GUI software from Yuneec to then update just the one file. Its not called autopilot when your looking at the GUI but you can match all the numbers up accordingly....

 

[Ralphy]

Did you figure it out? Sounds like you might of? If not I can tell you how to go about it. Its fairly simple once you have the 1.29 file extracted from the 3.0 bin plug your H into your computer and use the GUI software from Yuneec to then update just the one file. Its not called autopilot when your looking at the GUI but you can match all the numbers up accordingly....

No i didnt right now i screwed it up! I flashed the H with a old firmware TyphoonH_Ver2.21_A.bin and now the st16 doesnt pick it up.

I made a new bin file with 7 zip with the files in the screenshot above and i tried to flash it to the H. I replaced autopilot 1.30 with 1.29 in TyphoonH_Ver3.01_A.bin and my plan was to put in on an sd and update it via the H camera.

I am going to try to flash it back to the latest firmware and then i need your guidance going about it via GUI

 

[Grimsin]

No i didnt right now i screwed it up! I flashed the H with a old firmware TyphoonH_Ver2.21_A.bin and now the st16 doesnt pick it up.

I made a new bin file with 7 zip with the files in the screenshot above and i tried to flash it to the H. I replaced autopilot 1.30 with 1.29 in TyphoonH_Ver3.01_A.bin and my plan was to put in on an sd and update it via the H camera.

I am going to try to flash it back to the latest firmware and then i need your guidance going about it via GUI

Once you have flashed back to the latest everything. Plug the H into your comp and open the GUI software. Then top left one of the drop downs says tools. Click it and hit firmware update. It will ask you to select a file. Select TyphoonH_FC_V1.29_21_10_2016.yuneec which you should of extracted from the 3.0 bin file. It will then update the H to the 1.29.

 

[Ralphy]

Once you have flashed back to the latest everything. Plug the H into your comp and open the GUI software. Then top left one of the drop downs says tools. Click it and hit firmware update. It will ask you to select a file. Select TyphoonH_FC_V1.29_21_10_2016.yuneec which you should of extracted from the 3.0 bin file. It will then update the H to the 1.29.

Im not having any luck with this GUI. Despite connecting via usb cable i keep getting a Parameter name ort name Value cannot be null and operation timeout anytime i try doing something to the firmware.

I've tried two different computers already

 

[Grimsin]

Im not having any luck with this GUI. Despite connecting via usb cable i keep getting a Parameter name ort name Value cannot be null and operation timeout anytime i try doing something to the firmware.

I've tried two different computers already

Your plugged into the right port on the H right? there are 3 micro usb ports on it... if you have realsense anyhow. You need to be plugged into the one that is on the H body itself. Not the one on the realsense or the one on the cgo3. You installed the drivers that go to the GUI software correct?

Check on youtube for some of the tutorials on how to get connected to the H with the GUI.