JP6224475B2 - Vehicle control device - Google Patents

Description

  The present invention relates to a vehicle control device that performs data communication with an external device via a network, and more particularly to a vehicle control device that performs data communication with a vehicle diagnosis device on an IP basis using an Internet line.

  Generally, by connecting a vehicle control device mounted on a vehicle such as an automobile and a diagnostic device (diagnostic tool) so that communication can be performed regardless of wired or wireless, for example, in a repair shop or the like, It is known to read not only diagnostic information such as vehicle failure data but also internal data of a control ECU and rewrite of a control program using a predetermined communication format.

  In recent years, IP-based communication using an Internet line has been studied for communication between the vehicle control device and the diagnosis device. In this IP-based communication, it is necessary to use the Internet protocol (IP). For this reason, a standard (Diagnostic over Internet Protocol, hereinafter referred to as DoIP) for communication between a vehicle control device mounted on a vehicle and a diagnostic device has been standardized as ISO13400.

  As a technique related to such DoIP, for example, in Japanese Unexamined Patent Application Publication No. 2013-102393 (Patent Document 1), when each node returns a vehicle identification response message including a vehicle identification code to an external device, the communication load is reduced. In order to suppress the increase and increase in the use capacity of the non-volatile memory, a vehicle identification code is stored in a DoIP edge node that directly communicates with a diagnostic device that is an external device among a plurality of nodes. It is shown that the vehicle identification code stored in the DoIP edge node is also used when a vehicle identification response message is returned in response to the vehicle identification request message to the node.

JP 2013-102393 A

  By the way, when using an IP-based network, it is often the case that a plurality of unit vehicle control devices are simultaneously connected to the network. Here, the unit vehicle control device means individual control devices such as an engine control device, a brake control device, a transmission control device, and a navigation control device. For this reason, the diagnostic device that is an external device needs to identify to which vehicle the unit vehicle control device connected to the network belongs.

  ISO 13400 stipulates that a vehicle identification code (vehicle identification number, abbreviated as VIN) is used for this identification. For example, the diagnostic device transmits a vehicle identification request message to each unit vehicle control device connected to the network, and each unit vehicle control device returns a vehicle identification response message including the vehicle identification code VIN together with its IP address. become. As a result, the diagnostic device can identify which vehicle each unit vehicle control device belongs to by using the vehicle identification code VIN as a clue.

  In the following description, it is assumed that the vehicle identification code VIN is stored in the nonvolatile memory of the engine control ECU for convenience. However, the present invention is not limited to this, and the vehicle identification code VIN is assigned to another control ECU. May be stored.

  This vehicle identification code VIN is unique to each vehicle and is written in a nonvolatile memory of the engine control ECU of the engine control system. Therefore, in order for each unit vehicle control device to acquire the vehicle identification code VIN, the vehicle identification code VIN is read from the engine control ECU that stores the vehicle identification code VIN, and transferred to the node of the other unit vehicle control device. It may be added to the header of the identification response message. In addition, as described in Patent Document 1, from the viewpoint of communication load, a vehicle identification code VIN is stored in a node (edge node) that directly communicates with an external device among a plurality of nodes. It is conceivable to add this vehicle identification code VIN to the header of the vehicle identification response message.

  However, for some reason, the vehicle identification code VIN may disappear from the non-volatile memory, or the vehicle identification code VIN stored immediately after rewriting the control program of the engine control ECU may disappear. . In such a situation, when the diagnostic device transmits a vehicle identification request message, the vehicle identification response message returned from each unit vehicle control device does not include the vehicle identification code VIN. As a result, it becomes impossible to obtain a clue to associate (relate) each unit vehicle control device. For this reason, when unit vehicle control devices of a plurality of vehicles are connected to the network at the same time, the diagnostic device falls into a state where it cannot be identified which unit vehicle control device of any vehicle.

  In such a case, the vehicle identification code VIN can be recovered by writing the vehicle identification code VIN again in the nonvolatile memory of the engine control ECU. However, in the case where a plurality of vehicles are connected to the network, It is difficult to determine whether the vehicle is in a state where the vehicle identification code VIN of the vehicle has disappeared.

  An object of the present invention is a vehicle control device capable of identifying which vehicle each unit vehicle control device belongs to even when the vehicle identification code VIN stored in one unit vehicle control device has disappeared. Is to provide.

  A feature of the present invention is that one of the nodes included in the plurality of unit vehicle control devices is used as a representative node, and the individual identification information included in the representative node is transferred and stored as other vehicle identification information to other nodes than the representative node. In response to a vehicle identification request message transmitted from the diagnostic apparatus to each node, each node sends a vehicle identification response message including a vehicle identification code and vehicle identification information stored in each node itself, or to each node itself. Any one of the vehicle identification response messages including the stored vehicle identification information is returned to the diagnostic apparatus.

  According to the present invention, even if the vehicle identification code VIN stored in the unit vehicle control device has disappeared, the nodes of each unit vehicle control device for each vehicle have common vehicle identification information. Therefore, since the diagnostic device can manage them by linking them as a group, it can identify to which vehicle each unit vehicle control device belongs.

