Track File : Post Processor : New Version (0.2)

[Ian Melville]

Hi Lee, I think those sentences are ignored at the moment. it is $PFLAA ones without a hex!callsign that cause the issue.

I used Excel to modify just those fields by inserting abcde!abcde, then opened it in the post processor and all was good. Obviously all mode A/C aircraft will have the same ID, and location will always be level, above or below us.

Parsing of the $PAWRT will need to be read and used to modify those $PFLAA messages so that the Post Processor shows them for what they are. I guess the only options it currently has is to show max an min threat level, which is pretty meaningless.

Not really sure how PFLAA and PAWRT relate to each other. Initially I thought the hex bit paired them, and there are matches. But not sure what to do with those with no match. Is there going to be an explanation for us on the PAWRT sentence?

[Admin]

Aha,

The message without an ICAO, or callsign was specifically for SkyDemon, I need to check my information, but I recall SkyDemon got upset when given the "ICAO!REG" for a bearingless target.

Regarding the PAWRT message, this is work in progress but the intention is to provide additional hints to the post processor about the type of messages received for the given ICAO.

Format

$PAWRT,<ICAO>,<Mode-A>,<Mode-C>,<Mode-S>,<ADS-B>,<P3I>,<Flarm-IN>

the ICAO is a 6 digit hex code, each of the other fields are booleans indicating
0 - no message received
1 - message received

so for example

Code: [Select]

$PAWRT,AABBCC,0,0,0,0,1,0     // P3I received
$PAWRT,012345,0,1,1,1,1,0     // Mode-C, Mode-S, ADS-B & P3I received
$PAWRT,404040,0,0,0,0,0,1     // Flarm-IN received
thx
Lee

[Ian Melville]

Hi Lee, I was thinking that the post processor filled in the blanks when it read the track file. After all this is a topic about the post processor 

Understand the sentence now, but where will the Mode A/C ICAO hex code come from?

[Admin]

Understand the sentence now, but where will the Mode A/C ICAO hex code come from?

Quite!
These are the issues with Mode-C

At the moment (internal build) the ICAO is auto-generated based upon unused Codes, apparently no codes begin
0xFxxxxx

So I am allocating those, and simply using a reg of Mode-C.
I think the differing threat levels will be applied to ICAO something like
0xF00001 // level 1
0xF00002 // level 2
0xF00003 // level 3

eg Mode-C only

Code: [Select]

$PAWRT,F00001,0,1,0,0,0,0     // Mode-C
TBH, not sure how useful this is to the post-processor, but it makes the data format more complete/rigorous

Thx
Lee

[Ian Melville]

Thanks Lee and all the best in trying to get mode A/C captured.

As far as the post processor is concerned, I don't think there is a great deal of value in trying to analyse the directionless messages. It would be nice to be able to verify the threat levels against actual range, but that is near impossible for Mode S and impossible for mode A/C. Convincing everyone to fit a PAW would be easiest 

[the_top_pilot]

There are people who will not invest in PAW. These are the people I want to avoid so Mode C is a winner.
I have 2 new PAW's with Pi 2, I am still using an engineering version with mode C/S detection and am happy with the results.

Steve

[Ian Melville]

Steve,
I think you misunderstood my comments. I am all for getting alerts regarding Mode A/C/S Bearing less target during flight. It is the display in the post processor that is of debatable value.

[brinzlee]

Is there any news when the updated Post Processor will be ready for a run with the new TRK files.....?
Kind regards
Brinsley

[DaveStyles]

Being quickly checked by the engineering team. We'll release it tomorrow hopefully.
regards
Dave.

[DaveStyles]

http://www.pilotawarehardware.com/dl/PawPostV2.jar

download from here....

enjoy...

[Ian Melville]

Thanks Dave. Quick test on recent file worked fine.

[brinzlee]

Looks good to me too
Thank you
Brinsley

[bnmont]

Just used the processor to look at a log from recent flight, am I correct in believing I had a P3i signal from 106Km !

[Ian Melville]

I suspect a glitch or code error there. Just one ping at the distance, nothing in between. Not sure that 4F.... is a valid hex ID, perhaps one of the PAW generated ones out of the box?

Without the track log I cannot tell which.

[Richard W]

I am having trouble understanding the 'track' display.  These are the first and last records for aircraft 405091 :-

$PFLAA,0,-5754,17710,-488,1,405091!405091,288,,40,,8*5F
...
$PFLAA,0,-18121,-7692,147,1,405091!405091,295,,38,,8*58

I think this says that the aircraft was to the south, tracking from east to west, and becoming more southerly, all relative to my position.  This tallies with the textual description "mainly south, level and east".  However, the graphic display is all to the west, and mainly north.  It looks as though the N-S and E-W axes have been swapped?