Remote Port Packet Structure; Table A-5. Link Level Protocol Message Block - Comtech EF Data Radyne RCS20 Installation And Operation Manual

RCS20 M:N Redundancy Switch Revision 15
Remote Operations MN-RCS20 and CD-RCS20
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 message block is shown in Table A-5, Link Level Protocol Message Block.

Table A-5. Link Level Protocol Message Block

SOURCE DESTINATION
SYNC COUNT ADDRESS ADDRESS FSN OPCODE DATA BYTES CHECKSUM
1 byte 2 bytes 1 byte 1 byte 1 byte 2 bytes (count) bytes 1 byte
A.2

Remote Port Packet Structure:

The RLLP Remote Port Packet 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> = Number of bytes in the <DATA> field, (2 bytes).
<SOURCE ID> = Identifies the address of the equipment from where the message originated, (1 byte).
<DEST ID> = Identifies the address of the equipment where the message is to be sent, (1 byte).
<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).
A–11