diff --git a/src/blog/2025/01/integrating-siemens-s7-plcs-with-node-red-guide.md b/src/blog/2025/01/integrating-siemens-s7-plcs-with-node-red-guide.md index bc481e6829..040b2ab2d6 100644 --- a/src/blog/2025/01/integrating-siemens-s7-plcs-with-node-red-guide.md +++ b/src/blog/2025/01/integrating-siemens-s7-plcs-with-node-red-guide.md @@ -233,4 +233,6 @@ Make sure the IP addresses of your device and PLC are in the same subnet. If the ## Conclusion -Integrating Siemens S7 PLCs with Node-RED opens up powerful automation possibilities with minimal complexity. By following the steps outlined in this guide, you can easily connect your PLC to Node-RED, control devices, and visualize real-time data on dashboards. Whether you're writing data to control outputs or reading sensor values, Node-RED offers a flexible, user-friendly platform for industrial automation. \ No newline at end of file +Integrating Siemens S7 PLCs with Node-RED opens up powerful automation possibilities with minimal complexity. By following the steps outlined in this guide, you can easily connect your PLC to Node-RED, control devices, and visualize real-time data on dashboards. Whether you're writing data to control outputs or reading sensor values, Node-RED offers a flexible, user-friendly platform for industrial automation. + +Beyond Siemens S7, FlowFuse connects Allen-Bradley, Omron, Beckhoff, and any Modbus or OPC UA-enabled PLC to MQTT, cloud, and enterprise systems. See the [FlowFuse PLC integration overview](/landing/plc/) for all supported protocols and use cases. \ No newline at end of file diff --git a/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md b/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md index 7bb061ac18..8313dada01 100644 --- a/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md +++ b/src/blog/2025/07/reading-and-writing-plc-data-using-opc-ua.md @@ -277,3 +277,5 @@ This guide covered the basics, but OPC UA offers far more. In the next article, When it is time to move beyond prototypes, **FlowFuse** delivers what industrial systems truly need—remote device management, instant rollbacks with full version control, built-in team collaboration, and high availability you can trust. If you’re ready to simplify your OPC UA integration and scale industrial workflows with Node-RED, [start your free trial]({% include "sign-up-url.njk" %}) of FlowFuse today. + +OPC UA is one of several protocols FlowFuse uses to connect PLCs to MQTT, cloud platforms, and enterprise systems. See the [FlowFuse PLC integration overview](/landing/plc/) for EtherNet/IP, Siemens S7, Modbus, and more. diff --git a/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md b/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md index bad2cd1f40..634cf4904e 100644 --- a/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md +++ b/src/blog/2025/08/advanced-opcua-real-time-subscriptions-alarms-historical-data.md @@ -285,4 +285,6 @@ Managing OPC UA flows across multiple sites? FlowFuse helps teams deploy Node-RE Following our managed MQTT broker, we've now added database services built right into the platform, plus new AI features that make building flows faster than ever. +Connecting PLCs beyond OPC UA? FlowFuse also supports Siemens S7, EtherNet/IP, Modbus TCP/RTU, and MQTT — see the [FlowFuse PLC integration overview](/landing/plc/) for all supported protocols and use cases. + [Get started free]({% include "sign-up-url.njk" %}) and scale and manage your Node-RED deployments today. diff --git a/src/blog/2025/09/using-modbus-with-flowfuse.md b/src/blog/2025/09/using-modbus-with-flowfuse.md index 4a37f4676f..e5563779fd 100644 --- a/src/blog/2025/09/using-modbus-with-flowfuse.md +++ b/src/blog/2025/09/using-modbus-with-flowfuse.md @@ -172,3 +172,5 @@ Modbus RTU has stood the test of time in industrial automation because it’s si * Scale from a single sensor to a **factory-wide monitoring and control system**. The real value comes when you stop treating Modbus as just a communication protocol and start using FlowFuse as the **bridge between industrial devices and enterprise systems**. From dashboards to alerts, from analytics to cloud integration — the possibilities are endless once the data is in your hands. + +Modbus is one of several protocols FlowFuse uses to connect PLCs — see [how FlowFuse connects any PLC to MQTT, cloud, and enterprise systems](/landing/plc/) for the full picture. diff --git a/src/blog/2025/10/how-to-log-plc-data-csv-files.md b/src/blog/2025/10/how-to-log-plc-data-csv-files.md index 6ad60380f1..37e10debbb 100644 --- a/src/blog/2025/10/how-to-log-plc-data-csv-files.md +++ b/src/blog/2025/10/how-to-log-plc-data-csv-files.md @@ -232,4 +232,6 @@ FlowFuse makes this process straightforward by combining Node-RED’s flexibilit And while CSV is a reliable starting point, FlowFuse also integrates seamlessly with modern databases and historians like InfluxDB, TimescaleDB, and MySQL. Even better, FlowFuse Cloud includes a built-in PostgreSQL service and an AI Query Node that lets you explore your data conversationally — turning raw logs into actionable insights. +For more on how FlowFuse connects PLCs across OPC UA, Siemens S7, EtherNet/IP, and Modbus to collect and route industrial data, see the [FlowFuse PLC integration overview](/landing/plc/). + > You can [talk to our team](/book-demo/), they’ll walk you through a live demo showing how FlowFuse helps you connect, collect, transform, and visualize your industrial data reliably and intelligently. diff --git a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md index 26460ada13..9eaea723c3 100644 --- a/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md +++ b/src/blog/2025/10/plc-to-mqtt-using-flowfuse.md @@ -195,3 +195,5 @@ Manufacturers typically see substantial cost reduction in the first year, with i ## Get Started Connect your first PLC today. [Sign up for FlowFuse](https://app.flowfuse.com/), install the Device Agent on your edge hardware, and have data flowing to MQTT in under an hour. The platform handles the complexity—you focus on turning factory data into insights. + +MQTT is one of several ways FlowFuse connects PLCs to the modern industrial stack. For a full view of supported protocols — OPC UA, EtherNet/IP, Siemens S7, Modbus, and more — see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md index 9cf58ba9a0..94d11cb070 100644 --- a/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md +++ b/src/blog/2025/10/using-ethernet-ip-with-flowfuse.md @@ -239,6 +239,6 @@ Check out our [Getting Started with Dashboard guide](/blog/2024/03/dashboard-get ### Beyond Allen-Bradley -FlowFuse isn't limited to EtherNet/IP. Connect Siemens PLCs via S7, use OPC UA for vendor-neutral communication, integrate Modbus devices, or connect IoT sensors with MQTT. Mix protocols as needed—your factory floor probably isn't single-vendor anyway. +FlowFuse isn't limited to EtherNet/IP. Connect Siemens PLCs via S7, use OPC UA for vendor-neutral communication, integrate Modbus devices, or connect IoT sensors with MQTT. Mix protocols as needed—your factory floor probably isn't single-vendor anyway. For a full view of every supported PLC brand and protocol, see the [FlowFuse PLC integration overview](/landing/plc/). [Book a demo](/book-demo/) to see how FlowFuse connects your entire operation. diff --git a/src/blog/2025/11/building-hmi-for-equipment-control.md b/src/blog/2025/11/building-hmi-for-equipment-control.md index dfe4798434..50e5e7ff2a 100644 --- a/src/blog/2025/11/building-hmi-for-equipment-control.md +++ b/src/blog/2025/11/building-hmi-for-equipment-control.md @@ -260,4 +260,6 @@ As your system grows, organize controls across multiple dashboard pages for diff And if you need to deploy the solution across many production lines, FlowFuse's DevOps features help you manage the scale. Build your HMI once, then deploy it across multiple edge devices and push updates centrally without visiting each location. +For a full view of the PLC brands and protocols FlowFuse supports — Siemens, Allen-Bradley, Omron, OPC UA, Modbus, and more — see [how FlowFuse connects any PLC to the modern industrial stack](/landing/plc/). + [Book a demo](/book-demo/) to see how FlowFuse can help your organization connect, collect, transform, and visualize industrial data with our low-code and AI-powered editor—without the hassle of infrastructure management, deployment complexities, or security concerns at scale. diff --git a/src/blog/2025/11/store-and-forward-edge-data-buffering.md b/src/blog/2025/11/store-and-forward-edge-data-buffering.md index d5b6e602b1..a8520a77b6 100644 --- a/src/blog/2025/11/store-and-forward-edge-data-buffering.md +++ b/src/blog/2025/11/store-and-forward-edge-data-buffering.md @@ -346,3 +346,5 @@ This pattern solves a common problem in industrial environments: maintaining com The system you've built is production-ready as-is, but you can extend it based on your requirements—add monitoring for buffer capacity, implement data validation rules, or configure forwarding to multiple destinations. The core mechanism remains the same. If you want to get the flow template that you can use directly and modify according to your needs, check out our [latest blueprint](/blueprints/getting-started/store-and-forward/). + +Store-and-forward is just one part of a complete PLC integration. For the full picture — connecting Siemens, Allen-Bradley, Omron, and other PLCs to MQTT, cloud, and enterprise systems — see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2025/12/what-is-plc.md b/src/blog/2025/12/what-is-plc.md index 58a1deee90..1beca3e3f8 100644 --- a/src/blog/2025/12/what-is-plc.md +++ b/src/blog/2025/12/what-is-plc.md @@ -214,7 +214,7 @@ A single Node-RED instance can simultaneously communicate with Siemens S7 PLCs, FlowFuse adds the enterprise infrastructure: centralized management across hundreds of edge devices, version control and rollback, role-based access, audit logging, and security at every layer. Build one flow that reads from Siemens PLCs and deploy it to every facility. When something changes, update once and push the change everywhere. Edge instances run locally even if network connections drop. -FlowFuse doesn't replace your PLCs. It connects them. That Rockwell controller keeps running its proven logic. The Siemens system continues its scan cycle. What changes is the integration layer that lets isolated systems finally communicate. +[FlowFuse doesn't replace your PLCs. It connects them.](/landing/plc/) That Rockwell controller keeps running its proven logic. The Siemens system continues its scan cycle. What changes is the integration layer that lets isolated systems finally communicate. A [large US manufacturing company](/customer-stories/manufacturing-digital-transformation/) with over 10,000 employees uses FlowFuse to manage thousands of Node-RED instances deployed across global facilities. These instances collect data from sensors, PLCs, and cameras on production lines, enabling them to transition from paper-based operations to real-time data visibility. A team of five developers—former manufacturing engineers, not software specialists—built hundreds of applications using Node-RED's visual programming. FlowFuse now manages deployment to thousands of remote devices and maintains multiple versions across all instances, solving what had become an unmanageable tracking challenge as they scaled. diff --git a/src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md b/src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md index 6d4c9ee29c..18345cfac3 100644 --- a/src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md +++ b/src/blog/2026/01/eliminate-opc-ua-bottleneck-ai-agents.md @@ -103,4 +103,6 @@ This isn't about replacing people with automation. It's about making the data in And it's not limited to OPC UA. FlowFuse's MCP approach works the same way across any industrial system—MQTT brokers, Modbus devices, SQL databases, REST APIs, whatever protocols you're running. Same natural language interface, same investigation capabilities, different underlying systems. The infrastructure you have becomes the infrastructure you can actually use. +For a complete guide to connecting PLCs via OPC UA, EtherNet/IP, Siemens S7, and Modbus to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/). + diff --git a/src/blog/2026/01/kepware-opcua-better-alternative.md b/src/blog/2026/01/kepware-opcua-better-alternative.md index e87cd5a3b7..4f79f63404 100644 --- a/src/blog/2026/01/kepware-opcua-better-alternative.md +++ b/src/blog/2026/01/kepware-opcua-better-alternative.md @@ -112,3 +112,5 @@ Kepware functions reliably. That's not disputed. But reliability alone doesn't j Evaluate alternatives now from strength. Or negotiate renewals later from weakness under new ownership terms. Kepware won through early dominance and ecosystem lock-in. That's separate from being the right architecture for current operations. + +See [how FlowFuse connects any PLC to MQTT, OPC UA, cloud, and enterprise systems](/landing/plc/) — without per-tag licensing or proprietary lock-in. diff --git a/src/blog/2026/01/opcua-vs-mqtt.md b/src/blog/2026/01/opcua-vs-mqtt.md index c18b0b1dfb..5f3a2f9bd9 100644 --- a/src/blog/2026/01/opcua-vs-mqtt.md +++ b/src/blog/2026/01/opcua-vs-mqtt.md @@ -258,3 +258,5 @@ The right question isn't "MQTT or OPC UA?" It's "MQTT where? OPC UA where? Both where?" Answer that based on your requirements, not vendor marketing. + +For a practical guide to connecting PLCs via both OPC UA and MQTT in FlowFuse — alongside EtherNet/IP, Siemens S7, and Modbus — see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2026/01/why-modbus-still-exist.md b/src/blog/2026/01/why-modbus-still-exist.md index 97c23da2ea..39feaf24ad 100644 --- a/src/blog/2026/01/why-modbus-still-exist.md +++ b/src/blog/2026/01/why-modbus-still-exist.md @@ -118,4 +118,4 @@ The result is a patchwork that reflects industrial reality rather than protocol This approach proves that Modbus survives not because it's technically superior, but because it solves real problems with minimal friction. The protocol succeeded by being simple enough that anyone can implement it, cheap enough that everyone does, and reliable enough that nobody has to think about it. -FlowFuse is the industrial data platform designed to bridge this gap between legacy Modbus registers and modern enterprise systems. Our platform provides the connectivity and security layers needed to transform aging infrastructure into a secure, data-driven operation. +FlowFuse is the industrial data platform designed to bridge this gap between legacy Modbus registers and modern enterprise systems. Our platform provides the connectivity and security layers needed to transform aging infrastructure into a secure, data-driven operation. See [how FlowFuse connects Modbus PLCs — and every other PLC brand — to MQTT, cloud, and enterprise systems](/landing/plc/). diff --git a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md index 60a02bdfe3..c84e3e21a9 100644 --- a/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md +++ b/src/blog/2026/02/modbus-tcp-vs-modbus-rtu.md @@ -106,3 +106,5 @@ If you are deploying TCP: isolate Modbus devices on a dedicated VLAN or network If you are maintaining a hybrid gateway architecture, resist the urge to rationalize it away. It is doing work. The two protocols make different guarantees, fail differently, and require different diagnostic skills when something goes wrong. Understanding that distinction before the system is designed costs nothing. Understanding it for the first time during an incident costs considerably more. + +For a practical guide to connecting Modbus PLCs — alongside OPC UA, EtherNet/IP, and Siemens S7 — to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2026/03/how-to-connect-to-twincat-using-ads.md b/src/blog/2026/03/how-to-connect-to-twincat-using-ads.md index ccb3243ed8..a7afcb488b 100644 --- a/src/blog/2026/03/how-to-connect-to-twincat-using-ads.md +++ b/src/blog/2026/03/how-to-connect-to-twincat-using-ads.md @@ -338,3 +338,5 @@ You now have a working ADS connection between FlowFuse and TwinCAT, reading vari This guide covered the core nodes to get you connected and working. The `node-red-contrib-ads-client` package includes several other nodes worth exploring on your own, and future articles will cover more advanced use cases in depth. With FlowFuse you can take this further. Build real-time dashboards that visualize live PLC data, connect TwinCAT to other systems like databases, ERP, or cloud platforms, set up alerts when variables go out of range, and create operator interfaces that let your team interact with the machine from anywhere. All of it built on the same connection you just configured, without writing a single line of custom integration code. + +Beckhoff TwinCAT ADS is one of many PLCs FlowFuse connects to the modern industrial stack. For Siemens, Allen-Bradley, Omron, Modbus, OPC UA, and more, see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2026/04/connect-industrial-edge-devices-aws-iot-core.md b/src/blog/2026/04/connect-industrial-edge-devices-aws-iot-core.md index 623862894b..99d220636d 100644 --- a/src/blog/2026/04/connect-industrial-edge-devices-aws-iot-core.md +++ b/src/blog/2026/04/connect-industrial-edge-devices-aws-iot-core.md @@ -221,3 +221,5 @@ A few things worth doing before you go to production: **Monitor connection state.** Add a status node in Node-RED connected to your mqtt out node. If the connection drops, you'll want to know immediately — not when someone notices missing data an hour later. Industrial data pipelines aren't complex. They just have a lot of small steps that have to be right. You've done the hard part. + +For more on how FlowFuse connects PLCs and edge devices — via OPC UA, EtherNet/IP, Siemens S7, and Modbus — to cloud and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2026/04/diagnosing-modbus-degradation.md b/src/blog/2026/04/diagnosing-modbus-degradation.md index a4ac706429..cffb61fe20 100644 --- a/src/blog/2026/04/diagnosing-modbus-degradation.md +++ b/src/blog/2026/04/diagnosing-modbus-degradation.md @@ -177,3 +177,5 @@ Physical changes to the RS-485 segment (wiring, termination, baud rate or parity What keeps a Modbus installation stable for years is mostly mundane: a poll list reviewed quarterly against the actual field, scan rates tiered with the reasoning written down, timeouts calculated from measured device response times rather than defaults, and per-device success rates visible on a dashboard that someone checks regularly enough to catch drift before it becomes failure. None of it is sophisticated. All of it requires treating the Modbus layer as something that needs ongoing maintenance, not a configuration artifact from the last integration project. If you've worked through both parts and the installation is still misbehaving, you're likely past what configuration review can resolve. Power quality on the RS-485 segment, a device firmware bug producing malformed responses on specific register ranges, or a network infrastructure change that introduced unexpected latency: these are real causes that look like everything else until you rule everything else out. A [protocol capture](https://en.wikipedia.org/wiki/Packet_analyzer) on the wire during an active failure event will tell you more in twenty minutes than another hour of configuration review. At that point, that's where to start. + +For a guide to connecting Modbus PLCs — alongside OPC UA, EtherNet/IP, and Siemens S7 — to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2026/04/modbus-polling-best-practices.md b/src/blog/2026/04/modbus-polling-best-practices.md index 64f7d17737..d261df8cb5 100644 --- a/src/blog/2026/04/modbus-polling-best-practices.md +++ b/src/blog/2026/04/modbus-polling-best-practices.md @@ -140,3 +140,5 @@ The three problems this article covers, scan rate uniformity, timeout miscalcula The fix for all three is the same kind of work: deliberate, once, documented. Tier your scan rates to match how fast your data actually changes. Calculate your timeouts from the physics of your network rather than accepting defaults. Read the register map before you batch. None of this takes long. None of it requires downtime. It just requires treating these as decisions rather than defaults. If you've made these changes and your installation is still misbehaving, the problem is in the operational layer: how your polling architecture handles the network and devices once they're running. The next article covers that: serial versus TCP failure modes, unresponsive device handling, live diagnostics, and how to fix what you find without taking production down. + +For a complete guide to connecting Modbus PLCs — alongside OPC UA, EtherNet/IP, and Siemens S7 — to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/blog/2026/04/stop-noisy-sensor-data-deadband-filter-flowfuse.md b/src/blog/2026/04/stop-noisy-sensor-data-deadband-filter-flowfuse.md index 6a9a6f3c1c..6306f2a4fc 100644 --- a/src/blog/2026/04/stop-noisy-sensor-data-deadband-filter-flowfuse.md +++ b/src/blog/2026/04/stop-noisy-sensor-data-deadband-filter-flowfuse.md @@ -115,3 +115,5 @@ A deadband filter solves this with a single comparison. No complex logic, no add But filtering noise is just one piece of a reliable industrial data pipeline. FlowFuse goes further. It simplifies collecting data from any device or protocol, implementing patterns like deadband filtering, [store and forward](/blog/2025/11/store-and-forward-edge-data-buffering/) to handle network interruptions, [dead letter queues](/blog/2026/03/how-to-implement-dlq-and-retries/) to catch and recover failed messages, and much more. All of it managed centrally, deployed consistently, and running reliably across your entire fleet. The filter handles the noise. FlowFuse handles everything else. + +For more on how FlowFuse connects PLCs and sensors — via OPC UA, Modbus, EtherNet/IP, and Siemens S7 — to MQTT, cloud, and enterprise systems, see the [FlowFuse PLC integration overview](/landing/plc/). diff --git a/src/landing/images/plc-landing-image.png b/src/landing/images/plc-landing-image.png new file mode 100644 index 0000000000..5e74e0d827 Binary files /dev/null and b/src/landing/images/plc-landing-image.png differ diff --git a/src/landing/plc.njk b/src/landing/plc.njk new file mode 100644 index 0000000000..ba637c62f3 --- /dev/null +++ b/src/landing/plc.njk @@ -0,0 +1,420 @@ +--- +layout: page +nohero: true +meta: + title: "PLC Integration Platform | Connect PLCs to MQTT, Cloud & SCADA | FlowFuse" + description: "Connect any PLC — Siemens S7, Allen-Bradley, Omron, Mitsubishi — to MQTT, OPC UA, cloud, and enterprise systems. FlowFuse makes PLC data integration fast with low-code flows." + keywords: "plc, programmable logic controller, plc integration, plc mqtt, node-red plc, opc ua plc, plc to cloud, siemens plc, allen bradley plc, plc data collection, plc logging, what is a plc, plc control system" + faq: + - question: "What is a PLC (Programmable Logic Controller)?" + answer: > + A Programmable Logic Controller (PLC) is an industrial computer used to automate manufacturing processes — controlling machines, assembly lines, conveyor belts, and other equipment on the factory floor. PLCs continuously read inputs from sensors and actuators, execute a control program, and send output signals to drive motors, valves, and other devices. Common PLC brands include Siemens (S7-300, S7-400, S7-1200, S7-1500), Allen-Bradley (Rockwell Automation ControlLogix, CompactLogix), Omron, Mitsubishi, Schneider Electric, and Beckhoff. + - question: "How does FlowFuse connect to PLCs?" + answer: > + FlowFuse connects to PLCs via industrial protocols including OPC UA, MQTT, Modbus TCP/RTU, EtherNet/IP (for Allen-Bradley), and the Siemens S7 protocol using a built-in low-code runtime. You drag in a certified protocol node, enter your PLC's IP address or endpoint, and data flows immediately. No custom code, no expensive gateways, no vendor lock-in. + - question: "Which PLC brands does FlowFuse support?" + answer: > + FlowFuse supports virtually all major PLC brands: Siemens (S7-1200, S7-1500, S7-300, S7-400), Allen-Bradley / Rockwell Automation (ControlLogix, CompactLogix via EtherNet/IP), Omron, Mitsubishi, Schneider Electric, Beckhoff TwinCAT, and any PLC that exposes OPC UA or Modbus TCP. If your PLC speaks a standard industrial protocol, FlowFuse can connect it. + - question: "Can I connect a PLC to MQTT using FlowFuse?" + answer: > + Yes. Connecting a PLC to MQTT is one of the most common FlowFuse use cases. FlowFuse reads tag data from your PLC (via OPC UA, S7, EtherNet/IP, or Modbus), transforms it as needed, and publishes it to any MQTT broker — including AWS IoT, Azure IoT Hub, HiveMQ, Mosquitto, or the built-in FlowFuse MQTT Broker. This is the foundation for building a Unified Namespace (UNS) or streaming factory data to the cloud. + - question: "How do I collect and log data from a PLC?" + answer: > + In FlowFuse, you build a flow that polls your PLC at a set interval (or subscribes to events), transforms the tag data, and writes it to your destination — a CSV file, InfluxDB, TimescaleDB, PostgreSQL, or a cloud data lake. You can also trigger logging on events (alarms, production counts, shift changes) rather than polling. FlowFuse manages deployment, versioning, and monitoring of these flows across multiple edge devices. + - question: "Can FlowFuse replace my existing SCADA system?" + answer: > + FlowFuse can augment or replace traditional SCADA systems. It provides real-time monitoring, custom dashboards via FlowFuse Dashboard, alarm management, and control logic — without the cost and inflexibility of monolithic SCADA software. Many organizations start by running FlowFuse alongside their existing SCADA to add cloud connectivity or modern dashboards, then expand from there. + - question: "Does FlowFuse work on-premises or in the cloud?" + answer: > + Both. FlowFuse runs on FlowFuse Cloud (fully managed, no infrastructure to maintain), self-managed on your own servers or private cloud, or directly on edge devices running the FlowFuse Device Agent. For PLC connectivity, many teams deploy the Device Agent on an industrial PC close to the machines, so data never has to leave the plant unless you choose to send it. +image: /landing/images/plc-landing-image.png +protocols: + - icon: "components/icons/globe-alt.svg" + title: "OPC UA" + description: "The IIoT standard. Connect to any OPC UA-enabled PLC — Siemens, Allen-Bradley, Beckhoff, and more — with built-in security and structured data models." + links: + - text: "OPC UA Tutorial →" + url: "/blog/2025/07/reading-and-writing-plc-data-using-opc-ua/" + - icon: "components/icons/wifi.svg" + title: "MQTT" + description: "Publish PLC tag data to any MQTT broker — AWS IoT, Azure IoT Hub, HiveMQ, or the built-in FlowFuse MQTT Broker. The foundation of a Unified Namespace." + links: + - text: "PLC to MQTT Guide →" + url: "/blog/2025/10/plc-to-mqtt-using-flowfuse/" + - icon: "components/icons/chip.svg" + title: "EtherNet/IP" + description: "Native Allen-Bradley / Rockwell communication. Read and write tags on ControlLogix and CompactLogix PLCs without a gateway." + links: + - text: "EtherNet/IP Guide →" + url: "/blog/2025/10/using-ethernet-ip-with-flowfuse/" + - icon: "components/icons/server-stack.svg" + title: "Siemens S7 Protocol" + description: "Direct S7comm connectivity to Siemens S7-300, S7-400, S7-1200, and S7-1500 PLCs. Read DB blocks, Merkers, I/O, and more." + links: + - text: "Siemens S7 Integration Guide →" + url: "/blog/2025/01/integrating-siemens-s7-plcs-with-node-red-guide/" + - icon: "components/icons/arrows-pointing-out.svg" + title: "Modbus TCP / RTU" + description: "The universal open protocol. Connect legacy PLCs, drives, meters, and sensors that speak Modbus — over Ethernet or serial." + links: + - text: "Modbus Guide →" + url: "/blog/2025/09/using-modbus-with-flowfuse/" + - icon: "components/icons/squares-plus.svg" + title: "5,000+ Community Nodes" + description: "Beyond the basics: PROFINET, BACnet, DNP3, IEC 61850, Mitsubishi MC Protocol, Omron FINS, Beckhoff TwinCAT ADS, and more — all available as open-source community nodes." + links: + - text: "Browse Node Library →" + url: "/integrations/" +steps: + - number: "1" + title: "Connect Your PLC" + description: "Drop a protocol node into your flow canvas — OPC UA, S7, EtherNet/IP, or Modbus. Enter your PLC's IP address and tag list. Data starts flowing in seconds." + - number: "2" + title: "Transform & Route" + description: "Filter, scale, aggregate, or enrich tag data using visual flow logic. Route it to MQTT, databases, dashboards, REST APIs, or cloud services — all in one flow." + - number: "3" + title: "Deploy & Scale" + description: "Push your flow to one edge device or a thousand with one click. Monitor health, update remotely, roll back instantly — all from the FlowFuse central platform." +advantages: + - title: "Protocol-agnostic" + description: "One platform connects Siemens, Allen-Bradley, Omron, Mitsubishi, legacy Modbus, and modern OPC UA — no vendor lock-in." + - title: "Low-code, fast to deploy" + description: "Drag-and-drop flows replace months of custom integration work. Go from PLC to live dashboard in hours, not weeks." + - title: "Edge + cloud flexibility" + description: "Run close to the machine on an industrial PC, in your private cloud, or on FlowFuse Cloud — or all three simultaneously." + - title: "Store-and-forward resilience" + description: "Buffer PLC data locally during network outages and forward it when connectivity is restored — zero data loss at the edge." + - title: "Open-source core" + description: "5,000+ open-source community nodes for protocols, integrations, and data transformation. No proprietary runtime fees, no protocol licensing costs." + - title: "Enterprise-ready" + description: "Role-based access, audit logs, DevOps pipelines, team collaboration, and professional support — for production OT environments." +resources: + - title: "How to Connect Any PLC to MQTT in Under an Hour" + image: "./blog/2025/10/images/plc-to-mqtt.png" + alt: "PLC to MQTT integration diagram" + url: "/blog/2025/10/plc-to-mqtt-using-flowfuse/" + - title: "OPC UA Tutorial: Connect and Exchange Data with Industrial Equipment" + image: "blog/2025/07/images/opcua-tutorial.png" + alt: "OPC UA tutorial illustration" + url: "/blog/2025/07/reading-and-writing-plc-data-using-opc-ua/" + - title: "How to Log PLC Data to CSV Files" + image: "./blog/2025/10/images/log-plc-data-to-csv.png" + alt: "PLC data logging illustration" + url: "/blog/2025/10/how-to-log-plc-data-csv-files/" + - title: "Getting Started: Integrating Siemens S7 PLCs with Node-RED" + image: "./blog/2025/01/images/s7-with-node-red.png" + alt: "Siemens S7 PLC integration guide" + url: "/blog/2025/01/integrating-siemens-s7-plcs-with-node-red-guide/" + - title: "EtherNet/IP Integration: Communicating with Allen-Bradley PLCs" + image: "./blog/2025/10/images/allen-bradly-plc.png" + alt: "Allen-Bradley PLC with EtherNet/IP" + url: "/blog/2025/10/using-ethernet-ip-with-flowfuse/" + - title: "How to Connect to Beckhoff TwinCAT PLC Using ADS" + image: "./blog/2026/03/images/backoff-twincat.png" + alt: "Beckhoff TwinCAT ADS integration" + url: "/blog/2026/03/how-to-connect-to-twincat-using-ads/" + - title: "Building a Web HMI for Factory Equipment Control" + image: "./blog/2025/11/images/building-a-web-hmi-for-factory.png" + alt: "Web HMI dashboard for factory" + url: "/blog/2025/11/building-hmi-for-equipment-control/" + - title: "Store-and-Forward: Buffering PLC Data During Network Outages" + image: "./blog/2025/11/images/store-and-forward.png" + alt: "Store and forward edge buffering" + url: "/blog/2025/11/store-and-forward-edge-data-buffering/" +--- + +
+ + +
+
+
+
+

