An often important task when logging important process data to a database or even to the cloud is verification that the data has been logged. This ensures that data has been successfully logged and will not be lost when overwritten in the downstream process.
In this video blog, we'll step through the configuration required in the OPC Data Logger for logging important process data to a database on condition related to a monitored item and how to perform a writeback to the OPC data source confirming the data has been successfully logged.
Watch this video to learn how to log process data from any OPC UA or DA data source based on a monitored item trigger with a writeback to the OPC server for verification using the OPC Data Logger. Looking for other how-to videos for OPC Data Logger? Click here!
Just to summarize, in this video, I've shown you:
- A quick review of the existing configuration for:
- OPC UA data source settings for logging from an OPC UA server
- Existing configured OPC item settings
- Existing configured data store for Azure SQL
- Azure SQL database table being logged to
- How to configure a writeback to an item in the OPC server for confirming logging has occurred successfully
- Including defining the Writeback in the SQL Server storage properties with the appropriate cause for the write back to the OPC item.
- How to log data from the OPC server based on the condition of a monitored item using a Monitored Item trigger
- Including defining the Monitored Item trigger for use as the trigger for logging in the Logging Group.
- Verifying successful triggered based logging to SQL / Azure and writeback to the OPC server.
Ready to log your own OPC process data to SQL and Azure SQL via monitored item triggers with verification using OPC Data Logger?