JP2020044917A - Electronic control device - Google Patents

Abstract

To determine whether a diagnosis code recorded by an on-vehicle electronic control device is a specific diagnosis code or not only by a vehicle inexpensively.SOLUTION: An on-vehicle electronic control device (20) includes a communication part, a list storage part, a code selection part, and a message generation part. In S11, the communication part receives an acquisition request of a specific diagnosis code from a request device (2), and transmits an acquisition request of a diagnosis code to other on-vehicle electronic control devices (30-36). The list storage part stores a list of the specific diagnosis codes. In S15, the code selection part refers to the list the list storage part stores, and selects the specific diagnosis code from the diagnosis codes the communication part receives from the other electronic control devices. In S16, the message generation part generates a communication message to transmit the specific diagnosis code selected by the code selection part from the communication part to the request device.SELECTED DRAWING: Figure 5

Description

  The present disclosure relates to a technique for determining whether a diagnostic code recorded by an on-vehicle electronic control device is a specific diagnostic code.

  It is known that a vehicle-mounted electronic control unit detects the occurrence of some abnormality in various sensors, actuators, and the like on the vehicle by OBD and records a diagnostic code corresponding to the abnormality. OBD is an abbreviation for On-board Diagnostics. Hereinafter, the diagnostic code is also referred to as DTC. DTC is an abbreviation for Diagnostic Trouble Code.

  For example, in Patent Literature 1, an inspection tool, which is an external device connected to a vehicle network, reads and displays DTC recorded by each of a plurality of electronic control devices via a master ECU, and a maintenance person inspects the DTC. A technique is described in which a DTC displayed on a tool is confirmed to recognize a failed portion. Hereinafter, the electronic control unit is also referred to as an ECU. ECU is an abbreviation for Electronic Control Unit.

  Further, Patent Literature 1 discloses a technique in which a DTC stored in a vehicle is transmitted to a center, and the DTC is transmitted from the center to an inspection tool.

  By the way, among the DTCs, when a specific DTC indicating that a defect that does not satisfy the safety standard of the road transport vehicle in the vehicle inspection has occurred is read out by the inspection tool, the vehicle inspection is rejected by utilizing the on-board failure diagnosis device. It has been proposed as an automobile inspection technique. The determination as to whether or not the specific DTC has been read out includes, for example, transmitting the DTC read from the vehicle by the inspection tool to a server such as a host computer at the center, and the server determining whether or not the received DTC is the specific DTC. It is done by doing.

JP 2006-113668 A

  However, in a system in which the server determines whether the DTC received from the inspection tool is the specific DTC, there is a problem that the server needs to be constructed and the cost of operating and maintaining the server is also required.

  On the other hand, it is considered that each of the on-vehicle ECUs requested to transmit the DTC from the inspection tool determines whether the recorded DTC is the specific DTC and transmits only the specific DTC to the inspection tool. Can be According to this configuration, since each of the ECUs selects the specific DTC from the recorded DTCs and transmits the selected DTC to the inspection tool, the inspection tool reads only the specific DTC from the vehicle. Therefore, a server for determining whether or not the DTC received from the inspection tool is the specific DTC becomes unnecessary.

  However, since it is necessary to install processing software for determining whether or not the recorded DTC is the specific DTC in each ECU mounted on the vehicle, the development of the processing software for each ECU becomes complicated and the development cost increases. There is a problem that.

  The present disclosure provides a technology for inexpensively determining whether or not a diagnostic code recorded by an on-vehicle electronic control device is a specific diagnostic code only by a vehicle.

  The electronic control unit mounted on a vehicle according to the present disclosure includes a communication unit (22, S2, S3, S5, S11, S12, S16, S21, S23, S25, S31, S32), a list storage unit (24), and a code selection unit. (26, S4, S15, S400 to S408) and a message generator (28, S4, S16).

  The communication unit receives a request for acquiring a specific diagnostic code from the requesting device (2), and transmits a request for acquiring a diagnostic code to the other electronic control devices (30 to 36) mounted on the vehicle. The list storage unit stores a list (200) of specific diagnostic codes to be transmitted to the requesting device. The code selecting unit refers to the list stored in the list storage unit and selects a specific diagnostic code from the diagnostic codes received by the communication unit from another electronic control device.