It is a block diagram of the vehicle control apparatus with which this invention is applied. It is explanatory drawing explaining the communication procedure between a diagnostic apparatus and each node. It is explanatory drawing explaining the management table of the diagnostic apparatus in case there exists a vehicle identification code. It is explanatory drawing explaining the management table of the diagnostic apparatus when there is no vehicle identification code. It is explanatory drawing explaining the communication procedure between the diagnostic apparatus which is typical embodiment of this invention, and each node. In embodiment shown in FIG. 5, it is explanatory drawing explaining the management table of a diagnostic apparatus in case there exists a vehicle identification code. In embodiment shown in FIG. 5, it is explanatory drawing explaining the management table of the diagnostic apparatus when there is no vehicle identification code.

  Next, embodiments of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to the following embodiments, and various modifications and application examples are included in the technical concept of the present invention. Is included in the range.

  FIG. 1 shows a configuration in a state where a plurality of vehicles and a diagnostic device are connected. In this embodiment, two vehicles are shown connected to a diagnostic device for the sake of simplicity.

  The first vehicle 10 and the second vehicle 20 are connected to an IP-based network 40 and are communicably connected to an external diagnostic device 30. As described above, the first vehicle 10 and the second vehicle 20 communicate with the diagnostic device 30 using DoIP defined in ISO 13400 as a communication protocol.

  The first vehicle 10 has a DoIP entity 13A and a DoIP entity 13B, and the second vehicle 20 has a DoIP entity 23A, a DoIP entity 23B, and a DoIP entity 23C. Further, these DoIP entities are additionally provided as necessary. Each DoIP entity 13 </ b> A, 13 </ b> B, 23 </ b> A, 23 </ b> B, 23 </ b> C includes a DoIP node that exchanges messages with the diagnostic apparatus 30. In the following description, the DoIP entity includes the concept of a DoIP node.

  And each DoIP entity 13A, 13B, 23A, 23B, 23C comprises sub-network with control ECU of the unit vehicle control apparatus of each vehicle. As described above, the unit vehicle control device including this sub-network means an individual control device such as an engine control device, a brake control device, a transmission control device, and a navigation control device.

  Therefore, for example, the DoIP entity 13A is connected to the engine control ECU 11A of the first vehicle 10 by the internal network 12A, and the DoIP entity 13B is connected to the brake control ECU 11B of the first vehicle 10 by the internal network 12B.

  Similarly, the DoIP entity 23A is connected to the engine control ECU 21A of the second vehicle 20 via the internal network 22A, the DoIP entity 23B is connected to the brake control ECU 21B of the second vehicle 20 via the internal network 22B, and the DoIP entity 23C is connected to the second network 20A. The navigation control ECU 21C of the vehicle 20 is connected to the internal network 22C.

  These sub-networks are representative examples, and various other sub-networks can be replaced or added. The communication protocol of this sub-network is connected with a communication protocol different from that of an IP-based network such as CAN or LIN.

  A vehicle identification code VIN1 and a vehicle identification code VIN2 are stored in a nonvolatile memory, for example, a flash memory, of the engine control ECU 11A of the first vehicle 10 and the engine control ECU 21A of the second vehicle 20, and these vehicle identification codes VIN1. , VIN2 is transferred to the DoIP entity 13A and the DoIP entity 23A at a predetermined timing. For example, the vehicle identification code VIN1 and the vehicle identification code VIN2 are transferred when the power supply of the unit vehicle control devices of the vehicles 10 and 20 is activated.

  Each DoIP entity 13A, 13B, 23A, 23B, and 23C includes a MAC address (Media Access Control address) that is a physical address that identifies a communication device on the network. The MAC address is a physical address uniquely assigned to the hardware of the network device in order to identify each node (= DoIP entity) on the network. As will be described later, this MAC address is used as individual identification information of each DoIP entity 13A, 13B, 23A, 23B, 23C, and one of them is used as vehicle identification information.

  This MAC address is assigned a unique value for each communication port of a node corresponding to a DoIP entity that performs packet transmission / reception. The DoIP entity 13A has a MAC address 13A-A, the DoIP entity 13B has a MAC address 13B-B, The MAC address 23A-A is assigned to the DoIP entity 23A, the MAC address 23B-B is assigned to the DoIP entity 23B, and the MAC address 23C-C is assigned to the DoIP entity 23C. Here, the DoIP entity 13A and the DoIP entity 23A are positioned as representative nodes.

  When the DoIP entities 13A, 13B, 23A, 23B, and 23C are communicably connected to the diagnostic apparatus 30 via the IP-based network 40 as described above, the first vehicle 10 and the second vehicle 10 are connected as shown in FIG. The DoIP entities 13A, 13B, 23A, 23B, and 23C of the vehicle 20 are connected simultaneously. As described above, the diagnostic device 130 reads out the diagnosis code and internal data, performs diagnosis of each control ECU, rewrites the control program, and the like. The diagnostic device 30 performs the DoIP of the first vehicle 10 and the second vehicle 20. The entities 13A, 13B, 23A, 23B, and 23C are selected and the above-described processing operation is executed.

  Therefore, the diagnostic device 30 needs to specify the vehicle that is the target of the processing operation, and for that purpose, it identifies which vehicle each node of each DoIP entity 13A, 13B, 23A, 23B, 23C belongs to. There is a need. For this identification, ISO 13400 stipulates that the vehicle identification code VIN is used.

  FIG. 2 shows a communication procedure for vehicle identification specified in ISO13400. As shown in FIG. 2, first, each DoIP entity 13A, 13B, 23A, 23B, 23C performs an IP address acquisition process.

  Next, after this IP address acquisition process, each DoIP entity 13A, 13B, 23A, 23B, 23C transmits a vehicle announcement message including its own IP address three times at times t1 to t3 by multicast. The diagnosis device 30 receives the vehicle announcement message, and transmits a vehicle identification request message to the corresponding DoIP entity based on the IP address at timing t4.

  When the corresponding DoIP entity receives the vehicle identification request message, in response to this, a vehicle identification response message including the vehicle identification code VIN is returned to the diagnostic device 30 that sent the message at timing t5. Accordingly, the diagnostic device 30 can identify to which vehicle each DoIP entity belongs based on the vehicle identification code VIN. Here, the vehicle identification response message is composed of at least a header area and a payload area, information for identifying the diagnostic device 30 and each DoIP entity is stored in the header area, and various various detailed information of each DoIP entity is stored in the payload area. Is remembered.

  Here, at the time of power activation, the vehicle identification code VIN1 is transferred from the DoIP entity 13A to the DoIP entity 13B, and similarly, the vehicle identification code VIN2 is transferred from the DoIP entity 23A to the DoIP entities 23B and 23C. The transferred vehicle identification codes VIN1, VIN2 are sent from the DoIP entities 13A, 13B, 23A, 23B, 23C to the diagnostic device 30, and the diagnostic device 30 uses the vehicle identification codes VIN1, VIN2 to output the DoIP entities 13A, The vehicle to which 13B, 23A, 23B, 23C belongs can be specified.

  Next, the linked state of the vehicles 10 and 20 and the DoIP entities 13A, 13B, 23A, 23B, and 23C in the diagnostic device 30 will be described with reference to FIG. In the diagnostic device 30 that has received the vehicle identification response message including the vehicle identification code VIN from the DoIP entity by the communication procedure shown in FIG. 2, the vehicle identification information VIN1 identifying that it belongs to the first vehicle 10 and the DoIP entities 13A and 13B Can be determined that the DoIP entities 13A and 13B belong to the first vehicle 10. Similarly, since the vehicle identification information VIN2 for identifying belonging to the second vehicle 20 and the DoIP entities 23A, 23B, and 23C are linked, the DoIP entities 23A, 23B, and 23C belong to the second vehicle 20. Can be judged.

  Thus, when the vehicle identification information VIN1 and VIN2 exist, the vehicle identification codes VIN1 and VIN2 are used as clues to which vehicle each DoIP entity 13A, 13B, 23A, 23B, and 23C is mounted. Can be managed.

  However, the vehicle identification codes VIN1 and VIN2 written in the engine control ECU 11A of the first vehicle 10 and the engine control ECU 21A of the second vehicle 20 disappear from the nonvolatile memory for some reason, and the control program for the engine control ECUs 11A and 21A The vehicle identification codes VIN1 and VIN2 stored immediately after rewriting may be lost.

  In such a case, the DoIP entities 13A, 13B, 23A, 23B, and 23C cannot return the vehicle identification code VIN1 and the vehicle identification code VIN2 to the diagnostic device 30. Therefore, as shown in FIG. 4, the DoIP entities 13A, 13B, 23A, 23B, and 23C are in a mutually disjoint relationship. Therefore, the diagnostic device 30 cannot identify which vehicle each DoIP entity 13A, 13B, 23A, 23B, 23C belongs to.

  As described above, the diagnostic device 30 can acquire the payload area information of the vehicle identification response message returned from each DoIP entity 13A, 13B, 23A, 23B, 23C, but the respective DoIP entities 13A, 13B, 23A, Which vehicle belongs to 23B and 23C cannot be identified, and the vehicle that is the target of the processing operation as described above cannot be specified.

  For example, the DoIP entities 23A, 23B, and 23C belong to the second vehicle 20, but since the individual DoIP entities 23A, 23B, and 23C are no longer associated with the vehicle identification code VIN2, the DoIP entity 23A , 23B and 23C are in a disjoint relationship, and the diagnostic device 30 cannot mutually identify the DoIP entities 23A, 23B and 23C.

  In order to deal with such a problem, in this embodiment, a DoIP entity to be a representative node is determined in advance among a plurality of DoIP entities in the vehicle, and the DoIP entity to be a representative node is fixed when the power is activated. A MAC address that functions as separate identification information is transferred to another DoIP entity.

  As a result, the MAC address of the representative node is stored in a node other than the DoIP entity serving as the representative node. The transferred MAC address (= specific identification information) of the DoIP entity is used as a vehicle identification MAC address (= vehicle identification information) of other DoIP entities.

  Then, when each DoIP entity 13A, 13B, 23A, 23B, 23C receives the vehicle identification request message from the diagnostic device 30, in response to that, the diagnostic device 30 of the message transmission source sends the vehicle identification codes VIN1, VIN2 The MAC addresses 13A-A and 23A-A of the DoIP entities 13A and 23A, which are representative nodes, are written in the header area of the vehicle identification response message as vehicle identification MAC addresses, and the vehicle identification response message is returned to the diagnostic device 30. To work.

  The vehicle identification codes VIN1 and VIN2 are transferred from the engine control ECUs 11A and 21A to the DoIP entity 13A and the DoIP entity 23A, which are representative nodes, when the power is turned on. For this reason, the DoIP entity 13A and the DoIP entity 23A, which are representative nodes, have a function of detecting that the vehicle identification code is not stored, and if it is detected that the vehicle identification code is not stored when the power is turned on. For example, it is configured to notify other nodes that the vehicle identification code is not stored. As a result, the other node creates a vehicle identification response message based on this.

  That is, if each DoIP entity 13A, 13B, 23A, 23B, 23C receives an identification request message transmitted from the diagnostic device 30 when the vehicle identification codes VIN1, VIN2 are not stored in its own memory, It operates to create a vehicle identification response message based on information indicating that the vehicle identification codes VIN1 and VIN2 are not stored and the vehicle identification MAC address and return the message to the diagnostic apparatus. When the vehicle identification request message is received from the diagnostic device, if the vehicle identification codes VIN1 and VIN2 are not stored, the LED lamp provided on the front panel of the vehicle is turned on to notify the outside. Is also possible.

  In the present embodiment, as described above, the DoIP entity 13A and the DoIP entity 23A are representative nodes, and the MAC address 13A-A and the MAC address 23A-A included therein are the vehicle identification MAC addresses, and the remaining DoIP entities. It is transferred and stored in 13B, 23B, and 23C.

  Next, the communication procedure of the present embodiment will be described with reference to FIG. 5, but the case shown in FIG. 5 is a case where the DoIP entities 23 </ b> A, 23 </ b> B, 23 </ b> C mounted on the second vehicle 20 communicate with the diagnostic device 30. Show.

  Each DoIP entity 13A, 13B, 23A, 23B, and 23C has a separate MAC address as described above. However, when communicating with the diagnostic device 30, each DoIP entity 13A, 13B, 23A, 23B, and 23C transmits a vehicle identification MAC address. The communication logic of the DoIP entity is set.

  Immediately after the power is turned on, the DoIP entity 23A serving as the representative node transfers and notifies its MAC address 23A-A as the vehicle identification MAC address to the DoIP entities 23B and 23C other than the representative node in the vehicle at timings t6 and t7. To do. The DoIP entities 23B and 23C that have received the notification temporarily store the received vehicle identification MAC address 23A-A in a volatile memory such as a RAM included in the node of the DoIP entities 23B and 23C, and timing t8, A response that the vehicle identification MAC address 23A-A is received is returned to the DoIP entity 23A at t9. In this state, the DoIP entities 23A, 23B, and 23C are in a state where the vehicle identification MAC address 23A-A is stored in common.

  Thereafter, the vehicle identification request messages are sequentially sent from the diagnosis device 30. For example, when a vehicle identification request message is sent to the DoIP entity 23B at timing t10, the DoIP entity 23B receives the vehicle identification code VIN2. In addition, the vehicle identification response message including the vehicle identification MAC address 23A-A sent at timing t6 is returned to the diagnostic device 30 at timing t11.

  Therefore, in addition to the vehicle identification code VIN2, the diagnostic device 30 can obtain information on the vehicle identification MAC address 23A-A unique to the vehicle as vehicle identification information. That is, the DoIP entities 23A, 23B, and 23C are linked (associated) with the vehicle identification code VIN2 and the vehicle identification MAC address 23A-A.

  Here, as described above, the vehicle identification response message is composed of a header area and a payload area. When the vehicle identification code has not disappeared, the vehicle identification code and the vehicle identification MAC address are stored in the header area. On the other hand, when the vehicle identification code has disappeared, the vehicle identification code is not stored in the header area, but only the vehicle identification MAC address is stored. In addition, it is also possible to store information indicating that the vehicle identification code is not stored.

  6 and 7 show a state of association (association) between the vehicle and each DoIP entity in the diagnostic apparatus 30, and FIG. 6 shows that communication was performed when the vehicle identification codes VIN1 and VIN2 have not disappeared. FIG. 7 shows a case where communication is performed when the vehicle identification codes VIN1 and VIN2 disappear. 6 and 7, the vehicle identification MAC address 13A-A is represented as MAC1, and the vehicle identification MAC address 23A-A is represented as MAC2.

  As can be seen, mutual association between the DoIP entities 13A, 13B, 23A, 23B, and 23C is possible by using the vehicle identification codes VIN1 and VIN2 and the vehicle identification MAC addresses 13A-A and 23A-A. Become.

  As shown in FIG. 6, in the diagnostic device 30, vehicle identification codes VIN1, VIN2 and vehicle identification MAC addresses MAC1, MAC2 are linked. Furthermore, DoIP entities 13A and 13B are linked as a group to the vehicle identification MAC address MAC1. Similarly, DoIP entities 23A, 23B, and 23C are linked as a group to the vehicle identification MAC address MAC2. As described above, since the vehicle identification MAC addresses MAC1 and MAC2 are related to the vehicle identification codes VIN1 and VIN2, which of these two pieces of information is used to determine which DoIP entity 13A, 13B, 23A, 23B, and 23C. It is possible to manage whether it is mounted on a vehicle.

  On the other hand, FIG. 7 shows a case where communication is performed in a state where the vehicle identification codes VIN1 and VIN2 have disappeared. As can be seen from FIG. 7, when the vehicle identification codes VIN1 and VIN2 disappear, the association between the vehicle identification codes VIN1 and VIN2 and the vehicle identification MAC addresses MAC1 and MAC2 disappears, so that the vehicle identification codes VIN1 and VIN2 are used. The vehicle cannot be specified. In such a case, conventionally, as shown in FIG. 4, the DoIP entities 13A, 13B, 23A, 23B, and 23C are individually separated, and there is no way to know how the strings are connected to each other. There wasn't.

  However, according to the present embodiment, DoIP entities 13A and 13B are associated with the vehicle identification MAC address MAC1, and DoIP entities 23A, 23B, and 23C are associated with the vehicle identification MAC address MAC2. It can be seen that at least the DoIP entities 13A, 13B are mounted on the first vehicle 10 and the DoIP entities 23A, 23B, 23C are mounted on the second vehicle 20.

  Thus, by assigning a common vehicle identification MAC address to each of a plurality of DoIP entities mounted on a vehicle, the plurality of DoIP entities can be managed as a group unique to the vehicle. Therefore, the relationship between the respective DoIP entities does not vary individually, and it becomes possible to know the linked state of a plurality of DoIP entities as a vehicle-specific group.

  It is also possible to store the association information of the vehicle identification code and the vehicle identification MAC address previously received in the diagnostic device 30. In this case, the vehicle identification code written in the engine control ECU disappears from the non-volatile memory, or the vehicle identification code stored immediately after the engine control ECU program is rewritten disappears. Even if it exists, it becomes possible to specify which vehicle identification code is stored by using the stored association information and the vehicle identification MAC address as a clue.

  This makes it possible to easily identify a vehicle in which the vehicle identification code has disappeared from among a plurality of connected vehicles. Furthermore, the vehicle identification code can be transmitted to the engine control ECU and written in the flash memory.

  As described above, the present invention uses one of the nodes included in the plurality of unit vehicle control devices as a representative node, and transfers the specific identification information of the representative node to other nodes other than the representative node as vehicle identification information. For each vehicle identification request message stored and transmitted from the diagnostic device to each node, each node receives a vehicle identification response message including a vehicle identification code and vehicle identification information stored in each node itself, or each node One of the vehicle identification response messages including the vehicle identification information stored in itself is returned to the diagnostic apparatus.

  According to this, even if the vehicle identification code VIN stored in the unit vehicle control device has disappeared, the nodes of each unit vehicle control device for each vehicle have common vehicle identification information. Therefore, since the diagnostic apparatus can manage them by linking them as a group, it can identify to which vehicle each unit vehicle control apparatus belongs.

  DESCRIPTION OF SYMBOLS 10 ... 1st vehicle, 20 ... 2nd vehicle, 30 ... Diagnostic apparatus, 40 ... IP-based network, 11A, 21A ... Engine control ECU, 11B, 21B ... Brake control ECU, 12A, 12B ... Network of 1st vehicle, 13A, 13B ... DoIP entity of the first vehicle, 13A-A, 13B-B ... MAC address of the DoIP entity of the first vehicle, 21C ... Navigation control ECU, 22A, 22B, 22C ... Network of the second vehicle, 23A, 23B , 23C ... DoIP entity of the second vehicle, 23A-A, 23B-B, 23C-C ... MAC address of the DoIP entity of the second vehicle.

