Aschex vs. binary values, Command responses – B&B Electronics WLNN-AN(ER,SE,SP.EK)-DP551 - Manual User Manual
Page 28

28
Airborne Enterprise CLI Reference Manual
<integer>
value represented as a decimal integer or as
“aschex” value
in the form 0xhhh…hhh.
one or more pairs of hexadecimal digits with no prefix in the
form hhh…hhh.
<portid>
an I/O port bit number, from 0 to 7.
<IPadrs> - Internet Protocol address string in the format:
nnn.nnn.nnn.nnn; for example: 192.168.10.3.
6.7
ASCHEX vs. Binary Values
Data can be sent to the module as either binary data or a hexadecimal
representation of the actual data being transmitted.
When a LAN device or serial port Host issues a pass command, the data is
transmitted as binary data. By comparison, when the command putget or
putexpect is issued, the senddata content must be encoded as ASCII
hexadecimal digit pairs. The data is translated across the Module and received
as an ASCII representation of the actual data. This is true whether the
transmission initiates from the LAN device or from the Host.
For example, the digits 31 correspond to the ASCII character 1. If you issue a
putget or putexpect command with the senddata value of 314151, the
destination receives the ASCII characters 1, A, and Q.
6.8
Command Responses
The Module responds to CLI commands with a response indicating whether the
CLI command was executed successfully. All responses are terminated by
Multiline responses have each line terminated with
terminated by
After the Module executes a CLI command successfully, it returns the response:
OK
Otherwise, it returns an error response. Error responses are returned in the
following general format:
Error 0xhhhh: error text
In the response the aschex value is the error code. A summary of error code can
be found in section 0.
The TCP CLI interface by default echoes back CLI session input. It is possible to turn
this feature off by issuing the telnet-echo disable command.