TX 312

TX312 Transmitter
Revision: 12/10
C o p y r i g h t © 2 0 0 0 - 2 0 1 0
C a m p b e l l S c i e n t i f i c , I n c .
Warranty and Assistance
The TX312 TRANSMITTER is warranted by Campbell Scientific, Inc. to be
free from defects in materials and workmanship under normal use and service
for twelve (12) months from date of shipment unless specified otherwise.
Batteries have no warranty. Campbell Scientific, Inc.'s obligation under this
warranty is limited to repairing or replacing (at Campbell Scientific, Inc.'s
option) defective products. The customer shall assume all costs of removing,
reinstalling, and shipping defective products to Campbell Scientific, Inc.
Campbell Scientific, Inc. will return such products by surface carrier prepaid.
This warranty shall not apply to any Campbell Scientific, Inc. products which
have been subjected to modification, misuse, neglect, accidents of nature, or
shipping damage. This warranty is in lieu of all other warranties, expressed or
implied, including warranties of merchantability or fitness for a particular
purpose. Campbell Scientific, Inc. is not liable for special, indirect, incidental,
or consequential damages.
Products may not be returned without prior authorization. The following

contact information is for US and International customers residing in countries
served by Campbell Scientific, Inc. directly. Affiliate companies handle
repairs for customers within their territories. Please visit
www.campbellsci.com to determine which Campbell Scientific company
serves your country.
To obtain a Returned Materials Authorization (RMA), contact Campbell

Scientific, Inc., phone (435) 753-2342. After an applications engineer
determines the nature of the problem, an RMA number will be issued. Please
write this number clearly on the outside of the shipping container. Campbell
Scientific's shipping address is:
CAMPBELL SCIENTIFIC, INC.

RMA#_____
815 West 1800 North
Logan, Utah 84321-1784
For all returns, the customer must fill out a “Declaration of Hazardous Material
and Decontamination” form and comply with the requirements specified in it.
The form is available from our website at www.campbellsci.com/repair. A
completed form must be either emailed to repair@campbellsci.com or faxed to
435-750-9579. Campbell Scientific will not process any returns until we
receive this form. If the form is not received within three days of product
receipt or is incomplete, the product will be returned to the customer at the
customer’s expense. Campbell Scientific reserves the right to refuse service on
products that were exposed to contaminants that may cause health or safety
concerns for our employees.
TX312 Transmitter Table of Contents
PDF viewers note: These page numbers refer to the printed version of this document. Use
the Adobe Acrobat® bookmarks tab for links to specific sections.
1. Introduction..................................................................1
2. GOES System...............................................................3
2.1 Orbit..........................................................................................................3
2.2 NESDIS and Transmit−Windows.............................................................3
2.3 Data Retrieval ...........................................................................................3
3. TX312 Functions ..........................................................4

3.1 LED Function ...........................................................................................4
3.2 Diagnostics Switch ...................................................................................5
3.3 Communication Ports ...............................................................................5
3.3.1 RS-232 Port.....................................................................................5
3.3.2 CS I/O Port......................................................................................5
3.3.3 SDI-12 Serial Port...........................................................................5
3.4 RF Connectors ..........................................................................................6
3.4.1 RF Transmission Connector............................................................6
3.4.2 GPS Connector................................................................................6
3.5 Power Connector ......................................................................................6
4. SatCommand Software ...............................................9

4.1 Install SatCommand..................................................................................9
4.2 SatCommand General Description............................................................9
4.3 Making Edits.............................................................................................9
4.3.1 NESDIS ID .....................................................................................9
4.3.2 Timed Channel................................................................................9
4.3.3 Timed Bit Rate ..............................................................................10
4.3.4 Timed Interval...............................................................................10
4.3.5 First Timed Transmission .............................................................10
4.3.6 Timed Tx Window ........................................................................10
4.3.7 Timed Msg Format........................................................................10
4.3.8 Random Channel...........................................................................10
4.3.9 Random Bit Rate ...........................................................................11
4.3.10 Random Randomizing Interval ...................................................11
4.3.11 Random Randomizing Percentage ..............................................11
4.3.12 Random Repeat Count ................................................................11
4.3.13 Random Data Format ..................................................................11
4.3.14 Random Msg Counter .................................................................11
4.4 Save and Transfer the Settings to the TX312..........................................11
4.5 Using SatCommand for TX312 Testing .................................................12
4.5.1 Terminal Window .........................................................................12
4.5.2 Commands ....................................................................................12
4.5.2.1 Recall Configuration Settings..............................................12
4.5.2.2 Position................................................................................12
4.5.2.3 Version ................................................................................12
i
4.5.2.4 GPS Status .......................................................................... 12

4.5.2.5 Read Audit Log................................................................... 13
4.5.2.6 Enable Transmitter.............................................................. 13
4.5.2.7 Disable Transmitter ............................................................ 13
4.5.2.8 Max Timed Message Length .............................................. 13
4.5.2.9 Max Random Message Length ........................................... 13
4.5.2.10 Clear Timed Buffer........................................................... 13
4.5.2.11 Clear Random Buffer........................................................ 13
4.5.2.12 Send to Timed Buffer ....................................................... 13
4.5.2.13 Send to Random Buffer .................................................... 13
4.5.2.14 SDI-12 Configuration ....................................................... 13
4.5.2.15 Show Defaults................................................................... 14
5. Programming the Datalogger ...................................14

5.1 CRBasic Programming........................................................................... 14
5.1.1 GoesData ...................................................................................... 14
5.1.1.1 Result Code......................................................................... 14
5.1.1.2 Data Table........................................................................... 14
5.1.1.3 Table Option ....................................................................... 14
5.1.1.4 Buffer Control..................................................................... 15
5.1.1.5 Data Format ........................................................................ 15
5.1.1.6 GOESData() Example......................................................... 16
5.1.2 GoesStatus.................................................................................... 17
5.1.2.1 GoesStatus Read Time........................................................ 17
5.1.2.2 GoesStatus Read Status ...................................................... 18
5.1.2.3 GoesStatus Read Last Message Status................................ 18
5.1.2.4 GoesStatus Read Error Register.......................................... 19
5.1.3 GoesGPS ...................................................................................... 21
5.1.4 GoesSetup..................................................................................... 22
5.1.4.1 Result Code......................................................................... 23
5.1.4.2 Platform ID ......................................................................... 23
5.1.4.3 Window .............................................................................. 23
5.1.4.4 Timed Channel.................................................................... 23
5.1.4.5 Timed Baud Rate ................................................................ 23
5.1.4.6 Random Channel ................................................................ 24
5.1.4.7 Random Baud Rate ............................................................. 24
5.1.4.8 Timed Interval .................................................................... 24
5.1.4.9 Timed Offset....................................................................... 24
5.1.4.10 Random Offset.................................................................. 24
5.1.4.11 GOESSetup Example........................................................ 24
5.2 Edlog Programming ............................................................................... 24
5.2.1 Deciding How Much Data will be Transmitted and When........... 25
5.2.2 Deciding What Data Format to Use ............................................. 25
5.2.3 Managing Data, Writing More Data than Will Be Transmitted ... 26
5.2.4 Sending Data to the Transmitter (P126) ....................................... 26
5.2.4.1 Buffer Control..................................................................... 27
5.2.4.2 Data Format ........................................................................ 27
5.2.4.3 P126 Result Codes.............................................................. 27
5.2.5 Read Status and Diagnostic Information from the TX312 ........... 28
5.2.5.1 P127, Command 0: Read Time.......................................... 29
5.2.5.2 P127, Command 1: Read Status......................................... 29
5.2.5.3 P127, Command 2: Read Last Message Status.................. 30
5.2.5.4 P127, Command 3: Transmit Random Message................ 30
5.2.5.5 P127, Command 4: Read TX312 Error Registers.............. 31
ii
5.2.5.6 P127, Command 5: Clear TX312 Error Registers ..............32

5.2.5.7 P127, Command 6: Return TX312 to on-line mode. ..........32
5.2.6 Edog Programming Examples.......................................................32
6. Field Installation ........................................................35

6.1 Field Site Requirements..........................................................................35
6.2 Transmission Antenna ............................................................................35
6.3 GPS Antenna ..........................................................................................36
6.3.1 How the GPS Signal is Acquired and Used ..................................36
6.3.2 GPS Antenna Location..................................................................36
Appendices
A. Information on Eligibility and Getting Onto

the GOES System............................................... A-1
A.1 Eligibility ............................................................................................ A-1
A.2 Acquiring Permission.......................................................................... A-1
B. Data Conversion Computer Program .................... B-1
C. Antenna Orientation Computer Program .............. C-1
D. RAWS-7 Data Format .............................................. D-1

D.1 Introduction......................................................................................... D-1
D.2 Format................................................................................................. D-1
D.3 Programming the Datalogger for RAWS-7 Format ............................ D-1
D.4 RAWS-7 Sample Data ........................................................................ D-2
D.5 Writing Additional Data Values Beyond the RAWS-7....................... D-3
E. GOES DCS Transmit Frequencies ......................... E-1
F. High Resolution 18-Bit Binary Format................... F-1
G. Extended ASCII Command Set ..............................G-1
H. GOES/Radio Set Certification ................................ H-1
Figures
2-1. Major Components of the GOES/DCP System .......................................4
3-1. TX312 Label............................................................................................7
3-2. TX312 Connectors...................................................................................8
3-3. DCP Enclosure ........................................................................................8
iii
Tables
5.1-1. GoesStatus Command 0: Read Time ................................................ 18
5.1-2. GoesStatus Command 1: Read Status............................................... 18
5.1-3. GoesStatus Command 2: Read Last Message Status ........................ 19
5.1-4. GoesStatus Command 4: Read TX312 Error Registers .................... 19
5.1-5. Error Codes........................................................................................ 20
5.1-6. Result Codes Indicating Communication Problems .......................... 23
5.1-7. GoesSetup and GoesData Runtime Result Codes.............................. 23
5.2-1. P127 Result Codes ............................................................................. 29
5.2-2. P127 Command 0: Read Time.......................................................... 29
5.2-3. P127 Command 1: Read Status......................................................... 30
5.2-4. P127 Command 2: Read Last Message Status.................................. 30
5.2-5. P127 Command 3: Initiate Random Transmission ........................... 31
5.2-6. P127 Command 4: Read TX312 Error Registers.............................. 31
5.2-7. Error Codes........................................................................................ 32
5.2-8. P127 Command 5: Clear Error Registers.......................................... 32
5.2-9. P127 Command 6: Force On-line Mode ........................................... 32
D-1. RAWS-7 Output ................................................................................ D-2
iv
TX312 Transmitter
1. Introduction
The TX312 transmitter supports one-way communication, via satellite, from a
Campbell Scientific datalogger to a ground receiving station. Satellite
telemetry offers a convenient telecommunication alternative for field stations
where phone lines or RF systems are impractical.
The TX312 utilizes non-volatile memory to store configuration information,

such as platform ID, transmission baud rate, channel number, scheduled
transmission time, offset time and message window length. The TX312 also
has a 15.7 K byte RAM buffer for scheduled transmissions and a buffer for
random transmissions. The clock is maintained with a GPS receiver.
TX312 supports the following certification standards:
• 300/1200 BPS DCPRS Certification Standard version 1.0b - March 2000

• 100 BPS Self-timed DCPRS Certification Standard - November 1981
• 100 BPS Random DCPRS Certification Standard - November 1981
• SDI-12, A Serial-Digital Interface Standard for Microprocessor-based
Sensors version 1.2 - October 21, 1996
High data rates are supported. The TX312 includes serial communication
ports:
• CS I/O for Campbell dataloggers

• RS-232 port used for dataloggers and PC communication
• SDI-12 is used where only SDI-12 sensors are used and a datalogger is not
needed
The CS I/O port is a Campbell Scientific Synchronous Device for

Communication (SDC) port.
NOTE The 21X and CR7 dataloggers do not support SDC or the
TX312.
NOTE The National Environmental Satellite, Data, and Information

Service (NESDIS) certification of the TX312 was done for
Forest Technology Systems, Ltd. under model name FTS
TX312. See Appendix H for a copy of the certification
certificate.
1
TX312 Transmitter
Specifications:
On-board memory: Non-volatile flash for setup parameters. 16 kbytes for

data
Transmission Data
Rates: 100, 300 and 1200 bps
Power requirements: 10.8 to 16 VDC, 5 mA quiescent, 90 mA during GPS
fix and 2.6 Amps during transmission
25316 Transmit
Antenna: 11 dBi Gain, Right Hand Circular polarization, Type
N female connector, wind load of ~100 knots
Transmit power: 5.6 watts for 100 and 300 bps, 11.2 watts for 1200 bps
Frequency Range: 401.701 MHz to 402.09850 MHz
Frequency Stability: Initial Accuracy: ±20 Hz disciplined to GPS; Short
term drift: ±0.04 Hz/sec, Ageing: ±-0.1 ppm/Year,
Vcc + Temperature: ±-0.1 PPM
Channel Bandwidth: 100/300 bps 1.5 kHz; 1200 bps 3 kHz
Time Keeping: Initial setting accuracy: ± 100 microseconds
synchronized to GPS; Drift ± 10 milliseconds/day over
operating temperature range; GPS scheduled updates
are 1 at power up and once per day there after. Once
every 28 days required for continual operation
GPS antenna: 3.3 volt active; SMA female connector
RS-232 serial port: Signal Levels: RS-232C; Connector: DB9F; Command
protocols: ASCII, Binary, Field diagnostics,
Dataloggers with RS-232 port
CS I/O port: Signal Levels: TTL, Connector DB9M; Command
Protocol: Campbell Scientific Synchronous Device
Communication, Binary Command, Campbell
Scientific Dataloggers.
SDI-12 Port: Multiplexed with CS I/O port. Protocol SDI-12
Recorder version 1.3
Environmental: Operating: -40° to 60°C; Storage -50º to 70ºC; 0 to
99% RH, non-condensing
Dimensions (with
mounts): 6.4” H x 11” L x 2.1” W (16.2 x 27.9 x 5.3 cm)
Weight: 2.1 lbs (0.95 kg)
2
TX312 Transmitter
2. GOES System
2.1 Orbit
The TX312 transmitter sends data via Geostationary Operational
Environmental Satellites (GOES). GOES satellites have orbits that coincide
with the Earth's rotation, allowing each satellite to remain above a specific
region. This allows a user to point the GOES antenna at a fixed position in the
sky.
There are two satellites, GOES East and GOES West. GOES East is located at
75° West longitude and GOES West is located 135° West longitude. Both
satellites are located over the equator. Within the United States, odd numbered
channels are assigned to GOES East. Only even numbered channels are
assigned to GOES West. Channels used outside the United States are assigned
to either spacecraft.
2.2 NESDIS and Transmit−Windows

GOES is managed by the National Environmental Satellite Data Information
Service (NESDIS). NESDIS assigns the platform ID, uplink channel number,
and self-timed or random transmit windows. Self-timed windows allow data
transmission only during a predetermined time frame (typically one minute or
less, every one, three, or four hours). The self-timed data is erased from the
transmitter's buffer after each transmission, random data is not. Random
windows are for critical applications (e.g., flood reporting) and allow
transmission immediately after a threshold has been exceeded. The
transmission is then randomly repeated to ensure it is received. A combination
of self-timed and random transmission can be executed by the TX312.
2.3 Data Retrieval

Data retrieval via the TX312 and the GOES system is illustrated in Figure 2-1.
The DAPS User Interface Manual, provided by NOAA/ NESDIS, describes the
process of retrieving the data from the NESDIS ground station. The data are in
the form of 3-byte ASCII (see Appendix B for a computer program that
converts the data to decimal). You can also retrieve data directly from the
NESDIS ground station via the DOMSAT satellite downlink. DOMSAT is
only practical for organizations with many GOES users; contact NESDIS for
more information (see Appendix A).
3
TX312 Transmitter
GOES Satellite
Satellite Antenna
GOES transmitter,
datalogger, and
power supply, also
known as a DCP
Data Collection Platform (DCP) Ground Receiving Station
FIGURE 2-1. Major Components of the GOES/DCP System
3. TX312 Functions
3.1 LED Function
The TX312 has four LEDs used to indicate the state of the TX312 transmitter.
When power is first applied to the TX312, the four LEDs will cycle through
quickly, then the Synchronizing Clock to GPS LED will light for 15 minutes.
If there are data in a buffer waiting for transmission time, the Data In Buffer
LED will light.
During transmission, the Transmitting LED will light.
The Fault LED will only light after the Diagnostics button has been depressed.
Press and hold the Diagnostics button for about 2 seconds. The Fault LED will
flash once to indicate the Failsafe has not been tripped. If the LED flashes
twice, the Failsafe has tripped. To clear the Failsafe, press and hold the
diagnostic button for about 10 seconds. If the failsafe has tripped, the
transmitter probably needs to be returned for service.
4
TX312 Transmitter
3.2 Diagnostics Switch

The Diagnostics switch has two purposes. Press and hold the Diagnostics
button for about 2 seconds. The Fault LED will flash once to indicate the
Failsafe has not been tripped. If the LED flashes twice, the Failsafe has
tripped. To clear the Failsafe, press and hold the diagnostic button for about
10 seconds. If the failsafe has tripped, the transmitter probably needs to be
returned for service.
The Failsafe circuit is designed to shut down a malfunctioning transmitter that

is transmitting too long or too often. The Failsafe circuit helps prevent
malfunctioning transmitters from interfering with other transmissions.
3.3 Communication Ports

