[aprssig] "Out-of-order" data on APRS-IS
J T w0jrt at yahoo.comTue Aug 9 18:11:29 UTC 2005
- Previous message: [aprssig] "Out-of-order" data on APRS-IS
- Next message: [aprssig] "Out-of-order" data on APRS-IS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Pete, Keep in mind Mark said this problem also happens when no digipeaters are involved -- i.e. cases where multiple I-gates hear the same packet directly. I, too, have seen long-delayed packets. Here's one example: 20050720210800,W0JRT-14>APRS,WIDE1-1,WIDE2-1*,qAR,KA2FNK:!3856.46N/09450.50Wk090/055N 20050720211101,W0JRT-14>APRS,WB0HAC,WIDE1*,WIDE2-1,qAR,KA2FNK:!3856.50N/09446.67Wk093/059N 20050720211134,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3856.78N/09446.25Wk340/059N 20050720211301,W0JRT-14>APRS,WB0HAC,WIDE1*,WIDE2-1,qAR,KA3NAM-11:!3856.39N/09451.04Wk044/054N 20050720211301,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3858.15N/09446.55Wk015/047N 20050720211134,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3856.78N/09446.25Wk340/059N 20050720211301,W0JRT-14>APRS,WB0HAC,WIDE1*,WIDE2-1,qAR,KA3NAM-11:!3856.39N/09451.04Wk044/054N 20050720211301,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3858.15N/09446.55Wk015/047N 20050720211334,W0JRT-14>APRS,WIDE1-1*,WIDE2-1,qAo,KC5YTI-15:!3858.26N/09446.37Wk089/018N 20050720211350,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAR,KA3NAM-11:!3856.46N/09450.50Wk090/055N 20050720211635,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3858.29N/09445.53Wk126/000N 20050720211726,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3858.27N/09445.54Wk267/015N 20050720211738,W0JRT-14>APRS,WB0HAC,WIDE1*,WIDE2-1,qAR,KA3NAM-11:!3856.50N/09446.67Wk093/059N 20050720211758,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAo,W0JRT:!3858.23N/09445.66Wk178/031N 20050720211852,W0JRT-14>APRS,WIDE1-1,WIDE2-1,qAR,KA3NAM-11:!3856.78N/09446.25Wk340/059N Look at the first packet and the one at time 1350. KA3NAM-11 heard the packet DIRECTLY and still reported it 5 minutes and 50 seconds later than KA2FNK who heard the packet via TWO digipeater hops. Another example: The packets at times 1134 and 1852 are identical, and both were heard directly by two I-Gates (W0JRT and KA3NAM-11). No digipeaters were involved. However, KA3NAM-11 reported the packet 7 minutes and 18 seconds later than W0JRT. For several days I noticed this behaviour, and in every case the delayed packets were always I-gated through the same station (KA3NAM-11). I sent Joe (KA3NAM) e-mail about this and he said he'd look into it. The problem went away, but I never heard back from Joe so I'm not sure what (if anything) he changed. -Jerome W0JRT ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
- Previous message: [aprssig] "Out-of-order" data on APRS-IS
- Next message: [aprssig] "Out-of-order" data on APRS-IS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