The message generation unit generates a communication message for transmitting the specific diagnostic code selected by the code selection unit from the communication unit to the requesting device.
According to this configuration, one of the on-vehicle electronic control devices that receives the acquisition request for the specific diagnostic code from the requesting device receives the diagnostic code received from the other electronic control device based on the stored list of the specific diagnostic codes. Since the specific diagnostic code is selected and transmitted to the requesting device, the vehicle can determine whether the diagnostic code recorded in the vehicle is the specific diagnostic code.

Therefore, there is no need to construct a server for determining whether or not the diagnostic code recorded in the vehicle is a specific diagnostic code, and there is no need to operate and maintain the server.
Further, other electronic control devices than the one electronic control device that receives the request for acquiring the specific diagnostic code from the requesting device, upon receiving the request for acquiring the diagnostic code, determine whether the recorded diagnostic code is the specific diagnostic code. It is transmitted as it is without determining whether or not it is. This facilitates the development of the processing software of another electronic control device, and reduces the development cost.

  From the above, in the electronic control device of the present disclosure, it is possible to inexpensively determine whether or not the diagnostic code recorded by the on-vehicle electronic control device is the specific diagnostic code only by the vehicle.

FIG. 2 is a block diagram showing a vehicle control system. The schematic diagram which shows a specific DTC list. FIG. 7 is a sequence diagram showing output processing of a specific DTC. 9 is a flowchart illustrating output processing of a specific DTC. FIG. 13 is a sequence diagram showing another output process of the specific DTC. FIG. 4 is a block diagram illustrating disabling of a function depending on the presence or absence of an ECU. FIG. 4 is a block diagram illustrating a function invalidation request from an inspection tool. FIG. 9 is a sequence diagram illustrating a function invalidation process. FIG. 7 is a sequence diagram showing a process of editing a specific DTC list.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
[1. First Embodiment]
[1-1. Constitution]
The vehicle control system 10 shown in FIG. 1 includes a master ECU 20 and a plurality of slave ECUs 30 to 36. The master ECU 20 and the plurality of slave ECUs 30 to 36 are connected to an in-vehicle LAN 100 such as a CAN, and execute vehicle control specified in advance. CAN is an abbreviation for Controller Area Network. The inspection tool 2 is connected to the master ECU 20 via a connector at a maintenance shop or the like.

  The master ECU 20 and the plurality of slave ECUs 30 to 36 are mainly configured by a known microcomputer having a CPU (not shown) and a semiconductor memory such as a RAM, a ROM, and a flash memory.

  Various functions of the master ECU 20 and the plurality of slave ECUs 30 to 36 are realized by the CPU executing a program stored in the non-transitional substantial recording medium. In this example, the semiconductor memory corresponds to a non-transitional substantial recording medium storing a program. When this program is executed, a method corresponding to the program is executed. Note that the master ECU 20 and the plurality of slave ECUs 30 to 36 may each be configured by a single microcomputer, or may be configured by a plurality of microcomputers.

  The master ECU 20 includes a communication unit 22, a list storage unit 24, a code selection unit 26, and a message generation unit 28 as the configuration of the functions realized by the CPU executing the program.

  The method of realizing these elements constituting the master ECU 20 is not limited to software, and a part or all of the elements may be realized using one or a plurality of hardware. For example, when the above function is implemented by an electronic circuit that is hardware, the electronic circuit may be implemented by a digital circuit including a large number of logic circuits, an analog circuit, or a combination thereof.

