{"id":53169,"date":"2026-06-26T15:00:00","date_gmt":"2026-06-26T13:00:00","guid":{"rendered":"https:\/\/www.cybus.io\/?p=53169"},"modified":"2026-06-26T17:28:10","modified_gmt":"2026-06-26T15:28:10","slug":"siemens-plc-to-mqtt-s7plus","status":"publish","type":"post","link":"https:\/\/www.cybus.io\/en\/siemens-plc-to-mqtt-s7plus\/","title":{"rendered":"Siemens PLC to MQTT: Two Paths for Every Tag, No Re-Engineering"},"content":{"rendered":"\n
\n

Connecting a Siemens PLC to MQTT is how factory data reaches the systems that act on it \u2013 historian, MES, analytics and the unified namespace that ties OT and IT together.<\/h2>\n\n\n\n

In a Siemens-powered plant, that data lives deep inside the PLC. The goal of a connected factory is simple: full Siemens PLC data access<\/strong> \u2013 every operationally relevant value the controller holds reaching the systems that act on it. While OPC UA is the standard starting point, the densest controllers often hold more than their built-in servers can expose. When you hit that ceiling, you need a second path: Siemens’ S7plus (S7+) protocol, native and high-performance, reaching past the built-in server’s limits.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n
\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n

Expert article by <\/p>\n\n\n\n

Dr. Diwaker Jha
Industrial Connectivity Expert, Cybus<\/em><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n

The Blind Spot: 16,000 Tags That Never Reach MQTT<\/strong><\/strong><\/strong><\/strong><\/h2>\n\n\n\n

For full Siemens PLC data access, every tag has to be reachable \u2013 yet the densest controllers hold more than the built-in server is sized to expose. Take a case we ran into in the field: a Siemens S7-1200 holding over 18,000 tags. The customer connected via OPC UA and the first couple of thousand tags flowed \u2013 then the count stopped just under 2,000. That is the server’s node cap<\/a>, the number of tags it can expose. Live updates are a separate budget: about 1,000 monitored items at 1,000 ms sampling, dropping to roughly 100 when you need 100 to 500 ms. The remaining 16,000 tags were healthy and present, but they sat just past what the built-in server is sized to expose. For complex datatypes, it falls further still \u2013 to a few variables. Not enough for modern, data-rich production environments.<\/strong><\/p>\n\n\n\n

For a decision-maker, those locked tags aren’t just a technical hurdle; they are a blind spot. Your historian, MES and analytics dashboards can only optimize what they can see. In complex batch plants, the variables out of reach are often the ones that matter most: yield, energy efficiency and quality metrics. The breakthrough? The customer didn’t have to touch the controller. They simply opened the second path: native S7plus.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n

“Getting Siemens data into MQTT isn’t a connector question, it’s an architecture decision: one path leaves tags behind, two paths leave nothing on the shopfloor.<\/strong>“<\/h3>\n\n\n\n

\u2014 Dr. Diwaker Jha, Industrial Connectivity Expert, Cybus<\/em><\/h4>\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n

OPC UA and S7plus: Two Paths from Siemens PLC to MQTT<\/strong><\/strong><\/h2>\n\n\n\n
Feature<\/th>OPC UA (Built-in)<\/strong><\/th>S7plus (via Connectware)<\/strong><\/a><\/th><\/tr><\/thead>
Visibility Ceiling<\/strong><\/strong><\/td>~2,000 Nodes (S7-1200)<\/td>No node cap (All 18,000+ Tags)<\/td><\/tr>
Read Speed<\/strong><\/strong><\/strong><\/td>Bounded by node + sampling caps<\/td>~40 ms single \/ ~100 ms complex (tested on S7-1200)<\/td><\/tr>
Native Symbol Support<\/strong><\/strong><\/td>Yes (within budget)<\/td>Yes (Symbolic Addressing)<\/td><\/tr><\/tbody><\/table><\/figure>\n<\/div><\/div><\/div><\/div>\n\n\n\n
\n

Split the Controller, or Open a Second Path with S7plus<\/strong><\/strong><\/h2>\n\n\n\n

The traditional way past these limits is painful: “split” the controller. This involves adding new CPUs, spreading the logic across them and then performing a complete rewiring and revalidation. It is a capital-intensive project that demands significant downtime. <\/p>\n\n\n\n

A Factory Data Hub approach changes the math. By using S7plus \u2013 Siemens’ own native, high-speed protocol \u2013 you gain full visibility into the existing hardware. You keep the same CPU and the same program. You simply choose the right path for the volume of data required. Connectware speaks both, allowing you to lead with OPC UA and transition to S7plus as your data needs scale.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n

Bottom Line: Two Paths to Your Siemens Data, No Re-Engineering<\/strong><\/strong><\/strong><\/h2>\n\n\n\n

Many platforms stop at the built-in server’s limit. Connectware speaks both OPC UA and native S7plus \u2013 two paths to your Siemens data.<\/strong><\/p>\n\n\n\n

The alternative to a second data path is re-engineering the controller: adding CPUs, rewiring and revalidating, with the line down throughout. Production stoppages are expensive \u2013 Siemens’ own True Cost of Downtime 2024<\/a> puts unplanned downtime at 11% of annual revenue for the world’s largest manufacturers. S7plus avoids that work entirely: same controller, same program, every tag.<\/p>\n\n\n\n

As the single reliable source of truth between OT and IT, Connectware ensures your infrastructure never becomes your bottleneck. Whether you need the open standard of OPC UA or the full depth of S7plus, you have the road already paved. Don’t let a built-in server limit your factory’s intelligence.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n\n

\n
\n

Stop migrating data you can’t see<\/strong><\/h2>\n\n\n\n

Every tag your built-in server hides is a blind spot in your historian, MES and analytics. Connectware gets all of them into MQTT \u2013 OPC UA first, native S7plus when you need every tag, no re-engineering.<\/p>\n<\/div><\/div><\/div><\/div>\n\n\n

<\/p>\n

<\/div>\n