Attribute Name | Description | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
transmission mode | Specifies the communication mode as either ASCII (zero) or RTU (one). | |||||||||||||||||||||
socket info | Specifies the host and service name to use when making a socket connection. The entry to use is specified in the "socket index" attribute. This table contains the following:
Where:
|
|||||||||||||||||||||
socket index | Specifies the index into the "socket info" table of the entry to use. | |||||||||||||||||||||
max data length | The request(s) will be formatted such that the number of data bytes returned from the RTU will not exceed this number. This value is only read on startup. The minimum value for this is four. If the value is less than this minimum, it will be silently set to the minimum. | |||||||||||||||||||||
debug device | UNIX | The device file where debug information is to be printed. The full
path must be provided; for example "
|
||||||||||||||||||||
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.
|