Comtech EF Data MBT-4000B - Manual (Page 41)

Multi-Band Transceiver System Revision 0
Remote Command MN/MBT4000B.IOM
A–5
2. From Target-to-Controller, the only permitted values are:
= (ASCII code 61)
? (ASCII code 63)
! (ASCII code 33)
* (ASCII code 42)
# (ASCII code 35)
They have these meanings:
The ‘=’ code (target to controller) is used in two ways:
First, if the controller has sent a query code to a target (for example MUT?, meaning ‘is
mute enable or disable?’), then the target would respond with MUT=x, where x
represents the state in question, 1 being ‘enable’ and 0 being disable.
Second, if the controller sends an instruction to set a parameter to a particular value, and
providing the value sent in the argument is valid, then the target will acknowledge the
message by replying with MUT= (with no message arguments).
The ‘?’ code (target to controller) is only used as follows:
If the controller sends an instruction to set a parameter to a particular value, and if the
value sent in the argument is not valid, then the target will acknowledge the message by
replying (for example) with MUT? (with no message arguments). This indicates that
there was an error in the message sent by the controller.
The ‘*’ code (target to controller) is only used as follows:
If the controller sends an instruction to set a parameter to a particular value, and if the
value sent in the argument is valid, however, the target is in the wrong mode (e.g.,
standby mode in redundancy configuration) that it will not permit that particular
parameter to be changed at that time, then the target will acknowledge the message by
replying (for example) with MUT* (with no message arguments).
The ‘!’ code (target to controller) is only used as follows:
If the controller sends an instruction code which the target does not recognize, then the
target will acknowledge the message by echoing the invalid instruction, followed by the !
character. Example: XYZ!
The ‘#’ code (target to controller) is only used as follows:
If the controller sends an instruction code which the target cannot currently perform
because of hardware resource issues, then the target will acknowledge the message by
echoing the invalid instruction, followed by the # character.