AutoQuad Forum

Hello,

Today i have tried the new Android GCS. First i have to say i really like the new GUI. Looks way better and improves the usability by quite a bit. However i found a few irregularities. Might be because i am still on 6.6 R19 but still i would like to know if that is the case.

1. I put takeoff and some waypoint. Takeoff to 10 meters (relative altitude) with 1 m/s vertical velocity. 0 Loiter and then to a waypoint 50 meters away. Works perfectly with 1.5.8. Well with the new one it shot up and sideways quite fast. Loaded the mission in 1.5.8 and the value of the Vertical speed was at height and the value of height was at speed. So it was a takeoff command to 1 meter with a speed of 10 m/s. That explains the behavior.
Now my question is if that is related just to r19 that i am using or is it a bug in the new GCS where the values are in the wrong place (or under the wrong label).
I exchanged the values in 2.3.3 (1 for height and 10 for speed) and it worked as expected. So i assume the fields are just labeled wrong.

2. After a mission with takeoff, 2 waypoint, return to launch i put a landing command. it executes perfectly up to the landing part. It would not initiate landing. I assume that is because i use R19. I imported the mission in 1.5.8 and when i try to edit the return to launch point it crashed the app. So i assume there is a difference in the code from 1.5.8 to 2.3.3. Also assuming that is related to R22... but i cannot confirm at this point. The same mission created in 1.5.8 executes perfectly.

Everything else worked ok as far as i tested but spend most of the day just playing around with missions and tuning the speed :p It flies perfectly with about 40 kph atm working on making it go even faster but i need better motors and bigger props.

So hopefully somebody can tell me what is up with the above points. Also if somebody has the hex file for r22 i would really appreciate if they could give it to me. I am to lazy to compile the code myself. Although if nobody has it i will have to do it

Thanks.

Oh yeah i forgot. AQ is awesome. Not the most stable FC on the shitty quad i have put it on and definitely not the easiest to setup and configure but by far the best performing UAV FC. Missions are executed very well. There is a hiccup here and there but overall very very impressive.

Hi Iceman, welcome to the club!

Are you sure you have v2.3.3 of the Android GCS? We're currently testing v2.3.0 internally.
So ... where did you get this future release? Wanna have, too!

Here you go:
http://autoquad.org/software-downloads/?did=29
Version 2.3.3
Everywhere i look it is labeled 2.3.3

I am ahead of the trend :p Any chance i could get the r22 hex file ?

Well, what can I say, I had placed a note that it was for r22
Between r19 en r22 the mission commands have been changed and I guess you already noticed that..
And, you are quit fast to download, so for now you must compile it yourself or wait. A hex file takes some time.

Well the takeoff is usable just have to switch the parameters. And i can create the entire mission on 2.3.3 and just import it in 1.5.8 to add return and landing :p

The distance between waypoints feature is very nice to have. And i like the whole feel of the new version. So until i compile the r22 i will still use it with this "workaround"

Thanks for clearing it up.

PS. Maybe a waring that it is just for r22 would be helpful for other users. You just wrote "Support for AutoQuad 6.6r22" which for me personally does not exclude r19 it just adds support for a new firmware. Maybe just my thinking is messed up...

I think joebar.rc is off for a well deserved meal and beverage
I was able to get a second 30-day eval license from Rowley; all I did was send another license request email.

You probably saw the other thread but if you happen to have a Linux machine, there is a simple, free and non-expiring way to build the hex file.

Regards,
- Felix

@Iceman: Attached are some HEX files for you in case you still have problems (r22, r25, r30)

gcs2.2.3 question about voltage refference:

What numbers to put inside the program setup?
are they independent of the type of battery (3s, 4S, etc)? (I guess)

In the screen there is a % value. I guess is the remaining % (in volts) w.r.t. limits.

For instance if you put 3.2vol as min limit, then in a 3S battery having 10volts, that number should be 4% (when you reach 3.2 x 3 = 9.6v, that % = 0). Is that the case?

Angel