Comtech EF Data CDM-625 - 19.4 Configuring the CDM-625 for Carrier ID Operation

CDM-625 Advanced Satellite Modem Revision 13
Carrier ID (MetaCarrier®) MN-CDM625
19–3
The entire CID message is broken into 18 packets containing 122 bits (formatting, FEC and user
information) for a total message length of 2,196 bits for the transmission of the MetaCarrier.
Each packet of the MetaCarrier message carries 32 bits of CID information data. However, the
MAC address is sent at a higher rate (more often), so that upon reception of a frame that is
comprised of three (3) packets, the MAC address may be obtained.
The data rate of messages being carried in the MetaCarrier is shown before spreading is applied
and the associated time to send a complete CID message (including the framing and FEC). The
time for a complete message is only valid once the MCDD-100 has achieved lock to the
MetaCarrier that may cause the stated times to be longer:
Therefore, the time for the CDM-625 with MetaCarrier to insert a complete CID ID sequence is
as follows. Note that the time for unique ID may be shorter than shown, since upon achieving
lock to the MetaCarrier, the unique ID is made available immediately since MetaCarrier lock
requires the reception of three full packets to declare lock.
Embedded
MetaCarrier rate
CID Data Rate
Time for Complete
Message
Time for Unique ID
224 kcps 56 bps 41 seconds 6.9 seconds
112 kcps 28 bps 82 seconds 13.8 seconds
56 kcps 14 bps 164 seconds 27.6 seconds
28 kcps 7 bps 328 seconds 55.2 seconds
14 kcps
3.5 bps
656 seconds
110.4 seconds
19.4 Configuring the CDM-625 for Carrier ID Operation
Carrier ID operation requires that you first enable Carrier ID feature operation, and then create
a MetaCarrier Custom Message. All other parameters (center frequency, symbol rate, and the
CDM-625’s MAC address) are set automatically. The CDM-625 provides several means for
configuring Carrier ID operation:
• Local Control via the CDM-625 Front Panel keypad and VFD.
• Remote Control with a user-supplied PC via the
o CDM-625 Web Server (HTTP) Interface using a compatible Web browser.
o Serial-based or Telnet-based Remote Control Interface using a terminal
emulation program or Windows Command-line.
o Ethernet-based Simple Network Management Protocol (SNMP) using a Network
Management System (NMS) and Management Information Base (MIB) File
Browser.