Skip to main content

Support Support


Questions and answers on ECAT Measurement modules.

What is the maximum number of high-speed ECAT modules that can be connected to an XCP gateway?

Note: To use high-speed measurement rates (sampling rates greater than 10 kHz) with CSM ECAT modules, the ECAT operating mode must be set to "10 kHz or packed" in the XCP gateway.

The maximum possible number of modules depends significantly on the selected sampling rate.
The following table applies if all modules of the measurement chain are configured at the same rate:

Sampling Rate Max. Number of Modules Max. Number of Channels
10 kHz 25 × ECAT STGMM 6 150 channels
25 × AD4 ECAT MM 100 channels
100 kHz 11 × AD4 ECAT MM 44 channels
1000 kHz 1 × AD4 ECAT MM 4 channels

Mixed high speed measuring rates can only be used in combination with the XCP version 1.4 format. To do this, set the XCP compatibility accordingly in the CSMconfig program settings. The combination possibilities of modules with different sampling rates are almost unlimited. Therefore, the maximum number of modules for two combinations is listed in the following table as an example:

Max. Number of Modules Sampling Rate Max. Number of Channels

+ 1 × AD4 ECAT MM
+ 1 × AD4 ECAT MM

1000 kHz 4 channels
100 kHz 4 channels
10 kHz 4 channels
+ 11 × AD4 ECAT MM
1000 kHz 4 channels
10 kHz 44 channels

The CSMconfig configuration software provides feedback when configuring an ECAT measurement chain:
Overload configurations are easy to detect and prevent because a warning message appears if the permissible CAN bus load is exceeded.

What is the pinning of the signal sockets for ECAT modules?

The pin assignment of the corresponding signal socket for the ECAT modules can be found in the two documents "ECAT STGMM6" and "ECAT ADMM4 HS", which are located under Help at CSMconfig.

Standard PIN assignment of the ECAT signal socket:

1. Signal socket for AD4 ECAT MM series

Connector measuring input

Pin Signal
(unipolar sensor excitation )
(bipolar sensor excitation)
View of module front LEMO 0B, 6pol
View of module front
LEMO 1B, 8pol
1 VIN - VIN - Input voltage, minus
2 VIN +
Input voltage, plus
3 VGND VGND Sensor supply ground
4 VOUT + VOUT + Sensor supply output, plus
5 - VOUT - Sensor supply output, minus
6 - - reserved, do not connect
Channel Shield
Channel Shield
TEDS Ground
Shield for measurement signal
8 TEDS Data TEDS Data Data line (TEDS)
Housing Cable Shield Cable Shield Outer Shield (housing)
2. Signal socket for STG ECAT MM series
Connector measuring input Pin Signal Description
View of module front LEMO 0B, 6pol
View of module front
LEMO 1B, 8pol
1 VIN - Input voltage, minus
2 VIN +
Input voltage, plus
3 VOUT - Bridge excitation voltage, ground
4 VOUT + Bridge excitation voltage, plus
5 VSENSE - Sense minus
6 VSENSE + Sense plus
Channel Shield
TEDS Ground
Shield for measurement signal
8 TEDS Data Data line (TEDS)
Housing Cable Shield Outer Shield (housing)

What is required for synchronization according to IEEE1588 (Precision Time Protocol)?

The following hardware is required for the synchronization of several ECAT measuring modules according to IEEE1588 (Precision Time Protocol):

  • XCP gateway; HW Rev. C000 with FW as of V3.10
  • Gateway-Option PTP/IEEE1588

If this option has not yet been activated for your gateway, please contact your personal customer advisor or

What are the special features of the CAN input at the XCP-Gateway?

When using the CAN input on the XCP-Gateway, the following characteristic features must be obeyed:

  • Modules can be operated with a maximum sampling rate of 1 kHz per channel.
  • CAN bit rates from 125 kBit/s to a maximum of 1 Mbit/s can be used.
  • CSMconfig only provides the means to configure the supported ECM modules (LambdaCANc, NOxCAN) via the CAN interfaces of the XCP-Gateway. Measurement operation is not possible because these modules transmit 32-bit signals. The only exception is the LambdaCANc if it is operated in 16-bit mode.
  • Connected CAN measurement modules are supplied with power via the XCP-Gateway. The gateway supplies up to 10 modules (HV Modules up to 3). Use an daisy chain cable with power supply for each additional group of 10 modules.
  • The CAN interfaces of the XCP-Gateway are terminated via an internal 120 Ω resistor. An additional terminating resistor is therefore only required at the end of a long measurement chain. Additional terminating resistors may even lead to problems.
  • It is not possible to use external DBC files at the CAN interfaces of the gateway. Only those measurement modules are supported which can also be found and configured in CSMconfig.
  • The transmission of CAN messages via the XCP-Gateway to the measuring modules connected to the CAN input is not supported.
    Thus, for example, modules that have an internal calibration procedure cannot be calibrated during measurement operation using a predefined CAN message.

Measurement interruptions occurred during an EtherCAT measurement. How can these measurement interruptions be avoided?

Measurements with Ethernet measurement technology at the XCP gateway very quickly result in a large amount of data, which must be passed on to the measurement software by the gateway.

The following points should be observed in order to avoid measurement interruptions or loss of data during measurements:

  • Use a powerful measuring computer with high-performance CPU. An SSD hard disk is recommended.
  • If possible, connect the measuring chain directly (LAN interface) or via a Vector Ethernet interface (e.g. VN5640, VN5601) to the measuring computer.
  • Avoid additional load on the measuring computer from other programs (e.g. Office products, Internet Explorer). Do not perform any other tasks on the computer during measurement operation.

Why is it not possible to edit the parameters for STGMM in the channel list?

There are numerous correlations between the different variables in STGMM. Since no automatic error detection and correction can be carried out in the channel list the parameters cannot be answered here.
This behaviour also applies to the exhaust gas modules of ECM and OUTMM.

The XCP gateway is not found in CSMconfig despite correct IP settings. What could be the reason?

In the firewall settings, ports 5555 and 5556 must be enabled in both directions inbound as well as outbound .


  • Port 5555: Used for measurement operation.
  • Port 5556: Used for the broadcast that is used to find both the gateway and the connected modules.

Where can the ECAT bus load be read?

The bus load of an ECAT measuring chain can only be read in the report of the XCP-Gateway.

Why does the calibration date not always appear in the CSMconfig report?

If you explicitly read out the module via the device dialog you can check a calibration date in the module. If no calibration information is displayed in this dialog, then none is stored in the module.

Note: Calibration information is not stored in the A2L file but only in the module. If an A2L file is loaded and a report is generated it does not contain any information about the calibration.

Can the ECAT measurement technology also be used in CSMview?

As of CSMconfig V8.10.1 ECAT measurement modules are also supported by CSMview but only with the Windows standard network connection. A connection via VX0312 and similar Vector interfaces which Windows does not detect as network adapter is not possible.

Which synchronization method has priority per XCP gateway 4S?

With the XCP gateway 4S pro there are two ways to synchronize:

  • PTP according to IEEE 1588
  • global time synchronization via GPS

If both mechanisms have been activated via CSMconfig, PTP always has the higher priority. In addition, the GPS signals are received and stored in the device. Thus a fast fallback to the GPS synchronization is possible if the PTP time master fails (approx. 10 seconds).

Why is it not possible to set a 120 Ohm full bridge on a HV STG4 pro at 10 V bridge excitation?

Due to the too high power consumption it is not possible to use a 120 Ohm bridge resistor at 10 V supply voltage. The user is informed of this fact when attempting such a configuration from Config 9.1.0.