3.3.1 RS-232 Port
The RS-232 port is a DB9 female connector configured as DCE. Only three
pins are used, transmit on pin two, receive on pin three, and ground on pin
five. Transmit is an output and receive is an input to the TX312.
The RS-232 port is used in conjunction with a PC and the 32 bit windows
compatible software, SatCommand. SatCommand software is used to read,
write, save, and transmit the configuration information from the computer to
the TX312 transmitter. SatCommand is also used to read status information
from the transmitter. The RS-232 port also supports dataloggers.
3.3.2 CS I/O Port

The CS I/O port is a Campbell Scientific Synchronous Device for
Communication (SDC) port. The CS I/O port is specifically designed to work
with Campbell Scientific SDC capable dataloggers. The CS I/O port is used
by Campbell Scientific dataloggers to transfer data from the datalogger to the
TX312 transmitter. The CS I/O SDC port allows other SDC devices and one
modem enabled device to be connected to the same port at the same time.
Only one device can be active at a time. This SDC port will allow the TX312
transmitter, the RF95A RF modem and a phone modem to be connected to the
CSI datalogger serial port all at the same time. The CS I/O port is a DB9 male,
voltage levels are TTL, pin out is:
1, 3, 5, 8 are not used
2 = Ground
4 = RXD (output)
6 = SDE (input)
7 = CLK (input)
9 = TXD (input)
3.3.3 SDI-12 Serial Port

The SDI-12 serial port is used by the TX312 only when a datalogger is not
used. Under most operating conditions, the datalogger is responsible for the
SDI-12 functions.
5
TX312 Transmitter
3.4 RF Connectors
3.4.1 RF Transmission Connector
The TX312 utilizes the type N female connector for RF power out. This
connector must have a proper antenna connection before transmission occurs.
Failure to use a properly matched antenna cable and antenna may cause
permanent damage to the RF amplifiers. The nominal impedance is 50 ohms,
the frequency range is approximately 400 to 403 MHz. At 100 and 300 BPS
transmission rates, the nominal EIRP is 48 dBm with an 11 dBic gain antenna.
At 1200 BPS, the nominal EIRP is 52 dBm.
3.4.2 GPS Connector

The GPS connector is an input to the TX312. Operation without an antenna
connected will not cause damage, but the transmitter will not transmit without
a valid GPS fix. The GPS connector is an SMA female. The GPS receiver
uses an active 3.3 V antenna.
The TX312 transmitter uses the GPS receiver for two functions. The precise
GPS time is used to ensure scheduled transmissions occur at the proper time.
The one-second GPS synchronization pulse is used to ensure a precise, drift-
free carrier frequency. See Section 6.3 for more information regarding GPS
and GPS antenna placement.
3.5 Power Connector

The TX312 power connector has two pins: ground and 12 V. The input power
requirement is 10.8 to 16 VDC at 3 amps. Because the TX312 can use up to 3
amps, the power should be connected directly to the battery. An in-line 7 amp
fast blow fuse can be used to help protect the transmitter. The TX312 is
shipped with a power cable that includes the fuse and a connector arrangement
that allows the transmitter to pull power directly from the battery when using
the CH100, PS100, PS12LA or CH12R power supply.
With the potential for a 3000 mA current drain, the voltage drop along the
battery power leads must be considered. The battery power leads are both
wires that run from the battery to the power input connectors of the TX312.
To calculate the voltage drop along the power leads, we must know the
resistance of the wire and the length of the wire. Usually the resistance of the
wire is listed as ohms per 1000 feet. As an example, a 24 AWG wire used by
CSI has a resistance of 23 ohms per 1000 feet. The length of the wire is the
distance the wire travels from the battery to the transmitter multiplied by two.
You must consider the current travels from the battery, to the transmitter and
back to the battery.
The TX312 will operate with a battery voltage range from 10.8 V to 16 V. A
fully charged lead acid battery will have a voltage of about 12.5 V. If the
battery is fully charged, a 1.7 V drop along the battery leads will stop the
transmitter from transmitting. At 3 amps, 1.7 V will be dropped with 0.566
ohms of resistance. Using the 24 AWG wire with 23 ohms resistance per 1000
ft, 24 feet of wire (battery power leads 12 ft long) will prevent transmission. A
reliable system that will transmit without a perfect battery voltage will
minimize voltage drop along the battery power leads. To minimize voltage
6
TX312 Transmitter
drop, keep the battery power leads short. A five-foot power lead is a long
power lead. If you must have a longer lead, use heavy wire. For power leads
less than ten feet but more than five feet, use no smaller than 18 AWG.
FIGURE 3-1. TX312 Label
7
TX312 Transmitter
FIGURE 3-2. TX312 Connectors
FIGURE 3-3. DCP Enclosure
8
TX312 Transmitter
4. SatCommand Software
Certain information required by NESDIS is unique to each DCP. This setup
information includes: platform ID, transmission baud rate, channel number,
scheduled transmission time, offset time, and message window length. The
TX312 has non-volatile memory to store the setup information. The setup
information is entered in the SatCommand software, then transferred to the
TX312. SatCommand software is a 32-bit windows application. The TX312
can be setup using terminal emulation software, but the process requires
knowledge of the ASCII commands. See the appendix section for a list of
appropriate commands.
4.1 Install SatCommand

Follow instructions on the disk.
4.2 SatCommand General Description

SatCommand has a status window, a terminal window, several control buttons,
a main menu, and an edit window used to make setup changes.
The Terminal window is used to manually enter commands to the transmitter.

The Status window is used to display information regarding the current state of
the transmitter. The control buttons are used to initiate some communications
between the computer and the TX312 transmitter. The main menu is across the
top of the screen and includes some file control functions, a list of commands
that can be sent to the transmitter, and a couple of tools. The edit window is
where changes to the transmitter setups are to be entered and saved for later
use.
4.3 Making Edits

Edits are made in the configuration window. The configuration window has
two columns; use the right column for all edits. When SatCommand is first
started, a default setup template is loaded. If the Retrieve Settings button is
selected, the current configuration of the TX312 will be loaded to the fields of
the edit window.
4.3.1 NESDIS ID
Edit the NESDIS ID number. Type in your NESDIS assigned ID number.
This is an 8-digit hex number. Valid characters are 0-9, A, B, C, D, E and F.
Example: 4F3E2D1E
4.3.2 Timed Channel

The Timed Channel is the NESDIS assigned self-timed transmission channel.
When using 100 and 300 baud, valid channel numbers are between 0 and 267.
When using 1200 baud, valid channel numbers are 0 to 133, where 101 to 133
are international channels. For 1200-baud channels, the formal channel
designation is the channel number followed by the letter A, for example: 99A.
For clarification, see Appendix E. If your assigned channel number does not
include the letter A, either you don’t have a 1200-baud channel assignment or
9
TX312 Transmitter
you’ve been given a 100/300 channel number. In SatCommad, don’t enter the
letter A. When 0 is entered, self-timed transmissions are disabled.
4.3.3 Timed Bit Rate

Enter the assigned channel bit rate (baud rate). Valid entries are 100, 300, or
1200. The bit rate is assigned by NESDIS and is tied to the channel number.
Using the wrong bit rate will prevent NESDIS from receiving your data.
4.3.4 Timed Interval

The Timed Interval is how often data is transmitted. The options include days,
hour, minutes, and seconds. Generally the interval will be zero days, 1 hour,
zero minutes, and zero seconds.
4.3.5 First Timed Transmission

The First Timed Transmission is also referred to as the Offset. The first timed
transmission will always be between zero and the timed interval. The TX312
will transmit on the next Timed Interval after the clock has been set.
4.3.6 Timed Tx Window

The Timed Transmit Window is the length of the assigned self-timed transmit
window in seconds. Valid entries are 5 to 120 seconds in 1 second increments.
4.3.7 Timed Msg Format

The Timed Message Format determines how the flag word is written and
which characters are legal. Select A if the data format is ASCII, select P for
Pseudo Binary, option B has not yet been defined by NESDIS. Please note:
The Timed Msg Format does not change the format of the data; instead, the
flag word is changed. The datalogger program determines the data format and
must match the format selected in the Timed Msg Format option.
4.3.8 Random Channel

If NESDIS has not assigned a Random Channel, Sections 4.3.8 through 4.3.14
do not apply.
The Random Channel is the NESDIS assigned random transmission channel.

When using 100 and 300 baud, valid channel numbers are between 0 and 267.
When using 1200 baud, valid channel numbers are 0 to 133, where 100 to 133
are international channels. For 1200-baud channels, the formal channel
designation is the channel number followed by the letter A, for example: 99A.
For clarification, see Appendix E. If your assigned channel number does not
include the letter A, either you don’t have a 1200-baud channel assignment or
you’ve been given a 100/300 channel number. In SatCommad, don’t enter the
letter A. When 0 is entered, self-timed transmissions are disabled.
10
TX312 Transmitter
4.3.9 Random Bit Rate

Enter the assigned channel bit rate (baud rate). Valid entries are 100, 300, or
1200. The bit rate is assigned by NESDIS and is tied to the channel number.
Using the wrong bit rate will prevent NESDIS from receiving your data.
4.3.10 Random Randomizing Interval

The Randomizing Interval is the average time between random transmissions.
When the TX312 receives data in the random data buffer, a random
transmission is scheduled. After the first transmission, the transmitter will
select a pseudo random time somewhere within the randomizing interval. This
process is repeated until the Random Repeat Count has been met, or the
datalogger removes the data from the random buffer.
4.3.11 Random Randomizing Percentage

Enter the percent of the randomizing interval that should be used in the
randomizing of random transmissions. Valid entries are 10 to 50, representing
10 to 50 percent of the randomizing interval.
4.3.12 Random Repeat Count

Enter the total number of random transmissions you want repeated after data
has been loaded to the random data buffer. Typically, 5 works well.
4.3.13 Random Data Format

The Random Message Format determines how the flag word is written and
which characters are legal. Select A if the data format is ASCII, Select P for
Pseudo Binary, option B has not yet been defined by NESDIS. Please note:
The Random Msg Format does not change the format of the data; instead, the
flag word is changed. The datalogger program determines the data format and
must match the format selected in the Random Msg Format option.
4.3.14 Random Msg Counter

The Random Msg Counter will insert a counter at the beginning of the data
stream. The counter indicates the number of random messages sent so far.
4.4 Save and Transfer the Settings to the TX312

Using the drop list, select the appropriate RS-232 communication port for your
computer.
Using a standard RS-232 serial cable, connect the Computer RS-232 serial port
to the TX312 RS-232 serial port. Apply 12 volts DC to the Power terminal.
Test the communications link by typing the enter key with the cursor in the
Terminal window. The TX312 will respond with the > character whenever the
Carriage Return character is received on the TX312 serial port.
11
TX312 Transmitter
After the information from Section 4.3 has been entered, select the Save/Send
Settings button. Provide a file name to save the settings to disk, then select the
Yes button on the Send to Transmitter dialog box. The settings will be
transferred to the TX312.
Once the transfer is complete, select the Status button to verify the transmitter
is setup and enabled. Specifically, look for the line that says Transmitter:
Enabled. If Transmitter: Disabled is shown, then the configuration settings
have an illegal parameter, or the transfer didn’t succeed.
4.5 Using SatCommand for TX312 Testing

4.5.1 Terminal Window
The Terminal is always open and ready for use. The Open Port button will
open the serial port, then change to Close Port. If the port is closed, typing in
the terminal window will open the port. To use the terminal window, use a
standard serial cable to connect the serial port of the computer to the RS-232
port of the TX312. SatCommand can be used to send data to the transmitter,
read the Audit Log, GPS Status, etc. The Terminal window supports
manually-entered commands (see the appendix for individual command). The
Terminal Window also supports automated commands found under Main
Menu/Commands.
4.5.2 Commands
From the main menu select Commands. Within the Commands menu there are
several useful commands that can be issued to the TX312. Both the command
and the TX312 response are shown in the Terminal Window.
4.5.2.1 Recall Configuration Settings

Recall Configuration Settings is best for experienced TX312 users. All the
settings are displayed in the terminal window, but each setting is not labeled.
Instead, the command used to read or set the setting is displayed before the
actual setting is displayed.
4.5.2.2 Position
Position will retrieve the time of the last GPS fix, Latitude, Longitude, and
Altitude in meters.
4.5.2.3 Version
Version will display information about the TX312 hardware and software. The
unit serial number, hardware version number, firmware version number, and
GPS version are displayed.
4.5.2.4 GPS Status

GPS Status will display if the GPS power is on or off. If the GPS is powered,
the GPS system reports the satellites currently tracked and the signal strength
from each spacecraft. If the GPS is off, use the Position or Read Audit Log
option to verify if the GPS system has obtained a GPS fix.
12
TX312 Transmitter
4.5.2.5 Read Audit Log

The Read Audit Log will display a history of the transmitter operation. The
latest entry in the audit log is shown at the top of the screen. The audit log will
record any error condition that has occurred in the past, plus other events.
4.5.2.6 Enable Transmitter

The Enable transmitter will enable the transmissions if the transmitter setup
parameters are all valid; otherwise, the transmitter cannot be enabled.
4.5.2.7 Disable Transmitter

The Disable Transmitter option is used to prevent the transmitter from
transmitting until it has been enabled.
4.5.2.8 Max Timed Message Length

The Maximum Timed Message Length command will calculate the maximum
number of bytes that can be sent given the current configuration of the
transmitter. To calculate the maximum number of bytes that can be sent, the
transmitter looks at the data rate (bits per second), and the message window
length. To convert the number of bytes that can be sent to the number of data
points that can be sent, divide the number of bytes by 3 if using Pseudo Binary
or by 7 if using an ASCII format.
4.5.2.9 Max Random Message Length

See Section 4.5.3.8 for details. The random message does not have a fixed
limit on message window size, but random messages should be kept as short as
possible to increase the likelihood of successful reception.
4.5.2.10 Clear Timed Buffer

The Clear Timed Buffer command will erase all data from the timed buffer.
4.5.2.11 Clear Random Buffer

The Clear Random Buffer command will erase all data from the random
buffer.
4.5.2.12 Send to Timed Buffer

The Send to Timed Buffer command is used to send data to the timed buffer.
Data will then be scheduled for transmission on the next available time slot.
4.5.2.13 Send to Random Buffer

The Send to Random Buffer command is used to send data to the random
buffer. Data will then be scheduled for transmission very soon.
4.5.2.14 SDI-12 Configuration

The SDI-12 configuration selects whether the SDI-12 or CS I/O port is active.
If the datalogger is unable to send data, use this command to check which port
is active. The CS I/O port is deactivated when the SDI-12 port has been
selected. The CS I/O port must be selected to use a datalogger.
13
TX312 Transmitter
4.5.2.15 Show Defaults

The Show Defaults will populate the edit window with default values, which
are not valid for transmission. Selecting show defaults, then sending the
defaults to the transmitter will return the transmitter to factory default settings
and prevent transmission of data. Once the defaults are loaded to the edit
window, the defaults can be edited. Sometimes it is useful to start from a
known condition.
5. Programming the Datalogger

5.1 CRBasic Programming
This section covers CRBasic programming concepts for the CR295(X),
CR800, CR850, CR1000, CR3000, and CR5000 dataloggers. Not all options
are available for the CR5000 and CR295(X) dataloggers. There are four
program instructions directly related to the TX312 GOES transmitter:
GoesData, GoesStatus, GoesGPS and GoesSetup.
5.1.1 GoesData
The GoesData instruction is used to send data from the datalogger to the
TX312 transmitter. Each time GoesData is executed, data is ordered with the
newest data to be transmitted first, which is opposite of how Edlog dataloggers
arrange data.
There are five parameters to the GoesData instruction: Result Code, Data
Table, Table Option, Buffer Control, and Data format.
In GoesData(), Table Option, Buffer Control, and Data Format can be

variables declared as type long. Error checking is done at run time instead of
compile time. See Table 5.1-7 for runtime error codes.
Using CRBasic dataloggers, time of Max, Min, etc. are stored as number of
seconds since 1990, which does not work for GOES transmission.
5.1.1.1 Result Code

The result code is used to determine if the GoesData instruction executed
successfully. When successful, GoesData will return a zero to the Result Code
variable. When GoesData executes successfully, but there is no new data in
the specified table, the result code is set to 100. See Table 5.1-6 for details
regarding result codes.
5.1.1.2 Data Table

The Data Table argument is used to specify which data table the GoesData
instruction is to copy data from.
5.1.1.3 Table Option

The Table Option is used to specify what data is copied from the data table.
There are three options. Use zero to specify all new data. Use one to specify
only the most current record. Use any other positive number to specify the
14
TX312 Transmitter
number of records to be copied each time GoesData is executed. When

copying data, the entire record is copied from the datalogger to the TX312
transmitter.
5.1.1.4 Buffer Control

Buffer Control is used to determine which buffer data is copied to, and if the
buffer is erased before data is copied to the buffer. Use Zero to append to the
self-timed buffer, use 1 to overwrite the self-timed buffer. Use 2 to append to
the random buffer, and 3 to overwrite the random buffer.
5.1.1.5 Data Format

Data Format is used to determine what format the data is transmitted in. This
is the format of the data sent over the satellite. The TX312 does not determine
the actual data format used, but can be set to match for data format selected
with the GoesData instruction. Use zero for CSI floating point pseudo binary.
Use 1 for floating point ASCII. Use 2 for 18 bit signed integer pseudo binary.
Options 3 through 8 are used for RAWS7 or Fire Weather applications.
Option 9 is used to clear the random buffer.
In dataloggers that support strings as a data type, all data format options except
3 (RAWS7) will support strings. Strings are transmitted from the first
character until the null terminator. If strings contain illegal characters, the
TX312 will replace the character with another character. By default the
replacement character is an asterisk. The replacement character can be
changed.
NOTE Both the random and timed buffers of the TX312 can be set to
accept ASCII or Pseudo Binary data. If the TX312 is set to
Pseudo Binary, all ASCII data is transmitted as the replacement
character, which is an Asterisk by default. When the TX312 is
set to ASCII data, both Pseudo Binary and ASCII data are
transmitted normally. Data format options zero and 2 are Pseudo
Binary, all others are ASCII.
NOTE When transmitting random messages in pseudo binary format the

message counter must be turned off (RMC=N). The message
count is a simple 3 digit count of how many times the
transmission has been repeated. Digits (0 - 9) are not legal
characters in pseudo binary mode and are replaced at
transmission time with the replacement character specified by
the IRC command. The default IRC character is *. If the random
message counter is on when the random data format is set to
pseudo binary, the first 3 characters sent are 0x20,0x20,0x2a
(space,space,*) instead of the intended 0x20,0x20,0x31
(space,space,1).
15
TX312 Transmitter
NOTE The order data appears in each transmission can be controlled.

Only whole records are copied from the datalogger to the
TX312. Each record is copied in the same order it appears in the
datalogger memory. The order of data records, oldest to newest
or newest to oldest, can be controlled. To arrange data records
oldest to newest, execute the GoesData instruction when data is
written to the data table. To arrange data newest to oldest,
execute the GoesData instruction once per timed transmission.
Either method works best when the table option is set to zero.
5.1.1.6 GOESData() Example

' GOESData() Example
' Sample program makes a few simple measurements and

' stores the result in the table named Tempdata.
' All new data from TempData is copied to the
' transmitter hourly.
' An hourly record containing stats regarding

' the Last GOES message are stored in another table
'declarations
Public TCTemp
Public PanelT
Public battery1
Public RC_Data
Public LastStatus(14)
Alias LastStatus(1)=RC_Last
Alias LastStatus(2)=Lst_Type
Alias LastStatus(3)=Lst_Bytes
Alias LastStatus(4)=Lst_Forward
Alias LastStatus(5)=Lst_Reflected
Alias LastStatus(6)=Lst_BattVolt
Alias LastStatus(7)=Lst_GPS
Alias LastStatus(8)=Lst_OscDrift
Alias LastStatus(9)=Lat_Deg
Alias LastStatus(10)=Lat_Min
Alias LastStatus(11)=Lat_Secd
Alias LastStatus(12)=Long_Deg
Alias LastStatus(13)=Long_Min
Alias LastStatus(14)=Long_Secd
'program table
DataTable (Tempdata,1,1000)
DataInterval (0,15,min,10)
Sample (1,TCTemp,FP2)
Sample (1,PanelT,FP2)
Sample (1,battery1,FP2)
EndTable
16
TX312 Transmitter
DataTable(GoesStats,true,300)
DataInterval(0,1,hr,0)
Sample(14,LastStatus(),fp2)
EndTable
BeginProg
Scan (10,Sec,3,0)
Battery (battery1)
PanelTemp (PanelT,250)
TCDiff (TCTemp,1,mV25C ,2,TypeT,PanelT,True ,0,250,1.8,32)
CallTable TempData
If IfTime (0,1,Hr)
GOESData (RC_Data,TempData,0,0,1)
EndIf
If IfTime (0,10,min)
GOESStatus (LastStatus(),2)
EndIf
CallTable GoesStats
NextScan
EndProg
5.1.2 GoesStatus
The GoesStatus instruction is used to read information from the TX312.
Information that can be read and stored in the datalogger includes information
relating to the next transmission, the last transmission, GPS time and position,
and all logged errors. The status information can be used to set the datalogger
clock and troubleshoot any problems that might arise. The GoesStatus
instruction also includes options to initiate a random transmission on
command.
The GoesStatus instruction includes seven different functions: Read Time,

Read Status, Read Last Message Status, Transmit Random Message, Read
Error Register, Clear Error Register, Return transmitter to on-line mode.
GoesStatus expects two parameters. The first is the array used to store the data
returned by GoesStatus, the second is the command to be issued. The first
element of each array returned by the GoesStatus command is the result code.
The result code is used to test if the GoesStatus instruction executed
successfully. When the result code is zero, GoesStatus executed successfully.
See Table 5.1-2 for details.
5.1.2.1 GoesStatus Read Time

Example:
Public gps(4)
GoesStatus (gps(), 0)
Command zero (Read Time) will read the TX312 clock. Under normal
operating conditions the time is GMT, and quite accurate. There are delays in
17
TX312 Transmitter
reading the time from the TX312. The array needs to be four elements or
more. Data is returned as: Result Code, Hour, Minute, Second.
TABLE 5.1-1. GoesStatus Command 0: Read Time
Index Contents
1 Command Result Code
2 Hours (GMT)
3 Minutes
4 Seconds
5.1.2.2 GoesStatus Read Status

Example:
Public Stats(13)
GoesStatus(Stats(), 1)
Command 1, (Read Status) is used to read information regarding the current

status of the transmitter. Information returned includes the number of bytes in
each data buffer, time until transmission and a loaded battery voltage.
TABLE 5.1-2. GoesStatus Command 1: Read Status
Index Contents
2 Bytes of data in self-timed buffer
3 Time until next self-timed transmission: Days
4 Time until next self-timed transmission: Hours
5 Time until next self-timed transmission: Minutes
6 Time until next self-timed transmission: Seconds
7 Bytes of data in random buffer
8 Time until next random transmission interval start: Hours
9 Time until next random transmission interval start: Minutes
10 Time until next random transmission interval: Seconds
11 Failsafe, 1 indicates transmitter disabled due to failsafe.
12 Loaded power supply voltage, 1 amp load. (tenths of volts)
13 Average GPS acquisition time (tens of seconds)
5.1.2.3 GoesStatus Read Last Message Status

Example:
Public LastStats(14)
GoesStatus(LastStats(), 2)
Command 2 (Read Last Message Status) is used to read information regarding

the last transmission. Information includes the type of transmission, size,
forward power, reflected power, etc. Also returned is the GPS derived
Latitude and Longitude, which is updated once a day. The GPS update
interval can be changed.
18
TX312 Transmitter
TABLE 5.1-3. GoesStatus Command 2: Read Last Message Status
Index Contents
2 Message type: Self-timed or Random
3 Size of message in bytes
4 Forward power in tenths of watts
5 Reflected power in tenths of watts
6 Power supply voltage under full load, in tenths of volts
7 GPS acquisition time in tens of seconds
8 Oscillator drift (signed, hundreds of Hz)
9 Latitude degrees
10 Latitude minutes
11 Latitude seconds
12 Longitude degrees
13 Longitude minutes
14 Longitude seconds.
5.1.2.4 GoesStatus Read Error Register

Example:
Public Errors(10)
GoesStatus(Errors(), 4)
Command 4 (Read Error Register) is used to return the total number of errors
that have occurred, and codes describing the last four errors. When the
command that caused the error is listed as 31, the error is an internal fault.
Otherwise the error is just a communication error.
TABLE 5.1-4. GoesStatus Command 4: Read TX312 Error Registers
Index Contents
1 Result Code
2 Number of Errors
3 Command that Caused the Error
4 Error Code
6 Error Code
8 Error Code
10 Error Code
19
TX312 Transmitter
TABLE 5.1-5. Error Codes
Error Codes:
Decimal
00 No error
01 Illegal command
02 Command rejected
03 Illegal checksum or too much data
04 Time out or too little data
05 Illegal parameter
06 Transmit buffer overflow
16 PLL lock fault
17 GPS fix fault
18 Input power supply fault
19 Software fault
20 Failsafe fault
21 GPS time synchronization fault
22 SWR fault – RF Load
23 Time Synch edge 1 detect fault
24 Time Synch edge 2 detect fault
25 Internal RF power supply failure
The TX312 has registers used to store information about errors that have
occurred. The total number of errors is stored, up to 255. Also stored is the
command that was issued when the error occurred and a code specific to the
type or error.
Internal fault codes are stored. When the command that failed is listed as 31
(0x1F), the error condition is an internal error with the TX312. The datalogger
receives the error code as a hex value and converts to decimal. Decimal values
are placed in input locations.
The error codes are very important information if the DCP experiences trouble
during operation. Generally a GPS time synchronize fault should not cause
concern, but a GPS fault may cause a scheduled transmission to be missed.
The data will be sent on the next transmission if the instruction appends data to
the self-timed buffer.
The internal TX312 errors provide critical information for diagnostics. Error
codes are return in hex format when using SatCommand software. Error codes
are returned in decimal format when using the datalogger.
Error code 16 (0x10), message abort due to PLL, is a hardware failure of the
phase locked loop circuit. Repeated PLL failures can not be rectified in the
field.
Error code 17 (0x11), message abort due to GPS, indicates the transmitter
aborted a transmission because the required GPS information was not available
at transmit time. Usually the transmitter will transmit on the next transmit
time. Check GPS antenna placement and GPS antenna type. See Section 6.3
for more information regarding the GPS antenna.
20
TX312 Transmitter
Error code 18 (0x12), message abort due to power supply, indicates the
transmitter power supply did not provide enough voltage. Check system
battery. If the system battery is low, the RF power supply will not be able to
operate properly. The loaded battery voltage must not drop below 10.8 volts.
Error code 19 (0x13), Software error, indicates the transmitter was not able to
run its internal software.
Error code 20 (0x14) is the Failsafe error. The failsafe is an internal hardware
circuit that will shut down the TX312 if it transmits too frequently or for too
long. The failsafe error code is not logged until the transmitter tries to transmit
after the failsafe has been tripped. The transmitter only trips the failsafe when
a serious hardware failure has occurred. Failsafe limits are different for
different baud rates. At 1200 baud, transmission cannot exceed 105 seconds or
repeat more often than every 30 seconds. At 100 baud, transmission cannot
exceed 270 seconds or repeat more often than 60 seconds. At 300 baud, same
transmission on time as 100 baud, but cannot repeat more often then every 30
seconds. The Failsafe can be reset by pressing and holding the reset switch for
10 seconds.
Error code 21 (0x15) indicates the transmitter missed a GPS fix, but does not
guarantee a missed a transmission. See Section 6.3 for GPS antenna
information.
Error code 22 (0x16) indicates a Standing Wave Ratio (SWR) Fault. The
SWR fault can be triggered by several different conditions. High reflected
power will trigger the SWR fault. Reflected power is caused by poor
transmission antenna and/or antenna cable condition or wrong type of antenna
or antenna cable. See Section 6 for transmission antenna information. Ice
buildup on an antenna can change the antenna properties, which can cause
excessive reflected power. Corrosion in connectors, water in antenna cables,
metal in close proximity to the antenna, and a damaged antenna can also cause
excessive reflected power.
The SWR fault can also be triggered by a low battery. If the transmitter cannot
generate enough transmission power, the SWR fault will trip. Always check
the system battery if there has been an SWR fault. This condition is indicated
by low reflected power.
To determine if the reflected power is too high or low, read the last message
status information. When the reflected power number is divided by the
forward power number, the result should be 0.5, with limits of 0.4 to 0.6. See
Section 5.1.2.3 for details on the Last Message Status command.
5.1.3 GoesGPS
Example:
Public GPSdata(6), GPStime(7)
GoesGPS(GPSdata(), GPStime())
The instruction GoesGPS() returns two arrays of information. The first array
is six elements long. The second array is seven elements long. The first array
21
TX312 Transmitter
includes the result code (see Table 5.1-6), time in seconds since January 1,
2000, Latitude in fractional degrees with 100 nanodegree resolution, Longitude
in fractional degrees with 100 nanodegree resolution, Elevation as a signed 32-
bit number in centimeters, and Magnetic Variation in fractional degrees with a
one millidegree resolution.
The second array, which must be dimensioned to seven, holds year, month,
day, hour (GMT), minute, seconds, microseconds. The second array can be
used to set the datalogger’s clock. See the ClockSet() instruction in the
CRBasic help for details.
5.1.4 GoesSetup
In GoesSetup(), All parameters can be variables of type Long except for the
Timed Interval, Timed Offset and Random interval which are all of type
String.
The GoesSetup() and GoesData() only return error messages at compile time.
Using GoesSetup, the datalogger can configure the transmitter under program
control. Because the parameters in the GoesSetup instruction can be variables,
error checking is done at run time, not compile time. Using GoesSetup(), the
custom display menu options and the datalogger keypad/display, programs can
be written that allow TX312 configuration via simple menus on the
keypad/display. See CRBasic help and Display Menu for details. GoesSetup
can also be used with constant values allowing fixed goes configuration
parameters to be stored in the datalogger, and executed when needed.
After GoesSetup executes, several TX312 settings are set to default values.
1) Messages are not centered in the transmission window.
2) Self-Timed message format is set to ASCII, which ONLY changes the flag
word. Pseudo binary formats will still work.
3) Random message format is set to ASCII, which ONLY changes the flag
word. Pseudo binary formats will still work.
4) Empty buffer message is turned off.
5) Randomizing percentage is set to 50%.
6) Data in the random buffer is repeated until cleared by the datalogger.
7) Random message counter is turned off.
Instruction details:
GoesSetup(Result Code, Platform ID, Window, Timed Channel, Time Baud,

Random Channel, Random Baud, Timed Interval, Timed Offset, Random
Interval)
22
TX312 Transmitter
5.1.4.1 Result Code

Result Code is used to indicate success or failure. Zero indicates Success.
Positive result codes indicate communication problems; negative result codes
indicate an illegal value in one of the parameters. See Table 5.1-6 for positive
result codes and Table 5.1-7 for negative result codes.
TABLE 5.1-6. Result Codes Indicating Communication Problems
0 Command executed successfully

2 Time out waiting for STX character after SDC addressing
3 Wrong character (not STX) received after SDC Addressing
4 Something other than ACK returned when select data buffer
command executed
5 Timed out waiting for an ACK when data buffer command was sent
6 CS I/O port not available, port busy
7 ACK not returned following data append or insert command
TABLE 5.1-7. GoesSetup and GoesData Runtime Result Codes
Code Error Condition

-11 Illegal Buffer Control
-12 Illegal Message Window
-13 Illegal Channel Number
-14 Illegal Baud Rate
-15 R count Error
-16 Illegal Data Format
-17 Illegal Data Format FP2_ASCII
-18 Self-Timed Interval Error
-19 Self-Timed Offset Error
-20 Random Interval Error
-21 Platform ID Error
5.1.4.2 Platform ID
Platform ID is an eight-character hexadecimal number assigned by NESDIS.
The Platform ID is always divisible by 2. Valid characters are 0-9 and A-F.
5.1.4.3 Window
Window is the message window length in seconds. Valid range is 5-120.
5.1.4.4 Timed Channel

Timed Channel is the assigned self-timed transmission channel. Valid range
for 300 bps is 0-266 and 0-133 for 1200 bps. Often1200 bps channels are
referred to using the 300 channel number scheme. Divide by 2 to get the real
1200 baud channel number.
5.1.4.5 Timed Baud Rate

Timed Baud rate is assigned and channel dependent. Valid options are 100,
300, and 1200.
23
TX312 Transmitter
5.1.4.6 Random Channel

Random channel is the assigned random channel number. See Timed Channel
description for valid entries.
5.1.4.7 Random Baud Rate

Random Baud rate is assigned and channel dependent. Valid options are 100,
300, and 1200.
5.1.4.8 Timed Interval

Timed Interval is assigned by NESDIS and is a string variable in the format of
“dd_hh_mm_ss”, where dd is days and usually 00, hh is hours and usually 01,
mm is minutes and usually 00, and ss is seconds and usually 00.
5.1.4.9 Timed Offset

Timed Offset is assigned by NESDIS and is a string variable in the format of
“hh_mm_ss”, where hh is hours and usually 00, mm is minutes, and ss is
seconds.
5.1.4.10 Random Offset

Random Offset is a string variable in the format of “hh_mm_ss” where hh and
ss are usually zero and mm is 30 or 45.
5.1.4.11 GOESSetup Example

Public setup_RC, setup
Sub Gsetup
GOESSetup (setup_RC,&H12345677,10,195,300,0,100,"0_01_00_0" ,"0_16_20" ,"1_0_0" )
If setup_RC = 0 Then setup = false
EndSub
BeginProg
setup = true
Scan (10,Sec,0,0)
If setup Then Call Gsetup
NextScan
EndProg
5.2 Edlog Programming

This section only applies to the CR10(X), CR23X, and CR510 dataloggers.
The datalogger is used to measure and record data values. The TX312 is used
to transmit data over a GOES satellite to a ground receiving station. Program
instruction 126 is used to send data from the datalogger to the TX312 satellite
transmitter. The TX312 has two data buffers. The data buffers will hold data
until it is time to transmit the data. Data in the self-timed buffer is erased after
transmission. Data in the random buffer will be erased after the preset number
24
TX312 Transmitter
of repetitions has been met. When properly configured, the TX312 will ensure
the data is transmitted on the correct channel, at the correct baud rate and at the
correct time without overrunning the transmit window.
The datalogger will interface with the TX312 under program control. Two
program instructions are used, P126 and P127. P126 is used to send data to a
buffer. New data is either added to existing data (append) or overwrites
existing data. In overwrite mode, all data in the buffer is erased before new
data is written. P127 is used to retrieve information from the TX312.
Information regarding GPS time, latitude and longitude can be retrieved and
stored in the datalogger. Information regarding the status and past errors can
also be retrieved.
Data that is sent to the self-timed buffer 60 seconds or more before transmit
time will be transmitted on the next scheduled transmission; otherwise, the data
will be scheduled for a later transmission.
5.2.1 Deciding How Much Data will be Transmitted and When