The communication unit 22 communicates with the slave ECUs 30 to 36 via the in-vehicle LAN 100 and communicates with the inspection tool 2 via the connector.
The list storage unit 24 is a rewritable nonvolatile storage device such as a flash memory, and stores the specific DTC list 200 shown in FIG. The specific DTC list 200 stores DTCs and determination information for determining whether each DTC is a specific DTC. The discrimination information indicates that it is a specific DTC if it is ○, and indicates that it is not a specific DTC if it is X.
In addition, the specific DTC is proposed as a DTC indicating that a failure that does not satisfy the security standard of the road transport vehicle in the vehicle inspection has occurred.

The code selecting unit 26 refers to the specific DTC list 200 and selects the specific DTC from the DTCs received by the communication unit 22 from the slave ECUs 30 to 36.
The message generator 28 generates a communication message to be transmitted to the inspection tool 2.

[1-2. processing]
(1) Specific DTC output processing 1
A specific DTC output process 1 in which the master ECU 20 outputs a specific DTC in response to a request from the inspection tool 2 will be described with reference to a sequence diagram of FIG.

  In S <b> 1, the inspection tool 2 transmits to the master ECU 20 a request to acquire the specific DTC to the slave ECU from which the specific DTC is to be acquired. The inspection tool 2 requests the master ECU 20 to acquire a specific DTC using a code defined by UDS of the international standard or a specific CANID when communicating by CAN. UDS is an abbreviation for Unified Diagnostic Services.

  In S2, the communication unit 22 of the master ECU 20 transmits not only the specific DTC but also the acquisition request of the recorded DTC to the slave ECU from which the specific DTC specified by the inspection tool 2 is to be obtained.

The slave ECU that has received the DTC acquisition request in S3 transmits the recorded DTC to the master ECU 20.
In S4, the communication unit 22 of the master ECU 20 receives a communication message including DTC recorded by the slave ECU from the slave ECU. Then, the code selection unit 26 of the master ECU 20 refers to the specific DTC list 200 stored in the list storage unit 24, and selects a DTC corresponding to the specific DTC from the DTC received from the slave ECU.

  The message generation unit 28 generates a communication message for transmitting the specific DTC selected by the code selection unit 26 to the inspection tool 2. Details of a process in which master ECU 20 selects a DTC corresponding to the specific DTC from the DTC received from the slave ECU will be described later.

In S5, the communication unit 22 of the master ECU 20 transmits the communication message generated by the message generation unit 28 in S4 to the inspection tool 2.
In S6, the processing of S1 to S5 is repeatedly executed for each slave ECU from which the specific DTC is to be obtained.

In S7, the inspection tool 2 determines whether or not the vehicle passes the vehicle inspection based on the specific DTC included in the communication message received from the master ECU 20.
(2) Specific DTC Selection Processing The specific DTC selection processing executed by the code selection unit 26 of the master ECU 20 in S4 of FIG. 3 will be described based on the flowchart of FIG.

  In S400, the code selection unit 26 counts the number of DTCs included in the communication message received from the slave ECU and sets the number to the variable N. In S402, the code selection unit 26 determines whether or not the N-th DTC corresponds to the specific DTC set in the specific DTC list 200. If the determination in S402 is Yes, that is, if the N-th DTC corresponds to the specific DTC set in the specific DTC list 200, the process proceeds to S406.

  If the determination in S402 is No, that is, if the Nth DTC does not correspond to the specific DTC set in the specific DTC list 200, the code selecting unit 26 determines in S404 the Nth DTC among the DTCs received from the slave ECU. Remove.

  In S406, the code selection unit 26 decrements N by one. Then, in S408, the code selection unit 26 determines whether or not N is greater than 0, that is, whether or not there is any DTC that has not yet been determined as to whether or not it is the specific DTC in the DTC received from the slave ECU. I do.

  If the determination in S408 is Yes, that is, if the DTC received from the slave ECU includes a DTC for which it has not yet been determined whether or not it is the specific DTC, the process proceeds to S402.

