Author Topic: Track Log explanation  (Read 2024 times)

PeterG

Track Log explanation
« on: June 26, 2020, 10:14:38 am »
Dear all

I was flying yesterday in the SW. As we don't have much of a grid of ground stations here, I never had the chance to experience the bearingless target upgrade.

But looking at the track log, it looks like PAW dropped out, probably due to high temperature eg a lot of lines like this.

Quote
$PALOG,20200625,115231,WIFI,UDP,192.168.1.27:4000,DISCONNECTED
$PALOG,20200625,115231,WIFI,UDP,192.168.1.27:2000,ATTEMPT
$PALOG,20200625,115232,TEMPERATURE,47.20,C

And then on the log, a host of these

Quote
$PALOG,20200625,115617,DEBUG,MODEC-FILTER-PASS,43C5E4,181,SIG,200,MAX,170,FILTER,3756,VDIFF

I didn't manage to find a single ground station between Cornwall and EGTU, but the A400M out of Newquay was there!

Is there a glossary of how to interpret the trk log for dummies?

Regards

Peter

Vic

Re: Track Log explanation
« Reply #1 on: June 29, 2020, 02:59:52 pm »
Peter  have you tried analysing your track log on the Aircrew site?

http://forum.pilotaware.com/index.php/topic,1424.0.html

PeterG

Re: Track Log explanation
« Reply #2 on: July 02, 2020, 12:33:15 pm »
Thanks for that. I've replayed the track and it was very interesting as to what was about that day.

But no, the replay didn't answer the questions, really.

Admin

Re: Track Log explanation
« Reply #3 on: July 02, 2020, 02:30:00 pm »
Hi Peter

The particular message (and many others) are intended for internal usage really
what this message is telling you, is that data was being sent to the device at that address, but no applications were listening

This is usually the case if you connect a phone and a tablet, but you are only running SkyDemon for example on the tablet

Thx
Lee

PeterG

Re: Track Log explanation
« Reply #4 on: July 03, 2020, 12:29:01 pm »
Thanks Lee - so probably the issue was a drop out with the tablet, not the PAW

Admin

Re: Track Log explanation
« Reply #5 on: July 03, 2020, 02:18:07 pm »
Hi Peter

This does not indicate a dropout, what it says is this

I have tried sending data to the connected device, but there is no app listening to this data
I am going to try sending data in a different format

Unless you tell Pilotaware explicitly what to send, it attempts to send GDL90 and FLARM/PilotAware data

thx
Lee

exfirepro

Re: Track Log explanation
« Reply #6 on: July 03, 2020, 09:48:23 pm »
Peter,

It is best to decide which data format you want to use with your Electronic Flight Bag of choice (i.e. SkyDemon, etc.) and set this in your PilotAware Configure Connectivity Settings, rather than leave this setting on ‘Auto’....

PilotAware (UDP) - if you want to see Bearingless Target Warnings on SkyDemon.

GDL90 - if you don’t care about Bearingless Target Warnings (SkyDemon won’t show them on GDL90) and want (reportedly) more reliable PAW to device connectivity.

Don’t forget to select the same option in your EFB (e.g. in SkyDemon / Settings / Navigation), then select this option when you ‘Go Flying’.

Regards

Peter

PeterG

Re: Track Log explanation
« Reply #7 on: July 03, 2020, 11:50:41 pm »
Thanks for that.

I'll give it a try asap