Troubleshooting
Why a Schneider M251 does not appear in RSLinx
Short answer
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.
On this page
An M251 that answers ping and the Schneider programming software is a healthy IP device, and neither fact has anything to do with 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. Your controller is invisible for one of two reasons. Either the EtherNet/IP service is not enabled on the port your cable occupies, so no reply ever comes back, or the reply comes back and the entry appears with a red X and a yellow question mark because the EDS is not registered. Work those two causes in that order and the M251 shows up.
What the browse actually asks for #
Ethernet is transport; the applications riding on it are separate transactions. Ping is ICMP. The Schneider engineering connection and any Modbus TCP clients run their own protocols. EtherNet/IP — the ODVA protocol that Rockwell tools browse — defines one discovery transaction: a List Identity request that the target must answer. That reply is the only thing that puts a node in the browse tree, so RSLinx is not a network inventory, and adding drivers does not change what it can see.
The two drivers you configured do different jobs. The EtherNet/IP driver sends List Identity requests out of the network adapter you point it at. The Ethernet Devices driver holds addresses you type in and queries them directly. A manually entered address still has to be answered by a protocol the driver speaks, so typing the M251's address into it produces nothing while the port stays silent. No driver combination browses a device that does not reply.
Close the addressing step with arithmetic #
Ping already succeeded on the 192.168.5 network with mask 255.255.255.0, and the subnet arithmetic shows why that settles the IP layer. Take example host addresses on that network, a PC at 192.168.5.50 and the controller at 192.168.5.120:
192.168.5.50 AND 255.255.255.0 -> 192.168.5.0
192.168.5.120 AND 255.255.255.0 -> 192.168.5.0
Both hosts resolve to 192.168.5.0, so delivery is local — no router, no gateway in the path. Decision: addressing is closed, and time spent re-checking IP settings is time taken from the two real candidates, the controller's EtherNet/IP service and the PC's adapter selection. Run one duplicate-address check (a second device holding the same IP can answer ping while breaking application traffic), then leave this layer alone.
The controller side: the service is per port #
The M251 has two Ethernet ports, and the EtherNet/IP service is enabled per port in the controller's Ethernet configuration, inside the Schneider programming software — no Rockwell tool can switch it on from outside. When ping works and every driver comes back empty, this is the usual cause: the service sits on the other port, or on none. Enable it on the port your cable occupies and download the configuration to the controller, scheduling the download for a moment when the machine can take the update. Schneider documents this same service for an M251-to-M221 EtherNet/IP link, so the setting and its setup examples live on the Schneider side.
Plan around one documented limit while you are in there. The M251 programming guide states that with at least one EtherNet/IP target configured, total connections — EtherNet/IP plus Modbus TCP together — are limited to 16. The arithmetic is short: 12 Modbus TCP clients already connected plus 4 EtherNet/IP targets equals 16, which is the whole pool, and a 17th connection is refused.
The PC side: one adapter, one path #
The List Identity broadcast leaves through one network adapter. A PC carrying a live wireless link, a VPN tunnel and the wired 192.168.5.x connection can send discovery out the wrong interface while your ping, addressed and therefore routed correctly, keeps succeeding. Disable every adapter except the wired one, or confirm which adapter the EtherNet/IP driver is configured to use, before touching the controller again.
Use the two drivers to split the fault. An empty EtherNet/IP browse tells you little on its own, so add an Ethernet Devices driver entry with the controller's exact address. A dead entry means no reply reached the PC, pointing back to the service or the path; an entry that appears but is not recognized moves the problem to EDS registration. If the device that will not appear is a Rockwell controller rather than third-party hardware, the causes lie elsewhere — start with PLC-5 not visible in RSLinx after processor replacement.
The red X: register the EDS with the right tool #
An entry showing a red X over an unrecognized device with a yellow question mark means the controller answered and RSLinx could not match the reply to a registered description. The fix is registration in the Device Description File Installation Tool, the Rockwell EDS utility — not a file-association option in the browse tree, because there is none. That is also why importing the EDS into the Schneider engineering tool achieved nothing: that import serves the Schneider software, not RSLinx. In the utility choose Add, then Register a single EDS file, or Register a directory of EDS files when loading a set, point it at the EDS for your exact M251 reference, finish, and refresh the browse. The unrecognized icon is then replaced by the device's proper identity.
The checklist, in order #
- Accept that addressing is proven: the subnet arithmetic closed it and the duplicate-address check is done.
- In the controller's Ethernet configuration, confirm the EtherNet/IP service is enabled on the port your cable occupies, then download when the machine allows.
- On the PC, disable every network adapter except the one on the controller's subnet, and confirm the adapter the EtherNet/IP driver uses.
- Browse with the EtherNet/IP driver; if empty, add an Ethernet Devices entry with the controller's exact address.
- Dead entry: no reply came back. Return to step 2, then check the path — a switch or firewall filtering discovery traffic passes ping and blocks the browse.
- Unrecognized entry: register the EDS for the exact reference, then refresh the browse.
- Device visible: configure the data connection and count it against the connection pool.
| What you see | What it proves | Do this |
|---|---|---|
| Ping works, every driver empty | IP path good, no EtherNet/IP reply | Enable the service on the connected port, fix the adapter |
| Ethernet Devices entry dead | Request out, nothing back | Controller service or a filtered path |
| Red X and yellow question mark | Reply back, device unrecognized | Register the M251 EDS, refresh the browse |
| Device visible, data needed | Browse solved | Configure the connection within the 16-connection pool |
When the requirement is every device visible #
If the client's acceptance test is "every component on the network appears in RSLinx", that test cannot be passed and should be renegotiated rather than chased. The browse lists EtherNet/IP responders; a device that speaks only Modbus TCP never appears in it, correctly. Offer the test that can be met: every EtherNet/IP device appears once its EDS is registered, and the remaining network is covered by a protocol-aware inventory. If the underlying need is Logix-to-M251 data, the M251 does not need to be browsable at all — the connection is configured between the controllers directly, constrained only by the M251's connection pool.
Questions asked
Does the Modicon M251 support EtherNet/IP, or only Modbus TCP?
It supports both. The M251 programming guide documents an EtherNet/IP service configured per Ethernet port, and caps the combined count: with at least one EtherNet/IP target configured, EtherNet/IP plus Modbus TCP connections together are limited to 16. The browse problem is almost never capability — it is the service not being enabled on the port you are connected to.
Where do I get the EDS file for the M251, and where do I register it?
From the manufacturer's support site, for the exact controller reference you have; the EDS is a plain text file describing that device. Downloading it is not enough — register it with the Device Description File Installation Tool (choose Add, then Register a single EDS file) and refresh the browse. Importing the same file into the Schneider engineering tool does nothing for RSLinx.
Does FactoryTalk Linx behave differently from RSLinx Classic here?
No difference where it matters: both tools show only devices that answer EtherNet/IP discovery, and both need the EDS registered before an unrecognized device renders correctly. The adapter, service and EDS checks in this article apply to either; only the configuration screens differ between the classic browse and the FactoryTalk application.
Does the M251 have to appear in RSLinx before a Logix controller can exchange data with it?
No. Browse visibility is identification, not a prerequisite for data exchange. Configure the EtherNet/IP connection on the M251 side and in the Logix project, and count it against the M251's 16-connection limit. Visibility then becomes a convenience while commissioning, not a gate the data path has to pass.