Versions Compared

Old Version 13

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Kirill Nikolaev (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TopConfPageTOCTopConfPage
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

Table of Contents
excludeTable of Contents

Back to the Table of Contents

General Description

CHARON-AXP offers two-port serial console on all supported AXP models.

...

set COM2 alias=TTA0

Refer to Mapping Serial line controllers to system resources 346554455 for details of mapping.

...

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

General parameters

CHARON-AXP console lines COM1 and COM2 have the following parameters:

(info) All the values in the following tables are case insensitive.

alias

Parameteralias
TypeIdentifier
Value

This parameter is used to set an useful name for COM1 or COM2 ports.

Usually it is "OPA0" for COM1 and "TTA0" for COM2

Example:

set COM2 alias=TTA0


communication

Parametercommunication
Type

Text string

Value

  • "ascii" - for connection to terminals  (default)

  • "binary" - for binary (packet) protocols, which are used mainly for communicating with PLCs

baud

...

Parameterlog_file_size
TypeText string
Value

If log rotation is enabled, the log_file_size parameter determines the log file size threshold at which the log is automatically rotated.

  • "unlimited" or "0" (default) - the feature is disabled
  • "default" - default size is used (4Mb)
  • <size>[KMG] - size of the current log file in bytes with additional multipliers:

    • K - Kilobyte - multiply by 1024

    • M - Megabyte - multiply by 1024*1024

    • G - Gigabyte - multiply by 1024*1024*1024

Examples:

set OPA0 log_file_size="default"


set OPA0 log_file_size=10M

(warning) Minimum log file size is 64K, maximum is 1G. Setting size less then 64K effectively makes the log file unlimited.

host

Value
Parameterhost
TypeText string

A remote host’s IP address or hostname (and optionally a remote TCP/IP

port

...

set OPA0 host="<host-name>[:<port-no>]"

If the "<port-no>" is not specified, the virtual serial line uses the TCP/IP port number specified by the "port" parameter (see below).

port

Parameterport
TypeNumeric
Value

The TCP/IP port number for the virtual serial line. A virtual serial line always listens on this port for incoming connection requests.

If multiple virtualized machines are running on a server, ensure the port number is unique across the platform.

...

Parameterapplication
TypeText string
Value

A command line for calling some host application for communication to CHAARON Charon on a given COM line.

Typically this parameter is used for mapping COM1 or COM2 ro or some "xterm" terminal emulator

Example:

set OPA0 application = "xterm -title OPA0 -e telnet 127.0.0.1 10003"

Notes on

...

"port" and "application" parameters

...

Use the combination of "port

...

" and "application" parameters as follows to connect a 3rd party terminal emulator or similar program.


set COM1 alias=OPA0 port=10003 application="xterm -title OPA0 -e chterm -h 127.0.0.1:10003"


In this example CHARON-AXP OPA0 console connects to port 10003 of localhost ("127.0.0.1") and at the same time it starts "xterm" with parameters "-title OPA0 -e chterm -h 127.0.0.1:10003", instructs it to connect to the port 10003 of the host with TCP/IP address "127.0.0.1" (localhost)  

     

It is possible to specify a port on a remote host (note that CHARON always acts as a server). The syntax is:

set COM2 alias=TTA0 host="192.168.1.1:20000" port=10000

In this example CHARON-AXP accepts connection on local port 10000 and connects to remote port 20000 of a host with TCP/IP address "192.168.1.1"

Note: the examples above are mainly used for inter-CHARON communications. They are used to connect CHARON-AXP to an application that communicates to CHARON-AXP as described below.

Example of two CHARON systems connected to each other:

On host "A":

...


On host "B":

...

On these two hosts, executing CHARON-AXP, the two TTA0 lines connect to each other, thus creating a "serial" cable between the two emulated Alphas. The sequential order in which the instances of CHARON-AXP are started makes no difference.

Back to the Table of Contents

Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

Mapping Serial line controllers to system resources

...

Parameterline
TypeText string
Value

A defined TTY port on host system:

SyntaxDescription
"/dev/tty<N>"Virtual serial lines
"/dev/ttyS<N>"Onboard serial lines
"/dev/ttyUSB<N>"Modem or USB serial lines adapters
"/dev/tty<XXX>"Proprietary (depending on a driver) devices such as DIGI or MOXA cards


Note

A specific account for running CHARON ("charon") does not allow usage of physical consoles "/dev/tty<N>" as CHARON consoles. If you plan to map CHARON console to "/dev/tty<N>" use only "root" account for CHARON running.

...


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc

"ttyY" notation specifics

...

MappingTypeCommentary

"/dev/tty<N>"

where N is from 0 to 11

Linux virtual tty

Those tty devices must be free from the Linux "getty/mgetty" and similar programs (specified in "/etc/inittab")

Example:

"/dev/tty1"


"/dev/ttyS<N>"

where N is a number

Onboard serial lines

Example:

"/dev/ttyS1"


"/dev/tty<XXX>"

where XXX is a complex letter/number notation

Proprietary (depending on a driver) devices 

Example for a first port of a MOXA card:

"/dev/ttyR01"

Example for a first port of a DIGI card:

"/dev/ttyaa"


"/dev/ttyUSB<N>"

where N is a number

Modem or USB serial lines adapters

Example:

"/dev/ttyUSB1"

...


Include Page
KBCOMMON:DOC-GoToToc
KBCOMMON:DOC-GoToToc