[aprssig] New n-N and 28 versus 30

[AB9FX]

I'm not sure how the timer works in digis. Is this timer just for 
callsign-SSID or is this for callsign-SSID and given frame? If for all the 
frame, then time could much longer. Probable short time would be needed only 
for messages retries. Beacon with the same position is not needed to be 
repeated even for few minutes.

I have another question about KPC-3+ v9.0
I tried to set digi and timer doesn't work as it did in v8.3 Any additional 
settings? There are new commands like UIDUPE, but timer doesn't work neither 
for UIFLOOD UITRACE nor UIDUPE.
73!
Andy AB9FX SP3LYR


----- Original Message ----- 
From: "Robert Bruninga" <bruninga at usna.edu>
To: <aprssig at lists.tapr.org>
Sent: 20 December, 2004 13:15
Subject: [aprssig] New n-N and 28 versus 30


>I also wonder if it is also time to change  the common
> 28 second filter parameter in most digis' UIFLOOD, and UITRACE
> parameters from 28 to 32?
>
> It was set to 28 so that people running 30 second trackers
> would not get filtered out.
>
> These days, No one should be running 30 seconds *routinely*
> so why not change the filter to 32 so they CANT (routinely).
> Of course the SYSOP can change it to 19 seconds if he
> wants for any special event or for doing mobile coverage
> studies at a 20 second rate if he wants,...
>
> But in general, I dont see why we leave this floodgate
> open for such rare occassions.  Better to keep it closed
> most of the time and only open it up when needed..
>
> I'm changing all my docs to show this.  or at least 30 secs.
>
> Bob
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig