Campbell Scientific TX312 User Manual
TX312 Transmitter
Revision: 12/10
Copyright © 2000-2010
Campbell Scientific, Inc.
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
completed form must be either emailed to repair@campbellsci.com
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.
www.campbellsci.com/repair
. A
or faxed to
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
TX312 Transmitter Table of Contents
5. Programming the Datalogger ...................................14
5.1 CRBasic Programming........................................................................... 14
5.1.1 GoesData...................................................................................... 14
5.1.2 GoesStatus.................................................................................... 17
5.1.3 GoesGPS...................................................................................... 21
5.1.4 GoesSetup..................................................................................... 22
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.5 Read Status and Diagnostic Information from the TX312 ........... 28
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.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.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.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.4.1 Buffer Control..................................................................... 27
5.2.4.2 Data Format........................................................................ 27
5.2.4.3 P126 Result Codes.............................................................. 27
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
TX312 Transmitter Table of Contents
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
TX312 Transmitter Table of Contents
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:
NOTE
NOTE
• 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.
The 21X and CR7 dataloggers do not support SDC or the
TX312.
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
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.
TX312 Transmitter
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)
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
If there are data in a buffer waiting for transmission time, the Data In Buffer
LED will light.
During transmission, the Transmitting
The Fault
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.
LED will light.
LED will only light after the Diagnostics button has been depressed.
Ground Receiving Station
LED will light for 15 minutes.
4
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.
TX312 Transmitter
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
3.4.2 GPS 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.
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, driftfree 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
8
FIGURE 3-3. DCP Enclosure
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.
TX312 Transmitter
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
4.3.3 Timed Bit Rate
4.3.4 Timed Interval
4.3.5 First Timed Transmission
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.
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.
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.
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
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.
TX312 Transmitter
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
4.5 Using SatCommand for TX312 Testing
4.5.1 Terminal Window
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.
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
12
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.
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.
TX312 Transmitter
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
5.1.1.1 Result Code
5.1.1.2 Data Table
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.
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.
14
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
5.1.1.4 Buffer Control
5.1.1.5 Data Format
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.
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.
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
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.
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
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
TX312 Transmitter
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
5.1.2.2 GoesStatus Read Status
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
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
1 Command Result Code
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)
18
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.
TABLE 5.1-3. GoesStatus Command 2: Read Last Message Status
Index Contents
1 Command Result Code
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:
TX312 Transmitter
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
5 Command that Caused the Error
6 Error Code
7 Command that Caused the Error
8 Error Code
9 Command that Caused the Error
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.
5.1.3 GoesGPS
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.
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
5.1.4 GoesSetup
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 32bit 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.
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
5.1.4.1 Result Code
TX312 Transmitter
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
Loading...