Table of Contents
Advertisement
From Target-to-Controller, the only permitted characters are:
Character
=
(ASCII code 61)
?
(ASCII code 63)
!
(ASCII code 33)
*
(ASCII code 42)
#
(ASCII code 35)
$
(ASCII code 36)
7.2.2.6
Optional Message Arguments
Arguments are not required for all messages. Arguments are ASCII codes for the characters '0' to '9' (ASCII codes 48 to 57), period '.'
(ASCII code 46), and comma ',' (ASCII code 44).
Serial-based Remote Product Management
Definition
This character is used in two ways:
If the Controller sends a query to the Target – for example: MUT? meaning "what's the current state of the MUTE function?", the
a.
Target would respond with MUT=x, where x represents the state in question: 1 being enabled, and 0 being disabled.
b.
If the Controller sends an instruction to set a parameter to a particular value, and the value sent is valid, the Target acknowledges
the message and responds with MUT= (with no message arguments).
If the Controller sends an instruction to set a parameter to a particular value, and the value sent is not valid, the Target then
acknowledges the message and responds with, for example, MUT? (with no message arguments). This indicates that there was an
error in the message sent by the Controller.
If the Controller sends an instruction code that the Target does not recognize, the Target responds by echoing the invalid instruction,
followed by !
Example: XYZ!
If the Controller sends the command to set a parameter to a particular value, and the value sent is valid BUT the router will not permit
that particular parameter to be changed at present, the Target acknowledges the message and responds with, for example, MUT* (with
message arguments).
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. This response can only occur if the
operator sends two or more 'hardware configuration' type commands without allowing adequate time between commands for the
hardware to be configured. For example, if the operator issued commands to change both the frequency and the attenuation with less
than 100 milliseconds between commands, and if this response is returned, then the command has not been accepted and the operator
must resend the command.
The Target acknowledges the message indicating that this block converter is not installed.
MBT-5000A L-Band Up/Down Converter System
7–7
Revision 1
MN-MBT-5000A
Advertisement
Table of Contents
