After configuring the Productivity 2000 EtherNet/IP scanner and matching the manifold’s I/O assembly settings, connect the controller’s external Ethernet port through a switch to the manifold adapter. This path needs no additional rack module for the EtherNet/IP scanner connection described here. A switch provides network connectivity; the scanner configuration tells the controller which device and I/O data to exchange.
Confirm the manifold supports EtherNet/IP I/O
First check the exact manifold adapter’s nameplate and documentation. The example involves an SMC EX250 family manifold, but the specific adapter and its protocol determine whether the Productivity 2000 can exchange cyclic I/O with it. Confirm that the installed adapter supports EtherNet/IP and identify its required input and output assembly instances and data sizes.
A familiar valve bank or an Ethernet jack does not establish protocol compatibility. A device may use Ethernet for a different protocol or for setup and diagnostics only. If the adapter does not support EtherNet/IP I/O, the Productivity 2000 scanner cannot control it through the proposed scanner connection; select a compatible adapter or a supported gateway.
Do not add a rack module as a first response to an unknown protocol. For the EtherNet/IP path in this setup, configure the scanner in the Productivity 2000 hardware configuration and use its external Ethernet port. The described connection does not require a P2-RS module.
Check: Record the exact adapter model, protocol, IP address, assembly instances, and assembly sizes from its documentation before building the I/O connection.
Wire the controller and manifolds through the switch
Connect the controller’s external Ethernet port to an industrial Ethernet switch, then connect each manifold’s Ethernet adapter to that switch. A single switch can carry traffic for multiple devices, provided each device has a unique IP address and the controller and devices have compatible network settings. The switch forwards Ethernet traffic; it does not register manifolds with the PLC or create I/O connections for them.
Set the controller and manifold addresses according to the plant network plan. Check that the subnet settings allow the controller and each adapter to communicate. If the network uses VLANs, routing, or managed switch controls, confirm that those settings permit the required traffic between the scanner and adapters. Do not copy an address from the existing ControlLogix installation: duplicate IP addresses can make communication intermittent or direct traffic to the wrong device.
Keep the initial commissioning path simple. Connect one manifold first, then add other adapters after the first I/O connection works. This makes an address conflict, wiring fault, or incorrect adapter configuration easier to isolate.
Check: Verify each device has a unique planned address and that the controller and first manifold show link on the intended switch ports.
Configure the Productivity 2000 scanner
In the Productivity 2000 hardware configuration, set up the EtherNet/IP scanner and define a connection for the manifold adapter. Enter the adapter’s IP address and the connection data required by that adapter. The scanner uses this configuration to open and maintain the I/O connection; it does not discover valve addresses merely because they share a switch.
- Open the controller hardware configuration and enable or configure its EtherNet/IP scanner function.
- Add the manifold as an EtherNet/IP I/O device using the adapter’s IP address.
- Enter the input and output assembly instances and data lengths required by the exact adapter documentation.
- Set the connection interval and other connection options to values supported by both the adapter and the controller configuration.
- Apply the configuration and inspect the scanner’s connection status and diagnostics.
Do not guess assembly numbers, byte counts, or connection settings from a different manifold adapter. Even products in the same manifold family can have different adapter options. A scanner configuration that connects to the wrong assembly or requests the wrong data size may fail to establish I/O or may map data incorrectly.
Check: Confirm the scanner reports the configured device connection as active before using its output data to actuate valves.
Match the adapter’s assembly map to PLC data
EtherNet/IP cyclic I/O transfers assembly data between the scanner and adapter. The adapter manual defines which assembly instances carry input and output data and how those bytes or bits correspond to manifold status and valve outputs. Use that mapping to identify the controller data that represents each point; do not assume the PLC automatically creates meaningful valve names or tags from the IP address.
Compare the configured lengths with the adapter’s documented I/O map. Account for the adapter’s actual valve configuration and any available status data. If the requested size does not match the configured manifold, the connection may reject the I/O configuration or the PLC may interpret offsets incorrectly. A bit-level error can energize a different valve than intended, so establish the correspondence from the adapter map before enabling machine logic.
Use descriptive PLC tags or comments for the resulting I/O points and document the relationship between each tag and the adapter’s assembly offset. Keep the network address, assembly configuration, and point mapping together in the commissioning record so a later replacement can be configured consistently.
Check: Cross-check every configured assembly instance and data size against the exact adapter documentation, then trace each intended valve output to its documented data position.
Commission one manifold before expanding the network
With the scanner connection active and the data map checked, test one output at a time under the machine’s approved commissioning conditions. Observe the controller’s output data and the physical valve response. Then operate an input or status point, if the adapter provides one, and confirm that the corresponding controller data changes as documented.
- Keep the machine in a state where an unexpected valve movement cannot create a process hazard or damage equipment.
- Command one known output and confirm that the intended valve, rather than a neighboring point, responds.
- Remove the command and confirm the output returns to its intended state.
- Check available input or adapter status data against a known physical condition.
- Repeat the point-to-point check across the configured manifold outputs before connecting additional manifolds.
For a temporary production restore, use only a verified known-good adapter configuration and documented point map. Record any temporary address or mapping changes, then schedule the permanent repair to restore the approved network plan and commissioning records. Do not leave an unverified output offset or duplicate address as the production fix.
Check: The commanded valve and observed feedback must match the point map for every tested channel before the machine sequence depends on the remote I/O.
Isolate connection and mapping faults in order
| Symptom | First checks | Likely correction |
|---|---|---|
| Scanner cannot connect | Link indication, cable and switch port, device IP, subnet, duplicate address, adapter protocol | Correct physical or network settings and confirm the adapter supports EtherNet/IP I/O |
| Connection rejects I/O configuration | Assembly instances, input/output sizes, adapter configuration | Enter the values specified for the installed adapter and manifold arrangement |
| Connection is active but the wrong valve moves | Assembly offsets, bit order, point map, PLC output logic | Correct the mapping and retest outputs one at a time |
| Several manifolds behave inconsistently | Unique IP addresses, switch configuration, per-device scanner entries | Resolve address conflicts and validate each connection separately |
Adding a rack module will not repair an incorrect device address, unsupported protocol, or assembly mismatch. Likewise, adding a switch only provides the network path; it does not tell the scanner which devices or assemblies to use. Read the scanner diagnostics and the adapter status indicators together so you can separate link problems from I/O connection and mapping problems.
Check: After each correction, verify that the scanner connection is active and repeat the single-output test before returning the manifold to automatic control.
Frequently asked questions
Why does the Productivity 2000 need an EtherNet/IP scanner configuration?
The scanner initiates and manages the cyclic I/O connection to each manifold adapter. A switch connection alone does not define the device’s IP address, assembly instances, or I/O sizes.
Why does the PLC not recognize manifold addresses automatically?
The network switch forwards traffic, while the scanner configuration identifies the adapter and its I/O assemblies. Configure each device’s unique IP address and the assembly data required by its documentation.
When should I stop troubleshooting and call support?
Stop if the exact adapter protocol and assembly settings are confirmed but the scanner still cannot establish a connection, or if verified output mapping does not match physical valve operation. Provide AutomationDirect or SMC official support with the controller configuration, adapter model, network settings, scanner diagnostics, and test results.