If the determination in S408 is No, that is, if it is determined whether all the DTCs received from the slave ECUs are the specific DTCs, the process ends.
(3) Specific DTC output processing 2
A specific DTC output process 2 in which the master ECU 20 outputs a specific DTC in response to a request from the inspection tool 2 will be described with reference to a sequence diagram of FIG.

  In the above-described specific DTC output processing 1, the master ECU 20 selects the specific DTC from the received DTC and transmits it to the inspection tool 2 every time a communication message including the DTC is received from each slave ECU from which the specific DTC is acquired. did.

  On the other hand, in the specific DTC output process 2, upon receiving the specific DTC acquisition request from the inspection tool 2, the master ECU 20 receives a communication message including the DTC from all the slave ECUs, and then extracts the specific DTC from the received DTC. Select and send to inspection tool 2.

Specifically, in S10, the inspection tool 2 transmits a request to acquire the specific DTC to all the slave ECUs of the vehicle to the master ECU 20.
In S11, the communication unit 22 of the master ECU 20 receives a request to acquire a specific DTC from the inspection tool 2. Then, the communication unit 22 transmits not only the specific DTC but also the acquisition request of the recorded DTC for each slave ECU.

The slave ECU that has received the DTC acquisition request in S12 transmits the recorded DTC to the master ECU 20.
In S13, the communication unit 22 of the master ECU 20 receives a communication message including the recorded DTC from the slave ECU. Then, the code selection unit 26 of the master ECU 20 temporarily stores the DTC received by the communication unit 22 from the slave ECU in a RAM or the like.

  In S14, the processing of S11 to S13 is executed for each slave ECU. In S15, when the communication unit 22 receives the communication message including the DTC recorded from all the slave ECUs 30 to 36, the code selection unit 26 refers to the specific DTC list 200 stored in the list storage unit 24, and The DTC corresponding to the specific DTC is selected from the DTCs temporarily stored in the DTC. The process of selecting a specific DTC from the received DTC is substantially the same as the above-described specific DTC selection process shown in FIG.

  In S16, the message generator 28 generates a communication message for transmitting the specific DTC selected by the code selector 26 to the inspection tool 2. Then, the communication unit 22 of the master ECU 20 transmits the communication message generated by the message generation unit 28 to the inspection tool 2.

In S17, the inspection tool 2 determines whether or not the vehicle passes the vehicle inspection based on the specific DTC included in the communication message received from the master ECU 20.
[1-3. effect]
In the first embodiment, the following effects can be obtained.

  (1a) Upon receiving the DTC acquisition request, the slave ECUs 30 to 36 other than the master ECU 20 transmit the request to the master ECU 20 without determining whether the recorded DTC is the specific DTC. Since it is not necessary to mount a process for determining whether or not the recorded DTC is the specific DTC in the slave ECUs 30 to 36, development of processing software for the slave ECUs 30 to 36 is facilitated, and development costs are reduced. Become cheap.

  (1b) Based on the specific DTC list 200 stored in the master ECU 20, the vehicle determines whether or not the DTC received from the slave ECUs 30 to 36 is the specific DTC and selects it. Since the selected specific DTC is transmitted from the vehicle to the inspection tool 2, a server for determining whether or not the DTC recorded in the vehicle is the specific DTC is unnecessary. Therefore, there is no need for building a server, and there is no need for operating and maintaining the server.

  In the first embodiment, the inspection tool 2 corresponds to a requesting device, the master ECU 20 corresponds to an electronic control device that receives a request for acquiring a specific diagnostic code from the requesting device, and the slave ECUs 30 to 36 respond to a request for acquiring a diagnostic code. Corresponds to the electronic control device that receives.

  Also, S2, S3, S5, S11, S12, and S16 correspond to the processing of the communication unit, S4, S15, and S400 to S408 correspond to the processing of the code selection unit, and S4 and S16 correspond to the processing of the message generation unit. I do.

