Network system, assembly diagnostic methods, manager ECU and main ECU

By using a network system for sending and receiving messages between ECUs, and by collecting and analyzing list information through the manager ECU and the main ECU, the problem of ECU assembly errors was solved, the correctness of power and communication connections was ensured, and the power saving and reliability of the system were improved.

CN123123370APending Publication Date: 2026-11-17DENSO CORP
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202610648116.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-15
Filing Date
2026-05-12
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In large-scale network systems, incorrect ECU assembly can lead to poor connections between power supply lines and communication networks, and existing technologies struggle to effectively diagnose whether the ECU is assembled correctly.

Method used

By using a network system that sends and receives messages between ECUs, the manager ECU and the master ECU collect and analyze a list of information representing the relationship between switch and slave ECU identifiers to diagnose whether the ECUs are correctly assembled.

Benefits of technology

It enables accurate diagnostics of ECU assembly, ensures proper connection of power supply lines and communication networks, and improves the system's power saving and reliability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123370A_ABST
    Figure CN123123370A_ABST
Patent Text Reader

Abstract

This invention provides a network system, an assembly diagnostic method, a manager ECU, and a master ECU. In a large-scale network system with multiple sets of slave ECUs (40, 50, 60) and master ECUs (20), a manager ECU (10) is provided to collect list information representing the relationship between identifiers of relay switches (16, 26, 28) and slave ECUs from multiple master ECUs. Therefore, based on the collected list information, it is possible to diagnose whether the slave ECUs are correctly assembled for the relay switches.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to a network system for sending and receiving messages between multiple ECUs, an assembly diagnostic method for diagnosing whether ECUs are correctly assembled in the network system, a manager ECU for the network system, and a master ECU. Background Technology

[0002] For example, Patent Document 1 discloses a vehicle communication system configured to connect multiple control devices mounted on a vehicle via a data communication network, with each control device sending and receiving data to and from the other via the network.

[0003] Existing technical documents Patent documents Patent Document 1: Japanese Patent No. 5639425 Summary of the Invention

[0004] In constructing a system consisting of multiple control units (ECUs) as described in Patent Document 1, power saving is required as a whole system. Therefore, for example, it is considered to enable at least one ECU (master ECU) to control the presence or absence of power supply to at least one ECU (slave ECU). Thus, the master ECU can supply power to the slave ECU only when the slave ECU needs to operate, and cut off the power supply to the slave ECU when the slave ECU does not need to operate. As a result, the dark current when the slave ECU does not need to operate can be cut off, and further power saving can be achieved as a whole system.

[0005] Here, as described above, in a configuration where the presence or absence of power supply to slave ECUs is controlled by the master ECU, the slave ECUs, conceived as objects to which the master ECU controls the presence or absence of power supply, including the connection to the power supply line controlled by the master ECU, need to be correctly assembled to avoid confusion with other types of slave ECUs. However, during the ECU assembly process, the possibility of incorrectly assembling an ECU other than the intended slave ECU is not zero. Furthermore, the assembly process of slave ECUs, including the connection to the power supply line, is not always performed correctly. Such assembly errors are more likely to occur in large-scale network systems with multiple sets of master ECUs and slave ECUs.

[0006] This disclosure is made in view of the foregoing points, with the aim of providing a network system capable of collecting information for diagnosing whether at least a number of slave ECUs are correctly assembled in a large-scale network system with multiple sets of master ECUs and slave ECUs. Furthermore, this disclosure aims to provide an assembly diagnostic method for diagnosing whether at least a number of slave ECUs are correctly assembled. Additionally, this disclosure aims to provide manager ECUs and master ECUs for use in large-scale network systems.

[0007] To achieve the above objectives, the network system disclosed herein is a network system for sending and receiving messages between multiple ECUs. The multiple ECUs include: a slave ECU that, upon startup, sends a message containing its own identifier; a master ECU that has the function of turning a switch on or off a power supply line provided to the slave ECU, and creates a list of relationships between the switch and the slave ECU's identifier based on the message containing the identifier received from the slave ECU when the switch is turned on; and a manager ECU that collects the list of information from the multiple master ECUs. Multiple groups of slave ECUs and master ECUs are provided, and the list of information collected by the manager ECU from the multiple master ECUs is used to diagnose whether at least a number of slave ECUs are correctly assembled.

[0008] The assembly diagnostic method disclosed herein diagnoses whether at least some ECUs are correctly assembled in a network system for sending and receiving messages between multiple ECUs. The multiple ECUs include slave ECUs, master ECUs, and manager ECUs, with multiple groups of slave and master ECUs. The assembly diagnostic method comprises the following steps: the master ECU turns on a switch located on the power supply line of the slave ECU; the slave ECU is powered on via the switch and starts up, sending a message containing its own identifier; the master ECU, based on the message containing the identifier received from the slave ECU when the switch is turned on, creates a list of information indicating the relationship between the switch and the identifier of the slave ECU; the manager ECU collects the list information from the multiple master ECUs; and based on the list information collected from the multiple master ECUs, diagnoses whether at least a number of slave ECUs are correctly assembled.

[0009] The present disclosure discloses a manager ECU for a network system for sending and receiving messages between multiple ECUs. The multiple ECUs, in addition to the manager ECU, include: slave ECUs that, upon startup, send a message containing their own identifier; and master ECUs that have the function of turning on or off a switch located on the power supply line of the slave ECUs, and that, based on a message containing an identifier received from the slave ECU when the switch is turned on, create a list of relationships between the switch and the identifier of the slave ECU. Multiple sets of slave ECUs and master ECUs are provided. The manager ECU has the function of instructing the multiple master ECUs to create the list of information and the function of collecting the list of information from the multiple master ECUs. The list of information collected by the manager ECU from the multiple master ECUs is used to diagnose whether at least a number of slave ECUs are correctly assembled.

