Multi-Server OPC Connectivity
Connect to up to 10 OPC Servers and log up to 10,000 signal points per server, with a total capacity of 100,000 points.
INDUSTRIAL DATA ACQUISITION · OPC TO DATABASE
OPCTechs OPC to DB
Connect Your Equipment to Your Database.
Turn Every Signal into Usable Data.
OPCTechs OPC to DB retrieves equipment signals from existing OPC Servers through an OPC interface and writes their values to a database at configurable intervals—creating a consistent, queryable history of process and equipment data.
OPC DATA PIPELINE / SYSTEM OVERVIEW
SOURCE / PLC & OPC SERVER
▣ PLC · 01
Equipment Signals
OPC Server A
TAG DATA
▣ PLC · 02
Equipment Signals
OPC Server B
TAG DATA
▣ PLC · 03
Equipment Signals
OPC Server C
TAG DATA
OPCTechs OPC to DB
OPC INTERFACE · INTERVAL MODE
AUTO
DESTINATION / SELECTED DATABASE
SQL Server
DATABASE
PostgreSQL
DATABASE
MS Access
DATABASE
INTERVAL RECORDING
OPC TAG → DB FIELD
SYSTEM ARCHITECTURE
A Seamless Path from Shop-Floor Signals to Database Records
Build on your existing OPC Server infrastructure. OPC to DB periodically collects selected signals and maps their values to defined fields in your chosen database.
DATA FLOW · SIGNAL-TO-DATABASE ARCHITECTURE
DEVICE LAYER · DATA SOURCES
PLCDevice A
PLCDevice B
PLCDevice C
OPC Servers (Up to 10)
COLLECTION LAYER · TAG MAPPING
OPC Interface
OPCTechs OPC to DBScheduled Logging / Field Mapping / Scaling
DATABASE LAYER · STORAGE TARGET
SQL Server
MS Access
PostgreSQL
Database / TableHistorical Data in Mapped Fields
Read Signals from Existing OPC Servers
Map OPC Tags to Database Fields
Automatically Log at Defined Intervals
CORE CAPABILITIES
Six Core Capabilities for Reliable Industrial Data Logging
From OPC connectivity and database mapping to configurable logging intervals and fallback values, the software provides the essential tools for structured signal storage.
Flexible Database & Field Mapping
Map OPC tags to selected databases, tables, and fields. Supported database platforms include SQL Server, Microsoft Access, and PostgreSQL.
Configurable Logging Intervals
Interval Mode supports logging intervals from 1 to 86,400 seconds, with a configurable start delay of 5 to 1,800 seconds.
CSV-Based Setup & Table Creation
Use TrendTag.csv to define OPC tags, destination fields, and storage parameters. The OPCTechsTrendComp utility helps generate the corresponding database tables.
Fallback Values & Signal Scaling
Define a FailValue to be stored when communication fails, and apply Scale and Offset parameters to transform signal values before writing them to the database.
System Logging & Data Retention
View runtime status messages in LogView and configure data retention periods and scheduled record deletion through the configuration file.
HOW IT WORKS
From OPC Tags to Database Records in Four Steps
01
Verify OPC Data Sources
OPC SERVER
Verify connectivity to existing OPC Servers and identify the PLC signal points to be logged.
02
Configure the Database & Tag Mapping
INI + CSV
Set database connection parameters and logging intervals, then map OPC tags to fields in TrendTag.csv.
03
Generate Database Tables
CONVERTER CSV → CREATE TABLE
Use OPCTechsTrendComp to validate the CSV configuration and create the required database tables.
04
Start Logging & Monitor Status
INTERVAL + LOGVIEW
Run OPCTechsTrend to record signal values at the configured interval, then check results in LogView and the destination database.
FLEXIBLE CONFIGURATION
Precise Tag Mapping.
Complete Control Over Data Storage.
INI and CSV configuration files let you define database connections, destination fields, logging intervals, and fallback values to match your operational requirements.
1
OPC Tag → Database Field
Assign individual OPC tags to specific database table fields.
2
Value × Scale + Offset
Apply a linear transformation to each value before storage.
3
FailValue + Interval
Set the fallback value for communication failures and the automatic logging interval.
TrendTag.csv
Field Mapping Example
| OPC Tag | DB Field | FailValue | Scale | Offset |
|---|---|---|---|---|
| Device1.AI.F1_A_01 | F1_A_01 | -9999 | 1 | 0 |
| Device1.AI.F1_A_02 | F1_A_02 | -9999 | 1 | 0 |
| Device1.AI.F1_A_03 | F1_A_03 | -9999 | 1 | 0 |
Destination Database: DB_Test / Table: Trend
OPCTechsTrend.ini
Configuration Example
[INTERVAL] StartDelay = 10 ; Start delay (seconds) IntervalTime = 10 ; Logging interval (seconds) IntervalDelete = 180 ; Retention period (days) CompressHour = 0 ; Deletion time (hour) CompressMinute = 10 ; Deletion time (minute)
Value Scaling
Scaling Formula Example
Value transformation before database storage:
Stored Value = OPC Item Value × Scale + Offset
Example: With an input value of 12.5, Scale = 2, and Offset = 5, the stored value is 30.
If communication fails, the configured FailValue can be recorded instead.
Configuration examples are for illustration only and do not represent the actual software interface.
APPLICATION SCENARIOS
Capture the Data That Powers Future Analysis
Maintain queryable historical records to support equipment reviews, process traceability, and operational analysis.
USE CASE 01
Production Process Data Logging
Periodically log PLC process parameters to a database for production condition reviews and historical traceability.
USE CASE 02
Equipment Operating History
Consolidate signals from multiple OPC Servers to build a centralized history of equipment conditions and operating values.
USE CASE 03
Energy & Environmental Data Logging
Record electricity usage, temperature, and other measurements made available through OPC Servers at scheduled intervals.
TECHNICAL SPECIFICATIONS
Specifications
Multi-server OPC connectivity, flexible field mapping, scheduled logging, and configurable data retention in one software solution.
| OPC Server Connections | Up to 10 servers |
| Data Point Capacity | Up to 100,000 points (10,000 per OPC Server) |
| Supported Databases | Microsoft SQL Server 2022 or later; Microsoft Access 2024 / Access for Microsoft 365; PostgreSQL |
| Supported Data Types | Bool (Bit), Int, Real, Float |
| Logging Interval | 1–86,400 seconds (Interval Mode) |
| Start Delay | 5–1,800 seconds |
| Value Scaling & Fallback | Scale, Offset, FailValue |
| Configuration Files & Utilities | OPCTechsTrend.ini, TrendTag.csv, OPCTechsTrendComp, LogView |
| Data Retention | Configurable retention period and scheduled record deletion |
| Supported Operating Systems | Windows 11 Pro / Windows Server 2022 or later |
FREQUENTLY ASKED QUESTIONS
Frequently Asked Questions
Does OPC to DB require a separate OPC Server?
OPC to DB connects through an OPC interface to read data from an existing OPC Server. It is designed for data acquisition and database logging; equipment signals must already be made available by an OPC Server.
Can it collect data from multiple machines or OPC Servers?
Yes. The software supports up to 10 OPC Servers and 10,000 points per server, with an overall capacity of 100,000 data points. Deployment requirements depend on the connected equipment and site environment.
What happens when OPC Server communication fails?
A configurable FailValue can be written to the corresponding database field when communication fails. This is a fallback-value function, not a store-and-forward mechanism for recovering data lost during an outage.
Can I configure how often data is recorded?
Yes. Interval Mode allows logging intervals from 1 to 86,400 seconds. The INI configuration file also provides settings for start delay and data retention.