+ Connect Your PLCs to the Modern Industrial Stack +

+

+ FlowFuse bridges Programmable Logic Controllers — Siemens, Allen-Bradley, Omron, and more — to MQTT, OPC UA, cloud platforms, and enterprise systems. No expensive gateways, no custom code. +

+
+ TALK TO AN EXPERT + GET STARTED FREE +
+
+
+
+ {% image "./images/plc-landing-image.png", "PLC connected to cloud, MQTT, and dashboards via FlowFuse", [496] %} +
+
+
+
+
+ + +
+
+

What is a PLC?

+
+
+

+ A Programmable Logic Controller (PLC) is a ruggedized industrial computer that automates electromechanical processes on the factory floor — controlling machines, conveyor belts, assembly lines, packaging systems, and more. +

+

+ PLCs continuously execute a scan cycle: they read inputs from sensors and field devices, run a control program (written in ladder logic, structured text, or function block diagrams), and write outputs to actuators, motors, and valves. +

+

+ Originally designed for deterministic machine control, modern PLCs also expose data over standard industrial protocols — making them the primary data source for IIoT, SCADA, MES, and digital transformation initiatives. +

+ Deep dive: What Is a PLC? → +
+
+
+

Common PLC Brands

+
    +
  • Siemens — S7-300, S7-400, S7-1200, S7-1500
    • +
  • Allen-Bradley (Rockwell) — ControlLogix, CompactLogix
    • +
  • Omron — NJ / NX Series
    • +
  • Mitsubishi — MELSEC iQ-R / Q Series
    • +
  • Schneider Electric — Modicon M340, M580
    • +
  • Beckhoff — TwinCAT
    • +
