![ProSoft Technology PLX51-DF1-ENI User Manual Download Page 34](http://html.mh-extra.com/html/prosoft-technology/plx51-df1-eni/plx51-df1-eni_user-manual_1618990034.webp)
Setup
Page 34 of 87
3.5.2.
DF1
S
LAVE
M
ODE
The DF1 Slave routing mode allows mapping of virtual Data Files to Logix tags across multiple
controllers. This is similar to the Bridge mode except the mapping of data files to Logix tags,
is no longer managed in Logix, but in the PLX51-DF1-ENI itself.
Thus, the routing of the Node address to Logix controller as well as DF1 File Number to a Logix
tag is managed by the PLX51-DF1-ENI where in Bridge mode, the DF1 File Number was routed
to a tag by the Logix controller. In the DF1 Slave mode, the PLX51-DF1-ENI can operate
completely independently from the Logix controller by directly reading and writing to Logix
tags.
NOTE: The DF1 Slave mode only works with PLC5, SLC Typed Read and Write
messages as well as PLC2 Unprotected Read and Write messages.
Figure 3.28. - DF1 Slave mode configuration
The DF1 Slave mode is configured in two steps. First, you must create a Target Name (CIP path
to the destination Logix controller) which will be used to link the DF1 File Number to the
destination Logix tag. When using PLC2 messages, the Target will be linked to the DF1 Node
Number. Therefore, if the device sending out PLC2 requests wants to access multiple Target
Tags, it will need to differentiate by using different Node Numbers.
The Logix controller paths can either be entered manually or you can browse to them by
clicking the Browse button. The Target Browser will open and automatically scan for all
available EtherNet/IP devices.