THE DEVELOPHE" OF Um-EAR!I!

E-ORBIT STORE-AND-FORWARD SA'l'ELLITES

IN THE AMATEUR RADIO SERVICE
ROBERT J. DIERSING
Department of computer Information systems
Texas A&I university
Campus Box 184, Kingsville, TX 78363

ABSTRACT while many proposals to provide placed in orbit in July, 1991, also by an
personal communications services via Airane launcher using the ASAP. It is a
networks of low earth orbit satellites have store-and-forward satellite similar to
been appearing in the literature, UOSAT-3.
engineers, researchers, and experimenters
in the Amateur Radio Service have been while PACSAT-1 is devoted entirely to
advancing the state of the art in single amateur radio operations, UoSAT-3 and
LEO store-and-forward satellite design and UoSAT-5 can operate in both the amateur
application. In the past two years at radio service and other services. when
least eight different spacecraft have been originally launched, UoSAT-3 provided
placed in orbit. some of these satellites service to radio amateurs and to the VITA
carry a wide variety of scientific and organization (Volunteers In Technical
technology experiments but the scope of Assistance). similarly, UoSAT-5 provided
this paper will be limited to several of service to radio amateurs and to the
the satellites whose primary mission is to SatelLife organization. VITA is a non-
provide store-and-forward message relay profit organization dedicated to providing
services for radio amateurs. The following technical and project assistance to
presentation emphasizes three major areas: developing countries. SatelLife is a
(1) a description of the spacecraft; (2) humanitarian organization founded by 1985
the ground station equipment and software Nobel Prize winner Dr. Bernard Lown. A
required to utilize the services provided recent description of UoSAT-3 operations by
by the satellites; and (3) statistics which VITA can be found in [?I. Additional
describe current usage patterns. information about SatelLife and UoSAT-5
operations can be found in [9]. Beginning
I. INTRODUCTION on February 4 , 1992, UoSAT-3 has been
devoted entirely to operations for the VITA
Among six amateur radio satellites and SatelLife organizations and UoSAT-5 has
launched during the first use of the Ariane been devoted exclusively to amateur radio
Structure for Auxiliary Payloads (ASAP) on operations. The discussion of these
January 22, 1990, were three spacecraft satellites in this paper is limited to
whose primary mission is providing store- amateur radio operations.
and-forward and file broadcast service to
the amateur radio community. Most of the 11. THE SATELLITES
first year of operation was spent on
application software development with file PACSAT-1, UoSAT-3, and UoSAT-5 possess
server and file broadcast services a number of attributes which make them
beginning in earnest in late 1990. During distinct examples of cost-effective
1991, both ground station and satellite- satellite and communications system
based software matured and stabilized such engineering. some of these attributes are
that these satellites see a high volume of embodied in the physical structure of the
daily use both by individual amateur radio satellites and others are associated with
station operators and stations acting as the hardware and software systems
gateways for terrestrial packet radio implementation. Some of the most
networks operating in the Amateur Radio interesting aspects of these systems are
Service. The most significant software described in the following two sections. A
developments of 1992 have maximized down- more complete description of PACSAT-1 can
link utilization by improving file and be found in [4]. Additional information
directory broadcasting and implementing about UoSAT-3 and UoSAT-5 can be found in
automatic hole filling. [lo] and [ll]. A discussion of amateur
radio satellites with digital communication
The primary focus of this paper will facilities in operation prior to 1990 is
be the PACSAT-1 satellite owned and available in [2].
operated by the Radio Amateur Satellite
Corporation of North America (AMSAT-NA) and A. PACSAT-1
the UoSAT-3 and UoSAT-5 satellites
constructed and operated by the University PACSAT-1 is one of four spacecraft on
of Surrey (England) UoSAT Spacecraft the January 22, 1990 launch which have been
Engineering Research Unit. UoSAT-5 was given the name "microsats". These are

0-7803-0922-7/93$03.001993aIEEE 378
extremely small satellites being of cubical
shape, measuring approximately 23 cm (9
inches) on a side, and weighing
approximately 10 kg. PACSAT-1 includes: a
five-channel VHF receiver using 1200 bps
Manchester FSK or 4800 bps NRZI demod-
ulator; a 4W, 70 cm transmitter using 1200
or 4800 bps standard BPSK or raised-cosine
BPSK modulator; a lW, 13 cm transmitter
with 1200 bps BPSK modulator; an NEC V-40
microprocessor running at 4.9 Mhz with 8
Mbytes data storage RAM, 256 Kbytes EDAC
RAM for program storage, a 2 Kbyte ROM boot
loader; and 6 Ah NiCad battery.
B. UoSAT-3 and UoSAT-5
UoSAT-3 is physically larger than the
PACSAT-1 microsat and carries other
experimental systems in addition to the
store-and-forward PACSAT Communications
Experiment (PCE) . For amateur radio
operations there is one uplink in the 2 m
band and one downlink in the 70 cm band.
9600 bps FSK modulation is used for both
uplink and downlink. The UoSAT-3 PCE uses
an Intel 80C186 microprocessor operating at
8 MHz with 256K bytes EDAC RAH for program
storage and 4M bytes of RAM for file
storage.
The UoSAT-5 PCE also uses an Intel
80C186 running at 8 MHz. However, there is
512K bytes EDAC RAM for program storage and
13M bytes of RAM for file storage. For its
exclusive allocation to amateur radio
operations there are two uplinks in the 2 m
band and one downlink in the 70 cm band.
9600 bps FSK modulation is used on both of
the uplinks and downlink.
c. satellite operatins systems
PACSAT-1, UoSAT-3, and UoSAT-5 use the
qCF real time multi-tasking operating sys-
tem developed by Price and his associates
at Quadron Service Corporation [ 4 ] . qCF
executes tasks written in the c programming
language and compiled with the Microsoft C
compiler. The net result is a programming
system allowing the use of a popular high-
level language in an environment having the
necessary development tools. Furthermore,
most spacecraft functions can be simulated
in an IBM-PC using a commercially available
80186 coprocessor card. The principal
differences in operating system software
from one spacecraft to another, are those
associated with I/O drivers and those
dictated by the data processing and
communications requirements of the other
onboard experiments and syst'ems.
111. FILE SERVER AND FILE BROADCAST
PROTOCOL
The development and implementation of
a protocol for any communication system
379
must necessarily take into account the
nature of the users of the system, the
nature of the equipment comprising the
system, and the characteristics of the
communication channel. PACSAT-1, UoSAT-3,
and UoSAT-5, operating in low earth orbit,
supplying communication services to widely
geographically distributed users, and using
an uncoordinated access radio channel
constitute a distinct system of users,
equipment, and channel.
Many amateur radio operators make use
of terrestrial packet radio bulletin board
systems (PBBS). These PBBSs are the
amateur radio counterpart of microcomputer-
based computer bulletin board systems which
use the public telephone network. However,
much of the activity on terrestrial PBBSs
is taken up with the repeated retrieval of
information of general interest. For
example, many individual amateur operators
interested in satellite operations may
access a PBBS to obtain the reference
elements used in their orbital prediction
programs. consequently, the exact same
information may be transmitted many times.
On terrestrial networks, repeated
transmission of the same data can be
tolerated because the system capacity is
available by virtue of the 24-hour per day
access time and multiple stations providing
PBBS service. such capacity obviously does
not exist in the case of an LEO satellite-
based system with limited visibility time
at any particular ground station location.
what is needed is a way for multiple users
to benefit from the same transmission of a
particular file since many users are within
the satellite footprint at the same time.
Not all information which amateur
radio satellite users would like to
exchange is of general interest.
Furthermore, different users might like to
exchange different types of data or
implement different types of applications
in which the satellite-based communications
system may play an integral part. users
may wish to retrieve a directory of files
stored in the spacecraft message system
memory or download a specific file. Users
may want to upload a file to the satellite
either for later broadcasting or for
retrieval by some other station half-way
around the world. So, in addition to
serving several users who need the same
data, there is also a need to serve users
needing more traditional file and message
forwarding facilities.
PACSAT- 1, UOSAT-3 , and UOSAT-5
satellites are in low earth orbits at an
average altitude of 800 km. From that
vantage point, over populated areas such as
the continental united States, hundreds and
perhaps even thousands of potential users
are within the satellite's footprint.
Although at any given ground station
location (in the middle latitudes) there
will be only 50 to 60 minutes of access
time per day, there is still sufficient
time for any individual station to receive
a large amount of data. For example, with
PACSAT-1 operating at 1200 bps, it is
possible to receive approximately 500K
bytes of data per day. For UoSAT-3 and
UoSAT-5, operating at 9600 bps, about 4M
bytes of data could be received. This
assumes, of course, that the ground station
is in operation for all times the satellite
is visible.
Based on the nature of the system
components and on the experience gained
with the UoSAT-2 Digital Communications
Experiment (DCE) [ Z ] , ward and Price have
developed the PACSAT Protocol Suite which
is fully documented in [ 5 ] , [6], [ T I , [12!,
and [13]. The interested reader is
directed to these references for the
complete details of the protocol
implementation. The data-link layer
protocol used is AX.25 [3]. The PACSAT
Protocol Suite implements a file broadcast
mode and a file server mode using a common
file format. Each of these two modes will
be described briefly and the hardware and
software required to access the satellite
will be presented in the next section.
A. PACSAT File Header
Files being transmitted in broadcast
mode and files being uploaded or downloaded
in file server mode make use of the PACSAT
file header. Figure 1 shows an example of
the information contained in the file
header. In broadcast mode, an individual
data-link layer frame information field
contains only the file number (ID), file
type and the offset to the location in the
file where the data belongs. The other
information needed to identify the file and
its attributes are contained in the file
header. A complete file header description
can be found in [13]. User software has
been provided to add a PACSAT file header
to a file before it is uploaded and to
remove or display a file header after the
file has been downloaded.
B. File and Directory Broadcast Mode
The broadcast protocol has the
following attributes: (1) Any frame, when
received independently, can be placed in
the proper location within the file to
which it belongs. (2) when all frames have
been received, the receiving station can
tell that the file is complete. (3) For
file types where it makes sense, partial
files are usable. This implies that if a
data compression scheme is used, it should
be possible to incrementally decompress the
file.
380
The broadcast mode transmits files in
the message system memory by giving each
file on the broadcast queue a certain
amount of downlink time. The broadcasts
continue in a round-robin fashion until a
predetermined time limit or number of
transmissions has been reached.
File broadcasting is done as a series
of AX.25 [3] unnumbered information (UI)
frames. U1 frames are not acknowledged by
the receiver and order of delivery is not
guaranteed. The terminal node controller
(TNC) shown in Figure 2 passes the frame on
to the application program only if the
frame is correctly received. Error
checking of the frame is done via CRC-16 by
the TNC. The format of the information
field of a broadcast frame is shown below.
eflagsxfile idxfile type>
eoffsetxdata><crc>
In the information field format above,
the file ID field is a file number assigned
by the file server system when the file is
uploaded rather than an ASCII character
string file name. The offset gives the
position relative to the beginning of the
file where the data belongs. The CRC shown
is a check on the I-field contents only and
is included primarily to allow detec:tion of
errors on the serial link between the TNC
and the computer.
Requests to place files in the
broadcast queue are likewise done with U1
frames. The spacecraft does respond to
broadcast requests but not in terms of a
data-link layer acknowledgement. It only
sends a U1 frame with v'OK" in the
information field to the station making a
successful broadcast request. Error
indications, such as broadcast queue full,
are also transmitted as U1 frames.
Even though a station may also access
the satellite in a connect-ed-mode
transaction (described in the next
section), the most recent developments in
satellite and ground station software make
the file and directory broadcast mode the
preferred method of operation. since
multiple users in the satellite footprint
may want to capture the same files and
update their directories at the same time,
downlink utilization is maximized when
broadcasting is utilized. Individual users
may request fills of specific "holes" in
their captured files and directories, but
the rebroadcast of entire files or
directories for a single user is
eliminated.
The satellite and ground station
software maximizing the use of directory
and file broadcasting with UoSAT-3 and
UoSAT-5 has been in operation since late
 available from multiple sources in the
file number oxo
under $200 U.S. price class. It is
file name important to note that because of the
f i l o extension broadcast type of operation on the
file sise 20270 satellite downlinks, other satellite
create date Tue Jan 08 04:56:58 1991
last modified Tue Jan 08 04:57:26 1991 enthusiasts, such as educators and
seu flag ox00 shortwave listeners can capture the data
file type ox00 being transmitted with a receive-only
body checksum Ox662d station. only licensed radio amateurs may
header checksum Oxla24
body offset 186 transmit on the satellite uplinks, however.
source n5ahd
ax25 uploader To utilize all of the communication
upload time uninitialized facilities available, four computer
download count 000
destination wd5ivd programs named PB, PG, PHS, and PFHADD have
ax25 downloader been made available free of charge to non-
download time uninitialized commercial users of the satellite. PB
expiry time uninitialized allows files and directories being
compression type ox00
priority 000 broadcast to be captured on the receiving
user filename ntc0l.doc station's computer. PB also allows a
title article draft station to request the broadcast of hole
keywords NTC9 2 fills in partially-received files and
directories. PG is used to upload files to
the spacecraft for later broadcast. PFHADD
Figure 1. PACSAT file header adds the header required for uploading a
contents. user file. PHS will display or remove the
1991. The same software was installed on file header after downloading a file. The
PACSAT-1 during October 1992. initial versions of PB, PG, PFHADD, and PHS
run on IBM-PC/AT and compatible systems.
C. File Server Mode Implementations for other systems have also
been developed.
Access to PACSAT-1 I UOSAT-3 , or UOSAT-
5 in file server mode is transaction Recall that file and directory
oriented. A user can request a directory broadcasting is done in AX.25 unconnected
listing of the files stored in the mode and file uploads are done in AX.25
spacecraft. He/she can also upload and connected mode. Consequently, PB looks for
download files. An upload or download U1 frames from the spacecraft and places
transaction can be resumed later if it was them in the proper location in the file
previously interrupted (by LOS, for being received if the user has requested
example ) . that the file be captured. PG, on the
other hand, establishes a connection with
When using the file server mode, an the file server and attempts to complete
W . 2 5 connection exists between the ground the transaction requested by the user. The
station and the spacecraft. standard following brief discussion of user software
balanced-mode HDLC procedures control the operation will provide some insight into
exchange at the data-link layer. The the mechanics of utilizing the communica-
transaction-oriented operation assures that tions facilities of the satellites.
the availability of the uplinks is maxi-
mized. Currently, the only use of the file A user wishing to monitor files and
server mode is for file uploading. Files directories being broadcast on the downlink
and directories are downloaded using the would configure his/her station equipment
broadcast mode already described. as shown in Figure 2 and execute the PB
program on the station computer. Figure 3
IV. GROUND STATION EQUIPMENT AND shows a typical screen display from the PB
OPERATION program while monitoring UoSAT-5 downlink
traffic. The lower half of the screen
A typical equipment configuration for shows certain informatory messages exactly
utilizing PACSAT-1, UOSAT-3, and UOSAT-5 is as they appear on the downlink. The upper
shown in Figure 2. Those who operate using left corner of the screen shows files for
other amateur radio satellites will already which capture is in progress (in this case
have the required transmitting and none) and the upper right corner shows
receiving equipment and antenna systems. directory headers and message numbers being
Those who operate using terrestrial packet heard on the downlink.
radio will already have the terminal node
controller (TNC). Similarly, many stations The last line of the screen is a
already utilize a microcomputer in some status line. "DIR: Part (05)'' means that
manner. The only item not usually present an updated directory has been partially
in the typical station is the PSK or FSK received and there are five holes (missing
modem. However, both of these are pieces). "AUTO: Dir" shows that the ground

38 IL
station computer directory is being updated
automatically from the monitored directory
data. "Dir" could be replaced by a file
number being downloaded. The values
labeled 'Os: **, "b: I*, "d: ", and "e: '*
stand for data rate in bytes per second for
the last five seconds, number of bytes
monitored from broadcast files, numher of
bytes monitored from broadcast directories,
and number of CRC errors between the TNC
and the ground station computer.
The line beginning with "PB: shows
which stations have made requests for files
or directories (or hole fills) to be
broadcast. station callsigns with the
suffix "\D" have made directory requests
while the others have made file broadcast
requests. The message "open: 1 a: WSERO"
shows that station WSERO is a connected-
mode user (probably doing a file upload) on
uplink no. 2 and that uplink no. 1 is
available for another user.
Figure 4 shows a portion of the ground
station computer directory after it has
been captured from the downlink traffic .
The upper right corner of the screen shows
the f i l e broadcast selection criteria in
the message "Select=All Mail". This means
that message traffic addressed to "All" or
traffic to this specific station's callsign
will be downloaded automatically. These
criteria can be changed to suit the station
382
operator through selection 'equations
employing relational and logical operators
which test appropriate fields in the PACSAT
File Header. Consistent with the selection
of "All", note that file numbers 5136,
511f, and 5118 have a square block in the
" S (tatus) *' column. This indica.tes that
these files, which have a to address of
"ALL", have already been downloaded. At
the lower left corner of the screen the
message '*A11 Mail AL BL" appears. These
are the selection criteria for the
directory display as opposed to the
criteria for automatic file downloading.
Thus, the directory display will show AL
(activity log) and BL (broadcast log) files
in addition to files addressed to other
satellite users.
A user wishing to upload a file would
first attach the PACSAT file header to the
file and then use the PG program to upload
it to the satellite. PG is used only for
file uploading and operates in connected
mode using the AX.25 data link layer
protocol. When using PG, a connection is
established, an upload transaction
executed, and the connection terminated as
a result of a single operator command. The
one-transaction-per-connection philosophy
ensures maximum utilization of the uplinks
in connected mode. There is no wasted time
while a ground station operator executes a
 Download: Priority Auto Grab Never Pill Dir Info. View dir. Quit: Help.
Message Holes Size Offset Rcvd Dir 3all S:EISLOG T: P:
Dir 5126 S:jZg T:VK6AKI P:VK6BMD
Dir 512f Srlmago viow T:YElAD P:SH5BVP
Dir 50d6 S:AD920713 T: P:
Dir 50d9 S: BL920 713 T: F:
Dir 5134 S:F I N N I T:OA6LFG F:OB7BY
Dir 5133 S:OB1311Tl.Z T:JA6FTL F:OH6SAT
Hesnage lefc heard.
Hesnage 4e32 heard.
Dir 50d8 S:TD920713 T: F:
Dir 50d7 S:AL920713 T: F:

OK NOGIB
OK NOGIB
OK NOGIB
PB: WB79KK KF5OJ\D KC2PB K8TL WB5EKW\D NOGIB\D KBYAA
BIT V2.16 PBP V2.05 DBP V1.00
Mon Jul 13 17:49:21 1992 Uptime= 92/22:9:12 EDAC= 2158 Fmem=4204
Lmem=2741 d:O s:O.
Open 1 a : W5ERO
OK N5AHD
Open 1 a : W5ERO
OK VE8DX

DIR: Part (05) AUTO: Dir s:0427 b:007650 d:001505 e:

-
Figure 3 . PB display while receiving data on the satellite downlink.

Keys: Pr 3 Auto Grab Never Find aRchview Quit Help Main Select=All Mail
Message Subject Posted at Size
_ _ _ ~ - - ___._--
5140 07/13 17:56 420
513f 07/13 17:54 991
513e 07/13 17:54 1090
5136 07/13 17:44 443
5134 07/13 17:29 1349
50d9 07/13 17:26 1340
50d7 07/13 17:23 14485
512f 07/13 15:55 695
5126 07/13 15:21 46410
5125 07/13 13:44 753
5120 07/13 12:49 1754
511f 07/13 12:48 72 5
5118 07/13 12:41 737
5108 07/13 11:16 1796
5101 07/13 10:16 810
50ff 07/13 10:16 10517
'50fd 07/13 09:33 2826

All Mail AL BL
DIR: Up-To-Date AUTO: Idle s:0969 b:369695 d:135249 e:0002

Figure 4. A display of a portion af a downloaded directory.

command and then pauses deciding what to do
next.
V. USER TRAFFIC STATISTICS
There are two methods which may be
used to collect satellite usage statistics.
First, a ground station can monitor the
downlink while the satellite is visible and
record all traffic for later analysis.
second, an analysis of the activity log
files stored on the spacecraft can be done.
The activity log files (AL files) can be
downloaded just as any other file kept by
the file server. Monitoring the downlink
provides a view of the traffic from a
particular location. Analysis of the AL
files provides an observation of the
traffic from the viewpoint of the
satellite. Both methods were employed
during collection of data reported in this
section.
-
During the time period between March
and November 199 1, several downlink traffic
samples were made at the author's ground
station location. Two of these samples are
summarized in Table 1. A third sample,
shown in Table 2 , is further subdivided by
time of day and day of week. None of these
samples showed any appreciable difference
in the mixture of file server, file
broadcast, and telemetry traffic. The
traffic samples have been used in the
development of a downlink traffic simulator
for LEO store-and-forward satellites [l].
For the data presented in Table 2 ,
daytime refers to the local (C:ST/CDT)
daytime visibility periods which occur
between roughly 16:OO and 19:OO UTC.
Nighttime refers to visibility periods
which occur between 03:OO and 06:OO UTC.
There are considerably fewer observations
in the daytime weekday category because,

383
 The chart for PACSAT-1 (Figure 5)
shows that directory requests outnumber
Table 1 uploads and downloads by a considerable
Summary of Two PACSAT-1 Downlink amount. On the other hand, notice that for
Traffic Samples UoSAT-5 (Figure 7), uploads outnumber
directory requests and downloads. This is
Sample No. 1 sample NO. 2 caused by the emphasis on directory and
03/17/91 06/16/91 file broadcasting with UoSAT-5. At the
to to time this paper was prepared, data was not
05/29/91 08/27/91 available for PACSAT-1 to show the effect
Byte of Byte of
Count Total Count Total of the installation of the same File and
directory broadcasting software. The
Total Bytes 3,168,924 2,107,941 average byte count associated with
Pile Server 1,353,752-42-7 897,444-42.6 connected mode transactions for UoSAT-5
Broadcasting 1,630,643-51.4 1,089,510-51.7
To lemetry 184,259-5.8 120,987-5.7 (Figure 8 ) is at least twice that of
PACSAT-1 (Figure 6). This is a consequence
of the higher speed uplinks and downlink on
UoSAT-5--9600 bps as opposed to 1200 bps
for the most part, work schedules did not for PACSAT-1.
allow monitoring during that time period.
Even so, there is little variation in the Finally, Figures 9 and 10 summarize
traffic mix for the three traffic types. broadcast mode activity for UoSAT-5 for a
It should be remembered that downlink two-week period. Figure 9 shows the number
monitoring will not record file uploading of file and directory broadcast requests
traffic from ground stations since uplink and hole file requests. There is little
traffic is not repeated on the downlink. variation in file broadcast and hole fill
requests from day to day and it will be
In contrast to the data in Tables 1 interesting to see if this trend continues
and 2 being observed at a single ground for the long term. Figure 10 shows an
station location, the data used to produce average 20 Mbytes of broadcast mode data
the plots in Figures 5 through 10 is taken per day and gives an indication of the
from the daily activity log files kept on utilization of a satellite like UOSAT-5.
the spacecraft . For PACSAT-1 , these It should be remembered that all of the
broadcast mode requests, whether for
figures represent complete file server
activity summaries for the period July 1 directories , files, or hole fill.s, were
through July 25, 1992. Figure 5 shows a initiated by ground station users.
transaction count and Figure 6 shows a byte Moreover, it is quite likely that more than
count for the 25-day time period. Figures one station in the satellite footprint
7 and 8 for UoSAT-5 correspond to Figures 5 captured a file or directory once
and 6 for PACSAT-1 except that they cover broadcasting had begun.
the time period from November 1 through
November 30, 1992. VI. SUMMARY
This paper has reviewed the current
state of the art in amateur radio store-
and-forward satellite communications.
Table 2 several operating satellite systems have
PACSAT-1 Downlink Traffic sample by been described along with the procedures,
Time of Day and Day of week equipment, and software required to access
09/02/91 to 11/28/91 them. A breakdown of downlink usage by
data type has been given for PACSAT-1. To
show how the PACSAT-1 and UoSAT-5
Weekdays Weekdays satellites are utilized on a day-to-day
Daytime Nighttime
Byte t of Byte t of basis, graphical summaries of two week8 of
Count Total Count Total PACSAT-1 and UoSAT-5 operation have been
included.
Total Bytes 513,660 1,576,803
Pile semer 214,418-41.7 680,316-43.1
Broadcasting 268,366-52.2 786,245-49.9 As interest in applications for Small
Telemetry 30,876-6.1 110,242-7.0 low-cost satellites continues to increase,
Downlink Time 01: 05 :40 03:27:24 development work and operational experience
Weekends Weekends
provided by researchers and experimenters
Daytime Nightt ime in the Amateur Radio Service will benefit
those designing and building similar
Total Bytes 2,177,564 1,610,162 communications systems for operation in
Pile Server 834,598-38.3 647,318-40.2
Broadcasting 1,206,108-55.4 862,376-53.6
other services.
Telemetry 136,858-6.3 100,468-6.2
Downlink Time 05:00:20 03:50:49

384
 PACSAT-1 C o n n e c t e d - M o d e A c t l v l t y Summary UOSAT-5 C o n n e c t e d Mode A c t l v l t y Summary
Daily T r a m a c t i o n Counts for 07-01-92 t o 07-25-92 Cai l y BVte Counts f o r 11-01-92 t o -11-30-62
P Ima
I
.BD

"-
c

3 sm

m m m

9DwlCado
04 m3 U m OI 0

+401-
,m 11 ,m 0 ,* %a
Day o f Month
- n I-m
. m m R m

-,+DI~K~QTY
Vl

neatmato
B
0

-Y kcadcast Wumote +Total

Figure 5. PACSAT-1 connected mode Figure 8. UoSAT-5 connected mode

activity summary in transactions. activity summary in bytes.

PACSAT-1 C o n n e c t e d - M o d e A c t i v l t y Summary WSAT-5 B r o a d c a s t Mode A c t l v l t y Summary

Datlv BYte b u n t 6 for 07-01-92 t o 07-25-92 D a l l y Transactlon Counts f o r 11-01-92 t o 11-30-92

;le-
5 *-
k
0 -

Day of t h n t h
+DownI oads +LptoadP
+OIrpctory m u o a t s -Total

Figure 6. PACSAT-1 connected mode Fiqure 9. UoSAT-5 broadcast mode

activity summary in bytes. activity summary in transactions.

WSAT-5 C o n n e c t e d Mode A c t l v l t y Summary WSAT-5 B r o a d c a s t Mode A c t l v l t y Summary

Dally Transactlon Count6 for 11-01-92 t o 11-30-62 D a l l y Byre C o u n t s for 11-01-92 to 11-30-92
-
"

Cuy of Month

Figure 7. UoSAT-5 connected mode

activity summary in transactions. activity summary in bytes.

385
 VII. REFERENCES [ 121 J. W. ward and H. E. Price, "PACSAT
Protocol: File Transfer Level 0 , " in
11 R. J. Diersing, "A simulator for Proc. 9 t h . ARRL c o m p u t e r N e t w o r k i n g
PACSAT-1 Downlink Traffic," in Proc. C o n f e r e n c e , London, Ontario, Canada,
AMSAT-NA N i n t h s p a c e S y m p o s i u m a n d 1990, pp. 209-231.
AMSAT/ARRL E d u c a t i o n a l workshop, Los
Angeles, CA, 1991, pp. 11-22. [ 131 J. W. Ward and H. E. Price, "PACSAT
File Header Definition,"in Proc. 9 t h .
21 R. J. Diersing and J. W. Ward, ARRL Computer Networking Conference,
"Packet Radio in the Amateur London, Ontario, Canada, 1990, pp.
Service," I E E E J. Selected A r e a s i n 245-252.
C o m m u n i c a t i o n s , vol. 7, pp. 226-234,
February, 19 89.

1 31 T. L. FOX, AX.25 A m a t e u r P a c k e t R a d i o
L i n k - L a y e r Protocol. Newington, CT:
American Radio Relay League, 1984.

t 41 J. A. King, R. MCGWier, H. Price, and

J. white, "The In-Orbit Performance
of Four Microsat Spacecraft,'" in
Proc. 4 t h . A n n u a l AIAA/USU C o n f e r e n c e
on S m a l l S a t e l l i t e s , Logan, UT, 1990.

1 51 H. E. Price and J. W. Ward, "PACSAT

Protocol Suite--An Overview, '' in
P r o c . 9 t h . ARRL C o m p u t e r N e t w o r k i n g
C o n f e r e n c e , London, Ontario, Canada,
1990, pp. 203-206.

[ 61 H. E. Price and J. W. Ward, "PACSAT

Broadcast Protocol," in Proc. 9 t h .
ARRL C o m p u t e r N e t w o r k i n g Conference,
London, Ontario, Canada, 1990, pp.
232-244.

1 71 H. E. Price and J. W. ward, "PACSAT

Data specification standards," in
Proc. 9 t h . ARRL C o m p u t e r N e t w o r k i n g
C o n f e r e n c e , London, Ontario, Canada,
1990, pp. 207-208.
E. Rosenberg and G. Garriot, "VITA
Operations Using UoSAT-3," in Proc.
AMSAT-NA N i n t h S p a c e s y m p o s i u m a n d
AMSAT/ARRL E d u c a t i o n a l Workshop, Los
Angeles, CA, 1991, pp. 125-136.
J. W. Ward, "Amateur Satellite
communications: UoSAT-OSCAR-22 in
Orbit," Q S T , vol. lxxv, pp.70-71,
September, 199 1.
J. W. Ward, ''Store-and-Forward
Message Relay Using Microsatellites:
The UoSAT-3 PACSAT communications
Payload," in Proc. 4th. Annual
AIAA/USU C o n f e r e n c e on S m a l l S a t e l -
l i t e s , Logan, UT, 1990.
J. W. Ward and H. E. Price, "Proto-
cols for Store-and-Forward Message
Switching Via Microsatellites," in
P r o c . 5 t h . A n n u a l AIAA/USU conference
on s m a l l s a t e l l i t e s , Logan, UT, 1991.

386