OCD-EEC1B-1213-B12S-PCM EtherNet/IP DLR Address Boundary

EncoderWorks can configure OCD-EEC1B-1213-B12S-PCM as a custom compatible replacement solution for absolute multiturn EtherNet/IP feedback where IP address, CIP data behavior, DLR continuity, 25-bit position structure, and Ø12 mm blind-hollow fit must remain aligned with the installed PLC project. The failure boundary is not only the 10–30 VDC supply, but also Ethernet port mapping, device identity, configuration assembly, preset behavior, direction logic, power reference, and radial connector clearance. Typical production lead time: 15 working days.

This model is used where the control system reads absolute multiturn position over an EtherNet/IP network instead of discrete parallel wires, Profibus data, or incremental A/B/Z pulses. A compatible replacement must preserve the 13-bit singleturn and 12-bit multiturn position structure, Binary position handling inside the device, CIP communication behavior, DLR ring function, IP-address setting method, radial M12 connector layout, and Ø12 mm blind-hollow mechanical interface.

System Limits

The first system boundary is the EtherNet/IP network and PLC configuration. OCD-EEC1B-1213-B12S-PCM uses CIP communication with position, velocity, acceleration, and temperature-related device data, so the PLC project must see the same network identity, IP address behavior, process-data expectation, configuration assembly, preset function, counting direction, round-axis setting, and diagnostic response. If the replacement is installed with a wrong IP address, incompatible configuration file, different data length, mismatched preset behavior, or changed direction logic, the network may detect a device while the axis reports wrong position, wrong direction, missing status data, or unstable commissioning results.

The second boundary is DLR continuity and Ethernet physical wiring. The two D-coded Ethernet ports, Tx/Rx pairing, shield continuity, power connector reference, GND integrity, and ring topology must match the installed machine. A correct encoder can still fail if the DLR path is broken, the wrong Ethernet port role is assumed, shield continuity is poor, the power reference is unstable, or the radial connector stack is stressed by nearby guarding or cable routing.

Wiring & Installation

Before replacement, confirm the full installed model code, EtherNet/IP IP address requirement, device identity expectation, configuration file, CIP assembly layout, preset requirement, counting direction, round-axis use, velocity and diagnostic data use, DLR topology, Ethernet port mapping, and 10–30 VDC power wiring. Do not treat this as a Bit Parallel or Profibus replacement, because the controller is reading a configured Ethernet device rather than separate data bits or a fieldbus node with termination switches.

The blind-hollow shaft installation must also be checked carefully. The Ø12 mm hollow interface, clamp condition, shaft insertion depth, torque restraint, radial connector clearance, static and dynamic misalignment, and shield grounding can affect long-term stability. Poor clamping, shaft offset, cable strain, connector stress, or grounding discontinuity can cause mechanical drift, communication faults, intermittent diagnostics, or early bearing wear.

Custom Compatible Solution

• Match EtherNet/IP device behavior, 13-bit singleturn plus 12-bit multiturn feedback, CIP data expectations, and IP-address requirement
• Preserve DLR continuity, D-coded Ethernet Tx/Rx mapping, A-coded power wiring, GND reference, and shield continuity
• Adapt the Ø12 mm blind-hollow shaft, 58 mm B-flange class housing, radial connector layout, and mechanical mounting boundary
• Review configuration-file compatibility, preset direction, round-axis parameters, diagnostic data, connector clearance, and shaft misalignment before shipment

Key Data