OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
UA9FBV > SAT      25.07.04 20:15l 140 Lines 4213 Bytes #999 (0) @ AMSAT
BID : ANS-207.S2
Read: GUEST
Subj: WEEKLY SATELLITE REPORT PART 2
Path: DB0FHN<DB0MRW<DB0WUE<DK0WUE<DB0RES<ON0AR<7M3TJZ<SP7MGD<IZ0AWG<IK1ZNW<
      RZ6HXA<ER3KAZ<UA9FBV
Sent: 040725/1808Z @:UA9FBV.PRM.RUS.AS #:3486 [Perm] GATEWAY $:ANS-207.S2
From: UA9FBV@UA9FBV.PRM.RUS.AS
To  : SAT@AMSAT


AMSAT NEWS SERVICE BULLETIN 207.S2 FROM AMSAT HQ
SILVER SPRING, MD, July 25, 2004
TO ALL RADIO AMATEURS
BID: $ANS-207.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

Chris G7UPN, reports on 23 July, 2004:
We're currently working on bringing it back up following an attitude anomaly
yesterday. This may take another few days before we're back online.
[07252004]
=====
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

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

Mike Swartwout, KE6YNJ, Sapphire Operations Lead reports this week:
I think Sapphire is reaching his last legs as PCSat did; the batteries have
been beaten up for too long and have lost capacity. (They were sized for a
1-year mission, so, as we approach 3 years in orbit, this is to be expected.)
However, it *could* be that we've all been digipeating/contacting him enough
that he can't get his power levels back up.So, to test that theory, I asking
for a halt to Sapphire digipeating for the time being; we'll keep an eye on
him for the next ten days and give you an update. If it's not a power manage-
ment problem and is just a sign of old batteries, we'll open him up for digi-
peating again.  Otherwise, we'll have to work out some new arrangement. In the
meantime, we will be turning the beacon off to conserve power, so you should
not expect to hear anything. Hopefully we can squeeze a few more months out of
him.
[07252004]
NNNN


Read previous mail | Read next mail


 18.09.2025 03:39:56lGo back Go up