Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
Connecting to Autosol OPC Server
Geo SCADA Knowledge Base
Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we?ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
📖 Home Back
When adding an OPC Server to ClearSCADA to connect to AES, the connection type on the Server tab defaults to "In Process" and should be changed to "Local Server" or "Remote Server" as required.
If this has not been done, the following symptoms may arise:
When adding a new OPC point to a scanner, ClearSCADA unregisters all the tags on that scanner and re-registers the tags again (including the new ones). Depending on how the OPC server responds with data, this can result in alarms being triggered (by 0 values) and trends including 0 values. Autosol will return 0 values with a quality of Not Connected. Unfortunately, ClearSCADA still uses this value to record historic data and alarms.
To get around this issue, there is an option in Autosol that means the problems go away. Select the option "Invalidate data when communication is lost" in the properties as shown in the dialog below.
autosol.png
Go: Home Back
Connecting to Autosol
When adding an OPC Server to ClearSCADA to connect to AES, the connection type on the Server tab defaults to "In Process" and should be changed to "Local Server" or "Remote Server" as required.
If this has not been done, the following symptoms may arise:
- You get an alarm "failed - co-createinstanceex returns 80040154"
- You cannot browse tags in the OPC server - "create browser returns 0x80070057, parameter is incorrect"
Configure Data Invalidation Setting
When adding a new OPC point to a scanner, ClearSCADA unregisters all the tags on that scanner and re-registers the tags again (including the new ones). Depending on how the OPC server responds with data, this can result in alarms being triggered (by 0 values) and trends including 0 values. Autosol will return 0 values with a quality of Not Connected. Unfortunately, ClearSCADA still uses this value to record historic data and alarms.
To get around this issue, there is an option in Autosol that means the problems go away. Select the option "Invalidate data when communication is lost" in the properties as shown in the dialog below.
autosol.png
Go: Home Back
Author
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.