| |
CX2SA > SAT 19.07.04 03:42l 141 Lines 4166 Bytes #999 (0) @ AMSAT
BID : ANS-200.S2
Read: DO4BMW GUEST
Subj: WEEKLY SATELLITE REPORT PART 2
Path: DB0FHN<DB0MRW<OK0PPL<DB0RES<ON0AR<7M3TJZ<WB0TAX<W7NTF<VE2RXY<CX2SA
Sent: 040719/0137Z @:CX2SA.LAV.URY.SA #:54858 [Minas] FBB7.00e $:ANS-200.S2
From: CX2SA@CX2SA.LAV.URY.SA
To : SAT@AMSAT
AMSAT NEWS SERVICE BULLETIN 200.S2 FROM AMSAT HQ
SILVER SPRING, MD, July 18, 2004
TO ALL RADIO AMATEURS
BID: $ANS-200.S2
UO-11 OSCAR-11
Catalog number: 14781
Launched: March 1, 1984
Status: Semi-operational.
Downlink: 145.826 MHz FM (1200-baud AFSK)
Mode-S Beacon: 2401.500 MHz
The URL is: http://www.users.zetnet.co.uk/clivew/
[06132004]
=====
AO-16 PACSAT
Catalog number: 20439
Launch Date: January 22, 1990
Status: Semi-operational, the digipeater command is on and open for
APRS users.
Uplink: 145.90 145.92 145.94 145.96 MHz FM
(using 1200-baud Manchester FSK)
Downlink: 437.026 MHz SSB (1200-baud PSK)
Mode-S Beacon: 2401.1428 MHz
Broadcast Callsign: PACSAT-11
BBS: PACSAT-12
A WOD collection of current graphics along with general information
and telemetry samples can be found at:
http://www.telecable.es/personales/ea1bcu
[05092004]
=====
UO-22 UOSAT
Catalog number: 21575
Launched: July 17, 1991
Status: Operational
Uplink: 145.900 FM 9600-baud FSK
Downlink: 435.120 MHz FM
Broadcast Callsign: UOSAT5-11
BBS: UOSAT5-12
[05092004]
=====
IO-26 ITAMSAT
Catalog number: 22826
Launch Date: September 26, 1993
Status: No uplinks currently
Uplink: 145.875 145.900 145.925 145.950 MHz FM (1200-baud)
Downlink: 435.812 MHz SSB
Broadcast Callsign: ITMSAT-11
BBS: ITMSAT-12
[05092004]
=====
GO-32 TECHSAT-1B
Catalog number: 25397
Launch Date: July 10, 1998
Status: Semi-Operational.
Downlink: 435.225 MHz FM (9600-baud FSK)
(435.325 n/a - temperature problems)
Uplinks: 145.850, 145.890, 145.930 FM
1269.700, 1269.800, 1269.900 FM
Broadcast Callsign: 4XTECH-11
BBS Callsign: 4XTECH-12
Shlomo, 4X1AS, reports:
Problem was reported to GO-32 team, was verified by the team and is being
attended.
Any further info to WSR would be appreciated.
[07182004]
=====
NO-44 PCSAT
Catalog number: 26931
Launch Date: September 30, 2001
Status: Semi-Operational
Uplink/downlink: 145.827 MHz 1200 baud AX.25 AFSK via W3ADO-1
Aux/Uplink: 435.250 MHz 9600 baud via PCSAT-2 (off)
APRS Downlink: 144.390 MHz (Region 2)
PCSat is a 1200-baud APRS digipeater designed for use by stations using
hand-held or mobile transceivers. Downlinks feed a central web site at:
http://pcsat.aprs.org
The APRS-equipped PCSat was built by midshipmen from the U.S. Naval Academy
under the guidance of Bob Bruninga, WB4APR.
For more information, visit the PCSat web site at:
http://web.usna.navy.mil/~bruninga/pcsat.html
[0509004]
=====
NO-45 SAPPHIRE
Catalog number: 26932
Launch Date: September 30, 2001
Status: Operational
Downlink: 437.095 MHz 1200 baud AX-25 AFSK
Uplink: 145.945 MHz UI Digipeater
Digi Callsign: KE6QMD
The NO-45 digipeater remains on. User are requested NOT
to use the Bulletin Board. When the Bulletin Board is used it effectively
"locks out" ground access to the spacecraft CPU.
Everyone is welcome to use the digipeating/APRS features of Sapphire,
callsign KE6QMD, as per the user service agreement located at the following
URL
http://web.usna.navy.mil/~bruninga/pcsat/contract.txt
John, KD6PA asked on the amsat-bb:
I noticed that it's back in the mode i noted initially last November where
it's sending two short bursts of largely unmodulated carrier approximately
every 60 seconds. Does its TNC need power-cycling again?
Mike Swartwout, KE6YNJ, Sapphire Operations Lead answered back:
The 60-second burst is the default setting, which either means that
the spacecraft CPU has already reset or (more likely) the period was not
changed after a previous reset. Sapphire has been 'on loan' to Santa Clara
University for a few months, so they may have changed the beacon period.
My own command station is down for roof repairs, so it'll be another week
before I can check for myself. If digipeating is down, let me know and I can
draft one of our backup stations into service. Otherwise, Sapphire is stable
enough to stay in the reset state for another week.
[07182004]
NNNN
Read previous mail | Read next mail
| |
