Replies to This Discussion

Permalink Reply by Pete Hollands on January 6, 2010 at 11:24am

Example of colour coding Ardustation telemetry waypoint routes:.....

Permalink Reply by John C. on January 7, 2010 at 2:46pm

Thanks for the work Pete. It's looking good! I recently added the Time of Week output to my flight logs.

ie: !!!TOW:422022750,LAT:32248268,LON:-110833968,SPD:27.76,CRT:0.00,ALT:66,ALH:50,CRS:126.28,BER:218,WPN:0,DST:455,BTV:0.00,RSP:35,***

I plan on trying to use this in your script to create a "playable" timeline of the flight in google earth.

I'm sure you have a few legs up on me in this, but it seems that it would be a cool feature.

JC

Attachments:

• udall2.txt, 77 KB

• ▶ Reply

Permalink Reply by Pete Hollands on January 7, 2010 at 2:58pm

John,

Adam Barrow had the same idea. It is the right way forward, I agree.

Are you already parsing the TOW field ? I can add it to the ardustation telemetry parser in just a few minutes if you want it in the code. Alternatively, if you send me a patch (we are using Tortoise SVN which is a neat tool for exchanging changes and working with the code repository), then I'll review your code for TOW, before submitting to the repository.

Pete

• ▶ Reply

Permalink Reply by John C. on January 7, 2010 at 7:31pm

looks like I may have gotten it in there.

I just added this in the Ardustation telemetry parsing above the LAT parse:

match = re.match(".*TOW:(.*?),",line) # Time of week
if match :
self.tm = float (match.group(1)) # Compatibility
else :
print "Failure parsing Time of Week at line", line_no
return "Error"

Attached is the full file. Now to figure out how to make an actual timeline.

JC

Attachments:

• uav_log_to_kml.py, 62 KB

• ▶ Reply

Permalink Reply by Pete Hollands on January 8, 2010 at 1:13am

Hi John,

That is super. I'm delighted that you have started to understand the code.

Adding time meta data to the KML will be a big step forward. Getting something working initially may not be too much work. (I've not looked at the KML for this in detail but I know all the hooks are there).

There is a major piece of re-organisation that will need to be done later. I think that the folder structure hierarchy in the Google Earth Places folder should become:-

Waypoint Routes Folder
Waypoint 1 Folder
Waypoint 1
Vectors to Waypoint 1
Waypoint 2 Foldler
Waypoint 2
Vectors to Waypoint 2
Waypoint 3 Folder
Waypoint 3
Vectors to Waypoint 3

In this way, when you click on waypoint 2 Folder, it will immediately switch on both the route wall as well as all the small model planes showing orientation of the lane during that route.

That can come a little later, after we've provide the timeline system of Google on either the routes or the vectors.

I'll review and upload the code.

Pete

• ▶ Reply

Permalink Reply by Pete Hollands on January 8, 2010 at 2:35am

John,

Reviewed and uploaded to the repository.

I made a small change. If TOW is not there, then it not now considered an error. This makes the change compatible with any Ardustation telemetry that does not have TOW for now.

# JOHNC ADDITIONS
match = re.match(".*TOW:(.*?),",line) # Time of week
if match :
self.tm = float (match.group(1)) # Compatibility
else :
pass # If TOW is not there, it is not a major error for now
# Most Ardupilots do not report TOW of week in telemetry
# print "Failure parsing Time of Week at line", line_no
# return "Error"

Are you promulgating the TOW format change to the main Ardustation telemetry format ?

I also fixed some bugs in the handling of .txt, .log and no file extension - and how that is then used to create the .csv and .kmz files.

Pete

• ▶ Reply

Permalink Reply by Cronselaar on March 16, 2010 at 8:50am

Hi

May i ask. What was the final outcome? I would really like to be able to log my flights. I'm still a UAV/programmer noob... So please just explain it step by step.

• ▶ Reply

Permalink Reply by John C. on March 16, 2010 at 10:04am

Pete's script works great. You just need a serial output log (via Xbee telemetry) to parse with his python script.

• ▶ Reply

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page