Any protocol, no exceptions
PLC, robots, Modbus, MQTT, OPC UA, SECS/GEM, Socket, Serial, and more are all supported. (Except closed equipment that does not publish its protocol)
LINKER
One LINKER SERVER completes your factory's equipment data center. Values from disparate equipment accumulate in one place, people see them on screen, and MES and AI put that data to work immediately.
- Tag data storage (Enterprise)
- 500K/s
- Query the past year of data
- Under 1 second
- Tag comparison analysis
- Tens of thousands
- Equipment interfaces (IF) connected on site
- 1,500+
Key benefits
A year of records in under 1 second
No matter how much data, a full year of records is retrieved in under 1 second. Compare and analyze tens of thousands of tags.
Start light at small sites
A single Connector runs collection and delivery together.
Put data to work immediately
Collected values flow to production output, dashboards, and AI analysis.
Who uses it
Used together by equipment, development, and operations staff
Equipment · automation staff
Set communication settings and collection items per tool, and operate equipment touchpoints by watching received values and connection status.
MES · ERP developers
Receive server data through Client, linking tags and business items to build output and status screens.
On-site IT operators
Deploy Server · Client · Connector to fit the site's scale, checking communication and business segments separately.
Functions
Connect, collect, deliver
Linker Server
A data hub for industrial devices. Processes real-time tags with the RxMemory in-memory DB and RocksDB · SQLite storage.
PLC · OPC UA · Modbus · MQTT · RESTLinker SECS/GEM
Equipment communication for semiconductor and display tools, developed in-house, with a scenario editor and log analysis tools.
HSMS · SECS-II · GEMLinker Connector
The Linker core library, embedded inside your application with no server. Saves directly to MySQL, MSSQL, and PostgreSQL.
Library · embeddedLinker Bridge
Relays a private-network Linker Server for access from a public network, connecting securely even when equipment and operations networks are separated.
Relay · authentication · access controlLinkerFlow
A web dashboard for building monitoring screens without code, using 50+ widgets.
Dashboard · mobile01
Connect any equipment
Connects PLCs such as Melsec and LS, robots, and IoT sensors via TCP, UDP, Serial, Modbus, MQTT, and OPC UA.
02
Connect semiconductor equipment yourself
Our own SECS/GEM implementation receives events, alarms, and production data, with two-way control tailored even to non-standard commands.
03
Pull a year of records in under 1 second
No matter how much data, a full year of records loads in under 1 second. Pull tens of thousands of tags at once for comparative analysis.
04
View it even on isolated networks
A Bridge server lets external monitoring systems securely query PLC data inside the plant.
05
Change without stopping
Checks equipment status remotely and applies feature changes and updates without stopping the system.
06
Check with test tools
Protocol-specific test tools and a SECS message editor cut equipment inspection time.
Screens
Check everything from equipment to business systems
Screen 1 · equipment, protocols, Server, RTDB, Client, business systems
Connecting equipment and business systems
Shows the path data takes to reach business systems, separating the roles of equipment reception and business delivery.
- Communication segment
- RTDB
- Client delivery
Screen 2 · messages per second, response time, online devices, active clients, collection status by unit
Server and equipment status on one screen
The Linker Server dashboard. See how fast the server exchanges data and whether each unit is collecting or disconnected, on one screen.
- Messages per second · response time
- Collection status by unit
- Disconnected units flagged instantly
LINKER SERVERLinkerServiceRunning · 127.0.0.1 : 9010
TCP server
Messages per second89/s
Avg RTT29 ms
Avg TX22 ms
Avg RX17 ms
Online devices30
Active clients48
DashboardDevicesTagsAlarmsClient subscription infoTransfer queueDevice task queueClient request queueLogSettings
System status
Online devices30
Active clients48
Messages per second89/s
Avg RX17 ms
Avg TX22 ms
TCP server
Equipment status (online 30 / total 36)
P1 · Filler 1Collecting
P2 · Filler 2Collecting
P3 · CapperCollecting
P4 · LabelerCollecting
P5 · Mixing tankCollecting
P6 · ReactorCollecting
P7 · Gantry robotCollecting
P8 · Dryer 1Collecting
P9 · Dryer 2Collecting
P10 · PackerCollecting
P11 · visual inspectorDisconnected
P12 · weight checkerDisconnected
P13 · ChillerCollecting
P14 · Conveyor 1Collecting
P15 · Conveyor 2Collecting
P16 · Air handlerCollecting
Screen 3 · device tree, driver, address, protocol, RTT, stop · start
Each machine's protocol, one server
Device list by group. Connect Mitsubishi · LS · Siemens PLCs, Modbus, OPC UA, and socket · serial equipment from one server, and stop and reconnect each individually.
- Multiple drivers connected at once
- Response time by device
- Individual stop · start
LINKER SERVERLinkerServiceRunning · 127.0.0.1 : 9010
TCP server
Messages per second76/s
Avg RTT41 ms
Avg TX36 ms
Avg RX13 ms
Online devices30
Active clients48
DashboardDevicesTagsAlarmsClient subscription infoTransfer queueDevice task queueClient request queueLogSettings
Overall statusSearch by device ID, name, or IP+ Add devicePrint logRefresh
Plant 1 filling line· 7 units
P1 · Filler 1MelsecMcNetConnected192.168.10.21 · 4134Protocol TCP StationRTT 3 msStopRelease⋮
P2 · Filler 2MelsecMcNetConnected192.168.10.22 · 4134Protocol TCP StationRTT 2 msStopRelease⋮
P3 · CapperLS XGTConnected192.168.10.31 · 2004Protocol TCP StationRTT 4 msStopRelease⋮
P4 · LabelerSiemens S7Connected192.168.10.41 · 102Protocol TCP StationRTT 5 msStopRelease⋮
P5 · Mixing tankModbus TCPConnected192.168.10.51 · 502Protocol TCP StationRTT 3 msStopRelease⋮
P6 · ReactorOPC UAConnected192.168.10.61 · 4840Protocol TCP StationRTT 6 msStopRelease⋮
P11 · visual inspectorSocketDisconnected192.168.10.71 · 9100Protocol TCP StationRTT -StartRelease⋮
Screen 4 · PLC, sensors, scales · testers, IoT, existing DB
One Connector for small sites
Where a separate server is hard to run, Connector embeds in your program and saves equipment values straight to your existing DB. As equipment grows, split out to LINKER SERVER.
- No server
- Into your existing DB
- Extend as is
Use cases
Use equipment data everywhere it's needed
Production count collection
Equipment sends production counts and status values, and the MES owner links values received by Client to work output.
Multiple protocols connected
One site runs PLC · OPC · Serial equipment together. The communications owner gathers items collected by Server into the RTDB.
Equipment message integration
HSMS/SECS equipment exchanges operational messages, and business systems take the items they need for equipment status and production records.
Condition-based equipment checks
The equipment team collects condition data such as temperature and vibration, reviewing change periods and inspection targets based on Analyze results.
Data connection for small sites
On-site staff run collection and delivery as one execution unit. Linker Connector runs Server and Client together.
Case studies
Connecting equipment from semiconductors to food
PCB manufacturing
Connect semiconductor equipment without foreign libraries
- Projects
- Each line had tools from different makers, so aligning SECS/GEM communication took time, and non-standard commands had to be left unintegrated.
- Method
- Our own SECS/GEM receives equipment events, alarms, and production data, with non-standard commands tailored per tool for two-way control. Messages were tested in advance with a scenario editor.
- What changed
- Adding tools is a matter of configuration, not communication development. Even vision inspection was tied into one automated line.
Semiconductor substrate manufacturing
Automate fine-process lines with equipment data
- Projects
- Fine-process lines still relied on manual checks and records at each unit.
- Method
- Collected line equipment data in real time with Linker Server, handling equipment control and production system integration on one server.
- What changed
- Equipment status and production conditions are recorded without human hands.
Secondary battery materials
Text alerts first for environmental equipment faults; causes in the data
- Projects
- Environmental equipment like bag filters, scrubbers, and dust collectors was scattered across the plant, so stops or faults went unnoticed until the next patrol. Why a unit stopped was never recorded.
- Method
- Linker Server collects front and rear temperature, level, blower current, circulation temperature, and cumulative energy from every unit in real time. Three-level conditions (warning · caution · watch) are set per unit, triggering SMS to the owner when met, while run and idle time and alarm history build up to analyze failure causes and stop patterns.
- What changed
- When something goes wrong, the owner's phone rings first. Uptime and stop history per unit build up weekly, so units with recurring failures are found and fixed first.
Large appliance manufacturing
Automates crimping process equipment
- Projects
- Checking and recording equipment conditions in the crimping process was manual.
- Method
- Automated process equipment by connecting it with Linker Server, then went on to build a semiconductor onboarding system.
- What changed
- Equipment conditions are recorded automatically, and process anomalies are visible right away.
Bio
Automatically controls bioprocess equipment
- Projects
- Many steps relied on people setting and recording process conditions.
- Method
- Connects equipment to control process conditions automatically and keeps operating data on monitoring screens.
- What changed
- Condition settings and records move into the system, so operators focus on handling anomalies.
Manufacturing equipment
Predicts failure signs from monitoring data
- Projects
- Equipment monitoring screens showed only current status, with no way to know when a failure would come.
- Method
- Built a structure that uses equipment data collected by Linker Server directly as training data, and added a failure-sign prediction model.
- What changed
- The collection server becomes your AI training data warehouse. Start predicting with no separate data migration.
Use-case scenarios
Do more with the data you collect
Add products one at a time as needed, and expand like this.
- Linker Server Server collects production values.
- Linker Client Client delivers the received items.
- MES MES accumulates work output.
- LINKER Collect equipment status.
- Analyze The model analyzes anomaly periods.
- Orchestrator Draft the inspection report.
- Linker Connector Receives equipment values in one process.
- RxControls Developers build the receiving screens.
- ERP Staff use the values in business records.
Alongside existing systems
Don't replace equipment. Just connect it
Deployment model
Configuration and cost vary with scope, user count, and installation environment. Tell us your situation and we will recommend the right approach.
Contact salesInstallation environment
Collection and delivery paths are designed around where on-premises · internal-network equipment and cloud business systems sit.
Existing system integration
Existing MES · ERP · ECHO AI receive Server data through Client.
Open standards
Covers communication touchpoints for OPC · HSMS/SECS and PLC · Socket · Serial, linking equipment communication items to business data.
FAQ
FAQ
Which protocols are supported?
Supports PLCs such as Melsec and LS, Modbus, MQTT, OPC UA, REST API, SECS/GEM, and TCP · UDP · Serial equipment.
Does SECS/GEM use foreign libraries?
No. Wavegram developed the SECS/GEM protocol in-house. Non-standard equipment commands are implemented to fit.
How long is data retained?
Stores 15 years in 1 TB at 1,000 tags. Supports event and periodic storage and automatic backup.
Doesn't it take long to pull up accumulated data?
No matter how much data, a full year of records loads in under 1 second. Overlay tens of thousands of tags for comparative analysis.
How many devices can connect?
Connects up to 255 equipment and clients combined, collecting values at intervals as short as 10 ms.
Hard to run a separate server.
Embed Linker Connector in your application to receive equipment data without a server and save it directly to your existing DB.