FAQ's about EtherNet/IP Made Easy

Are there any steps I need to take to before using EtherNet/IP Made Easy?

EtherNet/IP Made Easy is a simple executable and does not need to be installed. However, it is typically recommended that you upgrade all managed switches to the latest version of released firmware. The EtherNet/IP Made Easy will show you what version of FW is currently loaded in each of your switches, and you will find the latest versions of firmware to download below:

Lean Managed Switch (LMS)
Managed Compact Switch (MCS)
Modular Managed Switch (MMS)
SMART Managed Compact Switch (SMCS)
New firmware can be loaded into the switches using Factory Manager (or any) TFTP server.

Can I use EtherNet/IP Made Easy to configure non-Phoenix Contact devices?

The BootP server functionality to assign IP addresses can be used with non-Phoenix Contact devices. Uncheck the 'Show Only Phoenix Contact Devices' and you will be able to see, select and assign IP addresses to non-Phoenix Contact products. Managed switch configuration and EtherNet/IP bus coupler configuration screens use private MIBs and functionalities that other products do not support. Therefore, these configuration options can only be used on Phoenix Contact devices.

Can I configure multiple devices at the same time?

Managed switch configuration can be performed on multiple devices at the same time. Simply highlight all the switches to which you wish to apply a desired configuration change. EtherNet/IP bus coupler configuration can only be performed on one bus coupler at a time.

How can I perform a configuration task that is not available in EtherNet/IP Made Easy?

EtherNet/IP Made Easy is designed to function as a central wizard that interacts with your switches and I/O to ease configuration in most applications. However, remember that there is significant additional configurability, monitoring and diagnostic functions available in Phoenix Contact managed switches and I/O beyond what EtherNet/IP Made Easy provides. All Phoenix Contact Ethernet devices have embedded webservers which can be accessed with a simple web browser. To launch a webpage to any device and easily access these additional switch and I/O functions, simply highlight the device and right click.

How and why would I use the optional include/exclude address feature?

EtherNet/IP Made Easy uses SNMP and EIP broadcast messages to discover managed switches and I/O on your network. If you have devices on your network that you know will not respond to these broadcasts, you can specifically enter the IP addresses of these devices by using the include function. Conversely, if you have devices on your network that you do not want the tool to interact with, you can exclude specific IP addresses as well.

Beyond the default settings of the EtherNet/IP Made Easy, is there any additional device information that can be accessed or displayed?

Yes. For simplicity's sake, there is some additional information available about switches and I/O that is hidden by default. This information can be displayed by expanding these additional column headings in the Set IP Addresses and Managed Switch Configuration watch window. The additional information is as follows:

Set IP Address Page:
ObjectID is available to the right of Device Description

Managed Switch Configuration:
MAC Address is available to the left of IP Address
Currently applied method of IP Addressing is available to the right of IP Address
Large Tree Support setting status is available to the right of RSTP

What is Rapid Spanning Tree Protocol?

Rapid Spanning Tree Protocol (RSTP) is a standardized method (IEEE 802.802.1w/IEEE 802.1d) that enables the use of Ethernet networks with redundant data paths. Startup of RSTP functionality consists of two parts that must be executed in a specified order:

Enable RSTP on all switches that are to be operated as active RSTP components in the network.
Connect the switches to form a meshed topology.

Note: Only create the meshed topology after activating RSTP. For more information on RSTP please refer to the product manual for the switch being used in your application.

What is RSTP Fast Ring Detection?

RSTP Fast Ring Detection speeds up the switch-over to a redundant path in the event of an error and provides easy diagnostics. RSTP Fast Ring Detection provides each ring with an ID, this ID is made known to each switch in the relevant ring. A switch can belong to several different rings at the same time. When using RSTP Fast Ring Detection, please note the following:

For RSTP Fast Ring Detection, do not use devices that do not support this function.
Enable RSTP Fast Ring Detection on all devices.
All data paths must be in full duplex mode.

Notes:

