Bug #68840 for Ham-APRS-FAP: PHG in Mic-E not parsed

Wed Jun 15 22:11:38 2011 ZL2IA [...] OnNZ.net - Ticket created

Subject:	PHG in Mic-E not parsed
Date:	Thu, 16 Jun 2011 14:11:18 +1200
To:	bug-Ham-APRS-FAP [...] rt.cpan.org
From:	Jim Tittsler <ZL2IA [...] OnNZ.net>

The parser does not detect the PHG string in Mic-E encoded packets. ZL2AS-1>SXU1P1,ZL2AS-2,WIDE1,ZL2FX-3*,qAR,ZL1AFZ:'i.Kl <0x1c>#/">q}PHG5730 Te Ahioteatua Digi The parser returns "PHG5730 Te Ahioteatua Digi" as the comment without checking for the PHG indicator. (And since it can be only 7 characters long... and the altitude is not required, the packet length check >=8 seems too strict.) 73, Jim -- Jim Tittsler ZL2IA/AI8A/7J1AJH Te Anau GPG: 0x01159DB6 http://OnNZ.net/ham/ QRP/Satellites/APRS AMSAT-NA/AMSAT-ZL/NZART

Thu Aug 18 03:58:13 2011 HESSU [...] cpan.org - Taken

Thu Aug 18 04:04:38 2011 HESSU [...] cpan.org - Correspondence added 5 min

On Wed Jun 15 22:11:38 2011, ZL2IA@OnNZ.net wrote: Show quoted text

> The parser does not detect the PHG string in Mic-E encoded packets. > > ZL2AS-1>SXU1P1,ZL2AS-2,WIDE1,ZL2FX-3*,qAR,ZL1AFZ:'i.Kl > <0x1c>#/">q}PHG5730 Te Ahioteatua Digi > > The parser returns "PHG5730 Te Ahioteatua Digi" as the comment without > checking for the PHG indicator. (And since it can be only 7 > characters long... and the altitude is not required, the packet length > check >=8 seems too strict.)

Hi, I'm not sure if PHG in mic-e should be parsed at all. I checked the APRS101.PDF specification. It says the Mic-E Status Text Field should be checked for altitude, maidenhead locator (I have no idea what it should be used for if the mic-e data contains a position already), and then there are the device type codes. PHG is in the "APRS DATA EXTENSIONS" which are parsed from normal position packets. Is PHG with Mic-E in active use, or supported by some other software? - Hessu

Thu Aug 18 04:04:39 2011 The RT System itself - Status changed from 'new' to 'open'