Creating DUT Mapping
- Updated2025-10-31
- 3 minute(s) read
To design processes and the test station independently and modular to the battery, no battery-specific variables may be used in the process. To still have access to essential functions, use the standardized mapping described below.
Test Station to BMS
In the example below, both the selected operating mode and the status of terminal 15 must be transmitted to the battery.
The frequency group selected in the CAN group must match the frequency group in the mapping.
BMS to Test Station
Batteries send dynamic operating limits for current and voltage depending on the operating state and the charge. These can be entered in the application as limits of the setpoints from manual and automatic operation.
The following figure shows the mapping of the BMS-specific variables that are used in the application.
The following values are used in the application:
- Limits for current, voltage, and power
- State of charge (SOC)
- Voltage
- Current
Both dynamic limits and predicted values are available. In the example, the battery sends current limit values so that these are transferred to the dynamic and predicted values.
Furthermore, the current operating mode of the battery and optionally the SOC, the temperature (maximum) and measured current and voltage must be transmitted.
BMS to this Module
Use the following mapping to map specific signals from BMS to the signals used in this module, such as BMS_Mode or BMS_Temperature.
Advanced Logic
The PAscript BMS_Control.PS is available for extended control requirements. With this script, you can program the required logic in graphical programming.
The example represents feedback of the battery mode. In the sequence, the variables BattPack_BMS_Drive.STS, BattPack_BMS_Park.STS etc., are used for standardization. However, the battery works with only the variable BMS_Mode.AV. Therefore, the battery-specific setting of the status variables can be implemented by the following switch case command.