Claims (2)

A plurality of unit vehicle control device connected by the onboard network of the vehicle, the vehicle control device which stores vehicle identification code identifying the vehicle in at least one of the units the vehicle control device,
Each of the unit vehicle control devices includes a node for exchanging messages with an external diagnostic device via communication,
One of the respective nodes is used as a representative node, and individual identification information possessed by the representative node is transferred to another node as vehicle identification information, and stored.
In response to a vehicle identification request message transmitted from the diagnostic device to each of the nodes, each node includes a vehicle identification response message including the vehicle identification code and the vehicle identification information stored in the node itself. Or any one of the vehicle identification response messages including the vehicle identification information stored in the respective nodes themselves without including the vehicle identification code ,
The plurality of unit vehicle control devices and the diagnostic device are connected via an Internet line using an Internet protocol,
The individual identification information included in the representative node is a MAC address included in the representative node, and the MAC address included in the representative node is used as a vehicle identification MAC address that is the vehicle identification information. Transfer and store to the node,
Further, when the power of the plurality of unit vehicle control devices is activated, the vehicle identification code is transferred to the representative node, and the representative node detects that the vehicle identification code is not transferred and stored. And the representative node notifies the other nodes other than the representative node that the vehicle identification code is not transferred and stored when the representative node detects that the vehicle identification code is not transferred and stored. A vehicle control device. The vehicle control device according to claim 1 ,
When the other node receives the identification request message transmitted from the diagnostic device, it creates an identification response message based on the information indicating that the vehicle identification code is not transferred or stored and the MAC address for vehicle identification. Then, a vehicle control device that notifies the diagnostic device of a reply is provided .

Images