OPC Data Logger - Writebacks and Handshaking

When You Want to Make Sure the Data Is Logged

Users told us they often buffer data in PLCs for efficient reading in blocks and logging, but want to make sure the data has been stored before they clear the buffer and load it with more data to be logged.

There are plenty of other reasons user wanted a handshaking mechanism. OPC Data Logger writebacks are the solution. 

  • Map to any item in your OPC data source
  • Set multiple writebacks based on different conditions occurring with text file and database logging

When used with OPC Data Logger Triggers many flexible solutions for text or database logging are possible.



Text File Writeback Options

When logging to Text/CSV files, writebacks can be sent based on several conditions are defined on the Writeback tab of the Text File Data Storage properties

  • After the file is opened
  • After the file is closed
  • On each write to the file

Multiple writebacks can be defined and mapped to different device items for each type. 

Database File Writeback Options 

When logging to databases, writebacks can be sent based on several conditions are defined on the Writeback tab of the Database Data Storage properties

  • After connecting to the database
  • After database connection is closed or lost
  • After each item or group of items are logged 

If you have alarm callout notifications in your HMI that trigger off your PLC, you could setup an alarm to notify you if your database connection is lost with a writeback.

Writebacks work with all supported database types.


Get Started Now

The trial software is the full product and can log to any supported file or database format with no tag count limits. Once the OPC Data Logger starts logging, it will stop after 2 hours. You can restart it but all logging will stop after 30 days. 

Connect with Us

1-888-665-3678 (US + Canada toll free)
+1-704-849-2773 (Global)