Document No. ZD24010 Rev. B2
NAC1 User Manual
29 of 38
General notes:
1.
The setup commands can be sent in one of the following formats:
o
Command<space><data><CR>
o
Command<space><data><LF>
o
Command<space><data><CR><LF>
o
Command<space><data><LF><CR>
Note: The command parsing will start right after the <CR> or <LF>.
In the 3
rd
and 4
th
forms above the <LF> and <CR> will be ignored.
2.
In case of CLI commands with several parameters, each parameter is separated from each
other with the comma sign (',').
3.
Parameters can be skipped by typing the ',' only without any value following them. In the
case where there is no intention to change the trailing parameters, they can be simply
omitted.
4.
All values should be in ASCII format.
5.
If the communication is with a PC, the recommendation is to work with
SEO N
.
6.
If the communication is interactive with a user (for example communication using a Hyper
Terminal) the recommendation is to work with
SEO Y
.
7.
a. When
SEO N
is applied, the output (response from the unit) to all CLI commands will be in
the following form:
Command<space><data><CR><LF>
b. When SEO Y is applied, the output (response from the unit) to all CLI commands will be
in the following form:
Command<CR><CR><LF> Command<20><data><CR><LF><3E><20>
Note: The first Command<CR> is the ECHO of the received command.
8.
Error messages:
a. If the operator enters characters that do not match one of the specific CLI commands the
following error message will be reported: "Unknown command".
b. If the operator enters characters that do not match one of the parameters in a CLI
command the following error message will be reported: "Invalid command"
9.
Case sensitivity: Both commands and their parameters can be entered in uppercase or
lowercase letters.
