Comtech EF Data MCED-100 - Manual (Page 59)

MCED-100 MetaCarrier Embedding Device Revision 1
Serial-based Remote Product Management MN-MCED100
5–3
When the user‐supplied terminal emulator program is configured correctly, upon power‐up of the MCED‐100, the Serial Interface Info
Screen appears, followed by the Serial Interface command prompt MCED‐100>. From here, type “help[cr]” or “?[cr]” (without the
quotes) to display the MCED‐100’s available commands and queries, and to review instructions for using the interface.
5.2 Remote Commands and Queries Overview
5.2.1 Basic Protocol
In an EIA‐232 configuration, the Controller device is connected directly to the Target device via a two wire‐plus‐ground connection. All data
is transmitted in framed packets as asynchronous serial characters, suitable for transmission and reception to the Controller using a
universal asynchronous receiver/transmitter (UART). Controller‐to‐Target data is carried via EIA‐232 electrical levels on one conductor, and
Target‐to‐Controller data is carried in the other direction on the other conductor:
• Controller‐to‐Target: The Controller device (e.g., the user PC/Serial Interface) is used to transmit instructions (commands) to –
or to request information from (queries) – the Target device (i.e., the MCED‐100).
• Target‐to‐Controller: The Target, in return, only transmits response information to the Controller when specifically directed by
the Controller.
For Serial Remote Control, all issued commands (Controller‐to‐Target) require a response (Target‐to‐Controller). This response is either
to return data that has been queried by the Controller, or to confirm the Target’s receipt of a command to change the Target’s
configuration.