H2-DM1E Ethernet Timeout: Why Won't Designer Connect?

A CPU that goes online over USB but times out over Ethernet has an addressing fault, not a wiring fault. The Link Wizard blinking the ETH LED during Query is the tell: the discovery broadcast reached the module and the module answered. Cable, patch, switch port, and link negotiation are already proven. What fails is the step after discovery, where Do-more Designer stops broadcasting and tries to open a session to one specific host address.

Check the IP Field Before You Touch the Cable

Read the IP column in NetEdit or in the wizard's device list. An H2-DM1E that has never been addressed reports 255.255.255.255. That is the limited broadcast address. No host owns it, nothing can open a unicast session to it, and the wizard has no target once discovery finishes, so it runs out its timer and returns Ext error: Timeout error.

Swapping cables, ports, and laptops is the reflex fix and it burns an hour for nothing. The blink already cleared the physical path, and every PC on the segment reads the same all-ones address because that value lives in the CPU, not on the PC.

Bind the Query to the Right Adapter

NetEdit and the Link Wizard send the discovery broadcast out one adapter at a time. If the entry selected as default is a VPN tunnel, a virtual machine host-only adapter, a Bluetooth PAN, or a teaming interface, the broadcast never reaches the plant segment and the device list comes back empty or without a MAC. Selecting the physical NIC that is patched to the switch is what makes the module appear.

• Select the physical NIC explicitly in both NetEdit and the wizard. Do not trust the default entry.
• Disable the second physical NIC while commissioning if both sit on overlapping subnets. Windows will pick a route you did not intend.
• Windows Firewall drops the inbound UDP reply when the network profile is Public, even though the outbound query leaves cleanly. Allow NetEdit and Do-more Designer on the active profile, or reclassify the network as Work.
• Kill the VPN client. It reinstalls routes that swallow private subnets on reconnect.

Check before moving on: with the correct NIC selected, NetEdit lists the module and shows its MAC address. If no MAC appears on any adapter with the firewall off, stop chasing software and go back to the physical layer.

Write the Address Over USB

The USB link is the service port for exactly this situation. Use it to give the module a real address before you attempt any Ethernet link.

1. Connect USB and go online with Do-more Designer.
2. Open PLC > System Information.
3. Click Set Node and IP Configuration in the lower middle of the dialog.
4. Enter the IP address and subnet mask. Add the gateway only if Designer will reach the CPU across a router.
5. Write the configuration and close the dialog.

NetEdit does the same job without Designer: select the module by MAC in the device list, assign the IP configuration, and write it. Either path stores the address in the CPU's nonvolatile configuration, so it survives a power cycle without DHCP.

Check: reopen NetEdit and confirm the IP column shows the address you wrote instead of 255.255.255.255.

Put the PLC on the PC's Subnet

An address alone does not fix the timeout. The address and mask have to place the CPU on the same subnet as the PC running Designer, or the PC hands the packet to its gateway and you get the identical timeout with a legitimate-looking IP on the screen.

1. Run ipconfig /all on the PC and note the IPv4 address, subnet mask, and default gateway of the NIC you selected.
2. Pick a PLC address inside that subnet and outside the router's DHCP pool. Example only: PC at 192.168.1.50 / 255.255.255.0, PLC at 192.168.1.10 / 255.255.255.0, gateway 192.168.1.1.
3. Use the same subnet mask on both ends. A mask mismatch is the quiet failure that survives every other check.
4. Read the DHCP pool range out of the router before you commit the address. Get it running on a static address tonight, then add the MAC reservation when the network owner is on site.

Check: ping the PLC address from the PC. If the port answers ICMP you get replies. If it does not, run arp -a — an ARP entry carrying the MAC that NetEdit listed still confirms the module is answering on your segment at the address you set.

Build the Ethernet Link and Prove It

1. In Designer, create a new link and choose Ethernet in the Link Wizard.
2. Select UDP/IP as the protocol.
3. Select the physical NIC, then press Query.
4. Confirm the module now lists with its MAC and its configured IP, not the broadcast address.
5. Select it, name the link, finish, and go online.

End-to-end verification: with the USB cable unplugged, open PLC > System Information over the Ethernet link and confirm the node and IP settings read back the values you wrote. Then cycle CPU power, reconnect, and confirm the address is still there. Passing both means the configuration is in nonvolatile memory and the link is not depending on a stale discovery cache.

Watch the Repeat Offenders

• Duplicate address. The router leases your static IP to a laptop and the link drops intermittently. Move the PLC outside the pool or reserve it by MAC.
• Broadcast blocked. A managed switch or VLAN boundary kills the discovery broadcast. The Query list stays empty even though the module is addressed correctly — enter the IP address directly in the wizard instead of relying on Query.
• Adapter shuffle. Docking a laptop or plugging a USB-Ethernet dongle changes which NIC owns the route. Reselect the adapter, do not rebuild the link.
• Firewall profile flip. After a router reboot Windows can reclassify the network as Public and start dropping the replies again. Same symptom, same timeout.
• Link tied to a changed IP. A saved link points at the old address after someone re-addresses the CPU. Edit the link rather than debugging the network.

Stop here if the module shows no MAC in NetEdit with the PC cabled directly to the CPU, a static PC address set, and the firewall off — or if the IP configuration will not write over the USB link. Both point at the CPU's Ethernet hardware or its firmware, and neither is a night-shift repair. Open a case with AutomationDirect technical support with the module's MAC, the firmware revision from PLC > System Information, and the exact error text.

FAQ