[2. Second Embodiment]
[2-1. Differences from First Embodiment]
The differences between the second embodiment and the first embodiment will be described below. The same reference numerals as in the first embodiment denote the same components, and refer to the preceding description.

  In the vehicle control system 12 shown in the upper part of FIG. 6, the master ECU 40 differs from the first embodiment in that the master ECU 40 further includes a list editing unit 42 in addition to the configuration of the master ECU 20 of the first embodiment.

  The list editing unit 42 determines whether to enable or disable the DTC as the specific DTC in the specific DTC list 200 stored in the list storage unit 24, for example, by the following methods (a) to (c). Edit with.

(A) In the specific DTC list 200, the determination information indicating whether or not the DTC is the specific DTC is set to “に” or “×”.
(B) In the specific DTC list 200, the DTC entry is deleted or a new entry is added.

  (C) In the specific DTC list 200 from which the column of the discrimination information is removed, if the stored DTC is not the specific DTC, the DTC that is not the specific DTC is stored as a part of the specific DTC list 200.

[2-2. List editing example]
Hereinafter, editing examples (1) to (3) of the specific DTC list 200 by the list editing unit 42 will be described.

(1) Editing example 1
In the vehicle control system 12, the slave ECUs 30 to 34 realize a function of operating an automatic brake based on image data captured by a camera, for example, with three units except the slave ECU 36.

  It is assumed that the vehicle control system 14 illustrated in the lower part of FIG. 6 is configured by removing the slave ECU 32 that automatically controls, for example, a brake actuator from the vehicle control system 12 illustrated in the upper part of FIG. Since the slave ECU 32 has been removed, the automatic brake function is disabled in the vehicle control system 14.

  In this case, the list editing unit 42 of the master ECU 40 determines that the slave ECU 32 has been removed and does not exist in the vehicle control system 14 when receiving a request to acquire a specific DTC from the inspection tool 2 or from the inspection tool 2 Before the acquisition request is received, it is detected by communication within the vehicle control system 14.

  For example, if the communication unit 22 transmits a communication message to each slave ECU using the communication ID assigned to each slave ECU and cannot receive a reply message within a predetermined time, the list editing unit 42 sets the slave ECU corresponding to the communication ID to Is determined not to exist.

  When the list editing unit 42 detects that the slave ECU 32 has been removed and does not exist in the vehicle control system 14, the list editing unit 42 determines that the function of the automatic brake has been invalidated, and invalidates the setting in which the DTC corresponding to the automatic brake has been set as the specific DTC. Become

This setting is invalidated, for example, by the following methods (a1) to (c1) based on the editing methods (a) to (c) described above.
(A1) In the specific DTC list 200 of FIG. 2, the determination information indicating whether or not the DTC corresponding to the automatic brake is the specific DTC is changed from “「 ”to“ × ”.

(B1) In the specific DTC list 200 of FIG. 2, the entry of the DTC corresponding to the automatic brake is deleted.
(C1) The DTC corresponding to the automatic brake to be invalidated is stored as a part of the specific DTC list 200.

  By executing any one of the above-mentioned (a1) to (c1), for example, in the vehicle control system 14, the slave ECU 30 detects a camera abnormality and responds to a DTC acquisition request from the master ECU 40. Even if the slave ECU 30 transmits the DTC indicating the abnormality of the automatic brake, the master ECU 40 does not transmit the DTC indicating the abnormality of the automatic brake to the inspection tool 2 as the specific DTC.

(2) Editing example 2
As an editing example 2, as shown in FIG. 7, a function disabling process executed by the master ECU 40 when the inspection tool 2 requests the vehicle control system 10 to disable a specific function is illustrated in a sequence diagram of FIG. It will be described based on the following.

  In S20, the inspection tool 2 transmits a function invalidation request to the master ECU 40. In S21, the communication unit 22 receives a function invalidation request from the inspection tool 2. The list editing unit 42 transmits a function invalidation request from the communication unit 22 to the slave ECU whose function is to be invalidated. For example, when the inspection tool 2 requests the invalidation of the function of the automatic brake, the list editing unit 42 selects the slave ECU 32 as the slave ECU whose function is to be invalidated, and the communication unit 22 transmits the automatic brake to the slave ECU 32. Send an invalidation request.

