...
Console Parameters
CHARON-AXP console line TTA0 (COM1COM2) has the following parameters:
Parameter | Type | Value | |
---|---|---|---|
communication | Text string |
| |
line | Identifier | This parameter is used to connect a particular serial line mapping interface to the controller. Example:
|
All the values in this table are case insensitive.
...
Parameter | Type | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
line | Text string | A defined TTY port on host system:
| ||||||||||
baud | Numeric | Forces the baud rate of the corresponding TTY port to a specified value.The variety of supported values depends on the underlying physical communication resource (TTY port). The most widely used values are: 300, 1200, 9600, 19200, 38400. Example:
| ||||||||||
break_on | Text string | Specifies what byte sequences received over the physical serial line will trigger a HALT command. This parameter works only for the console line. Specify the following values: "Crtl-P", "Break" or "none" ("none" disables triggering a HALT condition). Example:
| ||||||||||
stop_on | Text string | Specifies what byte sequences received over the physical serial line will trigger a STOP condition. The STOP condition causes CHARON-AXP to exit. Specify either “F6” or “none” ("none" disables triggering a STOP condition). Example:
Setting "F6" triggers the STOP condition upon receipt of the " | ||||||||||
log | Text string | A string specifying a file name to store the content of the console sessions or a directory where the log files for each individual session will be stored. If an existing directory is specified, CHARON-AXP automatically enables creation of individual log files, one for each session using the same scheme as used for the generation of the rotating log files. If the "log" parameter is omitted, CHARON-AXP does not create a console log. Examples:
.
|
Example of mapping a console line to a host physical serial line:
...