Introduction

This Application note explanes, how to configure a generic modular adapter, when the entry for "ProxyConnect" is not described in the Ethernet/IP Slave Device Description (EDS).

Please refer to the following FAQ: "Why does my modular EDS file not work?" → https://kb.hilscher.com/pages/viewpage.action?pageId=18616112

As an example the Allen Bradley Point I/O Module Adapter "1734 AENT" is used, together with the fitting Point I/O Modules "1734 IB8" and "1734 OB8E".

Hardware configuration

The EDS File of each module is needed for further configuration of the Generic Modular Adapter.

These can be found on the Rockwell Automation Page:

https://www.rockwellautomation.com/de_DE/detail.page?pagetitle=Electronic-Data-Sheets&content_type=overview&docid=11432fc64a2a887b85011582be53806b

Software Configuration

Add Modules

In SYCON.net, add an EtherNet/IP Scanner (e.g. CIFX RE/EIM) and then add an ENIP Modular Generic Adapter to the network.

Open the Configuration Window of the Modular Generic Adapter and choose "Modules" in the Navigation Area.

Change “Slots in Rack” to 3 and add the modules:

Configure 1734-AENT

Configure 1734-IB8

Specify Connection

EtherNet/IP is a connection-oriented protocol, therefore the connection should always be specified first.

Open the EDS for 1734-IB8 and go to the section [Connection Manager], assuming that Connection23 (Input  only) will be used:

Configure connection settings

Please choose "Connection" in the Navigation Area of the Modular Generic Adapter. Select  the Module “Slot<1> 1734-IB8”.

Decode the field "trigger & transport" and "realtime format", which are defined in Connection23.

These parameters describe the connection variables, which have to be filled in the Connection configuration Window in Sycon.net.