The slave ECU 32 that has received the request to disable the function of the automatic brake in S22 disables the function of activating the automatic brake, and thereafter does not execute the control of the automatic brake.
In S23, the slave ECU 32 notifies the master ECU 40 that the disabling of the function for operating the automatic brake has been completed. The communication unit 22 of the master ECU 40 receives, from the slave ECU 32, a notification of completion of disabling the function of operating the automatic brake.

In S24, the list editing unit 42 executes one of the invalidation processes (a1) to (c1) described in the first editing example.
In S25, the list editing unit 42 notifies the inspection tool 2 from the communication unit 22 that the disabling of the automatic brake function has been completed.

(3) Editing example 3
As shown in FIG. 9, in S30, a request to edit the specific DTC list 200 is transmitted from the inspection tool 2 to the master ECU 40.

  In S31, the communication unit 22 receives a request to edit the specific DTC list 200 from the inspection tool 2. The list editing unit 42 responds to the editing request of the specific DTC list 200 received by the communication unit 22 from the inspection tool 2 by using any of the editing methods (a) to (c) described in the editing example 1. Edit.

In S32, the list editor 42 notifies the inspection tool 2 from the communication unit 22 that the editing of the specific DTC list 200 has been completed.
[2-3. effect]
In the second embodiment, the following effects can be obtained in addition to the effects (1a) and (1b) of the first embodiment.

  (2a) Editing methods (a) to (c) for specific DTC list 200 in the vehicle control system without manually executing the above editing methods (a) to (c) for specific DTC list 200 Since the execution is performed, the load of editing the specific DTC list 200 can be reduced.

  (2b) In the case of a configuration in which the DTC of the vehicle is transmitted from the inspection tool 2 to the server and the server determines whether or not the DTC is a specific DTC, an effective function and an invalid function are applied to the server for each vehicle. It is necessary to create a specific DTC list for each vehicle. Therefore, when a function is disabled or enabled in the vehicle, it is necessary to apply to the server each time the function is disabled or enabled.

  On the other hand, in the second embodiment, since the specific DTC corresponding to the invalid function is not transmitted to the inspection tool 2, it is necessary to notify the server and apply even if the function is invalidated or activated in the vehicle control system. There is no.

  (2c) Since the inspection tool 2 can request the master ECU 40 to edit the specific DTC list 200, addition and deletion of the DTC, and invalidation and activation of the specific DTC can be easily performed.

  (2d) By invalidating a function not required to be mounted on the vehicle, such as an automatic brake function, a function not required to be mounted on the vehicle has failed and is transmitted to the inspection tool 2 as a specific DTC, and the vehicle inspection is performed. Rejection can be suppressed.

In the second embodiment, S21, S23, S25, S31, and S32 correspond to processing of the communication unit, and S24 corresponds to processing of the list editing unit.
[3. Other Embodiments]
Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above embodiments, and can be implemented with various modifications.

  (1) In the above embodiment, the inspection tool 2 transmits a request for acquiring a specific DTC, a request for disabling a function, and a request for editing a specific DTC list to the master ECU 20. On the other hand, in addition to the inspection tool 2, a navigation device, a specific ECU in the vehicle control system is used as a request device for transmitting a request for acquiring a specific DTC, a request for disabling a function, and a request for editing a specific DTC list to the master ECU. May work.

  (2) In the second embodiment, in the list editing unit 42 of the master ECU 40, the software version of any one of the slave ECUs 30 to 36 is upgraded, and the function that has been disabled until now is enabled. This may be detected by communication within the vehicle control system 14 when receiving a request for obtaining a specific DTC from the inspection tool 2 or before receiving a request for obtaining a specific DTC from the inspection tool 2.

