568RE: [tracker2] Firmware build 53875
- May 30, 2006It'll do the first one... should the replacement that you show happen any time a WIDEn-N is used up?Scott
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Cap Pennell
Sent: Saturday, May 27, 2006 9:09 PM
Subject: RE: [tracker2] Firmware build 53875DoesALIAS WIDE, HOPLIMIT 1, DIGIID ON: APRS via WIDE1-1,WIDE2-1 become APRS via MYCALL, WIDE1*,WIDE2-1(with the "*" after WIDE1) ?Or become APRS via MYCALL*,WIDE2-1 (or something like that, to allow the second hop from that next digi down the road) ? Hope so.73, Cap KE6AFE-----Original Message-----
From: firstname.lastname@example.org [mailto:email@example.com]On Behalf Of scott@...
Sent: Saturday, May 27, 2006 20:24 PM
Subject: RE: [tracker2] Firmware build 53875Ok, I was going to ask exactly what you meant!Forgot to document the HOPLIMIT command. If HOPLIMIT = 0, it digipeats on the alias only. Otherwise it does ALIASN-n, where n is not greater than HOPLIMIT. Some examples:ALIAS TEMP, HOPLIMIT 0, DIGIID OFF: APRS via TEMP becomes APRS via TEMP*ALIAS TEMP, HOPLIMIT 0, DIGIID ON: APRS via TEMP becomes APRS via MYCALL*ALIAS WIDE, HOPLIMIT 2, DIGIID OFF: APRS via WIDE2-2 becomes APRS via WIDE2-1ALIAS WIDE, HOPLIMIT 2, DIGIID ON: APRS via WIDE2-2 becomes APRS via MYCALL*, WIDE2-1Scott
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Wes johnston
Sent: Saturday, May 27, 2006 7:34 PM
Subject: Re: [tracker2] Firmware build 53875Yikes... I said that wrong... I have seen no problems with the dupe checker.Wes----- Original Message -----From: Wes johnstonSent: Saturday, May 27, 2006 10:30 PMSubject: Re: [tracker2] Firmware build 53875I have seen no dupe checks.... and I'm running on 26 hours with no input lockups... ie still digipeating as expected. Also, noticed that it's decoding objects. Looking great!And to reiterate something another ham said... thanks for the great work you do.Wes----- Original Message -----From: scott@...Sent: Saturday, May 27, 2006 7:02 PMSubject: [tracker2] Firmware build 53875Digi config commands are now implemented:
ALIAS <n> <callsign>
Set digipeater alias for slot <n>. This will typically be
a generic alias like 'WIDE'. No SSID is allowed in this
DIGIID <n> on|off
Enable callsign substitution for digipeater alias <n>.
This should normally be enabled.
PREEMPT <n> on|off
Enable digipeater preemption for alias <n>. If preemption is
enabled, packets will be digipeated on this alias even if it
isn't the next address in the list.
USEALIAS <n> on|off
Enable digipeating for alias <n>
Remember that all of these except USEALIAS are global, meaning they aren't
specific to one configuration profile.
A normal setup should be something like this:
ALIAS 1 WIDE
HOPLIMIT 1 3
DIGIID 1 ON
PREEMPT 1 OFF
USEALIAS 1 ON
These commands will all work remotely, as long as you specify a slot number.
Typing 'ALIAS' at the command prompt will list all defined aliases, but it
won't work remotely. Might eventually make a compressed list format for
That leaves fixed position, SmartBeaconing, and profile switching. I'll try
to tackle the fixed position commands today (LATITUDE and LONGITUDE) but the
tricky part there is that they share space with the comment field. If I
stop doing it that way, I have to add some more code to the config program
to handle the differences.
I also fixed a couple of other bugs in the buffer handling. I'd still like
more feedback on dupe checking problems, if there is still a problem, but I
think this version should be pretty safe for mountaintop digi use.
- << Previous post in topic Next post in topic >>