Diagnostic

You don’t really need to start with a Diagnostic DB. Instead, you can create your own services in the Diagnostic section. The Diagnostic DB allows users to import ODX/PDX files into TSMaster.

In this automated process, the created diagnostic services are bound to system variables. By calling the API to modify the values of system variables, you can achieve looped invocation.

• _start: when variable’s value is 1, it indicates execution; when it’s 0, it indicates non-execution.
• _result: The variable is used to indicate the execution status, where 0 means not executed, 1 means running, 2 means executed successfully, and 3 means failure.

Yes, it requires the support of a diagnostic license. Since TSMaster supports the invocation of the automatic diagnostic process through COM, there is a registration limit to prevent misuse. Therefore, the corresponding diagnostic license is required for support.

After configuring the basic diagnostics and registering them as system variables, the results of each step will be displayed in the system variables when the automated diagnostic runs.

TC1005 does not support the diagnostic multi-frame transmission function. You may consider replacing it with another compatible CAN card to support UDS diagnostic functionality.

The inter-frame spacing for continuous frames depends on the STMin parameter replied by the receiving device. If the replied STMin = 0, it means sending at the fastest speed.

When the algorithm file is loaded, and the internal verification test within the software has passed, adding the sending key service results in an error message. Please refer to the following solutions:

Solution One :

1. In the basic diagnostic services, configure the 27 03 request seed service and the corresponding 27 04 sending key service.
   
   
2. In the automatic diagnostic process, directly add a 27 03 request seed service; there is no need to add the corresponding 27 04 request key service. The steps to add the request seed service are as follows:
   
   • Step 1: Right-click in the automatic diagnostic process, choose ‘Add New Step’ -> ‘Select Existing Configuration.’
     
     
   • Step 2: Click the dropdown button in the service name section, and choose the 27 03 request seed service.

Solution Two :
In the automatic diagnostic process, add seed and key services. The specific steps are as follows:

• Step 1: Right-click in the automatic diagnostic process, choose ‘Add New Step’ -> ‘Seed and Key.’
  
  
• Step 2: In the request service, click the dropdown button and choose Seed Level: 3, Key Level: 4.
  

The services in the database-based diagnostic module require hardware with a valid license to be able to transmit.

Sending multiple flow control frames usually occurs due to improper usage, and there are two possible scenarios:

1. Multiple basic diagnostic modules are created, and both modules are enabled before starting the project.
2. After creating a diagnostic module in the C script, diagnostic messages are sent, and after completion, the module is not deleted.

Usually, it is essential to pay attention to whether the current session is maintained, for example, the interval between the 27 command and the 31 command has exceeded approximately 10 seconds. In general, ECU extended sessions automatically return to the default session after more than 5 seconds, so there are several ways to ensure the extended session is maintained:

1. Execute all commands in the automation process to ensure controlled command sending times.
2. Add the 3E 80 command to the process to maintain the ECU session.
   
   
3. Check the time settings of the S3 server and client.