From OpenSCADAWiki
Using this tab you can set:
- The state of the controller object, as follows: Status, "Enabled", "Running" and the name of the storage containing the configuration.
Manual restart of the enabled controller object causes the force reformation of the acquisition blocks.
- Identifier, name and description of the controller.
- The state "Enabled" and "Running", in which the controller object must be translated at boot.
- Policy of scheduling and priority of the data acquisition task.
- ModBus protocol, used for requesting the real device (TCP/IP, RTU or ASCII).
- Address of the output transport using the unified connection with navigation. Default port of the ModuBus/TCP is 502. The field may be set to empty and be changed at the runtime. Format of the address is:
- "{TrModule}.[out_]{TrID}[:{TrAddr}]" — typical output with automatic creation TrID at it missing and providing TrAddr;
- "{TrModule}.in_{TrID}:{RemConId}" — initiative input with the connection identifier in RemConId.
- ModBus destination node. In the case of protocols RTU and ASCII this is the unique address of the physical device, and when TCP/IP this is the identifier of the unity.
- Merging of the data fragments. Standard functions 1-4 let to request at once multiple adjacent registers or bits. This strategy often allows to optimize the traffic and time. However, the required registers are not always located adjacent to each other, this option allows you to gather them in blocks of up to 100 registers, or 1600 bits.
- Installing of this parameter must be approached with caution, since not all devices support access to the registers between fragments.
- Using the multi-items writing functions (15, 16). Instead one-item writing will be used the multi-items functions.
- Asynchronous write. Enables asynchronously writing of the changes to the controller, in the general acquisition cycle and after the data acquisition itself, blocking of reading the written values on one cycle (before the writing buffer clearing).
- This mode also prevents for loss the writing data at the connection loss and the wrote data will be transmitted just the connection will be restored.
- Omit cycles for read back of written. Can be useful for PLC which applying the changes not fast and they are processed in some significant time depending on the PLC load. So, the cycles value then specifies count of the omitting read cycles before reading back the changed value, preventing the value twinkle.
- Timeout of connection in milliseconds. Specifies the time interval during which the answer is expected. If there is zero waiting time the transport waiting time by default is used. Allows taking into account individual properties of the controller in the common network.
- Timeout of restore in seconds. Specifies the time interval after which the re-attempt of the request to previously inaccessible device is done.
- Request tries for the protocols RTU and ASCII. Indicates the number of attempts by the repetition of the request in case of incomplete or damaged answer.
- Maximum size of the request block in bytes, useful for controllers with such limits.