MULTIPLE-JOB-ECU

A multiple-ECU job is like a single ECU job with the following characteristics:

• A SINGLE-JOB-ECU can only communicate with a controller

• MULTIPLE ECU JOBs describe jobs (macros from Java code) for diagnostic procedures, related to several control units

• The runtime system has to simultaneously manage multiple LOGICAL-LINK

• Typical use vehicle identification: There are diagnostic queries simultaneously sent to all built-in control units

A Diag-layer container is an element that accurately describes a control device. But there are a number of diagnostic tasks that run across multiple control units and because only one diag-layer containers can be active, such a diagnosis task can not be run within a single diag-layer container. It has therefore been arranged hierarchically on the same level as the Diag-layer container, the multiple-ECU job. The runtime system has to manage simultaneously multiple logical links, so that we can communicate with multiple controllers. A typical application would be the vehicle identification. If the diagnostic tester is connected to the vehicle, is typically queried once, which control devices are built-in which variants in the vehicle. This could theoretically treat over single-ECU-jobs, where each controller is checked individually. One can simplify the task but also by defining a multiple-ECU job in which all control devices are polled within that single job. The remaining structure of a multiple-ECU-jobs is that of a single ECU jobs.