Author Topic: Logs  (Read 6778 times)

Wesjon

Logs
« on: October 10, 2017, 02:34:04 pm »
Hi all

I used my system for the first time this weekend and was very impressed. Is there a way where I can view logs of what aircraft was close to me, height separation, etc?

Thanks
Wes

Admin

Re: Logs
« Reply #1 on: October 10, 2017, 04:19:31 pm »
Hi

When connected to the PilotAware Wi Fi : Go to

http://192.168.1.1
Select TRACKS

either download to the webclient you are using, OR, sync to a FAT32 formatted memory stick

You can also REPLAY, which will resend the data to your navigation device

Thx
Lee

Wesjon

Re: Logs
« Reply #2 on: October 11, 2017, 01:59:41 pm »
Thanks Lee. How do I open and read a .trk file?
« Last Edit: October 11, 2017, 02:13:57 pm by Wesjon »

Admin

Re: Logs
« Reply #3 on: October 11, 2017, 04:35:00 pm »
Thanks Lee. How do I open and read a .trk file?

The file is ascii, so notepad, wordpad etc

Thx
Lee

Wesjon

Re: Logs
« Reply #4 on: October 11, 2017, 04:36:05 pm »
Cheers Lee. Trying to figure out how to read it now..... ;D

Wesjon

Re: Logs
« Reply #5 on: October 12, 2017, 08:58:16 am »
Can anybody possibly elaborate what the data entry below means?

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47

Thanks!

Admin

Re: Logs
« Reply #6 on: October 12, 2017, 10:32:09 am »
Can anybody possibly elaborate what the data entry below means?

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47

Thanks!

try googling for 'flarm dataport specification'
This is basically telling you

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47
threat level 2

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47
relative X, Y, Z position in Metres, so basically 2km away 790ft above

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47
PilotAware/ICAO Code

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47
Tail Reg

$PFLAA,2,-1650,1384,241,1,40345F!#GTECC#,281,,35,0.0,0*47
Part of your PilotAware group (default PAWGRP)

Cant remember the others off hand, but probably track and climb rate

Thx
Lee


Wesjon

Re: Logs
« Reply #7 on: October 12, 2017, 10:53:15 am »
This is such amazing data. Spot on as just compared with Flightradar24.

Paul_Sengupta

Re: Logs
« Reply #8 on: October 12, 2017, 11:16:21 am »
That's Nic in the Champ, her with the PilotAware worn as a backpack by her toy bear!  :D

Wesjon

Re: Logs
« Reply #9 on: October 12, 2017, 11:22:42 am »
So damn cool this PAW!!

Paul_Sengupta

Re: Logs
« Reply #10 on: October 13, 2017, 03:30:00 pm »

Wesjon

Re: Logs
« Reply #11 on: October 13, 2017, 04:05:24 pm »
Was the bear piloting the plane?? ;D Nice setup!

PeterG

Re: Logs
« Reply #12 on: October 16, 2017, 10:02:20 am »
I've been looking at some recent logs as (as displayed on SkyDemon) some of the replays are odd.

eg one flight recently I led a group of aircraft taking off but the SD display showed an aircraft that had taken off behind me around 10km ahead, then 5k behind.  At one point we were in formation for a period but the relevant log entry showed 2 sets of data

$PFLAA,1,4500,,6,1,406xxxx!G-xxxx,,,,0.0,8*78  (similar reading for a number of entries)

$PFLAA,3,1500,,5,1,406xxxx!G-xxxx,,,,0.0,8*7C (the next entry and steady for a period)

In fact we were probably 4-500m apart at times.

I have a suspicion that some of this may be a rendering issue on SD and others placement of the anntenae, but would welcome your views

The log entry for the period we were flying together switches between 1500, 3000 and 4500m, so is this showing which zone the other aircraft is in or the actual distance between. After the other aircraft went ahead I have no other readings of it, even though it was never more than about 6k ahead.






Admin

Re: Logs
« Reply #13 on: October 16, 2017, 05:17:36 pm »
Hi Peter

These are ModeS entries, notice that there is only an X and Z component, but no Y
This is how FLARM indicates a bearingless target.
The numbers are rounded for threat levels of
4500, 3000, 1500 - for increasing threat, and simply used to size the rings in the display
These numbers are not accurate for range
Bearingless targets are inherently inaccurate for range calculation, but the relative height is accurate to within the accuracy of the transponder - IIRC 25ft for ModeS and 100ft for ModeC

Thx
Lee
« Last Edit: October 16, 2017, 05:19:30 pm by Admin »

PeterG

Re: Logs
« Reply #14 on: October 17, 2017, 11:06:33 am »
Thanks for that - makes sense now.

I had hoped to speak to the other pilot about how he's equipped but haven't been able to.