Industrial networks
Earlier articles
Troubleshooting
Why a PC Fails to Reach an HMI When Wi-Fi Owns Its Address
The wired programming connection fails because the laptop's Wi-Fi adapter already owns 192.168.0.20, the exact HMI address, so Windows treats the target as local and never sends packets out the Ethernet port. Disable Wi-Fi or move the HMI to an address no local interface owns, such as 192.168.0.25, and the connection returns.
Troubleshooting
Why a Modbus RTU Master Write Never Reaches an HMI Holding Register
Check four layers in order: bond both devices to the supply's minus terminal as the common DC reference, not the chassis-connected GND terminal; match master and slave roles plus 9600 8E1 framing; sniff the bus to confirm the full frame arrives with a valid CRC, because an early driver-enable release corrupts the last byte; and enter register 40001 as address 0x0000 on the wire.
Troubleshooting
Troubleshooting E-Designer and Q03UDECPU Ethernet comms
A dead E-Designer panel comes down to three checks before transport settings matter: Controller 1 moved from Unused to Ethernet, the cable in the configured port, and a full power cycle after the Q03UDECPU's parameters were downloaded. Run them in that order.
How-to
Sending SMS from an HMI through an HTTP GET modem
Tag-based HMI runtimes have no HTTP client, so a relay — a controller HTTP block, an industrial PC script or a gateway — sits between the HMI and the modem. The HMI sets a trigger tag, the relay fires the documented HTTP GET at the modem's SMS feature, and a send-busy-done-error handshake guarantees exactly one SMS per button press. Prove the request in a PC browser before writing any HMI logic.
How-to
Remote HMI access with dynamic DNS and a VPN
Never port-forward an HMI to the public internet. Reach Vijeo Design Air through a VPN that ends inside the plant network, and let dynamic DNS track the site's changing public address so the VPN client always finds the endpoint. The app itself keeps using the HMI's private IP address on the Wi-Fi and VPN paths alike.
How-to
How to Share One RS-485 PLC Port Between Multiple HMIs
Yes: several HMIs can share one RS-485 PLC port when the protocol coordinates who transmits — DH-485 token passing is the classic case — and every node holds a unique address. RS-485 itself only sets the electrical layer: 32 unit loads per segment, up to 1,200 m (4,000 ft) at low speed. Prove one panel, then add the rest one at a time and retest together.
Troubleshooting
Gateway setup when a network scan finds no Linux runtime
A runtime you can start from the Development Environment but cannot find with Scan for Devices is reachable for management but not for discovery. Install Gateway for Linux on the Debian industrial PC, add a gateway entry in the project that points at that PC's IP address, select it, and scan again; the IPC then appears.
How-to
Connecting an HMI to a Saitel DP embedded web interface
A Saitel DP has no dedicated physical screen; its embedded webserver is the standard operator interface, served over the network to any modern JavaScript- and HTML5-capable browser. Connect a browser terminal to the Saitel DP's subnet, open the configured address, and accept the hardware only after the exact model and browser version pass a live display test.
Troubleshooting
Choosing the RS-485 protocol for one HMI and multiple PLCs
Count the conductors before you open the HMI driver. On a 2-wire RS-485 DL-06 Port 2, Modbus RTU is the only protocol the port runs; rewire as 4-wire and K-sequence, DirectNET and Modbus RTU all open up, Modbus RTU fastest of the three. Give every PLC a unique station address, match baud and framing at both ends, and bring PLCs onto the bus one at a time.
Troubleshooting
Why One PLC to Two HMIs Fails Over RS-422 Multilink
A 1:1 serial test proves one cable and one framing set; it cannot prove a shared n:1 multilink. Fix two HMIs on one RS-422 trunk by running the multilink driver entry on both panels, giving each a unique link identity, matching every serial parameter, and terminating only the trunk ends. The documented limit is 16 displays, so two panels are a configuration problem, never a capacity one.
How-to
How to Send HMI RTC Time to a PCB Over Modbus
Modbus never broadcasts the panel clock. Configure the HMI as a Modbus client and let it write six holding registers — year, month, day, hour, minute, second — with function code 16 about once per minute, capturing all six values as one snapshot so a rollover never mixes an old date with a new time.
Troubleshooting
Building the RS-232 Modbus cable between an HMI and a controller
Map the pins by signal name, not by number: the HMI's transmit on 25-pin pin 2 goes to the controller's receive, the HMI's receive on pin 3 comes from the controller's transmit, and signal common runs end to end. The jumper between pins 8 and 12 stays at the HMI connector. Generic straight-through and null-modem cables cause silence because the 25-pin and 9-pin standards number the data lines differently.