+
+
+

Common PLC Protocols

+
    +
  • OPC UA — vendor-neutral, secure
    • +
  • MQTT — lightweight publish/subscribe
    • +
  • EtherNet/IP — Allen-Bradley native
    • +
  • Siemens S7 — S7comm / S7comm-plus
    • +
  • Modbus TCP / RTU — legacy & open
    • +
  • PROFINET / PROFIBUS — Siemens field bus
    • +
+
+
+
+
+
+ + +
+
+
+

PLC data is valuable — but hard to get out

+

+ PLCs generate rich, real-time data — production counts, machine states, alarms, energy readings — but that data is often trapped. Getting it into dashboards, databases, cloud analytics, or ERP systems traditionally requires expensive SCADA licenses, proprietary gateways, or months of custom integration work. FlowFuse changes that. +

+
+
+
+ + +
+
+

How FlowFuse Connects to Any PLC

+

+ FlowFuse's built-in low-code runtime includes 5,000+ nodes for industrial protocols. Drag in a protocol node, configure your PLC's address, and data flows. No gateway hardware required. +

+ +
+ {% for protocol in protocols %} +
+
+ {% include protocol.icon %} +
+

{{ protocol.title }}

+

{{ protocol.description }}

+ {% for link in protocol.links %} + {{ link.text }} + {% endfor %} +
+ {% endfor %} +
+
+
+ + +
+
+

