[aprssig] KPC3+ induced errors
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toWed Mar 16 20:27:17 UTC 2011
- Previous message: [aprssig] KPC3+ induced errors => IS dupe checking
- Next message: [aprssig] KPC3+ induced errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Caveat Emptor: I'm not the expert, but... On 3/16/2011 3:28 PM, Larry Cerney wrote: > Just for my own education, just where in the APRS system is dup checking > done? Dupe checking is done in the APRS-IS server, typically javAPRSSrvr. > What is monitored in the packet to identify a dup? The fromCall, toCall, and payload. The path is NOT included in the dupecheck as it varies as digipeaters and IGates handle the packet. fromCall>toCall,path,path,qxx,igate:payload > How long does the "dup window" remain open? The default dupe check window is 30 seconds. Any packet delivered to APRS-IS later than 30 seconds after the first delivery of the same packet will be passed on into the network. Delayed dupe introduction is easier to trace with packets that contain timestamps. The raw NMEA GPS strings include the timestamp so they will be easy to see the duplicate deliver vs time time of entry. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 > Larry K0ANI > > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig >
- Previous message: [aprssig] KPC3+ induced errors => IS dupe checking
- Next message: [aprssig] KPC3+ induced errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