[0010] The present disclosure discloses a master ECU for a network system that transmits and receives messages between multiple ECUs. In addition to the master ECU, the multiple ECUs include slave ECUs and a manager ECU. Upon startup, a slave ECU sends a message containing its own identifier. The master ECU has the following functions: turning a switch on or off a power supply line to the slave ECU; and generating a list of relationships between the switch and the slave ECU's identifier based on a message containing the identifier received from the slave ECU when the switch is turned on. Multiple sets of slave ECUs and master ECUs are provided. The manager ECU collects the list information from the multiple master ECUs. The list information collected by the manager ECU from the multiple master ECUs is used to diagnose whether at least a number of slave ECUs are correctly assembled.

[0011] Based on the aforementioned network system, assembly diagnostic method, manager ECU, and master ECU, in a large-scale network system with multiple sets of slave ECUs and master ECUs, it is possible to collect list information representing the relationships between identifiers of switches and slave ECUs from multiple master ECUs. Therefore, based on the collected list information, it is possible to diagnose whether multiple slave ECUs are correctly assembled for each switch. Furthermore, the diagnosis of whether multiple slave devices are correctly assembled includes not only checking whether the slave ECUs were pre-assigned for assembly, but also checking whether the connections of the slave ECUs to the power supply line and to the communication network are also correctly performed without any malfunctions. Attached Figure Description

[0012] Figure 1 This is a structural diagram showing the overall structure of the assembled diagnostic system of the network system, which includes the implementation methods.

[0013] Figure 2 This is a flowchart illustrating an example of the process performed by the manager ECU to collect list information.

[0014] Figure 3 This is a flowchart illustrating an example of the process performed by the main ECU to create and send list information.

[0015] Figure 4 This is a diagram representing an example of list information.

[0016] Figure 5 It means Figure 3 The flowchart step S220 is an example of the first list creation process.

[0017] Figure 6 It means Figure 3 The flowchart in step S260 is an example of the second list creation process.

[0018] Figure 7This diagram illustrates an example of the format in which the master ECU sends list information to the manager ECU.

[0019] Figure 8 This is a flowchart illustrating an example of a process executed by the ECU. Detailed Implementation

[0020] Hereinafter, embodiments of the network system and assembly diagnostic method of this disclosure will be described with reference to the accompanying drawings. However, this disclosure is not limited to the following embodiments, and various modifications described thereafter are also included within the technical scope of this disclosure. Embodiments and various modifications can be appropriately combined and implemented without creating technical inconsistencies. In the following description, the same or similar structures are sometimes omitted from description by using the same reference numerals in multiple drawings. Furthermore, when only a part of the structure is mentioned, the descriptions in other locations can be applied to other parts.

[0021] (First Implementation) Figure 1 This is a structural diagram showing the overall structure of the assembly diagnostic system 100 including the network system of this embodiment. The assembly diagnostic system 100 of this embodiment can be applied, for example, to an in-vehicle network system built within a vehicle and networked with multiple electronic control units (ECUs). However, the application examples of the assembly diagnostic system 100 of this disclosure are not limited to in-vehicle network systems and can also be applied to other uses. For example, the assembly diagnostic system 100 of this disclosure can be applied to network systems of robots, construction machinery, etc., that include multiple ECUs networked together.

[0022] like Figure 1 As shown, the assembly diagnostic system 100 of this embodiment includes an in-vehicle network system and a diagnostic device 1. The in-vehicle network system includes a manager ECU 10, a master ECU 20, an ECU 30, and first to third slave ECUs 40, 50, and 60. The manager ECU 10 is configured to function as both a manager ECU and a master ECU. The functions of the manager ECU and the master ECU will be described in detail later. However, the manager ECU 10 may not also function as a master ECU, and instead, both a manager ECU and a master ECU may be provided separately. Furthermore, the number of master ECUs 20 and slave ECUs 40, 50, and 60 is not limited to this. Figure 1 The example shown illustrates this. For instance, multiple master ECUs, separate from the manager ECU 10, can be connected to the manager ECU 10. Alternatively, a single master ECU can control the power supply to three or more slave ECUs.

[0023] The manager ECU 10 has a communication circuit 12 and a first relay circuit 14. The first relay circuit 14 includes a first relay switch 16. The first relay switch 16 is located on a power supply line 6 for supplying power to a first slave ECU 40. The master ECU 20 has a communication circuit 22 and a second relay circuit 24. The second relay circuit 24 includes a second relay switch 26 and a third relay switch 28. The second relay switch 26 is located on a power supply line 6 for supplying power to a second slave ECU 50. The third relay switch 28 is located on a power supply line 6 for supplying power to a third slave ECU 60.

[0024] The power supply voltage of the battery 2 installed in the vehicle is supplied to the power supply line 6 via the power circuit 4. The power circuit 4 can convert the power supply voltage of the battery 2 into the operating voltage of the manager ECU 10, main ECU 20, ECU 30, and the first to third slave ECUs 40, 50, and 60 as needed. The first to third slave ECUs 40, 50, and 60 are powered by the power supply line 6 and can operate when the corresponding first to third relay switches 16, 26, and 28 are turned on.

[0025] The first to third relay switches 16, 26, and 28 can be constructed, for example, by semiconductor switches such as MOSFETs and IGBTs. However, the first to third relay switches 16, 26, and 28 may also be constructed by conventional mechanical relays instead of semiconductor switches. Furthermore, the first relay circuit 14 and the second relay circuit 24 can be as follows: Figure 1 It can be installed inside the manager ECU10 and main ECU20 as shown, or it can be installed outside the manager ECU10 and main ECU20.