What You Can Build with PLC + FlowFuse

+ +
+ +
+
+ {% include "components/icons/circle-stack.svg" %} +
+
+

PLC Data Logging

+

+ Collect tag values, machine states, and counters at any interval. Write to InfluxDB, TimescaleDB, PostgreSQL, or CSV — for OEE tracking, trend analysis, and compliance. +

+ How to Log PLC Data → +
+
+ +
+
+ {% include "components/icons/computer-desktop.svg" %} +
+
+

Web HMI & Dashboards

+

+ Build modern operator interfaces that display live PLC data — gauges, trends, alarms, and controls — accessible from any browser without proprietary HMI software. +

+ Building a Web HMI → +
+
+ +
+
+ {% include "components/icons/cloud.svg" %} +
+
+

PLC to Cloud Integration

+

+ Stream PLC data to AWS IoT, Azure IoT Hub, Google Cloud, or any REST API. Enable predictive maintenance, AI analytics, and enterprise reporting without replacing your PLCs. +

+ PLC to Cloud Integration Guide → +
+
+ +
+
+ {% include "components/icons/link.svg" %} +
+
+

PLC to MES / ERP Integration

+

+ Bridge the OT/IT gap. Route production counts, downtime events, and quality data from PLCs directly into SAP, Oracle, or any MES — eliminating manual entry and delays. +

