[aprssig] Digipeater Question - Unused WIDE2
Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.toTue Apr 6 02:50:09 UTC 2010
- Previous message: [aprssig] aprssig Digest, Vol 70, Issue 2
- Next message: [aprssig] Digipeater Question - Unused WIDE2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm working on DigiPeater code for my APRSISCE/32 client and have run into a strangely pathed packet. KI4OIU>APU25N,AA4QI-1*,WIDE2:=3012.58N/08135.46W_WWW.JAXSKYWARN.WEBS.COM If this packet is received over RF, and my client is configured as a WIDE2 digi, should it digipeat the packet or not? It seems that the AA4QI-1 digi is doing this consistently. If you look at KI4OIU's raw packets (http://aprs.fi/?c=raw&call=KI4OIU&limit=50&view=normal) you'll see many packets with a non-used WIDE2 in them, and all of them (that I noticed, at least) immediately follow AA4QI-1*. AA4QI-1 itself uses a generic >APRS ToCall, so there's no hint as to what it is running. But regardless of why this is happening, should such a packet be digipeated by a WIDEn-N digi configured to do WIDE2? Or should the unused WIDE2 be treated as if it were used because the (implied) -SSID is 0? Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
- Previous message: [aprssig] aprssig Digest, Vol 70, Issue 2
- Next message: [aprssig] Digipeater Question - Unused WIDE2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
