Communication Settings

•Node Name
This is the computer name when connecting remotely. If the OPC server is running on the same PC, do not enter this.

•Program ID
The program ID of the OPC server to connect to.

•Default Access Path
Specify the access path.

•Communication Method
Normally, we recommend change notification. If the OPC server does not support this, we recommend "synchronous communication (cached value)."

•Update Rate
The update rate to notify the OPC server.

•Deadband
When you set a deadband, the server will not send a DataChanged event to the client unless there is a change equal to or greater than the set value.
 

•Convert the value to be written to CanonicalDataType
When writing a value to the OPC server, the value type is converted to match the CanonicalDataType returned by the OPC server before writing.
If the OPC server supports writing in data types other than CanonicalDataType, no check is necessary (the load is slightly reduced since no conversion is required).

•Waiting time after connection
Sets the wait time before performing AddGourp after connecting OPC.
 

•After connecting, use GetStatus to check that the OPC server is ready before proceeding.
After connecting, use OPC to check that the server is ready, then perform AddGourp.
 

Tag communication settings

•Item Name
Specifies the item name of the OPC server.

If the destination tag is an array, add ", the number of arrays" to the end of the item name.

For an array of 10 items, use "item name, 10"

When connecting to the OPC server of the Yokogawa package CENTUM, please note the following:

- If you define more than 2000 tags in one unit, a communication error may occur only for the tags that exceed 2000. In such a case, please divide it into multiple units and set tags so that each unit does not exceed 2000 points.

- If you have defined a large number of tags, online processing may take a long time. In such a case, check the "Start automatic monitoring" box for the folder.