EtherNet/IP Made Easy can monitor the status of the RSTP Fast Ring setting on Lean Managed Switches (if running firmware versions that support it) but it cannot change this setting. To activate RSTP Fast Ring on a Lean Managed Switch running firmware that supports it, you must go to the webpage of the device and activate this setting there.
For more information on RSTP Fast Ring Detection, please refer to the product manual for the switch being used in your application.

What is RSTP Large Tree Support?

If RSTP is operated using the default values, it is suitable for up to seven switches along the relevant path. The RSTP protocol would therefore be possible in a ring topology for up to 15 switches. The Large Tree Support option makes the ring topology suitable for 28 switches along the relevant path if RSTP is used. The Large Tree Support option could provide an RSTP ring topology with up to 57 devices. When using Large Tree Support, please note the following:

In the RSTP Large Tree Support topology, do not use devices that do not support Large Tree Support.
Enable the Large Tree Support option on all devices.
If RSTP is to be activated as the redundancy mechanism in an existing network with more than seven switches along the relevant path, then the Large Tree Support option must first be enabled on all devices.
It is recommended that Large Tree Support is not activated in networks with less than seven switches along the relevant path.

Notes:

On the Managed Switch Configuration page, it is also possible to monitor whether Large Tree Support is activated for each switch. A column displaying status of The Large Tree Support setting is minimized by default and can be expanded between the RSTP and Fast Ring column headings.
EtherNet/IP Made Easy can monitor the status of the Large Tree Support setting on Lean Managed Switches (if running firmware versions that support it), but it cannot change this setting. To activate RSTP Large Tree Support on a Lean Managed Switch, you must go to the webpage of the device and activate the setting there.
For more information on RSTP Large Tree Support, please refer to the product manual for the switch being used in your application.

What is the write community field?

This field holds the password that EtherNet/IP Made Easy will use when it sends SNMP 'sets' to a switch to configure it per the settings you have selected. You cannot leave this field blank when you send a desired new configuration to a switch. If the correct password for a switch is not in this field, the tool cannot change the switch settings. If a selected switch is sent a configuration but the switch does not have the same password as what is in the write community field, the tool cannot change the switch's configuration. Thus, to use the tool simultaneously for a group of switches, they must all have the same password and that password must be entered into the write community field of EtherNet/IP Made Easy.

What's the difference in 'Send Configuration' vs. 'Send & Save Configuration'?

'Send Configuration' changes a switch's settings to the configuration that you have selected in the checkboxes. However, if you then cycle power on the switch, the switch will revert back to the last previously saved configuration, since your new configuration has not been saved. 'Send & Save Configuration' sends your desired configuration to the switch and also sends a command to the switch to save the new configuration settings.

What is Dynamic Topology Multicast Tolerance (DTMT)?

Networks with atypical topology or frequent RSTP/Fast Ring Detection changes that could potentially cause intermittent RPI timeouts may see improved system performance by enabling DTMT (Dynamic Topology Multicast Tolerance). DTMT configures IGMP Querier Blocking, Forwarding and Snoop Aging to settings that maximize network resiliency.

More questions about using Phoenix Contact Products in EtherNet/IP networks?

Use our Knowledge Base

How do I enter Phoenix Contact EtherNet/IP bus couplers into RS Logix 5000?

When adding a new module in RS Logix 5000, you will need to select the device type 'ETHERNET-MODULE Generic Ethernet Module' under the 'Communications' folder. The rest of the information needed can be pulled from the IO Data Map window in the EtherNet/IP Made Easy.

If you are using any I/O modules that use PCP communications, you may also benefit from downloading and using pre-defined Add-On Instructions for these modules. These Add-On Instructions are for use within RS LogixTM 5000 (version 16 and up). Download the appropriate file or contact Technical Support (if required). Then use the import feature in RS Logix, select the file, insert the function block into your existing PLC code and set the parameters required for your application for a simple integration into your RS Logix software! Both relay ladder logic and structured text programming languages are supported and the files include help documentation. If a third party function block does not yet exist for the application you are designing, please send us a request to create it.

What are the different Plug & Play modes?

