Back to News
Tags:Factories & Automation

iNut Datalogger Gateway Solution — Unlimited PLC Connectivity via Modbus TCP/RTU

Break past WinCC's ~8-PLC limit: use iNut Datalogger to pool 100+ S7-1200 PLCs into a single SCADA via Modbus TCP/RTU — unlimited connections, data stored on-premise.

iNut Datalogger connecting 100+ PLCs to one SCADA - English cover

WinCC only connects to ~8 PLCs? Here's how to bring 100+ S7-1200 PLCs onto a single SCADA

iNut Datalogger gateway solution — unlimited PLC connectivity via Modbus TCP/RTU

If you've ever built a monitoring system with WinCC Professional on TIA Portal, you've probably hit this exact "wall": everything runs smoothly with the first few PLCs, then around the 8th–9th PLC, the connection starts glitching, throws errors, or simply won't let you add any more.

This isn't your fault. It's a real limit on the number of simultaneous connections a WinCC station can reliably maintain over PROFINET. For a plant with just a few PLCs, that's fine. But once the project grows — dozens or hundreds of PLCs, multiple cabinets, multiple lines — you get stuck: either buy more expensive licenses and hardware, or split the system into pieces and lose the overall view.

There's a third way — leaner and far cheaper.

Put a "middleman" between WinCC and your forest of PLCs

The idea is simple: instead of making WinCC struggle to connect directly to every PLC, you place iNut Datalogger as the middle layer. iNut Datalogger pools data from hundreds of PLCs, then presents it back to WinCC as Modbus TCP/IP (or RTU) — a protocol WinCC reads with ease.

Before: WinCC → direct connection → up to ~8 PLCs (9th PLC onward: connection fails).
After: WinCC ⟷ Modbus TCP/RTU ⟷ iNut Datalogger ⟷ 100+ PLCs (unlimited connectivity).

Comparison diagram: WinCC direct connection limited to ~8 PLCs vs the 100+ PLC expansion solution via iNut Datalogger
Comparison diagram: "Limited scenario" vs "Expansion solution via iNut Datalogger"
100+ PLC into one SCADAiNut Datalogger aggregates PLC data over Modbus TCP/RTU into WinCC/SCADA.INTEGRATION FLOWPLC 01–100+Field devicesiNut DataloggerEdge gatewayModbus TCP/RTUProtocolWinCC / SCADAOperator viewONE EDGE GATEWAY — ONE FACTORY VIEW

Why can iNut Datalogger do what WinCC can't do directly?

Because iNut Datalogger isn't a passive gateway — it's a mini edge server with a 4-core 64-bit CPU, 4GB RAM, 32GB internal storage (≥20GB available for applications), a 100Mbps Ethernet LAN port, and 2.4/5GHz WiFi, powerful enough to manage many concurrent Modbus sessions while logging data. It supports Modbus RTU and Modbus TCP in parallel, converts Modbus RTU ➜ Modbus TCP, and opens multiple Modbus Slave ports (1502–1507) so other SCADA software can connect in as well.

Beyond Siemens, iNut is compatible with Omron, Schneider, Rockwell, ABB, Mitsubishi, GE, and Delta — so even if your project mixes multiple brands, everything still comes together in one place.

Not just for viewing — for taking full control

The biggest difference: with iNut Datalogger, your data stays on your own premises. This is your own edge server, not a rented account on some foreign cloud. You store long-term data (1 year or more), retrieve history, and later use that same dataset to analyze trends, detect anomalies, or even run AI-based predictions.

And if you need your own monitoring interface — independent of WinCC — iNut Datalogger comes bundled with FUXA PRO (a free license worth 3.3 million VND), a web-based SCADA/HMI. You (or we) can build dashboards, load diagrams, control buttons, alerts, and more — right in the browser.

FUXA PRO dashboard — web-based SCADA/HMI running on iNut Datalogger
FUXA PRO interface — web-based SCADA/HMI on iNut Datalogger
👉 Stuck on the number of PLCs you can connect?

Share your system details and we'll build a sample connection diagram for free — sized exactly to your PLC count and device types.

Get free consultation

Share this article

Send it to a teammate or keep the link for later

Share on FacebookShare on TwitterShare on LinkedInShare via WhatsAppShare on ZaloSend by email