[aprssig] IRLP APRS Status Script: Multiconnect Bug?
bruninga at usna.edu
Fri Jul 25 11:58:49 CDT 2008
Keith, thanks for taking this on...
>> of the first 6 IRLP Objects... only one is in
>> the correct recommended IRLP/APRS frequency format.
> I did some modifications to the script on node IRLP 1148.
> How does it look now?
> IRLP1148 147.570MHz S T100 R15Km IDLE
I think adding the hyphen between IRLP and 1148 shows up nicer
on the radios and also fills the full 9 byte field. [IRLP-1148]
The S is not needed, assuming standard band-plan offsets. Also,
the S then pushes the Tnnn to the right and out of place with
the standard format. The reason for sticking to the new
standard is so that all software (including the new D710 radios)
can parse this tone and in the case of the radios, auto-tune to
this frequency and tone. So the Tone has to be in the right
place. And be exactly Tnnn always. (leading zero and no tenths).
Further the Range format for range has to be Rxxm or Rxxk. This
is so that the combination of FREQ, TONE and RANGE all fit
nicely on the 10x10 displays of all the APRS radios.
Ill go try to find those missing links and photos. Thanks. Bob
> > The objective is the following format to show on all APRS
> > and GPS units and radios the location, frequency, tone and
> > 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?
> After your comments, I could post my notes over on the IRLP &
> embedded lists. Individuals could duplicate my changes (if I'm
> close) but even better would be if the script author would
> script and make it available. Unfortunately, some (many?) IRLP
> owners are not also APRS users. I suspect that those that
> script (not all have) simply install it and follow the
> instructions. Even I did that. I seem to recall that you were
> with Randy KC6HUR (possibly not the original author, but I
> did the most recent modifications) and Dave VE7LTD (IRLP)
> 2007. Perhaps those changes didn't make it into the script.
> For IRLP node owners, the script is available at
> I don't know if it would make a difference, but on your page
> www.aprs.org/localinfo.html there are two missing graphics in
> the "IRLP
> and EchoLink FREQUENCY OBJECTS" section about 3/4 of the way
> page... www.aprs.org/aprs/IRLPx.JPG and
> Also on www.aprs.org/avrs.html the middle of the top three
> missing... www.aprs.org/avrs/EL-123456x.JPG, same file as one
> ones mentioned above.
> > The format did evolve over the last 4 years or so, and so it
> > expected that we will have to clean this up after the
> > Even my docs may be confusing?
> Thanks for posting your findings. Yes, the "proper settings"
> things is a moving target, but this is fixable. I'll await
> your comments
> before posting on the IRLP lists.
> 73 es cul - Keith VE7GDH
> IRLP 1148
> "I may be lost, but I know exactly where I am!"
> aprssig mailing list
> aprssig at lists.tapr.org
More information about the aprssig