- Challenge
- Siemens and Delta PLC data stayed inside an isolated factory network. Checking a machine meant being on the floor.
- Approach
- A hand-built ESP/NodeMCU bridge off that network, Node-RED and OPC UA for the protocols, and an Express and MongoDB backend behind a secured tunnel.
- Impact
- A plant manager sees machine status and switches the PLC-driven AC unit on or off from anywhere. Live at one manufacturing site.
1Isolated PLCs
Siemens and Delta PLCs sit on a factory network with no internet access.
2First hop
A hand-built ESP/NodeMCU bridge gets their signals off that network.
3Protocol layer
Node-RED and OPC UA handle the industrial protocols, so the Express API only sees clean events.
4Store and serve
The API stores readings in MongoDB and serves the remote dashboard.
5Both directions
Through a secured tunnel, a plant manager sees machine status and can switch the PLC-driven AC unit on or off.
- Deployment
- One manufacturing site
- Bridge hardware
- ESP/NodeMCU, initial version
- Remote access
- Secured tunnel to a live dashboard
Problem
Machine state lived entirely inside the plant’s isolated OT network. Siemens and Delta PLCs spoke OPC UA / Modbus to each other and to floor-local panels, but nothing about that state reached the inventory platform, and nothing about it reached anyone off the factory floor. A plant manager who wanted to check machine status, or toggle equipment like the PLC-driven AC unit, had to be physically on-site.
Constraints
- Factory OT network is isolated by design, with no direct exposure to the internet
- Siemens/Delta gear speaks OPC UA / Modbus, not anything web-native
- One site, real production line, no tolerance for downtime while building the bridge
- Remote access has to be secured, not just “open a port”
Approach
The first version of the bridge was built from scratch on ESP/NodeMCU hardware: the actual mechanism that gets a signal off the isolated PLC network and into anything IoT-reachable. Node-RED and an OPC UA adapter sit on top of that bridge, translating controller events into a stream the Express API can consume alongside inventory data.
Pieces that matter
- ESP/NodeMCU bridge: the actual first hop off an isolated PLC network, designed and built as the initial version before anything else in the pipeline existed
- Node-RED + OPC UA adapter: keeps industrial protocol handling out of core business logic in the Express API
- Secured tunnel: the remote dashboard isn’t just port-forwarded; access is tunneled and authenticated
- Two-way channel: the dashboard isn’t read-only telemetry; it can switch equipment (the PLC-driven AC unit) on or off remotely
Tradeoff
Rejected alternative: wait for a proper industrial IoT gateway product and integrate against it. That would have avoided the risk of depending on a bridge nobody else maintains. Building one instead meant owning a bespoke bridge on ESP/NodeMCU hardware, and in exchange the plant got live machine data without waiting on a vendor. It runs at the plant today against Siemens and Delta PLCs; a second site or another PLC vendor is the next test of the adapter layer.
Evidence
- Machine telemetry that was previously invisible off the plant floor now reaches the inventory platform
- A plant manager can view machine status and switch the PLC-driven AC unit on or off from anywhere, through a secured tunnel, not from the plant floor only
- Deployed and running in production at the manufacturing site




