Datasheet

TMC8462 Datasheet Document Revision V1.5 2019-June-21
157 / 204
7.10 MFC IO ESI/XML Conguration Block
This example shows the part of the ESI/XML conguration le for EtherCAT slaves used to congure the
MCF IO block directly out of the EEPROM (at power-up or reset). Therefore, the conguration block must
be classied as category 1 information within the EEPROM.
Another way to congure 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 conguration data string that is used in this XML structure is to use the wizard
included in the TMCL-IDE. See also section ESI Conguration Wizard.
1 < Eeprom >
< ByteSize > 2048 </ ByteS ize >
3
<! -- Manda tory configuration bytes acc ording to EtherCAT standa rd -->
5 ConfigData > 00 00 00 0 00 00 00 0 00 00 0 .. . </ ConfigData >
7 <! -- MFC IO Configuration vector must be of c ategory 1. -- >
<! -- It will be loaded into registers 0 x0580 ...0 x05E1 -- >
9 <! -- during EEPROM loadin g at startup . -- >
< Category >
11 < CatNo >1 </ CatNo >
< Data > 0 00000 0 00 00000 0 00 00000 0 00 00000 0 00 00000 0 00 00000 0
13 00 0 00 00000 0 00 00000 0 00 00000 0 00000 0 0 00000 0 00 00000
0000 0 00000 0 0 00000 0 00 00000 0 00 00000 0 00 00000 0 00 000
15 00 0 00 00000 0 00 00000 0 00 00000 0 00000 0 0 00000 0 00 00000
00 000000
17 </ Data >
</ Categ ory >
19
</ Eeprom >
Figure 33: MFC IO ESI/XML Conguration Block
Note
The zeros in the example above are just placeholders and must be adapted to
the respective conguration.
See the available application notes and examples on
www.trinamic.com
for more
information.
©2019 TRINAMIC Motion Control GmbH & Co. KG, Hamburg, Germany
Terms of delivery and rights to technical change reserved.
Download newest version at www.trinamic.com