Remote access and virtualization
Remote access, virtualization, containers and thin clients.
Latest articles
How-to
Connecting an SLC 5/03 PLC to an industrial remote access router
Connect the SLC 5/03's 9-pin channel 0, left in its default DF1 mode, to the router's serial port with a null-modem RS-232 cable at 19,200 baud, keeping it under 3 m. The rectangular port is DH-485 on RS-485 wiring at 19.2 kbps, needs an interface module, and must never meet an Ethernet jack.
Troubleshooting
Troubleshooting a PLC agent that will not go online remotely
A green remote session proves only that you reached the gateway. Prove the programming connection locally first, then the agent's target address and subnet, then the agent type and protocol, then the client — one boundary at a time. Most of these faults are a mistyped target address or an agent type that carries the wrong protocol.
Comparison
Thick client or thin client HMI for a control system upgrade
A thin-client HMI does not remove processor, memory, disk and network load; it concentrates all of it in one server and one network, so one failure can blank every operator position. Choose thin clients only if the site can staff, back up and recover that server; otherwise refresh thick clients, where a failure costs one station. Virtualizing the Windows XP HMI is a transition, not a modernization.
Troubleshooting
Using a USB programming cable inside a Hyper-V VM
Hyper-V gives Generation 1 guests no USB passthrough, so a Siemens USB PPI or MPI cable cannot appear inside the VM. Redirect the cable's host COM port over RDP, or move to an Ethernet-to-PPI adapter with an emulation driver on an isolated subnet; fix host-to-guest networking with an internal virtual switch and static IP addresses.
Troubleshooting
Running x86 Windows guests on an ARM host
An ARM virtualization host cannot boot an x86 Windows guest: a hypervisor passes through the processor's own instruction set, and VMware Fusion on Apple silicon documents 64-bit ARM guests only. Run x86 applications inside a Windows 11 ARM guest under emulation; keep kernel-driver workloads on an x86 host.
How-to
Running Studio 5000 in a VM with licensing and PLC access
Yes. Give each programming suite its own guest, serve FactoryTalk Activation from the host or a dedicated license VM so a rebuilt guest needs no rehost, and bind the guest to the physical NIC that carries the engineering network before touching USB passthrough. A guest that opens Logix Designer but cannot acquire a license or reach the controller has only passed installation.
Troubleshooting
Run a remote access VPN from your VM with NAT mode
Set the VM's network adapter to NAT and the guest adapter to DHCP, because NAT translates guest traffic through the host's routing table, including the routes a host-side VPN client adds. Bridged mode fails because the guest appears on the plant LAN as its own device and never sees those routes. Verify by pinging a remote site device from the guest.
Troubleshooting
Ping works but PLC program download fails over remote access
ICMP success proves only the routed IP path, not the programming session. A download opens separate query and download connections on documented TCP and UDP ports, and broadcast discovery does not cross a routed VPN. Point the controller's default gateway at the remote-access router LAN address, permit both programming ports to the controller LAN IP, and add the controller manually by IP.
How-to
P2V migration plan for an aging Windows machine controller
Converter 6.3 does not support Windows 7 as the computer it installs on, which is what the openssl.exe startup failure and the Error 29190 SSL-key message are reporting. Stop installing on the failing controller: back it up, run the converter from a supported management computer, and convert the Windows 7 source only with a release whose supported lists cover it — otherwise rebuild on a supported system. Current 6.6 and 9.0 lists start at Windows Server 2012 and Windows 10.
Troubleshooting
Mounting a VMware shared folder in a Linux automation VM
The error means the guest has no vmhgfs kernel filesystem — the share is not missing, because vmware-hgfsclient already proves discovery works. On a guest using packaged open-vm-tools, run sudo vmhgfs-fuse .host:/ /mnt/hgfs instead. If /usr/bin/vmhgfs-fuse does not exist, repair open-vm-tools first and change no network settings.
Troubleshooting
Fixing a VMware VM stuck with a multi-monitor layout
When a VMware guest keeps drawing a three-monitor layout on one panel after undocking, the host and the guest both report a single display, so the fault sits in the Workstation window, not in the VM configuration. Switch the application theme to Light — switch away and back if it is already Light — to force the window rebuild, keep Monitors on Use host settings for monitors, and exit Unity before you unplug the externals.
Comparison
Remote SCADA access through firewalls and proxies
Put the SCADA application and its data connections on the plant side of the firewall and carry only an authenticated VPN tunnel and a rendered remote session across it. A proxy forwards traffic under its administrator's policy and issues no licenses; session CALs are deployed and tracked on the session host. Restrict tunnel routes to that one host, license by counted people or devices, and keep direct port forwarding to an HMI host out of the design.