太阳集团6138(CHINA)澳门企业-环球百科

A. Process use case management

TSMaster's automated diagnostic process is not only for a specific application, but for the whole project to manage the diagnostic process. Users can configure test diagnostic process groups according to the needs of the complete project, and each group can contain several different diagnostic processes, and only in a diagnostic process contains specific diagnostic steps. As shown in the figure below:

Right mouse click on the UDS Process Management column to expand the action menu for Process Use Case Management as shown in the following figure:

❖ It mainly contains the following operations:

[1] Add a new group: Add a new diagnostic process group, such as model 1. For example, add a new model 1. Diagnostic process use cases can be added under the diagnostic group, which itself does not contain diagnostic steps.

[2] Add a new uds flow: add a new diagnostic flow use case, under the diagnostic flow use case you can add detailed diagnostic steps.

【3】Edit name: Select a process group or process use case, right click and select Edit name to edit the name of the node, as shown in the following figure:

[4] Switch to the uds flow: Switch to the current UDS flow node. Double-click the node, you can also achieve the effect of switching to the flow node. After switching to the node, the node icon and background color are shown in the figure below, while the node flow on the right expands to show the detailed diagnostic steps included in the uds flow:

[5] Start Uds flow: Start the diagnostic flow of this node. After clicking this option, the diagnostic module automatically executes the diagnostic steps from top to bottom according to the configuration on the right.

[6] Abort Uds flow: Click on this node to interrupt the diagnostic flow steps being executed.

【7】 Delete selected: Delete the selected node.

【8】 Delete all flows: Clear all nodes.

B. Configuration Diagnostics Flow (UDS Flow)

❖ B-1 Basic configuration steps:

Configure the diagnostic process with the basic steps shown below:

[1] Select a diagnostic process node in the left management column.

[2] Add, delete, and edit diagnostic steps in the edit area on the right.

[3] After adding a step, edit the step name.

[4] Select the type of step.

[5] Select the type of address for this step, physical address or functional address.

[6] Configure detailed diagnostic request packets and answer packets.

[7] Configure the wait time between steps after this step.

[8] Configure the error handling method when an error occurs in this step.

The above steps are the basic steps to configure the diagnostic process, the actual use, according to the application scenario also provides a more flexible mechanism, then read the subsequent chapters.

❖ B-2 Toolbar:

The diagnostic process configuration toolbar is shown in the following figure.

[1] Added a new diagnostic process group.

[2] New diagnostic process use cases have been added.

[3] Delete the selected diagnostic process group/use case.

[4] Start the configured diagnostic process.

[5] Interrupt the running diagnostic process.

[6] Lock/unlock the process configuration area. If this area is locked, it becomes uneditable in the diagnostic process area.

❖ B-3 Type of diagnostic step:

In order to increase the flexibility of diagnostic configuration in the test step, five types are designed for selection, as shown in the figure below, mainly including: Normal, SelectConfig, SeedAndKey, DownloadFile, TesterPresent, RoutineControl. through these five types, basically covers the market, basically covers all the mainstream diagnostic process requirements, the following detailed description of the characteristics of each type.

[1] Normal: Normal configuration. This configuration is mainly used for some simple occasions where the request data and answer data are clear. For example, if the service request data is [10 03] and the service response data is [50 03 12 34], you can choose the Normal type.The configuration of Normal is the simplest, directly fill in the Request with the request data you want to send [10 03], and fill in the Response with the desired response message [50 03 12 34]. When configuring the Response message, expand as follows:

Because in some test cases, ECU is not answering, for this case, users just need to uncheck Has Response. After completing the configuration, the effect is shown below:

[2] SelectConfig: Select the existing configuration, which is designed to allow the user to select the diagnostic steps that have been debugged in the Diagnostic Console console. The selection process is shown in the figure below:

This is the most recommended way for TSmaster to configure. Users can first configure and test all the sub-processes in Diagnostic Console, and then refer to the configuration in the auto-diagnostic process, the logic is shown in the following figure:

During the execution of the automated diagnostic process, the execution is exactly the same as it will be in the Diagnostic Console.

[3] SeedAndKey: SeedAndKey is a combination of commands, which can not be configured directly with the Normal command. Users can SelectConfig directly from the existing configuration, but also by selecting the type of SeedAndKey, in the automatic process directly configure the decryption steps. SeedAndKey only need to select the SeedLevel parameter can be decrypted DLL is directly associated with the TP parameter configuration loaded in the SeedAndKey in the Dll. As shown in the figure below:

As you can see, the prerequisite for correct operation in either the Diagnostic Console module or the Automatic Diagnostic module requires that the user has correctly completed the configuration of the TP layer parameters.

[4] TesterPresent: As mentioned earlier, TSMaster provides a global switch for TesterPresent, through which users can directly turn the command on and off. At the same time, in order to support more flexible testing needs, in the automation process steps, also provides a step-based configuration of the command, allowing users to choose to turn on and off the TesterPresent command at the desired step. After selecting this type, there are two main parameters to configure:

Whether to start/stop the command is as follows:

Configure the data for this command, as well as the cycle interval, as follows:

[Diagnostic step-by-step configuration summary]

To summarize the configuration flow of the test steps in the previous section, the logical flow is composed as shown below:

❖ B-4 Step interval:

The time interval between steps and steps of the diagnostic process module is settable, as shown below in ms.

❖ B-5 Error handling:

Error handling, at this stage, consists of two main parameters: the number of retries after an error and whether to stop or continue running after an error, as shown below:

❖ B-6 Enable step/position adjustment:

For the diagnostic process steps that have already been configured, users check the diagnostic steps they want to perform according to the selection box on the left, as shown in the following figure:

Adjustment of Execution Order: Whether it is a test case group, a test case or a specific step in a test case, when the user wants to adjust the execution order among them, he can directly drag and drop the corresponding test case to the corresponding position.

overviewPreface