Order Tray | Contact Us | Home | SIG Lists

[aprssig] IRLP APRS Status Script: Multiconnect Bug?

Steve Grantham aa5sg-2 at sera.org
Mon Jul 28 01:54:23 UTC 2008


Let's not forget, then, that in order for this to be useful and relevant 
information for the local mobile operator, some local station has to 
prudently and appropriately gate these packets from the Internet to RF in a 
fashion that would enhance their usefulness to the local mobile operator.

Steve, AA5SG


----- Original Message ----- 
From: "Robert Bruninga" <bruninga at usna.edu>
To: "'Steve Grantham'" <aa5sg at comcast.net>; "'TAPR APRS Mailing List'" 
<aprssig at lists.tapr.org>
Sent: Sunday, July 27, 2008 5:26 PM
Subject: Re: [aprssig] IRLP APRS Status Script: Multiconnect Bug?



In my mind, the value of these objects is for the mobile operator.  Hence, I 
see no need for the verbose version. Thanks!

APRS is for the local display of relevant information of immediate use in 
the local area to the mobile operator.  In most cases, I think it most 
important to configure information to display best there...

Bob, WB4APR


----- Original Message ----- 
From: "Steve Grantham" <aa5sg-2 at sera.org>
To: "TAPR APRS Mailing List" <aprssig at lists.tapr.org>
Sent: Sunday, July 27, 2008 5:02 PM
Subject: Re: [aprssig] IRLP APRS Status Script: Multiconnect Bug?


I looked at this last night and hastily edited the "aprs_status" and 
"aprs_status.conf" files on one of my low profile IRLP nodes.  Once I got it 
working as desired, I copied the files to my IRLP node 5980, which now shows 
text like "145.230MHz T136 R40m IDLE" or "145.230MHz T136 R40m REF9200" in 
the comments area.

<snip...>

The bottom line is...  If there is no real need for the "verbose" mode, then 
a cleaner and slimmer version of the script could be put together and 
distributed.  Until a judgment is made on this, either way, I'd prefer to 
see the principal script authors make the modifications for distribution.

Steve, AA5SG


----- Original Message ----- 
From: "Robert Bruninga" <bruninga at usna.edu>
To: "'TAPR APRS Mailing List'" <aprssig at lists.tapr.org>
Cc: <andy at technerd.com>
Sent: Friday, July 25, 2008 7:56 AM
Subject: Re: [aprssig] IRLP APRS Status Script: Multiconnect Bug?


I just checked FINDU and of the first 6 IRLP Objects out of 50, only one is 
in the correct recommended IRLP/APRS frequency standard format.  We need to 
figure out why this script is not yielding the consistency we need?  In this 
list, I cut out the date/lat/long so they fit better:

;IRLP-4740*442.600MHz T141 R20m OFFLINE  [Yes, correct!
;IRLP1148 *147570S100IDLE R15Km          [No . & no -
;IRLP-8045*146940s123IDLE                [No .
;IRLP-8549*431.640MHz simplex PL123Hz >REF9504 [C overlay?
;IRLP-4942*446325-146IDLE                [no . Tone fmt?
;IRLP-4090*442850+71IDLE                 [no . Tone fmt?
;IRLP-8045*146940s123IDLE                [has Freq in CALLSIGN
field

IRLP8045>APVR30,TCPIP*,qAC,T2MIDWEST:

The objective is the following format to show on all APRS maps and GPS units 
and radios the location, frequency, tone and range of nearby IRLP nodes:

;IRLP-NNNN*FFF.FFFMHz Tnnn RXXm STATUS

Where IRLP-NNNN is the object name Where Tnnn is the tone in Hz (no tenths) 
with leading zero
Where RXXm is subjective useable range in miles (or km)
Where STATUS is the present node status.

See www.aprs.org/localinfo.html

Where can we correct the IRLP information and docs to get everyone onto the 
same page? The format did evolve over the last 4 years or so, and so it is 
expected that we will have to clean this up after the fact... Even my docs 
may be confusing?

Bob, WB4APR







More information about the aprssig mailing list