Attributes to Configure in the Comm-Port Point

Attribute Name Description
connection info

This table contains the following information:

Field Number Field Name DE Type Possible Values
0 node rtBytes20 (see below)
1 object rtBytes20 (see below)
2 data rtBytes4 (see below)
3 table number rtUInt16 (see below)
4 bit rtInt16 (see below)

Where:

Field Name Description
node The DEC-Net node string. This can be a name or an ASCII string representing the node address (e.g. 1.16 or GEM00).
object This contains the object name or number (e.g. GEMSERVER0).
data This is used to hold the single upper case ASCII character representing the table letter. This table (with "table number") is used to indicate whether this PLC is the primary (one) or standby (zero).
table number This is the table number for the primary/standby indicator.
bit This is the bit within the specified table that indicated primary/standby status. Set this to minus one to use the whole table word.
max tbl count This attribute specifies the maximum number of table numbers to request for in a single request. The absolute maximum of 110 is silently enforced. If this value is zero the maximum of 110 will be used. This allows the user to control how large the requests/responses are.
debug device UNIX

The device file where debug information is to be printed. The full path must be provided; for example "/dev/ptyqf". In addition to a device file, the following key words are recognized: "stdout" and "stderr"; which send debug information to the specified file pointer.

[warning] If a pseudo-terminal device is to be used, specify the master device; otherwise the driver will be hung on the open waiting for the master side of the pseudo-terminal to be opened.

 

[caution] If a pseudo-terminal device is used, the scan task must be started before any process tries to open the slave device; otherwise no debug information will be printed.
Windows

This specifies a "named pipe" that will be created on the server machine. Client applications can then make connections to this "named pipe" to receive debug information. A separate thread is created to handle each client. There is a maximum of six client connections allowed. Additional clients trying to connect will fail.

Since this is a "named pipe", clients can connect from other machines on the network.

See the tesserNet Scan Debug Utilities for freely distributable client applications.

[warning] Depending on the network connection speed, some debug data may be lost. Tests here, show that for a full 10 Mbit/sec connection, no data is lost.