IMDHMIControls LibraryShop main store

How-to

Why RSLinx shows no processor name for a MicroLogix 1100

Industrial networks Published 5 min read

Short answer

The MicroLogix 1100 Ethernet port reports its IP address and module type to RSWho, not the processor name, and no RSLinx or controller setting changes that. Label machines by creating one Ethernet Devices driver per machine, named for the machine, holding only that machine's addresses in its station mapping.

On this page
  1. What each device reports to RSWho
  2. Why renaming the project does not change the browse
  3. Build one named driver per machine
  4. Scattered addresses and the two-subnet plant
  5. Set the processor name in the project anyway
  6. Verify each machine before you retire the master list
  7. Dead ends worth skipping
  8. Questions asked

A MicroLogix 1100 on the RSLinx Ethernet Devices driver reports its IP address and module type to RSWho — 172.31.61.195 micro 1100 plc — and never its processor name. The string is fixed by what the controller's embedded Ethernet port reports; no setting in RSLinx or in the controller changes it, and engineers who escalated the question to Rockwell Automation support were told the same. The working fix is organizational: give each machine its own named Ethernet Devices driver holding only that machine's addresses, so the driver name does the labeling the controller cannot.

What each device reports to RSWho #

RSWho prints whatever identity string the device sends over the driver in use, which is why device families disagree under one browse:

Device and driver What RSWho shows Why
SLC 5/05 on the Ethernet Devices driver (ab_eth-1) IP plus processor name, e.g. 172.31.61.194 line 4 The channel reports the processor name once its address is in the station mapping
MicroLogix 1100 on ab_eth-1 IP plus module type, e.g. 172.31.61.195 micro 1100 plc The embedded port reports a fixed identity string with no name field
Any controller on the EtherNet/IP driver (ab_ethip-1) IP address only This driver's browse does not display processor names
1756-ENBT or 1756-ENET module Model string The module reports its catalog identity rather than a user name
1756-EWEB module The name you configured That module family carries a configurable identity

Read the table family by family. A mixed fleet will never look uniform in a single browse, and no amount of configuration makes it so.

Why renaming the project does not change the browse #

The processor name lives in the RSLogix 500 project and in the controller. Renaming it offline and downloading updates the name in both places, and the 1100's reported string still does not include it, so RSWho keeps printing the module type. Note the cost before you try: a download takes a running MicroLogix out of Run mode, so on a production machine it belongs in a planned window, never as a display fix. Skip it for that purpose.

Build one named driver per machine #

  1. Open RSLinx Classic and open its driver configuration screen, where drivers are added and edited.
  2. Add a new driver of the Ethernet Devices type — the same type as ab_eth-1.
  3. Replace the auto-numbered default name with the machine's name, for example Line 4.
  4. Open the new driver's configuration and enter only that machine's IP addresses in its station mapping.
  5. Repeat steps 2 through 4 for every machine, one driver per machine.
  6. Open RSWho and expand each driver: only that machine's controllers should sit under it.

Multiple Ethernet Devices drivers coexist without interacting — each is an independent station list. RSWho groups each machine's nodes under a name you chose, and the driver list replaces the master sheet of addresses you have been keeping.

Scattered addresses and the two-subnet plant #

A station mapping imposes no order on addresses, because each one is typed by hand. IT-assigned addresses scattered across a range work exactly like a tidy block, which matters on a plant network where you cannot request sequential IPs.

The same property carries a two-subnet plant — nodes on 172.31.61.0/24 and 172.31.62.0/24. The EtherNet/IP driver ab_ethip-1 discovers devices with broadcast traffic, which routers do not forward, so its browse stops at the local subnet; it also lists IP addresses only, so it could not label anything even if it reached them. The Ethernet Devices driver talks only to the addresses you enter, so both subnets can share one driver. Keep ab_eth-1 for this work; the EtherNet/IP driver is the one to use when a SCADA client reads a small PLC over EtherNet/IP, which is a different job.

Run the routing check once with your own numbers. Illustrative arithmetic for a PC running RSLinx at 172.31.61.10 with subnet mask 255.255.255.0 and two controllers to list:

  • 172.31.61.10 AND 255.255.255.0 = 172.31.61.0 — the PC's network part
  • 172.31.61.195 AND 255.255.255.0 = 172.31.61.0 — same network part, direct session
  • 172.31.62.30 AND 255.255.255.0 = 172.31.62.0 — third octet differs (62 against 61), routed session

Both controllers can sit in one machine's driver. The check narrows what to confirm with IT: the PC's default gateway is set, and any firewall between 172.31.61.0 and 172.31.62.0 passes the RSLinx traffic to those addresses. The naming method adds no other routing requirement.