Plug & Play Mode: Disabled
When Plug & Play mode is disabled or deactivated, the reference configuration is compared to the physical configuration. If they are the same, the bus coupler is set to the 'RUN' state. If the reference configuration and the physical configuration differ, the MS (Module Status) LED lights up and process data exchange is no longer possible for safety reasons.

Plug & Play Mode: 'Inputs Only' Active
This mode enables Inline terminals connected in the field to be started up using the bus coupler without a higher-level configuration. The Plug & Play mode status (Inputs Only, Inputs & Outputs, and Disabled) is stored retentively on the bus coupler. The current mode is accessible via the WBM interface or the CIP interface. In Plug & Play mode, the connected Inline terminals are detected and their ability to operate is verified. If this physical configuration is ready to operate, it is started, however writing outputs is not enabled. To enable writing outputs, Plug & Play mode must be either deactivated or set to 'Inputs & Outputs'. The deactivation of Plug & Play mode is also the signal to save the active configuration as the reference configuration.

Plug & Play Mode: 'Inputs & Outputs' Active
This mode allows the writing of outputs. Care should be taken when setting a device to this mode. A mismatched I/O system configuration which is connected to end devices such as drive controls or motion controls can cause unwanted actions when outputs are turned on! Users must ensure in this Plug & Play mode that any connected end device will safely function if outputs are enabled.

Why should I disable BootP on my EtherNet/IP bus coupler?

Upon delivery, the IL EIP BK DI8 DO4 2TX-PAC bus coupler has no valid IP parameters. During initial startup, the device sends BootP requests without interruption until it receives a valid IP address. The requests are transmitted at varying intervals (2 s, 4 s, 8 s, 2 s, 4 s, etc.) so that the network is not loaded unnecessarily. If valid IP parameters are received, the device will use these parameters until the device is reset or power is cycled. Once a valid IP configuration is saved to the device, BootP should be disabled so the device will start with the stored IP configuration and will not send BootP requests.

How do I set the bus coupler back to factory default?

Resetting the device to the default settings reactivates BootP and deletes the IP parameters stored. The procedures to set each EtherNet/IP bus couplers back to factory default are as follows:

IL EIP BK DI8 DO4 2TXPAC

Switch off the power supply to the bus coupler
Press and hold the reset button located above the Ethernet ports.
Reapply the power supply
Release the reset button after 10 Seconds.

FLM BK EIP M12 DI 8 M12-2TX

First, switch off the power supply to the bus coupler and then remove any bridges for setting the baud rate.
Connect pin 5 using an external button to pin 1.
Keep the button pressed.
Then turn on the power supply.
Release the button when the 2 MBD LED flashes.

What does it mean to 'Pad I/O'?

Depending on the I/O configuration, the analog or special function data may start on an odd byte. If this is the case, it is possible that this word could span two words in the master scanner. By setting the parameter 'Pad I/O', one byte will be added to the produced/consumed size, thereby forcing the first word based module to start on an even byte. If this word already starts on an even byte and the user sets parameter does not select this option, no additional bytes will be added to the produced/consumed size.

How does the 'Add All I/O' function work?

'Add All I/O' tells the bus coupler to read device information from the current connected local bus. This information is then stored into the bus coupler non volatile memory. The next time the bus coupler is reset it expects that the configuration has not changed. If changes have been made, the local bus will go into an error state and indicate the error location in the Diagnostic word.

Why would I use the 'Accept New Configuration' button?

The 'Accept New Configuration' is used in situations when modules have been removed from the local bus but you do not want this configuration chance stored in the bus couplers non volatile memory. This will tell the bus coupler to store configuration from the last successful operation of the 'Add All I/O' function.

Why would I need to launch the bus couplers web page and manually activate Plug & Play mode?

When using IB IL RS232 modules, EtherNet/IP Made Easy can sometimes experience difficulty in determining the proper configuration for this module. In this instance, use the 'Launch Web Page to Activate Plug and Play' button to open the webpage to the bus coupler (the button will open directly to the services page). Then use the web-based management to place the bus coupler into Plug & Play mode and then cycle power to the bus coupler. This action allows this module to be properly read. After a reboot, you will need to use the 'Accept New Configuration' button to store this configuration.

