Calibration

You would need to write your A2L files first, then import them into TSMaster. You can view your signals and observe 8 parameters for free.
If you want to calibrate the parameters, you need to purchase the XCP license.

This problem primarily involves physical layer connections, calibration configurations, and factors related to the ECU.

• Check the physical connection and channel configuration of the CAN connection channel.
• Ensure that the main identifier ID in the calibration protocol is set correctly.
• Confirm if the ECU itself is functioning properly.

Yes, it is supported.

1. Activate the cache.
2. Load the hex file.
3. In the database, select the calibration values you want to read and import them into parameter curves.
4. Perform an offline calibration connection.
5. View the corresponding data signals in the parameter curves.

Yes, it supports CAN FD.

1. First, configure the bus hardware, changing it to the corresponding CAN FD baud rate and sample point, for example, 500k+2000k.
   
   
2. In Calibration Manager – Protocols, perform CAN FD parameter configuration:
   1. • Transport layer master-slave node identifier type: Change to Standard FD or Extend FD.
      • Request maximum data length, enable it.
      • FD DLC, choose 64 Bytes.
      • FD BRS, check the box.

   

TSMaster is compatible with CANOE’s A2L files, currently supporting version 1.61 only. Future versions will be optimized to support higher versions.

In general, resolving this issue may require remote support to ensure detailed configuration correctness. Here are some suggestions to address the problem:

1. Ensure that the ECU’s firmware version matches the A2L file and check if the addresses for calibration quantities are correct. It’s essential to record the CAN raw Trace during calibration for comparison and instruction inspection.

2. Pay attention to page switching during calibration and understand the difference between RAM and Flash. Typically, calibration pages are located in Flash pages, as indicated in the A2L file.
   
   

3. Check for address mapping. If there is mapping, ensure that there are corresponding definitions in the A2L file and that they match in the memory section or Flash memory. Alternatively, manually modify the configuration to match. For example, if the Flash’s starting address is 0x80040000 and is mapped to the RAM area with a starting address of 0x60000000, with a configured length of 0x10000, this maps the Flash address region to the RAM area.
   
   
   
   

4. Try replacing the ECU with another known-good one if there is a spare.

5. If the user has other normal calibration tools like CANape or INCA, compare the calibration configurations in these tools for cross-reference.

6. Consider recreating the calibration project, re-adding calibration signals, and resetting the signal stimulation window. Sometimes, empty addresses like F6 00 00 00 00 00 00 00 might require reconfiguration.

First, review the message information and check if the request messages (F6) sent during the calibration process are correctly transmitting variable addresses. If the addresses are not transmitted correctly, there may be an issue with the address configuration. Please check the address configuration in the memory section to ensure it aligns with the configuration in the A2L file.

Typically, if there is no response to the F4 command, it may be due to the use of illegal or abnormal addresses. When using CANape, pay special attention to checking the addresses following the F4 and F6 commands, and there may also be issues related to address mapping.

1. Enable the cache in ‘Memory’ -> ‘Memory Configuration’ and connect to the ECU. You can view the created memory image file in the Memory manager at the bottom.
2. Perform online calibration and modify the relevant calibration parameters.
3. In ‘Memory manager,’ select the latest modified image file, right-click, and choose ‘Export the currently selected file.’
4. Save it in hex format, which is the calibration workspace file during the calibration process.