Beruflich Dokumente
Kultur Dokumente
• The following Ethernet Network consists of a PC, Generic Device, DF1 Device
• The Generic device can be an Ethernet device (such as: PLC5E, SLC 5/05, 1756-
ENET) or another DF1 device
• The purpose of this document is to show the simplicity in working with the ENI
Utility
• This screen shows the IP Address Configuration for the examples shown above.
STEP #3: (Configuring the destination nodes in the Routing Table)
• At this point valid IP Addresses need to be entered to route DF1 messages from
the attached controller to destination Ethernet device(s).
• For the example above the only device that can be messaged to is the GENERIC
DEVICE at IP Address 100.100.100.6.
• Therefore, this IP Address is configured in the Routing Table
IMPORTANT CONSIDERATION:
• The ENI IP Addr. Tab has a RS232 baud rate.
• This is the baud rate of the DF1 device being connected to it.
• If the selection for RS232 baud rate = AUTO, then on power up if the DF1 device
is connected to the ENI, the ENI will sync the devices baud rate to the ENI.
Example #1:
• SLC 5/04 (channel 0) = baud rate of 19,200.
• On power up the ENI syncs this baud rate and establishes a connection via the
ENI to the SLC 5/04
• This is able to be done because the RS232 baud rate on the ENI is set to AUTO
Example #2:
• If the cable from the SLC 5/04 (channel 0) is now moved to SLC 5/03 (channel 0)
= baud rate of 9600
• The ENI will not recognize the SLC 5/03 until a power cycle is made to the ENI
• The ENI has synced up previously to a baud rate of 19,200 unless a power cycle
is made to AUTO DETECT a new baud rate of 9600
Example #3:
• If the cable from the SLC 5/04 (channel 0) was moved to a Micro 1500 (channel
0) = baud rate of 19,200
• The ENI will recognize the Micro 1500 because it already synced its baud rate to
19200 on the RS232 port
• Therefore, any device having a baud rate can connect to the ENI without a power
cycle/