[0026] The manager ECU 10 and the main ECU 20, as one of the functions of the main ECU, control the presence or absence of power supply to the first to third slave ECUs 40, 50, and 60. This function can be implemented through software such as a power supply control program, or through hardware. More specifically, the manager ECU 10 and the main ECU 20 can determine whether the first to third slave ECUs 40, 50, and 60 need to operate based on signals from sensors and switches (not shown) and / or messages from other ECUs. Furthermore, the manager ECU 10 and the main ECU 20 only activate the first to third relay switches 16, 26, and 28 corresponding to the first to third slave ECUs 40, 50, and 60 when operation of the first to third slave ECUs 40, 50, and 60 is required. Thus, power supply to the first to third slave ECUs 40, 50, and 60 is only performed when operation of the first to third slave ECUs 40, 50, and 60 is required. Conversely, when the operation of the first to third slave ECUs 40, 50, and 60 is not required, the manager ECU 10 and the main ECU 20 disconnect the first to third relay switches 16, 26, and 28 corresponding to the first to third slave ECUs 40, 50, and 60. Thus, when the operation of the first to third slave ECUs 40, 50, and 60 is not required, the power supply to them is cut off. Therefore, the dark current when the operation of the first to third slave ECUs 40, 50, and 60 is not required can be cut off, thereby achieving power saving as a whole in the vehicle network system.

[0027] The communication circuit 12 of the manager ECU 10 and the communication circuit 22 of the master ECU 20 are connected to the communication networks 18, 19, and 29, and are capable of receiving messages from other ECUs, including ECU 30 and the first to third slave ECUs 40, 50, and 60, or sending messages to other ECUs. ECU 30 and the first to third slave ECUs 40, 50, and 60 also have communication circuits 32, 42, 52, and 62, respectively. Communication circuits 32, 42, 52, and 62 have message sending and receiving functions similar to the communication circuit 12 of the manager ECU 10 and the communication circuit 22 of the master ECU 20. Therefore, ECU 30 and the first to third slave ECUs 40, 50, and 60 can also use communication circuits 32, 42, 52, and 62 to send and receive various messages with each ECU connected to the communication networks 18, 19, and 29.

[0028] In communication networks 18, 19, and 29, messages conforming to the CAN (registered trademark, hereinafter the same) protocol can be sent and received. When sending and receiving messages conforming to the CAN protocol, communication circuits 12, 22, 32, 42, 52, and 62 perform reception processing while the message is stored in the receive buffer. This reception processing includes determining whether the received message is illegitimate through format checking, cyclic redundancy checking, etc. Furthermore, communication circuits 12, 22, 32, 42, 52, and 62 only hand over the data and other information contained in the message to the processors of the manager ECU 10, master ECU 20, ECU 30, and the first to third slave ECUs 40, 50, and 60 if the message is determined to be normal.

[0029] In addition, communication circuits 12, 22, 32, 42, 52, and 62, while storing messages to be sent in the transmission buffer, mediate between messages sent from other ECUs and process the transmission of messages to communication networks 18, 19, and 29. The communication protocol is not limited to CAN; other communication protocols such as LIN, FlexRay (registered trademark), and Ethernet (registered trademark) can also be used. Furthermore, different communication protocols can be used for each communication network 18, 19, and 29.

[0030] Furthermore, the communication circuit 12 of the manager ECU 10 and the communication circuit 22 of the main ECU 20 have a relay function for relaying messages between multiple communication networks 18, 19, and 29. The communication circuits 12 and 22 are configured to have a protocol conversion function for relaying messages between communication networks with different communication protocols.

[0031] In addition to the manager ECU 10, main ECU 20, ECU 30, and the first to third slave ECUs 40, 50, and 60, other ECUs (not shown) can be connected to communication networks 18, 19, and 29. The first to third slave ECUs 40, 50, and 60 can be connected to communication networks 19 and 29, or to other communication networks connected to communication networks 19 and 29 via relay devices (not shown). In either case, the manager ECU 10 and main ECU 20 can use communication circuits 12 and 22 to send and receive various messages with the first to third slave ECUs 40, 50, and 60, which are directly or indirectly connected to communication networks 19 and 29.

[0032] When the first slave ECU 40 is assembled in the vehicle, its power port is connected to the power supply line connected to the first relay switch 16 of the first relay circuit 14. Additionally, the communication circuit 42 of the first slave ECU 40 is connected to the communication network 19. When the second slave ECU 50 is assembled in the vehicle, its power port is connected to the power supply line connected to the second relay switch 26 of the second relay circuit 24. Furthermore, the communication circuit 52 of the second slave ECU 50 is connected to the communication network 29. When the third slave ECU 60 is assembled in the vehicle, its power port is connected to the power supply line connected to the third relay switch 28 of the second relay circuit 24. Furthermore, the communication circuit 62 of the third slave ECU 60 is connected to the communication network 29.

[0033] The first to third ECUs 40, 50, and 60 are used, for example, to control various control devices mounted in the vehicle that are controlled by the first to third ECUs 40, 50, and 60 only when specific conditions are met or under specific conditions (e.g., door locking mechanisms, power window drive motors, headlight light sources, wiper motors, AV equipment, etc.). For example, the door locking mechanism is controlled by the ECU for door locking control when a user wants to get into or out of the vehicle. Similarly, the power window drive motor is controlled by the ECU for power window control when the user operates the window lift switch. Furthermore, the first to third ECUs 40, 50, and 60 can also be sensor ECUs that calculate detection results based on sensor detection signals only when specific conditions are met or under specific conditions.

