How-to
Choosing a Data Path From an M580 PLC to FactoryTalk View
Short answer
RSLinx will show the M580 as an EtherNet/IP node once its EDS file is registered, but the tag browse stays empty because the controller presents no symbolic tag database over CIP. Pick the route from the tag structure: located %MW and %M data goes over Modbus TCP on port 502 or an EtherNet/IP assembly, and unlocated variables are only reachable through OFS serving OPC.
On this page
The link works, but not as a Logix-style tag browse. RSLinx will enumerate an M580 as an EtherNet/IP node once you register its EDS file, and the browse tree stops right there: the M580 presents no symbolic tag database over that path, so no tag list ever appears. That is expected behavior, not a fault. The data path you choose depends on one property of the data: whether the variables the HMI needs are located (%MW, %M) or unlocated. Located data goes out over Modbus TCP on port 502 or an exposed EtherNet/IP block; unlocated variables are reachable only through OFS serving OPC.
Decide the route from the tag structure #
The controller's tag structure, not preference, sets the route. Located variables hold fixed %MW and %M addresses; unlocated variables are symbolic names only, and how located and unlocated variables differ in Modicon memory is what determines everything downstream.
- List every item the screens need. Mark each one located (%MW, %M) or unlocated.
- If any required item is unlocated and you will not relocate it, use OFS and an OPC data source. That is the only route that resolves a name.
- If every item can hold a located address, use Modbus TCP direct to the CPU. RSLinx leaves the data path entirely.
- If the plant standard permits only RSLinx data sources, keep the EtherNet/IP link, map all HMI data into one exposed block, and address block offsets, never names.
Commit to the route before touching a driver or an EDS file: the three routes share no configuration.
Why the RSLinx tag browse stays empty #
RSLinx data sources resolve Logix symbolic tags, the same service that lets a FactoryTalk project browse a controller natively, as covered in connecting a CompactLogix controller to an HMI over EtherNet/IP. The M580 is a CIP device from another vendor: RSLinx enumerates it, and the EDS gives it the correct identity and icon. What the EDS cannot do is publish a symbol database, because the M580 does not present one over that path. Reinstalling the driver, registering more EDS revisions or swapping cables changes nothing once the device answers ping and shows with a catalog identity in RSWho. The fault is the expectation, not the link.
Modbus TCP on port 502 for located data #
- In the Control Expert project, give every HMI item a located address and keep them contiguous: words in %MW, bits in %M. Download the project.
- From the FactoryTalk View PC, ping the CPU, then confirm its Modbus TCP server answers on the registered service port 502.
- Create a Modbus TCP data source in the FactoryTalk View project aimed at the CPU address and that port.
- If the installed edition offers no Modbus TCP data source, the decision is made for you: put a Modbus-capable OPC server between them, OFS or another, and consume OPC.
If the panel itself is being chosen at the same time, selecting a Modbus TCP HMI panel for an existing controller makes this the native path from day one.
Worked example: one block, four registers #
An illustrative screen needs a setpoint (INT), a flow totalizer (REAL) and a pump-run bit:
- Setpoint INT at %MW100: one register.
- Totalizer REAL at %MW101: a 32-bit value spans two registers, %MW101 and %MW102.
- Run bit packed at %MW103, bit 0.
- Block span: 103 − 100 + 1 = 4 registers. Check: 1 + 2 + 1 = 4.
- Adding a second REAL later at %MW104 and %MW105 grows the block to 105 − 100 + 1 = 6 registers, still one request.
Keep every HMI item inside one contiguous block so a single register read serves the whole screen at each update, and pack bits into word bits so they ride in the same read instead of a separate bit table.
EtherNet/IP with a registered EDS file #
When the plant standard is RSLinx data sources, the link itself is sound; you address fixed data, not names.
- Download the EDS file for the exact CPU or Ethernet module revision, for example the BMENOC0301/0311 family covered in the M580 Ethernet documentation, from Schneider Electric's official source. That documentation requires the EDS revision to be the same as or later than the device's.
- Close FactoryTalk applications that use RSLinx, run the RSLinx EDS Hardware Installation Tool, and register the file.
- In RSLinx, open Communications > Configure Drivers, add an EtherNet/IP driver, and enter the M580 address in the station map.
- Open RSWho. The M580 must show with its catalog identity; a generic or question-mark icon means the EDS did not register or is the wrong revision.
- On the controller side, enable the EtherNet/IP service in the Control Expert Ethernet configuration and map the HMI data into the exposed block. The EDS is what tells a scanner which input and output messages the adapter offers.
- In FactoryTalk View, address the offsets of that block.
The EDS also has a second home: when the M580 is the scanner and a third-party device is the adapter, that adapter's EDS is added to the DTM library in the Schneider engineering tool, the documented procedure covering M580, Quantum, M340 and Premium.
OPC through OFS for unlocated variables #
Unlocated variables resolve by name in one place only: OFS, the OPC Factory Server, configured against the Control Expert project. The same route serves derived-block internals, as described for accessing unlocated DFB variables through OFS.
- Install and license OFS on a PC with network access to the M580.
- Create the device alias pointing at the CPU address.
- Point OFS at the project's exported symbol file so names resolve, and re-import after every change that adds or renames variables.
- In FactoryTalk View, add an OPC data source targeting that OFS server.
- Browse the namespace and bind by selection. Never retype item names by hand.
On this link the HMI is always the client; being certain of which side takes the OPC server and client roles avoids configuring the connection backwards.
Prove the path before binding screens #
- Ping the CPU from the host PC. If that fails, fix the address, subnet or VLAN before touching software.
- On the EtherNet/IP route, the M580 shows with its catalog identity in RSWho. On the OPC route, item quality reads Good in the OFS test client.
- Force a known value into a scratch %MW word and watch a numeric display follow it at the update rate.
- Write from the HMI to that same scratch word and confirm the value in a Control Expert animation table. Do this only on a word that drives nothing, before the machine runs.
- On any 32-bit value that reads plausible but wrong, check word order and data type first; a swapped REAL is the usual cause.
- Pull the network connection: the display must flag the failure and recover on reconnect without restarting the application.
What breaks and what it means #
- Device in RSWho but no tag browse: expected on a non-Logix controller; take one of the three routes above.
- Generic or question-mark icon: the EDS is not registered or is older than the device revision.
- Tags good, then bad after a project download: the located block moved, or OFS is serving a stale symbol export; re-import and re-check the block base.
- Intermittent loss: a duplicate address on the subnet, a switch port negotiation fault, or the RSLinx service stopped after a Windows update.
- Writes rejected: the variable is not writable through that route, or write access is restricted in the controller project.
Archive the EDS file, the OFS configuration and the exported symbols together, so the whole link can be rebuilt after a PC replacement without re-deriving any of it.
Questions asked
Why does the M580 appear in RSWho but no tags appear when I browse it?
Because RSLinx resolves symbolic tags for Logix controllers, and the M580 presents no tag database over CIP. The EDS file adds identity, the correct icon and the assembly data a scanner needs — no EDS revision or firmware update will add a Logix-style browse. Take one of the three routes instead: located data over Modbus TCP or an exposed block, unlocated data through OFS.
Can FactoryTalk View read unlocated M580 variables without OFS?
No. An unlocated variable has no fixed address, so neither a Modbus request nor a CIP message can name it. Either serve the names through OFS as OPC items, or open the Control Expert project and assign located %MW addresses, after which Modbus TCP or an EtherNet/IP block carries the data. Decide per variable, not per project.
Does the Modbus TCP route still need RSLinx running?
No. A Modbus TCP data source talks straight to the CPU server on port 502 and RSLinx is not in that path at all. If your FactoryTalk View edition offers no Modbus TCP data source, put a Modbus-capable OPC server such as OFS between the panel and the CPU and consume OPC instead; RSLinx still plays no part.
Where does the EDS file belong: RSLinx or Control Expert?
Both, for different roles. When the M580 is the target of a PC-side EtherNet/IP driver, register its EDS with the RSLinx EDS Hardware Installation Tool. When the M580 acts as the EtherNet/IP scanner to third-party adapters, each adapter EDS is added to the DTM library in the Schneider engineering tool, the documented procedure for M580, Quantum, M340 and Premium.
Tags were good, then went bad after a project download. What moved?
Most often the located block moved, or OFS is serving a stale symbol export. Check the block base address in a Control Expert animation table, re-import the exported symbols into OFS, and re-download the OFS configuration. Keep the EDS file, the OFS configuration and the symbol export together in the project archive so the link can be rebuilt after a PC replacement.