+ Enterprise Integration → +
+
+ +
+
+ {% include "components/icons/bell-alert.svg" %} +
+
+

Alarm Management

+

+ Subscribe to PLC fault bits and alarm words, route notifications to Slack, email, SMS, or PagerDuty, and log alarm history for root-cause analysis. +

+
+
+ +
+
+ {% include "components/icons/wifi.svg" %} +
+
+

Unified Namespace (UNS)

+

+ Use FlowFuse as the adapter layer between your PLCs and an MQTT-based UNS. Normalize data from Siemens, Allen-Bradley, and legacy equipment into a common topic hierarchy. +

+ Learn about UNS → +
+
+ +
+
+
+ + +
+
+

From PLC to Insight in 3 Steps

+
+ {% for step in steps %} +
+
{{ step.number }}
+

{{ step.title }}

+

{{ step.description }}

+
+ {% endfor %} +
+
+
+ + +
+
+

The FlowFuse Advantage

+
+ {% for item in advantages %} +
+

{{ item.title }}

+

{{ item.description }}

+
+ {% endfor %} +
+
+
+ + +
+
+

+ Frequently Asked Questions +

+ {% include "faq.njk" %} +
+
+ + +
+
+

Learn More: PLC Integration Guides

+ +
+ {% for resource in resources %} + +
  • +
    + {% image resource.image, resource.alt, [208] %} +
    + +
    • +     + {% endfor %} +
    +
    +
    + + +
    +
    +
    +

    Ready to unlock your PLC data?

    +

    + Stop paying for expensive gateways and inflexible SCADA licenses. See how FlowFuse connects your PLCs to the modern industrial stack — in a live demo or a free trial. +

    +
    + Book a Demo + Get Started Free +
    +
    +
    +
    + +
    diff --git a/src/node-red/protocol/modbus.md b/src/node-red/protocol/modbus.md index 19896d8efe..c89fb3ae7d 100644 --- a/src/node-red/protocol/modbus.md +++ b/src/node-red/protocol/modbus.md @@ -140,3 +140,5 @@ Final flow is given below: {% endrenderFlow %} The way that we set up this example worked well for the small sample size and quickly getting content on the dashboard, but as you work through your own needs, think about the data structures that will be the most conducive to efficiently working with your data. + +Modbus is one of several industrial protocols FlowFuse supports for connecting PLCs to MQTT, cloud platforms, and enterprise systems. See the [FlowFuse PLC integration overview](/landing/plc/) for OPC UA, EtherNet/IP, Siemens S7, and more. diff --git a/src/node-red/protocol/opc-ua.md b/src/node-red/protocol/opc-ua.md index c2fbf25a7e..a2b29ede58 100644 --- a/src/node-red/protocol/opc-ua.md +++ b/src/node-red/protocol/opc-ua.md @@ -618,6 +618,8 @@ With the foundation laid in this documentation, you can customize the applicatio In the next documentation of the OPC UA series, we will establish how to create an OPC UA Client application in Node-RED. +OPC UA is one of several industrial protocols FlowFuse uses to connect PLCs to the modern stack. For EtherNet/IP, Siemens S7, Modbus, MQTT, and more, see the [FlowFuse PLC integration overview](/landing/plc/). + Source code for flow used in this documentation - {% renderFlow %} diff --git a/src/solutions/edge-connectivity.njk b/src/solutions/edge-connectivity.njk index 4ed085bc5d..d7fd864a55 100644 --- a/src/solutions/edge-connectivity.njk +++ b/src/solutions/edge-connectivity.njk @@ -5,7 +5,7 @@ image: /images/solutions/og-solutions-edge-connectivity.jpg subtitle: heroImg: ./images/pictograms/edge_blue.png description: -

    FlowFuse simplifies the management of deployments to edge devices in manufacturing, from equipment to PLCs. Our platform ensures secure and reliable handling of large-scale deployments, providing seamless edge connectivity solutions.

    +

    FlowFuse simplifies the management of deployments to edge devices in manufacturing, from equipment to PLCs. Our platform ensures secure and reliable handling of large-scale deployments, providing seamless edge connectivity solutions.

    ---
    diff --git a/src/solutions/scada.njk b/src/solutions/scada.njk index 105c7409a9..1565633ee6 100644 --- a/src/solutions/scada.njk +++ b/src/solutions/scada.njk @@ -98,6 +98,7 @@ meta: {% for p in howSection.p3 %}

    {{ p }}

    {% endfor %} +

    FlowFuse connects Siemens, Allen-Bradley, Omron, and other PLCs to MQTT, OPC UA, cloud, and enterprise systems — without expensive gateways or proprietary lock-in. See the FlowFuse PLC integration overview for all supported protocols and use cases.