Professional Documents
Culture Documents
The PC Server software is intended to plug into a global data base and
communicate with an ASCII terminal client or PC Client via a serial port.
The client can request periodic data from the data base, issue control
commands, and request special information.
Conventions
All commands and options are case-insensitive. Blanks before the command
are ignored. Keywords must begin with a letter or digit.
Commands from the terminal or PC client are echoed back except that Carriage
Return characters are expanded to the two characters Carriage Return and
Line Feed.
Escape
When the PC Server sees the escape character, it does not echo it
back. First it terminates all response transmissions in progress and
then sends
@^ '>'
Command repeat
SHELLS
The IOE2 and EDGE firmware require the use of terminal shells to utilize all available
terminal commands. IOE1 and IOGs do not require the use of terminal shells. Shells break
up the available terminal commands into groups of commands that perform similar
functions. For example the Core98 shell contains commands for interacting the RTU’s
global database.
To enter a shell:
IOE2
COMMAND: <name of shell>
EDGE
COMMAND: SHELL <name of shell>
To exit a shell:
COMMAND: EXIT
COMMANDS AND RESPONSES
Listed below are the set of commands a PC client can issue to the PC Server.
This command tells the PC Server to send data of the type specified for the point number.
ACCUM accumulations
ANALOG analog and analog upset values
BINARY binary values
STATUS status and status upset values
-NNNN indicates send multiple point data beginning with <point number>
and ending with the point numbered NNNN. Responses are limited
to 20 lines no matter how many points are specified.
<point number> ':' ' ' <value> ' ' ' ' '@' <year> ':' <halfday>
':' <hd_sec> ':' <ms> @^
COMMAND: BINOUT <point number> <signed 'S' | unsigned 'U'> <0x style hex value>
#...BR..DPS.B/B.A/S..CTS.RTS.DCD..ICTO..RXTO..OWNER... @^
1 9600 8N1 Byt Asy 25 2 0 5 20 DNPCLnkl @^
where
BR is baud rate
DPS is number of data bits, parity, number of stop bits
B/B is bit or byte oriented
A/S is asynchronous or synchronous
CTS is clear-to-send delay which can be no of milliseconds or hardware
RTS is request-to-send hold delay after last bit leaves
DCD is delay following receipt of data carrier detect hardware signal
ICTO is inter-character timeout
RXTO is receive-to-transmit minimum delay time
OWNER is name of process using comm port
COMMAND: READ <0x style hex start address> [0x style hex number bytes]
This command tells the PC Server to retrieve data from the specified
flash memory area for the user to view. The "Number of bytes" parameter
is optional and the default value is 128 bytes.
COMMAND: REASON
This command tells the PC Server to display the reason for the most
recent start up or re-boot operation.
Code Reason
-------- --------------------------------------------------
0 unknown or power up
1 one or more tasks failed to register
2 C++ new operator failed
3 voyager VOYOP_RESTART_NODE from my node
4 voyager VOYOP_RESTART_NODE from another node
5 0x80 control reboot command from my node
6 0x80 control reboot command from another node
7 writing to flash from my node
8 writing to flash from another node
9 unable to find config file in flash
10 registration and task config do not match
11 not enough queues requested
12 illegal registration
13 re-boot initiated by operator from Terminal
14 re-boot requested from master station
15 process detected something it did not like
16 process's private reason #0
17 process's private reason #1
18 process's private reason #2
19 process's private reason #3
20 process's private reason #4
21 process's private reason #5
22 process's private reason #6
23 process's private reason #7
24 process's private reason #8
25 process's private reason #9
26 process's private reason #10
27 process's private reason #11
28 process's private reason #12
29 process's private reason #13
30 process's private reason #14
31 process's private reason #15
128-223 watchdog timed out a task - subtract 128 to get task number
225 Nucleus - not enough memory to init
226 Nucleus - no tasks defined
227 Nucleus - invalid partition size
228 Nucleus - invalid queue item size
229 Nucleus - memory slicked by someone
230 Nucleus - begining of the task's stack was overwritten
231 Nucleus - error detected in TASK_CONFIG_BLOCK
This command tells the PC Server to re-boot the rtu into the specififed
software operating mode. If the software operating mode is not specified
the the rtu will be rebooted into the current software operating mode.
These commands tell the PC Server to retrieve and display the current
software operating mode.
They also tell the PC Server to list all of the tasks and show whether
they are running or stopped, and if they are stopped what caused the
stop.
The optional node_num will returns similar, but not the same information
from the specified node.
COMMAND: STRAPS
This command displays the setting of the hardware jumper straps (links).
The response on an IOE/IOB module looks like one of this
COMMAND: HELP
There are three levels 0, 1 and 2. At level 0, the user cannot issue
controls or setpoints and cannot read or set passwords. At level 1,
the user can do everything that can be done at level 0 plus he can issue
controls and setpoints. At level 2, the user can do everything that
can be done at level 1 plus he can view or change the passwords.
To enter the next higher security level, the command must include the
level number and password arguments. To drop to a lower security level,
the command only needs to include the security number argument.
COMMAND: PASSWORD
COMMAND: IPCONFIG