TMC8462 Datasheet • Document Revision V1.4 • 2018-May -09
157 / 204
7.10 MFC IO ESI/XML Configuration Block
This example shows the part of the ESI/XML configuration file for EtherCAT slaves used to configure the
MCF IO block directly out of the EEPROM (at power-up or reset). Therefore, the configuration block must
be classified as category 1 information within the EEPROM.
Another way to configure the MFC IO block is to directly write via PDI or ECAT interface to the EtherCAT
registers at 0x0580 to 0x05E1 (ESC Parameter RAM).
An easy way to generate the configuration data string that is used in this XML structure is to use the wizard
included in the TMCL-IDE. See also section ESI Configuration Wizard.
1
3
<Eeprom >
<ByteSize >2048 </ByteSize >
<!-- Mandatory configuration bytes according to EtherCAT standard -->
ConfigData >0000000000000000000... </ConfigData >
5
7
<!-- MFC IO Configuration vector must be of category 1. -->
<!-- It will be loaded into registers 0x0580 ...0 x05E1 -->
9
<!-- during EEPROM loading at startup.
-->
<Category >
11
13
15
17
19
<CatNo >1</CatNo >
<Data >00000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000
00000000
</Data >
</Category >
</Eeprom >
Figure 33: MFC IO ESI/XML Configuration Block
Note
The zeros in the example above are just placeholders and must be adapted to
the respective configuration.
See the available application notes and examples on www.trinamic.com for more
information.
©2018 TRINAMIC Motion Control GmbH & Co. KG, Hamburg, Germany
Terms of delivery and rights to technical change reserved.
Download newest version at www.trinamic.com
TRINAMIC [ TRINAMIC MOTION CONTROL GMBH & CO. KG. ]
