You are currently viewing 新功能发布 | TSMaster诊断功能的典型应用

New Releases | Typical Applications for TSMaster Diagnostics


The previous chapters mainly introduced some basic operation details about TSMaster diagnostic module, I believe you have a certain understanding and cognition of TSMaster diagnostic module. This chapter mainly introduces the typical application of TSMaster diagnostic function, which mainly includes the typical application operation of reading vehicle VIN code, writing configuration information and Flash Bootloader process.

A. Reading vehicle VIN numbers

The execution effect is shown below:

As you can see, the same ReadDataByID, the test step of quoting BasicConfig with the corresponding parsing information, you can directly out of the read string for "ReadDemo".

B. Writing configuration information

The execution effect is shown below:

As can be seen, the same WriteDataByID, quoting BasicConfig test step because of the corresponding parsing information, you can directly out of the read string for the "ReadDemo".

C. Flash Bootloader

In this paper, a simple Bootloader flow is designed to illustrate how to configure a Flash Bootloader flow based on the TSMaster diagnostic module.

C-1. Flash Bootloader flow:

First of all, design FlashBootloader flow is shown below, this is a sample flow, the user can be adjusted according to their actual design specifications plastic.

C-2. configure the flashing routine:

[1] First create Demo1 process: Note that switching the editor to Unlock state, otherwise you can't add new process steps.

[2] For the switching session shown in the flowchart, close the DTC, COM control and other commands, directly configure the bit Normal type of command can be (note that these commands can of course also be configured in BasicConfig out here referenced). As shown below:

[3] Based on ReadDataByID read the data at location ID=F188 and determine if the data is equal to, for example, SN12345678. if it matches, the part number is determined to be matched and proceed to the next step, otherwise exit the process. The configuration is as follows:

Mode 1: Configure the bit Normal form directly, as shown below:

Way 2:Configured in BasicConfig and then referenced in the process:

[4] Switching to Programming Session

[5] Add the Seed&Key step to unlock the ECU with the following configuration:

[6] After obtaining permissions, write the string "SN1234" at IDF190, for this kind of fixed string, the most economical thing is to directly configure NormalStep, as shown below:

[7] Add FlashDriver/Application files. The way to add is the same whether it is FlashDriver or application file. Both ways:

Way 1: Add the DownloadFile step directly, as shown below:

Way 2: Configure BasicConfig and then reference it in Flow as follows:

[8] Use RoutineControl to erase Flash. here the address and length are fixed, so you can directly configure the fixed values as follows:

If the address and length are dynamically changing, see the subsequent section to solve this problem by introducing system variables.

[9] Restart the ECU, directly add NormalStep as shown below, it should be noted that ECUReset to restart diagnostics, the waiting time between steps need to be adjusted according to the ECU design specifications, here set to 1000ms:

[10] The rest of the switching will be the default session, COM control, DTC control and other operations, in accordance with the previous steps can be completely.

Summary of the chapter

After completing the configuration, the total configuration flow is shown below, which shows that with the help of TSMaster's diagnostic module, the development of diagnostic processes such as Bootloader and other applications is a very simple matter:

The actual running effect diagram is shown below: