Troubleshooting
MicroLogix 1000 not found in RSLinx after a channel change
Short answer
The MicroLogix 1000 is missing from RSLinx because the channel-configuration download changed its serial port from DF-1 to DH-485, so the DF-1 driver and Auto-Configure can never verify against it. Reach the controller through DH-485 with a 1747-UIC at its default 19200 baud, go online, set Channel Configuration back to DF-1, download, and re-run Auto-Configure.
On this page
- Why did the MicroLogix 1000 disappear from RSLinx right after the download?
- What does "unable to verify setting" actually tell you?
- Which two drivers does a MicroLogix 1000 actually need?
- How do I confirm which protocol the channel is running now?
- What hardware reaches DH-485 from a PC?
- Why does the round-connector cable choice matter so much?
- How do I set the channel back to DF-1 without losing the connection?
- How do I prove the repair and keep it?
- Questions asked
The controller is not broken. The channel-configuration download that went in before the HMI work moved the MicroLogix 1000's serial port from DF-1 to DH-485, and from that moment a DF-1 driver in RSLinx can never verify against it — Auto-Configure ends with "unable to verify setting" no matter which serial values it tries. The recovery is to connect through the protocol now configured — a 1747-UIC interface converter on DH-485 — go online, set Channel Configuration back to DF-1, download, and re-run Auto-Configure on the DF-1 driver.
Why did the MicroLogix 1000 disappear from RSLinx right after the download? #
Because the download replaced DF-1 with DH-485 on the controller's only serial port: from that moment the port answers DH-485 frames, and no DF-1 driver setting — any baud, any COM port — will make Auto-Configure verify.
The dividing line is the download, not the hardware. A port running DH-485 does not answer DF-1 requests, even though the round connector still fits the same 1761-CBL family cable and the port is electrically healthy. Everything before that download worked; everything after it fails on the same cable — that pattern points at configuration, not at a failed port or converter. The controller also accepted the download and kept running, which is itself evidence the processor is fine.
What does "unable to verify setting" actually tell you? #
It means RSLinx finished probing serial parameters inside the selected driver's protocol and never received a valid reply — a protocol, COM-port, or cable mismatch, and not evidence that the controller has failed.
Auto-Configure tests serial settings within the communication format of the driver you picked. It does not convert a DF-1 driver into a DH-485 driver, and it does not ask the port to change language. When controller and driver speak different link protocols, every probed baud and parity combination can be electrically valid and still draw no recognizable reply. Read two things before touching anything: the Auto-Configure result, and what RSWho shows.
| What you observe | What it means | What to do |
|---|---|---|
| Auto-Configure succeeds and the controller appears in RSWho | Driver and physical path work | Save the configuration; investigate the programming-software path only if another connection still fails |
| Auto-Configure reports "unable to verify setting" | No valid protocol exchange completed | Check COM port, then protocol, then cable and adapter, in that order |
| The old driver worked before the channel change and no longer verifies | The download most likely replaced DF-1 with DH-485 | Confirm the protocol offline, then use the matching driver |
| Several unrelated drivers all fail | Driver substitution is hiding the real branch | Stop swapping drivers; identify the configured protocol first |
Which two drivers does a MicroLogix 1000 actually need? #
Two: DF-1 over RS-232, which every MicroLogix 1000 carries, and DH-485, which many units carry — the driver must match whichever mode the channel runs right now, and nothing else is worth trying.
Disable or close the other drivers while you test, so an RSWho result cannot be mistaken for this controller. DF-1 over RS-232 with the correct COM port and Auto-Configure is the everyday path. DF-1 is also not a single dialect across controller families — the same lesson runs through why DF-1 reads work on an SLC 500 but not a PLC-5. On the DH-485 side, one DH-485 driver with the right station setup browses the link, the same way an SLC 5/05 and a MicroLogix 1100 are linked over DH-485. Trying DH+ or Ethernet drivers against a serial port wastes the afternoon.
How do I confirm which protocol the channel is running now? #
Open the last project that was downloaded, in RSLogix 500, and read its Channel Configuration offline: the mode listed there is what the port is running, and that download is the dividing line between working and broken comms.
Do not infer the protocol from the cable or from the series letter — a Series E marking identifies a hardware revision, not the active mode. The MicroLogix 1000 has one round serial port, so whichever mode the project carries is the only mode that port runs; a MicroLogix 1500 differs in that it can run DF-1 on its RS-232 channel and DH-485 on a second channel at the same time. Branch on what the offline project shows:
- Project shows DF-1 — keep the DF-1 serial driver, verify the COM port and cable, and run Auto-Configure again.
- Project shows DH-485 — stop running DF-1 Auto-Configure and build the DH-485 path in the next section.
- Project unavailable or uncertain — test one known-good DF-1 path first: right COM port, right cable, sound converter. If verification still fails after those checks, treat the channel as DH-485 and recover through it.
What hardware reaches DH-485 from a PC? #
A 1747-UIC interface converter, which communicates on DH-485 at 19200 baud by default, or a 1761-NET-AIC (AIC+) that converts the controller's RS-232 to isolated DH-485 — plus the matching RSLinx driver pointed at the COM port Windows assigned.
Install the UIC and let Windows finish, then read the COM number in Device Manager under Ports. That number, and nothing else, is what the RSLinx DH-485 driver gets. If the driver's port differs from Device Manager, correct the driver. If the port does not appear at all, reinstall the UIC or move it to another USB socket. If another program owns the port, close it.
The UIC runs DH-485 at 19200 baud by default, with a documented method to move it to 9600 when a link requires it — touch that only if the controller side is not 19200. The 1761-NET-AIC (AIC+) is the alternative when the DH-485 side needs isolation or multiple drops: it converts the controller's RS-232 onto the DH-485 network. Some users report the UIC settles on DF-1 or DH-485 depending on what it connects to; treat that as convenient, and still configure the RSLinx driver deliberately.
Why does the round-connector cable choice matter so much? #
Because the MicroLogix round serial connector carries a power pin meant to feed a 1761-NET-AIC, and a 1761-family cable that routes that pin into an ordinary USB-serial converter can upset the converter — read the full cable catalog number before connecting anything.
The 1761-CBL family covers several pinouts, and "a 1761 cable" is not a specification. The round connector carries a pin whose job is to power an AIC+ through the matching cable; a cable that presents that pin to a plain USB-serial converter can upset the converter or the link. Confirm the full cable catalog number and where its power pin is routed before connecting it to a powered path, because that pin can damage equipment not built to receive it. If the converter itself is suspect and every configuration check has passed, substitute a single known-good unit — FTDI-chipset converters are a common field choice — and change nothing else, so the test isolates a single variable.
How do I set the channel back to DF-1 without losing the connection? #
Go online through DH-485 first: with the UIC path working and the controller visible in RSWho, open Channel Configuration in the running project, change the mode from DH-485 to DF-1, and download — keeping the DH-485 path connected until the download finishes.
- Install the 1747-UIC and record the COM port Windows assigns (illustrative example: COM7).
- In RSLinx Classic, open Communications → Configure, add the DH-485 driver, and point it at that COM port.
- Browse RSWho under that driver; the controller appears at its node address, and the MicroLogix default is node 1.
- In RSLogix 500, go online through Comms → System Comms with RSLinx already running.
- Open Channel Configuration, set the communication mode back to DF-1, and download.
- Expect the session to drop when the protocol changes — that is the change taking effect, not a fault.
- Reconfigure RSLinx with a DF-1 driver on the same COM port and run Auto-Configure; it should verify.
Worked example with the numbers: the offline project shows Channel Configuration = DH-485, 19200 baud, node address 1. The UIC default for DH-485 is also 19200 baud, so 19200 = 19200: the speeds already match and the 9600 option stays untouched. Windows assigns the UIC COM7 (illustrative), so the DH-485 driver is set to COM7. RSWho shows the controller at node 1, alone on the link, so the address is unique. After the DF-1 download, Auto-Configure on the same COM7 finds the DF-1 serial settings, and the configuration you keep is the DF-1 driver.
How do I prove the repair and keep it? #
Re-browse RSWho away from the driver and back, go online and confirm the project and channel mode, cycle the PC-side connection and confirm the controller reappears with no setting changes, then save the driver set with the RSLinx Classic Backup Restore utility.
- Browse away from the driver in RSWho and back; the controller must reappear each time.
- Go online and confirm the project and channel mode now show DF-1.
- Cycle the PC-side connection only: close RSLinx, reopen it, and confirm the controller reappears with no setting changes.
- Save the known-good driver configuration with the RSLinx Classic Backup Restore utility.
- Record the protocol, driver type, COM port, controller catalog number, cable catalog number, and interface used.
Before the next HMI-driven channel change, read the mode the project writes and decide it deliberately. The decision in one line: channel running DH-485 — recover through the UIC and revert online; channel running DF-1 — fix the COM port and cable and stop swapping drivers.
Questions asked
My controller is a MicroLogix 1000 Series E — does that guarantee DH-485?
No. The series letter marks the hardware revision, not the active communication mode, and DH-485 availability depends on the individual controller. What settles the question is the download itself: if the controller accepted a channel configuration containing DH-485, the port is speaking DH-485 on that link now, whatever the label says. Every MicroLogix 1000 still carries DF-1 capability, so the DF-1 end-state is always available to recover to.
Can Auto-Configure detect DH-485 settings if I keep trying it on the DF-1 driver?
No. Auto-Configure searches serial parameters — baud, parity, stop bits — inside the protocol of the driver you selected; that protocol stays fixed during the search. If the controller channel is running DH-485, every DF-1 probe can be electrically sound and still draw no valid reply, which is exactly the unable to verify setting result you are seeing.
Which COM port should the 1747-UIC driver use in RSLinx?
The one Windows assigned to the UIC. Read it in Device Manager under Ports, then select that same number when you configure the RSLinx driver, and close any other application holding the port. The UIC communicates DH-485 at 19200 baud by default, so a controller also running 19200 needs no speed change; a documented method exists to move the UIC to 9600 when a link actually requires it.
Do I need the 1747-UIC, or will a plain USB-to-serial converter work?
A plain RS-232 converter with the right 1761-family cable handles DF-1. For DH-485 you need the UIC, or a 1761-NET-AIC (AIC+) converting the controller's RS-232 side onto an isolated DH-485 network. FTDI-chipset converters are a common field choice when a substitute is needed; swap one in and change nothing else, so the test isolates a single variable.
Will changing the channel back and forth damage the controller?
No. A channel-configuration download changes communication settings, not firmware, and a protocol change dropping your session is expected behavior, not a fault. Keep the working DH-485 path connected until the DF-1 download completes, then reconnect through a DF-1 driver and let Auto-Configure confirm the new settings before saving the configuration with the Backup Restore utility.