Set the processor name in the project anyway #

The name never reaches RSWho on the 1100, but it identifies the program the moment someone opens RSLogix 500 online, and it does display in RSWho for the SLC 5/05 controllers in the same fleet.

  1. Open the project offline in RSLogix 500.
  2. Set the processor name in the controller properties to the same string as that machine's driver name.
  3. Download in a planned window.
  4. Go online through that driver and confirm the strings match.

One convention per machine, one label to maintain.

Verify each machine before you retire the master list #

  • Expand each named driver in RSWho and confirm its members are that machine's controllers and nothing else.
  • Ping every listed address from the RSLinx PC; an address that is listed but silent is a network or cabling problem, not a naming problem.
  • Go online through RSLogix 500 over that driver and confirm the project's processor name matches the driver name.
  • Exercise at least one node per subnet — one on 172.31.61.0/24, one on 172.31.62.0/24 — before calling the routing settled.
  • Retire the master address list only after every driver passes.
  • If a node disappears from the browse entirely after a communications change, that is a connection failure, not a naming limitation — the pattern covered in MicroLogix 1000 not found in RSLinx after a channel change.

Dead ends worth skipping #

  • Renaming the processor and downloading: it changes the project, not the 1100's reported string, and it costs a Run/Program cycle.
  • Hunting for an RSLinx display option for the 1100: the identity string has no name field to expose.
  • Switching to ab_ethip-1 for labels: an IP-only browse on a driver whose discovery stays on the local subnet.
  • Requesting consecutive addresses from IT: unnecessary when each address is entered manually.
  • Expecting every module to behave alike: each family reports its own identity, so treat them row by row.

Questions asked

Is there any RSLinx version that shows the MicroLogix 1100 processor name?

None has been reported. On the Ethernet Devices driver the 1100 always shows its IP address plus the module-type string, and engineers who took the question to Rockwell Automation support were told no way exists. If your unit ever displays a processor name on that driver, record the RSLinx revision and the 1100 firmware revision before assuming the behavior changed.

Why does the SLC 5/05 beside it show a name?

The 5/05 reports its processor name over the same Ethernet Devices driver once its address is in the station mapping. The 1100's embedded port reports a fixed module-type string instead. The difference sits in the device firmware, not in your configuration, which is why the two look inconsistent side by side in one browse.

How many Ethernet Devices drivers can one RSLinx installation run?

One per machine is the normal arrangement across a multi-line plant, and nothing in the driver configuration couples them or caps the count; each is an independent station list. The practical limit is discipline: a driver whose list grows beyond its machine's nodes stops being a label and becomes another master list.

Would the EtherNet/IP driver label the nodes better?

No. Its browse lists IP addresses only, and its discovery traffic is broadcast-based, which routers do not forward, so it stops at the local subnet. That is exactly why a plant spanning 172.31.61.0/24 and 172.31.62.0/24 stays on the Ethernet Devices driver, whose station mapping you fill in by hand.

Do station mapping addresses have to be consecutive?

No. Every address is entered manually in the driver's station mapping, so IT-assigned scattered addresses behave exactly like back-to-back ones, and one machine's driver can hold addresses from both plant subnets as long as the PC's routing reaches them.

Keep reading

  • Selection guide

    Connecting ControlLogix to RS232 and RS485 serial devices

    Convert the RS232 devices to RS485 at the electrical layer, then pick one master for the whole pair: 1734 ASCII modules for fixed-length or delimited frames, an in-chassis Modbus RTU module for a pure Modbus bus, or an EtherNet/IP-to-serial gateway with a protocol builder when variable-length checksummed frames share the wire with Modbus RTU. One master serializes every transaction behind the 3.5-character silent gap, 3.65 ms at 9600 baud.

    Industrial networks

  • Troubleshooting

    Why a Schneider M251 does not appear in RSLinx

    RSLinx and FactoryTalk Linx browse one transaction: the EtherNet/IP List Identity request, and a device appears only when the port you are cabled to answers it. Ping and Schneider software prove IP reachability, nothing more. Enable the M251's EtherNet/IP service on the connected port, browse through the right PC adapter, and register the M251 EDS when the entry shows a red X with a yellow question mark.

    Industrial networks

  • How-to

    Configure a PowerFlex 525 on EtherNet/IP from an Omron NJ301

    The tag data link fails after a good ping because the NJ, as the EtherNet/IP originator, must send the drive's chosen output assembly plus a 32-bit Run/Idle header: error 0x0127 means the output connection size is wrong. Import the revision-matched EDS, select the target assemblies it lists, create Input and Output network variables of exactly those sizes with the header included, and register them on the Tag Set tab.

    Industrial networks