[aprssig] 9600 APRS
Jason KG4WSV kg4wsv at gmail.comThu Apr 2 14:08:21 UTC 2009
- Previous message: [aprssig] 9600 APRS
- Next message: [aprssig] 9600 APRS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The 3 minute window just emphasizes the issue - reducing the time won't make it go away (unless you reduce it to zero). One of the problems regularly mentioned on the list is some mis-configured digipeater erroneously doing exactly what you are saying - holding packets for a while then sending them in a burst. This destroys the usefulness of a mobile station/object track, as old data gets interleaved with the new, and the station/object location bounces around between old locations and newer. Also, APRS is an Aloha network, and the random nature if the transmissions is part of the design. If you start semi-scheduling stuff, you'll need to take a look at the design of the whole network. I would guess that for starters, digipeaters would need fairly well synchronized clocks. The immediate transmission of a packet heard by a digi is a major part of the traffic _reduction_ algorithm in the APRS network. Your scheme could easily result in _more_ channel utilization _and_ lost data (see the part about sychronized digi clocks). -Jason kg4wsv
- Previous message: [aprssig] 9600 APRS
- Next message: [aprssig] 9600 APRS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
