Industrial Collector

Connect the PLCs, drives, meters and machines on your factory floor — Siemens S7, Allen-Bradley, Modbus, OPC UA and more — and stream normalized, analytics-ready data straight into your fleet database. Pick your equipment from a catalog; no register hunting, no coding, no per-protocol apps. One app monitors a whole mixed cell, polling controllers from different vendors side by side in a single gateway.

Early access — in active development. Modbus, OPC UA and demo mode run today. Siemens S7 and Allen-Bradley are powered by the Apache PLC4X engine and are being validated across devices — S7-1200/1500 controllers can already be read today through their built-in OPC UA server.

Why this app

One app for the whole floor. Siemens S7 (S7-1200/300/400), Allen-Bradley (EtherNet/IP & Logix), Modbus TCP and RTU/serial, and OPC UA — all in a single gateway app, polled side by side. Stop deploying and maintaining one collector per controller brand.

Connect by machine, not by protocol. Choose your equipment from a catalog of profile packs — e.g. “Atlas Copco GA Elektronikon” or “Ingersoll Rand Xe” — and the connection comes up with its tags, scaling, units and meaning already mapped. Enter the IP address and you’re collecting. No datasheet archaeology, no register spreadsheets.

Analytics-ready, normalized data. Every reading carries a value, an engineering unit, a quality flag and a semantic type (e.g. pressure.discharge, runtime.hours). Compare a compressor in Plant A against one in Plant B regardless of vendor or protocol. Raw addresses stay internal — they never leak to your dashboards.

Extensible without redeploying. Profile packs are content, not code: add or update equipment definitions on the fly, and share them across your fleet. Have a custom PLC program? Map its tags by hand in a simple YAML list — no pack required.

Safe for OT networks. Read-only to your PLCs by default — the collector never writes to your equipment. Runs on an isolated machine VLAN, with credentials kept in the platform secret store, never in plain config.

Supported devices & protocols

Look up your device below. The collector reads from any device that speaks one of these protocols — known models connect from the profile-pack catalog with zero tag mapping, and anything else connects via manual configuration. Listed models are addressable via the stated protocol per vendor documentation; profile packs are provided for an expanding set of specific models.

Availability: ✅ Modbus and OPC UA run today. 🔧 Siemens S7 and Allen-Bradley are powered by the Apache PLC4X engine and being validated across devices. 🗺️ Other protocols are on the roadmap (see below).

✅ Modbus — TCP and RTU/ASCII serial (RS-485 / RS-232)

If it exposes a Modbus register map — over TCP (port 502) or RS-485 serial (multidrop, unit IDs 1–247) — this app can collect it. Common families:

• PLCs & controllers: Schneider Modicon (M221, M241, M251, M262, M340, M580, Quantum, Premium), WAGO (750/753, PFC100/PFC200), Phoenix Contact PLCnext (AXC F 1152/2152/3152), Beckhoff TwinCAT (Modbus TCP / TF6250), ABB AC500, Delta (DVP, AS), Unitronics (Vision, UniStream), Fatek (FBs), Allen-Bradley Micro820/850/870.
• Air compressors: Atlas Copco Elektronikon (GA, ZR, ZT, ZP…), Kaeser Sigma Control 2, Ingersoll Rand Xe-series & XS-series, Gardner Denver / CompAir D-Series, Boge FOCUS, ELGi.
• Variable frequency drives: ABB ACS580 / ACS880 (ACS355/380/480), Danfoss VLT / FC (FC 102/202/302, FC 360), Schneider Altivar (ATV320/340/600/900), Yaskawa GA800 / GA500 / V1000 / A1000, Allen-Bradley PowerFlex 525 (750-series with Modbus card), WEG CFW, Delta (MS300, C2000), Invertek Optidrive.
• Energy & power meters: Schneider PowerLogic PM5000 / iEM3000 / ION, Janitza UMG (96/103/104/508/604), Carlo Gavazzi EM/ET (EM24, EM340, ET112/340), Socomec Diris, Eastron SDM (SDM120/230/630), Accuenergy Acuvim II, Siemens SENTRON PAC (PAC2200/3200/4200), Lovato DMG.
• Solar / PV inverters: SMA Sunny Boy / Sunny Tripower, Fronius GEN24 / SnapINverter, Huawei SUN2000, Sungrow, SolarEdge, Kostal, Solis (SunSpec/Modbus).
• Remote I/O, RTUs & protocol gateways: Advantech ADAM-6000/4000, Moxa MGate / ioLogik, HMS Anybus (Modbus RTU↔TCP), and generic RS-485 transmitters (temperature, pressure, flow, level, power).

