| |
ZL3AI > APRDIG 28.08.06 23:07l 115 Lines 3509 Bytes #999 (0) @ WW
BID : 8675-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 26 #26, 3/3
Path: DB0FHN<DB0MRW<DK0WUE<DB0RES<F6GGY<F4BWT<F3KT<IW2OAZ<ZL2BAU
Sent: 060828/2104Z @:ZL2BAU.#87.NZL.OC #:906 [Waimate] $:8675-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Message: 19
Date: Sat, 26 Aug 2006 09:31:48 -0400
From: tom burkhart <tburkhar_at_gmail.com>
Subject: Re: [aprssig] ISS
Currently the aprs system is not working on the iss, because the are
trying to set up sstv using the same frequencies.
The easiest way to see if aprs is active on the ISS is to look at the
fundu site http://www.findu.com/cgi-bin/ariss/index.cgi
There is an article on www.issfanclub.com that mentions the status of
the sstv upgrade. That site also has information on the status of packet
and voice activities.
The sstv upgrade is also mentioned at
http://www.arrl.org/news/stories/2006/08/22/2/?nc=1
Tom
KI4MDU
------------------------------
Message: 20
Date: Sat, 26 Aug 2006 09:53:18 -0400
From: "Ron Wenig" <ny3j_at_comcast.net>
Subject: RE: [aprssig] ISS
Thanks Tom,
Looks like the last APRS packet was received 8/13. I'll have to figure out
how to do SSTV when they get it working. That looks like it would be more
fun.
73, Ron ny3j
------------------------------
Message: 21
Date: Sat, 26 Aug 2006 09:12:44 -0500
From: "john b. leonard, jr." <w9jbl_at_comcast.net>
Subject: RE: [aprssig] Delayed packets (yet again)
Are we over-thinking this situation?
It occurs to me that it may be a combination of things, all contributing to
a built-in delay, which may be characteristic of the IS system.
Based on recent messages, both here and on the UI-View list, there seem to
be two concerns:
1. A delay between the times a beacon is sent out from an APRS station via
RF to when it's seen on APRS IS
2. Tracked objects "jumping" back some distance
The delay may be caused by the time lag between a packet going out at 1200
baud, going from the TNC to the computer at 9600 baud, being picked up by
an RF-Internet gateway, going to the server at much higher b/s rates,
crammed into the server's buffer, then sent out on the Internet to each
station connected, some of which are not range-filtered, and finally sent
from the computer at whatever rate the client NIC/computer sends it to the
screen.
Also, here is a recent log of activity of my station alone, from the T2
Midwest server. Range filtered at 300km:
Packets for W9JBL
Time in UTC
8/26/2006 13:20
W9JBL>APU25N,WA9CJN-15*,IL2-1,qAo,WB9WLS:=4155.50N/08845.11W- {UIV32N}
8/26/2006 13:24
W9JBL>APU25N,WA9CJN-15*,IL2-1,qAR,W9TMW:=4155.50N/08845.11W- {UIV32N}
8/26/2006 13:34
W9JBL>APU25N,TCPIP*,qAC,T2MIDWEST:=4155.50N/08845.11W- {UIV32N}
8/26/2006 13:36
W9JBL>APAGW,WA9CJN-15,WIDE2*,qAS,N9ZIP:Using Elcom uTNT Plus
8/26/2006 13:39
W9JBL>APU25N,TCPIP*,qAC,T2MIDWEST:=4155.50N/08845.11W- {UIV32N}
8/26/2006 13:43
W9JBL>APU25N,TCPIP*,qAC,T2MIDWEST:=4155.50N/08845.11W- {UIV32N}
8/26/2006 13:44
W9JBL>APU25N,TCPIP*,qAC,T2MIDWEST:=4155.50N/08845.11W- {UIV32N}
As the log shows, some packets are picked up directly by the server, others
are received after one AND two hops. Unless the server is reliably
filtering out ALL dupes, this may account for the jumping I saw in W9JBL-9
last weekend, where a late beaconed tracker packet hit the client computer,
containing GPS data made the icon regress to where the prior beacon located
it.
Just a thot/question.
bl
------------------------------------
"If stupidity got us into this mess, then why can't it get us out?"
- Will Rogers
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 26, Issue 26
Read previous mail | Read next mail
| |