What is 'Inline Status' data?

By default, 'Inline Status' word data is made available to the user as two bytes of diagnostic data in the produced data. These two bytes contain the Inline fault code (byte 0) and the number of the first module in the local bus that is faulted (byte 1). The status word adds 2 bytes to the produced data size by default. The status word updates status automatically so when an error is cleared the status will be set back to a 0.

Status Word (Byte 0)
Bit 0 CRC Error The CRC error bit will be set when a data transmission error occurs due to unwanted interference on the Inline local bus. If the transmission does not pass the CRC (Cyclic Redundancy Check) after the "Max Retry" has expired then the CRC error bit is set.
Bit 1 Peripheral Fault The Peripheral Fault bit will be set when any output is shorted or a loss of power to an intelligent segment module.
Bit 2 Power Fault The Power Fault bit will be set when any of the power supplies (UL, US, UM, EtherNet/IP) is in an under voltage condition (less than 11 V DC).
Bit 3 Module Change The Module Change bit will be set when the configuration present on the Inline local bus does not match the configuration that was stored in flash during the last configuration cycle.
Bit 4 Configuring Error The Configuring Error bit will be set when the bus coupler is not able to talk to the first I/O module connected to it. Possible failures include the bus coupler itself or the first I/O module connected to it.
Bit 5 Module Connection Error
The Module Connection Error bit will be set when the bus coupler is no longer able to talk to the modules connected to it and can determine the failure position. This failure occurs due to a broken data path.
Bit 6 Outputs Set to Preprogram EtherNet/IP Fault State
This bit can only be set in the Fault Response mode 2. It is made available to let the application know that the local outputs have gone to their preprogrammed EtherNet/IP fault state and will no longer respond to the controller.
Bit 7 Reserved for future use.

Status Word (Byte 1)
Contains the device number determines the position on the Inline station where a failure or warning has occurred. These positions are numbered starting at the bus coupler being assigned with a 1. The numbering will continue to the right up to 64, which is the maximum number of devices that can be connected to an Inline station [63 I/O devices (including two devices on the bus coupler) + 1 bus coupler].

How is I/O mapped?

The physical order of data in the I/O table is determined by the position of the modules on the local bus. The first module connected to the Inline Ethernet/IP bus coupler will reside in the first I/O byte (keeping in mind the "which data type comes first" rule). Furthermore, the LSB of the first module will be assigned to the first instance. The next module of the same type and image will line up next to the first module without leaving any "gaps" in the I/O table.

Consumed Data
DOPs - Digital output points
Padding - Padding is used to fill the DOP section so it ends at an even byte
AOPs - Analog output words
AIP Control Data - Analog input Configuration data
Special Function Data - Output data for special function modules

Produced Data
Inline Status Byte
Inline First Faulted Module
DIPs - Digital input points
Padding - Padding is used to fill the DIP section so it ends at an even byte
AIPs - Analog input Words

Special Function Data - Input data for special function modules

What options are available to configure analog input modules?

There are three methods to configure analog input modules. This configuration is done through an output word.

Option 1
This configuration word can be added to the consumed data area. This allows the configuration to be modified on the fly by the control system

Option 2
Use the Configure I/O option of EtherNet/IP Made Easy. On the Configure I/O page, highlight the module in the 'Module List', and select the correct 'Module Type'. You may then choose, for each channel of the module, the desired 'Configuration Option' from the drop down menus: Range, manual configuration (by bit), or to place the configuration in the poll. This information is then stored in non-volatile memory of the EIP bus coupler. The following ranges are available: -10 to +10 V, 0 to +10 V, +4 to +20 mA, 0 to +20 mA, -20 mA to +20 mA.

Option 3
The configuration word can also be manually entered using EtherNet/IP Made Easy. With this option you will need to reference the module's data sheets to determine what bits need to be set to configure the modules for its desired function. This information is then stored in non-volatile memory of the bus coupler.