Order Tray | Contact Us | Home | SIG Lists

[aprssig] Mic-E STATUS refresh and bad software?

Bob Bruninga bruninga at usna.edu
Mon Oct 9 18:10:29 UTC 2006

> Baud rate is NOT the primary limiting factor...
> ... if we could just get everyone to set a
> reasonable txdelay and stop using long comments 
> on every packet.  I see way too many short 
> Mic-E packets with a 30-character comment 
> tacked on to every position report!

Yes, that is why we had the STATUS rate settable to
say only include the STATUS in every 5th packet or
something.  But here is the problem  (I think)...

SOME software will ELIMINATE a STATUS if the next posit comes in without it.  It is not captured and RETAINED
like it is supposed to be.  I am sometimes hesitant to set my STATUS rate to seomehing link only 1 in five, because I am not sure if it will be captured.

Lets do some experimentation and identify the bad apples:
1) FINDU does not even capture STAUTS, so that is a biggie!
2) What do the other softwares do?

Here is the TEST:

1) SEND a Kenwood POSIT with STATUS.
2) Then send a few WITHOUT STATUS and no more.

Check your software and see if the STATUS remains associated and always visibile with the LAST position report received.

If it doesn't, then lets identiifes these problems and get them fixed.  Then we can campaign for everyone to cut down on their STATUS refresh rate.

de WB4APR, Bob
FINDU does not a  Not to mention D700's with half-second txdelays...

More information about the aprssig mailing list