50
Data Type
Each data word is fixed to 16-Bit Unsigned. This is equivalent to two bytes.
Table 19: EtherNet/IP User-Configurable I/O Data Format
Consumed Data
(PLC to Inverter)
Produced Data
(Inverter to PLC)
Word Offset
Parameter
Word Offset
Parameter
0
Any
0
Any
1
Any
1
Any
:
Any
:
Any
30
Any
30
Any
31
Any
31
Any
The default I/O configuration is described in Table 20.
Always use the studio to confirm the configuration before commissioning the device
Table 20: EtherNet/IP Default User-Configurable I/O Data Format
Consumed Data
(PLC to Inverter)
Produced Data
(Inverter to PLC)
Word Offset
Parameter
Word Offset
Parameter
0
00.02
0
01.04
1
00.04
1
01.01
:
None
:
None
30
None
30
None
31
None
31
None
9.2.5 Generic Class 1 (I/O) Connection Access
Clients may access the class 1 endpoint by opening a connection to assembly instances 100 and 150.
The structure of I/O consumed and produced data for this assembly instance pair is entirely user-
configurable (refer to section 9.2.4). The generic class 1 I/O connection is mutually exclusive of the
AC/DC drive profile class 1 I/O connection. For a generic class 1 I/O application example, refer to
sections 9.2.11.1 and 9.2.12.1.
9.2.6 AC/DC Drive Profile Class 1 (I/O) Connection Access
The interface card supports the ODVA AC/DC drive profile. No special EtherNet/IP configuration of the
interface card is required when using the AC/DC drive profile: all that is needed is that the controller
must target either assembly instances 20 & 70 or 21 & 71 in its connection parameters. The structure of
I/O consumed and produced data for the AC/DC drive profile class 1 I/O is predefined and fixed (refer to
Table 22 and Table 23) to 4 input bytes and 4 output bytes. It is highly recommended to complete the
reading of this section to understand the data mapping and the implications of using the AC/DC drive
profile. Note that when using the AC/DC drive profile class 1 I/O, the produced word and consumed
word configuration do not apply (refer to section 9.2.3). For an AC/DC drive profile class 1 I/O
application example, refer to sections 9.2.11.2 and 9.2.12.2.
The AC/DC drive profile implementation
provides support for several required CIP
objects, which are specified in Table 21. While
the various supported attributes of all of these
objects are accessible via explicit messaging,
the main intent of using the AC/DC drive profile
is to interact with the predefined input and
output assembly instances via an I/O
connection. The structure of these assembly
instances is defined by the EtherNet/IP
specification in order to engender
Table 21: AC/DC Drive Profile-Related Objects
Class Code
Object Name
0x04
Assembly Object
0x28
Motor Data Object
0x29
Control Supervisor Object
0x2A
AC Drive Object