Technologies
Whatever the PLC, the CNC or the protocol
We read data in the language your machine already speaks, without touching its control program.
Our clients
- Siemens
- Anadolu Isuzu
- BSH
- Tofaş
- Toyotetsu
- Martur
- Turkcell
- Vodafone
- Doğadan
- Pakmaya
- Bross
- Abdi İbrahim
- Nobel İlaç
- Plastimak
- Dalgıç Kalıp
- Barbaros Motor
- Magneti Marelli
- Rözmaş
- Sanel
Technologies
Controllers and protocols we integrate
These are the ones we meet most often. Proxus supports a wider driver list; ask if your controller is not here.
- 01
Siemens S7 PLC data collection
Read-only data collection from S7-1200, S7-1500, S7-300/400 and S7-200 over S7comm or OPC UA.
Explore → - 02
Allen-Bradley PLC data collection
Read-only collection of ControlLogix and CompactLogix tags over EtherNet/IP (CIP).
Explore → - 03
Mitsubishi PLC data collection
Reading MELSEC Q, iQ-R and FX5 PLCs over the MC protocol, without touching the program.
Explore → - 04
Omron PLC data collection
Reading Omron CJ, CS and NJ/NX PLCs over FINS and CIP, without touching the program.
Explore → - 05
Beckhoff TwinCAT data collection
Reading TwinCAT 2 and 3 controllers over ADS, without touching PLC code.
Explore → - 06
Fanuc CNC data collection
Reading state, program, part count and alarms from Fanuc Series 0i machines over the network.
Explore → - 07
Heidenhain CNC data collection
Reading state, program and alarm data from Heidenhain TNC controls over LSV2.
Explore → - 08
OPC UA integration
Connecting to OPC UA servers with security modes and certificates, node selection and data modeling.
Explore → - 09
Modbus integration
Reading Modbus TCP devices, and Modbus RTU through a serial device server, from register maps.
Explore → - 10
MQTT integration
Publishing plant data through an MQTT broker as JSON or Sparkplug B, with an orderly topic tree.
Explore →
Why reading PLC data looks hard
Most plants run several PLC brands, generations and protocols side by side; a new S7-1500 can sit on the same line as a twenty-year-old controller. Reading PLC data means knowing each one’s protocol, addressing and data types, and doing it without risking production or touching the control program.
VOLSOFT takes this on as an integrator: we do not change the PLC program, we make the existing variables readable. Where needed, we agree with your automation team or the machine builder which addresses to read.
Native driver or OPC UA?
If the controller exposes an OPC UA server, that is usually the first choice: security and data types are standard. If it does not, or it needs a licence, the controller is read over its own protocol (S7comm, EtherNet/IP, MC protocol, FINS, ADS, FOCAS). The choice is made in discovery, from the controller generation, the network and the number of variables.
Next step
Let’s turn your goal into a clear engineering scope.
Tell us about your plant, your machines and your goal. An integration engineer will set up a discovery call with you.
