|Active after start||If checked, then the group becomes active immediately after the start. |
This configurator sets the initial value of the property ActiveGroup.
|Update from server at server change||If checked, then automatic data refresh from the server right after startup is enabled (the data to be refreshed are defined on the Data page and the data in the PmData object containing ExtOpcClient). |
This configurator sets the initial value of the property Update.
|Minimum update rate [msec]||Rate in milliseconds. At the automatic update the OPC server won't send data faster than it is set here. |
This configurator sets the initial value of the property UpdateRate.
|Deadband [%]||At the automatic update the OPC server won't send data that changed less than entered here. |
This configurator sets the initial value of the property Deadband.
|"onDataReceive" event||onDataReceive event calling type. The OPC server usually sends multiple data items simultaneously and here it is defined for which received variables the event will be fired and what will be saved into the pEvent.Items parameter.|
A = call the event for all registered variables (in this object and also in other PmData objects) - The event fires for all variables that have received values. These are:
- variables defined in PmData object that have ExtOpcClient data extension registered into this PmOpcClientData object.
B = calling for the whole group of received variables - only for variables defined in this object (obsolete) - The event fires only for variables that have received values that were defined in this object on the Data page. The event fires only once for each received group of variables.
C = calling for each variable separately - only for variables defined in this object (obsolete) - The event fires only for variables defined in this object on the Data page, that have received values. The event fires for each variable individually. For example if there is agroup of 100 variables received, then the event is fired 100 times. That is the main reason why this approach is not recommended for large volumes of data items.
In the onDataReceive event it is possible to check the received data items from the pEvent.VarName parameter.
|Auto send to server when writing to item||If checked, then at any writing into the data item the value of this item is immediately written to the OPC server (at writing into data defined on the Data page and at writing into PmData object data containing ExtOpcClient). |
If you write into more items of this object at a time, the transfer is invoked for each item separatelly! Then it is better to disable this configurator and to send the data by the Write method.
Caution! Writing to the OPC is called only when the real write is performed (e.g. object.Item(0)=3) into the item - let's mark it A. But if the data binding (during the reading) to another item B (in another object) is defined in the item A and it is written into the item B then the item A doesn't know about the change and nothing is sent to the OPC server (the item A does know about the change only when it is read by someone - data binding is then "performed").