The Dialog of Device Parameters
In the General Settings section, the following parameters are set (see also Operations in Dialogs of Parameters ):
Comment – a comment to the device
Available – if TRUE, the device and its components are executed in real time; if FALSE, are not executed
Device type – a type is selected in the following list:
The Device type parameter is available only in the node creation dialog.
PROGRAM – a PROGRAM-type device only executes a user script and processes tags.
A PROGRAM-type device can contain only SERVER_ONLY tags.
MODBUS – a device of exchange via MODBUS.
A MODBUS-type device can contain MODBUS and/or SERVER_ONLY tags.
Address – a device address
Response time (ms) – maximal time to wait for a device reply; the default value is 1000
Attempts to reconnect on error – number of repeated attempts to connect with the device after a connection error; the default value is 3
Reconnect timeout (s) – timeout of a repeated connection with the device; the default value is 10
Node reinitialization on error – if TRUE: if a preset number of attempts to connect with the device is used up, either the socket is re-opened or the COM port is closed/opened, depending on a node type (network or RS)
Request period – a period of device inquiry; the default value is 1000 (the period dimension is set by the Request period dimension parameter)
Request period dimension – a dimension of the Request period parameter (ms, s, min or h); the default value is ms
Initial phase – time between switching the server to the run-time mode and the first inquiry of the device. This parameter is set as a shift with respect to the day beginning. The setting is designed to separate the polling of devices by time, for example - need to poll the device once per minute in 15 second increments. The request period is set to a 1 minute, the Device1 inital phase - 15 seconds, the Device2 - 30 seconds. The Device1 will be polled at 15 seconds of every minute, the Device2 at 30 seconds of every minute. Setting Start after run should be False- otherwise all devices will be polled at start, and only then they will start polling according to the polling phase. A dimension is set by the Phase dimension parameter, the default value is 0.
Phase dimension – a dimension of the Initial phase parameter (ms, s, min or h); the default value is ms
Start after run – if FALSE, an inquiry is started an inquiry cycle time later the server is launched
Request delay after response – after receiving the response, the OPC server sends a new request after a specified time. This parameter is used when working with devices with a slow buffer. .
Byte order - opens the byte swapping editor (see Setting the Sequence of Bytes).
In the Script section, the following parameters are set:
Script execution – enable/disable script execution
Edit script code – a value cell of that parameter contains the button 
to open the script editor
If extra properties are set for the device (see Setting Extra Properties ), their descriptions are displayed (and their values can be changed) in the Additional properties section.
If a node type is COM, the dialog of device parameters contains the Modem extra settings section, in which the following parameters are set:
Own phone number – if TRUE, the following parameter is available:
Phone number – own phone number.
In addition to the sections General Settings and Script, the dialog contains the Queries Settings section where the following parameters are set:
Maximal number of HOLDING registers in read request – this parameter is destined to limit number of registers requested in the Holding Registers region (the function 0x03) in one read request. Some devices themselves limit number of registers in one reply. Division of a long request to short ones improves noise immunity (especially when transferring Modbus RTU via radio channels). As a rule, Modbus TCP requests do not need to be limited.
Maximal number of INPUT registers in read request – this parameter is destined to limit number of registers requested in the Input Registers region (the function 0x04) in one read request. Some devices themselves limit number of registers in one reply. Division of a long request to short ones improves noise immunity (especially when transferring Modbus RTU via radio channels). As a rule, Modbus TCP requests do not need to be limited.
Do NOT use WRITE_SINGLE_COIL (0x05) – this parameter defines what function must be used to write into a tag of the Coil region - 0x05 or 0x0F
Do NOT use WRITE_SINGLE_REGISTER (0x06) – this parameter defines what function must be used to write into a tag of the Holding Registers region - 0x06 or 0x10;
Maximal admissible interval between addresses in read request – maximal admissible interval between addresses in one read request. For example, registers 0, 1, 2, 4 and 5 are requested. If the parameter equals 0, two requests are formed to poll the registers (0-2, 4-5). If the parameter is equal to 1 or greater, one request is formed to poll the registers (0-5, and the unused register 3 will be ignored when analyzing the reply). Increasing the parameter decreases number of requests and speeds the poll up (and this is useful for the poll via Modbus TCP) but makes the reply frame longer (and this is harmful for the poll via Modbus RTU). Note that some Modbus devices themselves limit number of parameters transmitted in on reply.
Use preamble – enable/disable the preamble that is set by the Preamble parameter
Preamble – a value that is set for this parameter is transferred prior to a standard MODBUS frame. To enable/disable that mechanism, use the Use preamble parameter.
There are no additional sections and parameters in the dialog.