What is The Objective of Logging Modbus Data
A Modbus data historian captures time-series values from Modbus devices and stores them in a structured database for long-term analysis. The objective is to collect operational values from one or more Modbus devices and store them in an open database such as Microsoft SQL Server for historical analysis, reporting, and system integration.
OAS Components Used
This example Use Case utilizes the following OAS Platform Components and can be deployed in many different configurations to achieve the best performance and reliability:
OAS Universal Data ConnectorWhich Modbus Protocols are Supported?
The OAS Modbus connector supports multiple Modbus communication formats. The devices connected through Ethernet or serial networks are then integrated into a centralized Modbus historian software architecture. This flexibility allows legacy and modern devices to be logged using the same system.
Ethernet-Based Modbus
- Modbus TCP over Ethernet
- Modbus RTU over Ethernet
- Modbus ASCII over Ethernet
Serial-Based Modbus
- Modbus TCP over Serial
- Modbus RTU over Serial
- Modbus ASCII over Serial
Additional Support
- Optional Enron addressing
Which Open Databases Can Store Modbus Historian Data?
The OAS Modbus data historian software logs device values to a wide range of relational, cloud, and open-source databases. This allows Modbus data to be integrated directly with enterprise reporting systems, analytics tools, and business intelligence platforms.
Enterprise Databases
- Microsoft SQL Server
- Oracle
- Access
- mySQL
Cloud Database Platforms
- SQL Azure
Open Source Databases
- PostgreSQL
- Cassandra
- MongoDB
- MariaDB
- SQLite
- CSV files
How Does Log Modbus Data Logger Store Device Data in A Database?
Modbus devices directly connect to the OAS Universal Data Connector using the Modbus Connector. Device registers are mapped to OAS Tags, and the Data Historian writes those values into database tables according to configured logging rules such as time intervals, events, or value changes.
Step 1: Connect to Modbus Devices
Modbus devices are connected to the OAS Platform through the Modbus Connector. This direct integration allows the system to read device registers efficiently and supports native Modbus communication features.
Step 2: Map Registers to Tags
Device registers are mapped to Tags within the OAS platform.
Tags represent real-time data points that can be used by:
- the Modbus data historian
- dashboards and visualization tools
- reporting systems
- external applications
Step 3: Configure Historian Logging
The OAS Data Historian writes Tag values to the selected database. Logging rules define how frequently data is recorded and under what conditions.
Logging can be configured using:
- time intervals
- event triggers
- value change detection
- scheduled recordings
The system supports unlimited logging groups and multiple database targets.
When deploying an enterprise logging solution with the OAS Platform where multiple physical locations are involved, you can also choose to deploy an instance of the OAS Universal Data Connector on each location’s network, ensuring all data points are capture, buffered, and logged even when network connections to the enterprise are down.
Data Historian Features
Data Logging Types:
- Continuous: Log continuously as fast as 100 nanoseconds.
- Event Driven: Log one record based on trigger.
- Data Change: Log a record for each value change.
- Snapshot: Go back in time to record data prior to an event.
- Time of Day: Log one record at a specific time each day.
Store and Forward:
No data loss on network failure or database fault.
100 Nanosecond Resolution:
Unique data handling of data from controller buffer to record values as fast as the controller can process values.
Open Format:
Data is logged to databases in an open format to access directly from any third party reporting system.
Log data to SQL Server, Oracle, Access, mySQL, Azure SQL, PostgreSQL, Cassandra, MongoDB, MariaDB, SQLite, and CSV files.
Automated Setup:
Utilize One Click Database to automatically setup logging of all data from the controller. Or utilize programmatic setup of Tags and Data Logging with a .NET application.
Frequently Asked Questions
What is a Modbus Data Historian?
A Modbus data historian records time-series data from Modbus devices and stores it in a database for long-term analysis. Engineers use historian data to monitor performance, troubleshoot issues, and generate operational reports.
What is the difference between a Modbus data logger and a historian?
A Modbus data logger typically records device values at fixed intervals, while a Modbus historian provides more advanced capabilities such as event-based logging, data buffering, and high-resolution timestamps for industrial analytics.
What is Modbus historian software used for?
Modbus historian software collects operational data from field devices and stores it in a database where it can be analyzed by reporting systems, business intelligence tools, or industrial analytics platforms.
The OAS Platform provides a flexible Modbus data logger and historian solution for capturing device data and storing it in open databases. By combining high-performance Modbus connectivity, flexible logging strategies, and distributed buffering, organizations can build reliable data infrastructures that support monitoring, analytics, and industrial reporting across multiple facilities.
