Communication Units

Enicstra stocks communication units used to bridge industrial networks and convert between protocols: fieldbus-to-Ethernet gateways, protocol converters (Modbus to Profinet, Profibus to EtherCAT, AS-Interface to Profinet), serial-to-Ethernet device servers, IO-Link masters, and the standalone communication adapters that let isolated subsystems join a plant's main control network.

Brands carried include Anybus by HMS, Hilscher netTAP and netHOST, Beckhoff EK1000/EK9000 series, Allen-Bradley 1788-EN2DN and 1769-SDN, Siemens IE/PB Link, Phoenix Contact AXC F gateways, ProSoft Technology, Red Lion Crimson, and Moxa MGate. Obsolete communication units — discontinued Anybus first generations, retired ProSoft codes, end-of-life Hilscher netTAP variants — are sourced through our supplier network. Each unit is bench-tested for power-up and ships with a 12-month functional warranty.

For an obsolete gateway or communication unit, send the OEM part number for a quote within 1–2 business days.

Facets Filter

Communication Units

Keyence NU-CL1 Communication Unit CC-Link Compatible

MFR #: NU-CL1

$416.50/ea ✓ Available

Compare + Product Group

Keyence NU-DN1 Communication Unit DeviceNet Compatible

MFR #: NU-DN1

$115.33/ea ✓ Available

Compare + Product Group

Keyence NU-EC1 Communication Unit EtherCAT Compatible

MFR #: NU-EC1

$1,000.69/ea ✓ Available

Compare + Product Group

Keyence NU-EN8N e-CON Input Unit

MFR #: NU-EN8N

$521.98/ea ✓ Available

Compare + Product Group

Keyence NU-EP1 Communication Unit EtherNet/IP Compatible

MFR #: NU-EP1

$248.50/ea ✓ Available

Compare + Product Group

Can't Find The Part You Need?

Send us the part number, manufacturer, quantity, and condition — we'll locate it.

Request a Quote

Buying guide

Choosing Communication Units components

Communication unit selection is mostly about identifying which two protocols need to talk and matching the gateway's supported protocol list to that combination. A unit that converts Modbus TCP to EtherNet/IP does not convert Modbus RTU to EtherNet/IP — the source-side protocol matters as much as the target.

Specs to confirm before ordering:

Source-side protocol and role (master/scanner vs. slave/adapter)
Target-side protocol and role
Number of devices supported on each side
Data throughput / cyclic update rate
Configuration method: web-based, PC software, DIP switch, or PLC-side configuration
Supply voltage: 24 VDC standard, some support 120/240 VAC
Mounting: DIN-rail, panel
Diagnostic features: link status LEDs, traffic counters, error logging, web diagnostics
Certifications for the installation jurisdiction
Tag mapping limit on configurable gateways

Common gotchas: an Anybus X-Gateway is configured offline with Anybus Configuration Manager and the configuration is loaded onto the device — without the configuration, the gateway passes no data. Hilscher netTAP and similar units require their firmware to match the protocol pair; the same hardware can be Profinet-Modbus or Profinet-EtherCAT depending on firmware. Modbus RTU on RS-485 needs the correct baud, parity, stop bits, and slave address matched on the gateway and the device — mismatched parity is a common cause of intermittent communication. Serial-to-Ethernet device servers (Moxa NPort, similar) provide either virtual COM port mode (for PC apps) or TCP raw socket mode (for PLC apps); modes are configured differently.

Typical applications: bringing a legacy Profibus or Modbus RTU plant into a new Profinet or EtherNet/IP control system, integrating IO-Link sensors with PLCs that lack IO-Link masters, bridging between two control systems that speak different protocols, and adding serial-device connectivity to Ethernet-based SCADA.

For obsolete communication units, send the OEM part number for a sourcing quote.

Related categories Frequently asked questions

Do you stock obsolete Anybus and Hilscher gateways?

Yes. Discontinued Anybus X-Gateway first generations, retired Hilscher netTAP and netHOST codes, end-of-life ProSoft Modbus-EtherNet/IP, and earlier Moxa MGate are sourced through our supplier network.

Will my saved gateway configuration transfer?

If the model and firmware match, yes — configuration files load from the OEM software (Anybus Configuration Manager, Hilscher SYCON.net). Across firmware revisions, the configuration usually needs to be re-imported or re-validated.

Master/scanner vs. slave/adapter — what's the difference?

Master/scanner initiates communication and polls slave devices. Slave/adapter responds to requests. A Profinet IO controller is a master; a Profinet IO device is a slave. Specify the gateway's role for each protocol side.

Can a gateway translate any-to-any?

No. Each gateway model supports a specific protocol pair (e.g., Profinet IO Device + Modbus TCP Master). Some flexible platforms (Anybus X-Gateway) cover many pairs across product variants but each unit is one pair.

What is the typical configuration time?

For simple data mapping (a few dozen tags), a half hour with the OEM software. For complex multi-device mapping, several hours. Without the original configuration file, allocate longer — re-engineering tag maps from network captures is time-consuming.

What is the warranty?

12-month functional warranty on the device. Application performance with customer-specific configurations is not warranted as part of the device.