Supported CIP objects
Identity Object
Class code : 0x01
There is one instance(=1) of this object in EK9500.
Class Attribute List
no class attributes implemented
Instance Attribute List
Attr ID | Access Rule | Name | (Struct.) | Data Type | Description |
|---|---|---|---|---|---|
1 | Get | Vendor ID |
| UINT (16) | 106, the vendor ID of Beckhoff. |
2 | Get | Device Type |
| UINT (16) | 12, communication adapter |
3 | Get | Product Code |
| UINT (16) | 9500 |
4 | Get | Revision |
| (Struct.) | Product revision |
Major | USINT (8) | The structure member, major | |||
Minor | USINT (8) | The structure member, minor. | |||
5 | Get | Status |
| WORD (16) | Not used |
6 | Get | Serial Number |
| UDINT (32) | The serial number of each device |
7 | Get | Product Name |
| SHORT_ STRING | “EK9500” |
The Identity Object Instance supports the following CIP Common services:
Common Service List
Service Code | Implementation | Service Name | Description | |
|---|---|---|---|---|
Class | Instance | |||
0x01 |
| √ | Get_Attributes_All | Returns the contents of all attributes of the class |
0x0E |
| √ | Get_Attribute_Single | Used to read an object instance attribute. |
Assembly Object
Class code: 0x04
There are three instances of this object as the following.
| Instance Number | Size (byte) |
|---|---|---|
Input | 129 | depending the amount and type of attached input terminals |
Output | 130 | depending the amount and type of attached output terminals |
Class Attribute List
no class attributes implemented
Instance Attribute List
Attr ID | Access Rule | Name | (Struct.) | Data Type | Description |
|---|---|---|---|---|---|
3 | Get/Set | Data |
| Array of BYTE | The implicit messaging content |
4 | Get | Size |
| UINT (16) | Number of bytes in Attr. 3 |
Common Service List
Service Code | Implementation | Service Name | Description
| |
|---|---|---|---|---|
Class | Instance | |||
0x0E |
| √ | Get_Attribute_Single | Used to read input and output process data (attr 3) or read process data length (attr. 4) |
0x10 |
| √ | Set_Attribute_Single | Used to write output process data (only possible if no class1 connection opened to this assembly) |
Application: Parameterization of EtherCAT terminals
When EtherCAT terminals are parameterized via the CIP services, the settings are only saved in the terminal. When a restore file is created, these settings are overwritten with the restore file, which makes it necessary to update the restore file again.
The following CIP services have been implemented to update the restore file. One advantage of this procedure is that the process can also be carried out without the web interface. When a terminal is replaced, the restore file restores the configuration to the EtherCAT Terminal.
Procedure:
- Parameterize terminals via the CIP services
- Optional “Unlock Restore File
- Create Restore File
- Optional ”Lock Restore File"
From SW version 10 (V0.55):
- Create Restore File (during this, the EtherNet/IP™ communication stop, this is an indicate that is working)
Set Attribute Single
Class 0x300
Instance 0xFFFF
Attribute 0x101
Send 4 Byte Data, 00 00 00 00 - Delete Restore File
Set Attribute Single
Class 0x300
Instance 0xFFFF
Attribute 0x102
Send 4 Byte Data, 00 00 00 00 - Lock Restore File
Set Attribute Single
Class 0x300
Instance 0xFFFF
Attribute 0x103
Send 4 Byte Data, 01 00 00 00 - Unlock Restore File
Set Attribute Single
Class 0x300
Instance 0xFFFF
Attribute 0x103
Send 4 Byte Data, 00 00 00 00 - Read Status of Restore File
Get Attribute Single
Class 0x300
Instance 0xFFFF
Attribute 0x103
Rec 4 Byte Data, 00 00 00 00 unlock, 01 00 00 00 lock