✅ OPC UA — any OPC UA server

Connect to any OPC UA server (opc.tcp://…, default port 4840); browse the address space and read nodes, with anonymous, username/password or certificate auth and security up to Basic256Sha256. Recognised servers include:

• Controllers with a built-in OPC UA server: Siemens SIMATIC S7-1500 (and S7-1200 on recent firmware), Beckhoff TwinCAT (TF6100), B&R Automation, Phoenix Contact PLCnext, WAGO PFC100/PFC200, Bosch Rexroth ctrlX, Schneider Modicon M251/M262, Mitsubishi MELSEC iQ-R, Omron NX/NJ, ABB AC500.
• Software & DCS servers / aggregators: KEPServerEX (Kepware), Inductive Automation Ignition, Prosys, Matrikon, Unified Automation, and OPC UA gateways/DCS bridges (Softing, HMS/Ewon).

🔧 Siemens S7 — S7comm / S7comm-plus (port 102), via the PLC4X engine

• SIMATIC S7-1500 — CPU 1511/1513/1515/1516/1517/1518, ET 200SP CPUs (1510SP/1512SP), S7-1500 Software Controllers.

• SIMATIC S7-1200 — CPU 1211C/1212C/1214C/1215C/1217C.

• SIMATIC S7-300 — CPU 312/314/315/317/319; S7-400 / S7-400H — CPU 412/414/416/417.

• LOGO! 8 (also speaks Modbus TCP).

  Note: S7-1200/1500 require “Permit PUT/GET communication” enabled and non-optimized data blocks — or use their built-in OPC UA server instead. S7-200 / S7-200 SMART are limited; use Modbus TCP where possible.

🔧 Allen-Bradley / Rockwell — EtherNet/IP (port 44818), via the PLC4X engine

• Logix (symbolic tag access): ControlLogix 1756 (L6x/L7x/L8x), CompactLogix 1769 & 5069 (5370 / 5380 / 5480), GuardLogix / Compact GuardLogix.
• Micro800 with Ethernet: Micro820 / Micro850 / Micro870 (global tags; Modbus TCP also available).
• Legacy MicroLogix / SLC 500 / PLC-5 speak PCCC (over EtherNet/IP or DF1 serial) — supported via a PCCC/gateway path (roadmap).

🗺️ Roadmap

Powered by the PLC4X engine and being wired in next: Beckhoff ADS (TwinCAT / CX), KNXnet/IP, IEC 60870-5-104, Profinet, DF1. Schneider Modicon M340/M580 connect today via Modbus or OPC UA. For building automation (BACnet), use the dedicated BACnet Collector app.

Don’t see your device? If it speaks Modbus or OPC UA, it works today; tell us about anything else and we’ll add a driver or profile pack.

What you get

Install the app in your project and assign edge PCs (gateways) to it. Then open the app board, go to the settings view and add a connection — two ways:

• From the catalog: pick the equipment (e.g. Atlas Copco GA), choose the gateway, enter the IP address. Tags, units and semantics come from the pack.
• Manually: choose the driver (S7, Modbus TCP/serial, EtherNet/IP, OPC UA), fill in the connection details, and list the tags you want.

From that moment the app collects at the configured interval and stores every reading in the measurements table of your fleet database — each carrying its value, engineering unit, quality flag and semantic type — while each machine’s live online/offline state is tracked in the assetstatus table.

Common collector features

Like every IronFlock collector, the Industrial Collector is configured entirely in the browser — add and edit connections in the built-in app board, with changes taking effect live and no restarts. It is reliable at the edge: connections reconnect automatically, each machine is collected in isolation (one unreachable PLC never stops the others), and if the gateway loses its connection to the platform, readings are buffered locally and forwarded in order the moment the link returns — no silent data loss (buffer size configurable per gateway, with an optional forward-only mode). And you can try it without hardware: switch any connection to demo mode and the app generates realistic data so you can explore the full experience before wiring up a single device.

Build on your data

The included app board gives you an instant overview of incoming data. For tailored presentations, build custom dashboards and SCADA boards that display your machine data side by side with data from other apps and other protocols, query it through the Data Backend, and use the Alarms app to monitor collected values in real time with SMS or email notifications. To bring devices online and install the app, see Device Management and App Management.