The combination of high transmission rate and small latency, as FETK ECU Interfaces offer it, is unique on the market. Because the investment in a FETK development ECU pays twice, for measurement and calibration as well as for prototyping experiments, the use of FETK ECU interfaces can make a major contribution to save development costs.
In contrast to validation and calibration of ECUs, where as much data as possible from the ECU has to be recorded simultaneously, prototyping of fast controls is depending on as small latency as possible. Functions are often model-based developed by means of ETAS ASCET or MATLAB®/Simulink® and then implemented on a special prototyping hardware, which communicates with the ECU in real-time. The latency of the communication when a 128 Byte long signal is exchanged between an FETK ECU interface and the prototyping hardware and back amounts less than 250 µs in the complete cycle. The flash memory of an ECU can be programmed via an FETK interface just as fast and save as with a debugger.
Different from the use of serial interfaces such as CAN, FETK interface operation by the ECU barely requires computing power. The independent power supply of an FETK enables to perform tests, as for example cold start tests independently of the operating state of the ECU.
Universal, standard conform and comfortable
The new FETK ECU Interface can be profitably and universally employed for diverse applications which demand different functionalities from the interface. From a user’s perspective, FETKs offer high ease of use: the Gigabit Ethernet interface is generic. This means it abstracts from the specific connection to the particular micro controller of an ECU. By means of an ES89x ECU and Bus Interface Module, applications can access ECUs with FETK interface via the standardized XCP-on-Ethernet protocol from their host device.
- High data transmission rates up to 20 MB/s (depending on the particular µC interface)
- XCP-on-Ethernet access to FETK-ECUs via an ES89x ECU and Bus Interface Module
- Best real-time behavior: Supports control cycles up to 10 µs
- Small latency of less than 250 µs in prototyping applications
- Simultaneous access of up to four applications to one ECU possible
- Compliant with ETK-S20.1 and ETK-S21.1
FETKs are available in two versions: FETK-S (left) and FETK-T (right).
Both variants use a microcontroller-specific production device (µC-PD) debug interface such as JTAG, DAP, or LFAST as access to the control system.
The FETK-T version additionally supports the particularly powerful µC emulation device (µC-ED) trace interfaces together with the high-performance transmission of trace data from the ECU via the serial Aurora interface.