Topics

1

Technical Support / $PFLAA message in track file

« on: September 30, 2017, 12:33:25 am »

Is there a published definition of the $PFLAA message as recorded in the track files? In most instances, I believe the first 4 elements after $PFLAA are alert state, Metres north of me, meters east of me, and metres above me, but I see several aircraft which have a suspiciously round number (e.g. 1500, 3000, 4500) in the field that I thought was "Metres N of me) and the "Metres E of me" field is then in each case blank. These cases appear to be flagged to generate alerts by PAW. From the Planefinder.net web site, these appear to be form aircraft that had indeed been flying in my immediate vicinity but which were actually probably landed at the times these messages appear in the track file. I am wondering if perhaps ADS-B outputs a different message string after an aircraft has landed - if so, how is that handled in the track file?

2

Technical Support / Bits needed to connect to FLARM Mouse?

« on: December 17, 2016, 10:05:58 pm »

I think I read somewhere a while back that a set of approved hardware would be specified (or sold via PilotAwareHardware.com) to allow the FLARM mouse to be connected?Is there any news on this now there is a formal release of a FLARM-enabled version? Clear hardware recommendations and installation/set-up instructions would be much appreciated!

3

Technical Support / First ground tests - OK except all voce messages say traffic is at my level !!!!

« on: July 17, 2016, 11:41:40 pm »

Just started trying my PAW - fired up OK first time, seeing ADS-B and Modes-S traffic (on "loosest" filter settings), both on screen and on the traffic list. All are at credible locations and altitudes (FL200 - FL400) on my map.. BUT with voice output from PAW plugged in, EVERY ADS-B contact is declared as "level". The status page shows 3D fix from 6 satellites and  QNE ~44ft and GPSS as ~400ft (not sure why they differ so much - baro calibration or GPS separation???) but either way, clearly not "level" with the ADS-B traffic which is correctly shown at FL200 or whatever both on map and on tabulation page. Also, Mode S audio does not give any indication of relative altitude - I presume it  gets it altitude form the baro sensor and GPS and does not need to get the Mode S altitude from my own aircraft (clearly it won't get that while I test at home!) to calculate a Mode S alt difference?

(PS - in case it's relevant, PAW was delivered with 20160530 s/w but successfully updated automatically to 20160708 version by ethernet cable link.)