[aprssig] IRLP Node Object
Paul Yeager paul at mtnlist.comMon Mar 26 03:37:02 UTC 2012
- Previous message: [aprssig] Transatlantic HF monitoring...
- Next message: [aprssig] IRLP Node Object
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I recently reconfigured my EGLNST digi to conform to WB4APR's latest recommendation for Kantronics 8.3 or later firmware at http://www.aprs.org/kpc3/kpc3+WIDEn.txt. Things seem to work fine, except for the IRLP node object that I programmed, which apparently aprs.fi has problem parsing. WB4APR's document suggests the following format: ;IRLP-4040*111111zDDMM.hhNIDDDMM.hhW0FFF.FFFMHz Tnnn CALLSIGN ... and what I entered is: ;IRLP-4397*111111z3522. NI08313. W0444.875MHz T131 K4RCC I used spaces instead of hundredths of degrees for position ambiguity. My problem is that aprs.fi appears not to like the format. Viewing the raw packets reveals: 2012-03-25 22:05:09 UTC: EGLNST>APN383,qAR,N4NE-1:;IRLP-4397*111111z3522. NI08313. W0444.875MHz T131 K4RCC [Delayed or out-of-order packet (timestamp)] Is my formatting of the object message faulty, or does aprs.fi not parse it correctly? Thanks in advance. 73 de W4SKI Paul Yeager -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.tapr.org/pipermail/aprssig/attachments/20120325/977fa475/attachment.htm>
- Previous message: [aprssig] Transatlantic HF monitoring...
- Next message: [aprssig] IRLP Node Object
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
