ODBC Datalogger plugin for KEPServerEX Kepware OPC Server

ODBC Datalogger plugin for KEPServerEX Kepware OPC Server


Plug-in module for OPC Server KEPServerEX, with which you can store data in OPC Server directly into ODBC compatible databases such as MySQL, MS SQL, PostgreSQL, Oracle and others. More

Manufacturer: PTC Kepware Code: KWS-DLOGR0-SUB

547 EUR excl. VAT (661,87 EUR incl. VAT)
Subscription license for 1 year - the annual subsccription software price includes an update & support program, which gives you access to updates and technical support for the duration of the license
/ year
Buy more for 230 EUR and get free delivery!
0 EUR230 EUR

Plug-in module for OPC Server KEPServerEX, with which you can store data in OPC Server directly into ODBC compatible databases such as MySQL, MS SQL, PostgreSQL, Oracle and others. More

Manufacturer: PTC Kepware Code: KWS-DLOGR0-SUB

The basic task of the OPC Server is to collect data from various data sources (PLC, CNC, robots and devices), convert them into a single OPC protocol and provide them to the higher-level systems for further processing. By processing we usually mean data visualization and archiving. But what if we can already archive data at the OPC Server level?  And what is it good for?

Many customers don't need screens and live data on them, nor do they need SCADA systems. They are mainly interested in report generation, production tracking or storing production process parameters. All these tasks are built on stored data in a database. That's why there is the DataLogger plug-in module, which you simply install into the KEPServerEX OPC platform and you can start storing the selected data in an ODBC compatible database. Need to store data from your Siemens Simatic, Allen-Bradley PLCs, Modbus meters or FANUC robots?  

Data storage options in KEPServerEX via DataLogger

  • periodic archiving = data storage occurs at a selected time interval, e.g. 1x5sec, 1x1min, 1x1hr, 1x1day, etc. It is also possible to enable "OnChange" archiving.
  • time archiving = the same conditions as for regular archiving apply and in addition it is possible to select a time period, e.g. Monday to Friday at 6-14h. This way you can archive different shifts in different tables.
  • conditional archiving - data archiving starts or stops when a condition is met, which can be e.g. the selected OPC value is > 1 or = 50 or is in BAD quality or is back to GOOD etc.

You won't lose data in case of a database failure

In the event of a connection failure between the KEPServerEX Datalogger and the connected database, you will not lose any data, because thanks to the "Store&Forward" function, KEPServerEX will start saving the data to the local disk. The maximum storage capacity is 2GB on disk. When the connection to the database is re-established, the data is automatically saved to the database.

By archiving the data using KEPServerEX itself, data collection projects are simplified because the data archiving no longer needs to be 100% performed by the parent application (usually the SCADA HMI system). The programming part of archiving on the OPC client side will be simplified and a new standardization in data archiving will be achieved. DataLogger stores data in an existing table or can create a new table in the database. In addition, it names the columns in the table according to the value it stores in it.

How to store data from production machines in a database?

Do you need to store data from your Siemens Simatic, Allen-Bradley PLCs, Modbus meters or FANUC robots?  No problem. Get a convenient package with more than 100 of the most commonly used OPC drivers (Manufacturing Suite) and the DataLogger plug-in. For a very affordable annual rental price, you can start saving data from your control systems into a database immediately and create reports on them, e.g. in PowerBI. It doesn't get any simpler or faster than that.

  • Supports many ODBC-compliant database management systems
  • User-friendly installation and configuration
  • Supports dynamically-created tags
  • Provides flexible triggering
  • Supports logging of Complex Tags from the Advanced Tags Plug-In
  • Includes the Simulator driver
  • Supports deadband for logged items
  • Supports an optional NumericID field for logged items
  • Has the ability to use Start/Stop Snapshots without requiring the Log on Static Interval Log on Data Change Trigger behaviors enabled
  • Provides a _LogDataBit system tag that allows client applications to trigger DataLogger
  • Supports JSON import/export for logged items
  • Offers third-party and remote configuration through the Configuration API
  • Store and Forward feature for non-volatile data persistence during database connection issues