[0034] Thus, the first to third slave ECUs 40, 50, and 60 control, for example, the controlled object devices that operate only under specific conditions or in specific environments. Therefore, in principle, when the operation of the first to third slave ECUs 40, 50, and 60 is required, the manager ECU 10 and the master ECU 20 will connect the first to third relay switches 16, 26, and 28 corresponding to the first to third slave ECUs 40, 50, and 60 to supply power to them. On the other hand, when the operation of the first to third slave ECUs 40, 50, and 60 is not required, the manager ECU 10 and the master ECU 20 will disconnect the first to third relay switches 16, 26, and 28 corresponding to the first to third slave ECUs 40, 50, and 60 to stop supplying power to them.

[0035] As one of the functions of the main ECUs, the manager ECU 10 and the main ECU 20 control the presence or absence of power supply to the first to third slave ECUs 40, 50, and 60, as described above. Additionally, as one of the functions of the manager ECU, the manager ECU 10 collects list information from multiple main ECUs (e.g., the manager ECU 10 and the main ECU 20) that is used in diagnostics to determine whether the first to third slave ECUs 40, 50, and 60 are correctly assembled, representing the relationships between the identifiers of the first to third relay switches 16, 26, and 28 and the first to third slave ECUs 40, 50, and 60. Furthermore, the manager ECU 10 and the main ECU 20 may also control control devices mounted on the vehicle.

[0036] The manager ECU 10, main ECU 20, ECU 30, and first to third slave ECUs 40, 50, and 60 can be configured as a typical computer. Specifically, the manager ECU 10, main ECU 20, ECU 30, and first to third slave ECUs 40, 50, and 60 are equipped with processors such as CPUs and GPUs, volatile memory such as RAM, and storage devices such as ROM and flash memory as non-volatile storage media. Various programs executed by the processor are stored in the storage devices. For example, the storage device of the manager ECU 10 stores a collection program for collecting list information indicating the relationship between the identifiers of the first to third relay switches 16, 26, and 28 and the first to third slave ECUs 40, 50, and 60.

[0037] Furthermore, the storage device of the manager ECU 10 can store the correct correspondence between the identifiers of the first to third relay switches 16, 26, 28 and the identifiers of the first to third slave ECUs 40, 50, 60 for each of the multiple master ECUs. In this case, the manager ECU 10 can act as a diagnostic unit, based on the comparison results between the stored correspondence and the collected list information, to at least diagnose whether the first to third slave ECUs 40, 50, 60 are correctly assembled. However, the manager ECU 10 may also choose not to diagnose whether the assembly is correct, but instead collect list information from the multiple master ECUs and send it to the diagnostic device 1. In this case, the diagnostic device 1, acting as a diagnostic unit, based on the pre-stored correct correspondence between the identifiers of the first to third relay switches 16, 26, 28 and the identifiers of the first to third slave ECUs 40, 50, 60 and the comparison results of the collected list information, to at least diagnose whether the first to third slave ECUs 40, 50, 60 are correctly assembled.

[0038] The diagnostic device 1 is communicatively connected to the manager ECU 10. The diagnostic device 1 instructs the manager ECU 10 to diagnose at least the first to third slave ECUs 40, 50, and 60 for correct assembly or to collect listing information. Based on the instructions from the diagnostic device 1, the manager ECU 10 begins diagnosing whether the assembly is correct or collecting listing information.

[0039] When the manager ECU 10 is instructed to perform diagnostics at least in the first to third stages to check whether the ECUs 40, 50, and 60 are correctly assembled, the manager ECU 10 performs diagnostics and outputs the diagnostic results to the diagnostic device 1. The diagnostic device 1 is equivalent to an external device of this disclosure. At this time, the manager ECU 10 may also output diagnostic results to the diagnostic device 1 and display the diagnostic results on a multimedia display or the like in the vehicle. When the manager ECU 10 is instructed to collect list information, the manager ECU 10 collects list information from multiple master ECUs and sends the collected list information to the diagnostic device 1.

[0040] Here, given the different types of controlled devices and sensors used to process the detection results by the first to third slave ECUs 40, 50, and 60, the timing of when the manager ECU 10 and the main ECU 20 begin and stop supplying power to each of the first to third slave ECUs 40, 50, and 60 may differ. Therefore, the first to third relay switches 16, 26, and 28 that should be connected to each of the first to third slave ECUs 40, 50, and 60 are predetermined. Figure 1 In the example shown, a first relay switch 16 is pre-connected from ECU 40 to a first relay circuit 14. A second relay switch 26 is pre-connected from ECU 50 to a second relay circuit 24. A third relay switch 28 is pre-connected from ECU 60 to the second relay circuit 24.

[0041] Therefore, the first to third slave ECUs 40, 50, and 60 need to be correctly connected to the power supply line via their respective first to third relay switches 16, 26, and 28, without being confused with other types of slave ECUs. Furthermore, the communication circuits 42, 52, and 62 of each of the first to third slave ECUs 40, 50, and 60 also need to be correctly connected to the communication networks 19 and 29 to enable communication with the communication circuit 12 of the manager ECU 10 or the communication circuit 22 of the master ECU 20.

[0042] However, during the assembly operations of connecting the first to third ECUs 40, 50, and 60 to the power supply line and to the communication network, the possibility of incorrectly assembling an ECU other than the intended one is not zero. Furthermore, the assembly operations of the first to third ECUs 40, 50, and 60 are not always performed correctly; there is a possibility that malfunctions may occur during the assembly operations. These malfunctions include poor connections to the power supply line and poor connections to the communication networks 19 and 29.