The free Tool "EZ-EDS" from ODVA (https://www.odva.org/software/EZ-EDS-Download), can be used to make decoding of the parameters easier.

Therefore, open the EDS by selecting "File → Open…”.  Select "Generic EDS" as EDS type and ignore the upcoming error messages.

When the file is successfully opened, select “Connection1” in the left tree view.

The name “Connection23” in EDS file is automatically converted to “Connection1”.

The following dialog window:

Based on these informations, now configure the Connection Area in Sycon.net:

Don't forget, to set the Connection name to "Connection23".

Configure assembly instance ID

Choose "Assembly" in the Navigation Area of the Modular Generic Adapter now. Select  the Module “Slot<1> 1734-IB8”.

Now the Connection Path has to be filled in. The Connection Path is described in the EDS here:

Switch back to EZ-EDS, select “Connection1”  in the left tree view.

Click the Button "Decode Path". A new Window will pop up. Select decimal format in this dialog now the instance ID can be read out for Configuration in Sycon.net.

Based on the above information, the assembly Instance ID can be specified.

The instance "20 04 24 67 2C BE 2C 04" can also be decoded manually as follows:

Configure Input assembly length

The input assembly length is defined in the field “T->O size” and field  “T->O format” of Connection 23:

It can be decoded as follows:

T → O 

, , Assem127

When the "Size" of the T=>O default description is empty, the format has to be evaluated.

In this case, Assem127 is used to define the format. Go to the definition of Assem127, in the EDS:

Since the field for the length is empty ($ Length in bytes), the Membe fields fields should be evaluated:

The Assemblys Member can be decoded as follows:

,,

32,,

,Assem4;

This means, the first Member is reserved, the second one has a size of 4Byte (32Bit) and the third one references to Assem4.

Go to Assem4:

The "total length in bytes" is defined as "1".

Now the total size of Assem127 can be defined:

Configure Output assembly length

The output assembly length is defined in the field “O->T size” and field  “O->T format” of Connection 23:

It can be decoded as follows:

O → T

,0,,

Since the field “O->T size” is not empty, it can directly be read – 0 Byte.

In this case no further evaluation is needed.

In case this field is refered to a Parameter or Assembly, please use the steps memtioned in the example above: "Configure Input assembly length".

Configure configuration assembly length

The configuration assembly length is automatically calculated by the data length of cfg. #1 and cfg. #2 data segment. 

The user is not allowed to directly edit this length.

Configure cfg. #1 data segment

The cfg #1 data segment is defined field "$ config part 1" of Connection23:

Here Assem124 is used to define the format. Go to the definition of Assem124:

In this case, both Values ("Member Size" and "Member Reference" have to be evaluated.

The Assemblys Member informations can be read as follows:

The field of the first Member indicated, that it has a data length of 16 bit. It also has a Reference to Param101.

Go to the definition of Param101:

The "data size in Byte" has a size of 2 Byte, with a default value of 1.

So the default data of Param101 is 0x0001.

The user can also define a value between min. value and max. value.

Go back the definition of Assem124, the Second Member has a length of 16 and has no Reference entry. This means, all data are defined with value 0.

Configure cfg. #2 data segment

The cfg #1 data segment is defined field "$ config part 2" of Connection23:

Here Assem103 is used to define the format. Go to the definition of Assem103:

This Assembly has a few more Members.

Please repeate the procedure mentioned in the first data segment for each Member.

For example the first Member:

The Size of this Member is definded with 16Bit and has a Reference to Param9:

The Size is defined witzh 2 Bytes, the Default Value is 1000 (Hex 03E8):

When analyzing all Members ans Parameters, the following table can be created:

Therefore the cfg #2 data segment results in:

E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803

Final assembly configuration of 1734-IB8

Configure 1734-OB8E

EtherNet/IP is a connection-oriented protocol, therefore the connection should always be specified first.

Open the EDS for 1734-OB8E and go to the section [Connection Manager], assuming that Connection9 (Exclusive Owner) will be used:

Configure connection settings

Please choose "Connection" in the Navigation Area of the Modular Generic Adapter. Select  the Module “Slot<2> 1734-OB8E”.

Decode the field "trigger & transport" and "realtime format", which are defined in Connection9.

These parameters describe the connection variables, which have to be filled in the Connection configuration Window in Sycon.net.

The free Tool "EZ-EDS" from ODVA (https://www.odva.org/software/EZ-EDS-Download), can be used to make decoding of the parameters easier.

Therefore, open the EDS by selecting "File → Open…”.  Select "Generic EDS" as EDS type and ignore the upcoming error messages.

When the file is successfully opened, select “Connection1” in the left tree view.

The name “Connection9” in EDS file is automatically converted to “Connection1”.

The following dialog window:

Based on these informations, now configure the Connection Area in Sycon.net:

Don't forget, to set the Connection name to "Connection9".

Configure assembly instance ID

Choose "Assembly" in the Navigation Area of the Modular Generic Adapter now. Select  the Module “Slot<2> 1734-OB8E”.

Now the Connection Path has to be filled in. The Connection Path is described in the EDS here:

Switch back to EZ-EDS, select “Connection1”  in the left tree view.

Click the Button "Decode Path". A new Window will pop up. Select decimal format in this dialog now the instance ID can be read out for Configuration in Sycon.net.

Based on the above information, the assembly Instance ID can be specified.

The instance "20 04 24 7B 2C 22 2C 2C" can also be decoded manually as follows:

Configure Input assembly length

The input assembly length is defined in the field “T->O size” and field  “T->O format” of Connection 9:

It can be decoded as follows:

T → O 

, , Assem127

When the "Size" of the T=>O default description is empty, the format has to be evaluated.

In this case, Assem127 is used to define the format. Go to the definition of Assem127, in the EDS:

Since the field for the length is empty ($ Length in bytes), the Membe fields fields should be evaluated:

The Assemblys Member can be decoded as follows:

,,

32,,

,Assem44;

This means, the first Member is reserved, the second one has a size of 4Byte (32Bit) and the third one references to Assem44.

Go to Assem44:

The "total length in bytes" is defined as "1".

Now the total size of Assem127 can be defined:

Configure Output assembly length

The output assembly length is defined in the field “O->T size” and field  “O->T format” of Connection 9:

It can be decoded as follows:

O → T

,,Assem126,

When the "Size" of the O=>T default description is empty, the format has to be evaluated.

In this case, Assem126 is used to define the format. Go to the definition of Assem126, in the EDS:

Since the field for the length is empty ($ Length in bytes), the Membe fields fields should be evaluated:

The Assemblys Member can be decoded as follows:

,,

,Assem34;

This means, the first Member is reserved, the second one references to Assem34.

Go to Assem34:

The "total length in bytes" is defined as "1".

Now the total size of Assem126 can be defined:

Configure configuration assembly length

The configuration assembly length is automatically calculated by the data length of cfg. #1 and cfg. #2 data segment. 

The user is not allowed to directly edit this length.

Configure cfg. #1 data segment

The cfg #1 data segment is defined in field "$ config part 1" of Connection9:

Here Assem124 is used to define the format. Go to the definition of Assem124:

In this case, both Values ("Member Size" and "Member Reference" have to be evaluated.

The Assemblys Member informations can be read as follows:

The field of the first Member indicated, that it has a data length of 16 bit. It also has a Reference to Param121.

Go to the definition of Param121:

The "data size in Byte" has a size of 2 Byte, with a default value of 1.

So the default data of Param121 is 0x0001.

The user can also define a value between min. value and max. value.

Go back the definition of Assem124, the Second Member has a length of 16 and has no Reference entry. This means, all data are defined with value 0.

Configure cfg. #2 data segment

The cfg #2 data segment is defined in field "$ config part 2" of Connection9:

Here Assem123 is used to define the format. Go to the definition of Assem123:

This Assembly has a few more Members.

Please repeate the procedure mentioned in the first data segment for each Member.

For example the first Member:

The Size of this Member is definded with 1Bit and has a Reference to Param43:

The Size is defined with 1 Byte, the Default Value is 0 (Hex 0000):

When analyzing all Members and Parameters, the following table can be created:

Therefore the cfg #2 data segment results in:

E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803 E803

Final assembly configuration of 1734-IB8

example project provided by Stephane in SUPFR-86193