Attributes to Configure in the Comm-Port Point

Attribute Name Description
optimize This attribute determines whether reads from the remote RTAP environment will use direct address or symbolic addresses (as specified in the scan input table, see Fields to Configure in the Scan Input Table). Set this to zero if the attribute being read may change (ie. deleted and re-created) while the scan task is running.
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.