Those who paid $19.99 and have not upgraded to the other flight modules will we be grandfathered in to the new price point or will we have to pay $10 bucks more AFL?
You make some good points, that's actually pretty fair. Don't get me wrong, I don't feel ripped off or cheated or anything like that and I bought autopilot without having to think about it too much, it's a useful app...but i can understand the point of view of people who might.
All the in app upgrades will become free, and you will get new versions of the app for free as well.Those who paid $19.99 and have not upgraded to the other flight modules will we be grandfathered in to the new price point or will we have to pay $10 bucks more AFL?
The beta for 2.2 is slated to start at the end of this week. As for 3.0, we can't say until we have 2.2 out the door.Do you have some release dates pour version 2.2 and 3 ?
Another note on the upcoming price change: In app upgrades will become free today, and the base price of the app will increase on Friday. See the announcement on our homepage for more details.
This means that if you have not purchased Autopilot yet, you have a few days to lock in at the $20 price point.
Can you reproduce this / send the video / send the flight telemetry?I got a really weird twitch in the gimbal. It tilted the horizon 9 degrees (according to the on screen telemetry) to the right. This happend a couple of times before i reached the orbit but the orbit worked as usually.
What device are you using? Do you think it may be related to overheating?10 minutes into the session i suddenly lost telemetry (happend once before) and i had to restart the app.
Pull the files from the flights directory (not flightrecorder anymore). We will be updating the documentation closer to release.After the mission i tried to download to healthydrones but all i could get out of the app was two missions i flown a couple of weeks ago.
Im not allowed to post a file with the extension used in the log file. I changed it to a txt file to be able to post it, hope it works.Can you reproduce this / send the video / send the flight telemetry?
What device are you using? Do you think it may be related to overheating?
Pull the files from the flights directory (not flightrecorder anymore). We will be updating the documentation closer to release.
It works (it is just text). The log does show the gimbal roll sporadically tilting to 7-9 degrees. There should be an engagements folder also. Please send the one labelled to 2015-11-08-112458-177 [email protected]. I need to see if Autopilot was sending this roll command, or if the aircraft was spontaneously doing it (implying an IMU issue on the hardware side).Im not allowed to post a file with the extension used in the log file. I changed it to a txt file to be able to post it, hope it works.
No, it is still supported. Did you try to upload the telemetry from the engagements folder, or the flights folder? It has to be the one from the flights folder. Note: we will be adding auto-upload in 2.2 as well to make this whole process seamless.Have you removed the option to export to healthydrones? I cant seem to be able to do it anymore.
On the app crash, my guess is the app ran in to memory pressure. The iPad Mini 2 is an older and underpowered device and Autopilot is demanding a lot of it. It probably finally gave up after about 7 minutes. One thing to try (if you intend to engage for long periods), is kill all other apps and restart the iPad right before launching Autopilot to give it as many system resources as possible - or upgradeI use a ipad mini 2 retina with cellular connection with all the latest firmwares, ios, apps etc.
It works (it is just text). The log does show the gimbal roll sporadically tilting to 7-9 degrees. There should be an engagements folder also. Please send the one labelled to 2015-11-08-112458-177 [email protected]. I need to see if Autopilot was sending this roll command, or if the aircraft was spontaneously doing it (implying an IMU issue on the hardware side).
No, it is still supported. Did you try to upload the telemetry from the engagements folder, or the flights folder? It has to be the one from the flights folder. Note: we will be adding auto-upload in 2.2 as well to make this whole process seamless.
On the app crash, my guess is the app ran in to memory pressure. The iPad Mini 2 is an older and underpowered device and Autopilot is demanding a lot of it. It probably finally gave up after about 7 minutes. One thing to try (if you intend to engage for long periods), is kill all other apps and restart the iPad right before launching Autopilot to give it as many system resources as possible - or upgrade![]()
I think HD can only take zip files, and since the app crashed before the flight was finished, it wasn't able to compress the data. If you zip up the directory in the flights folder, will it take it?In the flights folder i can only see the file i attached to my previous post, telemetry.tsv, and healthydrones refuse to upload that one. There are no other files in that folder.
Nope, didnt work. I will try a new flight to morrow if the weather allows it and try to reproduce the twitching of the gimbal so i can do another ttry with DH as well.I think HD can only take zip files, and since the app crashed before the flight was finished, it wasn't able to compress the data. If you zip up the directory in the flights folder, will it take it?
It works (it is just text). The log does show the gimbal roll sporadically tilting to 7-9 degrees. There should be an engagements folder also. Please send the one labelled to 2015-11-08-112458-177 [email protected]. I need to see if Autopilot was sending this roll command, or if the aircraft was spontaneously doing it (implying an IMU issue on the hardware side).
No, it is still supported. Did you try to upload the telemetry from the engagements folder, or the flights folder? It has to be the one from the flights folder. Note: we will be adding auto-upload in 2.2 as well to make this whole process seamless.
On the app crash, my guess is the app ran in to memory pressure. The iPad Mini 2 is an older and underpowered device and Autopilot is demanding a lot of it. It probably finally gave up after about 7 minutes. One thing to try (if you intend to engage for long periods), is kill all other apps and restart the iPad right before launching Autopilot to give it as many system resources as possible - or upgrade![]()
We use essential cookies to make this site work, and optional cookies to enhance your experience.