The amount of data that can be transmitted depends on several factors: the
transmit window length, the transmit baud rate, and the data format. The
transmit window limits the time available for data to be sent. The baud rate
determines how fast data is sent. The data format determines how many bytes
are required per data point.
The maximum number of data points that can be sent is estimated with this
formula:
b(a-2)/8c = total number of data points per transmission
Where:
a = window length in seconds

b = baud rate or bits/second; i.e., 100, 300, or 1200
c = bytes per data point
Binary data uses 3 bytes per data point.
ASCII data uses 7 bytes per data point.
The Sat Commander Software includes a Command to read the Max Timed
Message Length, which will use the TX312 to calculate the maximum number
of bytes to be sent, not the maximum number of data points. To use the
software to calculate the maximum number of data points that can be sent, first
setup the transmitter, then use the max timed message length command. Take
the result and divide by 3 if the data format is pseudo binary or divide by 7 if
using an ASCII format.
5.2.2 Deciding What Data Format to Use

The choice of data format effects two areas. First, the data format effects how
much data can be sent in a single transmission. Binary data formats require 3
bytes per data point. ASCII data formats require 7 bytes per data point.
Second, binary data must be decoded after transmission, ASCII does not. The
25
TX312 Transmitter
datalogger formats the data before the data is sent to the TX312. The data
format is chosen with the P126 program instruction.
5.2.3 Managing Data, Writing More Data than Will Be Transmitted

The datalogger has two data storage areas: Final Storage area 1 (FS1) and
Final Storage area 2 (FS2). When data is written to final storage, data is
written to the active final storage area. The active final storage area defaults to
FS1 when the datalogger starts the program table. Program instruction 80
(P80) is used to set the active final storage area. When P126 executes, all new
data in the active final storage area is sent to the transmitter. New data is all
data that has been written to the active final storage area since P126 last
executed.
Two separate data files can be maintained by managing which final storage
area is active when data is written. The amount of data copied to the
transmitter and the order of data copied to the transmitter can be controlled by
utilizing both final storage areas. If using FS2, datalogger memory must be
allocated to FS2. Final storage area 2 memory can be allocated using Edlog or
the keypad.
5.2.4 Sending Data to the Transmitter (P126)

Edlog instruction 126 is used to transfer data to the TX312.
1: Data Transfer to TX312 (P126)

1: 0000 Buffer Control
2: 0000 Data Format
3: 0000 Result Code Loc [ ______ ]
Parameter1: Buffer Control

0 Append to Self-Timed Buffer
1 Overwrite Self-Timed Buffer
2 Append to Random Buffer
3 Overwrite Random Buffer
9 Clear Random Buffer
Parameter 2: Data Format

0 CSI Floating Point Binary
1 Floating Point ASCII
2 Binary Integer, 18 Bit
3 RAWS 7, Fire Weather
4 Fixed Decimal, ASCII, xxx.x
5 Fixed Decimal, ASCII, xx.xx
6 Fixed Decimal, ASCII, x.xxx
7 Fixed Decimal, ASCII, xxx
8 Fixed Decimal, ASCII, xxxxx
Parameter 3: Input Location for Result Code
1 Input Loc [ ________ ]
26
TX312 Transmitter
5.2.4.1 Buffer Control

The first parameter of Edlog instruction 126 (P126) is called buffer control.
Buffer control has two purposes: 1) to determine which buffer data is written
to, and 2) if the buffer is erased before data is written. The TX312 has two
independent buffers, one for self-timed transmissions and one for random
transmissions. The self-timed buffer is treated differently than the random
buffer. After a self-timed transmission, the data is erased from the self-timed
buffer. After a random transmission, the data in the random buffer is
scheduled to be transmitted again. Random transmissions are repeated at
random intervals until P126 is used to “Clear Random Buffer” or the maximum
number of random transmissions have been met. The maximum number of
random transmissions can be set in SatCommander, default is off.
5.2.4.2 Data Format

The second parameter of P126 is used to format the data. The data is
formatted as P126 copies data from the datalogger to the transmitter.
CSI floating point binary data requires 3 bytes per data point. Data must be
low resolution. Sign and decimal location are maintained. This is an efficient
data format.
Floating point ASCII requires 7 bytes per data point. Data must be low
resolution. Sign and decimal location are maintained. Data does not need to
be converted after transmission. Data points are separated by a comma. This
is not an efficient data format, but it is convenient.
Binary, 18 bit, integer data format requires 3 bytes per data point. All data
stored in the datalogger must be in high resolution. All information right of
the decimal place is truncated. Data is transmitted as a signed, two’s
compliment, 18-bit integer. Precision can be maintained by pre and post
processing. This is an efficient data format that requires conversion and post
processing. See Appendix F for details.
RAWS 7 and fixed decimal ASCII are used to format data in a specific way.
See Appendix D for details.
5.2.4.3 P126 Result Codes

The third parameter of P126 requires an input location. In the input location,
the result of the P126 execution is stored as a result code. The result code can
be used to determine if P126 executed successfully. Under most conditions, if
P126 was not successful, a second execution of P126 will work.
To better understand the result codes, it is necessary to understand the

sequence of communication with the transmitter. Here are the steps:
1) The Datalogger CS I/O port is checked to see if the serial port is available.
If not, return code 6.
2) The transmitter is addressed and should return the STX character within
200 msec. If there is no response from the transmitter, result code 2 is
returned. If something other than the STX character is received, result
code is 3.
27
TX312 Transmitter
3) The command to select a data buffer is sent (random or self-timed). The

transmitter should respond with the ACK (06) character. If something
besides the ACK is received, result code is 4. If nothing is received within
500 msec, result code is 5.
4) If the first three steps are successful, the datalogger sends the command to
append or overwrite the data buffer, followed by the data. If the
transmitter does not respond with the ACK character within 500 msec
after the data has been transferred, the result code is 7. Result code 7
indicates the data was not received by the transmitter. The datalogger
cannot resend the data.
P126 result codes are the same as the positive result codes for our CRBasic
instructions and are shown in Table 5.1-6.
The result codes can be used to increase the success rate of data transmissions.
When the result code is 0, all went well. When the result code is 2-6, P126 did
not execute properly, but can still send the data. A result code of 7 indicates
P126 did not execute properly and the data probably cannot be sent again.
5.2.5 Read Status and Diagnostic Information from the TX312

Edlog instruction 127 (P127) is used to read status and diagnostic information
from the TX312.
1: TX312 Status (P127)

1: 0000 Status Command
2: 0000 Result Code Loc [ _____ ]
Parameter 1: Status Command

0 Read Time, Uses four Input Locations
1 Read Status, Uses 13 Input Locations
2 Read Last Message Status, Uses 14 Input Locations
3 Transmit Random Message, must be followed by command 6. One
Input Location
4 Read Error Register, Uses Ten Input Locations
5 Reset Error Register, One Input Location
6 Return transmitter to online mode, used after command 3, One Input
Location
Edlog instruction 127 (P127) has four basic functions:
1) Datalogger will retrieve information from the TX312 transmitter.
2) Datalogger will initiate a test transmission on a random channel.
3) Datalogger will reset the error register of the TX312.
4) Return TX312 to on-line mode following a forced random transmission.
Parameter 1 allows you to determine what command will be issued to the

TX312.
28
TX312 Transmitter
Parameter 2 is the starting input location for the string of information the
TX312 will return.
Each P127 command returns a string of information. Each command requires

a different number of input locations. The first piece of information returned is
always the result code of the command. Table 5.2-1 lists the result codes and
explains them.
TABLE 5.2-1. P127 Result Codes
0 Execution successful
1 Checksum error in response
2 Time out waiting for STX character after addressing
3 Something besides STX received after addressing
4 Received a NAK
5 Timed out while waiting for an ACK
6 CS I/O not available
7 Transmit random message failure, could be no data in random buffer
9 Invalid command code
5.2.5.1 P127, Command 0: Read Time

Retrieve the GPS time from the HDR GOES transmitter. The time is
Greenwich Mean Time (GMT). A time of 153 hours, 153 minutes, 153
seconds indicates GPS time is not available.
TABLE 5.2-2. P127 Command 0: Read Time
In Loc Contents
2 Hours (GMT)
3 Minutes
4 Seconds
5.2.5.2 P127, Command 1: Read Status

Read Status Command provides information specific to the next scheduled or
random transmission, including the amount of data in the buffers and power
supply voltage.
29
TX312 Transmitter
TABLE 5.2-3. P127 Command 1: Read Status
In Loc Contents
2 Bytes of data in self-timed buffer
3 Time until next self-timed transmission: Days
4 Time until next self-timed transmission: Hours
5 Time until next self-timed transmission: Minutes
6 Time until next self-timed transmission: Seconds
7 Bytes of data in random buffer
8 Time until next random transmission interval start: Hours
9 Time until next random transmission interval start: Minutes
10 Time until next random transmission interval: Seconds
11 Failsafe, 1 indicates transmitter disabled due to failsafe.
12 Loaded power supply voltage, 1 amp load. (tenths of volts)
13 Average GPS acquisition time (tens of seconds)
5.2.5.3 P127, Command 2: Read Last Message Status

Returns information specific to the last message transmitted plus the GPS
derived Latitude and Longitude.
TABLE 5.2-4. P127 Command 2: Read Last Message Status
In Loc Contents
2 Message type: Self-timed or Random
3 Size of message in bytes
4 Forward power in tenths of watts
5 Reflected power in tenths of watts
6 Power supply voltage under full load, in tenths of volts
7 GPS acquisition time in tens of seconds
8 Oscillator drift (signed, hundreds of Hz)
9 Latitude degrees
10 Latitude minutes
11 Latitude seconds
12 Longitude degrees
13 Longitude minutes
14 Longitude seconds.
5.2.5.4 P127, Command 3: Transmit Random Message

Overwrite random buffer with 1 2 3 4 (ASCII)
During GPS acquisition the LED lights green.
During transmission the LED lights red.
30
TX312 Transmitter
TABLE 5.2-5. P127 Command 3: Initiate Random Transmission
In Loc Contents
1 Result Code
Random message channel and repeat interval must be enabled in the TX312
configuration. If random messages have not been enabled, command 3 will
fail. If the GPS acquisition fails, the random transmission will fail. Command
3 will pull the TX312 off line. After the random transmission attempt, the
TX312 must be put back on line with command 6. When command 6 is used,
all data in the TX312 is erased. Random transmission may require up to five
minutes (GPS timeout) for setup and transmission. If command 6 is executed
before transmission, random transmission will be canceled.
During GPS acquisition, the LED will light solid green. During transmission,
the LED will light solid red. Command 3 will return 1 value, the command
result code. Zero indicates a successful execution of command 3, but does not
indicate the random transmission has happened or was successful.
5.2.5.5 P127, Command 4: Read TX312 Error Registers

Read error registers of TX312. Requires 10 input locations.
TABLE 5.2-6. P127 Command 4: Read TX312 Error Registers
In Loc Contents
1 Result Code
2 Number of Errors
4 Error Code
6 Error Code
8 Error Code
10 Error Code
31
TX312 Transmitter
TABLE 5.2-7. Error Codes
Error Codes:
Hex Decimal
0x00 00 No error
0x01 01 Illegal command
0x02 02 Command rejected
0x03 03 Illegal checksum or too much data
0x04 04 Time out or too little data
0x05 05 Illegal parameter
0x06 06 Transmit buffer overflow
0x10 16 Message abort due to PLL
0x11 17 Message abort due to GPS
0x12 18 Message abort due to power supply – internal 16 volt – RF
0x13 19 Software fault
0x14 20 Failsafe fault
0x15 21 GPS time sync fault
0x16 22 SWR fault – transmission antenna connection
0x19 25 Internal RF power supply failure
See Section 5.1.2.4 for more information.
5.2.5.6 P127, Command 5: Clear TX312 Error Registers

Clear error registers of TX312. Requires one input location.
TABLE 5.2-8. P127 Command 5: Clear Error Registers
In Loc Contents
1 Result Code
Result code of 0 indicates success. Command 5 is used to erase all errors from
the error registers of the TX312.
5.2.5.7 P127, Command 6: Return TX312 to on-line mode.

Command 6 is used to return the TX312 to online mode. Typically used after
a forced random transmission. The TX312 has an off-line time-out of one
hour.
TABLE 5.2-9. P127 Command 6: Force On-line Mode
In Loc Contents
1 Result code
Result code of 0 indicates success.
5.2.6 Edlog Programming Examples

Edlog instruction 126 is used to copy data from the datalogger final storage
area to the TX312 data buffer.
32
TX312 Transmitter
Edlog program example 1 writes data to final storage once an hour and
transfers data to the TX312 once every 4 hours.
; Edlog Program Example 1
; Set output flag high hourly
1: If time is (P92)
1: 0 Minutes (Seconds --) into a
2: 60 Interval (same units as above)
3: 10 Set Output Flag High (Flag 0)
; Write a time stamp to final storage
2: Real Time (P77)

1: 1221 Year,Day,Hour/Minute,Seconds (midnight = 2400)
; Write 41 input locations to final storage
3: Sample (P70)
1: 41 Reps
2: 1 Loc [ Status_RC ]
; Check if top of 4 hour interval, if true execute P126
4: If time is (P92)
3: 30 Then Do
; Transfer data to TX312
5: Data Transfer to HDR GOES (P126)

1: 0 Self-Timed/Append
2: 0 Binary Format
3: 41 Result Code Loc [ P126_RC ]
6: End (P95)
Edlog program example 2 writes data to final storage once an hour and
transfers data to the TX312 once every 4 hours. Example 2 also shows how to
use the result codes to ensure P126 executes successfully.
; Edlog Program Example 2
; Set output flag high hourly
1: If time is (P92)
33
TX312 Transmitter
; Write a time stamp to final storage
2: Real Time (P77)

1: 1221 Year,Day,Hour/Minute,Seconds (midnight = 2400)
; Write 41 input locations to final storage
3: Sample (P70)
1: 41 Reps
2: 1 Loc [ Status_RC ]
; Check if top of 4 hour interval, if true execute P126
4: If time is (P92)
3: 30 Then Do
; Transfer data to TX312

2: 0 Binary Format
6: End (P95)
; Check result code for P126, if between 1 and 6 P126 will be executed again.
7: If (X<=>F) (P89)
1: 41 X Loc [ P126_RC ]
2: 3 >=
3: 1 F
4: 30 Then Do
8: If (X<=>F) (P89)
1: 41 X Loc [ P126_RC ]
2: 4 <
3: 7 F
4: 30 Then Do
; Increment counter to count number of time P126 has been tried again
9: Z=Z+1 (P32)
1: 42 Z Loc [ Counter ]
; Try P126 again

2: 0 Binary Format
34
TX312 Transmitter
; Check number of times P126 has been executed unsuccessfully

; If P126 failed more than 3 times, give up and reset counter
11: If (X<=>F) (P89)

1: 42 X Loc [ Counter ]
2: 3 >=
3: 4 F
4: 30 Then Do
; Reset counter
12: Z=F (P30)

1: 0.0 F
2: 00 Exponent of 10
3: 42 Z Loc [ Counter ]
; Set P126 result code to zero, this will stop P126 from
; executing until the 4 hour transmit time comes around again.
13: Z=F (P30)

1: 0.0 F
3: 41 Z Loc [ P126_RC ]
14: End (P95)
15: End (P95)
16: End (P95)
6. Field Installation
6.1 Field Site Requirements
The TX312 has two siting requirements for proper operation. The GPS
antenna must have a clear view of most of the sky. The transmission antenna
must have a clear view of the spacecraft. Other requirements are not specific
to the TX312, but are mentioned here anyway. The TX312 must be mounted
in an enclosure that will protect it from the environment, including
condensation. Most GOES systems are powered by a battery that is charged
by a solar panel. The solar panel must have a clear view of the southern sky.
Pay special attention to winter sun angles.
6.2 Transmission Antenna

The TX312 transmission antenna is a right-hand circular polarized Yagi with
11 dBic gain. The antenna is directional and should be aimed at the spacecraft.
Both elevation and azimuth are unique to the location on the planet, and must
be set. A poorly aimed antenna will cause a drop in signal strength or possibly
prevent successful transmission.
The accuracy of the antenna aiming is not critical, but should be reasonably
good. As a guide, if the antenna is aimed 25 degrees off the spacecraft, the
35
TX312 Transmitter
received power will be half of a properly aimed antenna. Beyond 25 degrees,

the received power drops off very quickly.
6.3 GPS Antenna

6.3.1 How the GPS Signal is Acquired and Used
The GPS receiver will acquire a complete GPS fix at power up and once a day.
The TX312 transmitter will continue to operate normally for 28 days without a
GPS fix.
The GPS signal is used for two functions. The obvious use is to keep track of
time. The GPS receiver requires 3 satellites to acquire the time. For best
accuracy, four satellites are required. The second use of the GPS signal is to
correct the oscillator frequency. The GPS receiver will output a very accurate
1-second pulse. The 1-second pulse is used to correct oscillator drift caused by
changes in temperature and crystal aging.
The GPS is required for proper operation. After the transmitter is reset, or first
powered up, it can’t schedule a transmission until a GPS fix has been
established or the internal clock has been manually set. After the first fix, the
TX312 will acquire a GPS fix once a day. Each time the GPS system acquires
a fix, the entire GPS almanac is downloaded, which requires about 15 minutes.
6.3.2 GPS Antenna Location