[0043] Therefore, in this embodiment, as described above, the manager ECU 10 is configured to collect list information from multiple master ECUs representing the correspondence between identifiers of the first to third relay switches 16, 26, 28 and the first to third slave ECUs 40, 50, 60. Thus, the manager ECU 10 or the diagnostic device 1 can, based on the collected list information, diagnose at least whether the first to third slave ECUs 40, 50, 60, which are intended to be connected to the first to third relay switches 16, 26, 28, are correctly assembled.

[0044] Figure 2 This is a flowchart illustrating an example of the process performed by the manager ECU10 to collect list information. Execution Figure 2 The process shown in the flowchart is equivalent to the manager ECU 10 performing its function as a manager ECU. Furthermore, in Figure 2 The flowchart illustrates an example where the manager ECU10 also acts as a diagnostic unit, performing at least a diagnostic check to determine whether the first to third processes from ECUs 40, 50, and 60 have been correctly assembled.

[0045] In step S100, the manager ECU 10 at least determines whether to initiate diagnostics to determine whether the first to third slave ECUs 40, 50, and 60 are correctly assembled. In this step S100, for example, a positive determination is made if the manager ECU 10 receives a diagnostic instruction from the diagnostic device 1, and a negative determination is made if no diagnostic instruction is received. If a positive determination is made, the manager ECU 10 proceeds to step S110.

[0046] In step S110, the manager ECU 10 instructs each master ECU to create list information. This list information creation instruction is sent not only to the master ECU 20 but also transmitted within the manager ECU 10 to the master ECU functional units that function as master ECUs. In step S120, the manager ECU 10 determines whether the predetermined time required to complete the list information creation in each master ECU has elapsed since the instruction to create the list information. If the predetermined time has elapsed, the manager ECU 10 proceeds to step S130. Furthermore, the list information creation process in each master ECU will be described in detail later.

[0047] In step S130, the manager ECU 10 instructs each master ECU to send the created list information. Each master ECU contains a master ECU functional unit that functions as a master ECU within the manager ECU 10. According to this instruction, each master ECU sends the created list information to the manager ECU 10. In step S140, the manager ECU 10 receives the list information sent from each master ECU according to the list information sending instruction.

[0048] In step S150, the manager ECU 10 compares the correspondence between the identifiers of the first to third relay switches 16, 26, 28 and the first to third slave ECUs 40, 50, 60 with the collected list information for each of the plurality of master ECUs. In step S160, the manager ECU 10 determines whether the comparison is OK or NG (incorrect) based on the comparison result in step S150. If the comparison is determined to be OK, the manager ECU 10 proceeds to step S170. On the other hand, if the comparison is determined to be NG, the manager ECU 10 proceeds to step S180. Furthermore, the comparison process between the identifiers of the first to third relay switches 16, 26, 28 and the first to third slave ECUs 40, 50, 60 in the manager ECU 10 and the collected list information will be explained in detail later.

[0049] In step S170, the manager ECU 10 diagnoses that all ECUs are correctly assembled. On the other hand, the manager ECU 10 diagnoses that at least one of the ECUs, including the first through third ECUs 40, 50, and 60, is not correctly assembled. In step S190, the manager ECU 10 sends the diagnostic result to the diagnostic device 1.

[0050] Furthermore, if the manager ECU 10 does not perform at least the first to third diagnostic processes to determine whether ECUs 40, 50, and 60 are correctly assembled, steps S160 to S180 are omitted. In this case, the manager ECU 10 sends the list information collected from the multiple master ECUs to the diagnostic device 1 in step S190.

[0051] Next, refer to Figure 3 The flowchart illustrates an example of the processing performed by the main ECU 20 to create and send list information. Figure 3 The processing shown in the flowchart is also performed by the main ECU function unit in the manager ECU 10, which acts as the main ECU. The following explains the execution by the main ECU 20. Figure 3 The flowchart shows an example of the processing.

[0052] In step S200, the main ECU 20 determines whether it has received a list information creation instruction from the manager ECU 10. If it determines that a list information creation instruction has been received, the main ECU 20 proceeds to step S210. In step S210, the main ECU 20, for example, clears... Figure 4 The content of the list information is shown. Therefore, the main ECU 20 can recreate the list information.

[0053] List information generated by main ECU20, such as Figure 4 As shown, the list information includes the correspondence between "relay disconnected" when both the second and third relay switches 26 and 28 are disconnected and the identifier indicating the sending source contained in the message received by the main ECU 20. Furthermore, the created list information includes the correspondence between "second relay switch" when the second relay switch 26 is turned on and the third relay switch 28 is turned off and the identifier indicating the sending source contained in the message received by the main ECU 20, which is different from "relay disconnected". Also, the created list information includes the correspondence between "third relay switch" when the second relay switch 26 is turned off and the third relay switch 28 is turned on and the identifier indicating the sending source contained in the message received by the main ECU 20, which is different from "relay disconnected".

[0054] Additionally, in step S210, the main ECU 20 begins periodically sending wake-up messages to other ECUs communicatively connected to it via the communication network 18, etc. When other ECUs are configured to switch between sleep and start states, they become start states upon receiving the wake-up message. The start states ECUs then repeatedly send messages containing their own identifier as the source at predetermined intervals.

[0055] Furthermore, in step S210, the main ECU 20 stores the states (on or off) of the second and third relay switches 26 and 28, and then disconnects all of them. By storing the states (on or off) of the second and third relay switches 26 and 28, the main ECU 20 can restore the states of the second and third relay switches 26 and 28 to the stored states after the list information is created. Additionally, by disconnecting all of the second and third relay switches 26 and 28, the main ECU 20 can receive messages from other ECUs corresponding to the aforementioned "relay disconnection".

