IMPORTANT NOTE: The information contained in this document supersedes all previously
published information regarding this product. This manual is subject to change without prior notice.
About this Manual ...................................................................................................................................... v
Patents and Trademarks ............................................................................................................................ v
Product Support .......................................................................................................................................... v
This manual describes the installation and operation for the Radyne DMD Remote Operations.
This is a technical document intended for earth station engineers, technicians, and operators
responsible for the operation and maintenance of the Radyne DMD Remote Operations.
Patents and Trademarks
See all of Comtech EF Data’s Patents and Patents Pending at http://patents.comtechefdata.com.
Comtech EF Data acknowledges that all trademarks are the property of the trademark owners.
Product Support
For all product support, please call:
+1.240.243.1880
+1.866.472.3963 (toll free USA)
Preface
Military Standards
References to “MIL-STD-188” apply to the 114A series (i.e., MIL-STD-188-114A), which provides
electrical and functional characteristics of the unbalanced and balanced voltage digital interface
circuits applicable to both long haul and tactical communications. Specifically, these references
apply to the MIL-STD-188-114A electrical characteristics for a balanced voltage digital interface
circuit, Type 1 generator, for the full range of data rates. For more information, refer to the
Department of Defense (DOD) MIL-STD-188-114A, Electrical Characteristics of Digital Interface Circuits.
Related Documents
Department of Defense (DOD) MIL-STD-188-114A, Electrical Characteristics of Digital Interface
Circuits
Department of Defense (DOD) MIL-STD-188-165A, Interoperability and Performance Standards for
SHF Satellite Communications PSK Modems (FDMA Operation) (dated November 2005)
INTELSAT Earth Station Standards IESS-308, -309, -310, and -315
Applicable testing is routinely performed as a condition of manufacturing on all units to ensure
compliance with the requirements of the EN 60950 Safety of Information Technology Equipment (Including Electrical Business Machines) safety standard.
This equipment meets the Safety of Information Technology Equipment specification as defined
in EN60950.
Low Voltage Directive (LVD)
The following information is applicable for the European Low Voltage Directive (2006/95/EC):
Symbol Description
<HAR>
!
Type of power cord required for use in the European Community.
http://www.comtechefdata.com
Comtech EF Data Corp.
2114 West 7
Tempe, Arizona USA 85281
+1.480.333.2200
th
Street
MN-DMDREMOTEOP Revision 9 viii
Chapter 1. Remote Operations
1.1 Introduction
The Remote Protocols for the DMD20, DMD20LBST, DMD50, DMD2050, DMD2050E,
DMD1050 and OM20 are similar in design and utilize the same protocol platforms. This
document should be used as the primary source for identifying the various protocol structures
and control menus for products listed below. The most current Remote Protocols manual can be
accessed from the Radyne web site at http://www.comtechefdata.com
The Remote Protocols identified in MN-DMDREMOTEOP are RLLP (Radyne Link Level
Protocol), SNMP MIB file, Web Browser menus and Terminal Port menus. The MNDMDREMOTEOP document does not identify equipment setup processes. The Product manuals
include instructions to set up the equipment but will not include the protocol structure. The
Remote Protocol manual MN-DMDREMOTEOP is applicable to the following products:
The Remote Port allows for complete control and monitoring of all parameters and functions via
an RS-232 Serial Interface or RS-485 for RLLP Protocol. ‘Equipment Remote Mode’ can be
entered from the GUI interface under the “System” menu by selecting “System” and then
“Terminal” followed by “Terminal”. The baud rate and evaluation type can be changed at the front
panel by using the System>Baud Rate Menu.
Control and status messages are conveyed between the modem and all subsidiary modems and
the host computer using packetized message blocks in accordance with a proprietary
communications specification. This communication is handled by the Radyne Link Level Protocol
(RLLP), which serves as a protocol ‘wrapper’ for the RM&C data. Complete information on
monitor and control software is contained in the following sections.
This specification is applicable to the DMD20/20LBST, DMD50, DMD2050,
DMD2050E, DMD1050 and OM20 Modems. Any reference to the DMD20 in this
document can be applicable to any one of these three modems.
For configuration setup, refer to the product manuals.
1.2.1 Protocol Structure:
The Communications Specification (COMMSPEC) defines the interaction of computer resident
Monitor and Control Software used in satellite earth station equipment such as modems,
redundancy switches, multiplexers, and other ancillary support gear. Communication is bidirectional, and is normally established on one or more full-duplex 9600-baud multi-drop control
buses that conform to EIA Standard RS-485.
Each piece of earth station equipment on a control bus has a unique physical address, which is
assigned during station se tup/config uration or prior to ship ment. Valid dec imal addr esses on one
control bus range from 032 through 255 for a total of up to 224 devices per bus. Address 255 of
each control bus is usually reserved for the M&C computer.
1.2.2 Protocol Wrapper:
The Radyne COMMSPEC is byte-oriented, with the Least Significant Bit (LSB) issued first. Each
data byte is conveyed as mark/space information with two marks comprising the stop data. When
the last byte of data is transmitted, a hold comprises one steady mark (the last stop bit). To begin
or resume data transfer, a space (00h) substitutes this mark. This handling scheme is controlled
by the hardware and is transparent to the user. A pictorial representation of the data and its
surrounding overhead may be shown as follows:
S1 S2 B
0
The Stop Bits, S1 and S2, are each a mark. Data flow remains in a hold mode until S2 is
replaced by a space. If S2 is followed by a space, it is considered a start bit for the data byte and
not part of the actual data (B
Level Protocol (RLLP) organizes the actual monitor and control data within a shell, or ‘protocol
wrapper’ that surrounds the data. The format and structure of the COMMSPEC message
exchanges are described herein. Decimal numbers have no suffix; hexadecimal numbers end
with a lower case ‘h’ suffix and binary values have a lower case ‘b’ suffix. Thus, 22 = 16h =
000010110b. The principal elements of a data frame, in order of occurrence, are summariz ed as
follows:
<SYNC>: The message format header character or ASCII sync character that defines the
beginning of a message. The <SYNC> character value is always 16h.
<BYTE COUNT>: The Byte Count is the number of bytes in the <DATA> field (2 Bytes).
<SOURCE ID>: The Source Identifier defines the multi-drop addres s origin.
B1 B2 B3 B4 B5 B6 B7 S1 S2, etc.
0
- B 7). The COMMSPEC developed for use with the Radyne Link
All nodes on a given control bus have a unique address that must be defined.
<DESTINATION ID>: The Destination Identifier serves as a pointer to the multi-drop destination
device that indicates where the message is to be sent.
<FRAME SEQUENCE NUMBER>: The Frame Sequence Number (FSN) is a tag with a value
from 0 through 255 that is sent with each message. It assures sequential information
framing and correct equipment acknowledgment and data transfers.
<OPCODE>: The Operation Code field contains a number that identifies the message type
associated with the data that follows it. Equipment under MCS control recognizes this
byte via firmware identification and subsequently steers the DATA accordingly to perform
a specific function or series of functions. Acknowledgment and error codes are returned
in this field (2 Bytes).
<DATA>: The Data field contains the binary, bi-directional data bytes associated with the
<OPCODE>. The number of data bytes in this field is indicated by the <BYTE COUNT>
value.
<CHECKSUM>: The checksum is the modulo 256 sum of all preceding message bytes,
excluding the <SYNC> character. The checksum determines the presence or absence of
errors within the message. In a message block with the following parameters, the
checksum is computed as shown in Table 1-1.
Since the only concern is the modulo 256 (modulo 1 00h) equivalent (values that can be
represented by a single 8-bit byte), the checksum is F2h. For a decimal checksum calculation, the
equivalent values for each information field are:
In a Monitor and Control environment, every message frame on a control bus port executes as a
packet in a loop beginning with a wait-for-SYNC-character mode. The remaining message format
header information is then loaded, either by the M&C computer or by a subordinate piece of
equipment (such as the DMD20) requesting access to the bus. Data is processed in accordance
with the OPCODE, and the checksum for the frame is calculated. If the anticipated checksum
does not match, then a checksum error response is returned to the message frame originator.
The entire message frame is discarded and the wait-for-SYNC mode goes back into effect. If the
OPCODE resides within a command message, it defines the class of action that denotes an
instruction that is specific to the device type, and is a prefix to the DATA field if data is required. If
the OPCODE resides within a query message packet, then it defines the query code, and can
serve as a prefix to query code DATA.
The Frame Sequence Number (FSN) is included in every message packet and increments
sequentially. When the M&C computer or bus-linked equipment initiates a message, it assigns
the FSN as a tag for error control and handshaking. A different FSN is produced for each new
message from the FSN originator to a specific device on the control bus. If a command packet is
sent and not received at its intended destination, then an appropriate response message is not
received by the packet originator. The original command packet is then re-transmitted with the
same FSN. If the repeated message is received correctly at this point, it is considered a new
message and is executed and acknowledged as such.
If the command packet is received at its intended destination but the response message
(acknowledgment) is lost, then the message originator (usually the M&C computer) re-transmits
the original command packet with the same FSN. The destination device detects the same FSN
and recognizes that the message is a duplicate, so the associated commands within the packet
are not executed a second time. However, the response packet is again sent back to the source
as an acknowledgment in order to preclude undesired multiple executions of the same
command.
To reiterate, valid equipment responses to a message require the FSN tag in the command
packet. This serves as part of the handshake/acknowledges routine. If a valid response message
is absent, then the command is re-transmitted with the same FSN. For a repeat of the same
command involving iterative processes (such as increasing or decreasing the transmit power
level of a DMD20 modulator), the FSN is incremented after each message packet. When the
FSN value reaches 255, it overflows and begins again at zero. The FSN tag is a powerful tool
that assures sequential information framing, and is especially useful where commands require
more than one message packet.
The full handshake/acknowledgment involves a reversal of source and destination ID codes in
the next message frame, followed by a response code in the <OPCODE> field of the message
packet from the equipment under control.
If a command packet is sent and not received at its intended destination, a timeout condition can
occur because a response message is not received by the packet originator. On receiving
devices slaved to an M&C computer, the timeout delay parameters may be programmed into the
equipment in accordance with site requirements by Radyne prior to shipment, or altered by
qualified personnel. The FSN handshake routines must account for timeout delays and be able
to introduce them as well.
In acknowledgment (response) packets, the operational code <OPCODE> field of the message
packet is set to 0 by the receiving devices when the message intended for the device is
evaluated as valid. The device that receives the valid message then exchanges the <SOURCE
ID> with the <DESTINATION ID>, sets the <OPCODE> to zero in order to indicate that a good
message was received, and returns the packet to the originator. This "GOOD MESSAGE"
Opcode is one of nine global responses. Global response opcodes are common responses,
issued to the M&C computer or to another device that can originate from and are interpreted by
all Radyne equipment in the same manner. These are summarized as follows (all opcode values
are expressed in decimal form):
Response OPCODE Description OPCODE
Good Message 000d = 0000h
Bad Parameter 255d = 00FFh
Bad Opcode 254d = 00FEh
Incomplete Parameter 247d = 00F7h
Table 1-2: Response OPCODES
The following response error codes are specific to the DMD20:
When properly implemented, the physical and logical devices and ID addressing scheme of the
COMMSPEC normally precludes message packet contention on the control bus. The importance
of designating unique IDs for each device during station configuration cannot be
overemphasized. One pitfall, which is often overlooked, concerns multi-drop override IDs. All too
often, multiple devices of the same type are assigned in a direct-linked ("single-thread")
configuration accessible to the M&C computer directly.
For example, if two DMD20 Modems with different addresses (DESTINATION IDs) are linked to
the same control bus at the same hierarchical level, both will attempt to respond to the M&C
computer when the computer generates a multi-drop override ID of 22. If their actual setup
parameters, status, or internal timing differs, they will both attempt to respond to the override
simultaneously with different information or asynchronously in their respective message packets
and response packets, causing a collision on the serial control bus.
To preclude control bus data contention, different IDs must always be assigned to the
equipment. If two or more devices are configured for direct-linked operation, then the M&C
computer and all other devices configured in the same manner must be programmed to inhibit
broadcast of the corresponding multi-drop override ID.
The multi-drop override ID is always accepted by devices of the same type on a common control
bus, independent of the actual DESTINATION ID. These override IDs with the exception of
“BROADCAST” are responded to by all directly linked devices of the same type causing
contention on the bus. The “BROADCAST” ID, on the other hand, is accepted by all equipment
but none of then returns a response packet to the remote M&C.
The following multi-drop override IDs are device-type specific, with the exception of
"BROADCAST". These are summarized below with ID values expressed in decimal notation:
Directly-Addressed EquipmentMulti-Drop Override ID
Broadcast (all directly-linked devices) 00
DMD-3000/4000, 4500 or 5000 Mod Section, DMD20 01
DMD-3000/4000, 4500 or 5000 Demod Section, DMD20 02
RCU-340 1:1 Switch 03
RCS-780 1:N Switch 04
RMUX-340 Cross-Connect Multiplexer 05
CDS-780 Clock Distribution System 06
SOM-340 Second Order Multiplexer 07
DMD-4500/5000 Modulator Section 08
DMD-4500/5000 Demodulator Section 09
RCU-5000 M:N Switch 10
DMD20 Modulator 20
DMD20 Demodulator 21
DMD20 Modem 22
DVB3030 Video Modulator, DM240 23
RCS20 M:N Switch 24
RCS10 M:N Switch 25
RCS11 1:1 Switch 26
Reserved for future equipment types 27-31
Multi-drop override IDs 01 or 02 can be used interchangeably to broadcast a
message to a DMD-3000/4000 Modem, DMD-4500/5000, or a DMD20 Modem.
Radyne recommends that the multi-drop override IDs be issued only during
system configuration as a bus test tool by experienced programmers and that
they not be included in run-time software. It is also advantageous to consider
the use of multiple bus systems where warranted by a moderate to large
equipment complement.
Therefore, if a DMD20 Modulator is queried for its equipment type identifier, it will return a "20"
and DMD20 Demodulator will return a "21". A DMD20 Modem will also return a "22".
1.2.6 Software Compatibility:
The COMMSPEC, operating in conjunction within the RLLP shell, provides for full forward and
backward software compatibility independent of the software version in use. New features are
appended to the end of the DATA field without OPCODE changes. Older software simply
discards the data as extraneous information without functional impairment for backward
compatibility.
If new device-resident or M&C software receives a message related to an old software version,
new information and processes are not damaged or affected by the omission of data.
The implementation of forward and backward software compatibility often, but not always,
requires the addition of new Opcodes. Each new function requires a new Opcode assignment if
forward and backward compatibility cannot be attained by other means.
When Radyne equipment is queried for bulk information (Query Mod, Query Demod, etc.) it
responds by sending back two blocks of data; a Non-Volatile Section (parameters that can be
modified by the user) and a Volatile Section (status information). It also returns a count value that
indicates the size of the Non-Volatile Section. This count is used by M&C developers to index
into the start of the Volatile Section.
When new features are added to Radyne equipment, the control parameters are appended to
the end of the Non-Volatile Section, and status of the features, if any, are added at the end of the
Volatile Section. If a remote M&C queries two pieces of Radyne equipment with different revision
software, they may respond with two different sized packets. The remote M&C MUST make use
of the non-volatile count value to index to the start of the Volatile Section. If the remote M&C is
not aware of the newly added features to the Radyne product, it should disregard the parameters
at the end of the Non-Volatile Section and index to the start of the Volatile Section.
If packets are handled in this fashion, there will also be backward-compatibility between Radyne
equipment and M&C systems. Remote M&C systems need not be modified every time a feature
is added unless the user needs access to that feature.
1.2.7 Flow Control and Task Processing:
The original packet sender (the M&C computer) relies on accurate timeout information with
regard to each piece of equipment under its control. This provides for efficient bus
communication without unnecessary handshake overhead timing. One critical value is
designated the Inter-Frame Space (FS). The Inter-Frame Space provides a period of time in
which the packet receiver and medium (control bus and M&C computer interface) fully recover
from the packet transmission/reception process and the receiver is ready to accept a new
message. The programmed value of the Inter-Frame Space should be greater than the sum of
the "turnaround time" and the round-trip (sender/receiver/bus) propagation time, including
handshake overhead. The term "turnaround time" refers to the amount of time required for a
receiver to be re-enabled and ready to receive a packet after having just received a packet. In
flow control programming, the Inter-Frame Space may be determined empirically in accord with
the system configuration or calculated based on established maximum equipment task
processing times.
Each piece of supported equipment on the control bus executes a Radyne Link Level Task
(RLLT) in accordance with its internal hardware and fixed program structure. In a flow control
example, the RLLT issues an internal "message in" system call to invoke an I/O wait condition
that persists until the task receives a command from the M & C computer. The RLLT has the
option of setting a timeout on the incoming message. Thus, if the equipment does not receive an
information/command packet within a given time period, the associated RLLT exits the I/O wait
state and takes appropriate action.
Radyne equipment is logically linked to the control bus via an Internal I/O Processing Task
(IOPT) to handle frame sequencing, error checking, and handshaking. The IOPT is essentially a
link between the equipment RLLT and the control bus. Each time the M&C computer sends a
message packet; the IOPT receives the message and performs error checking. If errors are
absent, the IOPT passes the message to the equipment's RLLT. If the IOPT detects errors, it
appends error messages to the packet. Whenever an error occurs, the IOPT notes it and
discards the message; but it keeps track of the incoming packet. Once the packet is complete,
the IOPT conveys the appropriate message to the RLLT and invokes an I/O wait state (wait for
next <SYNC> character).
If the RLLT receives the packetized message from the sender before it times out, it checks for
any error messages appended by the IOPT. In the absence of errors, the RLLT processes the
received command sent via the transmitted packet and issues a "message out" system call to
ultimately acknowledge the received packet. This call generates the response packet conveyed
to the sender. If the IOPT sensed errors in the received packet and an RLLT timeout has not
occurred, the RLLT causes the equipment to issue the appropriate error message(s) in the
pending equipment response frame.
To maintain frame synchronization, the IOPT keeps track of error-laden packets and packets
intended for other equipment for the duration of each received packet. Once the packet is
complete, the IOPT invokes an I/O wait state and searches for the next <SYNC> character.
1.2.8 RLLP Summary:
The RLLP is a simple send-and-wait protocol that automatically re-transmits a packet whenever
an error is detected, or when an acknowledgment (response) packet is absent.
During transmission, the protocol wrapper surrounds the ac tual data to form information packets.
Each transmitted packet is subject to time out and frame sequence control parameters, after
which the packet sender waits for the receiver to convey its response. Once a receiver verifies
that a packet sent to it is in the correct sequence relative to the previously received packet, it
computes a local checksum on all information within the packet excluding the <SYNC> character
and the <CHECKSUM> fields. If this checksum matches the packet <CHECKSUM>, the receiver
processes the packet and responds to the packet sender with a valid response
(acknowledgment) packet. If the checksum values do not match, the receiver replies with a
negative acknowledgment (NAK) in its response frame.
The response packet is therefore an acknowledgment either that the message was received
correctly, or some form of a packetized NAK frame. If the sender receives a valid
acknowledgment (response) packet from the receiver, the <FSN> increments and the next
packet is transmitted as required by the sender. However, if a NAK response packet is returned
the sender re-transmits the original information packet with the same embedded <FSN>.
If an acknowledgment (response) packet or a NAK packet is lost, corrupted, or not issued due to
an error and is thereby not returned to the sender, the sender re-transmits the original
information packet; but with the same <FSN>. When the intended receiver detects a duplicate
packet, the packet is acknowledged with a response packet and internally discarded to preclude
undesired repetitive executions. If the M&C computer sends a command packet and the
corresponding response packet is lost due to a system or internal error, the computer times out
and re-transmits the same command packet with the same <FSN> to the same receiver and
waits once again for an acknowledgment or a NAK packet.
To reiterate, the format of the Link Level Protocol Message Block is shown below.
SYNC
Byte
Byte
COUNT
SOURCE
ADDRESS
DESTINATION
ADDRESS
FSN OPCODE
DATA
BYTES
CHECKSUM
1.3 Remote Port Packet Structure:
The Modem protocol is an enhancement on the DMD20 protocol. It also uses a packet structure
format. The structure is as follows:
<SYNC>: Message format header character that defines the beginning of a message. The
<SYNC> character value is always 0x16 (1 byte).
<BYTE COUNT>: The number of bytes in the <DATA> field (2 bytes).
<SOURCE ID>: Identifies the address of the equipment from where the message originated (1
byte).
<DESTINATION ID>: Identifies the address of the equipment where the message is to be sent (1
<FSN>: Frame sequence number ensures correct packet acknowledgment and data transfers (1
byte).
<OPCODE>: This byte identifies the message type associated with the information data. The
equipment processes the data according to the value in this field. Return error codes and
acknowledgment are also included in this field (2 bytes).
<...DATA...>: Information data. The number of data bytes in this field is indicated by the <BYTE
COUNT> value.
<CHECKSUM>: The modulo 256 sum of all preceding message bytes excluding the <SYNC>
character (1 byte).
The Modem RLLP is not software-compatible with the following previous
Radyne products: RCU5000 and DMD4500. These products may not occupy the
same bus while using this protocol as equipment malfunction and loss of data
may occur.
When transmitting a packet at 9600 baud, the Remote M&C should ensure that
the timeout value between characters does not exceed the time it takes to
transmit 200 characters (≈
200 msec). If this timeout value is exceeded, the
equipment will timeout.
1.4 DMD20 Opcode Command Set:
The DMD20/DMD20 LBST Opcode Command Set is listed below:
When new features are added to Radyne equipment, the control parameters
are appended to the end of the Non-Volatile Section of the Remote
Communications Specification, and status of the features, if any, are added at
the end of the Volatile Section. If a remote M & C queries two pieces of Radyne
equipment with different revision software, they could respond with two
different sized packets. The remote M & C MUST make use of the non-volatile
count value to index to the start of the Volatile Section. If the remote M & C is
not aware of the newly added features to the product, it should disregard the
parameters at the end of the Non-Volatile Section and index to the start of the
Volatile Section.
Before creating any software based on the information contained in this
document, contact the Comtech EF Data Customer Service Department (480333-4357) to find out if the software revision for that piece of equipment is
current and that no new features have been added since the release of this
document.
1.4.1 Modem Command Set:
Query Modulator Configuration and Status 2400h
Query Demodulator Configuration and Status 2401h
Query Modem Drop & Insert Map 2402h
Query Modems Identification 2403h
Query Modem Control Mode 2404h
Query Modulator Latched Alarms 2405h
Query Demodulator Latched Alarms 2406h
Query Modem Latched Alarms 2407h
Query Modulator Current Alarms 2408h
Query Demodulator Current Alarms 2409h
Query Modem Current Alarms 240Ah
Query Modulator Status 240Bh
Query Demodulator Status 240Ch
Query Modem Eb/No, BER and Level 240Dh
Query Time 240Eh
Query Date 240Fh
Query Time and Date 2410h
Query Modem Summary Faults 2411h
Query Modem Event Buffer 2412h
Query Modulator Configuration 2448h
Query Demodulator Configuration 2449h
Query Modem Features 2450h
Query Modulator Async Configuration 2451h
Query Demodulator Async Configuration 2452h
Query Up converter Configuration 2490h
Query Uplink RF 2491h
Query Down converter Configuration 2492h
Query Downlink RF 2493h
Query Demodulator Ethernet Terrestrial Interface Packet Status 2494h
Command Clear Latched Alarms 2C03h
Command Set Time 2C04h
Command Set Date 2C05h
Command Set Time and Date 2C06h
Clear Modem Common Latched Alarm 1 2C08h
Clear Modem Common Latched Alarm 2 2C09h
Command Delete Modem Event Buffer 2C0Ah
Command Soft Reset 2C0Bh
Command BUC FSK Pass Thru 2F61h
1.5 Detailed Command Descriptions:
1.5.1 DMD20 Modulator:
Opcode: <2400h> Query a Modulator's Configuration and Status
Loopback
<1> AUPC Remote 2047 0 = Disabled, 1 = Enabled
<2> AUPC Target Eb/No Target Eb/No at Receiver, 400 to 2000 (4.00 db to
20.00 db)
<2> AUPC Minimum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Maximum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Nominal
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
<1> Latched Alarm 4 Bit 0 = LBST BUC DC Current Alarm
Bit 1 = LBST BUC DC Voltage Alarm
Bit 2 = Ethernet WAN Alarm
Bit 3 = LBST BUC PLL Alarm
Bit 4 = LBST BUC Over Temperature Alarm
Bit 5 = LBST BUC Summary Alarm
Bit 6 = LBST BUC Output Enable Alarm
Bit 7 = LBST BUC Communications Alarm
0 = Not Latched, 1 = Latched
<1> Reserved Ignore
<2> LBST BUC DC
Amps, Implied decimal point, 1000 = 1.000A
Current
<2> LBST BUC DC
Volts, Implied decimal point, 10 = 1.0V
Voltage
<1> FSK Test Result 0 = Pass, 1 = Fail
<2> BUC Carrier Level Implied decimal point, dBm
<4> BUC Summary
Status
<1> BUC Temperature Implied Decimal Point, C
Loopback
<1> AUPC Remote 2047 0 = Disabled, 1 = Enabled
<2> AUPC Target Eb/No Target Eb/No at Receiver, 400 to 2000 (4.00 db to
20.00 db)
<2> AUPC Minimum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Maximum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Nominal
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
<1> Alarm 4 Bit 0 = LBST BUC DC Current Alarm, 1 = Fail
Bit 1 = LBST BUC DC Voltage Alarm, 1 = Fail
Bit 2 = Ethernet WAN Alarm, 1 = Fail
Bit 3 = LBST BUC PLL Alarm, 1 = Fail
Bit 4 = LBST BUC Over Temperature Alarm, 1 = Fail
Bit 5 = LBST BUC Summary Alarm, 1 = Fail
Bit 6 = LBST BUC Output Enable Alarm, 1 = Fail
Bit 7 = LBST BUC Communications Alarm, 1 = Fail
<1> Latched Alarm 4 Bit 0 = LBST BUC DC Current Alarm
Bit 1 = LBST BUC DC Voltage Alarm
Bit 2 = Ethernet WAN Alarm
Bit 3 = LBST BUC PLL Alarm
Bit 4 = LBST BUC Over Temperature Alarm
Bit 5 = LBST BUC Summary Alarm
Bit 6 = LBST BUC Output Enable Alarm
Bit 7 = LBST BUC Communications Alarm
0 = Not Latched, 1 = Latched
<1> Reserved Ignore
<2> LBST BUC DC
Amps, Implied decimal point, 1000 = 1.000A
Current
<2> LBST BUC DC
Volts, Implied decimal point, 10 = 1.0V
Voltage
<1> FSK Test Result 0 = Pass, 1 = Fail
<2> BUC Carrier Level Implied decimal point, dBm
<4> BUC Summary
Status
<1> BUC Temperature Implied Decimal Point, C
Opcode: <2405h> Query a Modulator's Latched Alarms
Query Response (5 Bytes)
<1> Latched Alarm 1 Bit 0 = Transmit FPGA/Processor Fault
Bit 1 = Drop DSP
Bit 2 = Transmit Symbol Clock PLL Lock
Bit 3 = Reserved
Bit 4 = Transmit L-Band Synthesizer Lock
Bits 5 – 7 = Reserved
0 = Not Latched, 1 = Latched
<1> Latched Common
Alarm 1
Bit 0 = -12V Alarm
Bit 1 = +12V Alarm
Bit 2 = +5V Alarm
Bits 3 – 5 = Reserved
Bit 6 = IF SYNTH Alarm
Bit 7 = Spare
0 = Not Latched, 1 = Latched
<1> Latched Common
Alarm 2
Bit 0 = TERR FPGA Config
Bit 1 = CODEC FPGA Config
Bit 2 = CODEC Device Config
Bit 3 = TRANSEC Power Test
Bit 4 = +1.5 V Rx Alarm
Bit 5 = +1.5 V TX Alarm
Bit 6 = +3.3 V Alarm
Bit 7 = +20 V Alarm
0 = Not Latched, 1 = Latched
Bit 1 = Internal Clock Activity Detect
Bit 2 = Tx Sat Clock Activity Detect
Bit 3 = Tx Data Activity Detect
Bit 4 = Terrestrial AIS. Tx Data AIS Detect
Bit 5 = Tx Clock Fallback
Bit 6 = DVB Frame Lock Fault
Bit 7 = TPC Conflict Check
0 = Not Latched, 1 = Latched
<1> Latched Alarm 4 Bit 0 = LBST BUC DC Current Alarm
Bit 1 = LBST BUC DC Voltage Alarm
Bit 2 = Ethernet WAN Alarm
Bit 3 = LBST BUC PLL Alarm
Bit 4 = LBST BUC Over Temperature Alarm
Bit 5 = LBST BUC Summary Alarm
Bit 6 = LBST BUC Output Enable Alarm
Bit 7 = LBST BUC Communications Alarm
0 = Not Latched, 1 = Latched
Opcode: <2408h> Query a Modulator's Current Alarms
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Maximum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Nominal
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
<2> AUPC Target Eb/No Target Eb/No at Receiver, 400 to 2000 (4.00 db to
20.00 db)
Opcode: <2631h> Command AUPC Minimum Power
Command Data (2 Bytes)
<2> AUPC Minimum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
Opcode: <2632h> Command AUPC Maximum Power
Command Data (2 Bytes)
<2> AUPC Maximum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
Opcode: <2633h> Command AUPC Nominal Power
Command Data (2 Bytes)
<2> AUPC Nominal
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
Opcode: <2634h> Command AUPC Local Configuration
Command Data (12 Bytes)
<1> AUPC Local Enable 0 = Off, 1 = EF AUPC, 2 = Radyne AUPC
<1> AUPC Local CL
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Maximum
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
<2> AUPC Nominal
Power
For DMD20 Signed value 0 to –2500 with implied
decimal point; (0.00 to –25.00 dBm) (two’s compliment)
For OM20 Signed value -2000 to -4500 with implied
decimal point; (-20.00 to -45.00 dBm)
Opcode: <2635h> Command AUPC Remote Configuration
Command Data (3 Bytes)
<1> AUPC Remote
0 = Off, 1 = EF AUPC
Enable
<1> AUPC Remote BB
0 = Disabled, 1 = Enabled
Loopback
<1> AUPC Remote 2047 0 = Disabled, 1 = Enabled
Opcode: <2636h> Command Modulator Reed Solomon N & K Codes and Interleaver Depth
Command Data (3 Bytes)
<1> Tx RS N Code 2 – 255, Reed-Solomon code word length
<1> Tx RS K Code 1 – 254, Reed-Solomon message length
<1> Tx RS Depth 4, 8, or 12
<1> Latched Alarm 1 Bit 0 = Receive FPGA/Processor Fault
Bit 1 = Carrier Loss
Bit 2 = Multiframe Sync Loss
Bit 3 = Frame Sync Loss
Bit 4 = IBS BER Alarm
Bit 5 = Satellite AIS
Bit 6 = Rx Data Activity
Bit 7 = Rx AGC Level
0 = Not Latched, 1 = Latched
<1> Latched Alarm 2 Bit 0 = Buffer Underflow
Bit 1 = Buffer Overflow
Bit 2 = Buffer Under 10%
Bit 3 = Buffer Over 90%
Bit 4 = RS Decoder Lock Fault
Bit 5 = RS De-Interleaver Fault
Bit 6 = RS Decoder Uncorrectable Word
Bit 7 = Reserved
0 = Not Latched, 1 = Latched
Bit 1 = Insert DSP Config
Bit 2 = Buffer Clock PLL Lock Detect
Bit 3 = Viterbi Decoder Lock
Bit 4 = Sequential Decoder Lock
Bit 5 = Rx Test Pattern Lock
Bit 6 = External Reference PLL Lock
Bit 7 = Rx Carrier Level
0 = Not Latched, 1 = Latched
<1> Latched Common
Alarm 1
Bit 0 = -12V Alarm
Bit 1 = +12V Alarm
Bit 2 = +5V Alarm
Bits 3 – 5 = Reserved
Bit 6 = IF SYNTH Alarm
Bit 7 = Spare
0 = Not Latched, 1 = Latched
<1> Latched Common
Alarm 2
Bit 0 = TERR FPGA Config
Bit 1 = CODEC FPGA Config
Bit 2 = CODEC Device Config
Bit 3 = TRANSEC Power Test
Bit 4 = +1.5 V Rx Alarm
Bit 5 = +1.5 V TX Alarm
Bit 6 = +3.3 V Alarm
Bit 7 = +20 V Alarm
0 = Not Latched, 1 = Latched
<1> Backward Alarms Bit 0 = Backward Alarm 1 IDR
Bit 1 = Backward Alarm 2 IDR
Bit 2 = Backward Alarm 3 IDR
Bit 3 = Backward Alarm 4 IDR
Bits 4 – 7 = Reserved
0 = No, 1 = Yes
<4> Error Counter Binary value
<4> Test Error Counter Binary value
<2> Raw BER Mantissa Bytes 1 - 2 = Binary value Raw BER; 896 = 8.96
<2> Corrected BER
<4> Offset Frequency Binary value, 1 Hz steps
<2> Test BER Mantissa Bytes 1 - 2 = Binary value test BER
<1> Raw BER Exponent Byte 3 = Binary value exponent
<1> Corrected BER
Byte 3 = Binary value exponent
Exponent
<1> Test BER Exponent Byte 3 = Binary value exponent
<1> Offset Frequency
If <> 0, '-' offset
Sign
<1> BER/EbNo Status Bit 0 = Raw BER and corrected BER status. 1 = Valid
Bit 1 = Test BER status. 1 = Valid
Bits 2 - 3 = EbNo status, 0 = EbNo is invalid, 1 = EbNo
is valid, 2 = EbNo is smaller than indicated value, 3 =
EbNo is greater than indicated value
Bit 4 = BER Counter Overflow. 1 = Overflow Condition
Bit 5 = Test BER Counter Overflow. 1 = Overflow
Condition
Bits 6 – 7 = Reserved
<1> Buffer Percent Full Binary value representing % buffer full, 0 - 100 in 1%
steps
<1> Input Level Binary value in 1 dB steps, implied sign
<1> Insert Status Fault Bit 0 = Frame lock fault. 1 = Fail
Bit 1 = Multiframe lock fault. Valid in E1 PCM-30 and
PCM-30C. 1 = Fail
Bit 2 = CRC lock fault. Valid in T1ESF, and E1 CRC
enabled. 1 = Fail
Bits 3 – 7 = Reserved
<1> Online Flag Online Switch Status: 0 = Offline, 1 = Online (DMD20 is
always online)
<1> Loss Flag 1 = Loss of IDI Signal, DMD20
<1> Alarm 5 Bit 0 = Trellis Decoder Lock, 1 = Lock
Bit 1 = IFEC Alarm, 1 = fail
Bit 2 = T1/E1 Signaling, 1 = Fail
Bit 3 = TPC Conflict Check, 1 = Fail
Bit 4 – 5 = Spares
Bit 6 = DVB Frame Lock Fault, 1 = Fail
Bit 7 = Spare
<1> Latched Alarm 4 Bits 0 – 6 = Reserved
Bit 7 = Low EbNo
0 = Not Latched, 1 = Latched
<4> Symbol Rate Binary value, 1 sps steps
<1> Latched Alarm 5 Bit 0 = Trellis Decoder Lock
Bit 1 = IFEC Alarm
Bit 2 = T1/E1 Signaling
Bit 3 = TPC Conflict Check
Bit 4 – 5 = Spares
Bit 6 = DVB Frame Lock Fault
Bit 7 = Spare
0 = Not Latched, 1 = Latched
<1> Alarm 6 Bit 0 = LBST LNB DC Current Alarm, 1 = Fail
Bit 1 = LBST LNB DC Voltage Alarm, 1 = Fail
Bit 2 = Ethernet WAN Alarm, 1 = Fail
Bits 3 – 7 = Spares
<1> Alarm 1 Mask Bit 0 = Receive FPGA/Processor Fault
Bit 1 = Carrier Loss
Bit 2 = Multiframe Sync Loss
Bit 3 = Frame Sync Loss
Bit 4 = IBS BER Alarm
Bit 5 = Satellite AIS
Bit 6 = Rx Data Activity
Bit 7 = Rx AGC Level
0 = Mask, 1 = Allow
<1> Alarm 2 Mask Bit 0 = Buffer Underflow
Bit 1 = Buffer Overflow
Bit 2 = Buffer Under 10%
Bit 3 = Buffer Over 90%
Bit 4 = RS Decoder Lock Fault
Bit 5 = RS De-Interleaver Fault
Bit 6 = RS Decoder Uncorrectable Word
Bit 7 = Reserved
0 = Mask, 1 = Allow
Bit 0 = TERR FPGA Config
Bit 1 = CODEC FPGA Config
Bit 2 = CODEC Device Config
Bit 3 = TRANSEC Power Test
Bit 4 = +1.5 V Rx Alarm
Bit 5 = +1.5 V TX Alarm
Bit 6 = +3.3 V Alarm
Bit 7 = +20 V Alarm
0 = Mask, 1 = Allow
<1> ESC Channel 1
Volume
<1> ESC Channel 2
Volume
Binary value, valid in IDR only, +10 dBm to –20 dBm
(two’s compliment)
Binary value, valid in IDR only, +10 dBm to –20 dBm
(two’s compliment)
<1> BER Exponent 6 through 9 for Viterbi, 5 through 7 for Sequential
<11> Rx Circuit ID 11 ASCII characters, null terminated
<1> Rx Terrestrial
0 = Disabled, 1 = Enabled
Loopback
<1> Rx Baseband
0 = Disabled, 1 = Enabled
Loopback
<1> Rx IF Loopback 0 = Disabled, 1 = Enabled
<1> Rx Interface Type 0 = G.703 Bal T1 AMI, 1 = G.703 Bal T1 B8ZS, 2 =
Bit 3 = Insert Clock Activity Detect, 1 = Activity
Bit 4 = External Reference Activity Detect, 1 = Activity
Bit 5 = High Stability Reference PLL Activity, 1 =
Activity
Bit 6 = Reserved
Bit 7 = Low EbNo, 1 = Fail
<1> Common Alarm 1 Bit 0 = -12V Alarm, 1 = Fail
Bit 1 = +12V Alarm, 1 = Fail
Bit 2 = +5V Alarm, 1 = Fail
Bits 3 – 5 = Reserved
Bit 6 = IF SYNTH Alarm, 1 = Fail
Bit 7 = Spare
<1> Common Alarm 2 Bit 0 = TERR FPGA Config, 1 = Fail
Bit 1 = CODEC FPGA Config, 1 = Fail
Bit 2 = CODEC Device Config, 1 = Fail
Bit 3 = TRANSEC Power Test, 1 = Fail
Bit 4 = +1.5 V Rx Alarm, 1 = Fail
Bit 5 = +1.5 V TX Alarm, 1 = Fail
Bit 6 = +3.3 V Alarm, 1 = Fail
Bit 7 = +20 V Alarm, 1 = Fail
<1> Latched Alarm 1 Bit 0 = Receive FPGA/Processor Fault
Bit 1 = Carrier Loss
Bit 2 = Multiframe Sync Loss
Bit 3 = Frame Sync Loss
Bit 4 = IBS BER Alarm
Bit 5 = Satellite AIS
Bit 6 = Rx Data Activity
Bit 7 = Rx AGC Level
0 = Not Latched, 1 = Latched
<1> Latched Alarm 2 Bit 0 = Buffer Underflow
Bit 1 = Buffer Overflow
Bit 2 = Buffer Under 10%
Bit 3 = Buffer Over 90%
Bit 4 = RS Decoder Lock Fault
Bit 5 = RS De-Interleaver Fault
Bit 6 = RS Decoder Uncorrectable Word
Bit 7 = Reserved
0 = Not Latched, 1 = Latched
Bit 0 = -12V Alarm
Bit 1 = +12V Alarm
Bit 2 = +5V Alarm
Bits 3 – 5 = Reserved
Bit 6 = IF SYNTH Alarm
Bit 7 = Spare
0 = Not Latched, 1 = Latched
<1> Latched Common
Alarm 2
Bit 0 = TERR FPGA Config
Bit 1 = CODEC FPGA Config
Bit 2 = CODEC Device Config
Bit 3 = TRANSEC Power Test
Bit 4 = +1.5 V Rx Alarm
Bit 5 = +1.5 V TX Alarm
Bit 6 = +3.3 V Alarm
Bit 7 = +20 V Alarm
0 = Not Latched, 1 = Latched
<1> Backward Alarms Bit 0 = Backward Alarm 1 IDR
Bit 1 = Backward Alarm 2 IDR
Bit 2 = Backward Alarm 3 IDR
Bit 3 = Backward Alarm 4 IDR
Bits 4 – 7 = Reserved
0 = No, 1 = Yes
<4> Error Counter Binary value
<4> Test Error Counter Binary value
<2> Raw BER Mantissa Bytes 1 - 2 = Binary value Raw BER; 896 = 8.96
<2> Corrected BER
Bytes 1 - 2 = Binary value corrected BER
Mantissa
<2> EbNo Binary value, 1 decimal point implied; 700 = 7.00
<4> Offset Frequency Binary value, 1 Hz steps
<2> Test BER Mantissa Bytes 1 - 2 = Binary value test BER
<1> Raw BER Exponent Byte 3 = Binary value exponent
<1> Corrected BER
Byte 3 = Binary value exponent
Exponent
<1> Test BER Exponent Byte 3 = Binary value exponent
<1> Offset Frequency
If <> 0, '-' offset
Sign
<1> BER/EbNo Status Bit 0 = Raw BER and corrected BER status. 1 = Valid
Bit 1 = Test BER status. 1 = Valid
Bits 2 - 3 = EbNo status, 0 = EbNo is invalid, 1 = EbNo
is valid, 2 = EbNo is smaller than indicated value, 3 =
EbNo is greater than indicated value
Bit 4 = BER Counter Overflow. 1 = Overflow Condition
Bit 5 = Test BER Counter Overflow. 1 = Overflow
Condition
Bits 6 – 7 = Reserved
<1> Buffer Percent Full Binary value representing % buffer full, 0 - 100 in 1%
steps
<1> Input Level Binary value in 1 dB steps, implied sign
<1> Insert Status Fault Bit 0 = Frame lock fault. 1 = Fail
Bit 1 = Multiframe lock fault. Valid in E1 PCM-30 and
PCM-30C. 1 = Fail
Bit 2 = CRC lock fault. Valid in T1ESF, and E1 CRC
<4> RFM AGC Voltage Rx AGC Voltage Level in Volts. There is an implied
decimal point. A value of 450 corresponds to 4.50V
<1> RFM AGC Voltage
If <> 0, '-' AGC Voltage
Sign
<4> Carrier-in-Carrier Run
Delay in µsec X 10
Time Delay
<4> Carrier-in-Carrier Run
Offset in KHz X 10
Time Frequency
Offset
<2> Carrier-in-Carrier
Ratio in dB
Ratio
Opcode: <2406h> Query a Demodulator's Latched Alarms
Query Response (8 Bytes)
<1> Latched Alarm 1 Bit 0 = Receive FPGA/Processor Fault
Bit 1 = Carrier Loss
Bit 2 = Multiframe Sync Loss
Bit 3 = Frame Sync Loss
Bit 4 = IBS BER Alarm
Bit 5 = Satellite AIS
Bit 6 = Rx Data Activity
Bit 7 = Rx AGC Level
0 = Not Latched, 1 = Latched
<1> Latched Alarm 2 Bit 0 = Buffer Underflow
Bit 1 = Buffer Overflow
Bit 2 = Buffer Under 10%
Bit 3 = Buffer Over 90%
Bit 4 = RS Decoder Lock Fault
Bit 5 = RS De-Interleaver Fault
Bit 6 = RS Decoder Uncorrectable Word
Bit 7 = Reserved
0 = Not Latched, 1 = Latched
Bit 0 = -12V Alarm
Bit 1 = +12V Alarm
Bit 2 = +5V Alarm
Bits 3 – 5 = Reserved
Bit 6 = IF SYNTH Alarm
Bit 7 = Spare
0 = Not Latched, 1 = Latched
<1> Latched Common
Alarm 2
Bit 0 = TERR FPGA Config
Bit 1 = CODEC FPGA Config
Bit 2 = CODEC Device Config
Bit 3 = TRANSEC Power Test
Bit 4 = +1.5 V Rx Alarm
Bit 5 = +1.5 V TX Alarm
Bit 6 = +3.3 V Alarm
Bit 7 = +20 V Alarm
0 = Not Latched, 1 = Latched
<1> Latched Alarm 4 Bits 0 – 6 = Reserved
Bit 7 = Low EbNo
0 = Not Latched, 1 = Latched
<1> Latched Alarm 5 Bit 0 = Trellis Decoder Lock
Bit 1 = IFEC Alarm
Bit 2 = T1/E1 Signaling
Bit 3 = TPC Conflict Check
Bit 4 – 5 = Spares
Bit 6 = DVB Frame Lock Fault
Bit 7 = Spare
0 = Not Latched, 1 = Latched
<1> Latched Alarm 6 Bit 0 = LBST LNB DC Current Alarm
Bit 1 = LBST LNB DC Voltage Alarm
Bit 2 = Ethernet WAN Alarm
Bits 3 – 7 = Spares
0 = Not Latched, 1 = Latched
Opcode: <2409h> Query a Demodulator's Current Alarms
<1> Alarm 1 Mask Bit 0 = Receive FPGA/Processor Fault
Bit 1 = Carrier Loss
Bit 2 = Multiframe Sync Loss
Bit 3 = Frame Sync Loss
Bit 4 = IBS BER Alarm
Bit 5 = Satellite AIS
Bit 6 = Rx Data Activity
Bit 7 = Rx AGC Level
0 = Mask, 1 = Allow
<1> Alarm 2 Mask Bit 0 = Buffer Underflow
Bit 1 = Buffer Overflow
Bit 2 = Buffer Under 10%
Bit 3 = Buffer Over 90%
Bit 4 = RS Decoder Lock Fault
Bit 5 = RS De-Interleaver Fault
Bit 6 = RS Decoder Uncorrectable Word
Bit 7 = Reserved
0 = Mask, 1 = Allow
Bit 0 = TERR FPGA Config
Bit 1 = CODEC FPGA Config
Bit 2 = CODEC Device Config
Bit 3 = TRANSEC Power Test
Bit 4 = +1.5 V Rx Alarm
Bit 5 = +1.5 V TX Alarm
Bit 6 = +3.3 V Alarm
Bit 7 = +20 V Alarm
0 = Mask, 1 = Allow
<1> ESC Channel 1
Volume
<1> ESC Channel 2
Volume
Binary value, valid in IDR only, +10 dBm to –20 dBm
(two’s compliment)
Binary value, valid in IDR only, +10 dBm to –20 dBm
(two’s compliment)
<1> BER Exponent 6 through 9 for Viterbi, 5 through 7 for Sequential
<11> Rx Circuit ID 11 ASCII characters, null terminated
<1> Rx Terrestrial
0 = Disabled, 1 = Enabled
Loopback
<1> Rx Baseband
0 = Disabled, 1 = Enabled
Loopback
<1> Rx IF Loopback 0 = Disabled, 1 = Enabled
<1> Rx Interface Type 0 = G.703 Bal T1 AMI, 1 = G.703 Bal T1 B8ZS, 2 =
<1> Number Of Events Number of events to query, maximum events that can
be queried is 3
Query Response (1, 77, 153 or 229 Bytes)
<1> Number Of Events Number of events in response: 0 = no events, there is
no additional response data, 1 = 1 event, see event
data for additional response data, 2 = 2 events, see
event data for additional response data, event data will
repeat once, 3 = 3 events, see event data for additional
response data, event data will repeat twice
Event Data (76 Bytes Per Event)
<4> Event Number Actual event number since events were cleared
Events are cleared on a po wer cycle, via the front panel
when the “CLEAR” key is pressed using “ERASE
EVENTS” under the “MONITOR” menu or via the
remote port by using opcode 2C0Ah and selecting 2
delete all events
The event number listed here is the actual event
number since events were cleared. The event buffer
stores up to 100 events; once the 101st event occurs
the first event stored in the event buffer is event
number 2 and the last is event number is 101. As new
events occur they are appended to the end of the event
buffer and events at the beginning of the buffer are
dropped.
Bit 1 = 5 Mbps data rate
Bit 2 = 10 Mbps data rate
Bit 3 = 20 Mbps data rate
Bit 4 = Rx IF Band
Bit 5 = Rx L Band
Bit 6 = Tx IF Band
Bit 7 = Tx L Band
0 = Feature Not Installed, 1 = Feature Installed
<1> Installed Features 2 Bit 0 = Enhanced ASYNC Feature
Bit 1 = IDR Feature
Bit 2 = Sequential Feature
Bit 3 = Reed Solomon
Bit 4 = Custom Reed Solomon Feature
Bit 5 = IBS Feature
Bit 6 = Drop & Insert Feature
Bit 7 = AUPC Feature
0 = Feature Not Installed, 1 = Feature Installed
<1> Installed Features 3 Bit 0 = 8PSK Feature
Bit 1 = 16QAM Feature
Bit 2 = 5 Mbps Turbo Codec Feature
Bit 3 = 20 Mbps Turbo Codec Feature
Bit 4 = OM73 Feature
Bit 5 = DVB Feature
Bit 6 = EDMAC Feature
Bit 7 = 512 Kbps Data Rate
0 = Feature Not Installed, 1 = Feature Installed
<1> Installed Features 4 Bit 0 = 52 Mbps data rate (DMD1050, DMD2050,
DMD2050E and DMD 50 only)
Bit 1 = 52 MHz Turbo Codec Feature (DMD2050,
DMD2050E and DMD 50 only)
Bit 2 = FSK (DMD20LBST and OM20 only)
Bit 3 = 16APSK Feature (DMD2050E Only)
Bit 4 = TPC 7/8 short KHz Feature (Super Card Only)
Bit 5 = R11 Scrambler Feature
Bit 6 = Eth Wan Monitor Feature
Bit 7 = Spare
0 = Feature Not Installed, 1 = Feature Installed
<1> Installed Features 5 Bit 0 = 8QAM Feature
Bit 1 = LDPC 5 Mbps Feature
Bit 2 = LDPC 10 Mbps Feature
Bit 3 = LDPC 20 Mbps Feature
Bit 4 = CNC 512 Kbps Feature
Bit 5 = CNC 1 Mbps Feature
Bit 6 = CNC 2.5 Mbps Feature
Bit 7 = CNC 5 Mbps Feature
0 = Feature Not Installed, 1 = Feature Installed
enterprises
FROM SNMPv2-SMI
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, NOTIFICATION-TYPE, Counter32,
Counter64
FROM SNMPv2-SMI
TEXTUAL-CONVENTION
FROM SNMPv2-TC
OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF;
LAST-UPDATED "200903111600Z"
ORGANIZATION "Comtech EF Data Corp"
CONTACT-INFO
"Customer Service
Postal: Comtech EF Data Corporation
2114 West 7th Street
Tempe, AZ 85281
USA
Tel: (480) 333-2200
Fax: (480) 333-2540
Website: www.comtechefdata.com"
DESCRIPTION
"Comtech EF Data MIB module."
REVISION "200812041600Z"
DESCRIPTION "DMD20 MIB
Object Identifiers description. This documents contents
are subject to change without prior notice. The private enterprise
number 2591 is a unique identifier assigned to Comtech EF Data
by the Internet Assigned Numbers Authority (IANA).
This number is used to uniquely define vendor specific
information such as private MIBs."
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "Power level in tenths of a dBm."
SYNTAX INTEGER (0..10)
RadTransmitPowerLevel ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "Power level in tenths of a dBm.”
SYNTAX INTEGER (-250..0)
RadAupcTransmitPowerLevel ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-2"
STATUS current
DESCRIPTION "Power level in hundreds of a dBm.
SYNTAX INTEGER (-2500..0)
RadReceivePowerLevel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Receive power level in dBm."
SYNTAX INTEGER (-100..0)
RadESCGain ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Sets the ESC channel volume in dB."
SYNTAX INTEGER (-20..10)
RadVoltageLevel ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "Voltage level in tenths of a volt."
SYNTAX INTEGER (0..550)
RadCurrentLevel ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-3"
STATUS current
DESCRIPTION "Current level in milliamps."
SYNTAX INTEGER (0..8000)
ControlType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Represents a boolean control value."
SYNTAX INTEGER { disable(1), enable(2) }
OffOnType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Represents a boolean Off/ON control value."
SYNTAX INTEGER { off(1), on(2) }
InversionType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "Represents a boolean inversion value."
SYNTAX INTEGER { normal(1), inverted(2) }
BerStatusStringType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "8a"
STATUS current
DESCRIPTION "Raw BER status"
SYNTAX OCTET STRING (SIZE (10))
CarrierSweepDelayType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "Sets the carrier sweep delay in secs. There is one implied decimal point.
A value of 215 corresponds to a 21.5 sec sweep delay."
SYNTAX INTEGER (0..65535)
TimeConstantType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "Sets time constants in mSecs for feedback or error accumulators. There is
one implied decimal point.
A value of 1000 corresponds to a 1.000 sec time constant"
SYNTAX INTEGER (0..65535)
EbnoType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-2"
STATUS current
DESCRIPTION "EbNo in db. There is an implied decimal point."
SYNTAX INTEGER (0..2500)
DISPLAY-HINT "d-2"
STATUS current
DESCRIPTION "EbNo alarm threshold. There is an implied decimal point."
SYNTAX INTEGER (0..990)
FirmwareNameType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "15a"
STATUS current
DESCRIPTION "This is the modem firmware name."
SYNTAX OCTET STRING (SIZE (16))
BufferClockSourceType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION "A clock source for the Rx Buffer"
SYNTAX INTEGER {
externalScte(1),
internalSct(2),
externalBnc(3),
rxSat(4),
externalIdi(5)
}
RadTemperature ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1"
STATUS current
DESCRIPTION "Temperature in tenths of a degree Celsius."
SYNTAX INTEGER (-25..75)
FskPassThruCmdType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "65a"
STATUS current
DESCRIPTION "This is an ascii message which will be received and then sent as an FSK
message"
SYNTAX OCTET STRING (SIZE (65))
FskPassThruReplyType ::= TEXTUAL-CONVENTION
DISPLAY-HINT "256a"
STATUS current
DESCRIPTION "This is an ascii reply to an earlier FSK pass thru command"
SYNTAX OCTET STRING (SIZE (256))