The ideal location for the GPS antenna is above everything, with the shortest
cable possible. The GPS antenna will not receive the GPS signal through a
steel roof or steel walls. Concrete will probably act like steel. Heavy foliage,
snow, and ice will attenuate the GPS signal. The more of the sky the antenna
has a clear unobstructed view of, the better the GPS performance. Better GPS
performance will show up as less or no missed transmissions. Poor GPS
antenna placement will increase the number of missed transmissions, or
possibly stop all transmission
36
Appendix A. Information on Eligibility
and Getting Onto the GOES System
A.1 Eligibility
U.S. federal, state, or local government agencies, or users sponsored by one of
those agencies, may use GOES. Potential GOES users must receive formal
permission from NESDIS.
A.2 Acquiring Permission

1. The user contacts NESDIS at the following address and submits a formal
request to transmit data via GOES. Non-U.S. or private users must also
submit a written statement indicating that their sponsor requires all or part
of the transmitted data. NESDIS will fax or mail the user a question form
to complete and submit for approval.
DCS Coordinator
Federal Office Building 4
Suitland, MD
(301) 457-5681
http://dcs.noaa.gov/contact.htm
2. Following approval, NESDIS sends a Memorandum of Agreement

(MOA). The MOA must be signed and returned to NESDIS.
3. After the MOA is approved, NESDIS will issue a channel assignment and
an ID address code.
4. NESDIS MUST BE contacted to coordinate a “start-up” date.
See http://noaasis.noaa.gov/DCS/ for more information.
A-1
This is a blank page.
Appendix B. Data Conversion
Computer Program (written in BASIC)
1 REM THIS PROGRAM CONVERTS 3-BYTE ASCII DATA INTO
DECIMAL
5 INPUT "RECEIVE FILE?", RF$
6 OPEN RF$ FOR OUTPUT AS #2
10 INPUT "NAME OF FILE CONTAINING GOES DATA"; NFL$
20 DIM DV$(200)
25 WIDTH "LPT1:", 120
30 OPEN NFL$ FOR INPUT AS #1
40 WHILE NOT EOF(1)
50 LINE INPUT #1, A$
55 A$ = MID$(A$, 38)
56 PRINT A$
100 J = INT(LEN(A$) / 3)
105 PRINT J
110 FOR I = 1 TO J
120 DV$(I) = MID$(A$, 3 * I - 2, 3)
130 NEXT I
140 B$ = RIGHT$(A$, LEN(A$) - 3 * J)
160 A$ = B$ + A$
170 K = INT(LEN(A$) / 3)
180 L=J
190 FOR I = J + 1 TO L
200 DV$(I) = MID$(A$, 3 * (I - J) - 2, 3)
210 NEXT I
270 FOR I = 1 TO L
280 A = ASC(LEFT$(DV$(I), 1)) AND 15
290 B = ASC(MID$(DV$(I), 2, 1)) AND 63
300 C = ASC(RIGHT$(DV$(I), 1)) AND 63
310 IF (A * 64) + B >= 1008 THEN DV = (B - 48) * 64 + C + 9000:
GOTO 400
320 IF A AND 8 THEN SF = -1 ELSE SF = 1
330 IF A AND 4 THEN SF = SF * .01
340 IF A AND 2 THEN SF = SF * .1
350 IF A AND 1 THEN DV = 4096
360 DV = (DV + ((B AND 63) * 64) + (C AND 63)) * SF
400 PRINT #2, USING "####.### "; DV;
405 IF I MOD 17 = 0 THEN PRINT #2, CHR$(13)
406 DV = 0
410 NEXT I
1000 WEND
B-1
Appendix C. Antenna Orientation
Computer Program (written in BASIC)
5 REM THIS PROGRAM CALCULATES THE AZIMUTH AND
ELEVATION FOR AN
6 REM ANTENNA USED WITH A DCP FOR GOES SATELLITE
COMMUNICATIONS
10 CLS : CLEAR 1000
20 INPUT "SATELLITE LONGITUDE (DDD.DD)"; SO
30 INPUT "ANTENNA LONGITUDE (DDD.DD)"; SA
40 PRINT "ANTENNA LATITUDE (DDD.DD)--(SOUTH LATITUDE
ENTERED"
45 INPUT "AS NEGATIVE NUMBER)"; AA: A = 90 - AA
50 INPUT "ANTENNA HEIGHT ABOVE SEA LEVEL IN FEET"; AH
60 T = SO - SA: TR = T * .01745329#: BR = 90 * .01745329#: AR = A *
.01745329#
70 X = COS(AR) * COS(BR) + SIN(AR) * SIN(BR) * COS(TR)
80 CR = -ATN(X / SQR(-X * X + 1)) + 1.5708
90 C = CR * (1 / .01745329#)
100 X1 = (SIN(BR) * SIN(TR)) / SIN(CR)
110 BR = ATN(X1 /SQR(-X1 * X1 + 1)): B = BR * (1 / .01745329#)
115 GOSUB 300
120 A1 = 90 - C: R1 = A1 * .01745329#
130 S1 = (6378 + (AH * .0003048)) / SIN(R1)
140 S2 = 35785! + 6378 - S1
150 A2 = 180 - A1: R2 = A2 * .01745329#
155 S4 = SQR(S1 ^ 2 - (6378 + AH * .0003048) ^ 2)
160 S3 = SQR(S4 ^ 2 + S2 ^ 2 - 2 * S4 * S2 * COS(R2))
170 X2 = (SIN(R2) / S3) * S2
180 ER = ATN(X2 / SQR(-X2 * X2 + 1)): E = ER * (1 / .01745329#)
190 PRINT "ANTENNA ELEVATION ANGLE="; E; " DEGREES"
200 PRINT "ANTENNA AZIMUTH ANGLE="; B; " DEGREES"
210 PRINT : PRINT : PRINT "HIT ANY KEY TO CONTINUE"
220 I$ = INKEY$: IF I$ = "" THEN 220 ELSE CLS : GOTO 20
300 IF T < 0 AND AA > 0 THEN B = B + 180: GOTO 380
310 IF T < 0 AND AA < 0 THEN B = B * -1: GOTO 380
320 IF T > 0 AND AA < 0 THEN B = 360 - B: GOTO 380
330 IF T > 0 AND AA > 0 THEN B = B + 180: GOTO 380
340 IF T = 0 AND AA > 0 THEN B = 180: GOTO 380
350 IF T = 0 AND AA < 0 THEN B = 360: GOTO 380
360 IF AA = 0 AND T > 0 THEN B = 270: GOTO 380
370 IF AA = 0 AND T < 0 THEN B = 90
380 RETURN
400 RETURN
460 RETURN
C-1
Appendix D. RAWS-7 Data Format
D.1 Introduction
RAWS-7 data format is used to transmit weather data in an ASCII based table
format. Upon reception, data does not need to be decoded. Software such as
WeatherPro can be used to archive and view the data. RAWS-7 data format is
compatible with NIFC.
D.2 Format
RAWS-7 format writes data in columnar format. The first 7 data points are
written to column 1, the next 7 data points are written to column 2 and the next
7 data points are written to column 3. Each data point is configured with a
fixed decimal place and a fixed number of characters. The RAWS-7 data block
is preceded by a carriage return and line feed character.
D.3 Programming the Datalogger for RAWS-7 Format

When using the RAWS-7 format, special care should be taken to ensure the
correct data will be written to final storage of the datalogger and thus
transferred to the SAT HDR GOES transmitter. Data is written in groups of 7.
One group of 7 represents 7 data points, usually for 1 hour of data. All data for
the RAWS-7 group must be transferred from the datalogger to the transmitter
at the same time. If writing hourly data, but transmitting on a 3-hour interval,
write all three hours of RAWS-7 data before P126 is executed. Write
additional data beyond the RAWS-7 data after the RAWS-7 data has been sent
to the transmitter.
The RAWS-7 format has some special functions built in. The RAWS-7 format
will behave differently depending on the amount of data in the active final
storage area of the datalogger. If there are 7 data points in the active final
storage area that have not been sent to the transmitter, the datalogger will
format 1 column of data. More than 7 and less than 14 data points are not sent
to the transmitter. If there are 14 data points, the RAWS-7 format will create a
table with 2 columns of 7 rows. If 21 data points are available, 3 columns of 7
rows each are created. If the number of data points is more than 14 but less
than 21, the first 14 data points are used while the extra are discarded. If there
are more that 21 data points, 3 columns of 7 rows are created. Data points in
excess of 21 are not sent to the transmitter, and can not be sent later.
The RAWS-7 data formats include fixed decimal place and fixed number of
characters. If the data value exceeds the range of the data format, all numbers
will default to 9. When the data value is negative, the minus sign is counted as
one character. As an example, if using data format 6, x.xxx, the minus sign fills
the only character location left of the decimal. All numbers less than -.999 will
print as -.999. All numbers greater than 9.9 will print as 9.999. P126, second
parameter, codes 3 through 8 are considered RAWS data formats
D-1
D.4 RAWS-7 Sample Data

00.12 00.05 01.09 Rain fall: Hundredths of and inch
109 022 002 Wind Speed: Avg of last 10 minutes
234 123 087 Wind Direction: Avg of last 10 minutes
115 069 -23 Air Temperature: Sample
100 056 012 Relative Humidity: Avg of Last 10 minutes
056 098 012 Fuel Temperature: Sample
10.5 11.9 13.6 Battery Voltage: Sample
Oldest data in left column
Table D-1. RAWS-7 Output
Row
Number Measurement Format
1 Total Rain (hr) xx.xx
2 Wind Speed (10 min avg.) xxx
3 Wing Direction (10 min avg.) xxx
4 Air Temp (Sample) xxx
5 RH (10 min avg.) xxx
6 Fuel Temp (Sample) xxx
7 Battery Voltage (Sample) xx.x
Using P126 for RAWS-7 data format
P126 has three parameters. Parameter 2 “Data Format” is used to select the
desired data format.

1: 0000 Buffer Control
2: 0000 Data Format
3: 0000 Result Code Loc [ ______ ]
Parameter 2: Data Format

0 CSI Floating Point Binary
1 Floating Point ASCII
2 Binary Integer, 18 Bit
3 RAWS 7, Fire Weather
4 Fixed Decimal, ASCII, xxx.x
5 Fixed Decimal, ASCII, xx.xx
6 Fixed Decimal, ASCII, x.xxx
7 Fixed Decimal, ASCII, xxx
8 Fixed Decimal, ASCII, xxxxx
D-2
P126 format code 3

ASCII RAWS-7 format, 1, 2 or 3 columns
1 Total Rain xx.xx

2 Avg Wind Speed xxx
3 Avg Wing Direction xxx
4 Sample Air Temp xxx
5 Avg Relative Humidity xxx
6 Sample Fuel Temp xxx
7 Battery Voltage xx.x
P126 format code 4

ASCII fixed decimal xxx.x
P126 format code 5

ASCII fixed decimal xx.xx
P126 format code 6

ASCII fixed decimal x.xxx
P126 format code 7

ASCII fixed decimal xxx
P126 format code 8

ASCII fixed decimal xxxxx
D.5 Writing Additional Data Values Beyond the

RAWS-7
If additional data points beyond the RAWS-7 need to be transmitted, each row
of data is stored in input locations until the data set is complete. Then the data
is copied to the transmitter.
When P126 is executed with a data format code of 4 through 8, the line of data
is preceded by a carriage return and line feed. Each data point is separated by a
space. Format code 8 can be used with high or low resolution data. Three steps
are required to write a row of data: Set the output flag, write data to final
storage, copy data to transmitter by executing P126.
Program example
CR10X program example to send fire weather data. If using the example
program, using the input location editor to name all the input locations can be
helpful. In Edlog.exe, start a new program then press F5 to bring up the input
location editor. Type in the names for all the input locations. The input location
names are listed at the end of the program example. F6 will bring up a pick list
of all the input locations. Using the pick list helps to avoid mistakes when
selecting input locations.
D-3
;{CR10X}
;
; RAWS-7 Data format example program
;
;Description:
; Measurements:
; Battery voltage (BattVolt) - volts
; Air temperature (AirTemp) - Degrees F
; Relative humidity (RH) - Percent
; Wind speed (Wspd) - MPH
; Wind direction (Wdir) - Degrees 0 to 355
; Fuel temperature (FuelT) - Degrees F
; Fuel Moisture (FuelM) - Percent
; Precipitation (Prcip) - Hundredth of inch
; Solar radiation (Srad) - Watts per meter squared W/m^2
;
; Calculations:
; 10 minute averages for wind speed and direction.
; Hourly maximum wind speed with corresponding wind direction.
; Program Signature (Prog_Sig)
; RAWS-7 data format and transmission:

;
; Program based on a 3 hour window. Hourly data transmitted. The hourly
; RAWS-7 values are written to final storage at the top of the hour.
; At the top of the 3 hour interval, the RAWS-7 values are copied
; to the SAT HDR GOES transmitter. (P126, Self-timed/insert, format code 3).
; Four additional values are written to final storage and copied to

; the SAT HDR GOES:
; Hourly maximum wind speed and direction of max wind speed.
; Hourly average solar radiation.
; Hourly Fuel moisture
;
*Table 1 Program
01: 10 Execution Interval (seconds)
1: Batt Voltage (P10)

1: 1 Loc [ BattVolt ]
; Power up air temp and RH sensor (HMP45C-L)

2: Do (P86)
1: 41 Set Port 1 High
; Power up fuel moisture sensor

3: Do (P86)
1: 48 Set Port 8 High
D-4
; Measure Fuel Moisture

; Wiring:
; Power enable: C8
; Signal: SE 12
4: Period Average (SE) (P27)
1: 1 Reps
2: 4 200 kHz Max Freq @ 2 V Peak to Peak, Period Output
3: 12 SE Channel
4: 10 No. of Cycles
5: 5 Timeout (units = 0.01 seconds)
6: 28 Loc [ FuelM ]
7: .001 Mult
8: 0 Offset
5: Do (P86)
1: 58 Set Port 8 Low
; Measure temperature and RH (HMP45C-L)

6: Excitation with Delay (P22)
1: 1 Ex Channel
2: 0 Delay W/Ex (units = 0.01 sec)
3: 15 Delay After Ex (units = 0.01 sec)
4: 0 mV Excitation
7: Volt (SE) (P1)

1: 1 Reps
2: 25 2500 mV 60 Hz Rejection Range
3: 2 SE Channel
4: 3 Loc [ AirTemp ]
5: .1 Mult
6: -40 Offset
8: Volt (SE) (P1)

1: 1 Reps
2: 25 2500 mV 60 Hz Rejection Range
3: 1 SE Channel
4: 4 Loc [ RH ]
5: .1 Mult
6: 0 Offset
; Measure wind speed (03001-L)

9: Pulse (P3)
1: 1 Reps
2: 1 Pulse Channel 1
3: 21 Low Level AC, Output Hz
4: 5 Loc [ Wspd ]
5: 1.677 Mult ; MPH
6: 0.4 Offset
D-5
; Wind Direction (03001-L)

10: Excite-Delay (SE) (P4)
1: 1 Reps
2: 5 2500 mV Slow Range
3: 3 SE Channel
4: 2 Excite all reps w/Exchan 2
5: 2 Delay (units 0.01 sec)
6: 2500 mV Excitation
7: 6 Loc [ Wdir ]
8: 0.142 Mult
9: 0 Offset
; Measure fuel temp

11: Temp (107) (P11)
1: 1 Reps
2: 9 SE Channel
3: 3 Excite all reps w/E3
4: 7 Loc [ FuelT ]
5: 1.8 Mult
6: 32 Offset
; Measure precip (TE525-L)

12: Pulse (P3)
1: 1 Reps
2: 2 Pulse Channel 2
3: 2 Switch Closure, All Counts
4: 8 Loc [ Prcip ]
5: 0.01 Mult
6: 0 Offset
; Measure solar radiation (LI200X-L)

13: Volt (Diff) (P2)
1: 1 Reps
2: 22 7.5 mV 60 Hz Rejection Range
3: 3 DIFF Channel
4: 9 Loc [ SRad ]
5: 200 Mult
6: 0 Offset
; **** Start of calculation section ****

; Set negative solar radiation values to zero
14: If (X<=>F) (P89)
1: 9 X Loc [ SRad ]
2: 4 <
3: 0 F
4: 30 Then Do
15: Z=F (P30)

1: 0 F
2: 0 Exponent of 10
3: 9 Z Loc [ SRad ]
D-6
16: End (P95)
; Correct Fuel Moisture

17: Polynomial (P55)
1: 1 Reps
2: 28 X Loc [ FuelM ]
3: 28 F(X) Loc [ FuelM ]
4: -220.14 C0
5: 365.89 C1
6: -114.96 C2
7: 0.0 C3
8: 0.0 C4
9: 0.0 C5
; Convert Air Temp to degrees F

18: Z=X*F (P37)
1: 3 X Loc [ AirTemp ]
2: 1.8 F
3: 3 Z Loc [ AirTemp ]
19: Z=X+F (P34)

1: 3 X Loc [ AirTemp ]
2: 32.0 F
3: 3 Z Loc [ AirTemp ]
; Eliminate RH values greater than 100

20: If (X<=>F) (P89)
1: 4 X Loc [ RH ]
2: 3 >=
3: 100 F
4: 30 Then Do
21: Z=F (P30)

1: 100 F
2: 0 Exponent of 10
3: 4 Z Loc [ RH ]
22: End (P95)
; correct zero wind speed offset.

23: If (X<=>F) (P89)
1: 5 X Loc [ Wspd ]
2: 4 <
3: 0.4001 F
4: 30 Then Do
24: Z=F (P30)

1: 0 F
2: 0 Exponent of 10
3: 5 Z Loc [ Wspd ]
25: End (P95)
D-7
; if no fuel temp sensor,

; load 999 for data value
26: If (X<=>F) (P89)
1: 7 X Loc [ FuelT ]
2: 4 <
3: -35 F
4: 30 Then Do
27: Z=F (P30)

1: 999 F
2: 0 Exponent of 10
3: 7 Z Loc [ FuelT ]
28: End (P95)
29: If (X<=>F) (P89)

1: 7 X Loc [ FuelT ]
2: 3 >=
3: 55 F
4: 30 Then Do
30: Z=F (P30)

1: 999 F
3: 7 Z Loc [ FuelT ]
31: End (P95)
; Calculate program signature once a day

32: If time is (P92)
3: 30 Then Do
33: Signature (P19)

1: 2 Loc [ Prog_Sig ]
34: End (P95)
; Calculate and hold 10 minute averages for Wspd and Wdir

; Values are written to input locations 10 and 11 (Avg10WS, Avg10WD)
; Direct output processing to input locations

36: Set Active Storage Area (P80)
1: 3 Input Storage Area
2: 10 Loc [ Avg10WS ]
D-8
; Calculate average wind speed and direction

37: Wind Vector (P69)
1: 1 Reps
2: 0 Samples per Sub-Interval
3: 1 S, é1 Polar
4: 5 Wind Speed/East Loc [ Wspd ]
5: 6 Wind Direction/North Loc [ Wdir ]
; Calculate and hold hourly Max Wspd and Wdir in input

; locations 12 and 13 (MaxHrWS, MaxHrWD)
; Direct output processing to input locations

2: 12 Loc [ MaxHrWS ]
40: Maximum (P73)

1: 1 Reps
2: 0 Value Only
3: 5 Loc [ Wspd ]
41: Sample on Max or Min (P79)

1: 1 Reps
2: 6 Loc [ Wdir ]
; Write hourly RAWS-7 data to final storage area 1.

; Order is important, First in - First out.
;Precip (Hourly Total)
;Wind Speed (10 minute Average prior to the hour)
;Wind Direction (10 minute Average prior to the hour)
;Air Temperature(Hourly Sample)
;Fuel Temperature (Hourly Sample)
;RH (Hourly Sample)
;Battery Voltage (Hourly Minimum)

; Direct output processing to final storage area 1

1: 1 Final Storage Area 1
2: 60 Array ID
44: Totalize (P72)

1: 1 Reps
2: 8 Loc [ Prcip ]
D-9
45: Sample (P70)

1: 1 Reps
2: 10 Loc [ Avg10WS ]
46: Sample (P70)

1: 1 Reps
2: 11 Loc [ Avg10WD ]
47: Sample (P70)

1: 1 Reps
2: 3 Loc [ AirTemp ]
48: Sample (P70)

1: 1 Reps
2: 7 Loc [ FuelT ]
49: Sample (P70)

1: 1 Reps
2: 4 Loc [ RH ]
50: Minimum (P74)

1: 1 Reps
2: 0 Value Only
3: 1 Loc [ BattVolt ]
; Send the basic RAWS-7 data to the SAT HDR GOES 5 minutes before transmit time.
; FS 1 must contain only the new RAWS-7 data, 3 hours of data.
3: 30 Then Do
; P126 set to "insert" data to "self-timed" buffer.

; Insert will erase the buffer before sending the
; new RAWS-7 data.
1: 1 Self Timed/Insert
2: 3 ASCII RAWS-7 Format
53: End (P95)
; ***********************************************
; Calculate and hold data beyond the RAWS-7 data.
; ***********************************************
; Four additional data values are written.

; Must create a table, one column for each hour.
; Each column has 4 data points:
; Direction of Max wind speed, Max wind speed,
; Ave Solar Radiation, fuel moisture.
; Solar radiation is in high resolution format.
D-10
; FIRST HOUR
; First hour (column 1) is the top of the first hour after
; the transmit window.
; Move hourly values to "old" place holders

; Input storage is used to hold hourly data until
; 3 hours of RAWS-7 data has been written to final storage
; and sent to the transmitter
1: 120 Minutes (Seconds --) into a ;changed 3/31/0

2: 16 Loc [ MaxWD_Old ]
56: Sample (P70)

1: 1 Reps
2: 13 Loc [ WDHrMxWS ]

2: 19 Loc [ MaxWS_Old ]
58: Sample (P70)

1: 1 Reps

2: 22 Loc [ SRad_Old ]
;Solar radiation is high resolution format

60: Resolution (P78)
1: 1 High Resolution
61: Average (P71)

1: 1 Reps
2: 9 Loc [ SRad ]

1: 0 Low Resolution
; Fuel Moisture
2: 25 Loc [ FM_Old ]
64: Sample (P70)

1: 1 Reps
2: 28 Loc [ FuelM ]
D-11
;SECOND HOUR
; At the second hour of a 3 hour interval, move hourly data

; values to the "mid" place holders.

2: 17 Loc [ MaxWD_Mid ]
67: Sample (P70)

1: 1 Reps

2: 20 Loc [ MaxWS_Mid ]
69: Sample (P70)

1: 1 Reps

2: 23 Loc [ SRad_Mid ]

72: Average (P71)

1: 1 Reps
2: 9 Loc [ SRad ]

1: 0 Low Resolution

2: 26 Loc [ FM_Mid ]
75: Sample (P70)

1: 1 Reps
2: 28 Loc [ FuelM ]
;THIRD HOUR
D-12
; At the top of the 3rd hour, move hourly data values

; to the "new" place holders

2: 18 Loc [ MaxWD_New ]
78: Sample (P70)

1: 1 Reps

2: 21 Loc [ MaxWS_New ]
80: Sample (P70)

1: 1 Reps

2: 24 Loc [ SRad_New ]

83: Average (P71)

1: 1 Reps
2: 9 Loc [ SRad ]

1: 0 Low Resolution

2: 27 Loc [ FM_New ]
86: Sample (P70)

1: 1 Reps
2: 28 Loc [ FuelM ]
; **********************************************
; Data values beyond RAWS-7, written to final
; storage and copied to transmitter
; **********************************************
; Write wind direction of the max wind speed, max wind speed,
; average solar radiation and fuel moisture to FS 1 and the GOES transmitter.
; Format will look like:
D-13
; xxx xxx xxx Dir Max WS : Oldest to the left

; xxx xxx xxx Max WS : Oldest to the left
; xxxxx xxxxx xxxxx Avg SRad : Oldest to the left
; xxx xxx xxx fuel mois : Oldest to the left
;P126 Instruction, Parameter 2 Options

; 3 RAWS-7 Output
; 4 xxx.x ASCII Output
; 5 xx.xx ASCII Output
; 6 x.xxx ASCII Output
; 7 xxx ASCII Output
; 8 xxxxx ASCII Output of a high resolution value
; No less than 5 minutes before transmit time, data is

; written to final storage and copied to the transmitter
3: 30 Then Do
88: Do (P86)

2: 123 Array ID
; Write first row after RAWS-7 data, Row 8.

; Direction of max wind speed
90: Sample (P70)
1: 3 Reps
2: 16 Loc [ MaxWD_Old ]
; Copy Row 8 to transmitter

2: 7 ASCII xxx Format
92: Do (P86)
; Write row 9 to final storage, Max Wind Speed

93: Sample (P70)
1: 3 Reps
2: 19 Loc [ MaxWS_Old ]
; Copy to transmitter
D-14
95: Do (P86)
; Set resolution high

; Write row 10 to final storage

97: Sample (P70)
1: 3 Reps
2: 22 Loc [ SRad_Old ]
; set resolution low

1: 0 Low Resolution
; Copy row 10 to transmitter

2: 8 ASCII xxxxx Format
100: Do (P86)
; Write row 11 to final storage

101: Sample (P70)
1: 3 Reps
2: 25 Loc [ FM_Old ]
; Copy row 11 to transmitter

103: End (P95)
*Table 2 Program
02: 600 Execution Interval (seconds)
1: If time is (P92)
3: 30 Then Do
2: HDR GOES Status (P127)

1: 2 Read Last Message Status
2: 30 Result Code Loc [ L_Msg_RC ]
D-15
3: Z=X*F (P37)
1: 35 X Loc [ Batt_load ]
2: .1 F
3: 35 Z Loc [ Batt_load ]
4: Z=X*F (P37)
1: 36 X Loc [ GPSAccTm ]
2: 10 F
3: 36 Z Loc [ GPSAccTm ]
5: End (P95)
; Set datalogger clock to GPS time once a day

6: If time is (P92)
3: 30 Then Do
7: HDR GOES Status (P127)

1: 0 Read Time
2: 44 Result Code Loc [ time_rc ]
8: If (X<=>F) (P89)
1: 44 X Loc [ time_rc ]
2: 4 <
3: 1 F
4: 30 Then Do
9: If (X<=>F) (P89)
1: 45 X Loc [ GPS_hour ]
2: 3 >=
3: 0 F
4: 30 Then Do
10: If (X<=>F) (P89)

1: 45 X Loc [ GPS_hour ]
2: 4 <
3: 24.1 F
4: 30 Then Do
11: Set Real Time Clock (P114)

1: 0 Set Hr,Min,Sec from locations
2: 45 Loc [ GPS_hour ]
12: End (P95)
13: End (P95)
14: End (P95)
15: End (P95)

D-16

2: 222 Array ID
18: Real Time (P77)

1: 0220 Day,Hour/Minute (midnight = 2400)
19: Sample (P70)

1: 1 Reps
2: 14 Loc [ P126_RC ]
20: Sample (P70)

1: 8 Reps
2: 30 Loc [ L_Msg_RC ]
21: Sample (P70)

1: 1 Reps
2: 2 Loc [ Prog_Sig ]
*Table 3 Subroutines
End Program
D-17
D-18
Appendix E. GOES DCS Transmit
Frequencies
300 & 100 BPS Channels 1200 BPS Channels 300 & 100 BPS Channels 1200 BPS Channels
Channel Frequency Channel Frequency Channel Frequency Channel Frequency
Number MHz Number+ A MHz Number MHz Number+ A MHz
1 401.701000 1 401.701750 48 401.771500

2 401.702500 49 401.773000 25 401.773750
3 401.704000 2 401.704750 50 401.774500
4 401.705500 51 401.776000 26 401.776750
5 401.707000 3 401.707750 52 401.777500
6 401.708500 53 401.779000 27 401.779750
7 401.710000 4 401.710750 54 401.780500
8 401.711500 55 401.782000 28 401.782750
9 401.713000 5 401.713750 56 401.783500
10 401.714500 57 401.785000 29 401.785750
11 401.716000 6 401.716750 58 401.786500
12 401.717500 59 401.788000 30 401.788750
13 401.719000 7 401.719750 60 401.789500
14 401.720500 61 401.791000 31 401.791750
15 401.722000 8 401.722750 62 401.792500
16 401.723500 63 401.794000 32 401.794750
17 401.725000 9 401.725750 64 401.795500
18 401.726500 65 401.797000 33 401.797750
19 401.728000 10 401.728750 66 401.798500
20 401.729500 67 401.800000 34 401.800750
21 401.731000 11 401.731750 68 401.801500
22 401.732500 69 401.803000 35 401.803750
23 401.734000 12 401.734750 70 401.804500
24 401.735500 71 401.806000 36 401.806750
25 401.737000 13 401.737750 72 401.807500
26 401.738500 73 401.809000 37 401.809750
27 401.740000 14 401.740750 74 401.810500
28 401.741500 75 401.812000 38 401.812750
29 401.743000 15 401.743750 76 401.813500
30 401.744500 77 401.815000 39 401.815750
31 401.746000 16 401.746750 78 401.816500
32 401.747500 79 401.818000 40 401.818750
33 401.749000 17 401.749750 80 401.819500
34 401.750500 81 401.821000 41 401.821750
35 401.752000 18 401.752750 82 401.822500
36 401.753500 83 401.824000 42 401.824750
37 401.755000 19 401.755750 84 401.825500
38 401.756500 85 401.827000 43 401.827750
39 401.758000 20 401.758750 86 401.828500
40 401.759500 87 401.830000 44 401.830750
41 401.761000 21 401.761750 88 401.831500
42 401.762500 89 401.833000 45 401.833750
43 401.764000 22 401.764750 90 401.834500
44 401.765500 91 401.836000 46 401.836750
45 401.767000 23 401.767750 92 401.837500
46 401.768500 93 401.839000 47 401.839750
47 401.770000 24 401.770750 94 401.840500
E-1
Appendix E. GOES DCS Transmit Frequencies
95 401.842000 48 401.842750 145 401.917000 73 401.917750

96 401.843500 146 401.918500
97 401.845000 49 401.845750 147 401.920000 74 401.920750
98 401.846500 148 401.921500
99 401.848000 50 401.848750 149 401.923000 75 401.923750
100 401.849500 150 401.924500
101 401.851000 51 401.851750 151 401.926000 76 401.926750
102 401.852500 152 401.927500
103 401.854000 52 401.854750 153 401.929000 77 401.929750
104 401.855500 154 401.930500
105 401.857000 53 401.857750 155 401.932000 78 401.932750
106 401.858500 156 401.933500
107 401.860000 54 401.860750 157 401.935000 79 401.935750
108 401.861500 158 401.936500
109 401.863000 55 401.863750 159 401.938000 80 401.938750
110 401.864500 160 401.939500
111 401.866000 56 401.866750 161 401.941000 81 401.941750
112 401.867500 162 401.942500
113 401.869000 57 401.869750 163 401.944000 82 401.944750
114 401.870500 164 401.945500
115 401.872000 58 401.872750 165 401.947000 83 401.947750
116 401.873500 166 401.948500
117 401.875000 59 401.875750 167 401.950000 84 401.950750
118 401.876500 168 401.951500
119 401.878000 60 401.878750 169 401.953000 85 401.953750
120 401.879500 170 401.954500
121 401.881000 61 401.881750 171 401.956000 86 401.956750
122 401.882500 172 401.957500
123 401.884000 62 401.884750 173 401.959000 87 401.959750
124 401.885500 174 401.960500
125 401.887000 63 401.887750 175 401.962000 88 401.962750
126 401.888500 176 401.963500
127 401.890000 64 401.890750 177 401.965000 89 401.965750
128 401.891500 178 401.966500
129 401.893000 65 401.893750 179 401.968000 90 401.968750
130 401.894500 180 401.969500
131 401.896000 66 401.896750 181 401.971000 91 401.971750
132 401.897500 182 401.972500
133 401.899000 67 401.899750 183 401.974000 92 401.974750
134 401.900500 184 401.975500
135 401.902000 68 401.902750 185 401.977000 93 401.977750
136 401.903500 186 401.978500
137 401.905000 69 401.905750 187 401.980000 94 401.980750
138 401.906500 188 401.981500
139 401.908000 70 401.908750 189 401.983000 95 401.983750
140 401.909500 190 401.984500
141 401.911000 71 401.911750 191 401.986000 96 401.986750
142 401.912500 192 401.987500
143 401.914000 72 401.914750 193 401.989000 97 401.989750
144 401.915500 194 401.990500
E-2
195 401.992000 98 401.992750 245 402.067000 123 402.067750

196 401.993500 246 402.068500
197 401.995000 99 401.995750 247 402.070000 124 402.070750
198 401.996500 248 402.071500
199 401.998000 100 401.998750 249 402.073000 125 402.073750
200 401.999500 250 402.074500
201 402.001000 101 402.001750 251 402.076000 126 402.076750
202 402.002500 252 402.077500
203 402.004000 102 402.004750 253 402.079000 127 402.079750
204 402.005500 254 402.080500
205 402.007000 103 402.007750 255 402.082000 128 402.082750
206 402.008500 256 402.083500
207 402.010000 104 402.010750 257 402.085000 129 402.085750
208 402.011500 258 402.086500
209 402.013000 105 402.013750 259 402.088000 130 402.088750
210 402.014500 260 402.089500
211 402.016000 106 402.016750 261 402.091000 131 402.091750
212 402.017500 262 402.092500
213 402.019000 107 402.019750 263 402.094000 132 402.094750
214 402.020500 264 402.095500
215 402.022000 108 402.022750 265 402.097000 133 402.097750
216 402.023500 266 402.098500
217 402.025000 109 402.025750
218 402.026500
219 402.028000 110 402.028750
220 402.029500
221 402.031000 111 402.031750
222 402.032500
223 402.034000 112 402.034750
224 402.035500
225 402.037000 113 402.037750
226 402.038500
227 402.040000 114 402.040750
228 402.041500
229 402.043000 115 402.043750
230 402.044500
231 402.046000 116 402.046750
232 402.047500
233 402.049000 117 402.049750
234 402.050500
235 402.052000 118 402.052750
236 402.053500
237 402.055000 119 402.055750
238 402.056500
239 402.058000 120 402.058750
240 402.059500
241 402.061000 121 402.061750
242 402.062500
243 402.064000 122 402.064750
244 402.065500
E-3
E-4
Appendix F. High Resolution 18-Bit
Binary Format
When using the binary 18 bit signed 2’s complement integer format, all data
values in the datalogger final storage area must be in high resolution format. In
most cases the datalogger program should set the data resolution to high at the
beginning of the program. Use the P78 instruction with parameter 1 set to 1.
Note: P77 Real Time can not write the time or date in high resolution. To send
a time stamp, first write the time back to input locations, then sample the input
locations as high resolution. As an alternative to using P77 for a time stamp,
the GPS time can be retrieved from the transmitter and written to final storage
in high resolution format. See instruction P127 for details.
Because the binary 18 bit integer is an integer, all information to the right of
the decimal point is dropped. This occurs while the datalogger is copying data
to the transmitter. The original data is left intact in final storage of the
datalogger. If transmitted data requires precision to the right of the decimal
place, multiply the number by the required factor of 10 before storing the data
to final storage. After data is received by the ground station, division by the
appropriate factor of 10 will replace the decimal point.
In high resolution format, data stored in final storage has a maximum

magnitude of 99999 and a minimum magnitude of 0.00001.
NESDIS has placed restrictions on the format of data sent over the GOES
satellite network. The first restriction is the use of 7 data bits and one parity bit
per byte. The second restriction is the most significant data bit of each byte, bit
6, is always set. Without data, each byte transmitted over the satellite has the
format of “p1xxxxxx”. The x’s will hold the 6 bits per byte allocated to data
information. The “p” is the parity bit and the “1” is bit 6 which is always set.
Resolution of each data point would be severely limited if the data point
consisted of only 6 bits. We use 3 consecutive bytes to form a data point word.
The first byte sent is byte 3, the most significant byte. A complete word is
created by using 3 consecutive bytes, stripping the 2 most significant bits from
each byte, then combining the 3 bytes into a word. See the examples below.
Each data point is formatted as an 18 bit integer. The format uses the
most significant bit (bit 17) to designate sign. The format of each 3
byte data point is as follows, note the top row shows the bits used and
there significance.
17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
p 1 x x x x x x p 1 x x x x x x p 1 x x x x x x
Where each “p” is the parity bit for that byte.

Where each “1” is bit 6 for that byte and always set to 1
Where the 6 “x”s represent bits 0 through 5, these make up the
information for each byte.
Where the 18 bit data point is made by combining the three bytes
after bit 7 and bit 6 of each byte have been dropped.
Where 0 represents bit 0 - the least significant bit
F-1
Appendix F. High Resolution 18-Bit Binary Format
Where 17 represents bit 17 - the most significant bit and is used to

determine the sign.
Converting the 18 bit data point to an integer can be done manually. Don’t
forget the 18 bits are numbered 0 through 17. Bit 17 is the sign bit, when bit 17
is set, the number is negative. If bit 17 is set, subtract 1 from the number then
take the complement of the number. If bit 17 is not set, simply convert the
number to its decimal equivalent.
Example positive data point conversion:
Byte Label byte 3 byte 2 byte 1

Actual data point 01000101 11110010 11010010
Drop first 2 bits of

each byte 000101 110010 010010
Combine the 3
bytes into one word 000101 110010 010010
Convert from Binary to Decimal 23698
Example of a negative data point conversion:
Byte Label byte 3 byte 2 byte 1

Actual data point 01111010 11001101 11101101
Drop first 2 bits of

each byte 111010 001101 101101
Notice bit 17 is set,
Combine the 3
bytes into one word 111010 001101 101101
Subtract 1 from the number 111010 001101 101100
Take the complement of

each bit 000101 110010 010011
Convert the binary value

into a decimal value, don’t
forget the negative sign -23699
F-2
Appendix G. Extended ASCII Command
Set
Appendix G describes the ASCII command interface for the TX312 transmitter. These
commands can be entered using the terminal window of SatCommander software, or
suitable terminal emulation software.
G.1 Command Interface

G.1.1 RS-232 Serial Port Interface
All Data Entry and Diagnostic functions are accessed using the RS-232
Interface.
G.1.1.1 RS232 Hardware Interface

The default settings for the RS-232 port are 9600 baud, 8 data bits, no parity
and 1 stop bit.
Three RS232 connections (TXD, RXD and GND) are used, no handshaking is
needed and should be set to none in the terminal emulator.
G.1.1.2 Command Protocol

A [CR] (0x0d) must be entered to get the transmitter’s attention and is used to
terminate a command line. The transmitter responds with a ‘>’ (0x3e) to
indicate that it is ready to receive a command. If no characters are entered for
60 seconds, any partially entered commands are deleted and the transmitter’s
attention is lost. To get the transmitters attention a character must be entered
followed by a [CR] until the ‘>’ prompt is returned.
Commands can optionally be terminated with [CR][LF]; in other words, a [LF]

character received following a [CR] will be ignored.
Each character entered is echoed to the host to allow for simple error checking
and to support the terminal nature of the implementation. A backspace
character (BS, 0x08) deletes the last character entered. The ESC character
(0x1b) will delete the entire command.
The command protocol is not case sensitive. Many commands are used to set
or retrieve various configuration parameters. When setting parameters, the
command is followed by an equals sign (‘=’) and a comma separated list of
parameters. When retrieving parameters, the command is entered without the
‘=’ or followed by a question mark (‘?’).
Some commands are used to direct the transmitter to execute a specific

function (e.g. clear a buffer); in such cases, neither a ‘=’ or a ‘?’ is required. If
the command has parameters associated with it they will appear as a comma
separated list following the command itself.
G-1
Appendix G. Extended ASCII Command Set
Unless otherwise noted, the transmitter will respond to all commands with one
of the following:
“OK[CR][LF]>" if command was accepted,

"Bad parameter[CR][LF]>" if a command parameter was invalid,
"Unknown Format[CR][LF]>" if there are too many or too few
parameters,
"Access Denied![CR][LF]>" if the command requires a higher access
level,
"Unknown Command[CR][LF]>" if the command is unknown,
"Execution Error[CR][LF]>" if the command fails during execution,
"Transmitter Must Be Disabled[CR][LF]>" if the transmitter must be
disabled prior to using this command.,
"Transmitter Must Be Enabled[CR][LF]>" if command must first be
enabled,
"Configuration Not Recognized[CR][LF]>" if configuration is invalid,
If the command was a request for a configuration parameter the transmitter will
respond with:
<cmd>=<data>[CR][LF]> When returning data parameters.
G.1.1.3 Command Access Level

All commands are subject to an access right to restrict access to calibration and
test commands. Two access levels are defined: USER and TECHNICIAN. An
error will be returned if a TECHNICIAN level command is entered while at the
USER command access level. USER level commands are always available
including when at the TECHNICIAN command access level. The Technician
level commands are not described here.
The command access level is changed by using the password protected

TECHMODE command. After power up the access level is always USER. The
access level of each command is noted in each command description.
Some commands are only available when transmissions are disabled. This is
also noted along with each command description.
G.2 General Configuration Commands

G.2.1 Clock Read/Set
Syntax:
TIME= yyyy/mm/dd hh:mm:ss
Access level: USER

TX312 State: Enabled/Disabled
This command sets the date and time in the transmitter. The date and time will
be overwritten when a GPS time synchronization occurs. Self timed
transmissions will not occur until the time has been set either using this
command or from the GPS. Random transmissions will occur with or without
time being set.
The real time clock starts at 01/01/2000 00:00:00 at power up.
G-2
G.2.2 Replacement Character Read/Set

Syntax:
IRC=c
Access level: USER

This command defines the ASCII character that will be substituted for any
Prohibited ASCII character detected in the transmission data when operating in
ASCII or Pseudo-Binary mode. The default character is ‘*’. Only printable
ASCII characters, excluding space, are permitted. In Pseudo-Binary mode,
numeric characters are considered illegal.
G.2.3 Save Configuration

Syntax:
SAVE
Access level: USER

This command directs the transmitter to commit the entered configuration

parameters to non-volatile memory. Until this command is entered, the
previously saved configuration can be recalled using the RSTR command.
G.2.4 Restore Configuration

Syntax:
RSTR
Access level: USER

This command directs the transmitter to restore the configuration parameters

from non-volatile memory. Changes made to the configuration are not
automatically saved to non-volatile memory as they are entered. This allows
changes to be made and verified before committing them to permanent storage,
but provides the ability to recall the last saved settings, if necessary.
G.2.5 Restore Default Configuration

Syntax:
DEFAULT
Access level: USER

This command directs the transmitter to set the configuration parameters to

their factory default (mostly invalid) values; this essentially clears the
operation of the transmitter. This command does not automatically save the
cleared parameters to non-volatile memory; the SAVE command must be
issued to complete the sequence.
This command does not set the calibration data or serial number to factory
defaults.
G-3
G.2.6 Enable Transmissions

Syntax:
ETX
Access level: USER

TX312 State: Disabled
This command enables transmissions. The configuration parameters will be

checked for validity. If valid, they are saved to non-volatile memory and the
transmitter is enabled. The enabled/disabled state of the transmitter is also
stored in non-volatile memory so that it will resume operation after a power
cycle if it was previously enabled.
Note that the factory default configuration is not valid. The factory default
parameters must be explicitly overwritten with valid values before
transmissions can be enabled.
G.2.7 Disable Transmissions

Syntax:
DTX
Access level: USER

TX312 State: Enabled
This command disables transmissions. Normal scheduling of transmissions is

suspended.
Note that the transmitter is automatically disabled if configuration parameters

are modified and must be re-enabled with the ETX command to resume
transmitting.
G.2.8 Read Configuration

Syntax:
RCFG
Access level: USER

This command lists all of the configuration parameters. Each parameter is in

the same format as if its individual command had been executed.
For Example:
RCFG
NESID=326d31d4
TCH=92
.
.
.
The output from the RCFG command can be captured by the host (in a text
file) and used to duplicate the configuration in another unit.
G-4
G.2.9 Enable Technician Command Mode

Syntax:
TECHMODE password
Access level: USER

This command changes the command access level to TECHNICIAN. The

access level will not change unless the password is correct.
G.2.10 Enable User Command Mode

Syntax:
USERMODE
Access level: USER

This command changes the command access level back to USER. No password
is required. A power cycle of the transmitter will also return the command
access level to USER.
G.2.11 Set GPS Fix Interval

Syntax:
GIN=hh:mm:ss
Access level: USER

Default value: 00:00:00
This command sets the GPS position fix interval to the hours, minutes, seconds
specified in hh:mm:ss. It can also be used without the ‘=’ sign to report the
current value. Valid range of hh:mm:ss is 00:05:00 to 24:00:00. A value of
00:00:00 will disable periodic GPS position fixes although they will still occur
at power up and every 24 hours as a side effect of the daily automatic OCXO
calibration. The current value of the GPS fix interval is also reported by the
RCFG command. The parameter is non-volatile when saved using the SAVE or
ETX commands.
G.3 GOES Transmission Configuration commands

The following commands are used to set the configuration parameters for
GOES transmissions. Unless otherwise specified, these parameters have
invalid default values and must be set explicitly before transmissions can be
enabled using the ETX command. These parameters are stored in non-volatile
memory by issuing the SAVE command or will be automatically saved when
the transmitter is enabled.
The transmitter is disabled automatically if any of these parameters are

modified. Parameters can be read by entering the command without the ‘=’
while transmissions are enabled or disabled. All parameters can be read at the
same time using the RCFG command.
G-5
G.3.1 Set GOES DCP Platform ID

Syntax:
NESID=xxxxxxxx
Access level: USER

Sets the transmitter’s GOES DCP Platform ID to the hex value xxxxxxxx.
Valid range is even hex numbers from 2 to 0xfffffffe.
G.3.2 Set Self-Timed Transmission Channel Number

Syntax:
TCH=ccc
Access level: USER

This command sets the channel number (ccc) for timed transmissions. ccc is
the channel number and has a valid range of 0 – 266 for bit rates of 100 and
300 BPS and a range of 0 – 133 for a bit rate of 1200 BPS.
For 100 BPS operation on channels 201-266, the transmitter will be configured
for International operation. Specifically, the 31-bit International EOT will be
used (0x63CADD04) in place of the ASCII EOT, and the preamble will be
forced to Long.
Setting the channel number to 0 will disable timed transmissions.
G.3.3 Set Self-Timed Transmission Bit Rate

Syntax:
TBR=bbbb
Access level: USER

This command sets the timed transmission bit rate where bbbb is the bit rate
parameter and has valid values of 100, 300 and 1200 BPS.
G.3.4 Set Self-Timed Transmission Interval

Syntax:
TIN=dd:hh:mm:ss
Access level: USER

Set interval between timed transmissions to days, hours, minutes, seconds

specified in dd:hh:mm:ss. Valid range is 00:00:05:00 to 30:23:59:59.
G-6
G.3.5 Set Self-Timed transmission First Transmission Time

Syntax:
FTT=hh:mm:ss
Access level: USER

Set the time for the first timed transmission of the day. Valid range is 00:00:00
to 23:59:59. The First Transmission Time is also referred to as the Offset, and
is between 00:00:00 and the Self-Timed Transmission Interval.
G.3.6 Set Self-Timed Transmission Transmit Window Length

Syntax:
TWL=xxx
Access level: USER

Set the length of the timed transmit window. Length is specified in seconds.
Valid range is 5 to 240 seconds.
G.3.7 Enable or Disable Self-Timed Transmission Message

Centering
Syntax:
CMSG=Y/N
Access level: USER

Center the timed transmission in the assigned window if Y otherwise transmit

at beginning of assigned window.
G.3.8 Enable or Disable Self-Timed Buffer Empty Message

Syntax:
EBM=Y/N
Access level: USER

If EBM is Y, send “BUFFER EMPTY” message if the buffer is empty at time

of transmission. If EBM is N do not transmit if the buffer is empty.
THIS IS NOT FULLY IMPLEMENTED! CURRENTLY IF BUFFER IS

EMPTY AT TRANSMIT TIME A MESSAGE IS WRITTEN TO THE
AUDIT LOG IF EBM=Y
G-7
G.3.9 Set Self-timed Transmission Preamble Length

Syntax:
TPR=S/L
Access level: USER

Set the preamble type for timed transmissions. Valid values are S or L (Short
or Long). This setting only applies for 100 BPS timed transmissions on
channels 1-200. All 300 and 1200 BPS transmissions us short preamble. All
100 BPS transmissions on channels above 200 use long preamble.
G.3.10 Set Self-Timed Transmission Interleaver Mode

Syntax:
TIL =S/L/N
Access level: USER

Set the timed transmission interleaver type. Valid values are S,L,N (Short,
Long or None). This setting only applies for HDR timed transmissions, i.e.
300 or 1200 BPS.
G.3.11 Set Self-Timed Transmission Data Format

Syntax:
TDF =A/P/B
Access level: USER

This command sets the timed transmission format to ASCII, Pseudo-Binary or

Binary. Valid values are A, P or B. This parameter is used to determine the
flag word in 300 and 1200 BPS transmissions.
Note: It is the responsibility of the host to ensure the data provided for
transmission is in the proper format. ASCII data can not be transmitted when
Pseudo Binary format is selected. Pseudo Binary can be transmitted with
ASCII format has been selected.
G.3.12 Set Random Transmission Channel Number

Syntax:
RCH=ccc
Access level: USER

This command sets the channel number for random transmissions. ccc is the
channel number and has a valid range of 0 – 266 for bit rates of 100 and 300
BPS and a range of 0 – 133 for a bit rate of 1200 BPS.
G-8
For 100 BPS operation on channels 201-266, the transmitter will be configured
for International operation. Specifically, the 31-bit International EOT will be
used (0x63CADD04) in place of the ASCII EOT.
Setting the channel number to 0 will disable random transmissions.
G.3.13 Set Random Transmission Bit rate

Syntax:
RBR=bbbb
Access level: USER

This command sets the random transmission bit rate where bbbb is the bit rate
parameter and has valid values of 100, 300 and 1200.
G.3.14 Set Random Transmission Interval

Syntax:
RIN =mm
Access level: USER

Set the random transmission randomizing interval to mm minutes. The

randomizing interval is the interval in which a random transmission will occur
if there is data in the random transmission buffer. The actual transmission time
will be random, but on average will occur at this rate. Valid range is 5 to 99
minutes.
G.3.15 Set Random Transmission Randomizing Percentage

Syntax:
RPC =mm
Access level: USER

This value determines the range of randomization as a percentage of the

randomizing interval. Random transmissions will occur at a uniformly
distributed random time within this range and on average occur at the
randomizing interval rate. Valid range is 10 to 50%.
For example, for a randomizing interval =15 (minutes) and a randomizing

percentage =20 (%), then the time between any two random transmissions will
be 12 to 18 minutes (15 ± 3 minutes).
G.3.16 Set Random Transmission Repeat Count

Syntax:
RRC =xx
Access level: USER

G-9
The random transmission repeat count is the number of times a random

transmission will be repeated. The random transmissions will occur once every
random transmission interval as specified by the randomizing interval. The
valid range of this parameter is 0 – 99. For example, a value of 3 will direct
the transmitter to send the data in the Random buffer 3 times before clearing it.
A value of 0 indicates that random transmissions will occur every random
transmission interval until the random buffer is cleared by the host.
G.3.17 Enable or Disable Random Transmission Message

Counter
Syntax:
RMC=Y/N
Access level: USER

If RMC is Y a random message counter will be included at the beginning of the

message, ahead of the user data. If it is N the random message count will not be
included.
G.4 SDI-12 Configuration Commands

G.4.1 Select CS I/O Port Mode
Syntax:
CSMODE=x
Where: x = SDC enables the CS I/O port for SDC slave communications
with a CR10X, CR10X PB or CR1000 data logger. The TX312
address is fixed at 0x41.
x = SDI enables the SDI-12 port as an SDI-12 recorder. Sensors

connected to the SDI-12 port will be polled using the SDI-12
commands entered into the SDI-12 command table.
Access level: USER

This parameter is saved to non-volatile memory using the SAVE command and
is part of the configuration read back with the RCFG command.
G.4.2 Enter SDI-12 Transparent Mode

Syntax:
ETM
Access level: USER

Enter SDI-12 transparent mode. The prompt will change from > to * to indicate
that the transmitter is in SDI-12 transparent mode. Any characters entered at
the terminal will be buffered up to the command termination character ‘!’ The
characters will then be sent to the SDI-12 port as SDI-12 commands. No check
for valid command or address is performed other than the requirement for a ‘!’
command terminator. Exit the SDI-12 transparent mode by typing [ESC].
G-10
G.4.3 Add SDI-12 Measurement Commands to the SDI-12

Command Table
Syntax:
SDI i,aX[C][n]!,[#values]
Where:
i is a command table index from 0-9
a is the SDI address of the sensor
X specifies the command type and is one of M, C or R
C is an optional character indicating the CRC is to be used in the
SDI-12 bus transaction
n is an optional parameter indicating the measurement variant being
used (0-9)
! is the command termination character
#values is the number of values to add to the transmit buffer from
those returned by the sensor. This parameter is optional. If not
specified all returned values are added to the transmit buffer.
The response to the SDI command will be “OK” if the SDI command was
successfully added to the command table or “Unknown Format” if the
command format is not recognized;
Examples:
i) SDI 2,1M6!,3
ii) SDI 7, 3CC4!,2
iii) SDI 1, 0R!,1
Access level: USER

This command adds an SDI-12 command to the SDI command table in the
table location specified by the table index. The command table can hold up to
10 entries numbered 0 to 9. The SDI-12 measurement sequence, including D
commands and service request detection as required, will be used as
appropriate for the command type. If the number of values returned by the
sensor is less than the #values parameter, the missing fields will be filled with
“///”. If there are more values returned than specified by the #values parameter,
the extra values will not be included in the transmit buffer.
When the SDI-12 port is enabled the SDI-12 commands will be executed
consecutively starting with index 0.
Commands entered using the SDI command are made non-volatile along with
other configuration commands using the SAVE command.
G.4.4 Clear SDI-12 Commands

Syntax:
CSDI [i]
Where:
i is an optional table index indicating the table entry to clear.
Access level: USER

G-11
This command clears the SDI command table entry indicated by i or all SDI-12
commands if i is not specified.
G.4.5 Print SDI-12 Commands

Syntax:
PSDI [i]
Where:
i is an optional table index indicating the table entry to print.
Access level: USER

This command prints the SDI command table entry indicated by i or all SDI-12
commands if i is not specified. The RCFG command will be also print the
contents of the SDI table along with the other configuration parameters.
G.4.6 Set SDI-12 Transmit Format

Syntax:
SDF=FC
Where:
FC is a format code
If FC=0 the data is transmitted as a series of records separated by [CR][LF].

The records are buffered until transmission time and then transmitted in reverse
chronological order. After transmission the buffer is cleared. Each record will
include the address of the sensor that generated the values and a comma
separated list of the values returned for a single measurement. The record
format is shown below:
a,sn.nnn,sn.nnnn,sn.nn[CR][LF]
Where: a is the sensor address

s is ‘+’ or ‘-‘
n are digits 0 – 9
Individual values including sign will be replaced with /// if the value was not
returned successfully by the sensor. Entire records will be replaced by /// if the
sensor did not respond successfully.
Examples:
In this example the newest record is at the top and oldest record is at the
bottom.
1,+3.14,-2.789,///,///[CR][LF]
5,-44,+86,+23.4[CR][LF]
2,+345.5,-23.88,-77.7[CR][LF]
1,+4.14,-3.789,///,///[CR][LF]
5,-44,+88,+23.5[CR][LF]
G-12
2,+348.5,-23.97,-55.7[CR][LF]
1,+3.24,-2.789,///,///[CR][LF]
5,-46,+86,+23.4[CR][LF]
2,+344.5,-28.88,-77.7[CR][LF]
1,+3.55,-2.733,///,///[CR][LF]
5,-24,+86,+25.4[CR][LF]
2,+645.5,-24.88,-77.7[CR][LF]
If FC=1 the format is the same except that each record is preceeded by a 24
hour time stamp with the format hh:mm:ss. The time stamp is always in 24
hour form and referenced to UTC.
G.4.7 Set SDI Sample Interval

Syntax:
SIN=hh:mm:ss
Access level: USER

Sets the sample interval for all SDI-12 sensors. If the interval is set to a value
less than the time required to perform all the SDI-12 measurements, the
measurements will be performed continuously. Setting the value to 00:00:00
effectively disables SDI-12 data collection.
Valid range is 00:00:00 to 23:59:59.
G.4.8 Set SDI Sample Interval Offset

Syntax:
SOF=hh:mm:ss
Access level: USER

Sets the sample interval offset for all SDI-12 sensors.
Valid range is 00:00:00 to 23:59:59.
G-13
G.4.9 Test SDI-12 Command Table

Syntax:
STT
Access level: USER

This command forces the command table to be executed immediately. The

measurement results are printed to the terminal rather than being buffered for
transmission.
G.5 Data Buffer Loading Commands

The following commands are used to manage and store data in the GOES
Transmission buffers.
G.5.1 Load Self-Timed Transmission Buffer

Syntax:
TDT =xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Access level: USER

This command overwrites the GOES Timed Buffer with the data provided.
The TX312 transmitter will insert the 31 bit GOES ID, any header information
(e.g. HDR Flag byte), and append the EOT so these should not be included in
the TDT data. If the timed data format is ASCII or Pseudo-Binary the
transmitter will also insert the correct parity bit for each message character and
replace illegal characters with the character specified by the IRC=c command
before transmission.
Characters that have meaning for the command interface (CR, LF, BS,
ESC,’~’) must be preceded by a ‘~’ character if they appear in the message
data.
The maximum length of the formatted data can be up to 126000 bits, or 15750
bytes.
If there is more data loaded into the buffer than can be transmitted in the
assigned transmit window the message will be truncated.
One minute prior to transmission data is removed from the transmit buffer and
encoded for transmissiion (The Data In Buffer LED will go out). If this
command is received within 1 minute of the transmission time or during a
timed transmission, the data will not be included in the current transmission but
will be buffered for the next interval.
G-14
G.5.2 Read Number of Bytes in the Self-Timed Transmission

Buffer
Syntax:
TML
Access level: USER

Returns the number of bytes stored in the timed transmission buffer.
G.5.3 Read the Maximum Self-Timed Message Length

Syntax:
MTML
Access level: USER

Returns the maximum number of bytes that can be transmitted with the current
timed transmission bit rate, window length and preamble type.
G.5.4 Clear Self-Timed Transmission Buffer

Syntax:
CTB
Access level: USER

Clears the timed transmission buffer.
G.5.5 Load Random Transmission Buffer

Syntax:
RDT =xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Access level: USER

This command overwrites the GOES Random Buffer with the data provided.
The G5 transmitter will insert the 31 bit GOES ID, any header information
(e.g. HDR Flag byte), and append the EOT so these should not be included in
the RDT data. If the random data format is Pseudo-Binary the transmitter will
also insert the correct parity bit for each message character and replace illegal
characters with the character specified by the IRC=c command before
transmission.
Characters that have meaning for the command interface (CR, LF, BS,
ESC,’~’) must be preceded by a ‘~’ character if they appear in the message
data.
Loading data into the Random transmission buffer, triggers the random
reporting sequence. Once triggered, the random reporting mechanism will
send the data loaded in the buffer for the number of transmissions as specified
G-15
by the random repeat count. The buffer will be cleared automatically when the
number of transmissions specified have occurred.
If the command is received within 1 minute or during a random transmission

the data will not be included in the current transmission but will be buffered for
the next one.
If there is more data loaded into the buffer than can be transmitted at the
assigned bitrate the message will be truncated.
G.5.6 Read Length of the Message in the Random

Transmission Buffer
Syntax:
RML
Access level: USER

Returns the number of bytes stored in the random transmission buffer.
G.5.7 Read the Maximum Random Message Length

Syntax:
MRML
Access level: USER

Returns the maximum number of bytes that can be transmitted at the current
random transmission bitrate.
G.5.8 Clear Random Transmission Buffer

Syntax:
CRB
Access level: USER

Clear the random transmission buffer.
G.6 Status and Other Commands

The following commands are used by the host to determine the status of the
transmitter for display and diagnostics purposes. These commands can be
entered with transmissions enabled or disabled.
G-16
G.6.1 Read Version Information

Syntax:
VER
Access level: USER

This command returns the transmitter serial number, hardware version number,
firmware version number and GPS module version numbers.
G.6.2 Read Transmission Status

Syntax:
RST
Access level: USER

This command returns the transmitter state, GPS state, time to next
transmission, number of bytes in timed transmit buffer, number of bytes in
random transmit buffer, number of times random data has been transmitted,
failsafe status and supply voltage.
The transmitter responds with:
Transmitter: Enabled/Disabled[CR][LF]
GPS: On/Off[CR][LF]
RTC: Valid/Invalid[CR][LF]
Time To Next Tx: dd:hh:mm:ss[CR][LF]
Timed Message Length: nnnn[CR][LF]
Next Timed Tx: N/A or mm/dd/yyyy hh:mm:ss
Random Message Length: nnnn[CR][LF]
Random Message Tx Count: nnn[CR][LF]
Next Random Tx: N/A or mm/dd/yyyy hh:mm:ss
Fail-Safe: OK/Tripped[CR][LF]
Supply Voltage: xx.x V
G.6.3 Read Last Transmission Status

Syntax:
LTXS
Access level: USER

This command returns the status of the last transmission. The last transmission
could have been a regularly scheduled timed transmission, a random
transmission, or a test transmission triggered by a test command.
G-17
If a transmission has occurred since the unit was last powered up, the
transmitter responds to the command with:
Tx Status: Failsafe Tripped/OK

Tx Type: Timed/Random/Test
Last Tx Length: 30 bytes
Last Tx Start Time: 2004/12/16 23:29:48
Last Tx Stop Time: 2004/12/16 23:29:49
Forward Power: -23.1 dBm
Power Supply: 12.0 V
If a transmission has not occurred since power up, the transmitter will respond
with:
No Tx Has Occurred
G.6.4 Read GPS Status

Syntax:
GPS
Access level: USER

This command returns the current GPS status including satellite numbers and
signal strengths in the following format if the GPS is on:
Fix Status: Full Accuracy

Almanac Available: N
PPS Output Stable: N
UTC Offset = 0.000000
Satellite # Signal
Strength
30 10.80
23 no lock
10 4.00
25 1.80
5 6.60
21 no lock
17 6.40
2 6.80
If the GPS is off the command returns:
GPS is off
G-18
G.6.5 Read GPS Position

Syntax:
POS
Access level: USER

This command returns position obtained during the last GPS fix in the
following format:
Time of fix: dd/mm/yyyy hh:mm:ss[CR][LF]

Lat: sxx.xxxxx[CR][LF]
Long: sxxx.xxxxx[CR][LF]
Alt: xxxxx[CR][LF]>
Where latitude is in degrees, + for N and - for S, longitude is in degrees, + for

E and – for W and altitude is in meters.
If a GPS fix has not yet occurred the transmitter will respond with: No GPS
Fix[CR][LF]>
G.6.6 Read Audit Log

Syntax:
RAL
Access level: USER

The RAL command is used to retrieve the audit log information in the
following format:
yy/mm/dd hh:mm:ss event message 1[CR][LF]

yy/mm/dd hh:mm:ss event message 2 [CR][LF]
.
.
.
yy/mm/dd hh:mm:ss event message N[CR][LF]>
Where: yy/mm/dd hh:mm:ss are the date and time that the message was
created.
event message x is a short text string describing the event detected.
G.6.8 Read Forward Power

Syntax:
RFWD
Access level: USER

Returns the current forward power in dBm. This value is updated at the bit rate
when transmitting and every 30 seconds when not transmitting.
G-19
G.6.9 Read Reflected Power

Syntax:
RRFL
Access level: USER

Returns the reflected power in dBm. This value is updated at the bit rate when
transmitting and every 30 seconds when not transmitting.
G.6.10 Read Power Supply

Syntax:
RPS
Access level: USER

Returns the power supply voltage in Volts. This value is updated at the bit rate
when transmitting and every 30 seconds when not transmitting.
G.6.11 Read TCXO Temperature

Syntax:
RTEMP
Access level: USER

Returns the TCXO temperature (PCB temperature) in degrees C. This value is

updated at the bit rate when transmitting and every 30 seconds when not
transmitting.
G.6.12 Read Measured Frequency

Syntax:
RMF
Access level: TECHNICIAN

This command returns the last measured OCXO and TCXO frequencies in the
following format:
F-OCXO: 10000005.9000
F-TCXO: 43199.9166
Units are Hz.
G-20
Appendix H. GOES/Radio Set
Certification
H-1
Campbell Scientific Companies
Campbell Scientific, Inc. (CSI)

815 West 1800 North
Logan, Utah 84321
UNITED STATES
www.campbellsci.com • info@campbellsci.com
Campbell Scientific Africa Pty. Ltd. (CSAf)

PO Box 2450
Somerset West 7129
SOUTH AFRICA
www.csafrica.co.za • cleroux@csafrica.co.za
Campbell Scientific Australia Pty. Ltd. (CSA)

PO Box 444
Thuringowa Central
QLD 4812 AUSTRALIA
www.campbellsci.com.au • info@campbellsci.com.au
Campbell Scientific do Brazil Ltda. (CSB)

Rua Luisa Crapsi Orsi, 15 Butantã
CEP: 005543-000 São Paulo SP BRAZIL
www.campbellsci.com.br • suporte@campbellsci.com.br
Campbell Scientific Canada Corp. (CSC)

11564 - 149th Street NW
Edmonton, Alberta T5M 1W7
CANADA
www.campbellsci.ca • dataloggers@campbellsci.ca
Campbell Scientific Centro Caribe S.A. (CSCC)

300 N Cementerio, Edificio Breller
Santo Domingo, Heredia 40305
COSTA RICA
www.campbellsci.cc • info@campbellsci.cc
Campbell Scientific Ltd. (CSL)

Campbell Park
80 Hathern Road
Shepshed, Loughborough LE12 9GX
UNITED KINGDOM
www.campbellsci.co.uk • sales@campbellsci.co.uk
Campbell Scientific Ltd. (France)

Miniparc du Verger - Bat. H
1, rue de Terre Neuve - Les Ulis
91967 COURTABOEUF CEDEX
FRANCE
www.campbellsci.fr • info@campbellsci.fr
Campbell Scientific Spain, S. L.

Avda. Pompeu Fabra 7-9, local 1
08024 Barcelona
SPAIN
www.campbellsci.es • info@campbellsci.es
Please visit www.campbellsci.com to obtain contact information for your local US or International representative.

TX 312

Uploaded by

Copyright:

Available Formats

TX 312

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TX 312

Uploaded by

Copyright:

Available Formats

TX312 Transmitter

Products may not be returned without prior authorization. The following

To obtain a Returned Materials Authorization (RMA), contact Campbell

CAMPBELL SCIENTIFIC, INC.

3. TX312 Functions ..........................................................4

4. SatCommand Software ...............................................9

4.5.2.4 GPS Status .......................................................................... 12

5. Programming the Datalogger ...................................14

5.2.5.6 P127, Command 5: Clear TX312 Error Registers ..............32

6. Field Installation ........................................................35

A. Information on Eligibility and Getting Onto

B. Data Conversion Computer Program .................... B-1

C. Antenna Orientation Computer Program .............. C-1

D. RAWS-7 Data Format .............................................. D-1

E. GOES DCS Transmit Frequencies ......................... E-1

F. High Resolution 18-Bit Binary Format................... F-1

G. Extended ASCII Command Set ..............................G-1

H. GOES/Radio Set Certification ................................ H-1

The TX312 utilizes non-volatile memory to store configuration information,

TX312 supports the following certification standards:

• 300/1200 BPS DCPRS Certification Standard version 1.0b - March 2000

• CS I/O for Campbell dataloggers

The CS I/O port is a Campbell Scientific Synchronous Device for

NOTE The National Environmental Satellite, Data, and Information

On-board memory: Non-volatile flash for setup parameters. 16 kbytes for

2.2 NESDIS and Transmit−Windows

2.3 Data Retrieval

Data Collection Platform (DCP) Ground Receiving Station

FIGURE 2-1. Major Components of the GOES/DCP System

During transmission, the Transmitting LED will light.

3.2 Diagnostics Switch

The Failsafe circuit is designed to shut down a malfunctioning transmitter that

3.3 Communication Ports

3.3.2 CS I/O Port

3.3.3 SDI-12 Serial Port

3.4.2 GPS Connector

3.5 Power Connector

FIGURE 3-1. TX312 Label

FIGURE 3-2. TX312 Connectors

FIGURE 3-3. DCP Enclosure

4.1 Install SatCommand

4.2 SatCommand General Description

The Terminal window is used to manually enter commands to the transmitter.

4.3 Making Edits

4.3.2 Timed Channel

4.3.3 Timed Bit Rate

4.3.4 Timed Interval

4.3.5 First Timed Transmission

4.3.6 Timed Tx Window

4.3.7 Timed Msg Format

4.3.8 Random Channel

The Random Channel is the NESDIS assigned random transmission channel.

4.3.9 Random Bit Rate

4.3.10 Random Randomizing Interval

4.3.11 Random Randomizing Percentage

4.3.12 Random Repeat Count

4.3.13 Random Data Format

4.3.14 Random Msg Counter

4.4 Save and Transfer the Settings to the TX312