In this case, when the DTC of the enabled function corresponds to the specific DTC, the list editing unit 42 sets the corresponding DTC in the specific DTC list 200 as the specific DTC.
(3) In the second embodiment, as the editing example (1) of the specific DTC list 200, the function is invalidated when the slave ECU is removed, and as the editing example (2), the function is invalidated by a request from the inspection tool 2. Was explained.

On the other hand, as the editing of the specific DTC list 200, the function activation when a slave ECU is added, and the function activation according to a request from the inspection tool 2 may be executed.
(4) A plurality of functions of one component in the above embodiment may be realized by a plurality of components, or one function of one component may be realized by a plurality of components. . Also, a plurality of functions of a plurality of components may be realized by one component, or one function realized by a plurality of components may be realized by one component. Further, a part of the configuration of the above embodiment may be omitted. Further, at least a part of the configuration of the above-described embodiment may be added to or replaced with the configuration of another above-described embodiment.

  (5) In addition to the above electronic control devices 20 and 40, a system including the electronic control device 20 as a component, a program for causing a computer to function as the electronic control devices 20 and 40, a semiconductor memory storing the program, and the like. The present disclosure can be realized in various forms, such as a non-transitional actual recording medium and an electronic control method.

2: Inspection tool (request device), 20, 40: Master ECU (electronic control device), 22: Communication unit, 24: List storage unit, 26: Code selection unit, 28: Message generation unit, 30 to 36: Slave ECU (Other electronic control devices), 42: List editor, 200: Specific DTC list

Claims (7)

An on-vehicle electronic control device (20, 40),
Upon receiving a request for obtaining a specific diagnostic code from the requesting device (2), the communication unit (22, S2, S3, S5, S11,...) Transmits a request for obtaining a diagnostic code to the other electronic control units (30 to 36) mounted on the vehicle. S12, S16, S21, S23, S25, S31, S32),
A list storage unit (24) storing a list (200) of the specific diagnostic codes to be transmitted to the requesting device;
A code selection unit (26, S4) configured to refer to the list stored in the list storage unit and to select the specific diagnostic code from the diagnostic codes received by the communication unit from another electronic control device. , S15, S400 to S408);
A message generation unit (28, S4, S16) configured to generate a communication message for transmitting the specific diagnostic code selected by the code selection unit from the communication unit to the request device;
An electronic control device comprising: The electronic control device according to claim 1,
A list editing unit (42, S24, S31) configured to invalidate a part of the specific diagnostic code of the list stored in the list storage unit;
Electronic control unit. The electronic control device according to claim 2, wherein
The list editing unit is configured to enable or disable the specific diagnostic code of a part of the list according to the presence or absence of the other electronic control device.
Electronic control unit. The electronic control device according to claim 2 or 3,
The list editing unit is configured to enable or disable the specific diagnostic code of a part of the list according to a software version of the other electronic control device.
Electronic control unit. The electronic control device according to any one of claims 2 to 4, wherein
The list editing unit (S24), when the communication unit receives a request for disabling a function for the another electronic control device from the requesting device, deletes the specific diagnostic code of the list corresponding to the function of the disabling request. Configured to disable,
Electronic control unit. The electronic control device according to any one of claims 1 to 5,
The list editing unit (S31) is configured to add the new specific diagnostic code to the list according to an instruction from the request device.
Electronic control unit. The electronic control device according to claim 1, wherein:
The message generating unit, when the communication unit receives the acquisition request for the specific diagnostic code from the requesting device, the specific diagnostic code selected by the code selecting unit from the diagnostic code received from the other electronic control device. Generating the communication message to be transmitted from the communication unit to the requesting device, when the communication unit receives a normal acquisition request of the diagnostic code from the requesting device, the diagnostic code received from the other electronic control device, It is configured to generate the communication message to be transmitted from the communication unit to the requesting device,
Electronic control unit.

Images