[0056] In addition, in step S210, the master ECU 20 stops the relay function of the communication circuit 22. Therefore, even if the master ECU 20 receives a message from the second slave ECU 50, for example, by turning on the second relay switch 26, it can prevent that message from being relayed to other ECUs. As a result, it is possible to prevent messages from the second slave ECU 50 from affecting the list creation processing in other master ECUs.

[0057] In step S220, the main ECU 20 performs a first list creation process based on the received message to create a list of communication nodes representing the correspondence between the identifiers of the aforementioned "relay disconnection" and other ECUs. Figure 5 The flowchart illustrates an example of the first list creation process. See below for reference. Figure 5 The flowchart illustrates the details of the first list creation and processing.

[0058] In step S400, the main ECU 20 starts a timer. The timer is used to determine the reception period for messages from other ECUs. This reception period is set to be sufficiently long than the message transmission interval in the other ECUs. And, as described later, if the timer times out after a predetermined period, the main ECU 20 stops receiving messages. Thus, for example, even if the main ECU 20 is unable to receive messages from other ECUs due to poor communication circuit connections, the first list creation process can still proceed.

[0059] In step S410, the main ECU 20 determines whether it has received a message from another ECU. If it determines that a message has been received, the main ECU 20 proceeds to step S420. On the other hand, if it determines that no message has been received, the main ECU 20 proceeds to step S440.

[0060] In step S420, the main ECU 20 obtains the identifier representing the sending source contained in the received message. Then, in step S430, the main ECU 20 appends the obtained identifier to the communication node list. The communication node list is equivalent to... Figure 4 The list shown represents the correspondence between "relay disconnected" and other ECU identifiers.

[0061] In step S440, the main ECU 20 determines whether the timer has timed out. If it determines that the timer has not timed out, the main ECU 20 repeats the processing that started from step S410. On the other hand, if it determines that the timer has timed out, the main ECU 20 terminates the process. Figure 5 The process shown in the flowchart proceeds to... Figure 3 Step S230 of the flowchart.

[0062] exist Figure 4In step S230 of the flowchart, the main ECU 20 clears the variable N, which is used to specify the number of the relay switch to be turned on. Then, in step S240, the main ECU 20 increments the value of variable N by 1. In step S250, the main ECU 20 turns on the Nth relay switch and turns off the other relay switches. For example, in... Figure 1 In the example shown, when N is 1, the second relay switch 26, as the Nth relay switch, is turned on, and the third relay switch 28, as another relay switch, is turned off. Conversely, when N is 2, the third relay switch 28, as the second relay switch, is turned on, and the second relay switch 26, as another relay switch, is turned off.

[0063] Thus, when the main ECU 20 has the function of turning multiple second and third relay switches 26 and 28 on or off, the main ECU 20 turns on the multiple second and third relay switches 26 and 28 one by one in sequence. As a result, the main ECU 20 can supply power to the slave ECUs connected to the turned-on relay switches to start them. After starting, the slave ECUs send a message containing their own identifier as the transmission source. Therefore, if the slave ECUs are correctly assembled, including connections to the power supply line and the communication network, the main ECU 20 can obtain the identifiers of the slave ECUs connected to the turned-on relay switches. Furthermore, the main ECU 20 can create a list indicating the correspondence between the identifiers of each relay switch and the identifiers of the slave ECUs based on the obtained slave ECU identifiers.

[0064] In step S260, the master ECU 20 performs a second list creation process to create a list representing the correspondence between the identifiers of each relay switch and the slave ECU. Figure 6 The flowchart illustrates an example of the second list creation process. See below for reference. Figure 6 The flowchart illustrates the details of the second list creation process.

[0065] Figure 6 The flowchart describes the processing steps S500 to S520 and the processing step S550. Figure 5 The steps S400 to S420 of the flowchart are the same as those in S440, so the explanation is omitted.

[0066] exist Figure 6In step S530 of the flowchart, the master ECU 20 determines whether the identifier obtained in step S520 is an identifier that does not exist in the communication node list. When the identifier obtained in step S520 is an identifier that exists in the communication node list, this identifier is not the identifier of the slave ECU connected to the connected relay circuit. Therefore, the master ECU 20 skips the processing of step S540 and proceeds to the processing of step S550. On the other hand, when the identifier obtained in step S520 is an identifier that does not exist in the communication node list, it can be said that this identifier is the identifier of the slave ECU connected to the connected relay circuit. In this case, the master ECU proceeds to step S540, as follows... Figure 4 As shown in the list information, the acquired identifier is appended to the list corresponding to the Nth relay switch that has been turned on. Furthermore, if multiple slave ECUs are connected to the Nth relay switch, the list contains identifiers for multiple slave ECUs.

[0067] Return again Figure 3 The flowchart will be explained further. In step S270, the main ECU 20 determines whether the value of variable N is less than the number of relay switches. When it is determined that the value of variable N is less than the number of relay switches, the main ECU 20 returns to step S240 and repeats the above process. On the other hand, when it is determined that the value of variable N reaches the number of relay switches, the main ECU 20 proceeds to step S280. Furthermore, at this point in time, the main ECU 20 completes... Figure 4 To create a list of information as shown.

[0068] In step S280, the main ECU 20 stops periodically sending wake-up messages. Additionally, the main ECU 20 restores the states of the second and third relay switches 26 and 28 to their stored states. Furthermore, the main ECU 20 releases the stoppage of the relay function of the communication circuit 22, restoring the relay function of the communication circuit 22.

[0069] In step S290, the main ECU 20 determines whether it has received a list information transmission instruction from the manager ECU 10. If it is determined that a list information transmission instruction has been received, the main ECU 20 proceeds to step S300. In step S300, the main ECU 20 sends the created list information to the manager ECU 10.

