These guides answer one practical question from different starting points: how does data from sensors and machines that are already installed get into IT systems, and what has to change on the way? Each guide compares the routes, shows what each one changes in the control system, and gives decision rules, including when Perinet is not the right choice.
A shortcut for comparing routes
Every route from a sensor to IT ends in an IP network somewhere: at the PLC, a gateway, an IO-Link master, a remote I/O station, or an adapter beside the sensor. Asking where that first IP address sits shows quickly where protocol translation happens, how much depends on the control system, and what has to change when you need a new data point. Many of these routes publish over MQTT, so the protocol alone does not separate them. Where the address sits does.
Start from your situation
I have installed 4-20 mA, 0-10 V or digital signals and can’t change the PLC.
Add an IP data path beside the control system, sensor by sensor.
I need machine states or counts for OEE.
Pick up running, stopped and part counts at the machine, without touching the PLC program.
I have Modbus RTU devices.
Give each Modbus device its own IP data path instead of a central gateway.
I’m deciding between SPE variants or cable options.
100BASE-T1, 10BASE-T1L and Ethernet-APL: which fits machines, buildings and process plants.
The guides
How to get sensor data without changing the PLC
Add an IP data path beside the control system; if the PLC depends on the signal, use an in-line monitor that reads the loop in passing while the PLC keeps its measurement.
Covers 4-20 mA, 0-10 V and digital signals, with periNODE and periSNOOP.
Read the guide
Talk to an engineer about your retrofit
Tell us which signal you have and where the data needs to end up. We will show you a practical architecture for getting it there without unnecessarily changing the control system. No sales call unless you want one.