User Manual

MTX3/MTX5-D/MRX7-D/XMV Series/EXi8/EXo8 Remote Control Protocol Specications V3.2.0 rev11
52
4. Command Sequence
4.1. Communication start sequence
The amount of time for the controller and the controlled device to start is different.
Remote control is an act of controlling the controlled device from the controller, so the controller must wait for the controlled device to
become ready.
The controller needs to wait using the sequence below.
1. If an Ethernet connection is required, the remote controller needs to establish a logical session, with the MTX device(s) based
on IP address(es) and port number.
(This is not necessary for a connection that only needs to be connected physically, as in RS-232C.)
2. After the session is established, the controller sends devstatus commands at 1 second or longer intervals.
3. If "OK devstatus runmode" is returned, the controller should check the information.
4. If the controller determines that the controlled device is in normal running mode, the controller can start sending command
strings to change parameter value and preset etc. If the controlled device is not in normal running mode, the controller continues
trying.
Note: In order to establish remote control communication, the external controller must send [devstatus runmode] command to the
device and await response. When the device responds as [OK devstatus runmode "normal"], the device is ready to receive
commands.
Remote controller
Establish communication path to
controlled device.
* If the communication path is
already established, the
controller sends devstatus
runmode at 1 second or longer
intervals until a result
notification is returned.
The controller checks the run
mode included in the result
notifications to see if the
device is ready to start remote
control communication.
The device may also actively
send change notifications, so
the controller must monitor
both result and change
notifications.
Controlled device
Connection detected.
Time
devstatus runmode
devstatus runmode
OK devstatus runmode "normal"
devstatus runmode
devstatus runmode
........
1 second or longer intervals
1 second or longer intervals
The reason for using such a sequence is provided below.
Example when the controller starts earlier than the controlled device
devstatus runmode
devstatus runmode
devstatus runmode
Remote controller
Normally running
Connection unknown
Waiting to start
Controlled device
Connection detection
Connected physically
........
OK devstatus runmode "normal"
Device starting
Device normal running