[0070] Figure 7This is an example of the transmission format for the list information sent by the master ECU 20 to the manager ECU 10. The transmission format includes an identifier for the master ECU 20, the value obtained by adding 1 to the number of relay switches, the size of the identifier data corresponding to "relay off", the data representing the identifier corresponding to "relay off", the size of the identifier data corresponding to the first relay switch, and the data representing the identifier corresponding to the first relay switch, etc.

[0071] The transmission format includes a value obtained by adding 1 to the number of relay switches in order to transmit an identifier corresponding to "relay open" in addition to the identifier corresponding to each relay switch. Furthermore, the transmission format includes the size of the identifier data corresponding to relay open and the size of the identifier data corresponding to the first relay switch in order to determine the data portion representing the identifier corresponding to relay open and the data portion representing the identifier corresponding to the first relay switch within the transmission format.

[0072] For example, in the sending format, such as Figure 7 As shown, the data portion representing the identifier corresponding to the relay disconnection can include the relay switch number, the number of identifiers, and the identifier obtained. Figure 7 In this context, the acquired identifiers are represented by NAD1, NAD2, and NAD3. Furthermore, when the relay is open, the relay switch number becomes a specific value indicating that the relay is open. The data portion representing the identifier corresponding to the first relay switch also has the same structure as the data portion representing the identifier corresponding to the relay being open.

[0073] Here, the comparison processing performed by the manager ECU 10 or diagnostic device 1 will be described. As described above, the manager ECU 10 or diagnostic device 1 stores the correct correspondence between the identifiers of the first to third relay switches 16, 26, 28 and the identifiers of the first to third slave ECUs 40, 50, 60 for each of the plurality of master ECUs. Furthermore, the list information of each master ECU collected by the manager ECU 10 from the plurality of master ECUs includes the correspondence between at least one relay switch and the identifier of the slave ECU connected to that relay switch.

[0074] Therefore, the manager ECU 10 or diagnostic device 1 can compare the identifier of the slave ECU corresponding to the relay switch in the correct correspondence stored for each master ECU with the identifier of the slave ECU corresponding to the relay switch contained in the acquired list information. In this comparison, if the identifiers of the slave ECUs corresponding to the relay switches are consistent with each other, it can be considered that the predetermined connected slave ECUs have not been confused with other types of slave ECUs and have been correctly assembled. Thus, according to this embodiment, the manager ECU 10 or diagnostic device 1 can diagnose whether multiple slave ECUs have been correctly assembled based on the list information collected by the manager ECU 10 from multiple master ECUs.

[0075] Furthermore, the manager ECU 10 or diagnostic device 1 can also diagnose whether the main ECUs 20 and ECU 30, which are not from the main ECUs, are correctly assembled based on the list information collected by the manager ECU 10 from multiple main ECUs. The reason for this is explained below.

[0076] When multiple master ECUs send list information to the manager ECU 10, the sending format includes an identifier of the master ECU indicating the sending source. Therefore, the manager ECU 10 or the diagnostic device 1 can diagnose that the master ECU is not correctly assembled if the list information obtained from each master ECU contains the identifier of a master ECU that is not pre-connected, or if the identifier of the master ECU does not match the identifier of the slave ECU corresponding to the relay switch when comparing each master ECU with the identifier of the slave ECU.

[0077] Furthermore, when multiple master ECUs send list information to the manager ECU 10, the format of the transmission includes the identifier of the ECU corresponding to the relay disconnection. Therefore, the manager ECU 10 or the diagnostic device 1 can diagnose that the ECU connected when the relay disconnected was not correctly assembled if the identifier of the ECU corresponding to the relay disconnection does not match the identifier of the ECU that was intended to be connected when the relay disconnected.

[0078] Finally, refer to Figure 8 The flowchart below illustrates an example of the processing executed by the first through third ECUs 40, 50, and 60. The following describes the processing executed by the first ECU 40. Figure 8 The flowchart illustrates an example of the processing.

[0079] In step S600, the first relay switch 16 connected to the first slave ECU 40 is turned on by the manager ECU 10, thereby starting the power supply to the first slave ECU 40. In step S610, the first slave ECU 40 executes a startup process. This startup process includes, for example, the initialization of various variables and the startup of various programs. Furthermore, if the startup process is complete, the first slave ECU 40 sends a message containing its own identifier in step S620. This message is sent periodically until the first slave ECU 40 determines that the power supply has stopped in step S630.

[0080] (Modified Example) The preferred embodiments of this disclosure have been described above, but this disclosure is not limited to any of the above embodiments and can be implemented in various ways without departing from the spirit of this disclosure.

[0081] For example, the manager ECU 10 can send list information creation instructions to each master ECU simultaneously, or it can send them sequentially to each master ECU in a predetermined order. However, even when sending list information creation instructions to each master ECU sequentially, it is preferable to send a stop instruction for the relay function of the communication circuit in advance. This ensures that each master ECU is unaffected by messages from slave ECUs when performing list information creation processing.

[0082] Furthermore, in the above embodiment, an example of the slave ECU starting up in response to the start of power supply was described. However, the slave ECU may also start up in response to the receipt of a wake-up message periodically sent by the master ECU after the start of power supply.

