Industrial networks
Industrial Ethernet, Modbus, serial links, fieldbus and data exchange.
Latest articles
Troubleshooting
Why HMI Remote Access Fails While PLC Access Still Works
Working local traffic between the HMI and the PLCs proves only the switch path, not the default-gateway path a translated remote connection needs. Verify the panel's gateway field, the forwarded ports 6080, 6002 and 6000, and address duplication, in that order; a DHCP laptop with no Internet in the same building points at the same gateway branch.
How-to
Connecting an HMI to remote PLCs over a WAN
Yes, it is feasible: an operator panel supervises geographically distributed PLCs over Modbus TCP on port 502 exactly as on a LAN, provided every site is reached through a site-to-site VPN or approved routed path with a valid return route. Never expose port 502 by public port forwarding, because Modbus TCP carries no authentication or encryption.
How-to
How to Send String Data Over Modbus Between an HMI and a Gateway
Modbus defines only coils and 16-bit registers, so an HMI cannot write a native string tag to a gateway. Pack the text as two ASCII characters per holding register, agree byte order and a length word at both ends, and rebuild the text in a gateway script before it is applied.
How-to
Routing browser access to a fixed-IP HMI over two subnets
A router with one interface in each network is the correct way to join 192.168.2.x to a fixed 198.168.120.x panel, with a return route or scoped source NAT for the replies. Widening the mask to 255.255.0.0 cannot work because the two prefixes stay separate, and 198.168.x is not RFC 1918 space, so it must stay behind the router.
Troubleshooting
HMI Modbus TCP works locally but not remotely over cellular
A Modbus TCP slave reply to an off-subnet client needs a next hop, and the HMI gets that from its Ethernet gateway address. Local polls stay on the HMI's subnet and work with the field blank, which is exactly why the fault looks like a software problem. Enter the cellular modem's LAN address as the gateway, forward port 502 to the HMI, then prove each layer with a local poll, a poll through the modem, and the SCADA client.
Troubleshooting
Why a PLC Modbus Master Read Returns Nothing From an HMI
When a PLC Modbus RTU master polls an HMI slave and gets nothing back, three faults hide behind the flashing LED: DTR direction control left at 0 instead of 2, the wrong starting address for LB0, and a one-scan enable that kills the transaction before Done. Fix them in that order.
Troubleshooting
Decoding Modbus holding register 4500001 from PLC to HMI
Holding register 4500001 is a typed reference, not the address on the wire: the leading 4 marks the area, the rest is a 1-based register number, and under the six-digit convention it must fall inside 400001-465536, so the reachable target is 450001, protocol address 50000. Match the slave ID and 8E1 serial settings, prove the read with an independent master, then enter the address in the HMI driver's own convention.
Troubleshooting
WinCC Professional intermittent PLC connection loss diagnosis
Treat the aborted-connections value as a running count of dropped sessions, not fault code 5. Capture the channel log, a packet capture and the CPU's online diagnostics while the link is down, because a live HMI session proves only the HMI's path. The TIA Portal scan is a trigger, not a repair: the durable fix is normally the runtime computer's path, a stale ARP entry or PLC connection resources.
How-to
Choosing a Data Path From an M580 PLC to FactoryTalk View
RSLinx will show the M580 as an EtherNet/IP node once its EDS file is registered, but the tag browse stays empty because the controller presents no symbolic tag database over CIP. Pick the route from the tag structure: located %MW and %M data goes over Modbus TCP on port 502 or an EtherNet/IP assembly, and unlocated variables are only reachable through OFS serving OPC.
Comparison
Logging PLC Data to SQL: Use a Gateway, Not the HMI
Neither the S7-1200 nor a Comfort panel can be the SQL client: enabling OPC UA or loading MQTT blocks moves data, it does not commit transactions. Serve the logging tags from the S7-1200 over OPC UA and let a gateway beside the customer's database write the rows, keep the panel's CSV logging as the staged first move, and bench-test any direct-SQL library against the full 30-column record before purchase.
Troubleshooting
HMI Modbus timeout caused by a PLC master-slave conflict
When an HMI times out on every PLC on its RS-485 network, including units wired directly to it, suspect a master-slave conflict: one PLC port is configured as a Modbus master and transmits against the panel. Make the HMI the only polling master, set every polled PLC port to slave mode with a unique station address, then retest.
How-to
Connecting multiple S7-300 PLCs to WinCC stations
Connect the six S7-300 PLCs and the three WinCC stations over Industrial Ethernet with configured S7 connections; PROFIBUS DP allows only one cyclic master, so it cannot host three independent operator stations. A CP 343-1 Lean gives each PLC 8 S7 connections and the full CP 343-1 up to 16. Keep everything in one STEP 7 project so NetPro configures all connections in one place.