Replies to This Discussion

Permalink Reply by Paul Mather on January 10, 2011 at 12:27pm

There must have been a change to the ArduPilot GCS output at some point. Are you using the "Legacy" output? Where it's !!!LAT:XXXXX, etc or are you using a binary output?

 

If it's legacy, take a look at the output .pde file (it's been renamed several times) and look at the BTV: output. Make sure it's sending a non-scaled value. So 12.41 = 12.41. You might have something *1000 so the output is scaled way up.

• ▶ Reply

Permalink Reply by John Klier on January 11, 2011 at 2:11pm

I just checked and there is no scaling factor. However it does appear that if I divide by 1000 the voltage showing up in the GCS may be correct.

• ▶ Reply

Permalink Reply by Paul Mather on January 11, 2011 at 2:17pm

Give that a try. Oiriginally I had been multiplying by 1000 which would have worked fine for you...but I was told by another AP user that it was off by a factor of 1000 so I removed that.... So something must have changed at some point in the legacy protocol.

• ▶ Reply

Permalink Reply by John Klier on January 11, 2011 at 2:52pm

Okay, I'll do that. Thanks for the help. Fantastic program BTW!

• ▶ Reply

Permalink Reply by The Old Flyer on January 19, 2011 at 1:35pm

Happy,

I just tried to load a waypoint file into the latest version and got this error:

 

I got the same error with v 1.2.10.

I can email you the whole error message if you need it.

 

The GCS just gets better and better!

• ▶ Reply

Permalink Reply by Paul Mather on January 19, 2011 at 1:51pm

Irvin, please email it to happy@happykillmore.com

 

I'm planning on re-vamping the mission load/save function. I just edited the code to get by for now...my plan is to make a universal file format that I can use on my GCS to load and save in just my GCS or output in a file type for a specific auto pilot..

• ▶ Reply

Permalink Reply by Paul G. on January 19, 2011 at 4:03pm

Happy, could I just ask what data is used for the heading display ? the one were the compass rotates around a fixed arrow.

• ▶ Reply

Permalink Reply by Paul Mather on January 19, 2011 at 5:14pm

Depends upong the input source. It's "heading" not "bearing" or "yaw"... The data comes from the GPS for this indicator.

• ▶ Reply

Permalink Reply by Paul G. on January 19, 2011 at 10:20pm

ahh - I was hoping it could come from UDB_EXTRA data but to be honest I did not look and check that mag data is in there.

• ▶ Reply

Permalink Reply by Paul Mather on January 19, 2011 at 10:31pm

If I get yaw from the protocol (like I do with UDB_Extra) then I show that in the 3D model on the left. Both the GE model and the heading indicator take heading values from the GPS.

 

In the case of UDB_Extra, in the F2 message, arguments 7 and 10 make up yaw. Argument 15 is heading.

• ▶ Reply

Permalink Reply by Erik Hatch on February 20, 2011 at 10:01am

doe this GCS have a function to have the UAV return to land?

• ▶ Reply

Permalink Reply by Paul Mather on February 20, 2011 at 10:08am

Depends upon your auto pilot. AttoPilot, yes, ArduPilot Mega, soon, Gluonpilot, soon, Uavdevboard, soon, FY21AP, if they send me hardware. Everyone else, no (or at least I have nothing in the works with other auto pilots).

• ▶ Reply

• ‹ Previous
• 1
• …
• 4
• 5
• 6
• 7
• 8
• …
• 12
• Next ›
• Page