home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
World of Ham Radio 1997
/
WOHR97_AmSoft_(1997-02-01).iso
/
sat
/
sat_03
/
amsoft.iii
next >
Wrap
Text File
|
1997-02-01
|
404KB
|
9,051 lines
WHATS-UP.DOC Release 1.40 Page 1
WHATS-UP (c) Joe Kasser, G3ZCZ, 1991-1996
_______
Joe Kasser G3ZCZ/W3 ____|__ | (tm)
POB 3419 --| | |-------------------
Silver Spring, Md. 20918 | ____|__ | Association of
Voice (301) 593 6136 | | |_| Shareware
Data BBS (301) 593 9067 |__| o | Professionals
Internet jkasser@capaccess.org -----| | |---------------------
|___|___| MEMBER
The program is distributed as a Shareware product. You may freely
copy and share the product for non commercial use, with your
friends, classmates, associates and radio hams. If you decide to use
the product, you are asked to become a registered user by completing
the registration form and sending it, and $35.00 (drawn on a US Bank
please) or equivalent in foreign currency to the author. Mastercard
and Visa are accepted if more convenient.
Upon receipt of your registration, you will receive one free update
disk, telephone and mail (electronic and regular) support. Please do
not use packet radio mail for commercial messages, or even those
that may be construed as such by individual SYSOPS through whose
BBSs the messages may pass.
This product may not be sold or distributed with another product
without the express written permission of Joe Kasser, G3ZCZ. Joe
Kasser, G3ZCZ will only support unmodified copies of this software.
Your comments and suggestions for changes are however welcome. If
you are the first to suggest a change that is implemented, you will
be sent a complimentary copy of the disk with the change
incorporated.
European Radio Amateur users may register (24.00 Pounds Sterling,
VAT) and obtain support from Terry Dansey at ReadyCrest Ltd., PO Box
75, Chatham, Kent, ME5 9DL, England. ReadyCrest Ltd., accepts credit
cards (Access, Visa, MasterCard and Eurocard). Telephones: Voice 44
(0)634-687168, FAX 44 (0)634-687178, Data (BBS) 44 (0)634-200931.
Potential Commercial and Educational Institution Users please
contact Joe Kasser directly for modifications and/or details of Site
licensing.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 2
Table of Contents
1.0 Introduction .......................................1
1.1 Capabilities of WHATS-UP ..........................3
1.2 Program Requirements ..............................4
1.3 Packet Link Quality Measurements ..................5
1.4 Copying Non-packet Telemetry ......................5
1.5 Obtaining Updates .................................5
1.6 Limit Checking ....................................6
1.7 Radio Control .....................................6
1.8 Using Different Terminal Units and TNCs ...........6
1.8.1 PK-232 .....................................6
1.8.2 KAM ........................................6
1.8.3 MFJ-1278 ...................................7
1.8.4 TNC1, TNC2 and PK-88 .......................7
1.8.5 PK-900 .....................................7
1.8.6 DSP-232 ....................................7
1.9 Upgraders Note Incompatibility ....................7
1.10 Logging Notes ....................................7
1.11 SAREX/MIR automatic connect/digipeat mode ........8
1.12 Self contained CW terminal .......................8
1.13 Parallel port Interface ..........................8
1.14 Equipping yourself for OSCAR ....................10
2.0 Customization .....................................12
2.1 Bringing WHATS-UP up for the First Time ..........12
2.2 Editing the Configuration File ...................12
2.3 Starting the program .............................13
2.3.1 Default ...................................13
2.3.2 User Chosen spacecraft ....................13
2.3.3 Custom Mode ...............................14
2.4 Screen Areas .....................................14
2.5 Setting Up Customized Display Pages ..............15
2.5.1 Customizing Analog Telemetry Channel
Displays .....15
2.5.2 Customizing Status Telemetry Channel
Displays .....16
2.5.3 Customizing Packet Header Displays ........16
3.0 Modes .............................................17
3.1 Standby Mode .....................................17
3.2 Interactive Mode .................................17
3.3 Real Time Mode ...................................17
3.4 Orbital Dynamics Mode ............................17
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 3
3.5 Playback Mode ....................................19
3.6 (Data) Extraction Mode ...........................19
3.7 Mutual Visibility Mode ...........................19
3.8 Audio Warnings and Orbit Data Displays ...........20
3.9 Autotrack ........................................20
4.0 Menus .............................................22
4.1 Function Keys ....................................22
4.1.1 FK 1 Capture to disk Toggle ...............22
4.1.2 FK 2 Type of display
Engineering Units/Raw Byte Toggle ..22
4.1.3 FK 3 Select display page ..................22
4.1.4 FK 4 Change Doppler frequency display .....23
4.1.5 FK 5 Display MH list ......................23
4.1.6 Alt-B send a 'Break' to the TNC ...........23
4.1.7 Alt-C connect to another packet station ...23
4.1.8 Alt-D disconnect from another
packet station .........23
4.1.9 Alt-F flush receiver buffer ...............23
4.1.10 Alt-I autotrack toggle ...................23
4.1.11 Alt-J jump to DOS (shell) ................23
4.1.12 Alt-P Printer on/off toggle ..............24
4.1.13 Alt-S Sound on/off toggle ................24
4.1.14 Alt-X Quit ...............................24
4.1.15 Alt += debug toggle ......................24
4.1.16 left arrow decreases playback speed ......24
4.1.17 right arrow increases playback speed .....24
4.1.18 Up arrow steps parallel port
radio memory up ........24
4.1.19 Down arrow steps parallel port
radio memory down ......24
4.2 Selections Menu ..................................24
4.2.1 Change Display Page .......................25
4.2.2 Edit Menu .................................25
4.2.3 Files Menu ................................25
4.2.4 Help Menu .................................25
4.2.5 Jump to DOS ...............................25
4.2.6 Modes Menu ................................25
4.2.7 Log Menu ..................................26
4.2.8 Orbits Menu ...............................26
4.2.9 Radio Menu ................................26
4.2.10 Spacecraft Menu ..........................26
4.2.11 TNC or PK232 Menu ........................26
4.2.12 Utilities Menu ...........................26
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 4
4.2.12 CW Menu ..................................26
4.2.14 Exit to DOS ..............................26
4.2.15 SAREX Menu ...............................26
4.3 Modes Menu .......................................26
4.3.1 Extract From Playback File ................27
4.3.2 Interactive Mode ..........................27
4.3.3 Orbital Parameters ........................27
4.3.4 Mutual Visibility .........................27
4.3.5 Playback Mode .............................27
4.3.6 Real Time Mode ............................27
4.4 Edit Menu ........................................27
4.4.1 Edit Doppler File .........................30
4.4.2 Any File ..................................30
4.4.3 Edit Keplerian Element File ...............30
4.4.4 Edit Spacecraft Configuration File ........30
4.4.5 Pick Capture-to-disk File .................30
4.4.6 Edit Capture-to-disk File .................30
4.4.7 Edit WHATS-UP.SYS .........................30
4.4.8 Two Files .................................30
4.4.9 Edit Doppler Channel File .................31
4.4.10 Edit Doppler Data File ...................31
4.4.11 Pick Spacecraft Configuration File .......31
4.4.12 Edit Today's Data ........................31
4.5 Files Menu .......................................31
4.5.1 Change Directory Path .....................31
4.5.2 Change Playback File ......................31
4.5.3 View Playback File ........................32
4.5.4 Show Spacecraft Capture-to-disk Files .....32
4.5.5 Show Data Files ...........................32
4.5.6 Show Files for 1 Spacecraft ...............32
4.6 Orbits Menu ......................................32
4.6.1 Pick AMSAT Format Element Set .............32
4.6.2 Edit Default Keplerian Element File .......33
4.6.3 Load Element File .........................33
4.6.4 Set Ref S/C (Mutual Visibility) ...........33
4.6.5 Pick NASA 2 Line Element Set ..............33
4.6.6 Show next pass ............................33
4.6.7 Set Ref = Sun (Mutual Visibility) .........34
4.6.8 View Spacecraft Orbit Elements ............34
4.6.9 Show/hide Sun Data ........................34
4.7 Radio Menu .......................................35
4.7.1 Turn Doppler Tracking ON/OFF ..............35
4.7.2 Set New Frequency .........................35
4.7.3 Change Doppler Interval ...................35
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 5
4.7.4 Set Radio Modulation ......................36
4.7.5 Read VFO A Frequency ......................36
4.7.6 Set Default Frequency .....................36
4.7.7 Select VFO A/B ............................36
4.7.10 Set Current Radio Memory .................36
4.7.11 Step Radio Memory Down ...................36
4.7.12 Set Radio Memory Scan Delay ..............36
4.7.13 Set Scan Radio Memory ON/OFF .............37
4.7.14 Select Radio Memory ......................37
4.7.15 Step Radio Memory Up .....................37
4.8 Spacecraft Menu ..................................37
4.8.1 Show Spacecraft Configuration File ........37
4.8.2 Default Spacecraft ........................37
4.8.3 picK Spacecraft ...........................37
4.8.4 Change Spacecraft .........................38
4.8.5 Pick Ops. Schedule ........................38
4.8.6 Show Ops. Schedule ........................38
4.9 TNC Menu .........................................38
4.9.1 UoSAT ASCII Beacon ........................39
4.9.2 Phase 3 RTTY Beacon .......................39
4.9.3 Set Morse Code (CW) .......................39
4.9.4 Fuji/MicroSat ASCII Packet ................39
4.9.4 Configure TNC .............................39
4.9.5 FM Packet .................................39
4.9.6 SARA ASCII Beacon .........................40
4.9.6 Select MFJ-1278 Radio Port
(if TNC is an MFJ 1278) ...............40
4.9.7 Select AO-13 PSK (if TNC is a DSP-2232) ...40
4.9.8 Select 9600 Baud Packet
(if TNC is a DSP-2232 or PK-900) ......40
4.10 Utilities Menu ..................................40
4.10.1 Change Directory Path ....................40
4.10.2 Enable/Disable RS-232 Port ...............40
4.10.3 Enable/Disable TNC Port
4.10.4 Turn MET Window ON/OFF ...................41
4.10.5 Show Space on Disk ............................41
4.10.6 Reset Header Counters ....................41
4.10.7 Show Defaults ............................41
4.10.8 Show Files ...............................41
4.10.9 Show Color Chart .........................42
4.10.10 Reconfigure WHATS-UP ....................42
4.11 Debug Menu ......................................42
4.11.1 CW Tone Test .............................42
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 6
4.11.2 Turn Debug OFF ...........................42
4.11.3 Set Frequency ............................42
4.11.4 Interrogate Radio ........................43
4.11.5 Show Defaults ............................43
4.11.6 Command Radio ............................43
4.11.7 Speak Frequency ..........................43
4.11.8 Identify Radio ...........................43
4.12 Log Menu ........................................43
4.12.1 Alt-A Append Entry .......................44
4.12.2 Alt-E Edit Log Entry .....................45
4.12.3 Alt-H Scan Log by Call ...................45
4.12.4 Pack Logbook .............................45
4.12.5 Alt-S Scan Log by Call ...................45
4.12.6 Alt-U Toggle Delete Mark .................45
4.12.7 Alt-X eXit Log ...........................46
4.12.8 Ins Toggle Insert Mode ...................46
4.12.9 End Show Last Page .......................46
4.12.10 Home Show First Page ....................46
4.12.11 PgUp Move Up One Page ...................46
4.12.12 PgDn Move Down One Page .................46
4.12.13 Up Arrow Move Up One Entry ..............46
4.12.14 Down Arrow Move Down One Entry ..........46
4.13 SAREX Menu ......................................46
4.13.1 Set Attack Mode ON/OFF ...................47
4.13.2 Change SAREX Call ........................47
4.13.3 Set Attack Mode Attack Mode [QCB] ........47
4.13.4 Reset SAREX Flags ........................48
4.13.5 Turn Zap R0MIR-1 ON/OFF ..................48
4.13.6 Single/Multiple User Connects ............48
4.14 CW Menu .........................................48
4.14.1 Sound Text ...............................49
4.14.2 Set CW Speed .............................49
4.14.3 Turn CW keyboard ON/OFF ..................49
4.14.4 Set CW Note ..............................50
4.14.5 Show CW Memories .........................50
4.14.6 Transmit Text ............................50
4.14.7 Slow CW Down .............................50
4.14.8 Speed CW Up ..............................50
4.14.9 Change CW Memory 1..10 ...................50
5.0 Orbital Elements ..................................51
5.1 Basics ...........................................51
5.2 Orbital Trajectories .............................51
5.3 Types of orbits ..................................52
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 7
5.3.1 Kepler's Laws .............................53
5.4 Orbital Elements ................................53
5.4.1 Angle of Inclination ......................54
5.4.2 Right Ascension of Ascending Node (RAAN) .......54
5.4.3 Eccentricity and Semimajor Axis ...........55
5.4.4 Decay Rate ................................56
5.4.5 Argument of Perigee .......................56
5.4.6 Epoch Time (of Ascending Node)
and Revolution Number .................56
5.4.7 The Mean Motion ...........................57
5.4.8 The Catalog Number ........................57
5.4.9 Mean Anomaly ..............................57
5.5 Anticipated Spacecraft Lifetimes .................57
5.5.1 Orbital Decay .............................57
5.5.2 Battery lifetime ..........................58
5.5.3 Radiation Damage ..........................58
6.0 The Spacecraft ....................................60
6.1 Receiving system components ......................61
6.1.1 Antennas ..................................61
6.1.2 Receivers .................................62
6.1.3 Terminal Units and Modems .................63
6.2 Receiving Signals from DOVE ......................64
6.3 Receiving Signals from UO-2 ......................65
6.4 Receiving Signals from AO-13 .....................65
6.5 Receiving PSK Modulated Signals in the 70cm Band .66
7.0 Decoding Spacecraft Telemetry .....................68
7.1 DOVE (DO-17) .....................................69
7.2 UoSAT-2 ..........................................72
7.3 AO-13 ............................................75
7.4 AO-16, WO-18 and LO-19 ...........................83
7.5 Fuji-OSCAR 20 ....................................91
8.0 Spacecraft No Longer Active ......................101
8.1 Fuji-OSCAR 12 ...................................101
8.2 SARA-OSCAR 23 ...................................104
8.2.1 The Primary Mission ......................105
8.2.2 The Secondary Mission ....................106
8.2.3 The Downlink .............................107
8.2.4 The Onboard Electronics ..................107
8.2.5 The Power System .........................108
8.2.6 Mechanical integration ...................108
8.2.7 Thermal Control ..........................109
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 8
8.2.8 Educational Opportunities ................109
8.3 ARSENE ..........................................110
8.3.1 Arsene Telemetry Equations ...............110
8.3.2 ARSENE Digital status telemetry ..........114
8.4 AO-21 (RM-1) ....................................115
9.0 File formats .....................................124
9.1 Configuration File (WHATS-UP.SYS) ...............124
9.1.1 Your callsign ............................125
9.1.2 Default spacecraft Name ..................125
9.1.3 Station Latitude .........................125
9.1.4 Station longitude ........................126
9.1.5 Station Altitude .........................126
9.1.6 Station minimum antenna elevation
for acquisition .................126
9.1.7 Default Kepler file ......................126
9.1.8 UTC offset ....................................126
9.1.9 Default directory path ...................126
9.1.10 Default extracted data file .............126
9.1.11 Default file name
with list of telemetry parameters
to extract file ......................126
9.1.12 TNC Type ................................127
9.1.13 Serial port to TNC ......................127
9.1.14 PC TNC Serial baud rate .................127
9.1.15 PC TNC port data bits ...................127
9.1.16 PC TNC port Stop bits ...................127
9.1.17 PC TNC Port parity bits .................127
9.1.18 Status (top) window color ...............127
9.1.19 Incoming window color ...................127
9.1.20 Outgoing window color ...................128
9.1.21 Prompt window color .....................128
9.1.22 Alarm window color ......................128
9.1.23 Bottom window color .....................128
9.1.24 Emphasis color ..........................128
9.1.25 Option color ............................128
9.1.26 Parameter changed color .................128
9.1.27 Parameter limit exceeded color ..........128
9.1.28 Orbit element window color ..............128
9.1.29 Orbit element window In range color .....128
9.1.30 Orbit element window early warning
color ...............128
9.1.31 Orbit element window next one up
color ...............128
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 9
9.1.32 Logbook window color ....................128
9.1.33 SAREX call display color in
Status window ...............128
9.1.34 Active color ............................128
9.1.35 Orbit element post pass color ...........128
9.1.36 Orbit alert dit time ....................128
9.1.37 Orbit alert note ........................128
9.1.38 Flag Sound ..............................128
9.1.39 Doppler display Flag ....................129
9.1.40 TNC Command to select modem for CW ......129
9.1.41 TNC Command to select modem for
UoSAT ASCII 1200 baud ......129
9.1.42 TNC Command to select modem for
1200 baud PSK ..............129
9.1.43 TNC Command to select modem for
400 baud AO-13 PSK .........129
9.1.44 TNC Command to select modem for
9600 baud packet ...........129
9.1.45 TNC Command to select modem for
1200 baud FM AFSK ..........129
9.1.46 Logbook file ............................129
9.1.47 QSO Logging flag ........................129
9.1.48 Minimum angle of the sun for darkness
at your QTH ...........129
9.1.49 TNC stream switch character .............130
9.1.50 Spacecraft Configuration File Linkages ..130
9.1.51 Marker and Comment line .................130
9.1.52 CW Memory contents ......................131
9.1.53 The marker line .........................131
9.1.54 TNC configuration commands ..............131
9.2 Spacecraft Parameter Files ......................131
9.2.1 Spacecraft ID ............................132
9.2.2 Spacecraft Suffix ........................132
9.2.3 Beacon Frequency .........................133
9.2.4 Doppler Measurement File .................133
9.2.5 Spacecraft Identification in
Keplerian Element File .....133
9.2.6 Doppler Measurement Sample Interval ......133
9.2.7 Initial Frequency Offset .................133
9.2.8 Autotrack flag ...........................133
9.2.9 Modulation ...............................134
9.2.10 Data Type ...............................134
9.2.11 Receiver Type ...........................134
9.2.12 Receiver Address ........................134
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 10
9.2.13 PC Serial port to Radio .................135
9.2.14 PC Radio port Serial baud rate ..........135
9.2.15 PC Radio port data bits .................135
9.2.16 PC TNC port Stop bits ...................135
9.2.17 PC Radio Port parity bits ...............135
9.2.18 Post pass delay .........................136
9.2.19 Station minimum usable pass time ........136
9.2.20 Early warning time (EWT) ................136
9.2.21 SAREX/Mir Callsign ......................136
9.2.22 SAREX/Mir Header Delay ..................136
9.2.23 SAREX/Mir Attack Mode ...................136
9.2.24 SAREX/Mir Beacon Text ...................137
9.2.25 LPT parallel port
radio memory parameters ..............137
9.2.26 Selected or default display page number .137
9.2.27 Page Definitions ........................137
9.2.28 Telemetry Parameter Configuration .......137
9.2.29 Digital Telemetry Status Channels .......144
9.2.30 Packet/Link Parameters ..................146
9.3 Telemetry Channel Extraction File ...............148
9.4 Extracted Telemetry Data File ...................149
9.5 Doppler File ....................................149
9.5.1 The Time .................................149
9.5.2 The Doppler Mark .........................150
9.5.3 The Frequency ............................150
9.5.4 The Doppler Shift ........................150
9.5.5 The Measured Shift .......................150
9.6 Kepler Element Files (*.TLE) ...............151
9.7 AMSAT Format Element File (*.AMS) ...............152
9.8 Spacecraft Operations File .................153
10.0 Glossary ........................................155
11.0 References and Further Reading ..................156
12.0 Change History ..................................157
13.0 Obtaining Further Information ...................158
14.0 Other Products by Joe Kasser, W3/G3ZCZ ..........159
14.1 PC-HAM 3.52 .....................................159
14.1.1 LOGBOOK..................................159
14.1.2 CONTEST .................................159
14.1.3 CQSS ....................................159
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 11
14.1.4 WHATSON .................................159
14.2 STARTREK The Computer Program ...................159
14.3.LAN-LINK 2.34 ...................................160
14.4 ELMER 1.00 ......................................161
14.5 BASIC PACKET RADIO ..............................162
15.0 How Shareware Works .............................164
Appendix 1 WHATS-UP 1.40 REGISTRATION FORM ...........166
Index ................................................167
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 1
1.0 Introduction
WHATS-UP is a ground station tool for communicating through and
monitoring the state of satellites.
WHATS-UP is a tool which provides you the Radio Amateur, or the
Educator, with the capability to perform experiments in spacecraft
orbital dynamics as well as monitoring the environment onboard
several of the Orbiting Satellites Carrying Amateur Radio (OSCAR)
during individual passes or over long periods of time.
WHATS-UP is a table driven program which uses configuration files to
allow maximum flexibility. If you have a Kenwood Radio, WHATS-UP
will monitor a default frequency, the when a spacecraft comes up
over the horizon, WHATS-UP will tune the Radio's VFO A to the
spacecraft beacon frequency (plus a presettable offset) and set the
receive mode for the satellite of interest. If the Radio responds
correctly, WHATS-UP will allow you to read back the VFO A frequency
during the pass and capture the data to a Doppler measurement file
for later import to a spreadsheet. At the end of the pass, WHATS-UP
will return the radio to the default frequency and communications
mode.
This version of the program is configured for a TNC-1, TNC-2, PK-88,
PK-900, DSP 2232, KAM and PK-232. Note, it will not allow you to
copy non packet telemetry if you don't have a multi-mode terminal
unit. It will intercept the Microsat Binary telemetry from AMSAT-
OSCAR 16 (PACSAT or AO-16), WEBER-OSCAR 18 (WEBERSAT or WO-18) and
LUSAT-OSCAR 19 (LUSAT or LO-19)) and display and process them as if
they were DOVE-OSCAR 17 (DO-17) ASCII telemetry. NOTE: AMSAT have
STILL NOT FINALIZED or PUBLISHED the Binary Telemetry Format for the
Microsats.
Spacecraft in the OSCAR series send back volumes of Telemetry daily
and apart from the odd Command station, few if any Radio Amateurs or
Educators seem to be doing anything with it. Radio Amateurs tend to
concentrate on the communications capabilities of the spacecraft and
ignore their telemetry completely. If they do listen to a beacon,
it's usually just to check that the transponder is on, heaven forbid
- to actually copy any data.
The telemetry can tell us a story. It can tell us what is happening
to both the spacecraft and its environment. As such it has a
tremendous educational potential which has remained just that - a
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 2
potential for at least the last eight years.
Before every satellite launch the equations and format for the
spacecraft telemetry are published by the builders. The telemetry
tells us about the health and welfare of the spacecraft itself, and
something about the payload. Spacecraft health and welfare
information tells us about the battery, solar cells and on board
computer status. Payload information can range from information
about transponder loading/utilization to data from instruments that
measure the environment of the space in and around the satellite.
Battery Telemetry is used by the command stations to determine when
the spacecraft can be used, and when the transponders should be shut
down. The number of individuals not associated with command stations
who have decoded spacecraft telemetry and published their findings
can be counted using the fingers of one hand.
Capturing, decoding and displaying telemetry from orbiting
spacecraft in real time, in the classroom, is an excellent way of
introducing space science to students. Signals from these spacecraft
are downlinked on frequencies that can be received on regular
vhf/uhf scanner radio receivers. WHATS-UP provides an introduction
as to how this can be done using readily available low cost
equipment. General topics discussed cover telemetry, the spacecraft
themselves. Groundstation hardware topics include receiving
antennas, radio receivers and modems. Software topics discussed
include the software used to track the spacecraft and the software
used to both decode and display the data in real time as well as
that for post pass analysis. Excluding the Personal Computer, a
simple telemetry capturing groundstation can be set up for less than
$500.00 in equipment costs.
There is no substitute for the excitement of hands-on experience in
awakening an interest in space. While OSCARs in the main, transmit
down to the ground (downlink) telemetry in morse code, several of
them also utilize standard computer literate digital data schemes
such as BAUDOT or ASCII codes. The thrill of receiving a signal from
space soon fades however if the data cannot be understood. Even
after the data has been decoded, watching the temperatures on-board
a spacecraft as it passes overhead is also of little interest, but,
what can be made interesting is receiving and capturing the data
over many days or even months and looking for trends and
relationships.
You can capture telemetry just by listening to a spacecraft and
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 3
copying morse code by ear writing it down with a pencil on a piece
of paper. All you need to do is listen on the correct frequency at
the right time and you will hear some signals. Write down what you
hear. Apart from the thrill of copying a signal from a satellite,
there's not much else to do with the data. While you can look up the
conversion equations and get a snapshot of what is happening, it
soon becomes tedious and only dedicated souls do it regularly.
When AMSAT were building the Phase 3A spacecraft, personal
computing was in its infancy. That was before the Apple 2 or the
TRS-80; that was the day of the home built S-100 machine, and the
AMSAT-GOLEM-80 Project. At that time, Karl Meinzer, DJ4ZC, had
written a native German high level computer language called IPS.
This language was very similar to Forth, but contained a multi-
tasking kernel. This language was programmed into the spacecraft
flight computer and also used in the ground command stations. Using
a computer on the spacecraft allowed AMSAT to provide telemetry that
could be captured by computer on the ground. While Phase 3A never
made it into orbit (the launch vehicle malfunctioned), subsequent
spacecraft continued to provide the same facility. Today UoSAT-2
(UO-2), AMSAT-OSCAR 13 (AO-13), UoSAT-OSCAR 14 (UO-14), AMSAT-OSCAR
16 (AO-16), DOVE-OSCAR 17 (DO-17), WEBER-OSCAR 19 (WO-18), LUSAT-
OSCAR 19 (LO-19), Fuji-OSCAR 20 (FO-20) and AMSAT-OSCAR 21 (AO-21)
are all sending back telemetry that you can capture with your PC and
amateur radio equipment. As most non radio amateurs do not
understand morse code, WHATS-UP concentrates on those spacecraft
which downlink computer compatible telemetry and can be received
with relatively simple equipment.
1.1 Capabilities of WHATS-UP
WHATS-UP contains the following features:
* Self contained CW (keyboard only - you copy audio by ear)
satellite ground terminal with parallel port interface to Radio
up/down frequency control.
* Automatic connect attempt and beaconing via MIR, SAREX or any
other satellite with appropriate TNC.
* Automatic logging of Acquisition of Signal (AOS) in LAN-LINK
compatible logbook.
* Display of spacecraft orbital elements and tracking data.
* Will automatically set your Kenwood receiver to spacecraft
beacon frequency when the spacecraft comes above your horizon
and return it to the default frequency when the pass is over.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 4
* Audio warning of AOS and loss of signal (LOS).
* Real-time, Interactive and Playback modes.
* Automatic Capture-to-disk of raw telemetry.
* Extracts telemetry channel data to a database or spreadsheet
readable file for further analysis.
* Link quality measurement.
* Capability to display and print the raw telemetry as it is
received.
* Up to 16 user configurable display pages (screens). You set the
position on the page (width of engineering unit field, and
number of decimal places) that a parameter is displayed at.
* Wild card page (parameter shows up on all pages).
* Selectable display of Engineering units or Hex byte for each
display page.
* Display of raw packets (i.e. STATUS)
* Color changes if a parameter value changed between successive
frames.
* Audio and visual alarms if a telemetry value exceeds, falls
below or falls outside a preset limit value(s).
* Dumb split screen terminal mode with user selectable number of
window rows.
* Customizable colors, PC to TNC baud rate, data parity and stop
bits.
* Default spacecraft configuration files.
* UTC Time of day clock display (in HH:MM:SS format)
1.2 Program Requirements
IBM PC or clone with at least 256k memory.
A Radio receiver and a TNC with an RS-232 interface is only
required for real time data capture.
The program DOES require that the packetized telemetry be received,
and captured-to-disk with the packet header on a different line to
the contents of the packet (HEADERLINE ON). I also suggest that you
turn the date/time stamp on so that you will be able to playback
your data and extract selected values and their corresponding time
codes into a file that can be read into your spreadsheet program for
further trend analysis.
This version (the default) is set up to display all packets as wild
cards (i.e. will show up on all pages), and then display several
temperatures and solar cell array currents.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 5
By putting the correct parameters in the SPACECRAFT.CNF file, you
can set up any of the pages to display any of the telemetry channel
data in any row and column in that page.
1.3 Packet Link Quality Measurements
The packet link quality part allows the following to be done. You
can define which of the packets you want to display/count (If you
just want to count them and not display them, set the page value to
99). You can then view an incrementing count counter each time a
selected packet is received. For example, using DO-17, you can also
display the contents of the STATUS, WASH or BCRXMT packets in any
display page. This feature allows you to get an idea of how good
your receiving system is.
1.4 Copying Non-packet Telemetry
Packet telemetry, by definition is error free. The RTTY blocks from
AO-13 on the other hand may be received with errors. These errors
may take the form of garbled or missing characters. If your link is
bad, and such hits do occur, you should edit the capture-to-disk
file before you playback the telemetry and decode/display the data.
If you get bad data in real time, look at the raw data. You will be
able to see the quality of the link.
1.5 Obtaining Updates
It is anticipated that WHATS-UP is going to grow and incorporate
features for decoding and displaying data from other spacecraft.
Better Microsat binary telemetry decode and display capability will
be added when AMSAT announce that the format has stabilized, and
sufficient registered users express interest in having it. To stay
on the mailing list and receive an update as it is released,
register your copy, then send in a disk containing at least 1
Megabytes (zipped) of captured data from the spacecraft of your
choice. If you would like to exchange data with other educational
institutions or users so as to be able to analyze more data than you
can get on a single pass, indicate that fact and we will try and put
you in direct touch with others who are similarly inclined.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 6
1.6 Limit Checking
Limits are only checked for parameters being displayed (in
Engineering units). With this approach, you can set up different
pages for different on-board subsystems, you can also set up
different display pages of the same parameters for daylight,
darkness and terminator crossing passes, with different limit values
to draw your attention to changes.
1.7 Radio Control
Assuming you use a radio, when you first bring up WHATS-UP, it sets
the radio VFO A to the beacon frequency of the default spacecraft
configuration file (*.CNF). When a selected spacecraft is scheduled
to come above your horizon WHATS-UP will tune the radio to the
spacecraft's beacon frequency. When the pass is over, WHATS-UP will
return the radio to the default frequency. You can thus set up a
"dummy" configuration file for your local Packetcluster or voice
repeater and monitor that channel as long as the selected spacecraft
are below your horizon.
If a pass is taking place, and a second selected spacecraft comes
over your horizon, WHATS-UP will tune to its frequency UNLESS the
autotrack is disabled. See Section 3.9 for a description of the
autotrack feature.
1.8 Using Different Terminal Units and TNCs
This section briefly covers some of the differences between the
various TNCs on the market. To copy PSK signals from Fuji-OSCAR 20
and the microsats, you will need a PSK modem adapter for your TNC.
WHATS-UP has no way of checking that it is present.
1.8.1 PK-232
The PK-232 does not have a software selectable TNC radio port. You
have to use the switch on the panel. The PK-232 will receive signals
from UO-11 properly, only if the hardware modification described in
Section 7.2 of this document is performed.
1.8.2 KAM
The KAM cannot demodulate SARA's 300 baud ASCII or 1200 baud ASCII,
so signals from SARA and UO-11 cannot be copied. The KAM 2.85
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 7
firmware used to develop WHATS-UP assumes vhf packet on the vhf
port, and the non packet modes on the hf port. WHATS-UP 1.20 does
not let you switch ports on the KAM.
1.8.3 MFJ-1278
The MFJ-1278 cannot copy SARA's 300 baud ASCII or UO-11's 1200 baud
ASCII. WHATS-UP does not change the radio port. You set the radio
command in the WHATS-UP.SYS file. If you wish to change the radio
port, an option is provided in the Configure TNC Menu.
1.8.4 TNC1, TNC2 and PK-88
These TNCs only copy packet. The other modes will not work.
1.8.5 PK-900
This TNC is treated like a PK-232. If you have the optional 9600
baud modem you can try for the 9600 baud microsats.
1.8.6 DSP-232
This TNCs will give you all known modes. The current firmware does
not give you step track from the TNC to the Radio for PSK.
1.9 Upgraders Note Incompatibility
If you are upgrading from 1.30 or an earlier version the WHATS-
UP.SYS and SPACECRAFT.CNF files in 1.40 are not compatible.
1.10 Logging Notes
When WHATS-UP logs an acquisition, it places some temporal
information in the comments column. This information is, either:
* A check mark, if AOS is as scheduled.
* The number of minutes into the pass if AOS is late.
* A '>' and the estimated time to AOS is acquisition occurred
when WHATS-UP computed the spacecraft as being below the
horizon.
This information is designed to help you update any estimates for
AOS in the event your element set is out of date.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 8
1.11 SAREX/MIR automatic connect/digipeat mode
This feature should be used with caution as it has the potential to
cause QRM to other stations on channel. As a safeguard, WHATS-UP
will turn its attack mode off if it someone connects and sends a
':QRT:' instruction.
1.12 Self contained CW terminal
WHATS-UP contains a CW terminal, controlling the radio keyer and
parallel port interface. You can connect the parallel port to the
radio up/down buttons via the simple circuit described in Section
1.13. With a display of the Orbit parameters, you can:
Transmit CW by typing the characters at the keyboard.
Copy CW by ear.
Control the VFO to compensate for Doppler shift using the
up/down arrows.
Log the contacts into the logbook.
And you don't need a TNC to do it. If you go on a cw satellite DX-
pedition, and are taking along a laptop or notebook computer, try
this feature. If you are staying home, try it in the shack.
1.13 Parallel port Interface
WHATS-UP contains a driver to interface the PC's parallel port to a
radio. It maybe used as described in Section 1.12, or as described
in this section.
The interface circuit is shown in Figure 1.13. It consists of a TTL
latching register type 75LS175 and optical isolators on the output
side. You also need a 5 volt supply for the 74LS175 which may be
obtained from any suitable source. Each optical isolator circuit is
identical, so only one is shown below. A serial LED with each
optical isolator provides visual indication that something is
happening. You must use a strobed interface to ensure reliable
control of each bit.
The parts may be obtained from Radio Shack or any similar source
and are not critical. Almost any optical isolator will do provided
it can handle the open key voltage from the radio. If you are using
a solid state radio which runs of a 12 Volt supply, then don't worry
about the interface.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 9
The port bit assignments are as follows:
Bit Assignment
1 Key
2 Radio up
3 Radio down
4..8 Unassigned/unused
You can set the printer port assignment in the receiver address
line of the SPACECRAFT.CNF file (Section 9.2.12).
Figure 1.13 Simple parallel interface circuit.
+---------------+-----------------------< +5 volts
PC Printer | |
Port |5V RESISTOR (330 ohms)
ST ----- | -------
1 >--------|CK | |-|<|--| |---------< key
DB0 | | keyboard LED | |---------< Common
2 >--------|A Qa|--------------------|_____|optical isolator
DB1 | | radio up 4N33 etc.
3 >--------|B Qb|--------------- similar isolation -< Up
DB2 | | radio down circuits
4 >--------|C Qc|--------------- -< Down
| |
| |Ground
|-----|-+
74LS175 |
25>----------------+--signal ground (also on 18..24).
Notes
1 Do not connect PC signal ground connect to radio common side.
If you do, there is not much point in using isolation circuits.
2 Decouple 5 Volt supply to PC Signal ground.
3 Ground all unused inputs of the 74LS175 to avoid spurious
effects due to transients.
4 Use similar optical isolator connections for the up and down
connections to the radio.
5 Optional, but useful. Wire a 470 ohm resistor in series with a
green LED across the 5Volts and ground.
6 Use red LEDs in series with the optical isolators.
7 Add pull-up resistors on PC interface lines and 74LS175 clear
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 10
and reset lines.
1.14 Equipping yourself for OSCAR
The OSCAR satellites use frequencies in the VHF and UHF bands not
normally covered by the usual short wave or HF transceivers. Also
since the spacecraft transponders receive on one band and transmit
on a second, you will need to talk at them on one band and listen to
them on a second band. That means, not only do they operate split
frequency, but they operate split frequency on different bands.
In order to work people via the OSCAR spacecraft, you will need
transmitting equipment for your uplink and receiving equipment for
the downlink. If you are already a serious VHF/UHF operator you will
have SSB/CW equipment for the VHF/UHF bands used by the spacecraft.
On the other hand if you are new to the satellite bands, you will
have to purchase or otherwise obtain the necessary equipment.
There are two types of OSCAR satellites in orbit at this time. The
Phase 2 spacecraft are in low orbits, and carry a Mode A transponder
with an uplink on the 2 Meter band, and a downlink on the 10 Meter
band as well as a transceiver for a different Mode. The Phase 3
spacecraft are in high orbits and carry a Mode B transponder with an
uplink on the 70 Cm band and a downlink on the 2 Meter band. If you
thus equip yourself for operation on the 2 Meter band, assuming that
you have HF capability, you will be able to monitor signals from
both types of satellites and may even be able to work Mode A.
Take a look at the advertisements for 2 Meter SSB/CW transceivers in
the magazines. They look nice, have useful specifications but the
price! Do you really want to spend that money on a band you are not
sure that you will be active on?. The VHF/UHF bands aren't like the
HF ones. The majority of your contacts will be ground wave line-of-
sight. That means that your maximum range under normal conditions
will be between 100 and 200 miles.
If you live in an area of high VHF/UHF activity you may find it
worth while, because you will always have someone to talk to and
when conditions are right, you will be able to work DX.
Another factor to consider is the distance between the operating
position and the antennas. Co-axial cable has significant losses at
VHF/UHF frequencies. Satellite links are usually marginal, that
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 11
means that you cannot afford any reduction in your uplink power or
in the strength of the downlink.
Consider an alternative. In the days before commercial multi mode
VHF/UHF equipment became available, many people got on the air using
transverters. A transverter is a piece of equipment that contains a
transmitting and a receiving converter. Equipment such as the old
"Europa B" and the Microwave Modules series which are still
available were used to good effect. The Microwave Modules and units
made by other manufacturers are still available as you can see by
looking at the advertisements in your favorite amateur radio
magazine.
The transverter must be driven by a transceiver. The output from the
transceiver down converter is fed to the regular station receiver.
The input to the transceiver up converter comes from a low power
point in the transceiver. The well known FT-101 series of HF
transceivers as well as a number of others were designed with
transverters in mind. They are readily available on the used
equipment market at reasonable prices. Look at those advertisements
again, compare the cost of a used FT-101 (or similar rig) and a
transverter with the cost of that multi mode VHF/UHF rig. Getting on
two meters SSB this way has a number of advantages as follows.
The FT-101 can be used as a back up HF rig in the event of a failure
in the prime station transceiver. The FT-101 can also be modified to
work the new WARC bands. It can thus be used in a stand alone manner
from all bands 160 through 10 Meters.
The transverter could even be mounted on the mast at the antenna,
thus potentially providing a significant reduction in line losses
bare).
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 12
2.0 Customization
2.1 Bringing WHATS-UP up for the First Time
WHATS-UP comes configured to use Com1 in the PC as the serial port
between the PC and the PK-232, and with the serial port between the
PC and the Kenwood Radio DISABLED (Set to 0). WHATS-UP is also
configured to assume DOVE as the default spacecraft.
If you type 'WHATS-UP' followed by the 'Enter' key, the program
will load and start to do things. If the default serial ports are
correct for your system, you need do nothing further, other than
change the colors of the windows to your preference.
2.2 Editing the Configuration File
The configuration file is called WHATS-UP.SYS. You must edit it
using option 'S' in the Edit Menu or with an ASCII word processor
(in the non document mode) to set up the correct parameters on the
RS-232 link between your TNC and your PC. See Section 10 for details
of what parameter is on which line of the WHATS-UP.SYS file. If you
wish to activate the Radio features, you must select a Radio Port.
Before you make any changes, make sure that you do not try and edit
your original, always work from a copy.
These are the minimum set up items to change in the WHATS-UP.SYS
file. Refer to Section 9 for fuller details of what items are on
which lines. Bring up the Selections menu, the access the Edit Menu.
choose the option for editing the WHATS-UP.SYS file. As you enter
items on the lines listed below, delete the entries currently in
place.
Line 1: Enter your callsign instead of the default one. Use Capital
letters (Upper case). If you do not have a callsign, pick a
mnemonic that represents your school or organization. You
may use up to 10 characters. The callsign entered here,
will be shown at the top of the status window, next time
you load WHATS-UP, and will also (more important) be
appended to your capture-to-disk files to identify the
ground station which received the data.
Line 3: Enter the latitude of your location. In the southern
hemisphere, use a negative number.
Line 4: Enter the longitude of your station in degrees West of
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 13
Greenwich in the range 0 to 359.9.
Line 5: Enter the station altitude above sea level in meters. If
you don't know, don't change anything.
Line 10: Enter the difference between local time in your PC and
UTC. For example, eastern standard time is 5.
Line 12: Enter the name of the TNC (PK-232, PK-900, DSP-2232, TNC2,
KAM, MFJ1278, or PK-88).
Line 15: If you are not using Com1 as the serial port between the
PC and the TNC, enter the port number on this line.
Line 16: If you are not using 1200 baud between the PC and the TNC
enter the actual value on this line.
Line 20: If you have a compatible radio with RS-232 control
capability, enter the port number on this line (usually
Port 2).
Read Section 9.1 to see what else to change to make the PC
communicate with the TNC and the radio.
Save the file at this time. WHATS-UP will now work for you in its
minimal mode. Read the manual to learn about its capabilities and
use section 9 when you customize it to suit yourself.
2.3 Starting the program
You may start the program in three ways as follows.
2.3.1 Default
Type 'whats-up' and return (without the ' characters). This brings
the program up in the default mode. It will read the whats-up.sys
file to determine the spacecraft being monitored, and then prompt
you for the mode.
2.3.2 User Chosen spacecraft
Type 'whats-up spacecraft' and return (without the ' characters).
The program reads the spacecraft.sys file to load the parameters for
the Microsat of choice, and then prompts you for the mode. Examples
of the command are :
'WHATS-UP DOVE' or 'WHATS-UP Fuji20'
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 14
2.3.3 Custom Mode
Type 'whats-up spacecraft mode' and return (without the '
characters). This brings the program up in the custom mode. It will
read the whats-up.sys file to determine the spacecraft being
monitored, and then start up in the mode you set. Valid modes are
'p', 'i', 'o' and 'r'. Examples of the command are:
'WHATS-UP DOVE R' or 'WHATS-UP Fuji20 R'
If you place a command line like this in your autoexec.bat file,
should you be copying telemetry in an unattended manner and a power
failure take place, the system will boot up into the correct WHATS-
UP mode when power is restored.
When the program loads, the first thing it does is load the
Keplerian data from the default data file and compute the current
position of all the spacecraft. The following typical messages will
be send during this activity.
MIR Loaded
RS-10/11 Loaded
AO-13 Loaded
UO-14 Loaded
DO-17 Loaded
Computing Next Pass for AO-10
Computing Next Pass for UO-11
Computing Next Pass for MIR
Computing Next Pass for RS-10/11
Computing Next Pass for AO-13
Computing Next Pass for UO-14
Computing Next Pass for DO-17
If the default Keplerian data file is not present on the disk, the
orbital mode will be disabled. If the default Keplerian data file is
empty, WHATS-UP will abort with a Run-Time Error.
2.4 Screen Areas
The screen is divided into four window areas. The Status window
occupies the top line. The prompt window occupies the bottom line.
Raw data are always shown in the lower data area. This window also
shows any outgoing text that you may type at the keyboard or any
commands WHATS-UP sends to the TNC. The data area in the top half of
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 15
the screen contains the processed data (real time and playback), the
raw data (interactive) and the orbital data display.
2.5 Setting Up Customized Display Pages
The ability to customize a display page is a unique tool provided
by WHATS-UP. This tool allows you to group telemetry information so
you can see how the monitor points you are interested in behave, and
visually see the changes. You can locate information in any position
on the screen and in any color you wish. You can also perform limit
checking on the data, and have the "out-of-limit" show up in
different colors and generate audible alarms.
Setting up display pages is an orderly procedure using the
information contained in Section 9. When you want to customize the
displays, make a copy of the supplied spacecraft configuration file
and work with it. Look at the format of the file, read Section 9.2
to sure that you understand what is in the file. Use the editor to
adjust the items in the spacecraft configuration file. After editing
the file, reload the file to enter the changed parameters into
WHATS-UP to see the effects of your changes. Repeat this procedure
until you are satisfied.
First, from the utilities menu, view the colors and decide on the
color scheme for the window and data.
Lay out the display page on graph paper for a screen window of 13
rows by 78 columns.
Decide on the name of the page. If it is a new page enter the name
on a new line after the existing pages before the line that ends in
an '*' character. Do not delete the '* character. After you have
entered the page name, insert a comma character ',' and a number for
the default page color. An example from the DOVE.CNF file for such
an entry is shown below.
PAYLOAD TRANSMITTER/RECEIVERS, 30
2.5.1 Customizing Analog Telemetry Channel Displays
The next few lines contain the analog telemetry decoding display
information. Review Section 9.2 to see what has to be inserted in
each of the elements. The analog telemetry lines are terminated with
the following line, which must be present even if no data lines are
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 16
present.
'* end of telemetry'
2.5.2 Customizing Status Telemetry Channel Displays
Section 9.2.14 describes the meaning of each item. The status
telemetry lines are terminated with the following line, which must
be present even if no data lines are present.
'* end of status bytes'
2.5.3 Customizing Packet Header Displays
The packet header configuration lines contain the analog telemetry
decoding display information. Details of the meaning of each item
are given in section 9.2.15. The packet header lines are terminated
with the following line, which must be present even if no data lines
are present.
'* end of packet types'
If you want to change the colors that channels out of limit, or
channels in which the data changed between telemetry frames are
displayed in, you must change the entries in the WHATS-UP.SYS file.
207 is a respectable value for the color to display data for which
the limit has been exceeded (flashing white on red background).
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 17
3.0 Modes
WHATS-UP is designed to operate in a number of modes as listed
below. Each mode has its own type of window display. To change
things or select features, touch the 'Esc' key to bring up the top
level menu. Menus in WHATS-UP are organized as a hierarchy, each
option will take you as deep as necessary to make your selection.
3.1 Standby Mode
The standby Mode presents you with the Modes Menu as described in
Section 4. This mode is activated if you bring up WHATS-UP without
specifying a mode in the command line.
3.2 Interactive Mode
The Interactive mode is a dumb terminal. You can use it to give
commands to the TNC. You should also use it to set the 'HEADERLINE
ON'. In this mode, you will see the raw packets on the channel. You
can also use this mode as a regular TNC program (If you do, you
ought to get your head examined, because LAN-LINK will do the job
much better). The capture-to-disk will turn on when the first packet
is copied, and will turn off two minutes after the last.
3.3 Real Time Mode
The Real-time mode converts and displays engineering data. You can
display up to 16 (configured by you) pages of information.
Information that changes between successive frames, is shown in a
different color. Information that has exceeded a preset (by you)
limit is shown in an alarm color (default: blinking red). The
capture-to-disk will turn on when the first packet is copied, and
will turn off two minutes after the last.
3.4 Orbital Dynamics Mode
The orbital dynamics mode gives you a display of the positions of
the spacecraft with respect to your location. If the spacecraft are
out of range, then you see time related information. If the
spacecraft are in range then you also see position related
information. The time that the spacecraft comes above your horizon
is when you acquire signals. This time is known as Acquisition of
Signals (AOS) time. You lose signals when the spacecraft drops below
your horizon. This time is known as Loss of Signals (LOS). WHATS-UP
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 18
allows you to define an early warning time (EWT) (in minutes) before
AOS. The period of time between AOS and LOS is known as the pass.
Orbit positional information is only as accurate as your PC clock
and the reference Keplerian data supplied by AMSAT and other
sources. You can expect an accuracy of within a minute or two if
your PC clock is correct. WHATS-UP only provides time displays
accurate to within a minute or two. Its not worth going for greater
accuracy in most cases.
The following information is only displayed for spacecraft in
range.
AZ Azimuth - Pointing angle to spacecraft along horizon (0 =
North, 90 = East).
EL Elevation - Pointing angle to spacecraft from horizon to
zenith.
RANGE Distance between your station and the spacecraft. An
Up arrow next to it indicates that the altitude is
increasing, a down arrow, that it is decreasing.
DPLR Doppler shift on spacecraft's beacon signal.
A typical example of part of the display is shown below.
══S/C═════WNDOW══AOS═══LOS══PASS════MA═════ALT════AZ══════EL═══RANGE
UO-11 02:05 00:08 00:19 00:11 143 681
AO-13 04:51 02:54 08:01 122 37723 47.92 24.91
=DO-17 03:32 01:35 01:45 00:10 206* 792
The first column provides information about the automatic
sequencer.
A check mark indicates that the spacecraft is the selected one for
data to be captured.
An equals sign indicates that WHATS-UP is configured to configure
itself to tune to its beacon signal and capture data at AOS for
that spacecraft.
A "less than equals" sign indicates that WHATS-UP is configured to
configure itself to tune to its beacon signal and capture data
at EWT for that spacecraft.
The display is color coded as follows.
Spacecraft out of range displayed in the default window color.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 19
Spacecraft in range are displayed in the 'in range' color.
Spacecraft within EWT are is displayed up in the EXT color. The
spacecraft designator for the next spacecraft to come in range is
displayed in the 'next one up' color. These colors may be configured
to your preference in the WHATS-UP.SYS file.
3.5 Playback Mode
The Playback mode allows you to play back captured telemetry with 4
speeds (speedy, slow, slower and snail's pace).
3.6 (Data) Extraction Mode
In this mode, data is extracted from a playback file into a file
that can be read into a spreadsheet. If you answer the prompt for
the default file with a non-existent filename, WHATS-UP will prompt
you for individual channel numbers. To terminate the sequence and
begin the extract mode, touch the 'Enter' key without entering a
channel number. Note: Start and stop times are text string matches.
3.7 Mutual Visibility Mode
This mode provides a display of the mutual visibility between a
spacecraft and all the others displayed in the window. A typical
section of a display is shown below.
===S/C=WNDOW==AOS===LOS==PASS===MA====ALT=LAT====LONG==FTPRNT=D-SSP
√MIR 00:48 22:46 22:54 00:08 66√ 395 -46.25 287.01 4378 11259
AO-10 02:42 00:39 07:09 06:29 217√ 19206 -13.89 343.58 16834 15543
AO-13 22:02 08:28 189√ 30799 -39.77 68.49 17841 7504
=AO-21 04:29 02:26 02:31 00:04 158√ 1003 -5.67 155.89 6729 2139
RS-12 00:14 22:11 22:23 00:11 245√ 963 -24.46 111.93 6608 3646
The information displayed in the mutual visibility mode window are
as listed below.
WNDOW Time till AOS (if out of range, or time till LOS if in
range.
AOS Time of AOS. This item is not displayed if the spacecraft
is in range.
LOS Time of LOS.
PASS The amount of time that the pass will last. If the
spacecraft is in range, then this item displays the
minutes remaining till LOS.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 20
MA Mean Anomaly, or position of the spacecraft in its orbit
(see Section 5).
If the spacecraft have mutual visibility, a check mark '√'
character will be displayed following the MA value.
ALT The altitude of the spacecraft above sea level. An Up
arrow next to it indicates that the altitude is
increasing, a down arrow, that it is decreasing.
LAT The latitude of the point on the surface directly below
the spacecraft (sub-satellite point).
LONG The longitude of the point on the surface directly below
the spacecraft (sub-satellite point).
FTPRINT The diameter of the footprint of the satellite on the
surface of the earth.
D-SSP The distance between the sub-satellite point of the
satellite and the one for which mutual visibility has been
calculated.
This mode is useful if you want to determine the possibility of a
double hop communications link through two spacecraft, or want to
see when Mir can work the Space Shuttle.
3.8 Audio Warnings and Orbit Data Displays
WHATS-UP provides audible warnings in morse code of AOS, LOS and
EWT. Each warning consists of a letter followed by the spacecraft
designator. An 'A' prefixes AOS, an 'L' prefixes LOS and a 'Q'
prefixes EWT.
WHATS-UP also shows orbit data associated with the selected
spacecraft in the bottom window. This data which duplicates the line
shown in the orbital mode, is there to be used in the real-time and
interactive modes.
3.9 Autotrack
An autotrack flag is present in each spacecraft configuration file.
The autotrack flag allows you to customize the way WHATS-UP switches
radio frequencies and TNC modes. If the autotrack is disabled,
WHATS-UP will not switch until after LOS of the satellite currently
tracking. If the autotrack flag is enabled, WHATS-UP will switch
radio frequency and TNC mode when a new spacecraft is present even
if it is currently tracking one. You use the autotrack flag to stop
WHATS-UP from switching away from a satellite in the middle of a
pass if a new one comes up over the horizon.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 21
If the autotrack flag a disabled, a flashing indicator will be seen
next to the spacecraft name in the status window.
WARNING
If you disable the autotrack flag in the default configuration file,
or manually load a spacecraft configuration file with the autotrack
disabled, WHATS-UP will not change radio frequencies or TNC modes
until the next LOS.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 22
4.0 Menus
WHATS-UP provides various features organized in a hierarchy of
menus. To bring up the top menu, touch the 'Esc' key.
4.1 Function Keys
The following function keys are active in the operational modes
described in Section 3:
FK 1 Capture to disk Toggle
FK 2 Type of display Engineering Units/Raw Byte Toggle
FK 3 Select display page
FK 4 Change doppler frequency display
FK 5 Display packet Monitor Heard (MH) list
Alt-B Send a 'Break' to the TNC Alt-C Connect to another
packet station
Alt-D Disconnect from another packet station
Alt-F Flush receiver buffer
Alt-I Autotrack toggle
Alt-J Jump to DOS (shell)
Alt-P Printer on/off toggle
Alt-S Sound on/off toggle
Alt-X Quit Mode
Alt += Debug toggle
left arrow Decreases playback speed
right arrow Increases playback speed.
4.1.1 FK 1 Capture to disk Toggle
This function key turns the capture-to-disk ON if it is off, and
turns it OFF if it is on.
4.1.2 FK 2 Type of display Engineering Units/Raw Byte Toggle
This function key changes the real-time, playback telemetry display
between raw data and decoded engineering units.
4.1.3 FK 3 Select display page
This function key allows you to select a different customized data
display page.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 23
4.1.4 FK 4 Change Doppler frequency display
This function key allows you to change the Doppler frequency
display between the computed receive frequency and the difference
between the satellite beacon frequency and the computed receive
frequency.
4.1.5 FK 5 Display MH list
This function key configures WHATS-UP into the Interactive mode and
sends a "MH" command to the TNC.
4.1.6 Alt-B send a 'Break' to the TNC
This function key allows you to send a "break" character to the
TNC. You use it if you accidentally put the TNC in the transparent
mode.
4.1.7 Alt-C connect to another packet station
This function key prompts you to enter a callsign, then, if you are
in the packet communications mode, attempts to connect you to that
station.
4.1.8 Alt-D disconnect from another packet station
This function key allows you to disconnect a packet mode
connection.
4.1.9 Alt-F flush receiver buffer
This function key allows you to flush the receive buffer.
4.1.10 Alt-I autotrack toggle
This function key allows you to enable or disable the autotrack
feature. You use this key to override the default value in the
spacecraft configuration file.
4.1.11 Alt-J jump to DOS (shell)
This function key lets you jump into DOS for a while without
exiting from WHATS-UP.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 24
4.1.12 Alt-P Printer on/off toggle
This function key lets you turn the printer on and off. If the
printer is turned on, any incoming raw data will be echoed to the
printer as well as to the screen.
4.1.13 Alt-S Sound on/off toggle
This function key lets you turn the sound on and off.
4.1.14 Alt-X Quit
This function key quits the mode and allows you to terminate WHATS-
UP and return to DOS.
4.1.15 Alt += debug toggle
This function key lets you enable and disable the Debug Menu. If
the debug menu is enabled, an '*' will be displayed on the left hand
side of the status window.
4.1.16 left arrow decreases playback speed
This function key decreases playback speed in the Playback mode.
4.1.17 right arrow increases playback speed.
This function key increases playback speed in the Playback mode.
4.1.18 Up arrow steps parallel port radio memory up
This function key steps the parallel port radio memory up on
channel.
4.1.19 Down arrow steps parallel port radio memory up
This function key steps the parallel port radio memory up on
channel.
4.2 Selections Menu
This menu presents you with the following typical options.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 25
C Change Display Page
E Edit Menu
F Files Menu
H Help Menu
J Jump to DOS
L Log Menu
M Modes Menu
O Orbits Menu
R Radio Menu
S Spacecraft Menu
T PK232 Menu
U Utilities Menu
W CW Menu
X Exit to DOS
Z SAREX Menu
4.2.1 Change Display Page
This option allows you to change the display page for the Real-
time, Playback and Extraction Modes. It performs the same operation
as Function key 3 (F3) when those modes are active.
4.2.2 Edit Menu
This option brings up the Edit Menu.
4.2.3 Files Menu
This option brings up the Files Menu.
4.2.4 Help Menu
This option displays help information for the function keys.
4.2.5 Jump to DOS
This option allows you to jump into a DOS Shell. You return to
WHATS-UP by typing the DOS command 'EXIT'.
4.2.6 Modes Menu
This option brings up the Modes Menu.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 26
4.2.7 Log Menu
This option brings up the Log Menu.
4.2.8 Orbits Menu
This option brings up the Orbits Menu. This option is only
available if an orbit element file (*.AMS or *.TLE) is present.
4.2.9 Radio Menu
This option brings up the Radio Menu if a Kenwood Radio is present
and the interface is operational.
4.2.10 Spacecraft Menu
This option brings up the Spacecraft Menu.
4.2.11 TNC or PK232 Menu
This option brings up the TNC Menu.
4.2.12 Utilities Menu
This option brings up the Utilities Menu.
4.2.13 CW Menu
This option brings up the CW Menu.
4.2.14 Exit to DOS
This option allows you to terminate WHATS-UP and return to DOS.
4.2.15 SAREX Menu
This option brings up the SAREX Menu.
4.3 Modes Menu
When you bring up the Modes menu you will be prompted with the
following options.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 27
E Extract From Playback File
I Interactive Mode
O Orbital Parameters
M Mutual Visibility
P Playback Mode
R Real Time Mode
Type the letter associated with the option to perform it.
Each of the options are described below.
4.3.1 Extract From Playback File
This option activates the Extraction mode.
4.3.2 Interactive Mode
This option activates the Interactive mode.
4.3.3 Orbital Parameters
This option activates the Orbital mode. This option is only active
if Keplerian data files are in the defined directory path.
4.3.4 Mutual Visibility
This option activates the Mutual Visibility mode.
4.3.5 Playback Mode
This option activates the Playback mode.
4.3.6 Real Time Mode
This option activates the Real-time mode.
4.4 Edit Menu
WHATS-UP contains an ASCII text editor suitable for files less than
64k in size. It is built based on Borland's Turbo Pascal Editor
Toolbox and the commands are compatible with Sidekick and Wordstar.
A summary of the editor commands is shown below.
F10 Switch Windows (if more than one window open)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 28
Backspace Delete left char
Del Delete Char
Enter New line
Ins Toggle insert mode
PgUp Move cursor up one page
PgDn Move cursor down one page
^A Move cursor left one word
^C Move cursor down one page
^D Move cursor right one character
^E Move cursor up one line
^F Move cursor right one word
^G Delete one character
^H Delete left one character
^I Tab
^L Find/replace next occurrence
^P Insert a control character into the text
^M New line
^N Insert line
^R Move cursor up one page
^S Move cursor left one character
^T Delete one word after cursor ^V Toggle insert mode
^W Scroll up
^X Move cursor down one line
^Y Delete line at cursor
^Z Scroll down
^K^B Mark beginning of block
^K^C Copy block to position of cursor
^K^D Save file and exit edit ^K^H Hide block marker
^K^K Mark end of block
^K^Q Abandon file and exit edit
^K^R Read file into screen
^K^T Mark single word as block
^K^V Move block to position of cursor
^K^W Write block to disk file
^K^Y Delete block
^K 1..9 Set marker 1 .. 9
^Q^A Find text and replace
^Q^B Move to beginning of block
^Q^C Move to end of file
^Q^D Move to right of line
^Q^E Move to top of window
^Q^F Find text
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 29
^Q^I Toggle autoindent mode
^Q^K Move to end of block
^Q^R Move to top of file
^Q^S Move to left of line
^Q^X Move to bottom of window
^Q^Y Delete to end of line
^Q 1..9 Jump to marker 1..9
The following options can be set in the Find/Find and Replace (^Qf
and ^Qa) operations.
# locates #th occurrence
G global replace
N replace without Y/N question
U ignore upper case/lower case
W match whole words only
Notes
1 The ^ key in front of a character identifies the character as a
'control' character. To activate it, hold down the Control key
AND the character key.
2 Some of the commands require two keystrokes.
3 Use ^P to embed a control character in the text. For example, if
you are creating a file containing commands to be sent to the
TNC, to enter a control-C character into the file, use the ^P^C
sequence of keystrokes.
WHILE USING THE EDITOR, WHATS-UP can't receive and process
characters from the TNC. All other features ARE INHIBITED OR LOCKED
OUT.
The Edit menu allows you to call up the various files for editing
as shown by this typical display.
D DOVE.DOP
F Any File
K WHATS-UP.TLE
M c:dove.CNF
P Pick ***.D17 File
R c:910313.D17
S WHATS-UP.SYS
T Two Files
W Arrays
X whats-up.txt
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 30
Y Pick ***.CNF File
Z Today's Data
Type the letter corresponding to your choice.
4.4.1 Edit Doppler File
This option lets you edit the file containing Doppler measurements.
4.4.2 Any File
This option lets you edit any file.
4.4.3 Edit Keplerian Element File
This option lets you edit the default file containing Keplerian
data.
4.4.4 Edit Spacecraft Configuration File
This option lets you edit the file containing the spacecraft
configuration data, such as display pages, and automatic radio
tuning options.
4.4.5 Pick Capture-to-disk File
This option lets you pick a capture-to-disk file to be edited. When
you implement this option you will be presented with a list of
available files. Move the cursor down to the desired file and push
the 'Enter' key.
4.4.6 Edit Capture-to-disk File
This option lets you edit the file containing data captured during
the last pass.
4.4.7 Edit WHATS-UP.SYS
This option lets you edit the WHATS-UP.SYS file.
4.4.8 Two Files
This option lets you edit any two files.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 31
4.4.9 Edit Doppler Channel File
This option lets you edit the file containing the channel numbers
of the data to be extracted from the raw telemetry, processed and
written to disk.
4.4.10 Edit Doppler Data File
This option lets you edit the file containing extracted data.
4.4.11 Pick Spacecraft Configuration File
This option lets you pick a spacecraft configuration file to be
edited. When you implement this option you will be presented with a
list of available files. Move the cursor down to the desired file
and push the 'Enter' key.
4.4.12 Edit Today's Data
This option lets you edit a file containing data captured today.
You will be prompted for the particular spacecraft.
4.5 Files Menu
This menu presents you with the following typical options.
A Change Directory Path
F Change Playback File
S Show Data Files
V View Playback File
Z Show *.D17 Files
1 Show Files for 1 Spacecraft
4.5.1 Change Directory Path
This option allows you to temporarily change the directory path to
the capture-to-disk files.
4.5.2 Change Playback File
This option allows you to change the playback file. To select a
file, move the cursor down to the desired file and push the 'Enter'
key. If you have more files than fit in the window, touch the 'PgDn'
key to display another window full.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 32
4.5.3 View Playback File
This option allows you to view the contents of the playback file.
4.5.4 Show Spacecraft Capture-to-disk Files
This option shows you the names of the capture-to-disk files for
the chosen spacecraft in the default directory path.
4.5.5 Show Data Files
This option shows you the names of ALL the capture-to-disk files in
the default directory path.
4.5.6 Show Files for 1 Spacecraft
This option shows you the names of the capture-to-disk files for a
particular chosen spacecraft in the default directory path. It will
prompt you for the filetype associated with the spacecraft (e.g.
O23, D17).
4.6 Orbits Menu
This menu presents you with the following typical options.
A Pick AMSAT Format Element Set
E Edit WHATS-UP.TLE
L Load Element File
M Set Ref S/C (Mutual Visibility)
N Pick NASA 2 Line Element Set
P Show next pass
S Set Ref = Sun (Mutual Visibility)
V View Spacecraft Orbit Elements
Z Show/hide Sun Data
4.6.1 Pick AMSAT Format Element Set
This option allows you to change the AMSAT Format Keplerian Element
file. To select a file, move the cursor down to the desired file and
push the 'Enter' key. If you have more files than fit in the window,
touch the 'PgDn' key to display another window full.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 33
4.6.2 Edit Default Keplerian Element File
This option lets you edit the default file containing Keplerian
data.
4.6.3 Load Element File
This option loads the data in the element file into WHATS-UP. When
you activate the option you will be prompted as follows.
Which Element File ? WHATS-UP.TLE
WHATS-UP will supply the default name, you may overwrite it to
supply the name of another file. You use this option to load a file
that is not located in the default directory.
4.6.4 Set Ref S/C (Mutual Visibility)
This option lets you set the spacecraft for which mutual visibility
will be calculated (in the mutual visibility mode). The default is
the Sun. To select a spacecraft, move the cursor down to the desired
name and push the 'Enter' key. If you have more spacecraft than fit
in the window, touch the 'PgDn' key to display another window full.
4.6.5 Pick NASA 2 Line Element Set
This option allows you to change the 2 Line Format Keplerian
Element file. To select a file, move the cursor down to the desired
file and push the 'Enter' key. If you have more files than fit in
the window, touch the 'PgDn' key to display another window full.
4.6.6 Show next pass
This option allows you to view the future passes of a spacecraft.
When you activate this option, you will be presented with a menu
window containing a list of spacecraft designators. Move the cursor
to the one of interest and touch the 'Enter' key to select it.
An * will be shown next to the MA column, if the spacecraft will be
in sunlight at the time. A + will be shown if the spacecraft will be
visible. Touch the space key to view a subsequent pass, touch the
'Esc' key to return to the spacecraft choice menu.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 34
4.6.7 Set Ref = Sun (Mutual Visibility)
This option lets you reset the Sun as the spacecraft for which
mutual visibility will be calculated (in the mutual visibility
mode).
4.6.8 View Spacecraft Orbit Elements
This option lets you view the data associated with the spacecraft.
When you activate this option, you will be presented with a menu
window containing a list of spacecraft designators. Move the cursor
to the one of interest and touch the 'Enter' key to select it.
If the default element file is in AMSAT format (*.AMS) the two line
display is not shown.
A typical display is shown below :-
1 20440U 90 5 E 91059.65616971 .00001077 00000-0 44042-3 0 2017
2 20440 98.6806 140.0431 0012003 123.1299 237.1040 14.29083383 57498
Catalog ID: 20440 Apogee: 803.312
Element Set: 201 Perigee: 786.093
Epoch Year: 1991 Period: 100.76
Epoch Day: 59.6561697 Semi Major Axis: 7172.862
Drag: 0.00001070
Inclination: 98.6806 Epoch Age: 22.263
RAAN: 140.0431 Current Date: 81.919
Eccentricity: 0.0012003 Current Orbit #: 6067
Argument of Perigee: 123.1299
Mean Anomaly: 237.1040
Mean Motion: 14.2908338
Epoch Orbit #: 5749
4.6.9 Show/hide Sun Data
This option allows you to display the position of the Sun in the
last row of the orbit display window. It will replace any spacecraft
in that position. The option as an on/off toggle, i.e. push once to
turn on the display, push again to turn it off.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 35
4.7 Radio Menu
This menu is only present if you have a Kenwood Radio defined as
your Radio Receiver for the spacecraft or are using the printer
port. The Radio menu presents you with the following typical
options.
D Turn Doppler Tracking ON
F Set New Frequency
I Change Doppler Interval
M Set Radio Modulation
R Read VFO A Frequency
S Set Default Frequency
V Select VFO A/B
The Radio printer port menu presents you with the following typical
options.
C Set Current Radio Memory
D Step Radio Memory Down
E Set Radio Memory Scan Delay
K Set Scan Radio Memory ON
M Select Radio Memory
U Step Radio Memory Up
The following options are valid for a Radio.
4.7.1 Turn Doppler Tracking ON/OFF
This option lets you turn the Doppler tracking on and off.
4.7.2 Set New Frequency
This option lets you set a new (default) frequency into the radio
and tune to it.
4.7.3 Change Doppler Interval
This option lets you change the time interval (in minutes) between
successive samples of the radio VFO frequency.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 36
4.7.4 Set Radio Modulation
This option lets you change the modulation mode in the radio.
Options are FM, USB, LSB and CW.
4.7.5 Read VFO A Frequency
This option lets you read back the frequency that VFO A is tuned
to, and displays it in the status window.
4.7.6 Set Default Frequency
This option lets you set the radio back to the default frequency
and tune to it.
4.7.7 Select VFO A/B
This option lets you select between the two VFOs in the radio and
tune to it.
4.7.8 Spare - Not used
4.7.9 Spare - Not used
WARNING
There is no way for WHATS-UP to read back the memory positions from
the radio. WHATS-UP consequently assumes synchronization.
4.7.10 Set Current Radio Memory
This option lets you set the radio memory number into WHATS-UP to
synchronize the radio to the software. Set this to the same number
as the memory channel of the radio.
4.7.11 Step Radio Memory Down
This option lets you set the radio memory down one position.
4.7.12 Set Radio Memory Scan Delay
This option lets you change the dwell time the radio waits on each
channel when scanning through WHATS-UP.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 37
4.7.13 Set Scan Radio Memory ON/OFF
This option lets you start and stop scanning through the radio
memories using WHATS-UP to control the scan. When the scan is turned
off, you will be prompted to synchronize the channels (in case of a
slippage). If WHATS-UP is in the scanning mode when a satellite pass
occurs, WHATS-UP will select the appropriate memory channel and
remain on that channel until the pass is over. At that time, it will
resume scanning.
4.7.14 Select Radio Memory
This option lets you step to a memory. You will be prompted to for
the memory number. Once the memory is reached, you will be prompted
for a new number. Enter 0 to remain at the current position.
4.7.15 Step Radio Memory Up
This option lets you set the radio memory up one position.
4.8 Spacecraft Menu
This menu presents you with the following options.
C Show DOVE.CNF
D Default Spacecraft
K picK Spacecraft
M Change Spacecraft
P Pick Ops. Schedule
S Show Ops. Schedule
4.8.1 Show Spacecraft Configuration File
This option allows you to display the spacecraft configuration file
default settings.
4.8.2 Default Spacecraft
This option allows you to override the default spacecraft. WHATS-UP
will select this one when the current pass is over.
4.8.3 picK Spacecraft
This option allows you to choose another spacecraft from a list. To
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 38
select one, move the cursor down to the desired one and touch the
'Enter' key. For example, amongst the default files supplied are
DOVE.CNF and FUJI.CNF. To select the DOVE or the Fuji-20 spacecraft,
move the cursor down to the 'DOVE.CNF' or 'Fuji.CNF' line and touch
the 'Enter' key.
4.8.4 Change Spacecraft
This option allows you to choose another spacecraft. To select a
another one, enter the name of the spacecraft.sys file. For example,
amongst the default files supplied are DOVE.CNF and FUJI.CNF. To
select the DOVE or the Fuji-20 spacecraft, type 'DOVE' or 'Fuji'
4.8.5 Pick Ops. Schedule
This option allows you to pick an operations schedule. (A file with
the default extension of "OPS".) You would use it to look at the
schedule for a spacecraft other than the one currently selected.
4.8.6 Show Ops. Schedule
This option allows you to look at the schedule the spacecraft
currently selected.
4.9 TNC Menu
This menu presents you with the following typical options. The
actual ones will depend on which TNC you have.
A UoSAT ASCII Beacon
B Phase 3 RTTY Beacon
C Set Morse Code (CW)
M Fuji/MicroSat ASCII Packet
O Select AO-13 PSK
P 1200 Baud FM Packet
R Select MFJ 1278 Radio Port
S SARA ASCII Beacon
T Configure PK232
U 9600 Baud Packet
If you select an option that your TNC cannot perform, you will get
an error message.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 39
4.9.1 UoSAT ASCII Beacon
This option will configure the PK-232 to copy the UoSAT-2
telemetry. Note: you require a hardware change in the PK-232 to make
sense of the received data (Section 7.2). You should not use WHATS-
UP to capture AMSAT/UoSAT binary telemetry because WHATS-UP filters
the ^J and ^M (carriage return and line feed characters) from the
incoming datastream.
4.9.2 Phase 3 RTTY Beacon
This option will configure the Multi mode TNC to copy the UoSAT-
OSCAR 13 Baudot Beacon.
4.9.3 Set Morse Code (CW)
This option will configure the Multi mode TNC to copy morse code.
You use this if you want to copy morse code telemetry. Note the
decoding formats are not provided in this program, so you will have
to decode the telemetry in some other way, such as by hand or by
means of a spreadsheet.
4.9.4 Fuji/MicroSat ASCII Packet
This option will configure the Multi mode TNC to copy the Fuji
ASCII format PACKET telemetry. You should not use WHATS-UP to
capture AMSAT/UoSAT binary telemetry because WHATS-UP filters the ^J
and ^M (carriage return and line feed characters) from the incoming
datastream.
4.9.4 Configure TNC
This option configures the TNC to copy the UI packets transmitted
by the Packet spacecraft or any other configuration defined by the
parameters at the end of the *.CNF file.
4.9.5 FM Packet
This option will configure the Multi mode TNC to copy the DOVE
ASCII format PACKET telemetry. You should not use WHATS-UP to
capture AMSAT/UoSAT binary telemetry because WHATS-UP filters the ^J
and ^M (carriage return and line feed characters) from the incoming
datastream.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 40
4.9.6 SARA ASCII Beacon
This option will configure the PK-232 to copy the SARA ASCII format
300 baud binary telemetry. The option is left in WHATS-UP for
possible future use.
4.9.6 Select MFJ-1278 Radio Port (if TNC is an MFJ 1278)
This option lets you change the MFJ Radio port. WHATS-UP doesn't
change it at any other time.
4.9.7 Select AO-13 PSK (if TNC is a DSP-2232)
This option lets you select 400 baud PSK demodulation.
4.9.8 Select 9600 Baud Packet (if TNC is a DSP-2232 or PK-900)
This option lets you select 9600 baud FM packet demodulation.
4.10 Utilities Menu
This menu presents you with the following typical options.
A Change Directory Path
D Show Space on Disk
E Enable/Disable RS-232 Port to TNC
M Turn MET Window ON/OFF
R Reset Header Counters
S Show Defaults
Z Show Files
* Show Color Chart
! Reconfigure WHATS-UP
4.10.1 Change Directory Path
This option allows you to temporarily change the directory path to
the spacecraft capture-to-disk, configuration and schedule files.
4.10.2 Enable/Disable RS-232 Port
This option allows you to temporarily enable or disable the serial
port to the TNC. This feature is for the time you want to use WHATS-
UP in the Orbit Dynamics mode and another program to access the TNC.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 41
4.10.3 Enable/Disable TNC Port
This option lets you enable and disable the PC serial port to the
TNC. Use it to stop WHATS-UP taking control of the port in multi-
tasking environments, so you can run LAN-LINK in one window, and the
Orbit Dynamics display of WHATS-UP in another.
4.10.4 Turn MET Window ON/OFF
This option allows you to temporarily enable or disable the
(Mission Elapsed Time) MET display. The default MET value for each
spacecraft is stored in the spacecraft.CNF file. When you activate
the display you will be prompted to enter the time. Push the 'Enter'
key to accept the default, overwrite the default with any value in
the format YYYY:MM:DD:HH:mm:ss. For example, 06:38:00 on March 2,
1995 is 1995:03:02:06:38:00.
If you enter a '0' the timer will start from 0.
Use the MET counter to display the launch time for a SAREX mission,
or the last memory load time for DO-17 and other microsats.
4.10.5 Show Space on Disk
This option allows you to see how much space is left on a disk with
exiting from the program.
4.10.6 Reset Header Counters
This option applies to spacecraft transmitting packetized
telemetry. When activated, the option resets the packet counters to
zero. Use this before a pass to see how many packets of each type
are received during the pass.
4.10.7 Show Defaults
This option allows you to display the WHATS-UP default settings.
4.10.8 Show Files
This option lets you display the files in the default directory
path. Use this if WHATS-UP tells you that a file does not exist and
you are sure that it does.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 42
4.10.9 Show Color Chart
This option allows you to display the color combinations. Use this
to see what how the different color combinations appear on your
screen, note the numbers associated with each color, then exit from
the program and edit the WHATS-UP.SYS file using your editor in its
ASCII (non document)mode to change the colors to those you desire.
4.10.10 Reconfigure WHATS-UP
This option reloads the configurations from the WHATS-UP.SYS file.
Use it after editing the file to see the effect of your changes.
4.11 Debug Menu
This menu is only active when the debug flag is enabled (Alt +=
key). The menu presents you with the following typical options.
C Sound CW String
D Turn Debug OFF
F Set Frequency
I Interrogate Radio
S Show Defaults
T Command Radio
V Speak Frequency
W Identify Radio
4.11.1 CW Tone Test
This option asks you to enter some characters at the keyboard. When
you do so, it then sounds them off in morse code. You use this
option to adjust the speed of the morse code used in the AOS, LOS
and EWT warning signals.
4.11.2 Turn Debug OFF
This option lets you turn the debug flag off.
4.11.3 Set Frequency
This option lets you enter a frequency into the selected VFO.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 43
4.11.4 Interrogate Radio
This option lets you enter a manual command into the radio and see
the reply returned by the radio.
4.11.5 Show Defaults
This option allows you to display the WHATS-UP default settings.
4.11.6 Command Radio
This option lets you enter a manual command into the radio.
4.11.7 Speak Frequency
This option commands the voice module in the radio to announce the
frequency on which it is tuned.
4.11.8 Identify Radio
This option lets you enter the 'identify' command into the radio
and see the reply returned by the radio.
4.12 Log Menu
WHATS-UP automatic logging Packet mode Connects, and satellite
Acquisitions. The Log files are in dBASE 3 format and can be
processed by the LAN-LINK and DBASE Log book Package in PC-HAM for
indexed listings, tracking of DXCC and other AWARDS, etc. This is
ideal for special event stations and DX-peditions, for the whole QSL
process and further statistical analyses of their operation. The
structure of the logbook files are as shown below.
Field Field Name Type Length
1 DATE Character 8
2 TIME Character 4
3 BAND Character 3
4 CALL Character 10
5 RX Character 3
6 TX Character 3
7 MODE Character 4
8 POWER Character 4
9 QSLSENT Character 1
10 QSLRX Character 1
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 44
11 COMMENTS Character 20
The size of the COMMENTS field is a compromise. Each field is a
fixed size so that each log entry takes up a minimum of 62
characters worth of space on the disk even if all the character
space is unused. You may change the size of the field if you wish,
but to do that you will have to use dBASE. Note also, that if you do
make the comments field longer, the display will be screwed up.
For the logging feature to work, the logbook files must be present
on the disk. You may create a logbook by accessing the Log menu.
When you bring up the Logbook you will be shown the last screen or
page of log entries. The last entry will be highlighted. At this
time a number of function keys can be used, or you may depress the
"Escape" key to bring up the Log Help Menu. The following functions
are available.
A Append Entry
E Edit Log Entry
H Scan for Log Entry
L Pack Logbook
S Scan for Call
U Toggle Delete Mark
X eXit Log Menu
Ins Toggle Insert Mode
End Show Last Page
Home Show First Page
PgUp Page Up
PgDn Page Down
Up One Entry
Down One Entry
4.12.1 Alt-A Append Entry
This function key allows you to manually append an entry to the
log. You can also use this command to enter the odd SSB contact into
the logbook file. If you do, use the characters "SSB" or "FM" for
those voice modes to remain compatible with the rest of the DBASE
logbook package.
When appending or editing an entry, LAN-LINK will automatically
enter the date, time, callsign of the other station, band, mode and
QSL information in upper case.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 45
The comments field in the LAN-LINK logbook file is restricted to a
maximum of 20 characters. If you try and enter more than 20, the
surplus will be ignored.
4.12.2 Alt-E Edit Log Entry
This function key allows you to edit the highlighted entry. Move
the cursor with the arrow keys, and end the edit process by
depressing the "Escape" key. You may use the "QSL" entry to tag the
fact that you have written out or received a QSL card.
4.12.3 Alt-H Scan Log by Call
This function key allows you to scan the logbook by callsign prefix
for the callsign in the highlighted entry in the logbook. This
command displays the contents of the logbook file in a formatted
manner on the screen. It requests the callsign of the log entry to
be displayed. If you want to see entries for particular callsigns or
parts of a callsign, enter those callsigns or the front parts of the
callsign. Valid entries are G, G3, G3Z etc. If you want to see every
entry in the log, don't use this command, use the Page Up and Page
Down keys from the Main Log menu.
4.12.4 Pack Logbook
This function key allows you to remove the logbook entries flagged
for deletion.
4.12.5 Alt-S Scan Log by Call
This function key allows you to scan the logbook by callsign prefix
for the callsign entered with the Alt-C or Alt-E keys. This command
displays the contents of the logbook file in a formatted manner on
the screen. It requests the callsign of the log entry to be
displayed. If you want to see entries for particular callsigns or
parts of a callsign, enter those callsigns or the front parts of the
callsign. Valid entries are G, G3, G3Z etc. If you want to see every
entry in the log, don't use this command, use the Page Up and Page
Down keys from the Main Log menu.
4.12.6 Alt-U Toggle Delete Mark
This function key allows you to mark an entry for deletion, or
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 46
unmark it in case you change your mind. Entries marked for deletion
will be flagged by an "*" character next to the record number.
4.12.7 Alt-X eXit Log
This function key lets you exit from the Logbook.
4.12.8 Ins Toggle Insert Mode
This function key allows you to turn the insert mode ON and OFF for
the edit/append functions.
4.12.9 End Show Last Page
This function key moves you to the last callsign on the last page
of the logbook.
4.12.10 Home Show First Page
This function key moves you to the first callsign on the first page
of the logbook.
4.12.11 PgUp Move Up One Page
This function key moves the display up one page of the logbook.
4.12.12 PgDn Move Down One Page
This function key moves the display down one page of the logbook.
4.12.13 Up Arrow Move Up One Entry
This function key moves the highlight up one entry in the logbook.
4.12.14 Down Arrow Move Down One Entry
This function key moves the highlight down one entry in the
logbook.
4.13 SAREX Menu
This menu is designed for use with the Shuttle Amateur Radio
Experiment (SAREX), MIR, and the packet radio Microsats, or any
terrestrial station you want to connect with as soon as they appear
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 47
on frequency.
A Set Attack Mode ON/OFF
C Set SAREX Call
M Attack Mode [QCB]
R Reset SAREX Flags
Z Turn Zap R0MIR-1 ON/OFF
0 Multiple User Connects
4.13.1 Set Attack Mode ON/OFF
If the Attack Mode is set, this option will cause WHATS-UP to issue
a connect request/beacon to the SAREX Call whenever a packet sent to
or from it is heard. The mode, is cleared when the connect is made
(and does not retry out) or when the "A" option is selected a second
time. If this mode is enabled, the Alert/SAREX Call prefix shown in
the Status Window will indicate accordingly.
A happy face will be displayed in the status window before the call
once the connect has been achieved.
Be careful using this feature, as it has the potential to cause a
great deal of QRM. It can also be cleared by another station
connecting to you and telling you to ":QRT:".
In the SAREX configuration you are listening on one channel while
transmitting on an other. If this feature is used on a simplex
channel (everyone transmits and listens on the same channel) aimed
at a DX-pedition or the MIR space station, there is a potential
lockout mode, in which any one station sending a connect request to
the desired/SAREX call will trigger the other ones on frequency who
will in turn trigger the first. If this pile up situation occurs, I
hope the DX-station will QSY and leave the automatic stations to do
their thing. IN any event, if you use this feature and cause QRM,
anyone can connect to you with the callsign of the DX station (as a
pirate) and shut you down. You will then not get the coveted DX QSL.
4.13.2 Change SAREX Call
This option lets you temporarily change the SAREX call.
4.13.3 Set Attack Mode Attack Mode [QCB]
This option allows you to configure the SAREX Attack mode to:
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 48
Q digipeat or call CQ via the SAREX station
C connect to the SAREX Callsign
B both at the same time
Use the CQ and beacon features to digipeat via MIR while attempting
a connect, and the connect alone for the Space Shuttle (SAREX). If
the Attack Mode is set, WHATS-UP will either try for a connect or
send an unproto packet containing the CQ text. If you want it to go
through the SAREX Callsign you must configure the UNPROTO parameter
in the TNC. For example, to attempt a digipeat via R2MIR, set
'UNPROTO CQ via R2MIR' from the command mode.
4.13.4 Reset SAREX Flags
This option lets you reset the SAREX Connect Status indicators in
the status window.
4.13.5 Turn Zap R0MIR-1 ON/OFF
This option turns the Zap feature ON and OFF.
4.13.6 Single/Multiple User Connects
This option configures the TNC for single or multiple users. Use
single when trying for a SAREX QSO and Multiple when beaconing
through MIR.
4.14 CW Menu
This menu provides you with a smart CW transmit terminal. The
keyboard will transmit letter, numbers and the following special
characters:
Keystroke Abbreviation Meaning
* SK End of QSO
& AS Wait
+ AR End of Message
( KN Go ahead designated station
= BT Break or pause
> AA New line
! SN Understand
% KA Attention
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 49
The following punctuation characters are supported
? IMI . AAA , MIM - DU
: OS ; KR ) KK / DN
" AF $ SX ' WG _ IQ
The CW menu presents you with the following typical options.
A Sound Text
D Set CW Speed
K Turn CW keyboard ON
N Set CW Note
S Show CW Memories
T Transmit Text
- Slow CW Down
+ Speed CW Up
1..0 Change CW Memory 1..10
WHATS-UP uses timing loops in software to produce the sounds and
key the transmitter. If you have time accessed multi-task switching
on your system, the sounds/key times will be wrong.
The menu options are as follows:
4.14.1 Sound Text
This option asks you to enter a line of text, then sounds it in
morse code. Use this option to test the audio note and speed.
4.14.2 Set CW Speed
This option allows you to change the default morse speed. The
higher the number you enter, the lower the speed. The number you
enter is the delay time of a single bit ("dot" or "space between
dots") in milliseconds.
4.14.3 Turn CW keyboard ON/OFF
This option allows you to turn the morse keyboard on and off. When
the CW keyboard is active:
the greek letter 'µ' will be seen flashing in the Status
window.
any letter or number typed at the keyboard will be output
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 50
to the parallel port keyer bit as well as to the TNC port.
4.14.4 Set CW Note
This option lets you set the audio cw tone used in the computer.
4.14.5 Show CW Memories
This option displays the contents of the CW memories as loaded from
the WHATS-UP.SYS file, or temporarily overridden by the "change
memory contents" option described in Section 4.14.9.
4.14.6 Transmit Text
This option asks you to enter a line of text, then transmits it in
morse code.
4.14.7 Slow CW Down
This option slows the CW rate by 5 milliseconds, each time it is
activated.
4.14.8 Speed CW Up
This option speeds the CW rate by 5 milliseconds, each time it is
activated.
4.14.9 Change CW Memory 1..10
When you enter a number between 1 and 9, or 0, this option asks you
to enter a line of text, and stores it in the CW memory associated
with the number. 0 is Memory number 10. The change is temporary and
will be lost when you terminate the program. For permanent changes,
edit the change into the appropriate line in the WHATS-UP.SYS file.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 51
5.0 Orbital Elements
5.1 Basics
As an object moves in space it is subject to gravity. The object
itself has mass and attracts other objects and is at the same time
attracted by the mass in the other objects. Sir Isaac Newton
formulated the law of gravity, which can be described in the
following manner.
All bodies attract each other with a force called gravitational
attraction. The strength of the mutual attraction between two bodies
is dependent on their masses, and the distance between the bodies.
In fact the closer together that the two bodies are, the greater is
the mutual attraction. Mathematically this can be expressed as the
gravitational attraction between two bodies is directly proportional
to their masses and is inversely proportional to the square of the
distance between them.
Planet Earth is an object moving in space and exerts a
gravitational force. It pulls anything close to it towards the
center of the Earth at an increasing speed. An increasing speed is
known as acceleration. The acceleration due to gravity at the
surface of the Earth is given the value of 1 Gravity (G).
5.2 Orbital Trajectories
If the Planet pulls everything towards itself, what keeps things in
orbit around it? For example, if you throw a rock up into the air,
gravity and air resistance (drag) slow it down and it falls back to
Earth. If you shoot a bullet towards the horizon it will travel much
further than the stone did, but will still fall to Earth (unless it
hits something first).
If you launch a rocket towards the horizon, the rocket will
accelerate as long as the fuel lasts. When the rocket fuel is
exhausted, the rocket will continue to travel in a straight line
until other forces alter its path. If the rocket is low enough, the
molecules of air or the atmospheric drag tends to slow it down. At
any height it will still be pulled back by gravity. The force of
gravity always acts towards the center of the Earth. On its own the
rocket will travel in a straight line. Gravity acting downwards will
curve the path of the rocket around the Earth.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 52
The force of gravity will pull the rocket away from its horizontal
path and cause it to fall in a downwards direction. Now the surface
of the Earth is also curved and also curves away in a downwards
direction. If speed of the rocket is such that the rate of descent
(due to the gravitational attraction of the Earth) is equal to the
curvature of the Earth, the rocket will always remain at the same
height , namely, it will be in a circular orbit. If the rocket does
not have enough speed it will gradually fall back to Earth, and if
it has more speed, it will tend to rise above the Earth.
If the rocket continues to burn fuel the speed of the rocket
increases and the path it takes rises away from the surface of the
Earth. When the fuel is exhausted, gravity is still there and still
slows down the rocket. As it slows down its path curves more sharply
until at its furthest point (apogee) it is traveling parallel to the
surface of the Earth. It is however traveling slower than the speed
necessary to maintain a circular orbit at that altitude and starts
to curve back towards the Earth. The force of gravity now acts in a
downward and (slightly) forward direction and speeds up the rocket
until at its lowest point (perigee) it once again is traveling
parallel to the surface of the Earth but now has enough speed to
rise away the surface. This process repeats each time around and
produces an elliptical orbit.(In this orbit, the center of the Earth
is one focus of the ellipse.
To place a satellite into an orbit, it must be given the right
amount of speed for the desired orbital altitude so that the orbital
velocity at apogee is such that it just balances the gravitational
pull of the Earth. Since the force of gravity decreases with
altitude, the orbital velocity is also different at different
altitudes. Any rocket can lift a small mass to a much higher
altitude than it can lift a large mass. How much and how high will
depend on the rocket itself.
5.3 Types of orbits
Different orbits are used for different purposes. Circular and
elliptical orbits come in various forms depending on the angle that
the plane of the orbit makes with the equator of the Earth. This
angle is known as the angle of inclination of the orbit (with
respect to the equator). A polar orbit has an angle of inclination
such that the spacecraft in that orbit can see the polar regions of
the Earth. A geostationary orbit is one which has an angle of
inclination parallel to the equator and an altitude of 22,240 miles
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 53
(35,790 km) and the spacecraft moves in its orbit at the same speed
as a point on the surface of the Earth below it. The spacecraft thus
appears to be stationary with respect to the Earth below it.
The direction in which the satellite moves around the Earth
determines the type of orbit. One which travels along its orbit in
the same direction as the rotation of the Earth (eastwards) is said
to be in a direct or prograde orbit. One which travels against the
rotation of the Earth (westwards) is said to be in a retrograde
orbit.
The movement of an object in space can be described mathematically.
In the early 17th century, the only known objects in space were the
Sun, the Moon, the Planets, a few comets and the stars. It was then
that Johannes Kepler formulated three laws that first described the
movement of the Planets about the Sun.
5.3.1 Kepler's Laws
Kepler's Laws are stated in the following paragraphs.
1. Each Planet revolves about the Sun in an orbit that forms a
circumference of an ellipse with the Sun at one focus of the
ellipse.
2. The line from the center of the Sun to the center of the Planet
(called the radius vector) sweeps out equal areas in equal
periods of time as the Planet travels along the circumference of
the ellipse.
3. The square of the time taken for a Planet to travel around the
circumference of the ellipse (period of revolution of the orbit
of a Planet) is proportional to the cube of the mean distance of
the Planet from the Sun.
In the first law, the focus within the Sun is actually at the
center of mass of the Earth-Sun system and not at the center of the
Sun.
5.4 Orbital Elements
The position of an object in space can be expressed in terms of its
relationship with other bodies. Each orbit can be described in terms
of a number of parameters which supply enough information to
accurately locate the satellite. Six basic parameters are used to
describe the position of a satellite in an elliptical orbit are
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 54
described in the following paragraphs. They are Angle of
inclination, Right Ascension of Ascending Node (RAAN), Eccentricity,
Semimajor Axis, Argument of Perigee and Epoch time of Ascending
Node.
Consider each one in turn.
5.4.1 Angle of Inclination
The angle of inclination of an orbit is the angle between the plane
of the orbit and the equator of the Earth. A satellite moving in a
direct orbit has an angle of inclination between 0 and 90 degrees,
one moving in a retrograde orbit has an angle of inclination of
between 90 and 180 degrees.
The maximum northern and southern latitudes reached by a satellite
are equal to the angle of inclination of its orbit.
5.4.2 Right Ascension of Ascending Node (RAAN)
While the spacecraft is moving around the Earth, the Earth is at
the same time rotating on its own axis, and is itself traveling in
an orbit about the Sun. The Right Ascension of Node is needed as a
fixed reference point in the sky.
Astronomers use the term celestial sphere to describe the sky for
two reasons. First, from where we are standing on the surface of the
Earth, the sky seems to be painted on the inside surface of a sphere
(with the stars in fixed positions on the sphere). Second, have you
ever known scientists to use a short commonly used word when they
can use long ones?
The orbital plane of a spacecraft intersects the equatorial plane
of the Earth in two places (one on each side of the globe). A line
drawn between these two points and continued out to the celestial
sphere is called the line of nodes. The two points on the line of
nodes where the planes intersect are called the point of nodes. Most
globes (and maps) show the north pole upwards. When the spacecraft
crosses the equatorial plane (passes above the equator) going
northward it is ascending from south to north and that node point is
known as the ascending node. Conversely when the satellite continues
on its way and travels half way around the world it crosses the
other node on the equatorial plane descending to the southern
hemisphere. This second node is called the descending node.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 55
The Earth is in an inclined orbit around the Sun, just like a
satellite is in orbit around the Earth. The Earth has an ascending
and descending node around the Sun, in a similar manner to a
spacecraft in orbit around the Earth. The orbital plane of the Earth
is known as the Ecliptic. The direction in space from the center of
the Earth through the intersection of the ecliptic and the Earth's
equatorial plane out to the celestial sphere is called the vernal
equinox or the First Point of Aries because it points to the
constellation of Aries (which is so far away that (for all practical
purposes) it is in fixed direction).
The angle between the line of nodes for the ascending node of the
orbit of the spacecraft continued out to the celestial sphere and
the vernal equinox when measured in an easterly (right as opposed to
westerly/left) direction along the earth's equator is defined as the
Right Ascension of the Ascending Node (RAAN).
5.4.3 Eccentricity and Semimajor Axis
In a circle, the radius of the circumference is constant. This
means that an object traveling along the circumference is always at
a constant distance from the center or focus of the circle. The
general shape of an orbit is an ellipse. Unlike a circle, an ellipse
has two focal points. The distance between each of the focal points
of the ellipse and an object on the circumference is constant. A
line through the two focal points and the circumference is called
the Semimajor Axis. The longest line perpendicular (at 90 degrees
to) the semimajor axis passing through the circumference of the
ellipse is called the Semiminor Axis.
The mathematical term describing the overall shape of an ellipse is
called Eccentricity. When the eccentricity of an ellipse is 0 the
length of the semimajor axis is equal to the length of the semiminor
axis and the shape being described is a circle. A value of
eccentricity greater than 0 means that there is a difference between
the lengths of the axes and the shape of the ellipse flattens out.
Eccentricity describes the shape of the orbit and the length of the
semimajor axis describes the size of the orbit. If these two
parameters are known, the apogee and perigee values for the orbit
can be calculated.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 56
5.4.4 Decay Rate
The Earth has an atmosphere. It is dense at ground level and thins
out with increasing altitude. The Earth's gravity attracts the
molecules of gas in the atmosphere and stops them from escaping. As
the satellite travels along its elliptical orbit around the Earth,
its altitude changes. When it is close to perigee, it bumps into
molecules of air. The lower it gets the greater the drag on it by
the air. When the orbital radius decreases as a result of drag, the
potential energy of the spacecraft also decreases as it comes closer
to the earth. This decrease in potential energy reappears in the
form of heat energy imparted to the atmosphere and to the skin of
the spacecraft, and in an increase of the kinetic energy of the
spacecraft. It is this latter that causes the velocity of the
spacecraft to speed up.
The rate of change of speed through the atmosphere at the perigee
pass will depend on the type of orbit and on the altitude of the
perigee point. In general, satellites with low perigee points will
be more affected than satellites with higher perigee points. The
effect of this over the long term is to lower the apogee point. Over
the long term, the satellite tends to spend more time in the denser
parts of the atmosphere which then tends to circularize the orbit
(at the perigee) at which point the air drag acts continuously on
the spacecraft and the orbit disintegrates. The rate of change of
the orbit measured at a particular epoch is called the decay rate.
5.4.5 Argument of Perigee
A line drawn between the perigee of an elliptical orbit and the
center of the Earth is called the line of perigee. This line also
passes through the apogee and is the semimajor axis of the orbit.
The angle between the line of perigee and the line of nodes is
called the argument of perigee. It is a measurement of the angular
distance between them and is measured in the ascending direction
from the line of nodes. The argument of perigee thus establishes the
position of the ellipse itself within the orbital plane.
5.4.6 Epoch Time (of Ascending Node) and Revolution Number
The Epoch time is a time when the satellite crosses its perigee
point. This time is given as a Julian date, and is the reference
time for when the orbital elements are valid. The Epoch Revolution
or orbit number is the orbit number (since first perigee crossing)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 57
for which the element set is valid.
5.4.7 The Mean Motion
The mean motion a satellite is a measurement of the number of
orbits completed in a day. It is equal to twice the value of PI
divided by the time that the spacecraft takes to complete one
revolution of its orbit (orbital period).
5.4.8 The Catalog Number
The catalog number is the number given to the object.
5.4.9 Mean Anomaly
As the satellite travels along its orbit, its position changes. The
angle (measured in the direction of forward rotation) between the
position of the spacecraft and the line of perigee is called the
true anomaly. The speed of the spacecraft is different at different
parts of the orbit. Calculations are simpler if the speed is
considered to be constant. The constant value is the average speed
of the spacecraft in its orbit. The mean anomaly is the hypothetical
position of the satellite in its orbit (along the ellipse) if it is
assumed to be traveling at its average speed.
5.5 Anticipated Spacecraft Lifetimes
There is not much point in setting up equipment to receive data
from these spacecraft if they are not going to be around for a
reasonable amount of time. Past experience points to three main
factors limiting the operational life of an OSCAR, namely orbital
decay, battery life, and total radiation dosage.
5.5.1 Orbital Decay
The last OSCAR to plunge back into the earth's atmosphere while
still active was UO-1. It was launched into a 500km orbit, and
lasted eight years. A chart in the Satellite Experimenter's Handbook
shows a lifetime of 40000-50000 days for spacecraft at the Microsat
altitude, or somewhere around 120 years; so orbital decay is not our
main worry. There has been some concern about AO-13's orbit, which
is expected to decay somewhere between 1994 and 1996. AMSAT however
are currently building Phase 3D as a replacement spacecraft so the
investment in receiving equipment will not be in vain.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 58
5.5.2 Battery lifetime
Battery breakdown has caused the demise of all amateur spacecraft
except UO-1. OSCARs 1, 2 and 3 were limited to whatever charge was
in the batteries when launched. Once Solar cells and nickel-cadmium
batteries were flown, the limiting factor became the number of times
the battery cells could be charged and discharged.
The batteries in OSCAR spacecraft in low earth orbit have lasted
between five and eight years. UO-1 was still looking good when it
re-entered the earth's atmosphere after 8 years. UO-2, launched in
March, 1984, has batteries with the same part number as those used
in the Microsats. These latter batteries were procured in much the
same manner, and were matched and tested by the same group of VITA
volunteers in Canada that performed the function for UO-2. The
batteries on UO-2 have shown no signs of weakening after almost six
years in orbit, so the prognosis for UO-2 and the Microsats looks
good.
5.5.3 Radiation Damage
Anything above the protection of the atmosphere is subjected to
exposure to the radiation due to the direct and secondary effects of
high energy particles, from the sun and elsewhere. The part of the
spacecraft most susceptible to such damage is the memory in the on-
board-computer (OBC). Such damage manifests itself as a bit flipping
from a 0 to a 1 or from a 1 to a 0, which is correctable. Since the
memory chips used are byte-wide, many types of single-chip failures
can be avoided in a manner analogous to locking out bad sectors on a
hard disk. UO-2, which uses somewhat similar technology chips, has
survived almost six years despite a failure of one small section of
memory several years ago.
Another part of the OBC is the controller itself which is
susceptible to a particle hitting it in a place that causes
uncorrectable errors, such as a wrong operation internal to the
microprocessor, or a CMOS latchup which can result in a high current
being drawn which overheats the part and destroys it.
The spacecraft are more likely to fail due to the cumulative
effects of this constant bombardment, which is known as total dose.
Once the total dose reaches a certain point, the gates in the
transistors that make up the computer and its memories will no
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 59
longer switch. This situation has occurred in AO-10. Predicting when
this might occur is difficult because of lack of knowledge
concerning two things; the total radiation dose in this orbit and
the tolerance limits for the parts used.
The MicroSats are in a much more benign orbit than AO-10 which with
its 4000 km perigee, spends more time in the Van Allen radiation
belts than was planned. AO-10's memories therefore failed sooner
than hoped, but the other electronics, the transponders, batteries,
and solar arrays live on. Through no-longer actively attitude
controlled, its transponders are still usable many weeks of the year
when its batteries are being charged by the sun.
AO-13 is in a better orbit with a lower perigee, and should not
suffer radiation degradation before other effects shorted its
lifespan.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 60
6.0 The Spacecraft
OSCAR spacecraft downlink signals in the amateur 145 MHz and 430
MHz bands modulated by means of Frequency Shift Keying (FSK),
Frequency Modulation (FM) or Phase Shift Keying (PSK). Some of the
characteristics of the downlinks of suitable OSCARs currently
operational are shown in Table 6-1. UO-2 and AO-13 send back BAUDOT
or ASCII data while AO-16, DO-17, WO-18, LU-19 and FO-20 downlink
packetized telemetry.
Table 6-1 Some of the Characteristics of OSCAR Downlinks.
Spacecraft Beacon Modulation Data Note
Frequency Type Rate
(MHz)
UO-2 145.825 FM ASCII 1200 Baud 1
435.025 FM ASCII 1200 Baud 1
AO-13 145.812 FSK BAUDOT 50 Baud 2
PSK ASCII 400 Baud 2
435.651 FSK BAUDOT 50 Baud 2
PSK ASCII 400 Baud 2
AO-16 437.025 PSK AX.25 1200 Baud 3
437.025 PSK AX.25 1200 Baud 3
DO-17 145.825 FM ASCII 1200 Baud
WO-18 437.100 PSK AX.25 1200 Baud 3
437.075 PSK AX.25 1200 Baud 3
LO-19 437.150 PSK AX.25 1200 Baud 3
437.125 PSK AX.25 1200 Baud 3
FO-20 435.912 PSK AX.25 1200 Baud
AO-21 145.987 FM AX.25 1200 Baud 5,6
SO-23 145.955 FM ASCII 300 Baud 4,6
Notes
1. Spacecraft also broadcasts bulletins and Various Telemetry
formats.
2. Spacecraft downlink modulation is changed according to a pre-
published schedule.
3. Alternate (back up) beacon frequency, may be used on Wednesdays.
4. Binary telemetry with ASCII identification.
5. Spacecraft also transponds FM signals uplinked on 435.016 MHz
and broadcasts voice bulletins from time to time.
6. Spacecraft no longer active.
Before discussing the equipment needed to receive signals from the
spacecraft, a brief word about the spacecraft themselves is in
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 61
order. Since these OSCARs rode into space as secondary payloads, the
orbits that they are in are close to those of the primary payload
and are not optimized for amateur radio communications. The
exception is AO-13 which contained a motor which was used by radio
amateurs to boost the spacecraft from the orbit the rocket placed it
in into its operational orbit. The ones that are in low earth orbits
can be received with simple equipment, but are in range for short
periods of time, AO-13 in an elliptical orbit is in range for many
hours each day, but needs more sophisticated receiving equipment.
The orbital parameters of the OSCARs under discussion are shown in
Table 6-2.
Table 6-21 Orbital Parameters of the OSCARs
Spacecraft Apogee Perigee Inclination Period
(km) (km) (Degrees) (Minutes)
UoSAT-2 699 670 98.0 98.3
AMSAT-OSCAR 13 39,000 2,500 26.1 686.65 [1]
AMSAT-OSCAR 16 804 780 98.7 100.8
DOVE-OSCAR 17 804 780 98.7 100.8
WEBER-OSCAR 18 804 780 98.7 100.8
LUSAT-OSCAR 19 804 780 98.7 100.8
FUJI-OSCAR 20 1,745 912 99.05 112.0
AMSAT-OSCAR 21 1,010 956 82.9 104.7
SARA-OSCAR 23 774 768 98.5 100.3
Notes
1 686.65 minutes is 11 hrs, 26 min.
6.1 Receiving system components
Consider the different components or building blocks that are used
in the different receiving configurations.
6.1.1 Antennas
Antennas receive signals, and each kind of antenna has some degree
of directive and polarization. When the spacecraft rises above the
local horizon, the ground station experiences acquisition of signals
(AOS). At this time the groundstation is receiving signals coming
from a particular direction (azimuth). As the spacecraft rises in
the sky, the elevation angle of the received signals changes, until
the spacecraft drops below the observer's horizon and the ground
station experiences loss of signals (LOS). As seen from the ground,
the spacecraft rises from a horizon in one direction, travels in an
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 62
arc across the sky and sets at a different horizon in a different
direction. Each pass for each spacecraft is different. Antennas for
receiving signals from spacecraft must thus be able to receive
signals coming in from almost any angle.
Antennas in this context, fall into two categories, omnidirectional
and rotatable. The simple turnstile antenna is horizontally
polarized and has a good response to signals arriving from high
angles and can be built for about $2.00. The ground plane and J Pole
antennas are vertically polarized and have a good response to
signals arriving from low angles. These antennas however do not have
much gain. Yagi Beam Antennas however have gain with respect to the
turnstile or ground plane, but only in specific directions. You can
think of the gain in some directions as being moved into the
direction that the antenna is pointed at. The gain of the antenna
depends on the number of elements in the antenna, and the higher the
gain, the narrower the area of the gain (lobe) is. Consequently,
these beam antennas must be moved to keep the spacecraft in the main
lobe of the antenna. Since the need for keeping the antenna pointed
at the spacecraft depends on the beam width of the antenna, the
lower the gain of the antenna the less accurate the tracking need
be. Luckily the orbits help out in this respect. UO-2 in low earth
orbit, which means it is fast moving, needs only a small amount of
gain, so TV style rotators can be employed to point antennas with
between 2 and 4 elements, while AMSAT-OSCAR 13 which is in an
elliptical orbit, moves so slowly for nearly 8 of its 11 hour orbit,
that again, TV style rotators can be used to point higher gain
antennas with between 8 and 11 elements.
Building your own antennas is an easy and worthwhile project.
Antennas for these OSCARS are simple and not very critical with
respect to the materials used. They can in fact be built from
recycled junk.
6.1.2 Receivers
There are two kinds of Receivers, namely FM and linear. FM
receivers are used for reception of the FM signals from DOVE and UO-
2, while linear receivers are needed for reception of the FSK and
PSK signals from the other spacecraft. All vhf/uhf scanner radios
are FM receivers. The linear receivers need single side band (SSB)
capability, something normally found in short wave communication
receivers. As a result of the growing popularity of amateur
satellite communications, suitable vhf/uhf transmitter-receivers
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 63
(transceivers) have been on the market for several years, however
these transceivers are expensive listing in the $800 to $1200 range.
An alternative approach to reception is to use a short wave
communications receiver listing around $500 together with a front
end downconverter which lists at under $100. The short wave radio
can also be used to tune in, not only the world of amateur radio,
but news broadcasts from overseas; a totally different are of
classroom activity.
"Expensive" is a relative term. These days, many people think
nothing of spending $1000 on a stereo system or on equipment for
photography or other hobbies.
6.1.3 Terminal Units and Modems
Digital radio links work much in the same way as digital signals
are transferred over the telephone line. However in this case,
instead of a phone wire, a radio link is used. Both links use modems
to convert the serial input/output digital RS-232 signals of the
computer to the audio tones used on the communications link.
Packet radio signals are demodulated by a radio modem known as a
Terminal Node Controller (TNC). The device is connected in between
the radio and the computer and provides hams with two way digital
communications. A packet only TNC lists for between $120 and $200.
For reception of the PSK signals from AO-16, WO-18, LO-19 and FO-20,
PSK Modems are available either as add-ons to a regular TNC or as
stand alone units, listing between $150 and $700.
The BAUDOT Radio Teletypewriter (RTTY) signals from AO-13 can be
demodulated by an RTTY Terminal Unit. These devices are listed at
between $100 and $300. On the other hand a multi-mode communications
controller listing between $250 and $700 can be used for AO-13 as
well as DOVE and the other spacecraft. AO-13 downlinks BAUDOT
because that is the most commonly used digital communications mode
used by radio amateurs at high frequencies (short waves)
The modem for UO-2 is a little more difficult, as its ASCII
encoding is the reverse of the standard used in the U.S.A. This is
because the spacecraft was built in the UK and its use of tones to
represent data reflects the encoding used in a popular tape
interface (in the UK) at the time the spacecraft was built (1982-
1984).
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 64
Still a do-it-yourself circuit needs a few integrated circuits, is
simple to build, easy to test, and very low cost (under $50).
Summarizing the costs of the items mentioned above, the list prices
fall between a low and high cost depending on the amount you wish to
pay. The summary is shown in Table 6-3. It should be noted that the
high price items may not be better than the cheaper ones,
particularly in the educational environment. This table is of course
only a guide, since you will probably end up with something in
between.
Table 6-3 Range of Equipment List Prices
Item Low Price High Price
Antenna $2.00 $100.00
Receiver $100.00 $1200.00
Radio Modem (TU/TNC) $150.00 $700.00
Tracking Software $25.00 $350.00
Telemetry Decoding Software $35.00 $35.00
---------------------------------------------------
TOTAL $312.00 $2385.00
Consider the equipment needed to receive signals from each of the
spacecraft in turn.
6.2 Receiving Signals from DOVE
DOVE (DO-17) which transmits on a frequency 145.825 MHz and AO-21
which transmits on a frequency of 145.987 MHz are the easiest
spacecraft to receive usable signals from. The frequencies are is
available on most hand held scanners, and signals are strong enough
to be heard on nothing more than the simple antenna provided with
the scanning radio when it is purchased. However, the thrill of
receiving satellite signals wears off very quickly without any means
to know what those signals mean.
A somewhat better system is needed for reliable regular reception
of usable signals. A basic receiving system for DOVE/AO-21 is shown
in Figure 6.1. Signals are strong enough that the ground station
does not need a tracking antenna; an omnidirectional antenna is
sufficient. The antenna can be a ground plane, a turnstile or a J-
pole design. A preamplifier should be used to compensate for any
losses in the cable between the antenna and the receiver, or any
fades in the strength of the received signals. Any scanning radio
which receives narrow band FM can be used as the receiver. This is
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 65
the same type of modulation used on the public service channels. If
the scanner can hear the police and other services and can tune to
145.825 MHz, then it is capable of receiving signals from DOVE. The
digital signals from DOVE are encoded as audio tones and need a
modem to convert them to the RS-232 digital signals that can be
interfaced to the serial port of a PC. This type of modem is known
in Radio Amateur circles as a Terminal Unit (TU).
Figure 6.1 Basic Receiving System for DO-17/AO-21
OMNIDIRECTIONAL
ANTENNA
|
|
\|/
SCANNER
RECEIVER ---------> TNC ---------> COMPUTER
The signals are sent as packets using a modified version of the
X.25 protocol called AX.25. Radio Amateurs use this protocol for
communications, and DOVE employs it for telemetry transmission
purposes so that any Radio Amateur equipped for packet radio
communications is also equipped for receiving signals from DOVE.
6.3 Receiving Signals from UO-2
The same basic radio receiving system used to receive signals from
DOVE can be used to copy the telemetry from UO-2. This spacecraft
however has a lower powered transmitter than that of DOVE and
consequently has a weaker signal strength on the ground. This lower
signal level, coupled with the fact that the modulation is plain
ASCII data means that errors will be seen in the received data due
to signal fades. Better antennas are needed for reliable reception,
and antennas that track or move and always point at the spacecraft
are desirable.
The TU used for UO-2 is different to that used for DOVE due to the
different data encoding (ASCII instead of AX.25).
6.4 Receiving Signals from AO-13
So far all the spacecraft considered have been low earth orbits.
AO-13 however is in an elliptical orbit with a high apogee. It also
downlinks telemetry as BAUDOT and ASCII data. While signals from
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 66
this spacecraft can be heard on the simple DOVE type of receiving
configuration with an omnidirectional receiving antenna, the signals
are weak and barely audible, i.e. they are in the noise and cannot
be received in usable form without a tracking antenna.
6.5 Receiving PSK Modulated Signals in the 70 cm Band
Receiving signals from AO-16, WO-18 and LU-19 as well as from FO-
requires somewhat more complex equipment. These spacecraft transmit
on downlink frequencies in the 70 cm or 430 MHz band. As they use
PSK, the receiver has to be a conventional communications receiver.
This can be either a communications receiver designed for that
frequency range, or a conventional short wave receiver with a front
end down converter. A PSK modem attached to the TU is also required.
Typical receiving configurations for these satellites are shown in
Figures 6-2 and 6-3.
Figure 6-2 Basic Receiving System for PSK Modulation.
OMNIDIRECTIONAL
ANTENNA
|
|
|
\|/ PSK MODEM
VHF/UHF | |
COMMUNICATIONS | |
RECEIVER --------> TNC ----> COMPUTER
The difference between the two approaches is that the first uses a
communications receiver designed for the 70 cm band; the second
approach uses a general short wave receiver and a front end down
converter.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 67
Figure 6-3 Alternate Basic Receiving System for PSK Modulation.
OMNIDIRECTIONAL
ANTENNA
|
|
DOWNCONVERTER
|
|
SHORT WAVE PSK MODEM
COMMUNICATIONS | |
RECEIVER | |
| | |
|-----------------------> TNC --------------> COMPUTER
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 68
7.0 Decoding Spacecraft Telemetry
Apart from UO-2, WO-18 and SO-23, none of the OSCAR spacecraft are
designed for "Science" purposes. Their telemetry consists of
spacecraft housekeeping parameters, monitoring on-board
temperatures, voltages and currents. While much use can be made of
these data, there isn't much real science data available. Even the
scientific spacecraft are in the main unusable by the average
listener because information about the scientific payload is not
readily available. Let's make a start with these spacecraft, then
look to a follow on activity. An OSCAR does not have to be a
separate spacecraft. The Soviet Union has provided their amateurs
with payload space aboard two of their weather satellites [8]. NASA
could do the same for an amateur scientific spacecraft which would
monitor radiation, the earth's magnetic field and solar activity;
such data being of use to radio amateurs for predicting propagation
and providing schools with data about the earth's environment. NASA
has a 'Mission to Planet Earth' project to provide an Earth
Observation Platform in 1997. An attached secondary payload to that
platform, transmitting packetized scientific telemetry data (with
well publicized formats) in the 145 MHz amateur band or in the 136
MHz scientific band could really bring not only the space program,
but the educational and scientific use of space, into every
educational institution in the country. In the mean time, this
section discusses the usable OSCAR spacecraft and their telemetry
and the corresponding decoding equations.
The satellites have been built by different organizations at
different times and each uses different data formats. SARA used a
300 baud ASCII format. DOVE and FO-20 transmit in an ASCII Packet
format, yet while DOVE transmits the data in Hexadecimal format, FO-
20 uses Decimal Format. AO-16, WO-18 and LO-19 transmit their
telemetry in pure binary format. By using packetization, the data
quality is checked in the link itself and bad packets are not
normally passed to the computer from the TNC. AO-13 does not have
any error checking at all, so it is up to the receiving station to
visually inspect the data before trying to convert it to engineering
units. UO-2 also transmits its telemetry as ASCII text, but the
designers of the spacecraft recognized that the downlink was prone
to error and incorporated a checksum in its data format. This
section discusses the data formats and decoding equations associated
with several of the OSCAR spacecraft.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 69
7.1 DOVE (DO-17)
DO-17 was launched January 22, 1990. Its prime mission is to
provide an easily received Digital Orbiting Voice Encoded beacon for
educational and scientific use. Dr. Torres 'Junior' de Castro,
PY2BJO sponsored the DOVE experiment. DO-17 is licensed in Brazil
with the callsign PT2PAZ. DO-17 was built by AMSAT, occupies less
than a cubic foot of space, masses 8.5 kg and contains a V40
microprocessor and 8 Megabytes of RAM. Essentially it is a loaded PC
Clone in orbit. AO-16, DO-17, WO-18 and LO-19 are commonly known as
Microsats and were constructed as a set by AMSAT during 1989. Each
of the Microsats contains bar magnets which align them along the
earth's magnetic field and is spun around that axis by photon
pressure from the sun acting on the communication antennas which are
painted white on one side and black on the other.
Unfortunately a combination of two on-board hardware failures and
lack of available manpower in AMSAT (a volunteer organization for
all practical purposes) have kept DOVE's voice off the air. At this
time DOVE only transmits packet telemetry. DO-17 transmits telemetry
in several different transfer packets as shown in Figure 7-1.
Figure 7-1 A typical example of a DO-17 Telemetry Frame.
23-Jan-91 02:49:23 DOVE-1*>TIME-1:
PHT: uptime is 173/00:36:26. Time is Wed Jan 23 02:47:30 1991
23-Jan-91 02:49:26 DOVE-1*>TLM:
00:59 01:59 02:87 03:31 04:59 05:5A 06:6E 07:52 08:6D 09:72 0A:A2
0B:DC 0C:E9 0D:D8 0E:02 0F:26 10:CC 11:A8 12:01 13:04 14:AD 15:94
16:98 17:94 18:96 19:98 1A:94 1B:91 1C:9B 1D:98 1E:25 1F:5F 20:BA
23-Jan-91 02:49:27 DOVE-1*>TLM:
21:95 22:82 23:24 24:1E 25:2A 26:01 27:02 28:02 29:01 2A:02 2B:02
2C:01 2D:29 2E:02 2F:9E 30:CA 31:9E 32:11 33:CE 34:C4 35:9A 36:A8
37:A6 38:B6
23-Jan-91 02:49:28 DOVE-1*>STATUS:
80 00 00 8F 00 18 CC 02 00 B0 00 00 0C 0E 3C 05 0B 00 04 04
23-Jan-91 02:49:28 DOVE-1*>LSTAT:
I P:0x3000 o:0 l:13081 f:13081, d:0
23-Jan-91 02:49:28 DOVE-1*>WASH:
wash addr:0680:0000, edac=0xd6
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 70
Telemetry data are transmitted in 57 (3A hex) channels in two
segments in the TLM packets. The format is AA:BB where 'AA' is the
hexadecimal channel number and 'BB' the hexadecimal value of the
telemetry at the time it was sampled.
The telemetry decoding equations for DOVE are shown in Table 7.1-1.
The Equations are in the form of a quadratic equation,
Y = A*N^2 + B*N + C where: N = Telemetry Count (00 - FF);
A, B, C = Equation Coefficients;
Y = Result (In Specified Units).
Note N must be converted from hexadecimal to decimal units before
performing the calculation. A sample decoded page is shown in Table
7.1-2.
Table 7.1-1 DOVE Telemetry Decoding Equations
Spacecraft: DOVE-1: Rev: 1 Date: 1/7/90
HEX Description: C: B: A: Units:
cccccccccc bbbbbbbbbb aaaaaaaaaa uuuuuu
0 Rx E/F Audio(W)+0.000 +0.0246 0.000 V(p-p)
1 Rx E/F Audio(N)+0.000 +0.0246 0.000 V(p-p)
2 Mixer Bias V: +0.000 +0.0102 0.000 Volts
3 Osc. Bias V: +0.000 +0.0102 0.000 Volts
4 Rx A Audio (W):+0.000 +0.0246 0.000 V(p-p)
5 Rx A Audio (N):+0.000 +0.0246 0.000 V(p-p)
6 Rx A DISC: +10.427 -0.09274 0.000 kHz
7 Rx A S meter: +0.000 +1.000 0.000 Counts
8 Rx E/F DISC: +9.6234 -0.09911 0.000 kHz
9 Rx E/F S meter:+0.000 +1.000 0.000 Counts
A +5 Volt Bus: +0.000 +0.0305 0.000 Volts
B +5V Rx Current:+0.000 +0.000100 0.000 Amps
C +2.5V VREF: +0.000 +0.0108 0.000 Volts
D 8.5V BUS: +0.000 +0.0391 0.000 Volts
E IR Detector: +0.000 +1.000 0.000 Counts
F LO Monitor I: +0.000 +0.000037 0.000 Amps
10 +10V Bus: +0.000 +0.05075 0.000 Volts
11 GASFET Bias I: +0.000 +0.000026 0.000 Amps
12 Ground REF: +0.000 +0.0100 0.000 Volts
13 +Z Array V: +0.000 +0.1023 0.000 Volts
14 Rx Temp: +101.05 -0.6051 0.000 Deg. C
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 71
15 +X (RX) temp: +101.05 -0.6051 0.000 Deg. C
16 Bat 1 V: +1.7932 -0.0034084 0.000 Volts
17 Bat 2 V: +1.7978 -0.0035316 0.000 Volts
18 Bat 3 V: +1.8046 -0.0035723 0.000 Volts
19 Bat 4 V: +1.7782 -0.0034590 0.000 Volts
1A Bat 5 V: +1.8410 -0.0038355 0.000 Volts
1B Bat 6 V: +1.8381 -0.0038450 0.000 Volts
1C Bat 7 V: +1.8568 -0.0037757 0.000 Volts
1D Bat 8 V: +1.7868 -0.0034068 0.000 Volts
1E Array V: +7.205 +0.07200 0.000 Volts
1F +5V Bus: +1.932 +0.0312 0.000 Volts
20 +8.5V Bus: +5.265 +0.0173 0.000 Volts
21 +10V Bus: +7.469 +0.021765 0.000 Volts
22 BCR Set Point: -8.762 +1.1590 0.000 Counts
23 BCR Load Cur: -0.0871 +0.00698 0.000 Amps
24 +8.5V Bus Cur: -0.00920 +0.001899 0.000 Amps
25 +5V Bus Cur: +0.00502 +0.00431 0.000 Amps
26 -X Array Cur: -0.01075 +0.00215 0.000 Amps
27 +X Array Cur: -0.01349 +0.00270 0.000 Amps
28 -Y Array Cur: -0.01196 +0.00239 0.000 Amps
29 +Y Array Cur: -0.01141 +0.00228 0.000 Amps
2A -Z Array Cur: -0.01653 +0.00245 0.000 Amps
2B +Z Array Cur: -0.01137 +0.00228 0.000 Amps
2C Ext Power Cur: -0.02000 +0.00250 0.000 Amps
2D BCR Input Cur: +0.06122 +0.00317 0.000 Amps
2E BCR Output Cur:-0.01724 +0.00345 0.000 Amps
2F Bat 1 Temp: +101.05 -0.6051 0.000 Deg. C
30 Bat 2 Temp: +101.05 -0.6051 0.000 Deg. C
31 Baseplt Temp: +101.05 -0.6051 0.000 Deg. C
32 FM TX#1 RF OUT:+0.0256 -0.000884 +0.0000836 Watts
33 FM TX#2 RF OUT:-0.0027 +0.001257 +0.0000730 Watts
34 PSK TX HPA Temp+101.05 -0.6051 0.000 Deg. C
35 +Y Array Temp: +101.05 -0.6051 0.000 Deg. C
36 RC PSK HPA Temp+101.05 -0.6051 0.000 Deg. C
37 RC PSK BP Temp:+101.05 -0.6051 0.000 Deg. C
38 +Z Array Temp: +101.05 -0.6051 0.000 Deg. C
39 S band TX Out: -0.0451 +0.00403 0.000 Watts
3A S band HPA Temp+101.05 -0.6051 0.000 Deg. C
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 72
Table 7.1-2 Sample Decoded (General Housekeeping) Page of DOVE
Telemetry
PHT: uptime is 177/12:34:12. Time is Sun Jan 27 14:45:16 1991
-X Array Cur : 0.174 A Array V :22.829 V
+X Array Cur : 0.000 A +Z Array V :23.836 V
-Y Array Cur : 0.000 A Ext Power Cur : 0.000 A
+Y Array Cur : 0.000 A BCR Input Cur : 0.480 A
-Z Array Cur : 0.000 A BCR Output Cur : 0.314 A
+Z Array Cur : 0.251 A BCR Set Point : 119
IR Detector : 56 BCR Load Cur : 0.241 A
+Z Array Temp : 3.0 C
+Y Array Temp : 4.8 C Battery 1 V : 1.330 V
Battery 2 V : 1.346 V
+2.5V VREF : 2.506 V Battery 3 V : 1.337 V
Ground REF : 0.020 V Battery 4 V : 1.325 V
Battery 5 V : 1.350 V
Bat 1 Temp : 3.0 C Battery 6 V : 1.431 V
Bat 2 Temp : -24.8 C Battery 7 V : 1.343 V
TX#1 RF OUT : 0.0 W Battery 8 V : 1.344 V
TX#2 RF OUT : 3.7 W
The TIME-1 packets identify the time that the data were downlinked.
The Uptime value in the time packet tells you how long the software
has been running (since last upload).
The STATUS packets contain information about spacecraft on-board
status. These bytes, have in the past, been changed by AMSAT without
prior or post notification to the radio amateur community. The LSTAT
packet contains engineering status information which has not been
published other than that the last value "d:0" means the spacecraft
is not set up as a digipeater.
The WASH packets provide engineering information about the on-board
RAM memory.
7.2 UoSAT-2
UoSAT-2 (UO-2) which was launched March 1, 1984, is similar to and
is a follow on to the now re-entered UO-1. It was designed and built
at the Department of Electronic and Electrical Engineering at the
University of Surrey, England. It was built to develop scientific
experimentation and space education. While much invaluable
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 73
experience has been received by the UoSAT people, not much has been
published in the general educational and radio amateur press about
its on-board experiments and telemetry data formats. As such, apart
from a small group of dedicated users, UO-2 seems to have been
ignored by the majority of radio amateurs and educational
institutions.
UO-2 carries four on-board experiments:- a Digital Communications
Experiment, a Space Dust Experiment, a Charge Coupled Device (CCD)
Video Camera Experiment and a Digitalker Experiment.
The Digital Communications Experiment demonstrated the concept of
store-and-forward digital communications using spacecraft in low
earth orbit. The Space Dust Experiment measures the impact of dust
particles, and calculates the momentum of the particles. The CCD
Video Camera Experiment takes pictures of the earth at a resolution
of 384 x 256 pixels with 128 gray levels. This exper-
iment does not seem to have returned any usable pictures. The
Digitalker Experiment provides clear digitized voice using a fixed
vocabulary and is switched on from time to time.
UO-2 transmits a number of different types of telemetry. WHATS-UP
can only decode and display the real-time telemetry. Should you tune
in signals from UO-2, you may get anything. Hang in there, sooner or
later it will transmit real-time telemetry, if not on one pass, then
on the next. The real-time telemetry is transmitted as 1200 baud
ASCII data using FSK. The sense of the modulation is inverted with
respect to convention due to the wide popularity of a BBC computer
tape interface (which used the inverted modulation) in England at
the time the spacecraft was built. This means that either a special
modem has to be built to receive the data or the PK-232 has to be
modified before it will copy signals from UO-2. This modification is
needed because the PK-232 RXR parameter does not work above 300 baud
due to a hardware limitation. This modification performs the
equivalent of the RXR operation in hardware by taking advantage of
an unused inverter inside the PK-232.
What has to be done is to wire U15 pins 1 and 2 to a switch in
series with the output to JP4. Adding a green LED to show the state
of the switch (at a glance) is optional. The steps are as follows:
1. Drill a 1/4 inch hole in the front panel of the PK-232 above the
red DCD LED.
2. Mount a Double Pole Double Throw (SPDT) switch on the front
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 74
panel of the PK-232 where it will not interfere with other
components (near the upper left corner by the AEA logo above the
threshold control).
3. Carefully cut the circuit board trace connecting U15's pin 6 to
the inside pin of JP4. This trace is easiest to cut where it
comes out from under R20 on the top (component side) of the PC
board. Be sure to double check that this is the correct trace
with an ohm meter. Cut with care (with a sharp X-acto knife) so
adjacent traces are not touched.
4. Solder a jumper wire between U15's pins 1 and 6.
5. Connect the center of one pole on this switch to the inner pin
of JP4 or the trace that goes to it (which was cut to disconnect
it from U15 pin 6).
6. Connect the corresponding switch contact which will be hardware
"RXR OFF" to U15 pin 6.
7. Connect the corresponding switch contact which will be hardware
"RXR ON" to U15 pin 2.
8. Mount a green LED on the front panel of the PK-232 above the red
DCD LED.
9. Wire one leg of the LED to the other pole of the switch, the
other end to a 1K ohm resistance (test the LED first to make
sure you wire it the correct way).
10. Wire the other end of the resistance to +12V near the voltage
regulator. Do not wire it to the battery back up voltage (if the
LED stays lit when you turn the PK-232 off, you wired it
wrongly).
11. Wire one side of the switch to ground so the green LED lights
when the REVERSE position is selected.
To copy the UO-2 FM AFSK ASCII Telemetry on 145.825 Mhz set the new
hardware RXR switch in the "reverse" position. Be sure to return
your RXR switch to "normal" when you want to return to regular
operation, as this switch is in the signal path in all modes when
the PK-232's internal modem is used.
A typical telemetry frame starts with a non printing ASCII
character (1E hexadecimal) followed by the identification and date.
The date code can be deciphered using the following YYMMDDWHHMMSS
format where YY is the last two digits of the year, MM, the month,
DD, the day of the month, W, the day of the week (Sunday = 0), the
remainder being hours,minutes and seconds. All times are given in
UTC. A blank line follows, then follow seven lines worth of ten
channels per line. The format of each line is as shown below.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 75
NNDDDCNNDDDCNNDDDCNNDDDCNNDDDCNNDDDCNNDDDCNNDDDCNNDDDCNNDDDC
where NN is the channel number, DDD the data and C a checksum to
validate the data. The checksum is needed because there is no error
checking built into the link. Each channel thus comprises six
digits. The checksum is computed for each channel by 'exclusive
or'ing (XOR) each nibble (4 bits) of each of the 6 characters in
that channel. A zero result means that the data was received
correctly, a non-zero result means the data was corrupted. Figure
7.2-1 contains an example of the raw UO-2 data showing some of the
errors due to noise on the downlink.
Figure 7.2-1 Example of a Received Raw UO-2 Telemetry Data Frame
00519D0141370267650361400404660503;4 6019E07045608040C08036C
10519C11298312000313056114069A15529A!6188;175452185905195058
20519F21220322662223000124001725000726093E27541528564D294681
30519E31041732287C33568B34007035217236276637393D38426B39455E
40649F41117242647343061044162545000146000247444748454949422x
50456251108D52634653284p54663215000056p00357451258447A59460E
60826A615FC1625F4A63334164440265160466174267700668000E69000F
UOSAT-2 9101281004625
7.3 AO-13
AO-13 which was launched June 15, 1988 was built as a joint venture
between radio amateurs in the U.S.A. and in Germany organized as the
Radio Amateur Satellite Corporation (AMSAT). AO-13 is a spin
stabilized long life long range radio amateur communications
satellite which provides daily intercontinental communications
capability for hours at a time. It contains a number of analog and
digital transponders with communications links on several
frequencies. An on-board computer based on the RCA 1802
microprocessor controls the spacecraft and generates the downlink
telemetry. Schedules are published in the amateur radio press which
provide information as to which transponder is active at any time
during the orbit. AO-13 also contains a motor which was used by
radio amateurs to boost the spacecraft from the orbit the rocket
placed it in into its operational orbit.
AO-13 transmits telemetry in a number of ways on two beacons. The
two meter beacon is on a frequency of 145.812 MHz and carries CW, 50
baud RTTY, and 400 baud PSK telemetry according to a published
schedule. WHATS-UP can only decode and display the 50 baud RTTY
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 76
telemetry which is transmitted in the form of Z blocks shown in
Table 7.3-1. The block is identified as a 'Z' block by the letter
'Z' before the words "HI. THIS IS AMSAT OSCAR 13" which identify the
spacecraft.
The block starts with the letter 'Z' in the first line. Time and
status information follows, then the first telemetry channel begins
several lines down and is shown with the value of 193. Six lines of
telemetry, each line containing ten values are transmitted, with a
blank line separating the two halves. Following the telemetry lines,
the spacecraft may transmit plain text information of general
interest. Although the Z block only contains 60 channels, the
equations for decoding all 128 of the telemetry channels are
presented in Table 7-3.2 in which the Channel Numbers are shown in
Hexadecimal.
The Bytes in the block are identified in the followings ways:
C - unsigned count (0 to +255)
Cs - signed count (-128 to +127, 2s complement)
Cx - signed count (+63 to -192, #3F=+63, #FF=-1, #80=-128,
#7F=-129, #40=-192, modified 2s complement)
All temperature channels are decoded identically using the equation
T = (C-120)/1.71 (in Degrees Centigrade). All channels measuring
currents use a linear equation with different calibrations
constants. Three equations are used providing maximum current values
of 1A, 2.5A and 5A, as follows:
1A: I = (C-15)*4.854 mA
2.5A: I = (C-15)*12.135mA
5A: I = (C-15)*24.27 mA
Table 7.3-1 AO-13 RTTY Telemetry Block
Z HI. THIS IS AMSAT OSCAR 13
05.02.54 8661
.0086 .0000 .07B9
64 6 0 1 16 218 1
193 170 158 143 181 144 147 140 200 7
147 7 7 7 165 29 100 7 149 7
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 77
10 7 145 115 34 7 153 129 122 180
152 73 7 145 137 55 7 183 136 151
7 154 137 169 211 142 127 100 9 140
161 7 173 149 150 154 14 131 127 210
HI THIS IS AMSAT OSCAR 13 08SEP90
NEW AO13 SCHEDULE FROM 17OCT90 AFTER MOVE TO LON 180 LAT 0
MODE B MA 000 TO 095
MODE JL MA 095 TO 125
MODE LS MA 125 TO 130
MODE S MA 130 TO 135
MODE BS MA 135 TO MA 140
MODE B MA 140 TO 256
Table 7.3-2 AO-13 Telemetry Decoding Equations
# Label Equation Remarks
00 Uin-BCR U=(C-10)*167mV U-Panel: +0.6V @ 0.35A
+0.7V @ 1A
01 Tx-PWRout-L Average power=(261-C)^2 / 724 Watts rectified
envelope voltage.
02 T-Rx-U Temp Mode-B receiver temperature.
03 ---
04 Uout-BCR U=(C-10)*79.5mV BCR output voltage.
05 ---
06 T-TX-U Temp Mode-B transmitter temperature.
07 I-14V-ST 5A Transponder separation bus.
08 U-10V-C U=(C-10)*53.2mV Computer supply
09 Press He-Hi off Helium tank pressure.
0A T-IHU Temp Integrated Housekeeping Unit
0B I-14V-S 1A Separation bus, 14V that
supplies torquer and LIU.
0C BCR-Oscill1 >~6=OK BCR status. No count = not
working. Typically C=80.
0D Press He-Lo off Helium regulator output.
0E T-BCR Temp Battery Charge Regulator.
0F I-10V-C 1A 10V continuous power supply.
10 BCR-Oscill2 As channel 0C
11 Press Tank off N2O4 tank pressure.
12 T-SEU Temp Sensor Electronics Unit
13 IbatCharge 2.5A Positive Current to battery.
14 L-Sensor (A) U=(C-10)*8.53mV Light-Sensor Antenna Side.
15 Motor Valve off
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 78
16 T-ABAT1 Temp Auxiliary battery 1
17 I-BCR-OUT 5A 14V line to battery and other
consumers.
18 L-Sensor (M) U=(C-10)*8.53mV Light-Sensor Motor Side.
19 ---
1A T-ABAT2 Temp Auxiliary battery 2
1B I-BCR-IN Equivalent to total current of all panels,
not available due to sensor failure.
1C Spin rate C>131, Spin rate=479/(C-109)-2 rpm
C<=131, Spin rate=(131-C)*0.85+20 rpm Sensor
angular position oscillator.
Lock indication channel #47.
1D Rx-L-AGC Gain reduction=(C-75)^2 / 1125 dB
1E T-MBAT Temp Mean battery (normally in use)
1F I-Panel6 1A Solar panel 6
20 Tx-PWRout-U Average power=(287-C)^2 / 1796 Watts As channel
01.
21 T-He-Tank Temp
22 T-Panel1 Temp
23 I-Panel5 1A
24 Rx-U-AGC Gain reduction=(C-71)^2 / 2465 dB
25 T-Tx-L Temp Mode-JL transmitter.
26 T-Panel3 Temp
27 I-Panel4 1A
28 ---
29 T-Rx-L Temp Mode-L receiver.
2A T-Panel5 Temp
2B I-Panel3 1A
2C U-14V-ST U=(C-10)*66.8mV Transponder separation bus.
2D T-RUDAK Temp RUDAK temperature.
2E T-top Temp Arm 1, Antenna side.
2F I-Panel2 1A
30 U-9V-U U=(C-10)*54mV Internal 9 volt bus from Mode-B
transponder.
31 T-wall-arm2 Temp
32 T-bottom Temp Arm 1, Motor side.
33 I-Panel1 1A
34 ---
35 T-wall-arm1 Temp
36 T-N2O4 Temp
37 ---
38 U-ABAT U=(C-10)*78.5mV Auxiliary battery.
39 T-S-xpnder Temp Mode-S transponder.
3A T-L-Sensor Temp Light sensor antenna side.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 79
3B ---
3C U-9V-L U=(C-10)*45.4mV As channel 30, Mode-L
3D T-AZ50-Tank Temp
3E T-nutation damper Temp Arm 3.
3F ---
40 ES-Sensitivity 2MUX0 Earth Sensor sensitivity
threshold. Bit significance
0 LSB 20mV
1 37mV Hysteresis
200mV
2 75mV Threshold
600mV
3 150mV
4 300mV
5 600mV
6 1.2V
7 MSB 2.4V
41 Antenna/SERI 2MUX1 Antenna relays and SERI
resistors.
bit significance
0 LSB Hi-gain 2m to U
1 Hi-gain 70cm to L
2 --+ SERI-1 load resistor
for
3 -+! SERI-2 both Light-
Sensors !! resistance
00 7.5 Ohm
01 3.9 Ohm
10 2.3 Ohm
11 5.9 Ohm
42 RUDAK-Status 2MUX2 IN-B (ex Motor-PWR).
C=82, Standard-ROS (S)
C=78, Emergency-ROS (N, Not-ROS)
C=80, Primitive-ROS (P)
43 S&RUDAK-CNTL 2MUX3 Mode-S and RUDAK interface.
bit significance
0 LSB RUDAK OFF
1 " NMI/
2 " Byte Clock
3 " Byte count reset
4 ---
5 Mode-S Beacon ON
6 " Squelch defeated
7 MSB " Squelch Hi Sensitivity
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 80
44 BCR-Sin 2MUX4 Array voltage offset.
U=29.1+(Cs*100)mV (16.3V...41.8V)
45 BCR-Sout 2MUX5 Battery knee voltage offset.
U=14.98+(Cx*20)mV (11.14...16.2V = 192...63)
46 BCR-relays 2MUX6
bit significance
0 LSB BCR-2 ON
1 Auxiliary battery charging
2 Auxiliary battery connected,
Main battery disconnected.
47 SS-1 C=255 or C=0, PLL locked
Sun-Sensor angular position
oscillator, Slit antenna
side.
48 SS-2 Time offset from SS-1
49 Flag-SS C=1, SS-1 Sun sensor data.
C=2, SS-2
4A SPIN-RAW Raw spin count (1/256).
4B Sensor-control bit significance (OUT4)
0 LSB --+ MUX-CTRL for sensor elec. module
1 -+!
!!
00 - Sun data
01 - spin ref./spin counter
10 - ES lower beam
11 - ES upper beam
2 Earth sensor positive edge select.
(Strobes value of spin count at
transition.)
3 Motor Instrumentation ON.
(Pressure sensors, motor valve
indicator.)
4 0.3V Sun Sensor Sensitivity
5 0.6V " " "
6 1.2V " " "
7 MSB 2.4V " " "
(Max. threshold #F = 1 solar constant)
4C SS-correction
4D Last ES-A Z last ES-pulse Antenna side.
4E " O# (Orbit number and MA value)
4F Last ES-M Z last ES-pulse Motor side.
50 " O# (Orbit number and MA value)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 81
51 Lockoutrange Within +- C counts from sun sensor pip, earth
sensor handler ignores data (Spin count 1
circle = 256 counts.)
52 ES-A Strobed spin count at edge selected,
Antenna Side beam.
53 Update Flag1 Indicates update, Antenna Side beam.
54 ES-M As channel 52 Motor Side beam.
55 Update Flag2 As channel 53 " " "
56 S/C STATUS bit significance
0 LSB LIU power ON
1 S/A plug status 0=Safe, 1=Arm
2 RUDAK-out (lock)
3 Mode-S Squelch open
4 ---
5 Memory Soft error Counter
6 " " "
7 MSB " " "
57 ---
58 ---
59 ---
5A ---
5B N no of 20ms per dot, morse speed.
5C n running count of units for morse.
5D ---
5E TRANSPONDER bit significance (OUT7)
0 LSB GB OFF
1 GB FSK (1=+170Hz)
2 DPSK OFF
3 EB ON
4 --+ PSK source
5 -+! for GB (EB: don't care)
!!
00 - no PSK
01 - ranging
10 - EB source
6 Low power transponder ON
7 MSB Passband OFF (Beacons and Mode-J +3dB)
5F ---
60 MODUS bit significance (magnet control)
0 magnet system ON
1 underspin magnet
61 M-Soll magnet vector desired angle to the despun sun
(clockwise as seen from top, 1 circle = 256)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 82
62 M-Out bit significance (OUT3, also L,S,J control)
0 LSB polarity Arm 1
1 polarity Arm 2
2 polarity Arm 3
3 Magnet power ON
4 Mode-J ON
5 ---
6 Mode-S ON
7 MSB Mode-L ON
63 O-FRAC-lo Fractional Z increment in 20ms
64 O-FRAC-hi Counts down to 0 from preset
value. 255th Z has different
value of O-FRAC. ~7000
counts/Z.
65 O/256 Z from perigee
66 O#-lo Orbit number
67 O#-hi
68 UHR 10ms UTC
69 sec
6A min
6B hour
6C day 1 January 1978 = AMSAT day 0.
6D 256day
6E SU0 10ms IPS stopwatch 0.
6F sec
70 min
71 min*256
72 SU1 10ms IPS stopwatch 1.
73 sec
74 min
75 min*256
76 SU2 10ms IPS stopwatch 2.
77 sec
78 min
79 min*256
7A SU3 10ms IPS stopwatch 3.
7B sec
7C min
7D min*256
7E Event-Lo Used as event ID word in
7F Event-Hi intermediate buffer.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 83
7.4 AO-16, WO-18 and LO-19
AO-16, WO-18 and LO-19 were launched January 22, 1990 together with
DO-17. AO-16 and LO-19 are designed to provide a platform for
experiments with digital store-and-forward communications techniques
as a follow-on to the Digital Communications Experiment of UO-2 11.
LO-19 is sponsored by AMSAT in Argentina. WO-18 is an engineering
project of the Center for Aerospace Studies at Weber State
University in Utah. It has the capability for digital communications
but is not used as such. It contains an on-board video camera which
has returned pictures of the earth using a non standard format
picture transmission format. WO-18 also carries a number of
experiments. The Spectrometer experiment is designed to observe the
spectrum of sunlight reflected off the earth's atmosphere and
surface. The Particle Impact Detector is a piezoelectrical crystal
mounted on the side of the spacecraft which produces an output
voltage each time a microparticle impact occurs. The Magnetometer
Experiment contains two orthogonal flux gate magnetometers. As they
were not calibrated they can only provide information about relative
changes in the magnetic environment of the spacecraft. As in the
case of UO-2, data about the experiments and their telemetry
calibrations is lacking in the general amateur radio press.
These spacecraft downlink telemetry in the 437MHz band similar to
that of DOVE but using a BINARY format in an unpublished and
apparently "changeable at any time without notice" sequence. WHATS-
UP intercepts the binary telemetry and converts it to a pseudo DOVE
format as shown in Table 7.4-1 before decoding and displaying the
information. The decoding equations first published by AMSAT in The
AMSAT Journal are given in Tables 7.4-2, 7.4-3 and 7.4-4.
Table 7.4-1 Example of Pseudo DOVE Display of Intercepted Binary
Telemetry and other intercepted Microsat Packets
27-Jan-91 17:04:22 LUSAT-1*>AMARG:
Jan 23, 1600Z.
AART driver loaded.
Reload will continue in a short time
73, LU7XAC
AMARG Control Team
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 84
27-Jan-91 16:41:50 PACSAT-1*>TIME-1:
PHT: uptime is 004/10:14:01. Time is Sun Jan 27 16:40:51 1991
27-Jan-91 16:41:54 PACSAT-1*>AMSAT:
Jan 22, 8:03 UTC - Reload in progress. Digi on. No BBS till
the weekend. NK6K
27-Jan-91 16:41:54 PACSAT-1*>LSTAT:
I P:0x3000 o:0 l:13884 f:13884, d:1 st:0
27-Jan-91 16:42:48 N8ITP>PACSAT-1*>N8ITP [C]
27-Jan-91 16:42:50 N8ITP>PACSAT-1*>N8ITP (UA)
27-Jan-91 16:42:55 N8ITP>PACSAT-1*>N8ITP:
test1122334455
27-Jan-91 17:04:22 LUSAT-1*>BCRXMT:
vmax=762169 battop=766771 temp=218292
27-Jan-91 17:06:31 LUSAT-1*>LSTAT:
I P:0x3000 o:0 l:13417 f:13417, d:0 st:2
27-Jan-91 17:06:38 LUSAT-1*>TIME-1:
PHT: uptime is 005/14:48:41. Time is Sun Jan 27 17:05:33 1991
27-Jan-91 17:06:41 LUSAT-1*>TLM:
00:DC 01:0E 02:30 03:0F 04:3A 05:10 06:DE 07:11 08:84 09:12
0A:00 0B:13 0C:E4 0D:14 0E:A9 0F:15 10:A8 11:16 12:6C 13:17
14:64 15:18 16:69 17:19 18:69 19:1A 1A:66 1B:1B 1C:6D 1D:1C
1E:5F 1F:1D 20:62 21:1E 22:D9 23:1F 24:62 25:20 26:BA 27:21
28:B0 29:22 2A:79 2B:23 2C:2C 2D:24 2E:24 2F:25 30:28 31:00
14-Feb-91 03:02:48 N4HY>LUSAT-1*>N4HY [D]
14-Feb-91 03:02:49 N4HY>LUSAT-1*>N4HY (UA)
14-Feb-91 03:03:09 LUSAT-1*>COMLUS:
COMMAND 9 ACK
14-Feb-91 03:06:51 LUSAT-1*>STATUS:
31 34 2D 46 65 62
Table 7.4.2 AO-16 Telemetry Decoding Equations
Spacecraft: PACSAT-1: Rev:
Date: 7/25/91
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 85
Equations are in the form: Y = A*N^2 + B*N + C
where:
N = Telemetry Count (00 - FF)
A, B, C = Equation Coefficients
Y = Result (In Specified Units)
HEX Description: C: B: A: Units:
cccccccccc bbbbbbbbbb aaaaaaaaaa uuuuuu
0 Rx D DISC: +9.202 -0.08990 0.000 kHz
1 Rx D S meter: +0.000 +1.000 0.000 Counts
2 Rx C DISC: +9.179 -0.09277 0.000 kHz
3 Rx C S meter: +0.000 +1.000 0.000 Counts
4 Rx B DISC: +9.837 -0.08838 0.000 kHz
5 Rx B S meter: +0.000 +1.000 0.000 Counts
6 Rx A DISC: +9.779 -0.09144 0.000 kHz
7 Rx A S meter: +0.000 +1.000 0.000 Counts
8 Rx E/F DISC: +10.817 -0.09911 0.000 kHz
9 Rx E/F S meter:+0.000 +1.000 0.000 Counts
A +5 Volt Bus: +0.000 +0.0305 0.000 Volts
B +5V Rx Current:+0.000 +0.000250 0.000 Amps
C +2.5V VREF: +0.000 +0.0108 0.000 Volts
D +8.5V Bus: +0.000 +0.0391 0.000 Volts
E IR Detector: +0.000 +1.000 0.000 Counts
F LO Monitor I: +0.000 +0.000037 0.000 Amps
10 +10V Bus: +0.000 +0.0500 0.000 Volts
11 GASFET Bias I: +0.000 +0.000026 0.000 Amps
12 Ground REF: +0.000 +0.0100 0.000 Volts
13 +Z Array V: +0.000 +0.1023 0.000 Volts
14 Rx Temp: +101.05 -0.6051 0.000 Deg. C
15 +X (RX) temp: +101.05 -0.6051 0.000 Deg. C
16 Bat 1 V: +1.8225 -0.0038046 0.000 Volts
17 Bat 2 V: +1.9418 -0.0046890 0.000 Volts
18 Bat 3 V: +1.8699 -0.0041641 0.000 Volts
19 Bat 4 V: +1.7403 -0.0032880 0.000 Volts
1A Bat 5 V: +1.8792 -0.0042492 0.000 Volts
1B Bat 6 V: +2.0499 -0.0054532 0.000 Volts
1C Bat 7 V: +1.9062 -0.0045331 0.000 Volts
1D Bat 8 V: +1.7536 -0.0033192 0.000 Volts
1E Array V: +8.055 +0.06790 0.000 Volts
1F* +5V Bus: +2.864583 4.090715E-2 -1.930042E-4 Volts
20* +8.5V Bus: +7.720951 +8.25979E-3 -1.76254E-5 Volts
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 86
21* +10V Bus: +8.882535 +1.39771E-2 0.000 Volts
22 BCR Set Point: -6.1130 +1.1270 0.000 Counts
23 BCR Load Cur: -0.0477 +0.00767 0.000 Amps
24 +8.5V Bus Cur: -0.00179 +0.000894 0.000 Amps
25 +5V Bus Cur: -0.00104 +0.00406 0.000 Amps
26 -X Array Cur: -0.00995 +0.00243 0.000 Amps
27 +X Array Cur: -0.02370 +0.00254 0.000 Amps
28 -Y Array Cur: -0.02220 +0.00273 0.000 Amps
29 +Y Array Cur: -0.01810 +0.00259 0.000 Amps
2A -Z Array Cur: -0.02230 +0.00221 0.000 Amps
2B +Z Array Cur: -0.02000 +0.00232 0.000 Amps
2C Ext Power Cur: -0.02000 +0.00250 0.000 Amps
2D* BCR Input Cur: -2.103334E-2 +3.382738E-3 0.000 Amps
2E* BCR Output Cur:-7.146611E-3 -5.247935E-5 4.878499E-5 Amps
2F Bat 1 Temp: +101.05 -0.6051 0.000 Deg. C
30 Bat 2 Temp: +101.05 -0.6051 0.000 Deg. C
31 Baseplt Temp: +101.05 -0.6051 0.000 Deg. C
32 PSK TX RF Out: -0.0291 +0.00361 +0.0000869 Watts
33 RC PSK TX Out: +0.0055 +0.00172 +0.0001180 Watts
34 PSK TX HPA Temp+101.05 -0.6051 0.000 Deg. C
35 +Y Array Temp: +101.05 -0.6051 0.000 Deg. C
36 RC PSK HPA Temp+101.05 -0.6051 0.000 Deg. C
37 RC PSK BP Temp:+101.05 -0.6051 0.000 Deg. C
38 +Z Array Temp: +101.05 -0.6051 0.000 Deg. C
39 S band HPA Temp: 0.00 1.0000 0.000 Counts
3A S band TX Out: -0.0088 +0.00435 0.000 Watts
* Revised in this release
Table 7.4.3 WO-18 Telemetry Decoding Equations
Spacecraft: WEBER-1: Rev: 1
Date: 1/7/90
Equations are in the form: Y = A*N^2 + B*N + C
where:
N = Telemetry Count (00 - FF)
A, B, C = Equation Coefficients
Y = Result (In Specified Units)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 87
HEX Description: C: B: A: Units:
cccccccccc bbbbbbbbbb aaaaaaaaaa uuuuuu
0 Rx D DISC: +11.087 -0.08949 0.000 kHz
1 Rx D S meter: +0.000 +1.000 0.000 Counts
2 Rx C DISC: +10.322 -0.09448 0.000 kHz
3 Rx C S meter: +0.000 +1.000 0.000 Counts
4 Rx B DISC: +10.348 -0.09004 0.000 kHz
5 Rx B S meter: +0.000 +1.000 0.000 Counts
6 Rx A DISC: +11.387 -0.09535 0.000 kHz
7 Rx A S meter: +0.000 +1.000 0.000 Counts
8 Rx E/F DISC: +10.746 -0.09348 0.000 kHz
9 Rx E/F S meter:+0.000 +1.000 0.000 Counts
A +5 Volt Bus: +0.000 +0.03523 0.000 Volts
B +5V Rx Current:+0.000 +0.000234 0.000 Amps
C +2.5V VREF: +0.000 +0.0133 0.000 Volts
D 8.5V BUS: +0.000 +0.0524 0.000 Volts
E IR Detector: +0.000 +1.000 0.000 Counts
F LO Monitor I: +0.000 +0.000033 0.000 Amps
10 +10V Bus: +0.000 +0.0767 0.000 Volts
11 GASFET Bias I: +0.000 +0.000026 0.000 Amps
12 Ground REF: +0.000 +0.0100 0.000 Volts
13 +Z Array V: +0.000 +0.1023 0.000 Volts
14 Rx Temp: +100.01 -0.5980 0.000 Deg. C
15 +X (RX) Temp: +100.01 -0.5980 0.000 Deg. C
16 Bat 1 V: +1.8292 -0.0037196 0.000 Volts
17 Bat 2 V: +1.8202 -0.0036943 0.000 Volts
18 Bat 3 V: +1.8050 -0.0036721 0.000 Volts
19 Bat 4 V: +1.8576 -0.0038979 0.000 Volts
1A Bat 5 V: +1.8095 -0.0037439 0.000 Volts
1B Bat 6 V: +1.8979 -0.0041754 0.000 Volts
1C Bat 7 V: +1.8246 -0.0038126 0.000 Volts
1D Bat 8 V: +1.7486 -0.0030475 0.000 Volts
1E Array V: +7.800 +0.06790 0.000 Volts
1F +5V Bus: +1.838 +0.0312 0.000 Volts
20 +8.5V Bus: +5.793 +0.0184 0.000 Volts
21 +10V Bus: +7.650 +0.0250 0.000 Volts
22 BCR Set Point: -6.1963 +1.1277 0.000 Counts
23 BCR Load Cur: -0.0405 +0.00620 0.000 Amps
24 +8.5V Bus Cur: +0.00384 +0.000830 0.000 Amps
25 +5V Bus Cur: -0.00763 +0.00394 0.000 Amps
26 -X Array Cur: -0.00140 +0.00210 0.000 Amps
27 +X Array Cur: +0.00946 +0.00226 0.000 Amps
28 -Y Array Cur: -0.01018 +0.00224 0.000 Amps
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 88
29 +Y Array Cur: -0.01168 +0.00239 0.000 Amps
2A -Z Array Cur: -0.01516 +0.00237 0.000 Amps
2B +Z Array Cur: -0.02111 +0.00239 0.000 Amps
2C Ext Power Cur: -0.02000 +0.00250 0.000 Amps
2D BCR Input Cur: -0.02189 +0.00332 0.000 Amps
2E BCR Output Cur:-0.03019 +0.00327 0.000 Amps
2F Bat 1 Temp: +100.01 -0.5980 0.000 Deg. C
30 Bat 2 Temp: +100.01 -0.5980 0.000 Deg. C
31 Baseplate Temp:+100.01 -0.5980 0.000 Deg. C
32 PSK TX RF Out: +0.2104 -0.01203 +0.0001786 Watts
33 RC PSK TX Out: +0.0340 -0.00969 +0.0002198 Watts
34 PSK TX HPA Temp+100.01 -0.5980 0.000 Deg. C
35 +Y Array Temp: +100.01 -0.5980 0.000 Deg. C
36 RC PSK HPA Temp+100.01 -0.5980 0.000 Deg. C
37 RC PSK BP Temp:+100.01 -0.5980 0.000 Deg. C
38 +Z Array Temp: +0.0000 +1.0000 0.000 Counts
Table 7.4.5 LO-19 Packet Telemetry Decoding Equations
Spacecraft: LUSAT-1: Rev: 1
Date: 1/7/90
Equations are in the form: Y = A*N^2 + B*N + C
where:
N = Telemetry Count (00 - FF)
A, B, C = Equation Coefficients
Y = Result (In Specified Units)
HEX Description: C: B: A: Units:
cccccccccc bbbbbbbbbb aaaaaaaaaa uuuuuu
0 Rx D DISC: +9.802 -0.08779 0.000 kHz
1 Rx D S meter: +0.000 +1.000 0.000 Counts
2 Rx C DISC: +8.429 -0.09102 0.000 kHz
3 Rx C S meter: +0.000 +1.000 0.000 Counts
4 Rx B DISC: +9.291 -0.08317 0.000 kHz
5 Rx B S meter: +0.000 +1.000 0.000 Counts
6 Rx A DISC: +9.752 -0.08310 0.000 kHz
7 Rx A S meter: +0.000 +1.000 0.000 Counts
8 Rx E/F DISC: +10.110 -0.08610 0.000 kHz
9 Rx E/F S meter:+0.000 +1.000 0.000 Counts
A +5 Volt Bus: +0.000 +0.0305 0.000 Volts
B +5V Rx Current:+0.000 +0.000250 0.000 Amps
C +2.5V VREF: +0.000 +0.0108 0.000 Volts
D 8.5V BUS: +0.000 +0.0391 0.000 Volts
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 89
E IR Detector: +0.000 +1.000 0.000 Counts
F LO Monitor I: +0.000 +0.000037 0.000 Amps
10 +10V Bus: +0.000 +0.0508 0.000 Volts
11 GASFET Bias I: +0.000 +0.000026 0.000 Amps
12 Ground REF: +0.000 +0.0100 0.000 Volts
13 +Z Array V: +0.000 +0.1023 0.000 Volts
14 Rx Temp: +93.24 -0.5609 0.000 Deg. C
15 +X (RX) Temp: +93.24 -0.5609 0.000 Deg. C
16 Bat 1 V: +1.7343 -0.0029740 0.000 Volts
17 Bat 2 V: +1.7512 -0.0032113 0.000 Volts
18 Bat 3 V: +1.7790 -0.0034038 0.000 Volts
19 Bat 4 V: +1.7286 -0.0030036 0.000 Volts
1A Bat 5 V: +1.8114 -0.0036960 0.000 Volts
1B Bat 6 V: +1.7547 -0.0032712 0.000 Volts
1C Bat 7 V: +1.7151 -0.0030739 0.000 Volts
1D Bat 8 V: +1.6846 -0.0028534 0.000 Volts
1E Array V: +8.100 +0.06790 0.000 Volts
1F +5V Bus: +2.035 +0.0312 0.000 Volts
20 +8.5V Bus: +5.614 +0.0184 0.000 Volts
21 +10V Bus: +7.650 +0.0250 0.000 Volts
22 BCR Set Point: +3.7928 +1.0616 0.000 Counts
23 BCR Load Cur: -0.0244 +0.00628 0.000 Amps
24 +8.5V Bus Cur: +0.00412 +0.000773 0.000 Amps
25 +5V Bus Cur: +0.02461 +0.00438 0.000 Amps
26 +X Array Cur: -0.01614 +0.00232 0.000 Amps
27 -X Array Cur: -0.01158 +0.00238 0.000 Amps
28 -Y Array Cur: +0.00278 +0.00206 0.000 Amps
29 +Y Array Cur: +0.00136 +0.00218 0.000 Amps
2A -Z Array Cur: +0.00370 +0.00209 0.000 Amps
2B +Z Array Cur: -0.00793 +0.00216 0.000 Amps
2C Ext Power Cur: -0.02000 +0.00250 0.000 Amps
2D BCR Input Cur: -0.00901 +0.00283 0.000 Amps
2E BCR Output Cur:+0.00663 +0.00344 0.000 Amps
2F Bat 1 Temp: +93.24 -0.5609 0.000 Deg. C
30 Bat 2 Temp: +93.24 -0.5609 0.000 Deg. C
31 Baseplt Temp: +93.24 -0.5609 0.000 Deg. C
32 PSK TX RF Out: +0.1059 +0.00095 +0.0000834 Watts
33 RC PSK TX Out: +0.0178 +0.00135 +0.0000833 Watts
34 PSK TX HPA Temp+93.24 -0.5609 0.000 Deg. C
35 +Y Array Temp: +93.24 -0.5609 0.000 Deg. C
36 RC PSK HPA Temp+93.24 -0.5609 0.000 Deg. C
37 RC PSK BP Temp:+93.24 -0.5609 0.000 Deg. C
38 +Z Array Temp: +93.24 -0.5609 0.000 Deg. C
39 LU Bcn Temp A: +93.24 -0.5609 0.000 * Deg. C
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 90
3A LU Bcn Temp D: +93.24 -0.5609 0.000 ** Deg. C
3B Coax Rly Stat: +0.000 +1.0000 0.000 Counts
3C Coax Rly Stat: +0.000 +1.0000 0.000 Counts
* Note 1: Thermistor located near box center adjacent to LU
thermistor channel no. 5.
** Note 2: Thermistor located near -X face of box on the experiment
baseplate.
LO-19 also transmits 8 channels of CW telemetry, at 12 W.P.M. with
reduced morse code (to save about 44% power). The format of the
telemetry is:
E LUSAT HI HI NL 111 222 333 444 555 666 777 888
where:
E is a calibration point to measure the output power.
NL:N is the EPROM version number. There are 7 copies of the
program in the EPROM, to prevent crashes or hang ups
due to degradation effects. The on board computer
automatically loads a valid version, and N indicates
which version was loaded.
L is the result of an internal RAM memory test by the 6805
microprocessor. If L=0, the RAM is "OK". If L=E, an
Error was detected.
The telemetry decoding equations for the LO-19 CW are shown in
Table 7.4.6.
Table 7.4.6 LO-19 CW Telemetry Decoding Equations
CH# 1 = N1 +5 Reg Volts : 636/N1 (Volts)
CH# 2 = N2 +10 Volts Battery 0.064*N2 (Volts
CH# 3 = N3 CW TX Temperature 0.354(134.7-N3) (Deg. C)
CH# 4 = N4 CW TX Power Output (10.9+N)^2/40.1 (Watts)
CH# 5 = N5 Temp. BOX No. 4 0.356(136-N5) (Deg. C)
CH# 6 = N6 +10 V Current 0.7*N6 (mAmps.)
CH# 7 = N7 Panel +Z Volts 0.15*N7 (Volts)
CH# 8 = N8 Reg. +8.5 Volts 0.056*N8 (Volts)
A typical example of a CW telemetry frame is shown below.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 91
E LUSAT HI HI 1O 128 167 042 162 040 148 045 156
decoding it, We have: E LUSAT HI HI
NL = 1O : N=1 (first version) ; L=O (Memory 6805 RAM "OK")
N1=128: 636/128 = + 4.97 V. REG.
N2=167: 0.064*167 = +10.69 V. BATTERY
N3=042: 0.354(134.7-042) = 32.81 Deg. C
N4=162: (10.9+162)^2/40.1= 745.5 mW.
N5=040: 0.356(136-040) = 34.17 Deg. C
N6=148: 0.7*148 = 103.6 mA. (over 10 V)
N7=045: 0.15*045 = + 6.75 V. +Z
N8=156: 0.056*156 = + 8.736 V. REG.
NOTE: the reduced cw code is USED ONLY for the numeric data, and
AFTER the "HI HI" as in the following example.
L U S A T H I H I 1 O
1: .- (A) 6: -.... (6)
2: ..- (U) 7: -... (B)
3: ...- (V) 8: -.. (D)
4: ....- (4) 9: -. (N)
5: . (E) 0: - (T)
7.5 Fuji-OSCAR 20
FO-20 which was launched on February 7, 1990 is a communications
satellite in low earth orbit providing simultaneous analog and
digital communications capability. FO-20 was built in Japan for
Japanese radio amateurs and is the second Japanese built OSCAR.
On February 7 1990, the National Space Development Agency of Japan
(NASDA) put the Marine Observation Satellite (MOS) 1b into orbit.
The launch vehicle also carried two secondary payloads, FO-20 and
the Deployable Boom and Umbrella Test (DEBUT) spacecraft which is
similar in shape and weight to FO-20. MOS-1b was placed into a
circular polar orbit, then DEBUT and Fuji-OSCAR 20 separated from
the launch vehicle at 0233, above Santiago, Chile. First signals
from the spacecraft were received in Tokyo around 0309 UTC.
FO-20 is similar in construction to FO-12. In fact, much of it was
originally constructed as a backup to FO-12 and designated as JAS-
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 92
1B. It has since been modified and improved as a result of the
lessons learned during the flight of FO-12. FO-12 was known as Fuji-
1 in Japan, so this spacecraft is known by the Japanese as Fuji-2
and as FO-20 by the rest of the world.
FO-20's planned service life is 5 years. It is in a sunsynchronous
elliptical polar orbit, having a perigee of about 900 km and an
apogee of about 1740 at an inclination of 99 degrees. The Period of
the orbit is about 105 minutes. This orbit is optimal for MOS-1b
which is to study oceanographic resources and observe agricultural
environmental conditions. In this orbit, the spacecraft passes over
a given line of latitude at approximately the same time each day. In
this orbit, the spacecraft is shielded from the sun by the earth for
about 33% of the time. This eclipse means that the solar cells can
only provide power for about 70 minutes in each orbit and that the
on-board nickel cadmium storage batteries have to power the
spacecraft for the remaining 35 minutes.
FO-20 weighs about 50 kg. and is a polyhedron shaped spacecraft
440mm in diameter and 470mm in height covered by approximately 1500
gallium arsenide solar cells which provide about 11 Watts of power
to keep the 11 series-connected NiCad cells (rectangular) with a
capacity of 6 AH charged. There are 26 sides to the polyhedron which
almost makes it spherical for all practical purposes other than
sticking solar cells to it. FO-12 was the same shape but only
carried about 600 cells. This larger number of cells means that FO-
20 has a positive power budget and should not need to be switched
off to recharge.
The Power supply converts the raw bus voltage of +11 to +18 V (+14
V average) to the three regulated voltages (+10 V, +5 V, -5 V) used
by the rest of the satellite with an efficiency greater than 70%.
The attitude of the satellite is maintained by using the torque
generated by the interaction of two permanent magnets with the
earth's magnetic field. This is a fairly conventional technique used
in the OSCAR series. Temperature stability is achieved by using
thermal insulation.
FO-20 carries two Mode J transponders, both of which may be
operational at the same time. One transponder is analog (Mode JA),
the other is digital (Mode JD).
The frequencies and capabilities of the analog transponder are
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 93
similar to those of FO-12. It consists of an inverted heterodyne
linear translator with a passband 100 kHz wide, operating with a
mode J Uplink passband of 145.9 to 146.00 MHz, and a corresponding
Downlink Passband of 435.9 to 435.8 MHz. The spacecraft has a
Transmitter Output of approximately 1 watt. A ground station needs
an Uplink EIRP of about 100 W to communicate through the
transponder. The JA telemetry beacon is on the nominal frequency of
435.795 MHz with a power output of about 100 mW and can use CW or
PSK modulation. FO-20 is using the callsign 8J1JBS and the beacons
transmit telemetry in the same manner as FO-12.
The digital transponder provides store-and-forward packet
communication using AX.25 link level protocol, version 2. Stations
who used FO-12 are able to use FO-20 without making any
modifications to their equipment. The uplink requires Bi-phased
Manchester code on an FM signal, at a bit rate of 1200 bps. There
are four Uplink Frequencies: 145.85 MHz, 145.87 MHz, 145.89 MHz,
145.91 MHz. The necessary ground station Uplink EIRP is also about
100 W. The transponder has an output power of about 1 W on a
downlink frequency of 435.91 MHz and uses NRZI PSK at 1200 bps. The
same PSK modem used to copy FO-12 or the Microsats is needed to copy
FO-20. The downlink channel also carries packet telemetry.
The on-board 144 MHz receiving antenna is a ring turnstile mounted
at the bottom of the side panels. The 435 MHz transmitting antenna
is a turnstile antenna mounted at the top of satellite. Both
antennas are circularly polarized. Ground tests have shown that the
transmitting antenna is more omnidirectional than that of FO-12,
however due to the structure of the hybrid circuitry which allow
both transponders to share the same antenna, the sense of the
circular polarization on the downlink is different for each mode. As
the apparent polarization is different depending on the geometry
between the spacecraft and the groundstation, you will probably have
to change between left hand and right hand circular polarization
during a pass. The spacecraft is designed so that you can usually
keep the uplink and downlink polarization the same.
Mode JA has provided strong transatlantic signals and many CW and
SSB QSOs. Mode-JD was switched on for the first time during Orbit
#95. To Digipeat via FO-20 you don't need to use a digipeater call.
With the present version of the software, all AX.25 frames with a
valid CRC heard by the spacecraft will be digipeated.
The spacecraft also carries a BBS which is accessed by means of the
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 94
same commands used to access a terrestrial WA7MBL/W0RLI/AA4RE type
of BBS. You access the BBS by connecting to 8J1JBS on any of the
four uplink channels. When you do connect to it, make sure that you
disconnect before LOS because FO-20 only allows 16 simultaneous
connections. Stations that hang in there after the satellite drops
below their local horizon block access by other stations and have
been christened 'Zombies'. The BBS program is a modified version of
the BBS program written for FO-12 and allows the use of 4 banks
(1Mbyte) of memory. A typical list of messages copied by KI6QE is
shown in Figure 7.5-1.
Figure 7.5-1 Typical Message Listing from the BBS (copied by KI6QE)
Fuji-OSCAR 20/JAS1b Mailbox ver. 2.00
commands [B/F/H/M/R/U/W]
Use H command for Help
JAS>JAS>NO. DATE UTC FROM TO SUBJECT
0086 04/13 05:15 WB6GFJ W6SHP Welcome
0085 04/13 05:14 WB6LLO KI6QE SOFTWARE
0084 04/13 05:14 WB6GFJ W9FMW Our Chat
0082 04/13 03:38 W9FMW WA4EJR MESSAGE ON CIS
0080 04/13 03:36 KG6EX N1GCR From Ashley
0078 04/13 03:32 KG6EX KD8SI From Ashley
0077 04/13 03:31 KG6EX N8AM From Ashley
0076 04/13 03:30 KG6EX DD4YR From Ashley
0075 04/13 03:27 KG6EX DL1CR From Ashley
0074 04/13 03:25 KG6EX G3RUH From Ashley
The spacecraft telemetry is transmitted either as CW or as PSK. The
CW telemetry monitors 12 analog data points and 33 status points,
the PSK telemetry monitors 29 analog data points and 33 status
points. Telemetry data from Fuji-OSCAR 20 is transmitted on both the
mode JA and JD beacons. Mode JA sends data by Morse code on the
beacon signal of 435.795 MHz, repeating one frame every one minute.
Mode JD sends a telemetry packet every 2 seconds on the digital
downlink channel of 435.91 MHz when the telemetry mode is operating,
otherwise, one frame is downlinked every one minute. The spacecraft
can downlink up to 30 items of data and 31 items of status in the
telemetry. The Mode JA beacon however only carries 12 data elements
and most of status bytes.
Mode JA Telemetry Data The Mode JA beacon transmits the telemetry
data in the format shown below. These data are sent by Morse code
with a "HI HI" at the beginning of each frame, with a speed of about
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 95
100 characters every minute, and always in this format repeatedly.
HI HI 1A 1B 1C 1D
2A 2B 2C 2D
3A 3B 3C 3D
4A 4B 4C 4D
5A 5B 5C 5D
The number identifies the group, the letters A through D are
decimal values expressed in two digits. Let this two-digit be N, for
each item, true value or engineering value is obtained by decoding N
as shown below. For example, a value of 123 for 1A means group 1 and
23 is the measured value of the solar array current. Groups 4 and 5
contain status information about the bird, where A, B, C and D
represent octal two-digit combinations of 00 through 37. This
corresponds to a combination of five binary digits. Each bit shows
status of each designated item in the order from MSB (Most
Significant Bit) to LSB (Least Significant Bit). The decoding
equations for the CW Mode JA telemetry are shown in Figure 7.5-2.
Figure 7.5-2 Fuji-OSCAR 20 Mode JA Telemetry Conversion Equations
CH DESCRIPTION CALIBRATION UNITS
1A total solar array current 19x(N+0.4) mA
1B battery charge/discharge current -38x(N-50) mA
1C battery voltage (N+4)x0.22 V
1D center tap voltage of battery (N+4)x0.1 V
2A bus voltage (N+4)x0.2 V
2B +5 V regulator voltage (N+4)x0.062 V
2C JTA output power 2.0x(N+4)^1.618mW
2D calibration voltage (N+4)/50 V
3A battery temperature 1.4x(67-N) deg. C
3B baseplate temperature #1 1.4x(67-N) deg. C
3C baseplate temperature #2 1.4x(67-N) deg. C
3D baseplate temperature #3 1.4x(67-N) deg. C
The status byte conversions are shown in Figure 7.5-3. This method
is used because all items whose status is represented in this manner
only have two possible situations, either ON or OFF, or binary
values 0 or 1. For example, if the first item of status 4A were 423,
the 4 identifies group 4, and the 23 should be thought of as its
equivalent binary code (10011). This shows the status in the order
of MSB to LSB, or bit 4 to bit 0. Using the decoding data 423 can be
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 96
decoded as follows.
1: Beacon is PSK,
0: Engineering data #2 is blank,
0: Engineering data #1 is blank,
1: JTD power is ON,
1: JTA power is ON.
Figure 7.5-3 Fuji-OSCAR 20 Mode JA System Status Bytes
CH BIT DESCRIPTION STATE
1 0
4A 0 JTA power ON OFF
4A 1 JTD power ON OFF
4A 2 Eng. data #1 --- ---
4A 3 Eng. data #3 --- ---
4A 4 Beacon PSK CW
4B 0 UVC ON OFF
4B 1 UVC level 1 2
4B 2 Battery tric full
4B 3 Battery logic tric full
4B 4 Main relay ON OFF
4C 0 PCU bit 1 (LSB)
4C 1 PCU bit 2 (LSB)
4C 2 PCU manual auto
4C 3 Eng. data #3 --- ---
4C 4 Eng. data #4 --- ---
4D 0 Memory bank #0 ON OFF
4D 1 Memory bank #1 ON OFF
4D 2 Memory bank #2 ON OFF
4D 3 Memory bank #3 ON OFF
4D 4 Computer power ON OFF
5A 0 Memory select bit 1 (LSB)
5A 1 Memory select bit 2 (MSB)
5A 2 Eng. data #5 --- ---
5A 3 Eng. data #6 --- ---
5A 4 Eng. data #7 --- ---
5B 0 Solar panel #1 lit dark
5B 1 Solar panel #2 lit dark
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 97
5B 2 Solar panel #3 lit dark
5B 3 Solar panel #4 lit dark
5B 4 Solar panel #5 lit dark
5C 0 JTA CW beacon CPU TLM
5C 1 Eng. data #8 --- ---
5C 2 Eng. data #9 --- ---
5C 3 Eng. data #10 --- ---
5C 4 Eng. data #11 --- ---
5D 0 Eng. data #12 --- ---
5D 1 Eng. data #13 --- ---
5D 2 Eng. data #14 --- ---
5D 3 Eng. data #15 --- ---
5D 4 Eng. data #16 --- ---
Telemetry data are downlinked on Mode JD by means of packets. These
data are transmitted the ASCII format shown in Figure 7.5-4. In the
ASCII telemetry (RA and RB) XXX is a 3 digit decimal number with a
range between 000 to 999. This number represents the value of N in
Table 5 for channels denoted #00 - #26.
Figure 7.5-5 contains the equations for converting the received
data into engineering values. The YYY bytes are three hexadecimal
bytes of system status data, denoted #27a - #29c and can be decoded
as shown in Figure 7.5-6. The SSS byte in the last row are binary
status data, denoted #30a - #39c. Figure 7.5-7 provides the
information needed to decode them in a manner similar to the Mode JA
status points shown in Figure 7.5-3.
Figure 7.5-4. Fuji-OSCAR 20 Mode JD PSK telemetry data format
JAS-1b FF YY/MM/DD HH:MM:SS
XXX XXX XXX XXX XXX XXX XXX XXX XXX XXX
XXX XXX XXX XXX XXX XXX XXX XXX XXX XXX
XXX XXX XXX XXX XXX XXX XXX YYY YYY YYY
SSS SSS SSS SSS SSS SSS SSS SSS SSS SSS
where, FF is the Frame Identifier, which may contain the following
types:
RA: Realtime telemetry, - ASCII
RB: Realtime telemetry, - Binary
SA: Stored telemetry, - ASCII
SB: Stored telemetry, - Binary
M0: Message #0
M1: Message #1
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 98
...........
M9: Message #9
YY/MM/DD is year/month/day, and HH:MM:SS is hour/minute/second, all
in UTC.
Figure 7.5-5. Fuji-OSCAR 20 Mode JD Telemetry Decoding Equations
CH DESCRIPTION CALIBRATION/UNITS
#00 total solar array current 1.91x(N-4)mA
#01 battery charge/discharge -3.81x(N-508)mA
#02 battery voltage Nx0.022V
#03 battery center voltage Nx0.009961V
#04 bus voltage Nx0.02021 V
#05 +5 V regulator voltage Nx0.00620 V
#06 -5 V regulator voltage -Nx0.00620 V
#07 + 10 V regulator voltage Nx0.0126 V
#08 JTA output power 5.1x(N-158)mW
#09 JTD output power 5.4x(N-116)mW
#10 calibration voltage #2 N/500 V
#11 offset voltage #1 N/500 V
#12 battery temperature 0.139x(669-N)deg. C
#13 JTD temperature 0.139x(669-N)deg. C
#14 Baseplate Temperature #1 0.139x(669-N)deg. C
#15 Baseplate Temperature #2 0.139x(669-N)deg. C
#16 Baseplate Temperature #3 0.139x(669-N)deg. C
#17 Baseplate Temperature #4 0.139x(669-N)deg. C
#18 temperature calibration #1 N/500 V
#19 offset voltage #2 N/500 V
#20 Solar Cell Panel Temp #1 0.38x(N-685)deg. C
#21 Solar Cell Panel Temp #2 0.38x(N-643)
#22 Solar Cell Panel Temp #3 0.38x(N-646)
#23 Solar Cell Panel Temp #4 0.38x(N-647)
#24 -------------------------
#25 temperature calibration #2 N/500 V
#26 temperature calibration #3 N/500 V
---------------------------------------------------------
Figure 7.5-6. Fuji-OSCAR 20 Mode JD HEX System Status Bytes
CH DESCRIPTION
#27a Spare (TBD)
#27b Spare (TBD)
#27c Spare (TBD)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 99
#28a Spare (TBD)
#28b Spare (TBD)
#28c error count of memory unit #0
#29a error count of memory unit #1
#29b error count of memory unit #2
#29c error count of memory unit #3
Figure 7.5-7. Fuji-OSCAR 20 Mode JD BINARY System Status Bytes.
CH DESCRIPTION STATE
1 0
#30a JTA power on off
#30b JTD power on off
#30c JTA beacon PSK CW
#31a UVC status on off
#31b UVC level 1 2
#31c main relay on off
#32a engineering data #1 -----
#32b battery status tric full
#32c battery logic tric full
#33a engineering data #2 -----
#33b PCU status bit 1 (LSB)
#33c PCU status bit 2 (MSB)
#34a memory unit #0 on off
#34b memory unit #1 on off
#34c memory unit #2 on off
#35a memory unit on off
#35b memory select bit 1 (LSB)
#35c memory select bit 2 (MSB)
#36a engineering data #3 ------
#36b engineering data #4 ------
#36c computer power on off
#37a engineering data #5 ------
#37b solar panel #1 lit dark
#37c solar panel #2 lit dark
#38a solar panel #3 lit dark
#38b solar panel #4 lit dark
#38c solar panel #5 lit dark
#39a engineering data #6 ------
#39b CW beacon source CPU TLM
#39c engineering data #7 ------
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 100
A typical set of raw PSK telemetry packets are those captured by
KI6QE and shown in Figure 7.5-8. A typical decoded and display page
from WHATS-UP is shown in Figure 7.5-9 for a different set of raw
data.
Figure 7.5-8 Fuji-OSCAR 20 PSK telemetry (as copied by KI6QE)
03-Apr-90 17:40:32 8J1JBS*>BEACON:
JAS1b RA 90/04/03 17:45:18
554 433 700 686 757 837 841 823 398 666
617 001 503 516 526 523 526 523 654 000
683 675 685 684 999 643 875 316 002 000
110 111 000 000 100 000 001 011 111 000
03-Apr-90 17:40:34 8J1JBS*>BEACON:
JAS1b RA 90/04/03 17:45:20
566 427 699 705 746 837 841 824 541 659
617 001 503 516 526 523 526 523 654 000
683 675 686 683 999 642 874 316 002 000
110 111 000 000 100 000 001 011 111 000
Figure 7.5-9 Sample Decoded Display (General Housekeeping)
Page from Fuji-OSCAR 20.
JAS1b RA 91/01/13 00:40:58
Solar Panel Temp #1: 15.20 Deg.C Total Array Current:1105.89 mA
Solar Panel Temp #2: 31.92 Deg.C Battery Charge : 102.87 mA
Solar Panel Temp #3: 32.68 Deg.C Battery Voltage : 14.806 V
Solar Panel Temp #4: 29.64 Deg.C Battery Center : 6.744 V
Baseplate Temp. #1 : 40.73 Deg.C Bus Voltage : 17.259 V
Baseplate Temp. #2 : 41.42 Deg.C +5 V Regulator : 5.214 V
Baseplate Temp. #3 : 40.87 Deg.C -5 V Regulator : 0.000 V
Baseplate Temp. #4 : 41.14 Deg.C +10 V Regulator : 10.471 V
Temperature Cal. #1: 1.30 V Offset Voltage #1 : 0.000 V
Temperature Cal. #2: 1.29 V Offset Voltage #2 : 0.000 V
Temperature Cal. #3: 1.75 V Calibration Volt #2: 1.230 V
Battery Temp. : 45.04 Deg.C JTA TX Output Power: 0.46 W
JTD Temperature : 42.12 Deg.C JTD TX Output Power: 3.52 W
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 101
8.0 Spacecraft No Longer Active
This section is provided for post mission analysis of digital data
from spacecraft that are no longer active in case you have access to
data from those satellites and wish to the tools in WHATS-UP to view
and analyze the data.
8.1 Fuji-OSCAR 12
The FO-12 PSK Telemetry Data Format. It is practically identical to
the FO-20 format. The format is shown in Table 8.1-1, the decoding
equations are presented in Table 8.1-2.
Table 8.1-1 Fuji-OSCAR 12 PSK Telemetry Frame Format
Table 8.1-1 Fuji-OSCAR 12 PSK Telemetry Frame Format
JAS-1 FF YY/MM/DD HH:MM:SS
xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx
xxx xxx xxx xxx xxx xxx xxx xxx xxx xxx
xxx xxx xxx xxx xxx xxx xxx xxx yyy yyy
sss sss sss sss sss sss sss sss sss sss
FF := Frame Identifier RA: Realtime Telemetry - ASCII
RB: Realtime Telemetry - Binary
SA: Stored Telemetry - ASCII
SB: Stored Telemetry - Binary
M0: Message #0
M1: Message #1
.......
M9: Message #9
YY/MM/DD = Date
HH:MM:SS = Time (The command station attempts to keep the clock
as close as possible to UTC)
[ Following is valid only for RA and SA frames ]
xxx = 000 - 999 Format: 3 digit decimal (Analog Data) 28
samples in row 0 column 0 through row 2 column 7
(denoted #00 - #27 below)
y = 0 - F one byte Hex (System Status Data)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 102
9 samples in row 2 column 8 through row 2 column 9
(denoted #28a - #29c below)
s = 0 or 1 Binary Status Data
30 samples in row 3 through row 3 column 9
(denoted #30a - #39c below)
Table 8.1-2 Fuji-OSCAR 12 Telemetry Calibration Equations
Ch. Item Equation Units
#00 Total Solar Array Current 1.91 * ( N - 4 ) mA
#01 Battery Charge/Discharge 3.81 * ( N - 528 ) mA
#02 Battery Voltage N * 0.0210 V
#03 Half-Battery Voltage N * 0.00937 V
#04 Bus Voltage N * 0.0192 V
#05 + 5 V. Regulator Voltage N * 0.00572 V
#06 - 5 V. Regulator Voltage N * -0.00572 V
#07 +10 V. Regulator Voltage N * 0.0116 V
#08 JTA Power Output 5.1 * ( N - 158 ) mW
#09 JTD Power Output 5.4 * ( N - 116 ) mW
#10 Calibration Voltage #2 N / 500 V
#11 Offset Voltage #1 N / 500 V
#12 Battery Temperature 0.139 * ( 689 - N ) Deg. C
#13 JTD Temperature 0.139 * ( 689 - N ) Deg. C
#14 Baseplate Temperature #1 0.139 * ( 689 - N ) Deg. C
#15 Baseplate Temperature #2 0.139 * ( 689 - N ) Deg. C
#16 Baseplate Temperature #3 0.139 * ( 689 - N ) Deg. C
#17 Baseplate Temperature #4 0.139 * ( 689 - N ) Deg. C
#18 Temperature Calibration #1 N / 500 V
#19 Offset Voltage #2 N / 500 V
#20 Facet Temperature #1 0.38 * ( N - 684 ) Deg. C
#21 Facet Temperature #2 0.38 * ( N - 684 ) Deg. C
#22 Facet Temperature #3 0.38 * ( N - 690 ) Deg. C
#23 Facet Temperature #4 0.38 * ( N - 683 ) Deg. C
#24 Facet Temperature #5 0.38 * ( N - 689 ) Deg. C
#25 Temperature Calibration #2 N / 500 V
#26 Temperature Calibration #3 N / 500 V
#27 Depth of Battery discharge ( N - 500 ) / 189 AH
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 103
Fuji-OSCAR 12 System Status Telemetry Bytes
Ch. Item
#28a Spare (TBD)
#28b Spare (TBD)
#28c Memory Unit #0 error count
#29a Memory Unit #1 error count
#29b Memory Unit #2 error count
#29c Memory Unit #3 error count
Fuji-OSCAR 12 Binary Status Data Points
Ch. Item 1 0
#30a JTA Power On Off
#30b JTD Power On Off
#30c JTA Beacon PSK CW
#31a UVC Status On Off
#31b UVC Level 1 2
#31c Main Relay On Off
#32a Engineering Data #1 ---- ----
#32b Battery Status Tric Full
#32c Battery Logic Tric Full
#33a Engineering Data #2 ---- ----
#33b PCU Status Bit 1 (LSB)
#33c PCU Status Bit 2 (MSB)
#34a Memory Unit #0 On Off
#34b Memory Unit #1 On Off
#34c Memory Unit #2 On Off
#35a Memory Unit #3 On Off
#35b Memory Select Bit 1 (LSB)
#35c Memory Select Bit 2 (MSB)
#36a Engineering Data #3 ---- ----
#36b Engineering Data #4 ---- ----
#36c Computer Power On Off
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 104
#37a Engineering Data #5 ---- ----
#37b Solar panel #1 Lit Dark
#37c Solar panel #2 Lit Dark
#38a Solar panel #3 Lit Dark
#38b Solar panel #4 Lit Dark
#38c Solar panel #5 Lit Dark
#39a Engineering Data #6 ---- ----
#39b CW beacon source CPU TLM
#39c Engineering Data #7 ---- ----
8.2 SARA-OSCAR 23
On 17 July 1991, the attention of AMSAT and the rest of world's
amateur radio satellite communicators was focused on UoSAT-F. UoSAT-
F became UoSAT 5 when it separated from the launcher and another
OSCAR carrying a packet amateur communications payload was in orbit.
The University of Surrey calls the spacecraft UO-5, AMSAT and radio
amateurs call it OSCAR 22 or UO-22. UO-5/UO-22 is a scientific
satellite similar to UO-4, launched in 1990.
Hardly anyone noticed that the same Ariane launch vehicle carried
the SARA spacecraft, which became OSCAR 23 a few seconds after
UoSAT-F became UoSAT-5. SARA-OSCAR 23 (SO-23) was built at
ESIEESPACE, an aerospace club at the Ecole Superieure d'Ingenieurs
en Electrotechnique et Electronique (ESIEE), in France. SARA is the
culmination of six years of development work which included building
payloads for balloon and sub orbital rocket launches.
SARA is not an amateur radio communications satellite. Although not
as complex, it is also an educational and experimental satellite
similar to the spacecraft built at the University of Surrey in
England, (UO-1, UO-2, UO-3, UO-4 and UO-5). It holds (and identifies
using) the callsign FX0SAT. SARA stands for "Satellite for Amateur
Radio Astronomy".
Radio astronomy was born in 1932 with the discovery by Karl Jansky
at the Bell Telephone Laboratories in New Jersey that radio waves
were coming from a source in the sky. SARA is not amateur radio's
first connection with radio astronomy. In 1937, Grote Reber, W9GFZ,
designed and built the world's the first radio telescope, a 31ft.
(9.4m) dish antenna, in his own backyard in Wheaton, IL. Using this
antenna, he discovered the first discrete radio sources in the sky
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 105
and mapped the distribution of radio emissions in the Milky Way.
Grote Reber was the only person doing research in Radio Astronomy
before World War II and single-handedly brought radio astronomy to
the attention of professional astronomers. Like Grote Reber, SARA is
also a pioneer, albeit with a two fold mission.
8.2.1 The Primary Mission
SARA's primary mission was a Radio Astronomy Experiment to listen
for hf radio signals from Jupiter's radio-electric activities in the
decametric wavelengths. Jupiter is known to be emitting radio noise
in the hf frequency bands. This Jovian DX cannot be investigated by
a terrestrial station because for much of the time, either the Earth
or its atmosphere blocks the signals. In the past, a few other
satellites have measured the Jovian emissions, but not for a long
enough period of time to achieve meaningful results.
Jupiter's radio emissions in the decametric band is powerful enough
to wipe out all other natural extra terrestrial signal sources under
normal conditions. In the vicinity of the earth, the flux received
from Jupiter ranges from 10.E-20 to 5.10.E-19 W.m^-2.Hz^-1 which is
much stronger than the galactic background noise. During the Sun's
calm period, the flux received from the sun is about 10.E-24 W.m^-
2.Hz^-1. During periods of high solar activity it increases to 10.E-
17 W.m^-2.Hz^-1. The solar eruptions can be distinguished from the
Jovian signals by their signal strength, length of time, and by
correlation with signals received on other wavelengths. Jupiter's
radio activity in the decametric band is partially known: above 15
MHz the ionosphere sometimes becomes transparent and makes it
possible to do some measurements, which can then be extrapolated to
the 2 to 15 MHz band.
The Jovian decametric emission is irregular. It occurs mostly
during storms that last from periods ranging from one minute to an
hour. Depending on the type of storm, radio-electrical energy is
concentrated into peaks of 1 to 50 mS or 1 to 10 S, in frequency
bands about 50 KHz wide sweeping across the spectrum. These storms
are closely related to the rotation of Jupiter's satellite Io and to
Jupiter's own rotation. Solar eruptions may also influence them.
Voyager 1 carried out reception tests in the vicinity of Jupiter,
but because of electromagnetic interference from its own instruments
in the decametric band, it could only detect the strongest peaks of
the Jovian emissions. To date, no measurements have yet been made in
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 106
the 2 to 15 MHz band during a period of high solar activity. SARA is
a pioneer following a voyager.
The radio-electrical waves are received by means of three pairs of
aerials placed perpendicularly to each other. This configuration
allows computation of the intensity of the field regardless of its
direction and polarization.
As the received electromagnetic field is quite strong, three pairs
of short aerials, five meters long are used. One of the pairs is
also used to downlink telemetry data to earth in the 2 m band. The
aerials are made of 100 mm wide steel tape. They were rolled up for
the launch and unrolled themselves as soon as they were freed in
orbit.
The Jovian emissions between 2 and 15 MHz are measured on eight
channels, each of them 100 KHz wide. The on board equipment averages
their amplitude over a time interval of 150 S. The average amplitude
produces the envelope of the storms but hides the peaks, which
represent the internal structure of the storms. A single receiver is
switched between the channels and between the three pairs of
aerials. The receiver thus gets in succession the three
polarizations of each of the eight channels. This cycle is executed
several times during the 150 S to prevent the measurements on the
different channels from being separated in time.
The receiver has a 40 dB dynamic range in order to detect the
Jovian peaks as well as certain solar ones without saturating the
receiver. This allows for enough sensitivity to detect the galactic
background noise which is constant at a known level, and which will
serve as a reference standard when Jupiter and the sun are silent.
8.2.2 The Secondary Mission
Consider the reliability of the electronic components in a
spacecraft. SARA uses consumer-made components, rather than military
or space qualified parts, for reasons of cost and availability. Why
do professional satellites use the most expensive components, and
why did SARA do otherwise? The launch causes vibrations amounting to
10 g. Once the payload gets into orbit, outer space is a favorable
environment for electronic equipment. As a result, SARA is made from
components that have been tested and burnt in.
Commercial mass produced components are just as reliable as
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 107
conventional space qualified parts. For instance, a TV set that can
work for 10 years or more without needing repairs has to be built
out of very reliable components. While SARA doesn't use hardened
components, it doesn't use risky components either. Chemical
capacitors are banished, the Power Amplifier transistors are
oversized and well cooled, the PROMs are debugged after programming,
as advised by the manufacturer. SARA's equipment is simple and
conservatively designed and that is why, statistically, a long
operational life can be anticipated for the satellite.
8.2.3 The Downlink
The satellite circles the earth in 100 minutes on its low, sun
synchronous, quasi-polar orbit at an altitude of about 770 km
downlinking its data continuously. One telemetry transfer frame
cycle takes 2 minutes 48 seconds. An uplink command capability can
shut the beacon down if it causes QRM.
The downlink transmitter power of the satellite was about 1 W at
145.955 MHz. The carrier wave was modulated in amplitude with a +/-
3400 Hz spectrum using AFSK coding at frequencies of 1200 and 2200
Hz at a speed of 300 bits/s. The aerial polarization was linear.
8.2.4 The Onboard Electronics
The electronics are controlled by a sequencer because data
acquisition and transmission are made at different rates and times.
All the logic state machines required for the experiment are built
on a single printed circuit card, the remaining cards being analog
or combinational logic. This approach simplified the design of the
equipment and testing.
The sequencing card manages the measurements: it specifies the
frequency and the pair of aerials to be used by the receiver,
digitizes and stores the data, interprets received commands, and
prepares the telemetry. Data stored during a 24 hour time period is
time-tagged and downlinked in telemetry cycles lasting a few
minutes.
The functions described above are performed by a microcontroller.
As the program must operate over a period of years in spite of
errors that could occur due to interference or ionizing particles,
it will be reset regularly.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 108
8.2.5 The Power System
The power system supplies power to the electronics equipment, and
also started the satellite up after the launch, having detected the
separation from the launcher. After a proper time delay, the energy
system freed the aerials and started supplying power to the
equipment. The equipment needs about 3 W and uses a non-regulated
voltage bus that is locally regulated to 5 V.
During certain times of the year, the satellite is eclipsed by the
earth for up to a third of each orbit. A storage battery is thus
used as a permanent power supply. The battery is charged when sun
shines on the photovoltaic cells. The battery is protected against
overloading.
Because the satellite does not have an attitude control system,
sunlight can hit it from any direction. Solar cells were placed on
each side of the space craft, which is in the form of a cube. Its
size was calculated so that each side is able to supply power for
the whole experiment. This means 60% of the surface of the 470 mm
cube was covered with high quality cells.
Separation from the launcher was detected by a push button that
directly controlled the power supply for the on-board experiment and
the cutter to free the aerials. In addition, the power supply is
controlled by a security circuit.
8.2.6 Mechanical integration
Integration is based on a single plate 400 mm by 400 mm, on which
everything else is mounted; the electronic equipment, the aerials,
the solar cells, the interface with the launcher and the manual
controls.
The solar cells are placed on two half shells made of aluminum
sheets that constitute the case when they are brought together. The
integration plate is easily accessible when they are removed. Each
piece of equipment is a box. The cables are directly connected to
the pieces they connect. The whole mechanical structure is made of
aluminum pieces. The junctions that carry strains are soldered. The
spacecraft when assembled is a cube measuring about 470 mm each
side.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 109
8.2.7 Thermal Control
To accomplish their mission, the electronic equipment and the
batteries need moderate temperatures. These temperatures can be
achieved using passive controls. The internal temperature only
depend on exterior conditions (Sun and Earth) and on the satellite's
characteristics.
The target temperature is an average of + 20 C, which can be
achieved by choosing appropriate coatings for the external surfaces
of the satellite. About 40% of the surface was not covered with
solar cells and was thermally coated. The shape of the box was
chosen so as to have a quasi-constant section in all directions,
temperature being then independent from the orientation of the
satellite relative to the sun. The equipment dissipates 3 W and does
not modify the thermal balance of the structure.
The heat must be able to pass easily from the lighted sides to the
dark ones so that temperatures remain close to the average. The
problem is simplified by the small size of the satellite, and by the
use of aluminum shells 2 mm thick which are enough to limit the
thermal gap to 30 degrees. The satellite then does not need to be
spun to maintain thermal control.
8.2.8 Educational Opportunities
SARA provided a unique educational opportunity in orbital dynamics.
The radio signals SARA monitored are generated by the interaction
between Jupiter and and one of its moons (Io) as a beam of radio
energy. Why? How? The signals are synchronized to sidereal time and
appear roughly four minutes earlier successive day. Why? It takes
about two hours for the beam to swing across the earth. Why?
Ideally SARA should have been placed in an orbit in which the earth
never gets between the spacecraft and Jupiter. SARA however took the
orbit the Ariane rocket gave it, an orbit optimized for the primary
payload, the Earth Resources Satellite (ERA-1). When the earth gets
between SARA and Jupiter there will be breaks in reception of Jovian
signals for up to 40 minutes each orbit.
Plot the current positions of Jupiter and the Earth in the solar
system. Look at the angles between Jupiter and the orbital plane of
SARA around the Earth. Does the Earth eclipse SARA? If so, how long
before the geometry is such that SARA will get uninterrupted viewing
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 110
of Jupiter? If SARA has uninterrupted viewing, how long will this
condition last? If SARA receives signals when it is eclipsed by the
earth, what are they and where are they coming from?
8.3 ARSENE
The ARSENE satellite was launched in the spring of 1993. It carried
a conventional AX.25 digipeater using frequency modulated (FM)
uplinks and downlinks. Unfortunately ARSENE's 2 meter downlink
failed during launch. Several stations made contacts via the S Band
transponder until it also failed several months later.
ARSENE began in the early 1980's about the same time as Phase 3.
The spacecraft is built from parts left over from other projects by
students and apprentices. ARSENE was 3 axis stabilized and carried
two transponders, Mode B (digital) and Mode S (analog). The Mode S
downlink is linear on 2446.540 MHz (0.8W). The uplink was centered
on 435.110 MHz with a 16 kHz Bandwidth. The mode B uplinks were
digital at 435.050, 435.100 and 435.150 MHz, the downlink was on
149.975 MHz (15/2W) using standard AX.25 FM equipment. The orbit is
36000 km apogee with a 20000 km perigee at an inclination of 0
degrees. This results in an orbit with an approximate 16 hour
period.
8.3.1 Arsene Telemetry Equations
This information is provided in case anyone has any ARSENE
Telemetry. The ARSENE packet beacon transmitted 30 analog telemetry
channels providing information about the function of the different
on-board modules on the satellite. The telemetry decoding equations
for the analog telemetry channels are shown below.
Channel Units Parameter Equation
A3 I Battery unload current y=1.664v +0.198
A4 V Battery end charge threshold y=1.008v +12.94
A5 V Battery voltage y=2v +8.72
A6 W VHF PA output power y=0.05v^3+0.531v^2+0.25v
A7 V Primary bus voltage y=7.152v
A8 I VHF PA current (10 V) y=0.365v +0.149
A9 I VHF PA current (26 V) y=0.365v +0.149
A11 V RSSI voltage TC channel y=v
A13 I Primary bus current y=0.619v +0.019
A15 V First VHF PA voltage y=9v
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 111
A17 I Solar generator current y=0.573v
A18 I Dc-dc converter input current y=0.256v +0.02
A19 I Shunt regulator current y=0.669v -0.185
A21 I Battery load current y=0.174v -0.027
A22 T Battery temperature y=14v
A23 T Solar generator #1 temper. y= - 0.679033v^5 +
9.57784v^4 -
51.2412v^3 +
127.622v^2 - 170.345v
+ 97.7918
A24 T Solar generator #5 temper. y= - 0.679033v^5 +
9.57784v^4 -
51.2412v^3 +
127.622v^2 - 170.345v
+ 97.7918
A38 V Fifth battery element voltage y=0.982v + 3.258
A42 T Plateau temperature y= - 0.337702v^5 +
4.60193v^4 -
25.4481v^3 +
71.3428v^2
-119.362v + 109.681
A44 T Shunt regulator temperature y= - 0.337702v^5 +
4.60193v^4 -
25.4481v^3 +
71.3428v^2 - 119.362v
+ 109.681
A46 T Solar generator #3 temperature y= - 0.771085v^5 +
10.2258v^4 -
51.6250v^3+123.311v^2
- 154.219v + 62.7882
A48 T Electro gates 5-6 temperature y= - 0.337702v^5 +
4.60193v^4 -25.4481v^3
+ 71.3428v^2
- 119.362v + 109.681
A53 P Nitrogen tank pressure y=69.463v
A54 T VHF PA temperature y= - 0.337702v^5 +
4.60193v^4 -
25.4481v^3 +
71.3428v^2 - 119.362v
+ 109.681
A55 T Nitrogen tank #4 temperature y= - 0.337702v^5 +
4.60193v^4 -
25.4481v^3 + 1.3428v^2
-119.362v + 109.681
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 112
A58 V RSSI voltage channel 1 y=v
A60 V RSSI voltage channel 2 y=v
A62 V RSSI voltage channel 3 y=v
A69 T Nitrogen tank #1 temperature y= - 0.337702v^5 +
4.60193v^4 -
25.4481v^3 +
71.3428v^2 - 119.362v
+ 109.681
A71 V Dosimetre 5 experiment y=v
The telemetry value of each channel is between 0-255. This
corresponds to a voltage "v" between 0 - 5 Volts. The real value "y"
of measured parameters is calculated from the formulas.
- Voltage V in Volt.
- Current I in Amp.
- Temperature in Celsius.
- Pressure P in Bars and power W in Watt.
The next table gives the normal range and the alarm thresholds of
different channels:
Alarm threshold
Channel Normal Values Low High Parameter
A3 0 - 6.954 A 0 7.054 A Unload
battery
current
A4 14.850 - 17.055 V 14.850 17.055 V End charge
battery
threshold
A5 12.089 - 16.386 V 12.011 16.503 V Battery
voltage
A6 0.859 - 20.539 W 0.859 20.539 W VHF PA
output power
A7 25.982 - 26.960 V 25.004 27.938 V Primary bus
voltage
A8 0 - 1.412 A 0 1.466 A VHF PA
current
(10V)
A9 0 - 1.412 A 0 1.466 A VHF PA
current
(26V)
A11 0.195 - 4.688 V 0.039 4.883 V RSSI voltage
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 113
TC channel
A13 0.055 - 2.002 A 0.043 2.098 A Primary bus
current
A15 9.668 - 26.895 V 9.141 27.949 V First VHF PA
voltage
A17 0.705 - 2.596 A 0.504 2.697 A Solar
generator
current
A18 0.050 - 0.760 A 0.030 0.915 A Dc-dc
converter
input
current
A19 0.102 - 1.801 A 0.050 2.206 A Shunt
regulator
current
A21 0.072 - 0.721 A 0.072 0.721 A Battery load
current
A22 7.227 - 31.563 .xC 6.680 31.836 .xC Battery
temperature
A23 -70.734 - 9.656 .xC -80.688 19.609 .xC Solar
generator #1
temperature
A24 -69.969 - 9.656 .xC -79.922 20.375 .xC Solar
generator #5
temperature
A38 5.502 - 7.401 V 5.406 7.497 V Fifth
battery
element
voltage
A42 -19.672 - 40.125 .xC -21.016 40.797 .xC Plateau
temperature
A44 -19.672 - 40.125 .xC -21.016 40.797 .xC Shunt
regulator
temperature
A46 -30.422 - 30.047 .xC -31.766 40.125 .xC Solar
generator #3
temperature
A48 -19.672 - 40.125 .xC -21.016 40.797 .xC Electro gate
5-6
temperature
A53 3.984 - 190.313 Bars 1.641 199.688 Nitrogen
tank
pressure
A54 -17.988 - 41.809 .xC -19.332 42.481 .xC VHF PA
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 114
temperature
A55 -19.672 - 40.125 .xC -21.016 40.797 .xC Nitrogen
tank #4
temperature
A58 0.195 - 4.688 V 0.039 4.883 V RSSI voltage
channel 1
A60 0.195 - 4.688 V 0.039 4.883 V RSSI voltage
channel 2
A62 0.195 - 4.688 V 0.039 4.883 V RSSI voltage
channel 3
A69 -19.672 - 40.125 .xC -21.016 40.797 .xC Nitrogen
tank #1
temperature
A71 0.488 - 0.508 V 0.488 0.508 V Dosimetre 5
voltage
8.3.2 ARSENE Digital status telemetry
ARSENE packet beacon also transmitted 9 status bytes containing
status information of some of the modules aboard the vehicle.
There are first two words STA and STB that give 15 status bits ST1
to ST16, four words X1 to X4 for message handling and three words
T1, T2 and T3 representing counters.
The next table give the significance of bits ST1-ST16.
SIGNIFICANCE
WORD Bit MODULE State 1 State 0
STA ST1 TNC 1 On Off
STA ST2 TNC 2 On Off
STA ST3 TNC 3 On Off
STA ST4 VHF transmission CIM TLM Packet
STA ST5 VHF power Low Normal
STA ST6 Experim. power supply On Off
STA ST7
STA ST8 Squelch Off On
STB ST9 Battery regulator On Off
STB ST10 OK to load battery Yes No
STB ST11 Battery loading mode Normal Housekeeping
STB ST12 Packet transponder On Off
STB ST13 Mode B or S B packet S Linear
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 115
STB ST14 10 Volts power supply On Off
STB ST15 High pressure gates Open Closed
STB ST16 ACS power supply On Off
Here is an example of the packet beacon telemetry format that had
been received at F6BVP during a test of the ARSENE packet
transponder performed during winter 1991 to validate the circuits
designed by Gerard F6FAO and to verify the software coded by Antoine
F6DWJ.
ARSENE-1>MESURE-3:
1 1X10 2A53 3A69 4A38 5X20 6A54 7A22
2 1X30 2A55 3A71 4A40 5X40 6A56 7A24
3 1STA 2A90 3A17 4A42 5STB 6A58 7A18
4 1A30 2A11 3A19 4A44 5A40 6A60 7T10
ARSENE-1>MESURE-3:
5 1A50 2A13 3A21 4A46 5A60 6A62 7T20
6 1A70 2A15 3A23 4A48 5A80 6A64 7T30
ARSENE
ARSENE
8.4 AO-21 (RM-1)
AO-21 (AO-21) was launched in February 1991 from the North
Cosmodrome at Plesetsk. The orbit is a slightly elliptical polar
orbit with an apogee of 1000 km at an inclination of 83 degrees. The
period of the orbit will be 105 minutes.
AO-21 was the first international OSCAR in which radio amateurs
from the Soviet Union took part. RM1 stands for "RADIO M-1", which
is the official prelaunch name of AO-21, emphasizes that the
spacecraft was built by, and for, Radio Amateurs around the world.
The idea of a joint effort between the two groups, one in the USSR
and the second, in Germany first appeared in the spring 1989. The
discussions about what and how things had to be done lasted till the
meeting of the representatives of the two groups in Surrey in July
1989 when the preliminary agreement about the cooperation was
signed. The final version of the cooperation agreement was later
signed in the autumn of 1989 after much of the work had been
completed.
According to the mutual agreement, Amsat-U-Orbita developed and
made the linear transponder, command radio link, telemetry system,
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 116
power supply system and decided all the problems with the official
and other government organizations about the location of the
equipment and launching.
The RUDAK group of AMSAT-DL developed and built the digital part,
called RUDAK-2 which contains a digipeater and an AX.25 mailbox. It
also provides other possibilities for experiments in transmitting of
information using modern digital methods. It also contains its own
RF input and output circuits.
The ground command station was developed by the Amsat-U-Orbita and
Amsat-U-Sputnik groups. The Rudak group however provided some
special digital part for it.
During the launch and orbital test period ground, the command
stations were UC1CWA situated in Molodechno and RK3KP in Moscow. The
ground command stations for Rudak-2 are situated near Munich at
DK1YQ and near Hanover, at DB2OS. The final agreement was signed on
behalf of Amsat-U-Orbita by the technical director of project
"RADIO-M1" - V.Chepyzhenko, RC2CA; and on behalf of AMSAT-DL, by
their president, K. Meinzer, DJ4ZC. The Project Manager for the
RUDAK-2 is Hanspeter Kuhlen, DK1YQ. The coordinators for the project
are P. Guelzow, DB2OS and L. Labutin, UA3CR.
AO-21 was an attached secondary payload (Piggy-back) aboard a USSR
geological research satellite which provides a Mode B communications
transponder in low earth orbit as well as an orbiting experimental
digital communications capacity.
The AO-21 Specifications are as listed below.
Dimension and shape: Cylinder of height about 4 meters and
diameter 1.8 meters
System configuration: Professional geological research equipment,
telemetry system, command link equipment, transponders and
power supply, thermal control. Amateur linear and digital
transponders, telemetry system, command link equipment, power
supply.
Attitude control: Satellite attitude will be maintained using a
gravity gradient approach in the form of a rod 9 meters long
pointing away from the earth.
Planned service life: 3 years.
Two sets of the equipment are installed aboard the satellite:
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 117
Linear transponder #1 is Mode B and contains the RUDAK-2 and other
subsystems, while Linear transponder #2 mode B with subsystems The
Primary transponder is Linear Transponder #1, the second one is a
spare which can be put into operation in the event of a failure of
the primary system. Mode B in low earth orbit provides a very good
communications link as anyone who worked AO-7 Mode B will testify.
The Transponder RF Frequency Assignments and Beacon Data for the
Primary Payloads are shown in Table 8.4.1, and those for the Backup
payload in Table 8.4-2. The 1100 bps is not a misprint, it is real.
Apparently this data rate is used by a popular PC tape cassette
interface in the Soviet Union. Because this PC is simple and cheap
for the Hams in the USSR, the AMSAT-U-Orbita team decided to use it
on this spacecraft, much in a similar manner to the use of reversed
AFSK tones in UO-2 due to the wide availability of a popular
interface for those tones in the United Kingdom. It is unclear as of
the time of writing this, if the telemetry is HDLC or some
proprietary synchronous PSK such as the 400 baud AO-13 downlink. As
such you may not be able to copy this telemetry.
Table 8.4-1 Primary Payload
Beacons and telemetry #1
CW telemetry 8 channels 145.822 MHz 0.2 Watts
Digital telemetry 30 channels 145.952 MHz 0.4 Watts
1100 bps,BPSK/FM, deviation 2kHz
Digital telemetry
Rudak-2 145.983 MHz 3.0 Watts
BPSK 1200 bps AX.25 (like F-O 20)
Transponders #1
Linear transponder: inversely heterodyned translator
Uplink passband 435.102 to 435.022 MHz
Downlink passband 145.852 to 145.932 MHz
Transmitter output max. 10 Watts
Bandwith (3db) 80 kHz
Uplink EIRP required about 100 Watts
Digital transponder Rudak-2: digipeater and store&forward packet
communication (AX.25), telecommunications experiment with digital
signal processing up to nearly 20 kHz, 1 MByte RAM disc, four
separate uplink channels.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 118
Uplink frequencies:
RX-1 435.016 MHz 1200bps,FSK,NRZIC/Biphase-M
RX-2 435.155 MHz (AFC) 2400 bps,BPSK, Biphase-S
RX-3a 435.193 MHz (AFC) 4800 bps,RSM
RX-3b 435.193 MHz (AFC) 9600 bps,RSM
RX-4 435.041 MHz (digital AFC) RX for RTX-DSP
Downlink frequency: 145.983 MHz 3 Watts
The downlink can be switched to the following operating modes:
Mode 1: 1200 bps, BPSK, NRZI,(NRZ-S) (like FO-20)
Mode 2: 400 bps, BPSK, Biphase-S (Like AO-13 beacon)
Mode 3: 2400 bps, BPSK, Biphase-S
Mode 4: 4800 bps, RSM, NRZIC (Biphase-M) (like 4800 bps uplink)
Mode 5: 9600 bps, RSM, NRZI (NRZ-S) +Scrambler (like 9600 bps
uplink)
Mode 6: CW keying (only for special events)
Mode 7: FSK (F1 or F2B),e.g. RTTY, SSTV, FAX, etc.(for special
events)
Mode 8: FM modulated by D/A signals from DSP-RISC processor (speech)
Table 8.4-2 Secondary Payload
Beacons and Telemetry #2
CW telemetry 8 channels 145.948 MHz 0.2 Watts
Digital telemetry 30 channels 145.838 MHz 0.4 Watts 1100 bps,
BPSK/FM, deviation 2kHz
Digital telemetry 30 channels 145.800 MHz 2.0 Watts 1100 bps
BPSK/FM, deviation 2kHz
Transponder #2
Linear transponder: inversely heterodyned translator
Uplink passband 435.123 to 435.043 MHz
Downlink frequencies 145.866 to 145.946 MHz
Transmitter output max. 10 Watt max.
Bandwith (3db) 80 kHz
Uplink EIRP required about 100 Watts
The spacecraft uses two antennas. The 435 MHz receiving antenna
which is shared by the analog and digital modes is a Helix with up
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 119
to +3 db gain using Right Hand circular Polarization. The 145 MHz
transmitting antenna is a Half wave dipole. AO-21 draws up to 100
Watts from the main spacecraft's power supply system. The Primary
RM-1 payload including the RUDAK draw up to 47 Watts, the secondary
payload draws up to 40 Watts. The Primary AO-21 payload including
the RUDAK weighs approximately 28 kg, the secondary payload weighs
approximately 22 kg. Both payloads are about 480x400x300 mm^3.
The CW telemetry started up as soon as the combined spacecraft
separated from the launch vehicle and was powered by main satellite
power system. A CW Morse-Code telemetry frame consists of the call
RS14 and 8 channels of four digits in the following format:
RS14 S0AB=S1AB=S2AB=S3AB=S4AB=S5AB=S6AB=S7AB
Channels 0 to 6 contain analog telemetry data. Channel 7 contains
engineering calibration parameters.
The first digit (S) identifies which system the telemetry is from.
A prefix of 7 identifies a general status, a prefix of 5 identifies
a command status. The second digit (0 to 7) are the numbers of the
line (channel). The remaining digits (A and B) are the analog
telemetry data which can be decoded according to the equations shown
in Table 8.4-3.
Table 8.4-3 AO-21 CW Telemetry decoding parameters
Channel Parameter Formula Unit
0 Transponder power output 0.05*N Watts
1 Transponder PA Temperature N Deg. C
2 +24 V Regulated N Volt
3 +16 V Regulated N Volt
4 +9 V Regulated N Volt
5 +24 V Regulated N Volt
6 Inside Temperature N Deg. C
7 Engineering Value N *
A typical frame such as
"RS14=7080=7137=7224=7316=7409=5524=5032=57PPRS14"
may be decoded as shown below.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 120
RS14
7080 - 4 Watts - general
7137 - 37 Deg. C - general
7224 - 24 Volts - general
7316 - 16 Volts - general
7409 - 9 Volts - general
5524 - 24 Volts - command
5032 - 32 Deg. C - command
57PP - command (transponder #1)
Examples of other frames copied and edited by G3ZCZ/W3 are
28-Feb-91 01:40 RS14=7032=7121=7224=7316=7410=7500=7600=77PP
01-Mar-91 02:19 RS14=7028=7121=7224=7316=7410=7500=7600=77PP
The "PP" at the end of the frame identifies the telemetry as having
come from transponder #1. Transponder #2 identifies its telemetry
with the "PPPP" sequence.
The AO-21 Digital PSK telemetry consists of 30 parameters
monitoring on-board conditions and 2 calibration verification
points. If you intend to receive, decode and display the digital
telemetry you will need an FM receiver, a TNC, a PSK modem, and a
computer or terminal. Even then you may not be able to decode the
data since it may not be downlinked in HDLC format. The decoding
equations for the digital telemetry are shown in Table 8.4-4. The
raw digital telemetry is expected to show up on your screen in the
format shown in Table 8.4-5.
Table 8.4-4 Decoding Equations for AO-21 Digital Telemetry
(Version 26-Dec-90)
Line Parameter Formula Unit Hex-Format-Line
1 "Zero" of the comparator 0C N/A 0000
2 Reference voltage 6D N/A 0010
3 Transponder #1 HF output pwr 0.2N^2 Watt 0020
4 Transponder #1 PA temperature 0.8*N Deg. C 0030
5 DC/DC converter temperature 0.8*N Deg. C 0040
6 +14 V Regulated 10*N Volt 0050
7 +24 V Regulated 10*N Volt 0060
8 +16 V Regulated 10*N Volt 0070
9 +12 V Regulated 10*N Volt 0080
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 121
10 +9 V Regulated 10*N Volt 0090
11 +7.5 V Regulated 10*N Volt 00A0
12 +5 V Regulated 10*N Volt 00B0
13 +9 V Regulated (linear) 10*N Volt 00C0
14 +9 V Regulated (digital) 10*N Volt 00D0
15 Service N * 00E0
16 Service N * 00F0
17 Transponder #2 HF output pwr 0.2*N^2 Watt 0100
18 Transponder #2 PA temperature 0.8*N Deg. C 0110
19 +24 V Regulated 10*N Volt 0120
20 +16 V Regulated 10*N Volt 0130
21 +10 V Regulated 10*N Volt 0140
22 +9 V Regulated 10*N Volt 0150
23 +7.5 V Regulated 10*N Volt 0160
24 Status command link 1 * 0170
25 Status command link 2 * 0180
26 Status command link * 0190
27 Status command link * 01A0
28 RPC +5V for Rudak-1 2.47*N Volt 01B0
29 RPC +5V for Rudak-RTX 2.47*N Volt 01C0
30 RPC +5V for Ramdisk 2.47*N Volt 01D0
31 RPC +14V total supply current 627-289*N mA 01E0
32 RPC module temperature 56.7*N-49.5 Deg. C 01F0
Note: RPC - Rudak Power Conditioner. The Service and command link
channels are reserved for use by the ground control team.
Table 8.4-5 Expected Format of Raw AO-21 PSK Telemetry
0000 0C E6 0C E6 0C E6 0C E6 0C E6 0C E6 0C E6 0C E6
0010 6D E6 6D E6 6D E6 6D E6 6D E6 6D E6 6D E6 6D E6
0020 i E6 i E6 i E6 i E6 i E6 i E6 i E6 i E6
....................................................
01F0 j E6 j E6 j E6 j E6 j E6 j E6 j E6 j E6
i...j - the value of the parameter in the hex format, repeated 8
times E6 - separation
The RUDAK system is a message store-and-forward package. Its
downlink is not expected to contain any telemetry. An example of
some RUDAK signals copied by W3/G3ZCZ a few days after launch is
shown in Table 8.4-6.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 122
Table 8.4-6 Example of AO-21 RUDAK Signals.
26-Feb-91 02:31:36 RUDAK*>BEACON:
* RUDAK-II / AMSAT OSCAR 21/RM1
* Up: 435.016MHz (1200)
* 435.155MHz (2400)
* Mailbox=RUDAK Mheard=RUDAK-1
26-Feb-91 02:32:37 RUDAK*>BEACON:
RUDAK-Telemetry (91-02-25 23:03:00):
Used stack entries: 0
Uplink Carrier Detect (during last minute): 0%
26-Feb-91 02:33:36 RUDAK*>BEACON:
* RUDAK-II / AMSAT OSCAR 21/RM1
* Up: 435.016MHz (1200)
* 435.155MHz (2400)
* Mailbox=RUDAK Mheard=RUDAK-1
26-Feb-91 02:34:37 RUDAK*>BEACON:
RUDAK-Telemetry (91-02-25 23:05:00):
Used stack entries: 0
Uplink Carrier Detect (during last minute): 0%
26-Feb-91 02:35:09 RUDAK,*>WB5BZE (UA)
26-Feb-91 02:35:11 RUDAK*>WB5BZE:
+-------------------------------------------------------+
+ Welcome to the RUDAK II Bulletin Board System V0.04 +
+-----------
26-Feb-91 02:35:13 RUDAK*>WB5BZE:
--------------------------------------------+
Logged in at 91-02-25 23:05:33, 1 User
This is a preliminary release.
Please rep
26-Feb-91 02:35:15 RUDAK*>WB5BZE:
ort deficiencies to DL2MDL.
73 de AMSAT-UA/AMSAT-DL/RUDAK-Group.
Enter H for help.
WB5BZE de RUDAK>
26-Feb-91 02:35:36 RUDAK*>BEACON:
* RUDAK-II / AMSAT OSCAR 21/RM1
* Up: 435.016MHz (1200)
* 435.155MHz (2400)
* Mailbox=RUDAK Mheard=RUDAK-1
26-Feb-91 02:35:51 RUDAK*>WB5BZE [D]
26-Feb-91 02:35:56 RUDAK*>WB5BZE [D]
26-Feb-91 02:36:32 KF4WQ>RUDAK*>KF4WQ [C]
26-Feb-91 02:36:37 RUDAK*>BEACON:
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 123
RUDAK-Telemetry (91-02-25 23:07:00):
Used stack entries: 0
Uplink Carrier Detect (during last minute): 0%
26-Feb-91 02:37:35 RUDAK*>WB5BZE (UA)
The AO-21 Packet Telemetry is formatted for display in the
spacecraft and downlinked as ASCII packets. Typical packets are
shown below.
18-Jun-94 20:38:18 RUDAK2*>BEACON [UI]:
++ Hi, this is the RUDAK-II experiment on AMSAT OSCAR 21 ++
18-Jun-94 20:38:21 RUDAK2*>TLM-2 [UI]:
5V-RAM: 4.97 V 3-RNG : off AGC
total current 4-soft: 0.2 V RX3: 142 temperature
14V-I : 307 mA RX4: 207 21.6 deg C
chksum: 0 upcnt: 0 stack: 2 noint: 0
18-Jun-94 20:38:23 RUDAK2*>TLM-3 [UI]:
RAMDISK:
wash sectors memory errors audio sectors picture sectors
start: 3100 single: 215 start: 165 start: 3100
end : 4095 multi : 0 end : 2412 end : 3452
ptr : 3785 sample freq: 8000 chksum: -19652 (-19652)
18-Jun-94 20:38:24 RUDAK2*>BEACON [UI]:
RUDAK-II Schedule: (down 145.987, up 435.016)
min/10 Beacon Mode
0..8 FM Repeater
9 AFSK TLM
The same information seen without the headers is shown below.
5V-RAM: 4.97 V 3-RNG : off AGC
total current 4-soft: 0.2 V RX3: 142 temperature
14V-I : 307 mA RX4: 207 21.6 deg C
chksum: 0 upcnt: 0 stack: 2 noint: 0
RAMDISK:
wash sectors memory errors audio sectors picture sectors
start: 3100 single: 215 start: 165 start: 3100
end : 4095 multi : 0 end : 2412 end : 3452
ptr : 3785 sample freq: 8000 chksum: -19652 (-19652)
RUDAK-II Schedule: (down 145.987, up 435.016)
min/10 Beacon Mode
0..8 FM Repeater
9 AFSK TLM
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 124
9.0 File formats
This section contains details of the contents of the different
files used by WHATS-UP.
9.1 Configuration File (WHATS-UP.SYS)
The contents of the Configuration file (WHATS-UP.SYS) are as
follows:
1 Your callsign (e.g. G3ZCZ)
2 Default spacecraft configuration file (e.g. Dove)
3 station latitude (e.g. 35.00)
4 station longitude (e.g. 74.00)
5 station altitude (e.g. 100)
6 station minimum antenna elevation for acquisition (e.g. 0)
7 default Kepler file (e.g. whats-up.TLE)
8 UTC offset (e.g. EST = 5)
9 default directory path (e.g. C:)
10 default extracted data file (e.g. whats-up.txt)
11 default file name with list of telemetry parameters to extract
file (e.g. ARRAYS)
12 TNC Type (e.g. PK-232)
13 PC serial port to TNC (e.g. 1)
14 PC serial TNC port baud rate (e.g. 1200)
15 PC Serial TNC port data bits (e.g. 8)
16 PC Serial TNC port Stop bits (e.g. 1)
17 PC Serial TNC port parity (e.g. N)
18 status (top) window color (e.g. 79)
19 Incoming window color (e.g. 14)
20 outgoing window color (e.g. 30)
21 prompt window color (e.g. 15)
22 alarm window color (e.g. 15)
23 bottom window color (e.g. 79)
24 Emphasis color (e.g. 14)
25 option color (e.g. 78)
26 parameter changed color (e.g. 95)
27 parameter limit exceeded color (e.g. 14)
28 Orbit element window color
29 Orbit element window Orbit element window In range color
30 Orbit element window early warning color
31 Orbit element window next one up color
32 Logbook window color
33 SAREX call color in status window
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 125
34 Active color
35 Post pass color in orbit element window
36 Orbit alert dit time
37 Orbit alert note
38 Flag Sound
39 Doppler display Flag
40 DSP-1200 Modem CW command
41 DSP-1200 Modem 1200 ASCII command
42 DSP-1200 Modem 1200 PSK command
43 DSP-1200 Modem 400 PSK command
44 DSP-1200 Modem 9600 FM command
45 DSP-1200 Modem 1200 FM command
46 Logbook path and name (.DBF may be left out)
47 QSO Logging Flag
48 Minimum angle of the sun for darkness at your QTH
49 TNC stream switch character, default '|'
50 The next few lines link the spacecraft configuration files.
51 The * that follows denotes the last line of SC ID data.
52 CW Memory contents: - The next ten lines contain the cw memory
data.
54 The * marker line
55 The remaining lines contain TNC configuration parameters.
You must configure WHATS-UP before you try any Real Time activity.
The contents of the configuration file are described below.
9.1.1 Your callsign
This item is the callsign displayed at the top of the screen and
appended to the capture files when capture-to-disk is turned on.
9.1.2 Default spacecraft Name
This item is the default spacecraft name (e.g. Dove). WHATS-UP adds
the ".SYS" to the end of the name (e.g. DOVE.CNF) and loads that
configuration file at start up.
9.1.3 Station Latitude
This item is your station latitude (e.g. 35.00). In the southern
hemisphere, enter a negative number.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 126
9.1.4 Station longitude
This item is your station longitude in degrees WEST of Greenwich.
(e.g. 74.00)
9.1.5 Station Altitude
This item is the altitude of your station antenna above sea level
in Meters. (e.g. 100)
9.1.6 Station minimum antenna elevation for acquisition
This item is the minimum angle of elevation of your antennas at
which you can acquire a signal. If you are on top of a hill or tall
building the angle my be less than 0, if you are in a valley, it may
be greater, such as 5 degrees.
9.1.7 Default Kepler file
This item is the default file name that contains the orbit element
data used when the program is first turned on (e.g. whats-up.TLE).
9.1.8 UTC offset
This item is the time difference (in hours) between the local time
in your PC and GMT or Universal Coordinated Time (UTC). WHATS-UP
always displays UTC time. (e.g. EST = 5)
9.1.9 Default directory path (e.g. C:)
This item is the directory path (e.g. C:\TLM) for the spacecraft
capture-to-disk (YYMMDD.S/C), spacecraft configuration (*.CNF) and
spacecraft operations schedule files (*.OPS).
9.1.10 Default extracted data file
This item is the name of the file to which data which is extracted
from a playback file will be written to in a comma delimited format
so that the data can be imported into a spreadsheet package for
further analysis (e.g. whats-up.txt).
9.1.11 Default file name with list of telemetry parameters to
extract file
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 127
This item is the name of the file containing the channel numbers to
extract from a playback file for further analysis (e.g. ARRAYS)
9.1.12 TNC Type
This item is the type of TNC or Multi-mode controller you are
using.
9.1.13 Serial port to TNC
This item is the Communications port number between the TNC and the
PC (e.g. 1). If you set it to 0, WHATS-UP will never try to access
the TNC.
9.1.14 PC TNC Serial baud rate
This item is the baud rate used between the TNC and the PC (e.g.
1200).
9.1.15 PC TNC port data bits
This item is the number of data bits used between the TNC and the
PC (e.g. 8).
9.1.16 PC TNC port Stop bits
This item is the number of stop bits used between the TNC and the
PC (e.g. 1).
9.1.17 PC TNC Port parity bits
This item is the parity setting used between the TNC and the PC.
The letters to use are defined as
N No parity, O Odd, E Even, M Mark, S Space.
The following items are the color values used for different windows
or messages.
9.1.18 Status (top) window color (e.g. 79)
9.1.19 Incoming window color (e.g. 14)
9.1.20 Outgoing window color (e.g. 30)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 128
9.1.21 Prompt window color (e.g. 15)
9.1.22 Alarm window color (e.g. 15)
9.1.23 Bottom window color (e.g. 79)
9.1.24 Emphasis color (e.g. 14)
9.1.25 Option color (e.g. 78)
9.1.26 Parameter changed color (e.g. 95)
9.1.27 Parameter limit exceeded color (e.g. 14)
9.1.28 Orbit element window color
9.1.29 Orbit element window In range color
9.1.30 Orbit element window early warning color
9.1.31 Orbit element window next one up color
9.1.32 Logbook window color
9.1.33 SAREX call display color in Status window
9.1.34 Active color
9.1.35 Orbit element Post pass color
9.1.36 Orbit alert dit time
This item is the speed of the morse code annunciator used to alert
you of satellite AOS, EWT and LOS.
9.1.37 Orbit alert note
This item is the tone of the morse code annunciator used to alert
you of satellite AOS, EWT and LOS.
9.1.38 Flag Sound
This item controls the sounds coming from the PC. A
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 129
1 is on,
0 is off.
9.1.39 Doppler display Flag
This item determines the type of Doppler display as follows:-
0 display beacon frequency,
1 display Doppler shift.
9.1.40 TNC Command to select modem for CW
9.1.41 TNC Command to select modem for UoSAT ASCII 1200 baud
9.1.42 TNC Command to select modem for 1200 baud PSK
9.1.43 TNC Command to select modem for 400 baud AO-13 PSK
9.1.44 TNC Command to select modem for 9600 baud packet
9.1.45 TNC Command to select modem for 1200 baud FM AFSK
9.1.46 Logbook file
This item is the default file name for the logbook (e.g. vhf.dbf).
9.1.47 QSO Logging flag
This item is the flag that determines if acquisition of signal is
logged. A:
1 means log,
0 means don't log.
9.1.48 Minimum angle of the sun for darkness at your QTH
This item sets the value for viewing of satellites. To see a
spacecraft, the spacecraft must be in sunlight and the ground viewer
must be in darkness. This parameter lets you adjust the apparent sun
angle for darkness at your location. Note while some spacecraft may
be in sunlight, and you may be in darkness, the spacecraft may not
be bright enough to be visible with the naked eye. MIR and the space
shuttle are bright enough.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 130
9.1.49 TNC stream switch character, default '|'
9.1.50 Spacecraft Configuration File Linkages
The next few lines contain the information which WHATS-UP uses to
link the spacecraft configuration files to the Keplerian elements
for orbit determination and automatic selection of spacecraft at AOS
time. There should be NO SPACE characters before or between the
commas, in the first two data elements. The lines contain data as
shown below.
UO-11,UOSAT11.CNF, 0
AO-13,OSCAR13Z.CNF, 0
AO-16,PACSAT.CNF, 0
DO-17,DOVE.CNF, 1
WO-18,WEBER.CNF, 0
LO-19,LUSAT.CNF, 2
FO-20,FUJI.CNF, 0
The first item is the Keplerian element identifier for the
spacecraft as used in the orbit element files.
The second item is the FULL configuration file name for the
spacecraft.
The third item is the automatic AOS selection flag as itemized
below.
'0', automatic selection is inhibited.
'1', WHATS-UP selects that spacecraft configuration file at EWT
time (if it is not selected at that time), and tunes the radio
to the beacon frequency + offset defined in that file.
'2', WHATS-UP selects that spacecraft configuration file at AOS
time (if it is not selected at that time), and tunes the radio
to the beacon frequency + offset defined in that file.
9.1.51 Marker and Comment line
This line must be present and begin with an '*' character. It
signals WHATS-UP that the spacecraft default parameters have been
read.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 131
9.1.52 CW Memory contents
The next ten lines contain the cw memory data
9.1.53 The marker line
This line must be present and begin with an '*' character.
9.1.54 TNC configuration commands
The remaining lines are commands sent to the PK232 when you
configure the TNC. Note to avoid lock ups FLOW and XFLOW MUST be
OFF. Typical commands are as follows:-
HEAD ON
ECHO OFF
DAYSTAMP ON
MONITOR 6
MSTAMP ON
FLOW OFF
XFLOW OFF
MFILTER None
9.2 Spacecraft Parameter Files
You need a Different spacecraft parameter file for each spacecraft.
Spacecraft parameter files are named by the spacecraft and given the
extension '.CNF'. Examples are 'DOVE.CNF' and 'Fuji20.CNF'. These
files determine how the individual channels are decoded, and where,
in which screen page, and in which color the decoded data are
displayed. Some of the items are unique to WHATS-UP and some to the
particular spacecraft.
The entries in the file are:
1 Spacecraft ID
2 Spacecraft Suffix
3 Beacon Frequency
4 Doppler Measurement File
5 Spacecraft Identification in Keplerian Element File
6 Doppler Measurement Sample Interval
7 Initial Frequency Offset
8 Autotrack flag
9 Modulation
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 132
10 Data Type
11 Receiver Type
12 Receiver Address
13 PC Serial port to Radio
14 PC Radio port Serial baud rate
15 PC Radio port data bits
16 PC TNC port Stop bits
17 PC Radio Port parity bits
18 Post pass delay
19 Station minimum usable pass time
20 Early warning time
21 SAREX/Mir Callsign
22 SAREX/Mir Header Delay
23 SAREX/Mir Attack Mode
24 SAREX/Mir Beacon Text
25 LPT parallel port radio memory parameters
26 Selected or default display page number
27 MET Start Time
28 Page Definitions
29 Telemetry Parameter Configuration
30 Digital Telemetry Status Channels
31 Packet/Link Parameters
The contents of each line in the SPACECRAFT.CNF file are as
described below.
9.2.1 Spacecraft ID
This is the callsign of the spacecraft. For example,
Spacecraft ID.
---------------------
DO-17 DOVE-1
FO-20 8J1JBS
9.2.2 Spacecraft Suffix
This becomes the filetype for the capture-to-disk files. The
default suggestions are as shown below.
Spacecraft Suffix
UoSAT-2 U11
Fuji-OSCAR 12 F12
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 133
AMSAT-OSCAR 13 O13
AMSAT-OSCAR 16 O16
DOVE-OSCAR 17 D17
WEBER-OSCAR 18 W18
LUSAT-OSCAR 19 L19
Fuji-OSCAR 20 F20
AMSAT-OSCAR 21 O21
9.2.3 Beacon Frequency
This is the frequency of the spacecraft beacon (in MHz) that you
are monitoring. It will be displayed in the status window.
9.2.4 Doppler Measurement File
This is the default name of the file used to store the Doppler
frequency measurements.
9.2.5 Spacecraft Identification in Keplerian Element File
Examples are as follows.
UO-11 AO-13 AO-16 DO-17 WO-18 LO-19
9.2.6 Doppler Measurement Sample Interval
This is the default sample interval (in seconds) used between
Doppler frequency measurements.
9.2.7 Initial Frequency Offset
This is the default value (in kHz) added to the beacon frequency,
and output to the Radio Receiver when a particular spacecraft is
selected. The default value is 5 to tune the radio 5 kHz above the
beacon. This will allow the signal to slide into lock, whereby the
TAPR PSK Modem will lock on and follow the frequency for the rest of
the pass.
9.2.8 Autotrack flag
This item tells WHATS-UP if it should allow another AOS to
interrupt data collection from this spacecraft.
0 Don't let another AOS to interrupt collection.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 134
1 Allow another spacecraft AOS to interrupt collection, namely,
tune to that spacecraft at its AOS.
9.2.9 Modulation
This is the type of modulation to set the Radio to to copy data
from the spacecraft. Current options are :-
C CW
F FM L LSB
P PSK
U USB
D FM Duplex. Use this mode for SAREX. If duplex is selected, then
the uplink frequency (in MHz) must be added following the D and
separated by a comma character (i.e. D,144.49).
9.2.10 Data Type
This is the type of data downlinked by the spacecraft.
A ASCII as used by UoSAT-2.
B BAUDOT as used by AO-13.
C CW as used by AO-21.
P Packet as used by DO-17, Fuji-OSCAR 20 and the Microsats.
9.2.11 Receiver Type
This is the manufacturer of the radio receiver you are using. This
version of WHATS-UP supports the:
Kenwood series.
Lpt line printer parallel port.
Icom (not tested).
9.2.12 Receiver Address
The assignment is as follows:
9.2.12.1 Kenwood
Not used.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 135
9.2.12.2 LPT parallel port
This item defines the printer port as shown below.
Assignment Printer Port PC Assignment
Bit Address (Hex)
1 $0378 LPT1
2 $0278 LPT2
3 $03BC Custom for my laptop
For example, to use LPT1 as the printer port, set this value to 1.
You may use different ports for different radios on different bands
9.2.12.3 Icom
Set the line to the decimal value of the radio address according to
the Icom radio manual.
9.2.13 PC Serial port to Radio
This item is the Communications port number between the PC and the
Radio (e.g. 2). If you set it to 0, WHATS-UP will never try to
access the radio via the serial port. If you select the LPT radio
option, set this value to 0.
9.2.14 PC Radio port Serial baud rate
This item is the baud rate used between the PC and the Radio (e.g.
4800).
9.2.15 PC Radio port data bits
This item is the number of data bits used between the Radio and the
PC (e.g. 8).
9.2.16 PC TNC port Stop bits
This item is the number of stop bits used between the Radio and the
PC (e.g. 2).
9.2.17 PC Radio Port parity bits
This item is the parity setting used between the Radio and the PC.
The letters to use are defined as
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 136
N No parity, O Odd, E Even, M Mark, S Space.
9.2.18 Post pass delay
This item is the time (in minutes) that WHATS-UP after the computed
LOS time before returning the radio to the default frequency (e.g.
2). This delay is to be used in the event that the elements do not
quite predict the exact times for your system.
9.2.19 Station minimum usable pass time
This item is the minimum time in minutes for a usable pass for
collecting data (e.g. 5).
9.2.20 Early warning time (EWT)
This item is the early warning time in minutes you want for notice
that a spacecraft is about to come up above your local horizon (e.g.
5).
9.2.21 SAREX/Mir Callsign
This item is the callsign to which the automatic beacon/connect
attempt will be made. if you wish to beacon, then you must set the
'UNProto' parameter in the TNC to the digipeater callsign. for
example to beacon via MIR, when MIR is using R0MIR, then set the
SAREX call to R0MIR, and set the TNC parameter as 'UNP CQ VIA
R0MIR'.
9.2.22 SAREX/Mir Header Delay
This item is the number of packet headers to count before issuing
the next beacon packet. Try to resist the temptation to set it at a
low value.
9.2.23 SAREX/Mir Attack Mode
This item is the SAREX/MIR Attack mode. Options are to try:
B - both connect and digipeat
C - connect to SAREX call
Q - call CQ via the SAREX call
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 137
9.2.24 SAREX/Mir Beacon Text
This item is the text to beacon via the SAREX/MIR. Put your grid
locator at the beginning of the line for APRS compatibility, i.e.
[FM19LA]. If you put an * as the first character, WHATS-UP will
ignore the value in the file.
9.2.25 LPT parallel port radio memory parameters
This line contains two items separated by a comma, e.g., 7,23.
The first item is the memory channel assigned to the spacecraft.
The second item is the number or total number of memory channels.
When the file is loaded at EWT or AOS, WHATS-UP will step through
the radio memories to the selected channel.
The maximum parameter is required so that when WHATS-UP is scanning
through the memories, it resets the count to 0 at the correct
channel.
9.2.26 Selected or default display page number
This is the default display page for the Real-time and Playback
modes, when WHATS-UP is first loaded.
9.2.27 Page Definitions
These are the page definitions, with two items on the line. The
format is PAGE_TITLE, Page_Color, as in the example below.
SPACECRAFT HOUSEKEEPING, 30
9.2.28 Telemetry Parameter Configuration
The next set of items are the Telemetry parameter configurations
(maximum = 99). You must have at least one of these lines in the
file. If you want a value to show up in more than one page (other
than the wild card [0]) you must enter it twice (once per page).
Typically each row contains 17 items in the format shown below.
TLM_Channel, TLM_Segment_ID, TLM_Description, TLM_Eqn_Type,
TLM_Ceof_C, TLM_Ceof_B, TLM_Ceof_A, TLM_Units,
TLM_Page, TLM_Row, TLM_Col, TLM_Width,
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 138
TLM_Dec, TLM_Limit_Check, TLM_Limit_Low,
TLM_Limit_High,
TLM_Negative_Blank.
Each item is described in the following sections.
9.2.28.1 TLM_Channel
This is the channel number of the telemetry data in the frame. The
DOVE channel number is hexadecimal (e.g. '0F'), Fuji is decimal.
Each entry must be two digits.
A special identifying TLM_Channel is defined in WHATS-UP. If the
value is '99 then the segment identifier and position of the segment
identifier is defined in tow positions in the line. This special
channel identifies the type of telemetry frame.
9.2.28.2 TLM_Segment_ID
This is the segment identifier as described in Section 9.2.28.99
below.
9.2.28.3 TLM_Description
This item is the text string or description of the telemetry
channel that will be displayed on the screen page. (e.g. '+Z Array
Temp.')
9.2.28.4 TLM_Eqn_Type
This item tells WHATS-UP the type of equation to use to decode the
telemetry.
Type 1 is the general purpose equation used by AMSAT-NA in the
Microsats.
Fuji (FO-12 and FO-20) uses two other types of equations (2 and 3).
They are in the formats of
Y = D*(N+E), and Y = F*(G-N).
If you know some algebra you can convert both of Fuji's equations to
the Format used by AMSAT, but since a computer is involved, why not
let it do the job. You do however have to convert an equation of the
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 139
form Y=(N+a)/b.
AO-13 also needs three more types (4 5 and 6) of equations to
decode the RTTY Z blocks.
A type 1 equation in WHATS-UP is a quadratic of the form of
Y = A*N^2 + B*N + C, where: N = raw telemetry data value,
A, B, C = Equation
Coefficients; Y, N are decimal
values.
A type 2 equation in WHATS-UP has the format in the form of
Y = B*(A+N) + C where C, B, A are coefficients; Y, N are
decimal values.
A type 3 equation in WHATS-UP has the format in the form of
Y = B*(A-N) + C where C, B, A are coefficients; Y, N are
decimal values.
A type 4 equation in WHATS-UP has the format in the form of
Y = B*(N+A)^2 +C where C,B, A are coefficients; Y, N are
decimal values.
A type 5 equation in WHATS-UP has the format in the form of
Y = B*(A-N)^2 + C where C, B, A are coefficients; Y, N
are decimal values.
A type 6 equation in WHATS-UP is a special case. It is the AO-13
(Channel 1C) Spin Rate
equation as specified below.
if N > 131 then Y := 479/(N - 109) - 2
else Y := (131 - N) * 0.85 + 20;
where N is the raw decimal number in Channel 1C and Y is the spin
rate.
9.2.28.5 TLM_Ceof_C
This item is the equation Coefficient C.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 140
9.2.28.6 TLM_Ceof_B
This item is the equation Coefficient B.
9.2.28.7 TLM_Ceof_A
This item is the equation Coefficient A.
9.2.28.8 TLM_Units
This item is the Units text string (e.g. '.C') in the screen
display. However if the Tlm_Channel is '99' then this item is the
segment identifier string.
9.2.28.9 TLM_Page
This item is the Display page number. A 0 is a 'wild card' which
will be displayed on every page.
9.2.28.10 TLM_Row
This item is the Display page row. It identifies which row in the
screen the data element will be displayed.
9.2.28.11 TLM_Col
This item is the Display page column. It identifies which column in
the screen the data item will be displayed.
9.2.28.12 TLM_Width
This item is the Display width for Engineering Units. It tells
WHATS-UP how many characters wide the display is to be. You can set
it to any value you want. For example, you can display a voltage as
'1.3' or '1.28567'. Before you widen the display too much, remember
the sampling accuracy of the analog-to-digital converter in the
spacecraft.
9.2.28.13 TLM_Dec
This item defines the number of digits after the decimal point in
the display.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 141
9.2.28.14 TLM_Limit_Check
This item tells WHATS-UP to perform limit checking on the telemetry
channel. It may have several values as
described below.
0 = do nothing,
1 = check below low limit,
2 = check above high limit,
3 = check for EITHER [below low limit] or [above high limit]).
9.2.28.15 TLM_Limit_Low
This item is the Low limit value (e.g. -4.00).
9.2.28.16 TLM_Limit_High
This item is the High limit value (e.g. +10.6).
9.2.28.17 TLM_Negative_Blank
This item is a 1 if you want computed negative values to be
displayed as a zero. Use this for example, in Solar Cell Voltage
computations, when negative values are produced by the equation
supplied even though the negative values are not real. The negative
values are produced because the equation used to convert the data is
not valid at low or zero values of light.
A line with an '*' as the first character terminates this section.
9.2.28.99 The Telemetry Identifier Line
The Telemetry identifier line has the same format as a regular
line, but contains different parameters as follows:
9.2.28.99.1 The Line Identifier
This item has to be '99' to identify the telemetry identifier line.
9.2.28.99.2 The Segment Identifier
This is used when the spacecraft transmits telemetry in more than
one segment. It contains the segment identifier showing which
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 142
segment the channel is down linked in.
9.2.28.99.3 Spare/Not Used
9.2.28.99.4 Location of Segment Identifier in Line
This item contains the location of the segment identifier in the
first line of the telemetry data.
9.2.28.99.5 Spare/Not Used
9.2.28.99.6 Spare/Not Used
9.2.28.99.7 Spare/Not Used
9.2.28.99.8 Segment Identifier String
This item is the segment identifier string as follows.
9.2.28.99.82.1 Fuji
The Fuji frame contains one real time segment (Segment 1) in a
frame addressed as 8J1JBS>BEACON. A typical frame is shown below.
19-Apr-90 17:14:34 8J1JBS*>BEACON:
JAS1b RA 90/04/19 17:13:58
609 430 687 676 744 837 845 829 498 681
617 001 505 516 526 524 526 523 654 000
683 675 686 695 999 643 875 471 099 000
110 111 000 000 111 100 001 111 111 000
The segment identifier is in the seventh and eighth characters of
the first line of the data. A segment identifier of that position
identifies the second segment. The segment identifier is the 'RA'
located on the first line of the data just after the JAS1b where the
'R' in 'RA' is the seventh character in the line.
Any telemetry frame addressed to BEACON received without that
segment identifier is assumed by WHATS-UP to be Segment 2.
9.2.28.99.8.2 DOVE
DOVE transmits telemetry in two frames each addressed as DOVE-
1>TLM. The Microsat ASCII frame thus contains two segments. Two
typical segments of DOVE telemetry are shown below.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 143
DOVE-1>TLM [01/29/90 22:08:46]:
00:59 01:59 02:86 03:30 04:58 05:58 06:6D 07:45 08:6C 09:66 0A:A1
0B:D9 0C:E8 0D:D8 0E:01 0F:23 10:CC 11:A8 12:00 13:01 14:A8 15:94
16:96 17:94 18:95 19:96 1A:93 1B:90 1C:9A 1D:98 1E:23 1F:5E 20:BC
DOVE-1>TLM [01/29/90 22:08:47]:
21:98 22:7B 23:24 24:21 25:2E 26:00 27:00 28:00 29:00 2A:00 2B:00
2C:00 2D:29 2E:00 2F:9B 30:C8 31:9C 32:11 33:DA 34:C0 35:95 36:A4
37:A4 38:B2 39:96 3A:00
The default segment identifier used by WHATS-UP is in the first
and second characters of the first line of the data. A segment
identifier of '00' identifies the first segment, and anything else
in that position identifies the second segment.
9.2.28.99.8.3 AO-13
AO-13 RTTY Telemetry is transmitted in the form of Z blocks shown
below (several blank lines have been deleted to same space in this
document).
Z HI. THIS IS AMSAT OSCAR 13
05.02.44 4661
.0086 .0000 .07B9
64 6 0 1 16 218 1
193 170 158 143 181 144 147 140 200 7
147 7 7 7 165 29 100 7 149 7
10 7 145 115 34 7 153 129 122 180
152 73 7 145 137 55 7 183 136 151
7 154 137 169 211 142 127 100 9 140
161 7 173 149 150 154 14 131 127 210
HI THIS IS AMSAT OSCAR 13 08SEP90
NEW AO13 SCHEDULE FROM 17OCT90 AFTER MOVE TO LON
180 LAT 0
MODE B MA 000 TO 095
MODE JL MA 095 TO 125
MODE LS MA 125 TO 130
MODE S MA 130 TO 135
MODE BS MA 135 TO MA 140
MODE B MA 140 TO 256
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 144
Note the non telemetry information at the end of the block. UO-2's
ASCII telemetry looks different, so WHATS-UP is told where to look
for the telemetry by the following items.
9.2.28.99.9 Spare
9.2.28.99.10 Number of Lines
This item is used in non packet telemetry to tell WHATS-UP how
many lines of data are in a frame.
9.2.28.99.11 First Line
This item is used in non packet telemetry to tell WHATS-UP which
line in the frame contains the first line of data.
9.2.28.99.12 Last Line
This item is used in non packet telemetry to tell WHATS-UP which
line in the frame contains the last line of data.
9.2.28.99.13 Header Lines
This item is used in non packet telemetry to tell WHATS-UP how
many lines there are in the header.
9.2.28.99.14 Character Count
In non packet telemetry this item tells WHATS-UP the maximum
number of characters on a line. Use it in BAUDOT,ASCII and CW
telemetry to stop the display overrunning the page and to force
recognition of the identifier and turn the automatic capture-to-disk
on.
9.2.29 Digital Telemetry Status Channels
The next set of lines instruct WHATS-UP how to display digital
telemetry status in the FO-20 frame. Digital status channels contain
a number of status points. FO-12 and 20 have three data elements in
each digital status channel. Typically, each line in the WHATS-
UP.SYS file contains ten items in the following format.
Status_Channel, Status_Display_Page, Status_Text,
Status_Bit_Mask, Status_Row, Status_Col, Status_ON_Text,
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 145
Status_OFF_Text, Status_ON_Color, Status_OFF_Color.
Each item is described in the following sections.
9.2.29.1 Status_Channel
This is the channel number of the digital status telemetry data in
the frame. Each entry must be two digits.
9.2.29.2 Status_Display_Page
This item is the Display page number. A 0 is a 'wild card' which
will be displayed on every page.
9.2.29.3 Status_Text
This is the text that is displayed in the page.
9.2.29.4 Status_Bit_Mask
This is the bit mask to mask out the position of the desired bit.
The masks are in decimal. i.e. 1, 10 and 100.
9.2.29.5 Status_Row
This item is the Display page row. It identifies which row in the
screen the data element will be displayed.
9.2.29.6 Status_Col
This item is the Display page column. It identifies which column in
the screen the data item will be displayed.
9.2.29.7 Status_ON_Text
This item is the text that is displayed when the spacecraft
telemetry contains a 1 value.
9.2.29.8 Status_OFF_Text
This item is the text that is displayed when the spacecraft
telemetry contains a 1 value.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 146
9.2.29.9 Status_ON_Color
This item is the color the text is displayed in when the spacecraft
telemetry contains a 1 value.
9.2.29.10 Status_OFF_Color
This item is the color the text is displayed in when the spacecraft
telemetry contains a 0 value.
These lines also terminate with an '*' character. A few typical
lines from a Fuji.CNF file are shown below.
30,3,JTA Power :,100, 4, 1, ON , OFF ,11,10
30,3,JTD Power :, 10, 4,25, ON , OFF ,11,10
30,3,JTA Beacon :, 1, 4,45, PSK , CW ,11,10
38,3,Solar Panel 3:,100,12, 1, LIT , DARK,11,10
38,3,Solar Panel 4:, 10,12,25, LIT , DARK,11,10
38,3,Solar Panel 5:, 1,12,45, LIT , DARK,11,10
Note the blanks in the Text ON and OFF positions. The blanks are
used to ensure that a word such as "LIT" which contains three
letters fully overwrites a word which contains four characters such
as "DARK".
9.2.30 Packet/Link Parameters
The next set of items are the Packet/Link Parameters configurations
(maximum = 16). If you want a value to show up in more than one page
(other than the wild card [0]) you must enter it twice (once per
page). Typically each row contains 10 items in the sequence shown
below.
Packet_title, Packet_Type, Packet_Lines, Packet_Page,
Packet_Color, Packet_Row, Packet_Col, Link_Page,
Link_Row, Link_Col, Binary_Byte_Count.
Each item is described in the following sections.
9.2.30.1 Packet_title
This item is the name of UNP address (e.g. TLM,WASH, BCXRT).
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 147
9.2.30.2 Packet_Type
This item is used by WHATS-UP to define the type of telemetry. The
following assignments have been allocated but are not necessarily
used in this release of WHATS-UP.
0 AO-13 Non Packet Decimal telemetry.
1 AMSAT Microsat Packet Telemetry (TLM) with the format CC:DD
where CC is the hexadecimal channel number and DD the
hexadecimal data.
2 AMSAT Microsat Packet Telemetry, hexadecimal ASCII STATUS
telemetry.
3 Fuji Packet Telemetry format of decimal data in which the line
and the position on the line identify the channel. WHATS-UP
allows for up to 60 channels.
4 AMSAT Microsat Packet Telemetry hexadecimal Binary STATUS
telemetry.
5 AMSAT Microsat Binary TLM Packet Telemetry.
6 UO 1/2 ASCII Telemetry.
9.2.30.3 Packet_Lines
This item is the number of lines of text in the packet. For
example, the AMSAT TLM packets contain three lines, the WASH packets
contain only one.
9.2.30.4 Packet_Page
This item is the page that the raw contents of the packet will be
displayed on. A '0' is a wild card which will make WHATS-UP display
it on every page. By careful use of this item, you can display both
raw and decoded packet data on the same page.
9.2.30.5 Packet_Color
This item is the color that the raw packet data will be displayed
in.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 148
9.2.30.6 Packet_Row
This item is the row position that the raw packet will be displayed
in, on the selected page.
9.2.30.7 Packet_Col
This item is the column position that the raw packet will be
displayed in, on the selected page.
9.2.30.8 Link_Page
This item is the Display page for the cumulative count of the
packet type. The wild card '0' applies.
9.2.30.9 Link_Row
This item is the row position that the packet header will be
displayed in, on the selected page.
9.2.30.10 Link_Col
This item is the column position that the packet header will be
displayed in, on the selected page.
9.2.30.11 Binary_Byte_Count
This item is the number of bytes in a binary packet. As no standard
currently exists, we have to tell the computer how many bytes to
expect.
These lines also terminate with an '*' character.
9.3 Telemetry Channel Extraction File
The contents of this file are the defaults for extracting data from
the playback file. A typical set are shown below. WHATS-UP does a
string match, and looks for the first time that a particular string
occurs. You may thus use the contents of a time packet, or the time
mark in a header.
ZCZC (default start time string) {start of file}
NNNN (default stop time string) {end of file}
2F
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 149
35
38
The first line contains the start string. 'ZCZC' tells WHATS-UP to
start extracting at the beginning of the file. The second line
contains the stop string. 'NNNN' tells WHATS-UP to stop extracting
at the end of the file. The remaining lines are the individual
channels (uppercase letters), one channel per line.
9.4 Extracted Telemetry Data File
This an ASCII string, comma delimited file which can be imported
into your spreadsheet. The format of the file is such that each line
starts with a date code or packet header. Then each channel and the
datum associated with that channel follow for all channels in the
packet segment or non packet frame for each and every channel
displayed in the selected page on the screen. If the data from that
channel is not displayed on the screen in the extract mode, the data
will not be extracted.
A typical example of three lines from this file is shown below.
"01-Mar-91 03:39:46 DOVE-1*>TLM:","35", 6.7,"38", -9.7
"01-Mar-91 03:39:56 DOVE-1*>TLM:","35", 6.7,"38", -10.3
"01-Mar-91 03:40:06 DOVE-1*>TLM:","35", 6.7,"38", -10.3
9.5 Doppler File
Doppler data are stored in this file. If the file does not exist,
it is created when needed. If it does exist, data are appended to
the file. The first line of data identifies the time, place and
spacecraft as shown below.
"*** 22-Feb-91 02:57 Doppler Track STARTED for WEBER @ G3ZCZ"
The next line provides the headings for the five columns as
follows.
"Time","Doppler Mark","Frequency","Doppler Shift","Measured Shift"
9.5.1 The Time
The Time is obtained from the PC clock.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 150
9.5.2 The Doppler Mark
The Doppler Mark is a sequential count incrementing at each sample.
It can be used to provide an 'X' axis in a graph. Elapsed time will
be the Doppler mark multiplied by the Doppler sampling interval in
seconds.
9.5.3 The Frequency
The Frequency is the measured radio frequency.
9.5.4 The Doppler Shift
The Doppler Shift is the calculated/predicted Doppler Shift in kHz.
9.5.5 The Measured Shift
The Measured Shift is the difference (in kHz) between the measured
radio frequency and the beacon frequency in the configuration file.
These parameters should allow you to plot Doppler curves and
determine orbit parameters using the time of closest approach
technique.
Typical entries in the file are shown in the following lines.
"02:57:32", 2, 437110740, 8.1494,10.740
"02:57:37", 3, 437110740, 8.1354,10.740
"02:57:42", 4, 437110740, 8.1202,10.740
"02:57:47", 5, 437109860, 8.1045,9.860
"02:57:52", 6, 437110670, 8.0880,10.670
"02:57:57", 7, 437110620, 8.0709,10.620
"02:58:13", 8, 437110620, 8.0525,10.620
"02:58:18", 9, 437109780, 7.9868,9.780
.
.
"03:07:17", 115, 437092570, -7.7884,-7.430
"03:07:22", 116, 437092570, -7.8204,-7.430
"03:07:27", 117, 437092570, -7.8511,-7.430
"03:07:32", 118, 437092570, -7.8802,-7.430
"*** 22-Feb-91 03:07 Auto End"
The lines of data end with a termination statement.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 151
All text items are enclosed in double quotation marks ("). All
elements are delimited by comma characters (,).
If you plan to do Doppler measurements on the Microsats, then you
may be interested in the following information.
The following frequencies were taken after the completion and final
tuning of the completed transmitter assemblies. The measurements
were made at a temperature of 23 deg. C. As the frequency does
change with temperature the current frequency will be slightly
different.
PACSAT: Normal PSK TX: 437.02625 MHz
Raised Cosine TX: 437.05130 MHz
S-Band TX: 2401.14280 MHz
DOVE: FM TX No. 1: 145.82516 MHz
FM TX No. 2: 145.82438 MHz
S-Band TX: 2401.22050 MHz
WEBERSAT: Normal PSK TX: 437.07510 MHz
Raised Cosine TX: 437.10200 MHz
LUSAT: Normal PSK TX: 437.15355 MHz
Raised Cosine TX: 437.12580 MHz
9.6 Kepler Element Files (*.TLE)
The following outlines the "NASA Two-Line" Keplerian data format.
Data for each satellite consists of three lines in the following
format:
Mir
1 16609U 91 36.87776287 0.00038608 39705-3 0 2481
2 16609 51.6077 232.9299 0024950 205.6681 154.3223 15.64092124284608
Line 1 contains an eleven-character name.
Lines 2 and 3 are the standard Two-Line Orbital Element Set used by
NASA and NORAD. The format description is:
Line 2 Column Description
01-01 Line Number of Element Data
03-07 Satellite Number
10-11 International Designator (Last two digits of launch
year)
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 152
12-14 International Designator (Launch number of the
year)
15-17 International Designator (Piece of launch)
19-20 Epoch Year (Last two digits of year)
21-32 Epoch (Julian Day and fractional portion of the
day)
34-43 First Time Derivative of the Mean Motion or
Ballistic Coefficient (Depending on ephemeris type)
45-52 Second Time Derivative of Mean Motion (decimal
point assumed; blank if N/A)
54-61 Radiation pressure coefficient. (Decimal point
assumed)
63-63 Ephemeris type
65-68 Element number
69-69 Check Sum (Modulo 10) (Letters, blanks, periods =
0; minus sign = 1; plus sign = 2)
Line 3
Column Description
01-01 Line Number of Element Data
03-07 Satellite Number
09-16 Inclination (Degrees)
18-25 Right Ascension of the Ascending Node (Degrees)
27-33 Eccentricity (decimal point assumed)
35-42 Argument of Perigee (Degrees)
44-51 Mean Anomaly (Degrees)
53-63 Mean Motion (Revs per day)
64-68 Revolution number at epoch (Revs)
69-69 Check Sum (Modulo 10)
All other columns are blank or fixed.
9.7 AMSAT Format Element File (*.AMS)
The AMSAT format file is the AMSAT file as received by means of
packet radio. WHATS-UP scans the text for the word "Satellite:".
When it finds it, it assumes that the next few lines carry the data
in the fixed order. You thus, do not need to edit the file, just
capture it to disk, and save with a filetype of 'AMS'. For example
the following file could be saved as ORBS-19.AMS.
If you need to enter data in by hand, edit an AMSAT format file,
such as this one.
4116] B BID: ORBS-019.D
Date: 20 Jan 91 02:58:24 Z
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 153
From: N4QQ@N4QQ
To: ALL@AMSAT
Subject: Orbital Elements 019.MICROS
R:910120/0258z 18616@N4QQ.MD.USA [Silver Spring,Md] Z:20901
From: N4QQ@N4QQ.MD.USA
To: ALL@AMSAT
HR AMSAT ORBITAL ELEMENTS FOR THE MICROSATS FROM N3FKV
HEWITT, TX JANUARY 19, 1991
TO ALL RADIO AMATEURS BT
Satellite: AO-16
Catalog number: 20439
Epoch time: 91014.08680572
Element set: 188
Inclination: 98.6853 deg
RA of node: 94.6412 deg
Eccentricity: 0.0010690
Arg of perigee: 259.0593 deg
Mean anomaly: 100.9381 deg
Mean motion: 14.28942714 rev/day
Decay rate: 3.95e-06 rev/day^2
Epoch rev: 5098
Satellite: DO-17
Catalog number: 20440
Epoch time: 91014.07510019
Element set: 187
Inclination: 98.6867 deg
RA of node: 94.6574 deg
Eccentricity: 0.0010787
Arg of perigee: 258.7019 deg
Mean anomaly: 101.2949 deg
Mean motion: 14.29004143 rev/day
Decay rate: 4.60e-06 rev/day^2
Epoch rev: 5098
9.8 Spacecraft Operations File
This is a text file which can usually be obtained from a packet
radio bulletin. You may create one with the editor, if you can't
find one on a packet radio BBS. A Typical file is shown below.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 154
AO-13 TRANSPONDER SCHEDULE
Mode-B : MA 060 to MA 165 :
Mode-JL: MA 165 to MA 190 :
Mode-LS: MA 190 to MA 195 :
Mode-S : MA 195 to MA 200 : <= Mode B is Off - no swishing!
Mode-BS: MA 200 to MA 205 : <= QRP on BS please.
Mode-B : MA 205 to MA 256 :
Omnis : MA 240 to MA 060 :
This schedule is expected to continue through 27 March 91
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 155
10.0 Glossary
AMSAT The Radio Amateur Satellite Corporation
AO AMSAT-OSCAR
AOS Acquisition of Signals
ARRL American Radio Relay League
CCD Charge Coupled Device
DO DOVE-OSCAR
DOVE Digital Orbiting Voice Encoder, also used interchangeably
with DOVE-OSCAR or DO
EWT Early Warning Time
FM Frequency Modulation
FO Fuji-OSCAR
FSK Frequency Shift Keying
LO LUSAT-OSCAR
LOS Loss of Signals
OSCAR Orbiting Satellite Carrying Amateur Radio
PSK Phase Shift Keying
RTTY Radio Teletypewriter
SSB Single Side Band
TNC Terminal Node Controller
TU Terminal Unit (Radio Modem)
UO UoSAT-OSCAR
WO WEBER-OSCAR
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 156
11.0 References and Further Reading
The best book is "The Space Radio Handbook" by John Branegan,
GM4IHJ. It is published by the Radio Society of Great Britain. The
book is available from the RSGB, Lambda House, Cranborne Rd, Potters
Bar, Herts., England EN6 3JE. The price is 13.34 pounds sterling.
John has also written several booklets on MIR, DOVE and UOSAT-2
specifically for the educator and beginner. He can be reached at 8
Whitehills, Saline, Fife, Scotland KY12 9UJ. (Send a SASE or IRCs
please)
Other books and articles of interest are listed below.
Space Radio Handbook, John Branegan, GM4IHJ, Radio Society of Great
Britain.
Satellite Experimenter's Handbook, Martin Davidoff, K2UBC, ARRL
1990, 2nd Edition.
A Turnstile Antenna for Two Meters, Joe Kasser, G3ZCZ, 73 Magazine,
June 1978.
Antennas for Microsat Ground Stations, Dick Jansson, WD4FAB, The
AMSAT Journal, Volume 13, Number 1, March 1990.
Satellite Antennas from Recycled Junk, Howard Sodja, W6SHP,
Proceedings of the OSCAR Seminar, September 29 & 30, 1990. Available
from Project OSCAR Inc.
Microcomputer Processing of UoSat-OSCAR 9 Telemetry, Robert J.
Diersing, N5AHD, The Satellite Anthology, Pages 46-51, ARRL, 1988.
The First Flock of Microsats, Tom Clark, W3IWI, Jan King, W3GEY,
Bob McGwier, N4HY and the AMSAT team, The AMSAT Journal, Volume 12
Number 1, May 1989.
Ariane Launch Vehicle Malfunctions - Phase 3A Spacecraft Lost!, Tom
Clark, W3IWI, Joe Kasser, G3ZCZ, Orbit Magazine, Volume 1 Number 2,
June/July 1980.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 157
12.0 Change History
1.00 (4/01/91) Initial Release.
1.10 (7/15/91) Converted to TP 6.0. Break procedure added on TNC
port. Radio port parameters added to WHATS-UP.SYS. Autotrack
added. Default radio freq/mode added. TNC and Radio Serial
Port values 0 added to allow WHATS-UP to run in a multi-
tasking environment without interfering with the serial ports.
Directory path changed to apply only to capture-to-disk files.
Debug Menu added. Radio Menu changed. CW telemetry automatic
capture-to-disk added (for A-O 21).
1.20 (11/08/91) SARA, TNC1, TNC2, PK-88, KAM and MFJ-1278 added.
1.30 (07/04/94) DSP-2232, PK-900 added. SAREX/MIR Attack Mode and
logging added. TLE and CNF nomenclature adopted.
1.40 (01/01/96) Mutual visibility mode, sunlight and visible
indicators, CW terminal functions, parallel port interface for
memory up/down control, mission elapsed time (MET) window
added. Julian dates for multi-year functions. Several
additions in various menus.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 158
13.0 Obtaining Further Information
For further information about any of the spacecraft and the Radio
Amateur Satellite program, photocopy and mail the following form
together with a self addressed stamped envelope (SASE) to :-
To: [ ] Project OSCAR Inc. POB 1136, Los Altos, CA. 94023-1136.
[ ] AMSAT-UK, 94 Herongate Road, Wanstead Park, London E12 5EQ.
Telephone (081) 989 6741.
I read about the Radio Amateur Satellite program in WHATS-UP and am
interested in it. Please send me further information about the
program, and details of membership in your organization.
CALL ________________ TODAY'S DATE _____________
NAME ______________________________________________
ADDRESS ___________________________________________
___________________________________________
CITY ___________________________________________
STATE _________ POSTCODE ______________________
Comments and questions ...
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 159
14.0 Other Products by Joe Kasser, W3/G3ZCZ
14.1 PC-HAM 3.52
PC-Ham contains the following suite of programs.
14.1.1 LOGBOOK
Full blown logging package. With automatic check of logs for awards
such as DXCC. Allows you to recall any entry by call sign within
seconds. Indexed displays, QSLing, Contest mode QSLing (prints the
lot) and lots more. Although written in dBASE3 the package contains
a compiled version (LOGBOOK.EXE), so you don't need dBASE to run it.
The source code is ONLY given to registered users. Ideal for DX-
peditions or for DX robot users to handle QSLing and log statistics.
14.1.2 CONTEST
Keeps Dupes in memory, logs QSO's to disk in format which can be
processed by the LOGBOOK package. Now compiled in Turbo BASIC,
source code is supplied so that you can modify the program to meet
your requirements.
14.1.3 CQSS
Sweepstakes game compiled in Turbo BASIC. Work the ARRL Sweepstakes
contest on your computer. You are located just outside Washington
DC. A propagation model is built in to the program. This program is
REQUIRED training for all sweepstakes operators. Earlier version of
the program is described in detail in Software for Amateur Radio by
Joe Kasser G3ZCZ, published by TAB Books, Blue Ridge Summit, PA.
17214.
14.1.4 WHATSON
Predict HF Propagation for given days. Contest mode with printout
to whole world at hourly intervals. Needs BASIC.
14.2 STARTREK The Computer Program
An ideal task for the beginner to learn a language on, is a
simulation game which is written to run on a computer that the
beginner has access to. For in that case, there is complete control
of all inputs and outputs. This kind of game (in which the player
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 160
makes decisions based on the information available to him or her
available at the time), can be made sufficiently sophisticated and
complex so as to make writing it an adequate challenge for anybody.
The techniques used in writing a good game are the same that
programmers use in professional activities. Writing a good game
poses a challenge that allows you to develop good habits and
techniques for programming and also allows you to learn a language
in an interesting manner. By taking an orderly approach to the game
design, complex operations may be clearly understood and converted
to computer code with the aid of a language reference manual,
irrespective of the language being used.
This product teaches the techniques for writing such a game using
the STARTREK game as an example, and the BASIC language as the
programming language in which to write the code.
Registration fees.
Single Copy $15.00
10 - 50 Copies $12.00 per registered copy.
50 - 100 Copies $10.00 per registered copy.
100 + Copies $8.00 per registered copy.
14.3.LAN-LINK 2.34
LAN-LINK is a Personal Packet Terminal Program for the TNC1, TNC2,
KPC-2 and most of all a smart multi-mode digital communications
controller for the PK-900, DSP-2232, KAM, MFJ1278 and the PK-232.
LAN-LINK is designed to optimize the configuration of the TNC in
each communications mode and to provide some smart terminal
features. LAN-LINK is a sophisticated program. In its basic state it
allows you to use the TNC in an optimal manner. It configures the
TNC (it types the commands) for you to maximize the communications
efficiency in the communications mode of your choice. That means,
for example, when working Packet on HF you need to program the TNC
parameters to different values than you would use on VHF to make
maximum use of the mode. One significant difference is the length of
the packet itself, for the longer it is, the greater the probability
of QRM destroying it. This program will adjust the packet parameters
for you.
PROGRAM HIGHLIGHTS: Function key and Menu driven. Expert system
(ELMER) in packet mode for building smart servers. Automatic logbook
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 161
entries for Packet and Mailbox/Beacon Mode AMTOR Connects,
semiautomatic logbook entries for other modes. Logbook file is dBASE
compatible and can be processed by the LOGBOOK Package of PC-HAM by
G3ZCZ for indexed listings, tracking of DXCC and other AWARDS, etc.
Contest operation, sends standard message and automatically
increments QSO count. Automatic optimized configuration of the TNC
for each communications mode. All mode Function key 'OVER' feature
(End). There are 60 files with fixed names (LAN-LINK.001 through
LAN-LINK.010) which may be viewed and transmitted by means of
function keys. They may also be edited from the Edit Menu. Set up of
TNC for AMSAT-OSCAR Telemetry reception. Time display and event
scheduler. ASCII Text Editor. Customizable Colors.
Access to the TNC Command Mode is provided in case the user wishes
to override any defaults. Automatic capture to disk of all packet
radio connects. Automatic indication of the number of Packet
connects. Local Area Network (LAN) message store and forward
capability. Capable of automatic connect attempts to download a QTC
from another station in the LAN. Capable of automatic connect
attempts to a packet BBS to download your incoming messages, when
your callsign appears on the BBS mail beacon annunciator. Capable of
automatically requesting Bulletins on subjects that interest you
from your local packet BBS. Digipeat monitoring and capture. Alert
signal to let you know when a predetermined call shows up in a
packet header on frequency. Conference and Bridge modes in
multiconnect situations. Indicator that a specific station
designated as the 'target' call connected in Packet Mode, or linked
to AMTOR Beacon/Mailbox while you were away. Automatic NET/ROM and
KA Node path set up from LAN-LINK.DIR call/path directory file.
Selective answering machine and MAILBOX using NC/L command dialogue.
Automatic Beacon Mode CQ caller. Automatic contest (DX-pedition)
mode. Will call CQ repetitively and either work the connect and keep
going after disconnect or signal you when a reply is received.
Zmodem binary file transfer capability. RTTY SELCAL.
14.4 ELMER 1.00
ELMER is an Expert System Based on a Finite State Machine. There
are two versions of ELMER supplied with LAN-LINK. One is built in
for use in packet mode communications, when connected to someone
else. The second version is a stand alone version for use in
developing the text files and the logic. The stand alone version
lets you program and debug your own personal ELMER by yourself. The
stand alone version is a separate product and requires separate
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 162
registration.
14.5 BASIC PACKET RADIO
Basic Packet Radio explains how the computer can be used to smarten
up your use of packet. Not only does the book explain packet radio,
it comes with a full feature version of LAN-LINK (for the PC) on
disk and contains the manual for the program.
The topics covered in the book are outlined below.
Getting Started in Packet Radio, What Packet Radio Is, The Shared
Radio Channel, The Virtual Channel, The Equipment Needed to Hold a
Packet QSO, The TNC, TNC Modes, The Terminal Program.
Connecting the PC to the TNC, Command Convention, Making the PC
Communicate with the TNC, Determining and Changing the State of a
Parameter, Setting the Carriage Returns and Line Feed Display
Controls, Flow Control, Connecting the TNC to the Radio, Delays in
the Transceiver.
The Local Area Network, How TNCs Communicate, Controlling the
Display of Monitored Packets, Setting Your TNC to Display or Ignore
Packets, The Wireless LAN, Use of Packet Beacons, The Alert Call,
The Target Call, LAN Answering Machine, Mail Beacon (Annunciator),
Remote Beacon Shutdown.
Connecting to Someone, Connecting to Other Stations the LAN-LINK
Way, The Point and Shoot (MH List) Way, Using the Call Menu, Loop
Backs, Names, Handles and Paths, Connecting via NET/ROM and TheNet,
Connecting via KA-Nodes, The SAREX Call and Working MIR.
Extending the Range, Digipeating, Using NET/ROM and TheNet Nodes,
Using G8BPQ Nodes, Using KA-Nodes, Using MSYS Nodes, Using ROSE
Switches, Using LAN-LINK to Communicate via Nodes, Path
Determination to a DX Station, Finding Packet Signals, Using
Communication Satellites.
The Packet Bulletin Board System, How to Connect to the PBBS,
Connected to the PBBS, Connected, But What Next ?, Telling it Your
Name, Getting Information about the PBBS Itself, The Command Prompt
Line, Changing the Prompt Line, Listing the Messages and Bulletins,
Reading Messages, Sending Messages, Sending Messages Around the
World, Sending a Bulletin, Forwarding Bulletins, Sending NTS
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 163
Traffic, The Parts of the NTS Message, Killing Messages, Using LAN-
LINK to Send NTS Traffic, Handling NTS Traffic, Files, Talk to the
SYSOP, Connecting Elsewhere via the PBBS, Obtaining On-Line Help,
Logging Off the PBBS, The F6FBB PBBS Features, Automating Message
Reading, Message Headers.
The PacketCluster, Summary of commands and features, Smartening Up
PacketCluster Access With LAN-LINK.
Internet wormholes and how to access them.
Other Applications of Packet, Data Base Servers, Using a REQFIL
Server, Using a REQDIR Server, Using a REQQTH Server, Electronic
Newspapers, Non Real-Time QSOs, Automatic Beacons, Robots and
Contests, Propagation Research, Transmission Control
Protocol/Internet Protocol (TCP/IP).
This is a book to read once, then use as a reference over and over
again. If you decide you don't like the book, send it back within 30
days for a swift refund.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 164
15.0 How Shareware Works
The Association of Shareware Professionals (ASP) has established
standards for its members and for any organization which has "ASP
Approved" status. The ASP wants to make sure the shareware principle
works for you. If you are unable to resolve a problem with an ASP
member or organization (other than technical support), the ASP may
be able to help. Please write to
The ASP Ombudsman, 545 Grover Road, Muskegon, MI. 49442-9427, USA.
You are encouraged to copy the floppy disk and share it freely with
others. You have the luxury of trying out the product at your own
pace and in the comfort of your own home or workplace.
After you have used the material for a reasonable evaluation period
(30 days), you should either discontinue use of the material or
register your copy. Your support is important and greatly
appreciated. With it, Shareware authors are encouraged to design and
distribute new products. Without it, a great deal of high quality,
low cost software will cease to be available.
Why pay at all?
You receive support from the author. You receive a CURRENT copy of
the program. Your input and ideas help shape future products. You
have a sense of pride and ownership in having honestly participated
in the Shareware revolution. You help to keep software prices down
by supporting a distribution method which doesn't depend on
expensive advertising campaigns.
Be aware of the following restrictions, designed to protect the
community of Shareware users and to prevent greedy people from
taking unfair advantage of the trust, hard work and good will of
Shareware authors.
1. No price or consideration may be charged for the material.
However, a distribution cost may be charged for the cost of the
diskettes, shipping and handling, not to exceed $6.
2. The files and programs on the disks may not be modified or
deleted.
3. The material cannot be sold as part of some other more inclusive
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 165
package.
4. The material cannot be "rented" or "leased" to others.
5. The end user must be told clearly in writing on the outside of
the package and in all advertising that the diskette(s) are
"Shareware."
6. The package must contain a written explanation that the disk is
for evaluation purposes, and that an additional "registration
fee" is expected by the author, if the material is used beyond
an initial evaluation period.
7. In the case of distribution via any telecommunications link, the
following must be done:
* An error checking protocol must be used.
* The individual files must be combined into, and transferred in
a library or archive format.
8. Shareware distribution is permitted only in the United States,
Canada, England, and Australia.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 166
Appendix 1 WHATS-UP 1.40 REGISTRATION FORM
PLEASE COPY this form and MAIL to
Software for Amateur Radio, P.O. BOX 3419, SILVER SPRING, MD 20918.
CALL ________________ TODAY'S DATE ________________
NAME ______________________________________________
ADDRESS ___________________________________________
___________________________________________________
CITY ______________________________________________
STATE _________ POSTCODE ____________ TNC TYPE_____
FIRMWARE REV ____ HOME BBS ______________
DISK SIZE 5.25 _____ 3.5 ____
Please register me as a user of WHATS-UP. I am currently using
WHATS-UP Version ______ which I obtained from _______. Please send
me the latest version of WHATS-UP or if a more recent one does not
exist at this time, QSL my registration and add my name to the list
to receive a free update when it becomes available.
I also enclose an additional amount for evaluation copies of ELMER
_, LAN-LINK _, PC-HAM _ and Startrek TCP _ ($5 for 1 program, $15.00
for the set). If I like them, I plan to register them in due course.
Basic Packet Radio Book (29.95) __.__
Shipping for book $3.50 US/Canada, $10.00 overseas __.__
WHATS-UP Registration ($45.00) __.__
LAN-LINK Registration ($45.00) __.__
ELMER Registration ($45.00) __.__
Evaluation software __.__
____________________________________
Maryland Residents please add 5% sales tax. __.__
Total Enclosed __.__
MasterCard/Visa Number ___________________________Expires __/__
Many additions come into WHATS-UP as a result of user suggestions,
so here's your chance to get some input in. Write them on this piece
of paper.
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 167
Index
µ, 50
AFSK, 9, 75, 108, 118, 124, 130
Alt-A, 6, 45
Alt-B, 3, 23, 24
Alt-C, 3, 23, 24, 46
Alt-D, 3, 23, 24
Alt-E, 6, 46
Alt-F, 3, 23, 24
Alt-H, 6, 46
Alt-I, 3, 23, 24
Alt-J, 3, 23, 24
Alt-P, 3, 23, 25
Alt-S, 3, 6, 23, 25, 46
Alt-U, 6, 46
Alt-X, 3, 6, 23, 25, 47
Altitude, 8, 14, 19, 21, 53, 57, 58, 108, 125, 127
AOS, 4, 5, 8, 18, 19, 20, 21, 43, 62, 129, 131, 134, 135, 138, 156
Ariane, 105, 110, 157
Arrows, 9
ARSENE, 8, 111, 115, 116
ASCII, 5, 9, 2, 3, 7, 8, 13, 28, 39, 40, 41, 43, 61, 64, 66, 69, 74,
75, 98, 102, 124, 126, 130, 135, 143, 145, 148, 150, 162
Astronomy, 105, 106
Autotrack, 3, 9, 7, 21, 22, 23, 24, 132, 134, 158
BAUDOT, 3, 40, 61, 64, 66, 135, 145
Beacon, 5, 9, 10, 2, 4, 7, 19, 24, 39, 40, 41, 48, 49, 61, 70, 76, 80,
94, 95, 97, 98, 100, 101, 104, 105, 108, 111, 115, 116, 118, 119,
123, 124, 130, 131, 132, 133, 134, 137, 138, 143, 147, 151, 162, 163
Branegan, 157
Capture-to-disk, 4, 5, 6, 13, 18, 23, 31, 32, 33, 41, 126, 127, 133,
145, 158
CNF, 6, 7, 8, 10, 16, 30, 31, 38, 39, 40, 42, 126, 127, 131, 132, 133,
147, 158
Co-axial, 11
Color, 5, 8, 9, 5, 16, 17, 18, 19, 20, 41, 43, 125, 126, 128, 129, 132,
138, 146, 147, 148
CW, 2, 4, 5, 6, 9, 4, 9, 11, 26, 27, 37, 39, 40, 43, 49, 50, 51, 76,
91, 92, 94, 95, 96, 97, 98, 100, 104, 105, 118, 119, 120, 126, 130,
132, 135, 145, 147, 158
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 168
Delay, 5, 10, 36, 37, 50, 109, 133, 137
Digipeater, 73, 94, 111, 117, 118, 137
Doppler, 3, 4, 9, 10, 2, 9, 19, 23, 24, 31, 32, 36, 126, 130, 132, 134,
150, 151, 152
DOVE-OSCAR, 2, 4, 62, 134, 156
Downconverter, 64, 68
Downlink, 7, 3, 4, 11, 61, 67, 69, 76, 84, 94, 95, 107, 108, 111, 118,
119, 122
Drag, 35, 52, 57
Earth-Sun, 54
EWT, 10, 19, 20, 21, 43, 129, 131, 137, 138, 156
Extract, 4, 8, 5, 20, 28, 125, 127, 128, 150
Fades, 3, 65, 66
FO, 4, 61, 64, 69, 92, 93, 94, 95, 102, 119, 131, 133, 139, 145, 156
Footprint, 21
Fuji-OSCAR, 7, 4, 7, 62, 92, 95, 96, 97, 98, 99, 100, 101, 102, 103,
104, 133, 134, 135, 156
Greek, 50
Hop, 21
Icom, 135, 136
Inclination, 7, 35, 53, 55, 62, 93, 111, 116, 153, 154
Index, 168
JAS, 93, 95, 98, 101, 102, 143
JBS, 94, 95, 101, 133, 143
Jupiter, 106, 107, 110, 111
Kepler, 8, 10, 54, 125, 127, 152
Keplerian, 4, 9, 15, 19, 28, 31, 33, 34, 131, 132, 134, 152
Keyboard, 6, 4, 9, 10, 15, 43, 49, 50
Keyer, 9, 51
Keystroke, 49
KPC, 161
LAN-LINK, 11, 4, 18, 42, 44, 45, 46, 161, 162, 163, 164, 167
Laptop, 9, 136
Latitude, 8, 13, 21, 93, 125, 126
Launched, 58, 59, 70, 73, 76, 84, 92, 105, 111, 116
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 169
Line-of-sight, 11
Logbook, 6, 9, 10, 4, 9, 44, 45, 46, 47, 125, 126, 129, 130, 160, 161,
162
Longitude, 8, 13, 21, 125, 127
LPT, 10, 133, 135, 136, 138
LSB, 37, 80, 81, 82, 83, 96, 97, 100, 104, 135
LUSAT, 2, 84, 85, 89, 91, 92, 131, 152
LUSAT-OSCAR, 2, 4, 62, 134, 156
Mheard, 123
MicroSat, 5, 2, 6, 14, 39, 40, 58, 84, 143, 148, 157
Milliseconds, 50, 51
MIR, 2, 6, 10, 4, 9, 15, 20, 21, 47, 48, 49, 130, 133, 137, 138, 152,
157, 158, 163
Mode-B, 78, 79, 155
Mode-BS, 155
Mode-J, 82, 83
Mode-JD, 94
Mode-JL, 79, 155
Mode-L, 79, 80, 83
Mode-LS, 155
Mode-S, 79, 80, 82, 83, 155
Morse, 5, 3, 4, 21, 39, 40, 43, 50, 51, 82, 91, 95, 129
Multi-mode, 2, 64, 128, 161
Multi-task, 50
Multi-tasking, 42, 158
Multi-year, 158
North, 19, 55, 116
Orbits, 3, 4, 6, 11, 26, 27, 33, 53, 58, 62, 63, 66
PACSAT, 2, 85, 131, 152
QTH, 9, 126, 130
RAAN, 7, 35, 55, 56
Range, 8, 3, 11, 14, 18, 19, 20, 62, 64, 65, 67, 76, 98, 107, 113, 125,
129, 163
Ranging, 82, 106
Re-entered, 59, 73
Real-time, 5, 18, 21, 23, 26, 28, 74, 138, 164
Receiver, 3, 9, 4, 5, 10, 12, 23, 24, 36, 64, 65, 66, 67, 68, 78, 79,
107, 108, 121, 133, 134, 135
COPYRIGHT Joe Kasser, G3ZCZ 1996.
WHATS-UP.DOC Release 1.40 Page 170
RS, 5, 13, 14, 15, 20, 41, 64, 66, 120, 121
SARA, 5, 7, 39, 41, 69, 105, 106, 107, 108, 110, 111, 158
SARA-OSCAR, 7, 62, 105
SAREX, 2, 4, 6, 9, 10, 4, 9, 26, 27, 42, 47, 48, 49, 125, 129, 133,
135, 137, 138, 158, 163
Segment, 138, 139, 141, 142, 143, 144, 150
Sidereal, 110
SSB, 11, 12, 45, 63, 94, 156
Stream, 9, 126, 131
Sub-satellite, 21
Sun, 4, 9, 33, 34, 35, 54, 55, 56, 59, 60, 70, 73, 81, 82, 85, 93, 106,
107, 108, 109, 110, 126, 130
Telemetry, 2, 7, 8, 10, 2, 3, 4, 5, 6, 15, 16, 17, 20, 23, 32, 40, 41,
42, 61, 65, 66, 69, 70, 71, 73, 74, 75, 76, 77, 78, 84, 85, 86, 87,
89, 91, 94, 95, 96, 98, 99, 101, 102, 103, 104, 107, 108, 111, 113,
115, 116, 117, 118, 119, 120, 121, 122, 124, 125, 127, 133, 138, 139,
140, 142, 143, 144, 145, 146, 147, 148, 149, 150, 157, 158, 162
Temporary, 51
Transceiver, 11, 12, 163
Transients, 10
Transverter, 12
Transverters, 12
TTL, 9
UoSAT-OSCAR, 4, 40, 156, 157
Uplink, 11, 94, 95, 108, 111, 118, 119, 123, 124, 135
Vector, 54, 82
Viewer, 130
WEBER-OSCAR, 2, 4, 62, 134, 156
Zap, 6, 48, 49
COPYRIGHT Joe Kasser, G3ZCZ 1996.