[0083] Furthermore, the systems, methods, and ECUs described in this disclosure can also be implemented using a dedicated computer, which constitutes a processor programmed to perform one or more functions embodied in a computer program. The systems, methods, and ECUs described in this disclosure can also be implemented using dedicated hardware logic circuits. The systems, methods, and ECUs described in this disclosure can also be implemented using one or more dedicated computers composed of a processor executing a computer program and one or more hardware logic circuits. For example, some or all of the functions of the manager ECU 10 and the main ECU 20 can also be implemented as hardware. Implementing a function as hardware includes using one or more ICs, etc. The processor (processor core) can be an MPU, GPU, DFP (Data Flow Processor), etc., in addition to a CPU. Some or all of the functions of the manager ECU 10 and the main ECU 20 can also be implemented using one of a System-on-Chip (SoC), an Integrated Circuit (IC), and a Field-Programmable Gate Array (FPGA). The concept of IC also includes Application Specific Integrated Circuit (ASIC). Furthermore, the computer program can be stored as instructions to be executed by the computer on a computer-readable, non-transitory tangible storage medium. The recording medium for the program can be an HDD (Hard-disk Drive), an SSD (Solid State Drive), flash memory, or the like. Additionally, the scope of this disclosure also includes non-transitory physical recording media such as the program used to enable the computer to function as the manager ECU10 and the main ECU20, and a semiconductor memory storing that program.

Claims

1. A network system for sending and receiving messages among multiple ECUs, characterized in that, The plurality of said ECUs have: At startup, the ECU sends a message containing its own identifier. The master ECU has the function of turning on or off a switch located on the power supply line of the slave ECU, and creates a list of information representing the relationship between the switch and the identifier of the slave ECU based on a message containing an identifier received from the slave ECU when the switch is turned on. as well as The manager ECU collects the list information from multiple said master ECUs. The slave ECU and the master ECU are provided with multiple sets. The list information collected by the manager ECU from the multiple master ECUs is used to diagnose whether at least a number of the slave ECUs are correctly assembled.

2. The network system according to claim 1, characterized in that, The manager ECU diagnoses whether at least a plurality of the slave ECUs are correctly assembled.

3. The network system according to claim 2, characterized in that, The manager ECU, for each of the plurality of master ECUs, pre-stores the relationship between the switch and the identifier of the slave ECU, and diagnoses whether at least a plurality of the slave ECUs are correctly assembled based on the comparison results of the stored relationship with the list information collected from the plurality of master ECUs.

4. The network system according to claim 2 or 3, characterized in that, The manager ECU sends the diagnostic results to an external device.

5. The network system according to any one of claims 1 to 3, characterized in that, The manager ECU instructs multiple master ECUs to create the list information.

6. The network system according to claim 5, characterized in that, Multiple master ECUs have message relay functions. The multiple master ECUs correspond to the relay function of the message that is instructed to create the list information and stop the message.

7. The network system according to claim 5, characterized in that, When the plurality of master ECUs receive the list information creation instruction through the manager ECU, they store the state of the switch at the time the creation instruction was received, and restore the stored state of the switch after the list information creation is completed.

8. The network system according to claim 5, characterized in that, When the master ECUs receive the list information creation instruction from the manager ECU, they respectively disconnect the switch and receive messages containing identifiers sent from other ECUs, and create a list of identifiers of other ECUs that are communicatively connected to themselves and are connected to the power supply line of the switch.

9. The network system according to any one of claims 1 to 3, characterized in that, At least one of the plurality of main ECUs has the function of turning the plurality of switches on or off. The at least one master ECU obtains the identifiers of the slave ECUs connected to the power supply lines of the switched switches by sequentially turning on the multiple switches one by one, and creates a list of information representing the relationship between the identifiers of the multiple switches and the slave ECUs.

10. An assembly diagnostic method for diagnosing whether at least a portion of the ECUs are correctly assembled in a network system for sending and receiving messages among multiple ECUs, characterized in that, The plurality of ECUs includes a slave ECU, a master ECU, and a manager ECU. The slave ECU and the master ECU are provided with multiple sets. The assembly diagnostic method includes the following steps: The main ECU will turn on the switch on the power supply line of the slave ECU; The ECU is powered via the switch to start and sends a message containing its own identifier; The master ECU generates a list of information representing the relationship between the switch and the identifier of the slave ECU based on a message containing an identifier received from the slave ECU when the switch is turned on. The manager ECU collects the list information from multiple master ECUs; as well as Based on the list information collected from the multiple master ECUs, a diagnosis is made as to whether at least a multiple of the slave ECUs are correctly assembled.

11. A manager ECU for a network system for sending and receiving messages among multiple ECUs, characterized in that, In addition to the manager ECU, the plurality of ECUs also include: From the ECU, at startup, a message containing its own identifier is sent; and The master ECU has the function of turning a switch on or off the power supply line of the slave ECU. Based on a message containing an identifier received from the slave ECU when the switch is turned on, the master ECU creates a list of information indicating the relationship between the switch and the identifier of the slave ECU. The slave ECU and the master ECU are provided with multiple sets. The manager ECU has the function of instructing multiple master ECUs to create the list information, and the function of collecting the list information from multiple master ECUs. The list information collected by the manager ECU from the multiple master ECUs is used to diagnose whether at least a number of the slave ECUs are correctly assembled.

12. A master ECU for a network system of sending and receiving messages among multiple ECUs, characterized in that, In addition to the main ECU, the plurality of ECUs also include slave ECUs and manager ECUs. The ECU sends a message containing its own identifier during startup. The main ECU has: The function of turning the switch on or off is set on the power supply line from the ECU; as well as Based on a message containing an identifier received from the slave ECU when the switch is turned on, this function generates a list of information representing the relationship between the switch and the identifier of the slave ECU. The slave ECU and the master ECU are provided with multiple sets. The manager ECU collects the list information from multiple master ECUs. The list information collected by the manager ECU from the plurality of master ECUs is used to diagnose whether at least the plurality of slave ECUs are properly assembled.

Citation Information

Patent Citations

  • Vibration recorder

    JP1981039425A