SE100 ICD
Signal Engineering, Inc
INTERFACE CONTROL DOCUMENT
FOR
SE1200 and SE300
GOES HIGHER DATA RATE DCP TRANSMITTERS
With RS232 CONTROL INTERFACE
Signal Engineering, Inc.
6370 Lusk Blvd., Suite F206
San Diego, California
92121
(858)-552-8131
FAX: (858) 552-1429
Document No: 23800-4105
Document Revision: AD
Revision Date: June 26, 2003
DOCUMENT REVISION HISTORY
New Revision Date Changes In New Revision
AA 4-24-01 Changes versus ICD for SE120 GOES
100 BPS Transmitter:
1. Overview section summarizes 300 BPS and 1200 BPS operation, and operation with internal GPS receiver for setting transmitter time-of-day automatically.
2. Load Transmitter Time-of-Day and Display Transmitter Time-of-Day command sections describes operation with internal GPS receiver in detail.
3. Transmit command includes 2 new fields: Transmit Type Code (to select 100, 300, or 1200 BPS GOES transmission), and Interleaving Control. Additional notes for this command added to describe rules for 100, 300, 1200 BPS maximum transmission time, random transmissions, and channel frequencies.
4. Display Self-Test Results command includes 2 new Transmitter Type Codes for transmitters which support 100 and 300 BPS transmissions only, and transmitters which support 100, 300, and 1200 BPS transmissions.
5. Appendix E: GOES Data Collection System Transmit Frequencies added.
6. Descriptions of failsafe rules for 300 and 1200 BPS operation added to LED Indicator and Pushbutton Reset Switch sections.
7. Transmit Type Code field added to Send Fixed Channel command to allow selection of 100 BPS, 300 BPS, or 1200 BPS channel frequency and failsafe timeout interval.
8. GOES Message Format descriptions added.
AB 7-5-01 Changes from previous revision:
1. Get Status command description added.
AC 2-03-03 Changes from previous revision:
1. In Transmit command and Display Transmit Queue response descriptions, added GOES HDR Data Type field (allows user to specify ASCII or PsuedoBinary data in the Flagword field of GOES 300 and 1200 BPS transmissions).
AD 6-26-03 Changes from previous revision:
1. Added Power Interface and RF Interface sections with connector descriptions.
DOCUMENT REVISION HISTORY 3
1. SCOPE 1
1.1. PURPOSE 1
1.2. OVERVIEW 1
2. APPLICABLE DOCUMENTS 2
2.1. Government Documents 2
3. EXTERNAL INTERFACE DESCRIPTION 3
3.1. Control Interface 3
3.2. LED Indicator 6
3.3. Pushbutton Reset Switch 7
3.4 Power Interface 8
3.5 RF Interface 8
4. GOES DCP MESSAGE FORMATS 9
4.1. GOES DCP Operating Modes 9
4.1.1. Self-Timed Transmit Mode 9
4.1.2. Random Transmit Mode 9
4.2. GOES 100 BPS Message Format 9
4.3. GOES 300/1200 BPS Message Format 11
5. COMMAND AND RESPONSE DEFINITIONS 13
5.1. SE1200 Command/Response Type Code Summary 13
5.1.1. User Function Type Codes 13
5.1.2. Diagnostic Function Type Codes 13
5.1.3. Miscellaneous Type Codes 14
5.2. Response Status Code Summary 14
5.2.1. Generic Response Status Codes 14
5.2.2. Transmitter Error Response Status Codes 14
5.2.3. Transmitter Error Response 16
5.3. Transmitter Time and Date Functions 17
5.3.1. Display Transmitter Time-of-Day Command 17
5.3.2. Display Transmitter Time-of-Day Response 17
5.3.3. Load Transmitter Time-of-Day Command 19
5.3.4. Load Transmitter Time-of-Day Response 20
5.4. Transmitter Configuration Functions 21
5.4.1. Display Transmitter ID Command 21
5.4.2. Display Transmitter ID Response 21
5.4.3. Set Transmitter ID Command 22
5.4.4. Set Transmitter ID Response 23
5.4.5. Query Command 23
5.4.6. Query Response 24
5.4.7. Display Global Parameters Command 24
5.4.8. Display Global Parameters Response 25
5.4.9. Set Global Parameters Command 27
5.4.10. Set Global Parameters Response 28
5.5. Transmit Queue Management Functions 29
5.5.1. Transmit Command 29
5.5.2. Transmit Response 35
5.5.3. Display Transmit Queue Command 37
5.5.4. Display Transmit Queue Response( Transmit Parameters) 38
5.5.5. Display Transmit Queue Response( Data ) 40
5.5.6. Display Transmit Queue Response( Error Status) 41
5.5.7. Cancel Transmit Command 42
5.5.8. Cancel Transmit Response 43
5.6. Transmitter Diagnostic Functions 44
5.6.1. Reset Transmitter Command 44
5.6.2. Reset Transmitter Response 44
5.6.3. Initiate Self-Test Command 45
5.6.4. Initiate Self-Test Response 45
5.6.5. Display Self-Test Result Command 46
5.6.6. Display Self-Test Result Response 46
5.6.7. Send Fixed Channel Command 48
5.6.8. Send Fixed Channel Response 48
5.6.9. Display Version Information Command 49
5.6.10. Display Version Information Response 50
5.6.11. Get Status Command 51
5.6.12. Get Status Response 51
5.6.13. Software Load Command 53
5.6.14. Software Load Response 53
APPENDIX A: SE1200 COMMAND EXAMPLES 54
A.1 SE1200 INITIALIZATION/ CONFIGURATION 55
A.2 SCHEDULING A TRANSMISSION 56
APPENDIX B: Legal Data Characters: GOES 100/300/1200 BPS Self-Timed Transmissions 57
APPENDIX C: Legal Data Characters: GOES 100/300/1200 BPS Random Mode Transmissions 58
APPENDIX D: Legal Data Characters: GOES 100 BPS International Channel Transmissions 59
APPENDIX E: GOES Data Collection System Transmit Frequencies 60
SCOPE
PURPOSE
This document defines the protocol used to control the operation of Signal Engineering's SE1200 transmitter via its control interface. Except where noted, this interface description also applies to the Signal Engineering SE300 transmitter.
The document includes the electrical and physical interface requirements, as well as the interface's software protocol and packet structures.
OVERVIEW
The SE1200 transmitter supports the 100 BPS, 300 BPS and 1200 BPS transmission formats specified by NOAA for operation on the GOES satellite system. It incorporates an internal GPS receiver from which it automatically loads time-of-day. This is necessary to meet the DCP reporting time accuracy required for 1200 BPS operation.
The SE300 transmitter supports the 100 BPS and 300 BPS transmission formats specified by NOAA for operation on the GOES satellite system. It may be operated either with or without an internal GPS receiver. If no internal GPS receiver is present, time-of-day must be loaded via the command interface.
If an internal GPS receiver is present (required in all SE1200s, optional in SE300s), the transmitter will automatically load its time-of-day clock after power-on with time obtained from the GPS satellite system. It will then periodically update its time-of-day clock using the GPS receiver to ensure that accurate time is maintained. See the section of this document that describes the Load Transmitter Time-of-Day and Display Transmitter Time-of-Day commands for more details about operation with an internal GPS receiver.
The functions supported by the SE1200's host interface fall into three major categories:
1. Time-of-Day Functions: Monitoring and setting the SE1200's time-of-day clock.
2. Transmit Management Functions: Transmitting data to a satellite by controlling the SE1200's transmit queue. Items may be added to, deleted from, or examined on the transmit queue. Each transmit queue entry contains control parameters, including the time and date of transmission, the channel number, as well as the data to be transmitted.
3. SE1200 Diagnostic and Maintenance Functions: These functions include initiating and reviewing the status of the SE1200's Self-Test and sending continuous carrier on a specified channel for calibration purposes.
APPLICABLE DOCUMENTS
Government Documents
S23.010 SELF-TIMED DATA COLLECTION PLATFORM RADIO SET
(16Nov81) CERTIFICATION STANDARDS (Revised November 1981)
S23.012 RANDOM REPORTING DATA COLLECTION PLATFORM RADIO SET
(16Nov81) CERTIFICATION STANDARDS
(NESDIS) IDCS USER'S GUIDE; ANNEX 4
(None) CERTIFICATION SPECIFICATIONS
(NESDIS) VERSION 1.0B of the 300/1200 BPS GOES Data Collection Platform
(March 2000) Radio Set (DCPRS) CERTIFICATION STANDARDS
EXTERNAL INTERFACE DESCRIPTION
Control Interface
The control connector contains a interface through which control information, status information and data are passed to and from the SE1200. Table 1 lists the signal assignments for each pin on the connector.
|Table 1: Control Connector Description |
|Pin # |Signal |Signal Type |Description |
|1 | |NC |No Connect |
|2 |GND |Ground |Ground |
|3 | |NC |No Connect |
|4 |GND |Ground |Ground |
|5 | |NC |No Connect |
|6 |GND |Ground |Ground |
|7 | |RES |Reserved (Must be No Connect at host end) |
|8 | |RES |Reserved (Must be No Connect at host end) |
|9 | |RES |Reserved (Must be No Connect at host end) |
|10 | |RES |Reserved (Must be No Connect at host end) |
|11 |232RTS |Input |Request To Send, RS232 compatible |
|12 |232CTS |Output |Clear To Send, RS232 compatible |
|13 |232RXD |Input |Receive Data, RS232 compatible |
|14 |232TXD |Output |Transmit Data, RS232 compatible |
| |
|SE1200 Bulkhead Connector: |
|3M 2514-6002 (Low profile 14-pin box header) |
| |
|Mating Flat Cable Connector: |
|3M 3385-6600 (14-pin socket connector, open-ended for daisy-chaining) |
|or 3M 3385-7600 (14-pin socket connector, closed-ended for line termination) |
|3M 3448-3014 (Clip-on strain relief for 14-pin socket connector) |
ADDITIONAL NOTES:
1. Input signals are from the external host to the SE1200.
2. Output signals are from the SE1200 to the external host.
The following rules define the SE1200 Command/Response structure and protocol.
1. The physical control interface of the SE1200 consists of:
a) A Transmit Data (TXD) signal.
b) A Receive Data (RXD) signal.
c) A control signal (RTS) used by the external host to wake the SE1200 from low-power sleep mode.
d) A status signal (CTS) used by the SE1200 to indicate ready to receive commands.
e) A signal ground.
2. Data transmission is asynchronous using 1 stop bit, 8 data bits, and no parity at 9600 Baud.
3. All transactions between the external host and the SE1200 are of the command/response type. A command request packet is sent to the SE1200 by the host and the command response packet is sent back to the host by the SE1200. The SE1200 never sends unsolicited data to the host.
4. Before each command transaction, the host wakes the SE1200 from low-power sleep mode by asserting the RTS signal on the control interface. The SE1200 will be ready to receive a command packet within 12 milliseconds after the RTS signal is asserted by the host. When the SE1200 is ready to receive a command it will assert the CTS signal.
5. After asserting the RTS signal, before it sends a command to the SE1200, the host must EITHER:
a) Wait at least 12 milliseconds. OR
b) Wait until the SE1200 asserts the CTS signal.
6. The SE1200 will not return to low-power sleep mode as long as the host is asserting the RTS signal. After RTS is de-asserted, the SE1200 will return to low-power sleep mode if no other tasks need to be performed. The SE1200 will leave CTS asserted until the host de-asserts the RTS signal.
7. All packets begin with an ASCII SOH (01h) character, and are terminated with an ASCII EOT (04h) character. Each packet contains a Type Code field, an 8-bit checksum field, and a 1-byte reserved field.
8. The checksum field of each packet contains the 8-bit arithmetic sum (carry discarded) of all packet bytes following the SOH (start of packet) character and preceding the EOT (end of packet) character.
9. When a packet is transmitted, the SOH (01h) and EOT (04h) characters may appear only once each in each packet, at the start and end, respectively, of the packet. Any packet byte which contains a value of 01h, 04h, or 23h must be replaced with two characters before the packet is transmitted: an ASCII ‘#’ (23h) character, followed by the 1’s complement of the original byte value.
a) When a packet is received, the receiver re-constructs the original packet by replacing each pair of bytes whose first byte is an ASCII ‘#’ (23h) character, with the 1’s complement of the byte following the ‘#’ (23h) character.
10. The SE1200 will respond to any command sent by the host with a Transmitter Error Response packet if any of the following errors are detected:
a) A Command received from the Host is too long or too short.
b) The received Command contains an invalid Type Code.
c) The SE1200 is unable to allocate internal memory to perform the requested function.
11. In all other cases, the SE1200 will respond to Commands sent by the host computer with the particular Response defined for each function.
12. Any Command fields defined as “reserved” should be set to zero by the host.
3.2. LED Indicator
A single red LED indicator is mounted on the top edge of the transmitter Printed Wiring Board, next to the Pushbutton Reset switch.
|LED Indicator Blink Patterns |
|LED Blink Pattern |Description |
|(Immediately after power-on) |Power-up initialization started. |
| | |
|Blink ON, then OFF | |
|1 time. | |
|(Following single ON/OFF LED blink immediately|RS-232 control interface enabled (HSB control interface disabled). |
|after power-on) |Power-up initialization complete, ready to receive commands. |
| | |
|Blink ON, then OFF | |
|2 times. | |
|(Following single ON/OFF LED blink immediately|HSB control interface enabled (HSB control interface disabled). |
|after power-on) |Power-up initialization complete, ready to receive commands. |
| | |
|Blink ON, then OFF | |
|4 times. | |
|(Following a transmission) |The post-transmit interval is in progress. The transmitter will enter this state after its RF output|
| |is turned off either by a Reset command or by the normal completion of a data message transmission. |
|Blinking ON/OFF continuously for 60 seconds. |When the interval has elapsed after RF output is turned OFF, the LED will go OFF. |
| | |
| |If the transmitter’s RF output is turned ON again during this post-transmit interval via the Send |
| |Fixed Channel command, then a Failsafe condition will occur. |
| | |
| |For 100 BPS transmissions, the post-transmit interval is 60 seconds. |
| | |
| |For 300 BPS and 1200 BPS transmissions, the post-transmit interval is 30 seconds. |
|ON Continuously. |Failsafe condition has occurred. The Pushbutton Reset switch must be pushed to clear the condition. |
| |A power cycle or reset command will NOT clear this condition. |
| | |
| |OR |
| | |
| |A catastrophic error has occurred. The transmitter is not operable. |
3.3. Pushbutton Reset Switch
The Pushbutton Reset switch is located on the top edge of the transmitter’s Printed Wiring Board next to the LED indicator, and can be accessed through a hole in the top of the transmitter’s housing. The sole purpose of this switch is to clear a Failsafe condition.
Per NESDIS specification, GOES DCP transmitters must include a “Failsafe” feature that prevents continuous transmission. For 100 BPS transmissions, a DCP transmitter may not transmit continuously for more than 4.5 minutes and may not transmit again for 60 seconds after a transmission has completed.
For 300 BPS transmissions, a DCP transmitter may not transmit continuously for more than 4.5 minutes and may not transmit again for 30 seconds after a transmission has completed.
For 1200 BPS transmissions, a DCP transmitter may not transmit continuously for more than 105 seconds and may not transmit again for 30 seconds after a transmission has completed.
If the maximum continuous transmission time is exceeded, or if a transmission completes and a new transmission is attempted before the post-transmission “No Transmit” interval has elapsed, then the transmitter’s Failsafe feature is required to disable its RF output until it is manually cleared by a human operator.
The SE1200 transmitter will go into a Failsafe state if one of two events occur:
1. The transmitter’s RF output is turned on and left on for more than the maximum allowed transmit time.
2. The transmitter’s RF output is turned on again (via Send Fixed Channel command) before the specified interval has elapsed following any sort of transmission.
The transmitter’s software prevents normal self-timed or random data message transmissions from violating either of the Failsafe conditions. Unless a hardware failure occurs, the only way a Failsafe condition can happen is for the operator to cause the condition by manually turning on the RF output via the Send Fixed Channel command (to transmit unmodulated carrier).
If a Failsafe condition occurs, the transmitter’s LED indicator will be turned ON continuously, its microprocessor is reset, and its RF output is disabled. The only way to clear a Failsafe condition is for the operator to push the Pushbutton Reset switch. A power cycle or Reset command will NOT clear a Failsafe condition.
3.4 Power Interface
|Pin # |Signal |Description |
|1 |+12 Volts |11-15 Volt DC input (12-Volt nominal). |
|2 |12 Volt Return | |
|Mating Connector: |
|AMP Part Number: 1-480318-0 |
3.5 RF Interface
50 Ohm, SMA connector, male.
GOES DCP MESSAGE FORMATS
GOES DCP Operating Modes
Self-Timed Transmit Mode
Self-timed transmissions are made at scheduled times and are used for the reporting of data at regular intervals. Typically, self-timed mode Data Collection Platforms (DCPs) are assigned a transmission time slot of a certain length, beginning at a particular time offset after the start of each hour of the day, on the assigned channel.
Random Transmit Mode
Random mode transmissions are made at randomly distributed times within a transmission “window” of a chosen size on an assigned channel. Random mode transmissions are normally used for reporting events that may occur at any time and must be reported immediately. Typically, a channel is shared by many random mode DCPs, and message collisions are possible. Message delivery is guaranteed by keeping messages short, repeating each message several times, and transmitting each message at randomly chosen times within a specific transmission “window”.
GOES 100 BPS Message Format
Modulation for GOES 100 Bits Per Second (BPS) transmissions is Manchester encoded Binary Phase Shift Keying (BPSK). A data “0” consists of a +60 Degree carrier phase shift for 5 milliseconds, followed by a –60 Degree carrier phase shift for 5 milliseconds. A data “1” consists of a -60 Degree carrier phase shift for 5 milliseconds, followed by a +60 Degree carrier phase shift for 5 milliseconds. All phase shifts are relative to zero phase (i.e. unmodulated carrier). The message format is given below:
|Carrier |ALT 0/1 |MLS |BCH ID |Data |… |Data |EOT |
• Carrier: Unmodulated Carrier, used for frequency synchronization.
• ALT 0/1: Alternating ‘0’ and ‘1’ bits, used for bit timing synchronization.
• MLS: 15-bit Maximum Length Sequence, used for data character synchronization.
• BCH ID: 31-bit Bose-Chaudhuri-Hocquenghem (BCH) coded word that uniquely identifies the DCP.
• Data: 8-bit data characters, with Odd Parity in most-significant bit.
• EOT: End-Of-Transmission pattern (either 8-bit or 31-bit).
|Transmit |Carrier |Alternating |Maximum |Maximum |EOT |
|Type |Duration |0/1 Bits |#Data Bytes |Transmit Time |Pattern |
| | | |in each Transmit | |Length |
| | | |(Bytes) |(Minutes) | |
| |(Seconds) |(Bits) | | |(Bits) |
|Self-timed, |0.5 |49 |3342 |4.5 |8 |
|Short Preamble, | | | | | |
|Chan 1-199 | | | | | |
|Self-timed, |5.0 |241 |3259 |4.5 |8 |
|Long Preamble, | | | | | |
|Chan 1-199 | | | | | |
|Self-timed, |5.0 |241 |3259 |4.5 |31 |
|Chan 202-266 | | | | | |
|Random mode |0.5 |49 |3342 |4.5 |8 |
• Channel Frequencies: See Appendix E.
• Failsafe Requirements:
• Absolute maximum transmission time is 4.5 minutes.
• Minimum time between end of one transmission and start of next transmission is 60 seconds.
GOES 300/1200 BPS Message Format
Modulation for GOES 300 and 1200 Bits Per Second (BPS) transmissions is 8-ary Phase Shift Keying (8-ary PSK). Data is encoded into “symbols” that are represented by eight discrete carrier phase shifts: 0, 45, 90, 135, 180, 225, 270, and 315 Degrees. All phase shifts are relative to zero phase (i.e. unmodulated carrier). The message format is given below:
|Carrier |ALT 0/180 |FSS |BCH ID |Flagword |Data |EOT |Encoder Flush |
• Carrier: Unmodulated Carrier, used for frequency synchronization.
• ALT 0/180: Alternating 0 Degree and 180 Degree carrier phase shifts, used for symbol timing synchronization.
• FSS: 15-symbol Frame Synchronization Sequence, used to identify the interleaving type used for the message, and for randomizer/encoder/interleaver synchronization. One of three FSS patterns is sent, each consisting of a unique sequence of 0 Degree and 180 Degree carrier phase shifts. The three 15-bit FSS patterns are given below (where a ‘0’ bit represents a 0 Degree phase shift, and a ‘1’ represents a 180 Degree phase shift):
• 02CE (hex): No Interleaver used for message.
• 08E9 (hex): Short Interleaver used for message.
• 1F35 (hex): Long Interleaver used for message.
• BCH ID: 32-bit field containing a left-justified 31-bit Bose-Chaudhuri-Hocquenghem (BCH) coded word that uniquely identifies the DCP.
• Flagword: 8-bit field containing special flags:
• Bit 8: Odd Parity for the Flagword.
• Bit 7..6: 2-bit Data Format Code (01=ASCII, 11=Pseudo Binary).
• Bit 5: Spare, undefined.
• Bit 4: Reserved for possible future Data Compression.
• Bit 3: Reserved for possible future Reed Solomon Encoding.
• Bit 2: Clock updated since last transmission =1, not=0.
• Bit 1: Spare, undefined.
• Data: 8-bit data characters, with Odd Parity in most-significant bit.
• EOT: 8-bit End-Of-Transmission pattern.
• Encoder Flush: 16 bits of ‘0’s used to flush any remaining data from the Trellis encoder.
All message fields following the FSS field are converted to symbols by putting each 8 bits of the message through a randomizer and then through a convolutional encoder. Each 8 bits of the message is thus converted into 4 symbols. The randomizer is intended to make the spectral output independent of the data content of the message. The encoding done allows for some recovery from bit errors in the received message.
This system also supports block interleaving of the symbols in the message. A message may be sent using no interleaving, using a “short” interleaver of 384 symbols, or using a “long” interleaver of 768 symbols. Interleaving involves loading each block of N symbols (where N is the interleaver size) of the message into a two-dimensional array in a pre-defined order. Using the interleaver shuffles the order in which the symbols are transmitted, causing consecutive message symbols to be separated by some number of symbols, depending on the interleaver size.
The convolutional encoding used for the message can correct errors in single symbols, but not errors in multiple consecutive symbols. The advantage of using interleaving is that, if a burst of noise occurs that corrupts several consecutively transmitted symbols, after the message is de-interleaved by the receiver, the corrupted symbols are no longer consecutive, but separated by many symbols and can be individually corrected.
The disadvantage of using interleaving is that it usually requires longer transmissions than would be the case without interleaving. This is because the entire interleaver block must always be transmitted, and if the actual message data does not completely fill the interleaver block, the remaining space must filled with zeroes. There is also some question as to whether the sizes of the interleavers chosen for GOES will actually provide protection against the sources of errors which are likely to occur in the system.
|Transmit |Carrier |Alternating |Maximum |Maximum |EOT |
|Type |Duration |0/180 Symbols |#Data Bytes |Allowed |Pattern |
| | | |in each Transmit |Transmit Time |Length |
|(No interleaving) | |(Symbols) |(Bytes) |(Seconds) | |
| |(Seconds) | | | |(Bits) |
|Self-timed, |0.5 |3 |10055 |270 |8 |
|300 BPS | | | | | |
|Random mode, |0.5 |3 |80 |3.0 |8 |
|300 BPS | | | | | |
|Self-timed, |0.25 |3 |15512 |105 |8 |
|1200 BPS | | | | | |
|Random mode |0.25 |3 |174 |1.5 |8 |
|1200 BPS | | | | | |
• Channel Frequencies: See Appendix E.
• Failsafe Requirements:
• Absolute maximum transmission time is 4.5 minutes for 300 BPS, 1.75 minutes for 1200 BPS.
• Minimum time between end of one transmission and start of next transmission is 30 seconds for both 300 and 1200 BPS.
COMMAND AND RESPONSE DEFINITIONS
SE1200 Command/Response Type Code Summary
User Function Type Codes
The following table contains the type codes for all SE1200 commands and responses for "User" functions: functions performed as part of normal operation.
| |User Function Type Codes |
|10h |Display Transmitter ID |
|11h |Set Transmitter ID |
|13h |Load Transmitter Time-Of-Day |
|14h |Display Transmitter Time-Of-Day |
|16h |Cancel Transmit |
|17h |Display Transmit Queue |
|18h |Query |
|1Dh |Display Version Information |
|1Eh |Transmit |
Diagnostic Function Type Codes
The following table contains the type codes for all SE1200 commands and responses for Diagnostic functions: special functions used to calibrate, test, or troubleshoot the SE1200.
| |Diagnostic Function Type Codes |
|76h |Reset Transmitter |
|77h |Display Self-Test Result |
|78h |Initiate Self-Test |
|7Ah |Send Fixed Channel |
|7Ch |Software Load |
Miscellaneous Type Codes
The following table contains the type codes for SE1200 responses, which don't fall into any other category. The Transmitter Error Response packet is the SE1200's response to a corrupt or invalid Request packet from the host.
| |Miscellaneous Type Codes |
|F0H |Transmitter Error Response packet |
Response Status Code Summary
Generic Response Status Codes
The following table contains the SE1200 response status codes for general types of errors.
| |Generic Response Status Codes |
|00h |Operation Completed Successfully |
|01h |Rejected: Illegal Request |
|03h |Failed: Specified Item Not Found |
|04h |Rejected: Invalid Transmit Start Date/Time |
|05h |Rejected: Requested Transmit Overlaps Another Scheduled Transmit |
|06h |Rejected: Invalid Transmit Channel Number or Preamble Code |
|07h |Rejected: Invalid Random Transmit Interval |
|08h |Failed: EEPROM Update Error |
|09h |Rejected: Invalid Random Transmit Repeat Count |
|0Ah |Rejected: Time-of-Day Clock Not Loaded Yet |
|0Bh |Failed: CRC Error On Software Load Command Data |
Transmitter Error Response Status Codes
The following table contains the SE1200 response status codes, which may be returned in a Transmitter Error Response.
| |Transmitter Error Response Status Codes |
|01h |Received Command Too Long |
|02h |Received Command Too Short |
|03h |Received checksum is invalid |
|04h |Received command type code is invalid |
|06h |Unable To Allocate Memory For Operation |
Transmitter Error Response
Title : Transmitter Error Response.
Description : Reports errors detected in commands received from the Host.
Response : N/A.
|Transmitter Error Response |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |F0h |TYPE | Type Code |
|3 | |SS | Received Command Error Status |
| | | |01h = Command is too Long. |
| | | |02h = Command is too Short. |
| | | |03h = Invalid Checksum in received packet. |
| | | |04h = Illegal Type Code. |
| | | |06h = Unable To Allocate Memory For Operation. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. A Transmitter Error Response is returned by the SE1200 when the command received from the host contains errors indicating that the command may be corrupt.
Transmitter Time and Date Functions
Display Transmitter Time-of-Day Command
Title : Display Transmitter Time-of-Day Command
Description : Display Current Transmitter Time-of-Day.
Response : Display Transmitter Time-of-Day Response
|Display Transmitter Time-of-Day Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |14h |TYPE | Type Code |
|3 | |CS |Checksum |
|4 |04h |EOT |End of Packet |
Display Transmitter Time-of-Day Response
Title : Display Transmitter Time-Of-Day Response
Description : Returns the current Transmitter Time and Date and status for the command.
Response : N/A
|Display Transmitter Time-of-Day Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |14h |TYPE | Type Code |
|3 | |SS | Status |
| | | |00 = Completed OK |
| | | |0A = Time-of-day clock not loaded yet. |
|4 |00h |RES0 | Reserved |
|5 | |TOD6 | Current Year (Years since 1992) |
| | | |Range: (0...) |
| | | |Example: 1992 = 00h, 1993= 01h |
|6 | |TOD5 | Current Day (MSB) (Day=1 indicates Jan 1) |
| | | |Range: (1..365) or |
| | | |(1..366) In Leap Years |
| | | |Example: Jan 2 = 02h, Feb 1 = 20h |
|7 | |TOD4 | Current Day (LSB) |
|8 | |TOD3 | Current Hour |
| | | |Range: (0...23) |
|9 | |TOD2 | Current Minutes |
| | | |Range: (0...59) |
|10 | |TOD1 | Current Seconds |
| | | |Range: (0...59) |
|11 | |TOD0 | Current 1/10 Seconds |
| | | |Range: (0...9) |
|12 | |CS |Checksum |
|13 |04h |EOT |End of Packet |
|Examples: Current Data and Time Conversions |
|DATE |YEAR |DAY |HOUR |MINUTES |SECONDS |
| Feb 2,1992 |0 |33 |13 |20 |30 |
|1:20:30 PM | | | | | |
| Jan 1,2002 |10 |1 |0 |0 |0 |
|12:00:00 AM | | | | | |
ADDITIONAL NOTES:
1. If an internal GPS receiver is installed in the SE1200:
a) The SE1200’s time-of-day clock can only be loaded by time acquired from the GPS receiver. Load Time-of-Day commands will be accepted by the SE1200 and a status of Completed Ok (00h) will be returned in the response, but the SE1200 time-of-day clock will not be changed in any way by the command.
b) If time-of-day has not yet been acquired from GPS, Display Transmitter Time-of-Day responses will contain a status of Time-of-day Clock Not Loaded Yet (0Ah).
c) The SE1200 converts the time obtained from GPS to Coordinated Universal Time (i.e. UTC time). After it is loaded from GPS, the SE1200 time-of-day clock will always contain UTC time.
d) Transmit start times specified in commands must be given in UTC time.
e) Transmit start times that are returned in responses will be UTC times.
f) If the SE1200 time-of-day clock has not been loaded yet, the GPS receiver will left powered on continuously until time has been acquired.
g) The SE1200 relies on the stability of its high precision Temperature Compensated Crystal Oscillator (TCXO) to maintain the time accuracy required for GOES 1200 BPS operations for at least 1 week without adjustment. After the SE1200 has acquired time from GPS, it will power down the GPS receiver. At intervals of approximately 24 hours, it powers up the GPS receiver and attempts to acquire GPS time. If it succeeds, it will update the SE1200 time-of-day clock to ensure that it contains accurate UTC time. If the GPS receiver is unable to acquire time within 1 hour, it is powered down and another attempt is made approximately 24 hours later.
h) If the SE1200 is unable to acquire time from GPS for more than 7 consecutive days, its time-of-day clock will revert to a “Not Loaded Yet” state. The SE1200 will remain in this state (with the GPS receiver powered on continuously) until time is acquired again from GPS. In this state, transmissions are NOT permitted and the SE1200 will return a status of “Time-of-Day Clock Not Loaded Yet” in the responses to the Transmit command and the Display Time-of-Day command.
Load Transmitter Time-of-Day Command
Title : Load Transmitter Time-Of-Day Command
Description : Load transmitter's TOD clock with the Time and date.
Response : Load Transmitter Time-Of-Day Response
|Load Transmitter Time-of-Day Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |13h |TYPE | Type Code |
|3 |00h |RES0 | Reserved |
|4 | |TOD6 | New Year (Years since 1992) |
| | | |Years Range: (0...) |
| | | |Example: 1992= 00h, 1993= 01h |
|5 | |TOD5 | New Day (MSB) (Day=1 indicates Jan 1) |
| | | |Range: (1..365) or |
| | | |(1..366) In Leap Years |
| | | |Example: Jan 2 = 02h, Feb 1 = 20h |
|6 | |TOD4 | New Day (LSB) |
|7 | |TOD3 | New Hour |
| | | |Range: (0...23) |
|8 | |TOD2 | New Minutes |
| | | |Range: (0...59) |
|9 | |TOD1 | New Seconds |
| | | |Range: (0...59) |
|10 | |TOD0 | New 1/10 Seconds |
| | | |Range: (0...9) |
|11 | |CS |Checksum |
|12 |04h |EOT |End of Packet |
Load Transmitter Time-of-Day Response
Title : Load Transmitter Time-of-Day Response
Description : Returns status for Load Transmitter Time-of-Day Command.
Response : N/A
|Load Transmitter Time-of-Day Response |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |13h |TYPE | Type Code |
|3 | |SS | Transmitter Status. |
| | | |00 = Completed OK. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES:
1. If an internal GPS receiver is installed in the SE1200:
a) The SE1200’s time-of-day clock can only be loaded by time acquired from the GPS receiver. Load Time-of-Day commands will be accepted by the SE1200 and a status of Completed Ok (00h) will be returned in the response, but the SE1200 time-of-day clock will not be changed in any way by the command.
b) If time-of-day has not yet been acquired from GPS, Display Transmitter Time-of-Day responses will contain a status of Time-of-day Clock Not Loaded Yet (0Ah).
c) The SE1200 converts the time obtained from GPS to Coordinated Universal Time (i.e. UTC time). After it is loaded from GPS, the SE1200 time-of-day clock will always contain UTC time.
d) Transmit start times specified in commands must be given in UTC time.
e) Transmit start times that are returned in responses will be UTC times.
f) If the SE1200 time-of-day clock has not been loaded yet, the GPS receiver will left powered on continuously until time has been acquired.
g) The SE1200 relies on the stability of its high precision Temperature Compensated Crystal Oscillator (TCXO) to maintain the time accuracy required for GOES 1200 BPS operations for at least 1 week without adjustment. After the SE1200 has acquired time from GPS, it will power down the GPS receiver. At intervals of approximately 24 hours, it powers up the GPS receiver and attempts to acquire GPS time. If it succeeds, it will update the SE1200 time-of-day clock to ensure that it contains accurate UTC time. If the GPS receiver is unable to acquire time within 1 hour, it is powered down and another attempt is made approximately 24 hours later.
h) If the SE1200 is unable to acquire time from GPS for more than 7 consecutive days, its time-of-day clock will revert to a “Not Loaded Yet” state. The SE1200 will remain in this state (with the GPS receiver powered on continuously, trying to acquire time) until time is acquired again from GPS. In this state, transmissions are NOT permitted and the SE1200 will return a status of “Time-of-Day Clock Not Loaded Yet” in the responses to the Transmit command and the Display Time-of-Day command.
Transmitter Configuration Functions
Display Transmitter ID Command
Title : Display Transmitter ID Command
Description : Display current transmitter Platform ID.
Response : Display Transmitter ID Response
|Display Transmitter ID Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |10h |TYPE | Type Code |
|3 | |CTL | Control Field: |
| | | |00h = Display currently active GOES Platform ID. |
| | | |01h = Display default GOES Platform ID stored in |
| | | |EEPROM. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
Display Transmitter ID Response
Title : Display Transmitter ID Response
Description : Returns current platform ID and command status code.
Response : N/A
|Display Transmitter ID Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |10h |TYPE | Type Code |
|3 | |SS | Transmitter Status. 00 = Completed OK |
|4 | |ID3 | Platform ID (MSB) |
| | | | |
| | | |GOES: The Platform ID is a unique 31-bit BCH code that NESDIS assigns to each operational GOES |
| | | |Transmitter. |
| | | | |
| | | | |
| | | |For each type of platform ID, the ID is contained left-justified, zero filled to the right in the |
| | | |4-byte ID field. |
|5 | |ID2 | |
|6 | |ID1 | |
|7 | |ID0 |Platform ID (LSB) |
|8 | |CS |Checksum |
|9 |04h |EOT |End of Packet |
See the description of the Set Transmitter ID Command for an explanation of the two options allowed by the Control field in the DTID Command .
Set Transmitter ID Command
Title : Set Transmitter ID Command
Description : Set the Transmitter's Platform (BCH) ID.
Response : Set Transmitter ID Response .
|Set Transmitter ID Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |11h |TYPE | Type Code |
|3 | |CTL | Control Field: |
| | | |00h = Set the currently active GOES Platform ID |
| | | |equal to the contents of ID3..ID0, but don't |
| | | |overwrite the default GOES Platform ID in |
| | | |EEPROM. |
| | | |01h = Set the currently active GOES Platform ID |
| | | |equal to the contents of ID3..ID0 and |
| | | |overwrite the default GOES Platform ID in |
| | | |EEPROM with the contents of ID3..ID0. |
|4 | |ID3 | Platform ID (MSB) |
| | | | |
| | | |(See Additional Notes) |
|5 | |ID2 | |
|6 | |ID1 | |
|7 | |ID0 | Platform ID (LSB) |
|8 | |CS |Checksum |
|9 |04h |EOT |End of Packet |
ADDITIONAL NOTES
FOR ALL TYPES OF TRANSMITTERS:
1. A default Platform ID is stored in non-volatile memory. Typically, it is set once when the transmitter is installed and never changed. The Platform ID which is contained in the preamble sent with each transmission (i.e. the "currently active Platform ID") is set equal to the default Platform ID after a transmitter power cycle or a transmitter reset.
2. The new Platform ID should be set using the No-Update option (00h) in the STID Command Control Field if the user has a requirement to change the Platform ID frequently (if the transmitter is used as part of a test set, for example). This is because there is an upper limit on the number of times that the EEPROM used to store the default Platform ID can be updated.
3. If the no-update option (CTL=00h) is specified, the SE1200 will use the new Platform ID only until the next power cycle or reset, at which time the Platform ID will revert to the default ID saved in non-volatile storage.
FOR GOES:
1. The National Environmental Satellite, Data, and Information Service (NESDIS) is responsible for assigning the "Address Word" (or Platform ID) for each DCP in operation, and authorizing access to the GOES satellite.
2. The Platform ID consists of a 31 bit "Bose-Chaudhuri-Hocquenghem" code that is left justified in a 32-bit field with the Least Significant Bit set to zero. The Platform ID is issued by NESDIS as 8 hexadecimal characters representing the left justified 32-bit field. As an example, the Platform ID "01020304", corresponds to (0000 0001 0000 0010 0000 0011 0000 010 - MSB sent First). The contents of bytes ID0...3 would be ID3 = 01h, ID2 = 02h, ID1 = 03h, and ID0 = 04h.
Set Transmitter ID Response
Title : Set Transmitter ID Response
Description : Return status for the Set Transmitter ID command.
Response : N/A
|Set Transmitter ID Response |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |11h |TYPE | Type Code |
|3 | |SS | Transmitter Status. |
| | | |00h = Completed OK. |
| | | |08h = Failed: EEPROM Update Error. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. If EEPROM update fails, transmitter will use new Platform ID only until next transmitter power cycle or reset, at which time the Platform ID used will revert to the default ID stored in the EEPROM.
Query Command
Title : Query Command
Description : Interrogate transmitter to see if it is powered up.
Response : Query Response
|Query Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |18h |TYPE | Type Code |
|3 | |CS |Checksum |
|4 |04h |EOT |End of Packet |
Query Response
Title : Query Response
Description : Return the status for the Query command.
Response : N/A
|Query Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |18h |TYPE | Type Code |
|3 | |SS | Status. |
| | | |00h = Completed OK. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
Display Global Parameters Command
Title : Display Global Parameters Command.
Description : Display current transmitter global parameters.
Command: : N/A
|Display Global Parameters Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Ch |TYPE | Type Code |
|3 | |CS |Checksum |
|4 |04h |EOT |End of Packet |
Display Global Parameters Response
Title : Display Global Parameters Response.
Description : Return current transmitter global parameters.
Response : N/A
|Display Global Parameters Response |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Ch |Type | Type Code |
|3 | |SS | Status |
| | | |00h = Completed OK. |
|4 | |FREQOFF1 |Frequency Offset (0..500 Hz) (MSB) |
|5 | |FREQOFF0 |Frequency Offset (0..500 Hz) (LSB) |
|6 | |FRQOFFSIGN |Frequency Offset Sign Flag |
| | | |=00h: Positive Frequency Offset. |
| | | |=01h: Negative Frequency Offset. |
|7 | |RES0 |Reserved |
|... |... |... | ... |
|12 | |RES5 | Reserved |
|13 | |RCSF |Runtime Code Select flag: |
| | | |=01h: Load HSB Runtime Code Image. |
| | | |01h: Load RS232 Runtime Code Image. |
|14 | |RES7 |Reserved |
|... |... |... | ... |
|35 | |RES28 | Reserved |
|36 | |CS |Checksum |
|37 | |EOT |End of Packet |
ADDITIONAL NOTES
1. Frequency Offset is a 2-byte binary field containing the offset (0 to 500) in Hz (approximately) by which the transmit frequency will be corrected.
2. The transmitter software converts the value in the Frequency Offset field to a voltage which is applied (via a D/A Converter) to the frequency adjustment input of the transmitter’s Temperature Compensated Crystal Oscillator (TCXO). Since the exact frequency change versus voltage characteristic is slightly different for each TCXO, the value in the Frequency Offset is only an approximation of the actual frequency adjustment. To achieve a very precise frequency adjustment, the transmitter’s output frequency may need to be measured and the value in the Frequency Offset field modified several times before a final value is arrived at.
3. The sign of the frequency correction applied is determined by the contents of the Frequency Offset Sign Flag field:
=00h : Positive Frequency Offset. Transmit frequency will be INCREASED by the number of Hz (approximately) specified in the Frequency Offset field.
=01h : Negative Frequency Offset. Transmit frequency will be DECREASED by the number of Hz (approximately) specified in the Frequency Offset field.
4. Runtime Code Select Flag is a 1-byte binary field whose value determines which of the two runtime software images is loaded after power-up:
=01h: HSB runtime software image is loaded after power-up. If this software image is selected, then after the next power cycle, the transmitter will only respond to its HSB interface. To enable the RS232 interface and disable the HSB interface, set the Runtime Code Select Flag = 00h (or any value other than 01h) using the Set Global Parameters command, then cycle the power to the transmitter.
01h: RS232 runtime software image is loaded after power-up if Runtime Code Select Flag contains any value other than 01h. If this software image is selected, then after the next power cycle, the transmitter will only respond to its RS232 interface. To enable the HSB interface and disable the RS232 interface, set the Runtime Code Select Flag = 01h using the Set Global Parameters command, then cycle the power to the transmitter.
WARNING! Make sure that you don’t change the state of this field unless you really want to select the other command interface.
Set Global Parameters Command
Title : Set Global Parameters Command.
Description : Set transmitter global parameters.
Command : N/A
|Set Global Parameters Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Bh |Type | Type Code |
|3 | |FREQOFF1 |Frequency Offset (0..500 Hz) (MSB) |
|4 | |FREQOFF0 |Frequency Offset (0..500 Hz) (LSB) |
|5 | |FRQOFFSIGN |Frequency Offset Sign Flag |
| | | |=00h: Positive Frequency Offset. |
| | | |=01h: Negative Frequency Offset. |
|6 | |RES0 |Reserved |
|... |... |... | ... |
|11 | |RES5 | Reserved |
|12 | |RCSF |Runtime Code Select flag: |
| | | |=01h: Load HSB Runtime Code Image. |
| | | |01h: Load RS232 Runtime Code Image. |
|13 | |RES7 |Reserved |
|... |... |... | ... |
|34 | |RES28 | Reserved |
|35 | |CS |Checksum |
|36 | |EOT |End of Packet |
ADDITIONAL NOTES
1. Frequency Offset is a 2-byte binary field containing the offset (0 to 500) in Hz (approximately) by which the transmit frequency will be corrected.
2. The transmitter software converts the value in the Frequency Offset field to a voltage which is applied (via a D/A Converter) to the frequency adjustment input of the transmitter’s Temperature Compensated Crystal Oscillator (TCXO). Since the exact frequency change versus voltage characteristic is slightly different for each TCXO, the value in the Frequency Offset is only an approximation of the actual frequency adjustment. To achieve a very precise frequency adjustment, the transmitter’s output frequency may need to be measured and the value in the Frequency Offset field modified several times before a final value is arrived at.
3. The sign of the frequency correction applied is determined by the contents of the Frequency Offset Sign Flag field:
=00h : Positive Frequency Offset. Transmit frequency will be INCREASED by the number of Hz (approximately) specified in the Frequency Offset field.
=01h : Negative Frequency Offset. Transmit frequency will be DECREASED by the number of Hz (approximately) specified in the Frequency Offset field.
4. Runtime Code Select Flag is a 1-byte binary field whose value determines which of the two runtime software images is loaded after power-up:
=01h: HSB runtime software image is loaded after power-up. If this software image is selected, then after the next power cycle, the transmitter will only respond to its HSB interface. To enable the RS232 interface and disable the HSB interface, set the Runtime Code Select Flag = 00h (or any value other than 01h) using the Set Global Parameters command, then cycle the power to the transmitter.
01h: RS232 runtime software image is loaded after power-up if Runtime Code Select Flag contains any value other than 01h. If this software image is selected, then after the next power cycle, the transmitter will only respond to its RS232 interface. To enable the HSB interface and disable the RS232 interface, set the Runtime Code Select Flag = 01h using the Set Global Parameters command, then cycle the power to the transmitter.
WARNING! Make sure that you don’t change the state of this field unless you really want to select the other command interface.
Set Global Parameters Response
Title : Set Global Parameters Response.
Description : Returns Status from the Set Global Parameters Command.
Response : N/A
|Set Global Parameters Response |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Bh |Type | Type Code |
|3 | |SS | Status |
| | | |00h = Completed OK. |
| | | |08h = Failed: EEPROM Update Error. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
Transmit Queue Management Functions
Transmit Command
Title : Transmit Command
Description : Contains the control parameters for the transmission and the data bytes to be transmitted.
Response : Transmit Response
|Transmit Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Eh |TYPE | Type Code |
|3 | |FLAGS | Control Flags |
| | | |BIT7 : Transmission Mode Control |
| | | |= 0 Self-Timed Mode: Transmission occurs at |
| | | |the time specified in the Transmit Start Time |
| | | |field. |
| | | | |
| | | |= 1 Random Mode: The SE1200 will transmit |
| | | |this message at a random starting time |
| | | |within the specified random transmit |
| | | |interval. |
| | | | |
| | | |BITS[2:0] : Random Transmit Repeat Count |
| | | |Range: ( 1...3) |
| | | |(the number of times within the specified random |
| | | |transmit interval that the transmitter will |
| | | |transmit the message data at a different |
| | | |randomly generated transmit start time) |
|4 | |TOD7 | Not used for self-timed transmissions |
|5 | |TOD6 | Transmit Start Time( Year) |
| | | |(Number of years since 1992) |
| | | |Range: (0...) |
| | | | |
| | | |Example: 1993 = 01h |
|6 | |TOD5 | Transmit Start Time( Day)(MSB) |
| | | |(Day=1 indicates Jan 1) |
| | | |Day Range: ( 1...365) or |
| | | |( 1...366) In Leap Years |
| | | | |
| | | |Example: Jan 2 = 02h, Feb 1 = 20h |
|7 | |TOD4 | Transmit Start Time( Day ) (LSB) |
|8 | |TOD3 | Transmit Start Time( Hour) |
| | | |Range ( 0...23) |
|9 | |TOD2 | Transmit Start Time( Minute) |
| | | |Range ( 0...59) |
|10 | |TOD1 | Transmit Start Time( Second) |
| | | |Range ( 0...59) |
|11 |00h |RES0 | Reserved |
|12 | |TAG15 | Tag field (MSB) |
| | | |The TAG field is NOT transmitted, but is provided |
| | | |for user identification of transmit queue entries. |
| | | |Typically, the field contains the filename for |
| | | |the data to be transmitted. |
|.. |... |... | ... |
|27 | |TAG0 | Tag Field (LSB) |
|28 | |PC |GOES 100 BPS: |
| | | |Transmit Preamble Code: |
| | | |00 = Short Preamble (1.44 sec.) |
| | | |(Random or Self Timed Transmissions) |
| | | | |
| | | |01 = Long Preamble (7.76 sec.) |
| | | |(Self Timed Transmissions only) |
| | | | |
| | | | |
| | | |GOES 300 and 1200 BPS: Not used. |
|29 | |CN1 | Transmit Channel Number (MSB) |
| | | |GOES 100 BPS and 300 BPS: |
| | | |1 to 266 : GOES 100/300 BPS Channels |
| | | | |
| | | |GOES 1200 BPS: |
| | | |1 to 133 : GOES 1200 BPS Channels |
| | | | |
| | | |NOTE: For GOES 100 BPS transmissions in the channel range 202 to 266, only even-numbered channels |
| | | |are allowed, and the transmissions are formatted according to the IDCS (International channel) |
| | | |standard for 100 BPS DCP operation on GOES satellites. For GOES 300 BPS transmissions, all channels |
| | | |in the range 1-266 are allowed. See Appendix E for channel frequency details. |
|30 | |CN0 | Transmit Channel Number (LSB) |
|31 | |DATALEN1 | Transmit Data Length (MSB) |
| | | |(Specifies the number of data bytes to be transmitted, contained in command byte positions 64... |
| | | |N+63) |
|32 | |DATALEN0 | Transmit Data Length (LSB) |
|33 | | |Transmit Type Code |
| | | |(Selects type of transmission to be made) |
| | | |00 = GOES 100 BPS transmission. |
| | | |01 = GOES 300 BPS transmission. |
| | | |02 = GOES 1200 BPS transmission. |
|34 | | |Interleaving Control |
| | | |GOES 100 BPS: Not used. |
| | | | |
| | | |GOES 300 and 1200 BPS: |
| | | |00 = No interleaving |
| | | |01 = Short interleaver used. |
| | | |02 = Long interleaver used. |
| | | | |
| | | |NOTE: Although interleaving is supported by the GOES Higher Data Rate (300 and 1200 BPS) |
| | | |transmission format, there is normally NO REASON to use interleaving for DCP transmissions. This |
| | | |control field is provided in so that it can be enabled for very special applications. For all other |
| | | |cases, set this field = 00 (No interleaving). |
|35 | | |Reserved |
|36 | | | Data Type |
| | | |GOES 100 BPS: Not used. |
| | | | |
| | | |GOES 300 and 1200 BPS: |
| | | |00 = ASCII data. |
| | | |01 = Psuedo Binary data. |
| | | | |
| | | |NOTES: |
| | | |This field causes the 2-bit Data Type field in the 8-bit GOES HDR Flagword to be set to the proper |
| | | |value for the specified data type. It has no other effect. The transmission type (i.e. Self-Timed or|
| | | |Random) specified by Transmit Data Command FLAGS field Bit7 determines which type of data (ASCII or |
| | | |Psuedo Binary) that the transmitter will consider legal for the transmission when it screens the |
| | | |user’s data for illegal character values. |
| | | |If a Random transmission is specified (i.e. Transmit Data command FLAGS field Bit7=1), the |
| | | |transmitter will force the data type to be Psuedo Binary in the GOES HDR Flagword. |
| | | |If this Data Type field is set to a value other than one of the legal values specified above, the |
| | | |transmitter will force the data type to be ASCII in the GOES HDR Flagword. |
|37 | | |Reserved |
|.. |.. |... |... |
|63 | | | Reserved |
|64 | |DATA1 | Transmit Data Byte1 |
|.. |.. |... |... |
|N+63 | |DATAN | Transmit Data ByteN |
|N+ | |CS |Checksum |
|64 | | | |
|N+65 |04h |EOT |End of Packet |
ADDITIONAL NOTES
GOES 100 BPS, 300 BPS, and 1200 BPS:
1. There are two separate sets of transmit frequencies used by the GOES data collection system, those used for 100 or 300 BPS transmissions (identified as GOES 100/300 BPS Channel 1-266), and those used for 1200 BPS transmissions (identified as GOES 1200 BPS Channel 1-133). See Appendix E: GOES Data Collection System Transmit Frequencies for a detailed list of channel number versus frequency for each of the three data rates.
2. If the Transmit Data Length specified is equal to zero, then the Transmit Data command should not include any data bytes (i.e. Transmit Data Byte1..N). In this case, the transmission made will consist of just the specified transmission preamble and End-Of-Transmission pattern.
3. "Random Transmission" refers to a mode of transmission which conforms to the NESDIS RANDOM REPORTING DCP RADIO SET Certification standard. For random transmissions, the Repeat Count specifies the number of times that the same downloaded data is to be transmitted within the specified interval. The SE1200 will automatically compute/find up to three random transmission start times within the specified interval which don't overlap or fall within the "No Transmit Allowed" delay interval at the end of any other scheduled transmissions.
4. For random mode transmissions, the TOD7-TOD0 field defines the Random Transmission Interval Start Time and Random Transmission Interval Length for the transmission(s) to be attempted as follows:
HH:MM:SS.
TOD7-TOD4: Random Transmit Interval
TOD7 = Number of Hours in the Interval.
TOD6 = Number of Minutes in the Interval.
TOD5 = Number of Seconds in the Interval.
TOD4 = Not used.
TOD3-TOD0: Random Transmit Interval Start Time
T0D3 = Random Trans. Interval Start Time( Hour)
TOD2 = Random Trans. Interval Start Time( Minute)
TOD1 = Random Trans. Interval Start Time( Seconds)
TOD0 = Not Used
5. The Random Transmit Interval is assumed to start at the specified time on the current day, unless the specified start time has already passed, in which case it is assumed to start at the specified time on the day after the current day.
6. A Random Transmission Interval may be specified which crosses the boundary between the current day and the following day. For example, if the current day is JAN 1, the random starting time is 23:00:00, and the Interval is 2 hours (02:00:00), then the random transmit window will occur between JAN 1, 23:00:00 and JAN 2, 00:59:59.
7. The DATA field contains the actual data to be transmitted to the satellite.
8. Data Transmission Order:
a) Data bytes are transmitted in the order in which they are received from the host.
9. Each byte in the DATA Field contains one 7-bit ASCII character plus a parity bit. The SE1200 forces ODD parity into the most significant bit of each byte of data before transmitting the byte (per NESDIS), so it is not necessary for the host to generate and include parity in each of the transmit data bytes before downloading the data into the transmitter.
10. The following ASCII control characters are NOT allowed in a DCP message: DLE(10h), NAK(15h), SYN(16h), ETB(97h), CAN(98h), GS(9Dh), RS(9Eh), SOH(01h), STX(02h), ETX(83h), ENQ(85h), ACK(86h), and EOT(04h). The SE1200 translates any illegal character encountered in the transmit data into a '/' (ASCII(2Fh)) character before transmitting the data.
GOES 100 BPS Only:
1. Data Transmission Order:
a) Each data byte is transmitted least significant bit first.
2. The SE1200 forces all random mode transmissions to use the short transmission preamble (per the NESDIS standard).
3. The duration of all GOES 100 BPS transmissions must be less than 4 minutes and 30 seconds. The SE1200 will terminate all transmissions with the End-of-Transmission pattern before the duration of the transmission reaches 4 minutes and 30 seconds.
a) Maximum number of data bytes that may be transmitted at 100 BPS with Short Preamble = 3342 Data Bytes.
b) Maximum number of data bytes that may be transmitted at 100 BPS with Long Preamble = 3259 Data Bytes.
4. At the selected transmit start date/time, the SE1200 transmits the preamble (Short/Long) selected, followed by the data in the TRANSMIT DATA field, followed by the required EOT pattern. (Note: the SE1200 always terminates a Message with the EOT pattern required for the specified transmit channel: 1-byte EOT for domestic GOES channels, 4-byte IDCS EOT pattern for international channels).
5. The SE1200 will not permit another transmission to be made for 60 seconds following the transmission of the last bit of the End-Of-Transmission (EOT) pattern (per the NESDIS standard). The SE1200 transmit queue entry for each just-completed transmission will not be purged until after this 60 second post-transmission interval has elapsed.
GOES 300 BPS Only:
1. The duration of all GOES 300 BPS self-timed transmissions must be less than 270 seconds. The maximum number of data bytes that may be transmitted in a self-timed transmission at 300 BPS is 10055 Data Bytes.
2. At the specified transmit start date/time, the SE1200 transmits the preamble, followed by the data in the TRANSMIT DATA field, followed by the required EOT pattern.
3. The SE1200 will not permit another transmission to be made for 30 seconds following the completion of any 300 BPS transmission (per the NESDIS standard). The SE1200 transmit queue entry for each just-completed transmission will not be purged until after this 30 second post-transmission interval has elapsed.
4. The duration of all GOES 300 BPS random transmissions must be less than 3 seconds. Interleaving is not allowed for random transmissions. The maximum number of data bytes that may be transmitted BPS in a random transmission at 300 BPS is 80 Data Bytes.
GOES 1200 BPS Only:
1. The duration of all GOES 1200 BPS self-timed transmissions must be less than 105 seconds. The maximum number of data bytes that may be transmitted in a self-timed transmission at 1200 BPS is 15512 Data Bytes.
2. At the specified transmit start date/time, the SE1200 transmits the preamble, followed by the data in the TRANSMIT DATA field, followed by the required EOT pattern.
3. The SE1200 will not permit another transmission to be made for 30 seconds following the completion of any 300 BPS transmission (per the NESDIS standard). The SE1200 transmit queue entry for each just-completed transmission will not be purged until after this 30 second post-transmission interval has elapsed.
4. The duration of all GOES 1200 BPS random transmissions must be less than 1.5 seconds. Interleaving is not allowed for random transmissions. The maximum number of data bytes that may be transmitted BPS in a random transmission at 1200 BPS is 174 Data Bytes.
Transmit Response
Title : Transmit Response
Description : Returns the status for the Transmit command.
Response : N/A
|Transmit Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Eh |TYPE | Type Code |
|3 | |SS | Status |
| | | |00h = Completed OK. |
| | | |01h = Illegal Command. |
| | | |04h = Rejected: Invalid Transmit Start Time. |
| | | |05h = Rejected: Transmit Overlaps Another |
| | | |Scheduled Transmit. |
| | | |06h = Rejected: Invalid Transmit Channel Number |
| | | |or Preamble Code. |
| | | |07h = Rejected: Invalid Random Transmit Interval. |
| | | |09h = Rejected: Invalid Random Transmit Repeat |
| | | |Count Value. |
| | | |0Ah = Rejected: Transmitter Time Not Loaded Yet. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
Display Transmit Queue Command
Title : Display Transmit Queue Command
Description : Displays transmit parameters, or the data to be transmitted for the specified transmit queue entry.
Response : Display Transmit Queue Response
|Display Transmit Queue Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |17h |TYPE | Type Code |
|3 | |QE | Transmit Queue Entry Number |
| | | |(1...N, for N transmit queue entries) |
|4 | |QPN | Transmit Queue Entry Page Number field |
| | | |Bit[7]: Queue Entry Page Section Select Flag |
| | | |= 0: 1st half of QE page. |
| | | |= 1: 2nd half of QE page. |
| | | |Bit[6:0]: QE Page Number |
| | | |= 01: Transmit Parameters of QE. |
| | | |= 02...N: A page (240 bytes max) of |
| | | |transmit data. |
| | | | |
| | | |NOTE: |
| | | |For transmit queue entry data pages containing data to be transmitted (i.e. QE pages 02..N), Bit[7]|
| | | |Queue Entry Page Section Select Flag specifies which half of the QE page is to be displayed. |
| | | | |
| | | |If the 1st half of QE page is selected, then up to 120 bytes of data, starting with the 1st byte of|
| | | |data in the page, are returned in the response. |
| | | | |
| | | |If the 2nd half of QE page is selected, then up to 120 bytes of data, starting with the 121st byte |
| | | |of data in the page, are returned in the response. |
| | | | |
| | | |This feature allows all data contained in any transmit queue entry to be displayed/retrieved for |
| | | |test purposes. |
| | | | |
| | | |If QE Page Number = 01 (i.e. 1st page of transmit QE), then Bit[7] Queue Entry Page Section Select |
| | | |Flag is ignored, and only the defined transmission parameter information (contained in the 1st QE |
| | | |page) is returned in the response. |
|5 | |CS |Checksum |
|6 |04h |EOT |End of Packet |
Display Transmit Queue Response( Transmit Parameters)
Title : Display Transmit Queue Response( Transmit Parameters)
Description : Displays transmit parameters for the specified transmit queue entry. This is the format of the response to a Display Transmit Queue Command with Queue Page Number = 01h.
|Display Transmit Queue Response( Transmit Parameters) |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |17h |TYPE | Type Code |
|3 | |SS | Status = 00h (Completed OK) |
|4 | |NFP | Number of free pages (240 transmit data bytes/page) available in transmitter memory. |
|5 | |FLAGS | Control Flags |
| | | |BIT7 : Transmission Mode Control |
| | | |= 0 Self-Timed Mode: Transmission occurs at |
| | | |the time specified in the Transmit Start Time. |
| | | | |
| | | |= 1 Random Mode: The SE1200 will transmit |
| | | |this message at a random starting time |
| | | |within the specified random transmit |
| | | |interval . |
| | | | |
| | | |BITS[2:0] : Random Transmit Repeat Count |
| | | |Range: ( 1...3) |
| | | |(the number of times within the specified random |
| | | |transmit interval that the transmitter will |
| | | |transmit the message data at a different |
| | | |randomly generated transmit start time) |
|6 |00h |RES0 | Reserved |
|7 | |TOD6 | Transmit Start Time( Year) |
| | | |(Number of years since 1992) |
| | | |Range: (0...) |
| | | | |
| | | |Example: 1993 = 01h |
|8 | |TOD5 | Transmit Start Time( Day)(MSB) |
| | | |(Day=1 indicates Jan 1) |
| | | |Day Range: ( 1...365) or |
| | | |( 1...366) In Leap Years |
| | | | |
| | | |Example: Jan 2 = 02h, Feb 1 = 20h |
|9 | |TOD4 | Transmit Start Time( Day ) (LSB) |
|10 | |TOD3 | Transmit Start Time( Hour) |
| | | |Range ( 0...23) |
|11 | |TOD2 | Transmit Start Time( Minute) |
| | | |Range (0...59) |
|12 | |TOD1 | Transmit Start Time( Second) |
| | | |Range ( 0...59) |
|13 |00h |RES1 | Reserved |
|14 | |TAG15 | Tag field (MSB) |
| | | |The TAG field is NOT transmitted, but is provided |
| | | |for user identification of queue entries. |
| | | |Typically, the host loads this field with the |
| | | |filename for the transmit data. |
|.. |... |... | ... |
|29 | |TAG0 | Tag Field (LSB) |
|30 | |PC |GOES 100 BPS: |
| | | |Transmit Preamble Code: |
| | | |00 = Short Preamble (1.44 sec.) |
| | | |(Random or Self Timed Transmissions) |
| | | | |
| | | |01 = Long Preamble (7.76 sec.) |
| | | |(Self Timed Transmissions only) |
| | | | |
| | | | |
| | | |GOES 300 and 1200 BPS: Not used. |
|31 | |CN1 | Transmit Channel Number (MSB) |
| | | |GOES 100 BPS and 300 BPS: |
| | | |1 to 266 : GOES 100/300 BPS Channels |
| | | | |
| | | |GOES 1200 BPS: |
| | | |1 to 133 : GOES 1200 BPS Channels |
| | | | |
| | | |NOTE: For GOES 100 BPS transmissions in the channel range 202 to 266, only even-numbered channels |
| | | |are allowed, and the transmissions are formatted according to the IDCS (International channel) |
| | | |standard for 100 BPS DCP operation on GOES satellites. For GOES 300 BPS transmissions, all channels |
| | | |in the range 1-266 are allowed. See Appendix E for channel frequency details. |
|32 | |CN0 | Transmit Channel Number (LSB) |
|33 | |DATALEN1 | Transmit Data Length (MSB) |
|34 | |DATALEN0 | Transmit Data Length (LSB) |
|35 | | |Transmit Type Code |
| | | |(Selects type of transmission to be made) |
| | | |00 = GOES 100 BPS transmission. |
| | | |01 = GOES 300 BPS transmission. |
| | | |02 = GOES 1200 BPS transmission. |
|36 | | |Interleaving Control |
| | | |GOES 100 BPS: Not used. |
| | | | |
| | | |GOES 300 and 1200 BPS: |
| | | |00 = No interleaving |
| | | |01 = Short interleaver used. |
| | | |02 = Long interleaver used. |
| | | | |
| | | |NOTE: Although interleaving is supported by the GOES Higher Data Rate (300 and 1200 BPS) |
| | | |transmission format, there is normally NO REASON whatsoever to use interleaving for DCP |
| | | |transmissions. This control field is provided in so that it can be enabled for very special |
| | | |applications. For all other cases, set this field = 00 (No interleaving). |
|37 | | | Reserved |
|38 | | | Data Type |
| | | |GOES 100 BPS: Not used. |
| | | | |
| | | |GOES 300 and 1200 BPS: |
| | | |00 = ASCII data. |
| | | |01 = Psuedo Binary data. |
| | | | |
| | | |NOTES: |
| | | |This field causes the 2-bit Data Type field in the 8-bit GOES HDR Flagword to be set to the proper |
| | | |value for the specified data type. It has no other effect. The transmission type (i.e. Self-Timed or|
| | | |Random) specified by Transmit Data Command FLAGS field Bit7 determines which type of data (ASCII or |
| | | |Psuedo Binary) that the transmitter will consider legal for the transmission when it screens the |
| | | |user’s data for illegal character values. |
| | | |If a Random transmission is specified (i.e. Transmit Data command FLAGS field Bit7=1), the |
| | | |transmitter will force the data type to be Psuedo Binary in the GOES HDR Flagword. |
| | | |If this Data Type field is set to a value other than one of the legal values specified above, the |
| | | |transmitter will force the data type to be ASCII in the GOES HDR Flagword. |
|39 | | | Reserved |
|.. |... |... |... |
|65 | | | Reserved |
|66 | |CS |Checksum |
|67 |04h |EOT |End of Packet |
Display Transmit Queue Response( Data )
Title : Display Transmit Queue Response( Data)
Description : Returns a page (1...240 bytes) of data to be transmitted from the specified transmit queue entry. This is the format of the response to a Display Transmit Queue Command with Queue Page Number = 02...N.
Response : N/A
|Display Transmit Queue Response (Data) |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |17h |TYPE | Type Code |
|3 | |SS | Status |
| | | |00h = Completed OK |
|4 | |DATA1 | Data Byte1 |
|... |... |... | ... |
|N+2 | |DATAN | Data Byte N |
|N+2 | |CS |Checksum |
|N+2 |04h |EOT |End of Packet |
Display Transmit Queue Response( Error Status)
Title : Display Transmit Queue Response( Error Status)
Description : Returns the status for a Display Transmit Queue Command in the event that the Command cannot be completed.
Response : N/A
|Display Transmit Queue Response (Error Status) |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |17h |TYPE | Type Code |
|3 | |SS | Status |
| | | |03h = Specified Transmit Queue Entry or Queue Entry |
| | | |Page Not Found. |
|4 | |NFP |Number of free pages (240 transmit data bytes/page) available in transmitter memory. |
|5 | |CS |Checksum |
|6 |04h |EOT |End of Packet |
Cancel Transmit Command
Title : Cancel Transmit Command
Description : Cancels a scheduled transmission, specified by its transmit start time.
Response : Cancel Transmit Response
|Cancel Transmit Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |16h |TYPE | Type Code |
|3 |00h |RES0 | Reserved |
|4 | |TOD6 | Transmit Start Time( Year) |
| | | |(Number of years since 1992) |
| | | |Range: (0...) |
| | | | |
| | | |Example: 1992 = 00h, 1993 = 01h |
|5 | |TOD5 | Transmit Start Time( Day)(MSB) |
| | | |(Day=1 indicates Jan 1) |
| | | |Day Range: ( 1...365) or |
| | | |( 1...366) In Leap Years |
| | | | |
| | | |Example: Jan 2 = 02h, Feb 1 = 20h |
|6 | |TOD4 | Transmit Start Time( Day ) (LSB) |
|7 | |TOD3 | Transmit Start Time( Hour) |
| | | |Range ( 0...23) |
|8 | |TOD2 | Transmit Start Time( Minute) |
| | | |Range (0...59) |
|9 | |TOD1 | Transmit Start Time( Second) |
| | | |Range ( 0...59) |
|10 | |RES1 | Reserved |
|11 | |CS |Checksum |
|12 |04h |EOT |End of Packet |
Cancel Transmit Response
Title : Cancel Transmit Response
Description : Returns the status for the Cancel Transmit command.
Response : N/A
|Cancel Transmit Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |16h |TYPE | Type Code |
|3 | |SS |Status |
| | | |00h = Completed OK. |
| | | |01h = Illegal Request (transmit already in progress). |
| | | |03h = Specified Transmit Queue Entry Not Found. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. If the specified transmission is already in progress, the transmitter will return a status of (01h) Illegal Request.
Transmitter Diagnostic Functions
Reset Transmitter Command
Title : Reset Transmitter Command
Description : Execute a “Soft” reset and re-initialize internal variables.
Response : Reset Transmitter Response
|Reset Transmitter Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |76h |TYPE | Type Code. |
|3 |00h |RES0 | Reserved |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. A reset will reset all transmission hardware to its power-up default (i.e. it will power OFF the digital frequency synthesizer and RF hardware sections).
2. The Time-of-Day clock is cleared.
3. Any pending GOES transmissions will be discarded.
Reset Transmitter Response
Title : Reset Transmitter Response
Description : Acknowledges Reset Transmitter Command before performing reset.
Response : N/A
|Reset Transmitter Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |76h |TYPE | Type Code. |
|3 | |SS |Transmitter/ Status. |
| | | |00h = Completed OK. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
Initiate Self-Test Command
Title : Initiate Self-Test Command
Description : Re-execute Power-up diagnostics, reset transmitter.
Response : Initiate Self-Test Response
|Initiate Self-Test Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |78h |TYPE | Type Code |
|3 | |CS |Checksum |
|4 |04h |EOT |End of Packet |
Initiate Self-Test Response
Title : Initiate Self-Test Response
Description : Acknowledges Initiate Self-Test Command before executing the self-test.
Response : N/A
|Initiate Self Test Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |78h |TYPE | Type Code. |
|3 | |SS | Status. |
| | | |00h = Completed OK. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. The self-test performed is the same one done at power-up. After the self-test completes, the SE1200 will undergo the same hardware and software initialization as that caused by a Reset command.
2. The transmitter self-test takes approximately 15 seconds to complete. The user should wait at least that long after receiving the Initiate Self-Test Response before attempting to issue subsequent commands to the transmitter.
Display Self-Test Result Command
Title : Display Self-Test Result Command
Description : Display the result of the most recent execution of the transmitter’s self-test.
Response : Display Self-Test Result Response
|Display Self-Test Result Command |
|Pos |Byte |Name | Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |77h |TYPE | Type Code |
|3 | |CS |Checksum |
|4 |04h |EOT |End of Packet |
Display Self-Test Result Response
Title : Display Self-Test Result Response
Description : Returns the result of the most recent execution of the transmitter’s self-test.
Response : N/A
|Display Self-Test Result Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |77h |TYPE | Type Code. |
|3 | |SS | Status. |
| | | |00h = Completed OK. |
|4 | |STSF0 |Self-Test Status Flags Byte0 |
|5 | |STSF1 |Self-Test Status Flags Byte1 |
|6 | |RES0 |Reserved |
|7 | |RES1 |Reserved |
|8 | |RES2 |Reserved |
|9 | |RES3 |Reserved |
|10 | |GPS |GPS Receiver Flag: |
| | | |00 = GPS receiver not installed. |
| | | |01 = GPS installed. |
|11 | |TT |Transmitter Type: |
| | | |(Specifies the type of transmissions supported by |
| | | |the transmitter). |
| | | |05 = GOES 100 BPS and 300 BPS only |
| | | |06 = GOES 100 BPS, 300 BPS, and 1200 BPS |
|12 | |CS |Checksum |
|13 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. The self-test performed is the same one done at power-up. After the self-test completes, the SE1200 will undergo the same hardware and software initialization as that caused by a Reset command.
2. The transmitter self-test takes approximately 15 seconds to complete. The user should wait at least that long before attempting to issue subsequent commands to the transmitter.
3. The Self-Test Status Flags contain the results of the most recent execution of the transmitter’s self-test and are defined as follows:
Self-Test Status Flags
Byte0 CONTENTS
BIT0=1 Reserved
BIT1=1 Reserved
BIT2=1 Battery Voltage < 10.0 Volts
BIT3=1 Software Boot Code Flash CRC Error
BIT4=1 RS232 Software Flash CRC Error
BIT5=1 Temperature Sensor Test Failure
BIT6=1 TCXO DAC Test Failure
BIT7=1 Reserved
Byte1 CONTENTS
BIT0=1 HSB Software Flash CRC Error
BIT1=1 RF PLL Lock Failure
BIT2=1 TOD Interrupt Test Failure
BIT3=1 Modulation Interrupt Test Failure
BIT4=1 Manufacturing Data Flash CRC Error
BIT5...7 Reserved
4. If the transmitter aborts a transmission because it detects a low-battery condition or a RF PLL lock failure condition, it will set the corresponding bit of the Self-Test Status Flags at the time of the failure. The flag will remain set until the next power cycle or reset.
5. All Self-Test Status Flags are cleared after a Display Self-Test Result command response has been sent back to the host.
6. The Transmitter Type codes (that specify the type of transmissions supported by the transmitter) for other Signal Engineering, Inc. transmitter models are given below.
a) 00 = GOES 100 BPS only.
b) 01 = ARGOS and SCD-1.
c) 02 = GOES 100 BPS and GMS 100 BPS.
d) 03 = GOES 100 BPS and METEOSAT 100 BPS.
e) 04 = METEOSAT 100 BPS only.
Send Fixed Channel Command
Title : Send Fixed Channel Command
Description : Send unmodulated carrier on specified Channel Number.
Response : Send Fixed Channel Response
|Send Fixed Channel Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |7Ah |TYPE |Type Code |
|3 | |SC |Transmit Type Code: |
| | | |00 = GOES 100 BPS |
| | | |01 = GOES 300 BPS |
| | | |02 = GOES 1200 BPS |
|4 |00h |RES1 |Reserved |
|5 | |CHAN1 |Transmit Channel Number (MSB) |
|6 | |CHAN0 |Transmit Channel Number (LSB) |
|7 | |CS |Checksum |
|8 |04h |EOT |End of Packet |
NOTES:
1. The Transmit Type Code field selects the channel frequency associated with the specified channel number and the failsafe interval for the specified data rate:
a) =00 (GOES 100 BPS) causes the GOES 100/300 BPS channels and the GOES 100 BPS failsafe interval to be used.
b) =01 (GOES 300 BPS) causes the GOES 100/300 BPS channels and the GOES 300 BPS failsafe interval to be used.
c) =02 (GOES 1200 BPS) causes the GOES 1200 BPS channels and the GOES 1200 BPS failsafe interval to be used.
2. There are two separate sets of transmit frequencies used by the GOES data collection system, those used for 100 or 300 BPS transmissions (identified as GOES 100/300 BPS Channel 1-266), and those used for 1200 BPS transmissions (identified as GOES 1200 BPS Channel 1-133). See Appendix E: GOES Data Collection System Transmit Frequencies for a detailed list of channel number versus frequency for each of the three data rates.
Send Fixed Channel Response
Title : Send Fixed Channel Response
Description : Return status of the Send Fixed Channel Command.
Response : N/A
|Send Fixed Channel Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |7Ah |TYPE | Type Code |
|3 | |SS |Transmitter/ Status. |
| | | |00h = Completed OK. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
Display Version Information Command
Title : Display Version Information Command
Description : Display transmitter hardware and software version information.
Response : Display Version Information Response
|Display Version Information Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Dh |TYPE |Type Code |
|3 | |CS |Checksum |
|4 |04h |EOT |End of Packet |
Display Version Information Response
Title : Display Version Information Response
Description : Return transmitter hardware and software version information.
Response : N/A
|Display Version Information Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |1Dh |TYPE | Type Code |
|3 | |SS |Transmitter/ Status. |
| | | |00h = Completed OK. |
|4 | | |Reserved (16 chars) |
|.. | | | |
|19 | | | |
|20 | | |Software Build Time: |
|.. | | |‘hh:mm:ss’ |
|27 | | | |
| | | |where: h, m, s are ASCII numerals ‘0’..’9’ |
|28 | | |Reserved (8 chars) |
|.. | | | |
|35 | | | |
|36 | | |Software Build Date: |
|.. | | |‘mm/dd/yyyy’ |
|45 | | | |
| | | |where m, d, y are ASCII numerals ‘0’..’9’ |
|46 | | |Reserved (78 chars) |
|.. | | | |
|123 | | | |
|124 | |CS |Checksum |
|125 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. All version information fields contain printable ASCII characters only.
2. All Reserved fields are filled with ASCII Space (20h) characters.
Get Status Command
Title : Get Status Command
Description : Display transmitter status information.
Response : Get Status Response
|Get Status Command |
|Pos |Byte |Name | Description |
|0 |01h |HCSB | HSB Command Specification Byte |
|1 |08h |Length | Length = # Bytes positions 0...7 |
|2 |74h |Type | Type Code |
|3 |00h |RES0 |Reserved |
|4 |00h |RES1 |Reserved |
|5 | |OFFSET1 |Starting offset of status information (MSB) |
|6 | |OFFSET0 |Starting offset of status information (LSB) |
|7 | |NUMBYTES |Number of status information bytes to be returned in response |
Get Status Response
Title : Get Status Response
Description : Returns transmitter status information.
Response : N/A
|Get Status Response |
|Pos |Byte |Name |Description |
|0 | |Length | Length = # Bytes 0...N |
|1 |74h |Type | Type Code. |
|2 | |SS | Status. |
| | | |00h = Completed OK. |
|3 | | |First status information byte |
|… | | |… |
|N | | |Last status information byte |
ADDITIONAL NOTES:
1. Transmitter status information is maintained as a structure containing fields of defined sizes at fixed byte offsets. The sizes and offset are given in the following table.
2. Any number of status information bytes may be retrieved with a Get Status command, from 1 byte to all defined bytes, starting at any offset into the status information structure.
3. For fields with size greater than 1 byte, bytes are ordered MSB first.
|Offset (Bytes) |Field Size |Field Format |Status Information Field |
| |(Bytes) | | |
|0 |2 |Unsigned Binary |Current Battery Voltage (millivolts) |
|2 |1 |Signed |Current Temperature (Degrees C) |
| | |Binary | |
|3 |2 |Unsigned |Battery Voltage before last transmit (millivolts) |
| | |Binary | |
|5 |1 |Signed |Temperature before last transmit (Degrees C) |
| | |binary | |
|6 |2 |Unsigned |Battery Voltage during last transmit (millivolts) |
| | |Binary | |
|8 |10 |ASCII |Latitude of last GPS position (DDMM.MMMMM, |
| | |Decimal |where DD=Degrees, MM.MMMMM=Minutes, and M,D are ASCII numeric characters ‘0’..’9’) |
|18 |1 |ASCII |Latitude Direction (‘N’ or ‘S’) |
| | |Alpha | |
|19 |11 |ASCII |Longitude of last GPS position (DDDMM.MMMMM, |
| | |Decimal |where DDD=Degrees, MM.MMMMM=Minutes, and M,D are ASCII numeric characters ‘0’..’9’) |
|30 |1 |ASCII |Longitude Direction (‘E’ or ‘W’) |
| | |Alpha | |
|31 |6 |ASCII |Altitude of last GPS position |
| | |decimal |(Meters) |
|37 |1 |Unsigned binary |Time of last GPS position( Year) |
| | | |=0: 1992, =1:1993, etc. |
|38 |2 |Unsigned binary |Time of last GPS position( Day) |
| | | |=1..366 |
|40 |1 |Unsigned binary |Time of last GPS position( Hour) |
| | | |=0..23 |
|41 |1 |Unsigned binary |Time of last GPS position( Minute) |
| | | |=0..59 |
|42 |1 |Unsigned binary |Time of last GPS position( Second) |
| | | |=0..59 |
|43 |1 |Unsigned binary |Number of missed GPS fixes |
|44 |1 |Unsigned binary |Time of last Missed GPS fix( Year) |
| | | |=0: 1992, =1:1993, etc. |
|45 |2 |Unsigned binary |Time of last Missed GPS fix( Day) |
| | | |=1..366 |
|47 |1 |Unsigned binary |Time of last Missed GPS fix( Hour) |
| | | |=0..23 |
|48 |1 |Unsigned binary |Time of last Missed GPS fix( Minute) |
| | | |=0..59 |
|49 |1 |Unsigned binary |Time of last Missed GPS fix( Second) |
| | | |=0..59 |
|50 |2 |Unsigned binary |Most recent GPS receiver Health/Status bytes |
|52 |1 |Unsigned binary |Failsafe Tripped Indicator |
| | | |=1: Transmitter failsafe has tripped (reset button must be pushed to resume normal |
| | | |operation). |
|53 |4 |Unsigned binary |Duration of last transmit (milliseconds) |
Software Load Command
Title : Software Load Command
Description : Writes a block of software object code to flash memory.
Response : Software Load Response
|Software Load Command |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |7Ch |TYPE |Type Code |
|3 | |LDCTL |Load Control |
| | | |=00: Erase sector of flash and write data to flash. |
|4 | |SADDR3 |Flash Start Address Byte3 (MSB) |
|5 | |SADDR2 |Flash Start Address Byte2 |
|6 | |SADDR1 |Flash Start Address Byte1 |
|7 | |SADDR0 |Flash Start Address Byte0 (LSB) |
|8 | |RES1 |Reserved |
|9 | |RES2 |Reserved |
|10 | |CRC1 |CRC MSB over 4K byte block of data (DATA1..DATAN) |
|11 | |CRC0 |CRC LSB over 4K byte block of data (DATA1..DATAN) |
|12 | |DATA1 |First data byte of 4K byte block |
|… | |… | |
|12+N | |DATAN |Last data byte of 4K byte block |
| | |CS |Checksum |
| |04h |EOT |End of Packet |
Software Load Response
Title : Software Load Response
Description : Return status of the Software Load Command.
Response : N/A
|Software Load Response |
|Pos |Byte |Name |Description |
|0 |01h |SOH |Start of Packet |
|1 | |RES |Reserved |
|2 |7Ah |TYPE | Type Code |
|3 | |SS |Transmitter/ Status. |
| | | |00h = Completed OK. |
|4 | |CS |Checksum |
|5 |04h |EOT |End of Packet |
ADDITIONAL NOTES
1. 16-bit CRC over 4K byte block of data in command request packet uses CRC CCITT algorithm (polynomial = 1021h). SE1200 will calculate CRC over the block of data and compare result to CRC included in command request packet. If CRCs don’t match, a bad status is returned in response and write to flash will not be performed.
APPENDIX A: SE1200 COMMAND EXAMPLES
A.1 SE1200 INITIALIZATION/ CONFIGURATION
|Host |SE1200 |Description |
|Assert RTS | |Wake up SE1200 |
| | Assert CTS |Host checks if SE1200 is powered up and has completed its|
|QUERY Command | |self-test. |
| | | |
| | QUERY Response |SE1200 is powered up and has completed its self-test, so |
| | |it responds with status=OK. |
| | | |
|SET TRANSMITTER ID Command | |Host sends new Platform ID and specifies that ID is to be|
|(CTL=Default ID) | |stored in non-volatile memory (overwrite old default ID).|
| | | |
| | SET TRANSMITTER |SE1200 sends response after Platform ID update is |
| |ID Response |complete. |
| | | |
|DISPLAY TRANSMITTER ID Command | |Host reads current default transmitter Platform ID back |
|(CTL=Default ID) | |to verify update. |
| | | |
| | DISPLAY TRANSMITTER |SE1200 returns response containing current default |
| |ID Response |Platform ID (stored in non-volatile memory). |
| | | |
|LOAD TRANSMITTER TIME Command | |Host loads SE1200 time-of-day clock. |
| | | |
| | LOAD TRANSMITTER |SE1200 sends response after loading of time-of-day clock |
| |TIME Response |is complete. SE1200 is now ready to make transmissions. |
| | | |
A.2 SCHEDULING A TRANSMISSION
|Host |SE1200 |Description |
|Assert RTS | |Wake up SE1200 |
| | Assert CTS |Host sends a TRANSMIT Command, containing the control |
|TRANSMIT Command | |parameters for the requested transmission (Transmit |
|(Transmit Parameters, | |Date/Time, Channel, etc), and the data to be transmitted.|
|Data) | | |
| | | |
| | TRANSMIT |SE1200 checks for transmit parameter errors and for |
| |Response |overlap with other scheduled transmissions. If no errors,|
| |(Status=00h (OK)) |SE1200 queues and schedules the transmission and returns |
| | |TRANSMIT Response packet containing completion status for|
| | |the command. |
| | | |
ADDITONAL NOTES
APPENDIX B: Legal Data Characters: GOES 100/300/1200 BPS Self-Timed Transmissions
|Legal Data Characters: GOES 100/300/1200 BPS Self-Timed Transmissions |
|MSN | Least Significant Nibble : Bits [3..0] |
| |
|MSN | Least Significant Nibble : Bits [3..0] |
| |
|MSN | Least Significant Nibble : Bits [3..0] |
| |0 |1 |2 |3 |4 |5 |6 |
|1 |401.701000 |1 |401.701750 |44 |401.765500 | | |
|2 |401.702500 | | |45 |401.767000 |23 |401.767750 |
|3 |401.704000 |2 |401.704750 |46 |401.768500 | | |
|4 |401.705500 | | |47 |401.770000 |24 |401.770750 |
|5 |401.707000 |3 |401.707750 |48 |401.771500 | | |
|6 |401.708500 | | |49 |401.773000 |25 |401.773750 |
|7 |401.710000 |4 |401.710750 |50 |401.774500 | | |
|8 |401.711500 | | |51 |401.776000 |26 |401.776750 |
|9 |401.713000 |5 |401.713750 |52 |401.777500 | | |
|10 |401.714500 | | |53 |401.779000 |27 |401.779750 |
|11 |401.716000 |6 |401.716750 |54 |401.780500 | | |
|12 |401.717500 | | |55 |401.782000 |28 |401.782750 |
|13 |401.719000 |7 |401.719750 |56 |401.783500 | | |
|14 |401.720500 | | |57 |401.785000 |29 |401.785750 |
|15 |401.722000 |8 |401.722750 |58 |401.786500 | | |
|16 |401.723500 | | |59 |401.788000 |30 |401.788750 |
|17 |401.725000 |9 |401.725750 |60 |401.789500 | | |
|18 |401.726500 | | |61 |401.791000 |31 |401.791750 |
|19 |401.728000 |10 |401.728750 |62 |401.792500 | | |
|20 |401.729500 | | |63 |401.794000 |32 |401.794750 |
|21 |401.731000 |11 |401.731750 |64 |401.795500 | | |
|22 |401.732500 | | |65 |401.797000 |33 |401.797750 |
|23 |401.734000 |12 |401.734750 |66 |401.798500 | | |
|24 |401.735500 | | |67 |401.800000 |34 |401.800750 |
|25 |401.737000 |13 |401.737750 |68 |401.801500 | | |
|26 |401.738500 | | |69 |401.803000 |35 |401.803750 |
|27 |401.740000 |14 |401.740750 |70 |401.804500 | | |
|28 |401.741500 | | |71 |401.806000 |36 |401.806750 |
|29 |401.743000 |15 |401.743750 |72 |401.807500 | | |
|30 |401.744500 | | |73 |401.809000 |37 |401.809750 |
|31 |401.746000 |16 |401.746750 |74 |401.810500 | | |
|32 |401.747500 | | |75 |401.812000 |38 |401.812750 |
|33 |401.749000 |17 |401.749750 |76 |401.813500 | | |
|34 |401.750500 | | |77 |401.815000 |39 |401.815750 |
|35 |401.752000 |18 |401.752750 |78 |401.816500 | | |
|36 |401.753500 | | |79 |401.818000 |40 |401.818750 |
|37 |401.755000 |19 |401.755750 |80 |401.819500 | | |
|38 |401.756500 | | |81 |401.821000 |41 |401.821750 |
|39 |401.758000 |20 |401.758750 |82 |401.822500 | | |
|40 |401.759500 | | |83 |401.824000 |42 |401.824750 |
|41 |401.761000 |21 |401.761750 |84 |401.825500 | | |
|42 |401.762500 | | |85 |401.827000 |43 |401.827750 |
|43 |401.764000 |22 |401.764750 |86 |401.828500 | | |
|100/300 |Frequency |1200 |Frequency |100/300 |Frequency |1200 BPS |Frequency |
|BPS |(MHz) |BPS |(MHz) |BPS |(MHz) |Channels |(MHz) |
|Channels | |Channels | |Channels | | | |
|87 |401.830000 |44 |401.830750 |132 |401.897500 |67 |401.899750 |
|88 |401.831500 | | |133 |401.899000 | | |
|89 |401.833000 |45 |401.833750 |134 |401.900500 |68 |401.902750 |
|90 |401.834500 | | |135 |401.902000 | | |
|91 |401.836000 |46 |401.836750 |136 |401.903500 |69 |401.905750 |
|92 |401.837500 | | |137 |401.905000 | | |
|93 |401.839000 |47 |401.839750 |138 |401.906500 |70 |401.908750 |
|94 |401.840500 | | |139 |401.908000 | | |
|95 |401.842000 |48 |401.842750 |140 |401.909500 |71 |401.911750 |
|96 |401.843500 | | |141 |401.911000 | | |
|97 |401.845000 |49 |401.845750 |142 |401.912500 |72 |401.914750 |
|98 |401.846500 | | |143 |401.914000 | | |
|99 |401.848000 |50 |401.848750 |144 |401.915500 |73 |401.917750 |
|100 |401.849500 | |DCS Pilot |145 |401.917000 | | |
|101 |401.851000 |51 |401.851750 |146 |401.918500 |74 |401.920750 |
|102 |401.852500 | | |147 |401.920000 | | |
|103 |401.854000 |52 |401.854750 |148 |401.921500 |75 |401.923750 |
|104 |401.855500 | | |149 |401.923000 | | |
|105 |401.857000 |53 |401.857750 |150 |401.924500 |76 |401.926750 |
|106 |401.858500 | | |151 |401.926000 |Manufact. |Test Channels |
|107 |401.860000 |54 |401.860750 |152 |401.927500 |77 |401.929750 |
|108 |401.861500 | | |153 |401.929000 | | |
|109 |401.863000 |55 |401.863750 |154 |401.930500 |78 |401.932750 |
|110 |401.864500 | | |155 |401.932000 | | |
|111 |401.866000 |56 |401.866750 |156 |401.933500 |79 |401.935750 |
|112 |401.867500 | | |157 |401.935000 | | |
|113 |401.869000 |57 |401.869750 |158 |401.936500 |80 |401.938750 |
|114 |401.870500 | | |159 |401.938000 | | |
|115 |401.872000 |58 |401.872750 |160 |401.939500 |81 |401.941750 |
|116 |401.873500 | | |161 |401.941000 | | |
|117 |401.875000 |59 |401.875750 |162 |401.942500 |82 |401.944750 |
|118 |401.876500 | | |163 |401.944000 | | |
|119 |401.878000 |60 |401.878750 |164 |401.945500 |83 |401.947750 |
|120 |401.879500 | | |165 |401.947000 | | |
|121 |401.881000 |61 |401.881750 |166 |401.948500 |84 |401.950750 |
|122 |401.882500 | | |167 |401.950000 | | |
|123 |401.884000 |62 |401.884750 |168 |401.951500 |85 |401.953750 |
|124 |401.885500 | | |169 |401.953000 | | |
|125 |401.887000 |63 |401.887750 |170 |401.954500 |86 |401.956750 |
|126 |401.888500 | | |171 |401.956000 | | |
|127 |401.890000 |64 |401.890750 |172 |401.957500 |87 |401.959750 |
|128 |401.891500 | | |173 |401.959000 | | |
|129 |401.893000 |65 |401.893750 |174 |401.960500 |88 |401.962750 |
|130 |401.894500 | | |175 |401.962000 | | |
|131 |401.896000 |66 |401.896750 |176 |401.963500 |89 |401.965750 |
|100/300 |Frequency |1200 |Frequency |100/300 |Frequency |1200 BPS |Frequency |
|BPS |(MHz) |BPS |(MHz) |BPS |(MHz) |Channels |(MHz) |
|Channels | |Channels | |Channels | | | |
|177 |401.965000 |90 |401.968750 |222 |402.032500 | | |
|178 |401.966500 | | |223 |402.034000 |113 |402.037750 |
|179 |401.968000 |91 |401.971750 |224 |402.035500 | | |
|180 |401.969500 | | |225 |402.037000 |114 |402.040750 |
|181 |401.971000 |92 |401.974750 |226 |402.038500 | | |
|182 |401.972500 | | |227 |402.040000 |115 |402.043750 |
|183 |401.974000 |93 |401.977750 |228 |402.041500 | | |
|184 |401.975500 | | |229 |402.043000 |116 |402.046750 |
|185 |401.977000 |94 |401.980750 |230 |402.044500 | | |
|186 |401.978500 | | |231 |402.046000 |117 |402.049750 |
|187 |401.980000 |95 |401.983750 |232 |402.047500 | | |
|188 |401.981500 | | |233 |402.049000 |118 |402.052750 |
|189 |401.983000 |96 |401.986750 |234 |402.050500 | | |
|190 |401.984500 | | |235 |402.052000 |119 |402.055750 |
|191 |401.986000 |97 |401.989750 |236 |402.053500 | | |
|192 |401.987500 | | |237 |402.055000 |120 |402.058750 |
|193 |401.989000 |98 |401.992750 |238 |402.056500 | | |
|194 |401.990500 | | |239 |402.058000 |121 |402.061750 |
|195 |401.992000 |99 |401.995750 |240 |402.059500 | | |
|196 |401.993500 | | |241 |402.061000 |122 |402.064750 |
|197 |401.995000 |100 |401.998750 |242 |402.062500 | | |
|198 |401.996500 | | |243 |402.064000 |123 |402.067750 |
|199 |401.998000 |101 |402.001750 |244 |402.065500 | | |
|200 |401.999500 | | |245 |402.067000 |124 |402.070750 |
|201 |402.001000 |102 |402.004750 |246 |402.068500 | | |
|202 |402.002500 | | |247 |402.070000 |125 |402.073750 |
|203 |402.004000 |103 |402.007750 |248 |402.071500 | | |
|204 |402.005500 | | |249 |402.073000 |126 |402.076750 |
|205 |402.007000 |104 |402.010750 |250 |402.074500 | | |
|206 |402.008500 | | |251 |402.076000 |127 |402.079750 |
|207 |402.010000 |105 |402.013750 |252 |402.077500 | | |
|208 |402.011500 | | |253 |402.079000 |128 |402.082750 |
|209 |402.013000 |106 |402.016750 |254 |402.080500 | | |
|210 |402.014500 | | |255 |402.082000 |129 |402.085750 |
|211 |402.016000 |107 |402.019750 |256 |402.083500 | | |
|212 |402.017500 | | |257 |402.085000 |130 |402.088750 |
|213 |402.019000 |108 |402.022750 |258 |402.086500 | | |
|214 |402.020500 | | |259 |402.088000 |131 |402.091750 |
|215 |402.022000 |109 |402.025750 |260 |402.089500 | | |
|216 |402.023500 | | |261 |402.091000 |132 |402.094750 |
|217 |402.025000 |110 |402.028750 |262 |402.092500 | | |
|218 |402.026500 | | |263 |402.094000 |133 |402.097750 |
|219 |402.028000 |111 |402.031750 |264 |402.095500 | | |
|220 |402.029500 | | |265 |402.097000 | | |
|221 |402.031000 |112 |402.034750 |266 |402.098500 | | |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.