HMS Anybus CompactCom 30

To Next Page

To Previous Page

Network Specific — EtherCAT 20 (38)

9.3.2 Keywords

The ESI-file generator is up to date with the following differences between the 30-series and the

40-series.

The Product Code, Revision Number and Product Name must be updated to reflect the current

module. Note: These values can be changed via the EtherCAT object (F5h) and the ESI-file val-

ues must match the EtherCAT object values.

CompactCom 40 EtherCAT</Type>

The EtherCAT state transition timeouts must be present in the ESI-file per the latest specifica-

tion. Note: These timeout values can be change via the EtherCAT object (F5h) and the ESI-file

values must match the EtherCAT object values.

</StateMachine>

The sync manager start addresses have been changed in the 40-series, and the sync manager

sizes are now configurable in the EtherCAT configuration tool.

<Sm MinSize="34" MaxSize="1486" DefaultSize="276" StartAddress="#x4000"

ControlByte="#x26" Enable="1">MBoxOut</Sm>

<Sm MinSize="34" MaxSize="1486" DefaultSize="276" StartAddress="#x4800"

ControlByte="#x22" Enable="1">MBoxIn</Sm>

<Sm StartAddress="#x2800" ControlByte="#x20" Enable="1">Inputs</Sm>

The 40-series supports File over EtherCAT (FoE) and this must be reflected in the ESI-file. If

FoE is disabled in the EtherCAT host object, this keyword must be removed from the ESI-file.

<FoE/>

Since the 40-series is using the HMS slave controller, the EEPROM byte size and the SII config-

uration data must be changed according to the following settings.

The 40-series supports the boot strap state, and requires the following keyword.

Migrating from Anybus

CompactCom

™

30 to Anybus

CompactCom

™

40 Design Guide SCM-1202-043 1.1

HMS Anybus CompactCom 30 - Page 22