---
title: "EtherNet/IP-Overview and Capability"
id: "ethernet-ip"
project: "Clean Power VFD User Guide"
url: "https://smartd.clickhelp.co/articles/clean-power-vfd-publication/ethernet-ip"
updated: 2026-10-29T18:46:31Z
---

# EtherNet/IP\-Overview and Capability

[Home](/articles/clean-power-vfd-publication/home) » [Networks and communication](/articles/clean-power-vfd-publication/networks-and-communication) » EtherNet/IP-Overview and Capability

* * *
 
![](/resources/Storage/clean-power-vfd-publication/res/Safety%20picture%20Blue%20Notice.png)
 
The EtherNet/IP documentation is based on the SmartD implemented **revision 1.0.12 on 2026 May 5th**.
 
* * *

## What You Can Do with EtherNet/IP (and When to Use It)
 
## EtherNet/IP provides two complementary ways to interact with the Clean Power VFD:
 
1. **Cyclic I/O (Class 1)** – for real-time control and monitoring. Use cyclic I/O when you need deterministic exchange between a PLC/Scanner and the drive, such as:

* Start/stop, forward/reverse, fault reset, and interlocks using a **Control Word / Status Word**
* Send a **speed reference** (and, where supported by firmware/profile, a torque reference)
* Read back **actual values** (speed, current, power) and drive status

1. **Explicit messaging (Class 3)** – for on-demand reads/writes (commissioning & diagnostics). Use explicit messaging when you need parameter access, change management, or one-time reads such as:

* Reading device identity and network configuration
* Reading drive monitoring attributes (current, power, torque, mode)
* Reading (and, where supported) writing configuration attributes

**Important:** The Clean Power VFD supports the following CIP explicit services::

* **Get\_Attributes\_All (0x01)** - returns the full set of supported attributes for objects where this service is implemented.
* **Get\_Attribute\_Single (0x0E)** - reads one specific attribute.
* **Set\_Attribute\_Single (0x10)** - writes one specific attribute, where write access is supported by the object and firmware.

![](/resources/Storage/clean-power-vfd-publication/info.png) The service **Get\_Attributes\_All (0x01)** is supported on

* Motor Data Object,
* Control Supervisor Object,
* AC/DC Drive Object,
* Identity Object,
* ethernet\_link Object, and
* TCP/IP Object.

For other objects, or when a client tool receives an Attribute Not Supported or Online Read Rejected response, use Get\_Attribute\_Single instead.

## Supported CIP objects (summary)

The Clean Power VFD implements the ODVA **CIP AC/DC Drive profile** plus standard EtherNet/IP network objects. The main objects used by an automation engineer are:

* **Identity Object (0x01)** – device identification
* **Message Router (0x02)** – CIP routing *(Limitation: Not yet supported)*
* **Assembly Object (0x04)** – cyclic I/O assemblies (Class 1)
* **Motor Data Object (0x28 / 40 dec)** – motor nameplate data (read/write depends on firmware support) (*Limitation: only read)*
* **Control Supervisor Object (0x29 / 41 dec)** – run/stop, direction, state, reset, and fault/warning status.
* **AC/DC Drive Object (0x2A / 42 dec)** – speed reference, actual speed, current, power, drive mode, ramps, and scaling.
* **TCP/IP Interface Object (0xF5 / 245 dec)** – IP addressing and TCP/IP settings
* **Ethernet Link Object (0xF6 / 246 dec)** – Ethernet link speed, link flags, and MAC address.

## Cyclic I/O assemblies (Class 1)
 
The drive supports multiple I/O assembly pairs. Conceptually:

* **Output Assembly (O→T)**: PLC → Drive (what the drive consumes)
* **Input Assembly (T→O)**: Drive → PLC (what the drive produces)

Supported assembly instance numbers include (availability depends on firmware “phase”):

* **Basic Speed Control**: Output **20**, Input **70**
* **Extended Speed Control**: Output **21**, Input **71**
* **Extended Speed + Torque Control**: Output **23**, Input **73***(phase dependent) (Limitation: not yet supported)*
* **Extended Process Control**: Output **25**, Input **75***(phase dependent) (Limitation: not yet supported)*
* **SmartD (vendor) variants**: Outputs **120/121/123/125**, Inputs **170/171/173/175***(phase dependent) (Limitation: 123/125 and 173/175 not yet supported)*

The SmartD variants add extra cyclic data beyond the standard ODVA words (example: output frequency, motor current, power, alarm words, and configurable words), depending on the selected assembly.
 
## Producer–Consumer model and Listen-Only connections
 
The Clean Power VFD acts as an **Adapter**:

* It **consumes** the PLC’s Output Assembly (O→T) and
* **produces** the Input Assembly (T→O)

The **PLC/Scanner owns the connection** and typically sends O→T as **unicast**.
 
Additional devices (HMI, historian, gateway) may establish **Listen-Only** connections to the drive’s produced Input data when the scanner is configured for multicast production. 
Listen-only devices do **not** control the drive; they “listen” to the same produced data stream.
 
## Network ports and physical interfaces
 
The product provides **two RJ-45 Ethernet ports** with auto-negotiated speed/duplex. There are **no physical port LEDs** on the product.
 
## Electronic Data Sheet (EDS)
 
**EDS file** are provided for PLC integration and device discovery.
 Download location: **SmartD services website** – [Network parameter data files](https://services.smartd.co/network-parameter-data-files/)*https://services.smartd.co/network-parameter-data-files/*