| |
ZL3AI > APRDIG 22.12.06 00:18l 276 Lines 10803 Bytes #999 (0) @ WW
BID : 9372-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 30 #19, 1/4
Path: DB0FHN<DB0MRW<DK0WUE<7M3TJZ<ZL2BAU
Sent: 061221/2302Z @:ZL2BAU.#79.NZL.OC #:22198 [Waimate] $:9372-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. RE: Get ready to receive RAFT and ANDE telemetry! (Robert Bruninga)
2. Re: Get ready to receive RAFT and ANDE telemetry! (Jason Winningham)
3. RAFT and ANDE IGating (Robert Bruninga)
4. Re: Get ready to receive RAFT and ANDE telemetry! (A.J. Farmer (AJ3U))
5. RE: aprssig Digest, Vol 30, Issue 18 - UI-View SatGate Parms (Ken Whalen)
6. APRS USER TELEMETRY Plan for ANDE and RAFT (Robert Bruninga)
7. Re: APRS USER TELEMETRY Plan for ANDE and RAFT (Keith - VE7GDH)
8. Re: APRS USER TELEMETRY Plan for ANDE and RAFT (Steve Dimse)
9. RE: APRS USER TELEMETRY Plan for ANDE and RAFT (Robert Bruninga)
10. Re: APRS USER TELEMETRY Plan for ANDE and RAFT (Steve Dimse)
11. PSKMail Live CD (Brian B. Riley)
12. Re: PSKMail Live CD (Stephen Brown Jr)
13. RE: PSKMail Live CD (Ray McKnight)
14. Re: PSKMail Live CD (Jeff Davis, KE9V)
15. Re: PSKMail Live CD (Stephen Brown Jr)
16. Re: PSKMail Live CD (Amateur Radio WB8NUT)
17. Re: PSKMail Live CD (Joel Maslak)
18. Re: PSKMail Live CD (Lance Cotton)
19. Re: PSKMail Live CD (Steve Dimse)
20. Re: PSKMail Live CD (Stephen Brown Jr)
21. RE: PSKMail Live CD (Scott Miller)
22. Re: PSKMail Live CD (Steve Dimse)
23. Re: PSKMail Live CD (Gregg Wonderly)
24. Re: PSKMail Live CD (Jeff Davis, KE9V)
25. Re: PSKMail Live CD (Jason Winningham)
26. RE: PSKMail Live CD (Scott Miller)
27. Re: PSKMail Live CD (Rick Green)
28. RE: PSKMail Live CD (Herb Gerhardt)
29. Re: PSKMail Live CD (Brian B. Riley)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Dec 2006 14:07:50 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Get ready to receive RAFT and ANDE telemetry!
>We are in need of stations around the world to receive
>this telemetry and gate it to the APRS-IS...
>
>An easier option: If you have a TM-D700 radio,... set
>[it] to work as a SatGate to help capture these packets.
>[by digipeating over to the national network...]
Although that is a very clever approach, unfortunately, there are 3 reasons
why we do not recommend that except in extremely remote continents where
there is no other way to get the packets.
1) The danger of someone missconfiguring their mobile and then digipeating
BACK on 145.825, though small, is bad enough to reduce the satellite
effectiveness by 50% for each mobile that forgets to properly set their TX
frequency. These stations then would be jamming the uplink 50% of the time
after each packet heard. This risk, though small, is not the kind of risk
we like to take in space stuff where such a problem can block an entire
continent.
2) We do not want packets from 145.825 digipeated over to national APRS
networks, because once there, the packets cannot be determined to be from
the Satellites and do not show up on the PCSAT web pages on FINDU. This
causes frustration and confusion and takes time of key players to
constantly troubleshoot and comment on.
3) Since anyone that can receive APRS on 144.39 or whatever national
frequency can receive the satelltie just as easily themselves, there is
little advantage to this process.
Now #2 might not be as big a problem as I fear, because presumably if a
-real- satgate gets the packet first, then that copy may be the one that
FINDU see's and then it will ignore all others [which are delayed by the
digipeat (but unmarked as being via the satellite)]. But it seems not
worth the risk.
But thanks for your enthusiasm! I suggest a parked vehicle with a D700
would be a great candidate for an RS-232 cable from the driveway through a
window to a PC running as an Igate would also work when parked at home if
one has a clear horizon. The mobile antenna will possibly do better than
the base station because it has a shorter less lossy coax run.
De WB4APR, Bob
>You do not need an Internet connection at all for this setup.
>See details here:
>
>http://aj3u.com/aprs/aj3u-10.php
>
>Here is the operations website for ANDE and RAFT:
>
>http://eng.usna.navy.mil/~bruninga/ande-raft-ops.html
>
>Access for digipeating is not granted until their primary mission is
>complete. Look for an e-mail from Bob (WB4APR) for a go-ahead to
>start digipeating.
>
>--
>A.J. Farmer, AJ3U
>http://www.aj3u.com
------------------------------
Message: 2
Date: Tue, 19 Dec 2006 13:31:38 -0600
From: Jason Winningham <jdw_at_eng.uah.edu>
Subject: Re: [aprssig] Get ready to receive RAFT and ANDE telemetry!
Can someone remind me (again) what a satgate configuration should look
like? Isn't it a standard Igate connected to a particular APRS-IS server?
I've been told this before, but it looks like I've lost my configuration
file.
-Jason
kg4wsv
------------------------------
Message: 3
Date: Tue, 19 Dec 2006 15:19:32 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: [aprssig] RAFT and ANDE IGating
>Can someone remind me (again) what a satgate configuration
>should look like? Isn't it a standard Igate connected
>to a particular APRS-IS server?
Actually, it is a standard Igate connected to your favorite standard APRS
server. Since ALL of the packets from ANDE and RAFT are all APRS packets,
they should go directly into the APRS-IS via what ever is best for you.
Though I welcome an opinion by the APRS-IS folks.
We only set up the special SATgate servier for PCSAT-2 that had a lot of
9600 baud science data that did not need to be flooded into the APRS-IS.
But now, with ANDE and RAFT, it is all standard APRS at 1200 baud, so it
should be fine for the normal APRS-IS.
So, all you have to do is QSY your Igate radio from the national APRS
frequecny to 145.825...
**** AND **** TURN OFF GATING TO RF ********* **** THIS IS ABSOLUTELY
CRITICAL ******
That should do it.
Thanks!
Bob, WB4APR
------------------------------
Message: 4
Date: Tue, 19 Dec 2006 17:28:41 -0500
From: "A.J. Farmer (AJ3U)" <farmer.aj_at_gmail.com>
Subject: Re: [aprssig] Get ready to receive RAFT and ANDE telemetry!
As far as I know, you can connect to any APRS-IS server. It all gets to
the same place. I think there was a "dedicated" SatGate APRS-IS server a
while back but I think it was just an attempt to track how many SatGates
were out there...
--
A.J. Farmer, AJ3U
http://www.aj3u.com
------------------------------
Message: 5
Date: Tue, 19 Dec 2006 19:44:40 -0330
From: "Ken Whalen" <vo1st_at_rac.ca>
Subject: [aprssig] RE: aprssig Digest, Vol 30, Issue 18 - UI-View
SatGate Parms
With respect to Satgate settings, does a setup page exist for UI-View?
Ken VO1ST-1
------------------------------
Message: 6
Date: Tue, 19 Dec 2006 18:49:34 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: [aprssig] APRS USER TELEMETRY Plan for ANDE and RAFT
ANDE, RAFT and MARScom Telemetry Plan:
The first few days of ANDE, RAFT and MARScom will focus on capturing whole
orbit telemetry. User packets are not authorized (except for authorized
command station checkouts). But we do welcome TELEMETRY and LOG capture
files for any data that did not make it through the Satgates and APRS
Internet System. We make these telemetry requests:
1) Make sure your TNC or logging clock is within a second or so of UTC
time. It can be LOCAL time if you clearly tell us whether to ADD or
SUBTRACT X hours from the time indicated. If you send us the file, include
your statment of the accuracy or offset of your clock in the first line of
the file.
2) Please compare your packets to the raw packets captured at the bottom of
the live FINDU downlink page: http://pcsat.aprs.org. We only need a copy
of the raw packets that you captured that are -not- on that list (at the
bottom of the page). You will have to make your comparison within an hour
or so, depending on activity, so that the packets of interest do not scroll
off the page.
3) It would be very helpful to our data team if you edited out all the
dupes and only send us the packets that are not on FINDU.
CAUTION: Since the FINDU page normally does not have a time stamp and only
shows the relative age of a packet (but no reference) it is obsolete the
moment you view it. So it is best to either annotate the time at the
instant that you refreshed the page, or better is to click on the LINK that
says "clickhere to see times in UTC". It will download another page with
complete time stamps.
FREQUENCY: Monitor 145.825 MHz 1200 baud packet for ANDE and RAFT.
Monitor 27.965 SSB 1200 baud AFSK packet for NMARS. Notice, you may also
hear UO-11 on the same 145.825 frequency. NMARS is lighter and will
eventually lead RAFT.
TELEMETRY NOTES: The telemetry from all three satellites are in
standard APRS telemetry format of the KPC-3 TNC's:
T#SSS,111,222,333,444,555,11111111,000. There are several easy
observations:
1) It is important to note that T#SSS is a serial number and that these
serial numbers are helpful for determining dupes or absolute time. For
RAFT and NMARS, these are once a minute and will count up to 999 and then
roll back to 000. That takes about 16 hours unless we take some high rate
data.
2) ANDE, however, does a COLD boot on every pass. So for ANDE, the T#SSS
is every 50 seconds and will tell you how long the TNC has been up since it
last awoke. Hopefully it will only be awake for 10 to 20 minutes at a
time, though while it is in range of the pesky RAFT's telemetry, it may be
kept awake for hours until RAFT gets out of range.
WHAT TO LOOK FOR:
For RAFT and NMARS you can visually decode the 5 channels of
telemetry (see format above).
111 - is Voltage in 0.1 volts. (80 ==> 8.0 volts)
222 - is Solar current in 2 mA's. Multiply by 2 for mA
333 - is Battery current in 2 mA's. Multiply by 2 for mA
444 - is Load current in 2 mA's. Multiply by 2 for mA
555 - is temperature (a cubic, but 128 is about room temp)
A healthy spacecraft will be above 8.0 volts and will see consistent solar
current while in the sun.
ANDE is more complicated because it has a total of 20 telemetry channels
divided up among four separate packets. So it takes 3.3 minutes to get a
complete set. You can tell which set you get by the first 2 digits of the
8 bit number at the end.
00XXXXXX, 01XXXXXX, 10XXXXXX and 11XXXXXX. ANDE runs on primary batteries
and no solar power, so it either works or it doesn't. But the most
important data is the spin rate which we hope to derive from the 6 solar
sensors. These packets are the 11XXXXXX packets.
For more info on telemetry, check these pages:
http://www.ew.usna.edu/~bruninga/craft/RAFTeqns.gif
http://www.ew.usna.edu/~bruninga/ande/ANDEeqns.txt
And for up-to-date info about this mission, please check the main
operations page:
http://www.ew.usna.edu/~bruninga/ande-raft-ops.html
Bob Bruninga, WB4APR
US Naval Academy Satellite Lab
------------------------------
Read previous mail | Read next mail
| |
