An SMH4 0011000 controller may appear once in SMLogix over USB and later return “controller not found.” The evidence shows a reliable workaround: connect the controller through LAN and run SMLogix on Windows 10 Pro. Treat the USB cable, USB driver, and interfering software as diagnostic hypotheses rather than confirmed root causes.
Observed SMLogix connection behavior
| Environment | Observed result | Engineering conclusion |
|---|---|---|
| Windows XP SP3, USB | The driver installed with a compatibility warning. The first communication test succeeded and reported 192.168.111.2, but subsequent tests could not find the controller. | Do not rely on this combination; SMLogix operation on Windows XP had not been tested for years. |
| Windows 7, USB | Windows detected the device but could not locate a driver. | The USB path was not commissioned successfully. |
| Windows 10 Pro, USB | Windows installed a driver, but the SMLogix communication test reported no USB connection. | Automatic driver installation did not prove application-level communication. |
| Windows 10 Pro, LAN | SMLogix detected the controller reliably and maintained a stable connection. | Use LAN as the supported field workaround for this symptom set. |
Separate the reported faults
The communication history contains two distinct failures. One is transport detection: SMLogix cannot find the SMH4 through USB. The other is the message that smconfig initialization is incomplete. The latter appeared after an initially successful USB communication test, so it does not establish that the later USB detection failures have the same cause.
Firewall configuration changes did not restore the Windows 10 USB connection. Possible interfering software and a poor-quality USB cable were suggested as causes, while the Windows 7 driver failure was considered a possible cable-quality indicator. Neither hypothesis was confirmed by the available test results.
Restore engineering access through LAN
- Stop using Windows XP as the validation platform for this issue because current SMLogix operation there was not being tested.
- Connect the SMH4 to the engineering computer through LAN instead of the controller’s mini-USB port.
- Run SMLogix on Windows 10 Pro and execute its communication test.
- Proceed with application testing only after SMLogix detects the controller consistently across repeated tests.
Do not assume that the USB-reported address 192.168.111.2 is the required LAN address; the evidence identifies it only as the address reported during the first successful USB session. Determine the active LAN configuration from the actual controller and network setup.
Verify the workaround
Acceptance requires more than one successful discovery. Repeat the SMLogix communication test and confirm that controller visibility remains stable. The reported resolution met this criterion on Windows 10 Pro over LAN. If USB operation remains a project requirement, test the cable, driver installation, and potentially interfering software individually; the evidence does not identify which one caused the USB failure.
FAQ
Why does SMLogix say the SMH4 controller is not found over USB?
The available evidence does not confirm one root cause. Driver handling, interfering software, and USB cable quality remain hypotheses; LAN on Windows 10 Pro restored stable access.
Can SMLogix connect to an SMH4 through LAN instead of USB?
Yes. For the SMH4 0011000 in this case, SMLogix detected the controller reliably and remained stable over LAN on Windows 10 Pro.
Should I configure the LAN connection as 192.168.111.2?
Not from this evidence alone. SMLogix reported 192.168.111.2 during an initial USB session; verify the controller’s actual LAN configuration before assigning or using an Ethernet address.