Datasheet

TMC8462 Datasheet • Document Revision V1.5 • 2019-June-21
110 / 204
7 MFC IO Block Description
7.1 General Information
The MFC IO block includes a set of functions realized as dedicated hardware blocks.
The MFC IO block offers 24 fully configurable IOs that can be used with any function of the MFC IO block.
16 low voltage IOs capable of 3.3V or 5V and 8 high voltage IOs capable of up to 24V are available.
The MFC IO block functions can be used either via the MFC IO control interface (see section 5.2) or via
EtherCAT data objects mapped as registers to the Process Data Memory.
When using the MFC IO control interface the microcontroller has full control over the MFC IO block and its
hardware functions. This allows for offloading some firmware tasks towards the TMC8462, to do system
level control, or to extend the microcontroller’s IO capabilities.
When accessing the MFC IO block via EtherCAT data objects, centralized control from the EtherCAT master
is enabled. It it also possible to use the TMC8462 in device emulation mode without any microcontroller
connected while still using the dedicated hardware blocks and functions of the MFC IO block. For example,
the SPI master interface of the MFC IO block can be used to connected to a position sensor, which is read
out by the EtherCAT master.
Configuration of the MFC IO block is done via the SII EEPROM at startup or by the EtherCAT master or
microcontroller after startup.
SII EEPROM configuration data must be of category 1 and is automatically loaded at startup and written
into the ESC Parameter Ram section of the EtherCAT Register Set starting at address 0x0580 (see Section
6.4.11.1).
The ESC Parameter RAM section can also be written by the EtherCAT master or the local microcontroller
for direct configuration or to modify configuration after startup.
The block diagram in Figure 31 shows the general approach for the MFC IO block configuration.
Note
Even if the MFC IO block is only accessed from the microcontroller and the
EtherCAT access feature is not used, it is recommended to store at least the
crossbar configuration (section 7.5), the HVIO configuration (section 7.6) and the
switching regulator configuration (section 7.7) in the SII EEPROM.
By doing this, the settings are loaded faster than having to write them from the
microcontroller and it also reduces the memory usage on the microcontroller
itself.
Note
The MFC IO block parameters and register can be mapped into the the ESC
Process Data RAM. For some applications and combinations it is possible to use
these registers as cyclic data within a SyncManager. This is not possible for all
registers and combinations and depends on the use case!
©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