Inspection device and inspection system

Abstract

The inspection device (2) has a decision section (S20-S30), a conduction control section (S40), an information acquisition section (S60), a storage section (13), and a connection inspection section (S70). The decision section decides whether to set the power supply switching section (14, 15) to the on state or to the off state. The conduction control section sets the power supply switching section to the on state or to the off state individually in compliance with the decision made by the decision section. The information acquisition section acquires first verification information for verifying whether the connection load is connected to the power supply switching section after the power supply switching section becomes the on state. The storage section stores second verification information. The connection inspection section performs connection inspection of judging whether the connection load is connected to the power supply switching section by comparing the first verification information and the second verification information.

Description

[0001] Cross-reference of related applications

[0002] This international application claims the benefit of Japanese Patent Application No. 2024-026697, filed with the Japan Patent Office on February 26, 2024, the entire disclosure of which is incorporated herein by reference. Technical Field

[0003] This disclosure relates to an inspection apparatus and inspection system for performing connectivity checks. Background Technology

[0004] Patent document 1 describes a method for checking the connection of an external connector by inserting a pin for connection inspection into a through hole in an external connector housing when the inner connector housing and the outer connector housing are in a semi-fitted state.

[0005] Previously, in the manufacturing process of electronic control systems, connection checks to confirm whether the specified device was connected to the electronic control device were carried out using specialized machines.

[0006] Existing technical documents

[0007] Patent documents

[0008] Patent document 1: Japanese Patent Application Publication No. 2006-73329. Summary of the Invention

[0009] As a result of the inventor's detailed investigation, it was discovered that the need to use a special machine for connection checks is the cause of the reduced efficiency of connection checks.

[0010] This disclosure improves the efficiency of connection checking.

[0011] One embodiment of this disclosure is an inspection device comprising a decision unit, a conduction control unit, an information acquisition unit, a storage unit, and a connection inspection unit.

[0012] The decision unit is configured to determine whether to set each of the one or more power supply switching units to an on state or an off state. The one or more power supply switching units are configured to switch between an on state that enables each of the one or more power supply paths that supply power from the power source to the one or more connected loads to be on and an off state that disables the power supply path.

[0013] The conduction control unit is configured to set each of one or more power supply switching units to an on or off state according to the decision made by the decision unit.

[0014] The information acquisition unit is configured such that, for each of the one or more power supply switching units, after the power supply switching unit becomes in the on state, it acquires first verification information for verifying whether the connected load is connected to the power supply switching unit.

[0015] The storage unit stores second verification information used for the connection verification.

[0016] The connection checking unit is configured to perform a connection check to determine whether one or more of the connected loads are connected to the power supply switching unit by comparing first verification information and second verification information for each of the one or more power supply switching units.

[0017] The inspection apparatus of this disclosure, configured in this way, can perform connection inspections without the use of dedicated machines, thus improving the efficiency of connection inspection work.

[0018] Another aspect of this disclosure is an inspection system comprising one or more power supply switching units and an inspection device configured to control the operation of the one or more power supply switching units. The inspection device includes a decision unit, a conduction control unit, an information acquisition unit, and a connection inspection unit.

[0019] The inspection system of this disclosure, as thus constructed, is a system equipped with the inspection device of this disclosure and can achieve the same effect as the inspection device of this disclosure. Attached Figure Description

[0020] Figure 1 This is a block diagram illustrating the structure of the vehicle control system according to the first embodiment.

[0021] Figure 2 This is a diagram showing the construction of the connection checklist of the first embodiment.

[0022] Figure 3 This is a flowchart illustrating the connection check process of the first embodiment.

[0023] Figure 4 This is a block diagram illustrating the structure of the vehicle control system according to the second embodiment.

[0024] Figure 5 This is a diagram illustrating the construction of the connection checklist according to the second embodiment.

[0025] Figure 6 This is a flowchart illustrating the connection check process of the second embodiment.

[0026] Figure 7 This is a block diagram illustrating the structure of the vehicle control system according to the third embodiment.

[0027] Figure 8 This is a diagram showing the structure of the communication connection checklist according to the third embodiment.

[0028] Figure 9 This is a flowchart illustrating the communication connection check process of the third embodiment.

[0029] Figure 10 This is a block diagram illustrating the structure of the vehicle control system according to the fourth embodiment.

[0030] Figure 11 This is a diagram showing the construction of the connection checklist according to the fourth embodiment.

[0031] Figure 12 This is a flowchart illustrating the connection check process of the fourth embodiment.

[0032] Figure 13 This is a diagram showing the construction of the connection checklist according to the fifth embodiment.

[0033] Figure 14 This is a flowchart illustrating the connection check process of the fifth embodiment.

[0034] Figure 15 This is a block diagram illustrating the structure of the vehicle control system according to the sixth embodiment.

[0035] Figure 16 This is an explanatory diagram illustrating the associated information and startup information.

[0036] Figure 17 This is a diagram showing the correspondence between controlled objects and groups.

[0037] Figure 18 This is a block diagram showing the structure of the vehicle control system according to the seventh embodiment.

[0038] Figure 19 This is a block diagram showing the structure of the central ECU and upstream power distribution unit in the seventh embodiment.

[0039] Figure 20 This is a first block diagram illustrating the structure of the regional ECU according to the seventh embodiment.

[0040] Figure 21 This is a second block diagram illustrating the structure of the regional ECU according to the seventh embodiment.

[0041] Figure 22 This is a block diagram illustrating the construction of the ECU according to the seventh embodiment.

[0042] Figure 23 This is a diagram showing the structure of the start table according to the seventh embodiment.

[0043] Figure 24 This is a diagram showing the construction of the connection checklist according to the seventh embodiment.

[0044] Figure 25 This is a flowchart illustrating the connection check process of the seventh embodiment.

[0045] Figure 26 This is a diagram showing the structure of the start table according to the eighth embodiment.

[0046] Figure 27 This is a first block diagram illustrating the structure of the regional ECU according to the eighth embodiment.

[0047] Figure 28 This is a second block diagram illustrating the structure of the regional ECU according to the eighth embodiment.

[0048] Figure 29 This is a diagram showing the construction of the connection checklist according to the eighth embodiment.

[0049] Figure 30 This is a flowchart illustrating the connection check process of the eighth embodiment.

[0050] Figure 31 This is a block diagram illustrating the structure of the vehicle control system according to the ninth embodiment.

[0051] Figure 32 This is a diagram showing the structure of the communication connection checklist according to the ninth embodiment.

[0052] Figure 33 This is a flowchart illustrating the communication connection check process of the ninth embodiment. Detailed Implementation

[0053] [First Implementation Method]

[0054] The following and appendix Figure 1 The first embodiment of this disclosure will now be described.

[0055] In this embodiment, the vehicle control system 1 is mounted on a vehicle, such as... Figure 1 As shown, it includes a main ECU2, slave ECUs 3, 4, and 5, and a battery 7. ECU is an abbreviation for Electronic Control Unit.

[0056] The main ECU2 and the slave ECUs 3, 4, and 5 are connected via communication bus 8 in a manner that enables them to communicate with each other.

[0057] Battery 7 supplies power to various parts of the vehicle with DC battery voltage (e.g., 12V). The main ECU 2 and slave ECUs 3-5 operate by receiving power from battery 7.

[0058] The main ECU2 includes a control unit 11, a CAN communication unit 12, a storage unit 13, electronic fuses 14 and 15, and a current detection unit 16. CAN is an abbreviation for Controller Area Network. CAN is a registered trademark.

[0059] The control unit 11 is an electronic control device centered on a microcomputer, including a CPU 21, ROM 22, and RAM 23. Various functions of the microcomputer are implemented by the CPU 21 executing programs stored on a non-transient physical recording medium. In this example, the ROM 22 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 21 via hardware. Additionally, the number of microcomputers constituting the control unit 11 can be one or more.

[0060] The CAN communication unit 12 communicates with the slave ECUs 3, 4, and 5 connected to the communication bus 8 by sending and receiving communication frames based on the CAN communication protocol.

[0061] Storage unit 13 is a storage device used to store various types of data. Storage unit 13 stores connection checklist 25, which will be described later.

[0062] Electronic fuse 14 is configured on power supply path 9 between battery 7 and ECU 3. Electronic fuse 15 is configured on power supply path 10 between battery 7 and ECU 4.

[0063] Electronic fuses 14 and 15 include a switching element (e.g., a MOSFET) and a control circuit. The control circuit of electronic fuses 14 and 15 is configured to disconnect power supply paths 9 and 10 by switching the switching element from the on state to the off state when the current flowing through power supply paths 9 and 10 exceeds a preset overcurrent threshold.

[0064] The control circuits of electronic fuses 14 and 15 are configured to, in accordance with instructions from the control unit 11, connect or disconnect the power supply paths 9 and 10 by setting the switching elements to an on or off state.

[0065] The control circuits of electronic fuses 14 and 15 measure the current flowing through electronic fuses 14 and 15 (i.e., the current flowing through power supply paths 9 and 10), and are configured to output current value information showing the measured current values ​​to the main ECU 2. The current values ​​shown in the current value information output by electronic fuses 14 and 15 are respectively equivalent to the current consumed from ECUs 3 and 4 (hereinafter referred to as consumed current values).

[0066] The current detection unit 16 is configured to detect the current value flowing through the power supply paths 9 and 10, and output the power supply path current value information showing the detected current value to the main ECU 2.

[0067] ECUs 3 to 5 each include a control unit 31, a CAN communication unit 32, and a storage unit 33.

[0068] The control unit 31 is an electronic control device centered on a microcomputer including a CPU 41, ROM 42, and RAM 43. Various functions of the microcomputer are implemented by the CPU 41 executing programs stored on a non-transient physical recording medium. In this example, the ROM 42 is equivalent to a non-transient physical recording medium storing the program. Furthermore, through the execution of this program, methods corresponding to the program are executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 41 via hardware. Additionally, the number of microcomputers constituting the control unit 31 can be one or more.

[0069] The CAN communication unit 32 of ECU3 to 5 communicates with the communication devices (i.e., master ECU2 and slave ECU3 to 5) connected to the communication bus 8 based on the CAN communication protocol.

[0070] Storage unit 33 is a storage device used to store various types of data.

[0071] A vehicle diagnostic device 90 (so-called a diagnostic tester) is connected to the main ECU2. The diagnostic device 90 is installed in vehicle dealerships and repair shops, etc.

[0072] The fault diagnosis device 90 is configured to be detachable via a connector (not shown) and connected to the main ECU 2 during fault diagnosis. The fault diagnosis device 90 can obtain various information from the main ECU 2 and slave ECUs 3, 4, and 5 via the main ECU 2, or can update the data stored in the main ECU 2 and slave ECUs 3, 4, and 5.

[0073] like Figure 2 As shown, the connection checklist 25 sets the electronic fuse ID, connected load category, and desired current consumption value (hereinafter referred to as desired current consumption value) for each of the multiple electronic fuses 14 and 15 provided in the vehicle control system 1. The connected load category is the category of the load connected to the electronic fuse that is the object. Examples of connected load categories include ECU, sensors, and actuators.

[0074] In the connection checklist 25 of this embodiment, for electronic fuse 14, the electronic fuse ID is set to "eFuse_1", the connected load category is set to "ECU", and the expected current consumption value is set to "500mA". For electronic fuse 15, the electronic fuse ID is set to "eFuse_2", the connected load category is set to "ECU", and the expected current consumption value is set to "200mA".

[0075] Next, the sequence of connection check processes performed by the control unit 11 of the main ECU2 will be explained. The connection check process is a process that is repeatedly performed during the startup of the main ECU2.

[0076] When the connection check process is executed, the CPU 21 of the control unit 11, as follows: Figure 3 As shown, in S10, it is determined whether the main ECU2 is set to connection check mode. The control unit 11 of the main ECU2 is configured to set the main ECU2 to connection check mode when it receives a connection check command from the fault diagnosis device 90.

[0077] Here, if the main ECU2 is not set to connection check mode, CPU21 proceeds to S100. On the other hand, if the main ECU2 is set to connection check mode, CPU21 sets the electronic fuse indicator value i set in RAM23 to 0 in S20.

[0078] In S30, CPU21 increments the electronic fuse indicator value i (i.e., adds 1).

[0079] In S40, CPU21 sets the i-th electronic fuse (i.e., the electronic fuse whose electronic fuse ID is set as "eFuse_i") to the ON state.

[0080] In S50, CPU21 has a pre-set standby time for the on-state.

[0081] In S60, CPU21 obtains current value information from the i-th electronic fuse.

[0082] In S70, CPU21 performs a connection check on the i-th electronic fuse. Specifically, if the current value shown in the current value information obtained from S60 is above the connection determination value, CPU21 determines it to be "connected"; if the current value shown in the current value information obtained from S60 is below the connection determination value, it determines it to be "not connected". The connection determination value is obtained by multiplying the expected current consumption value of the i-th electronic fuse by a preset connection check ratio. The connection check ratio is, for example, 0.1. For example, since the expected current consumption value of the first electronic fuse is 500mA, the connection determination value of the first electronic fuse is 500 × 0.1 = 50 [mA].

[0083] In S80, CPU21 stores the connection check result (i.e., the connection check result at S70) in storage unit 13 for the i-th electronic fuse.

[0084] In S90, CPU21 determines whether the electronic fuse indicator value i is greater than or equal to the preset total number of electronic fuses n (2 in this embodiment). If the electronic fuse indicator value i is less than the total number of electronic fuses n, CPU21 proceeds to S30.

[0085] On the other hand, when the electronic fuse indicator value i is greater than or equal to the total number of electronic fuses n, CPU21 switches to S100.

[0086] When transitioning to S100, CPU21 determines whether main ECU2 is connected to fault diagnosis device 90. If main ECU2 is not connected to fault diagnosis device 90, CPU21 terminates the connection check process.

[0087] On the other hand, when the main ECU2 is connected to the fault diagnosis device 90, in S110, the CPU21 sends one or more connection check results stored in the storage unit 13 that have not been sent to the fault diagnosis device 90 to the fault diagnosis device 90, and ends the connection check process.

[0088] The main ECU2 is configured such that each of the electronic fuses 14 and 15 is set to the on state. The electronic fuses 14 and 15 are configured to switch between the on state that connects the power supply paths 9 and 10 and the off state that disconnects the power supply paths 9 and 10.

[0089] The main ECU2 is configured such that, for each of the electronic fuses 14 and 15, after the electronic fuses 14 and 15 become conductive, it obtains current value information from the electronic fuses 14 and 15, showing the value of the current flowing through the power supply paths 9 and 10.

[0090] The main ECU2 is configured to perform a connection check to determine whether the slave ECUs 3 and 4 are connected to the electronic fuses 14 and 15 by comparing a pre-set current consumption value (which is the current consumption value of the slave ECUs 3 and 4 connected to the electronic fuses 14 and 15 and receiving power from the battery 7) with the current value shown in the current value information.

[0091] Because the main ECU2 can perform connection checks on whether the ECUs 3 and 4 are connected to the electronic fuses 14 and 15 without the use of special equipment, the efficiency of the connection check can be improved.

[0092] Furthermore, the main ECU2 is configured to store the connection check results. It is also configured to send the stored connection check results to a fault diagnosis device 90 located externally to the main ECU2. Thus, the main ECU2 can notify the operator performing the connection check of the connection check results.

[0093] In the embodiments described above, the main ECU2 is equivalent to the inspection device and the main control device, the battery 7 is equivalent to the power source, the slave ECUs 3 and 4 are equivalent to the connected load and the slave control device, the electronic fuses 14 and 15 are equivalent to the power supply switching unit, and the vehicle control system 1 is equivalent to the inspection system.

[0094] In addition, S20 to S30 are equivalent to the processing of the decision-making unit, S40 is equivalent to the processing of the conduction control unit, S60 and electronic fuses 14 and 15 are equivalent to the processing of the information acquisition unit, S70 is equivalent to the processing of the connection check unit, S80 is equivalent to the processing of the connection check result storage unit, and S110 is equivalent to the processing of the connection check result transmission unit.

[0095] In addition, the current value information is equivalent to the first verification information, and the current consumption value is equivalent to the second verification information.

[0096] [Second Implementation]

[0097] The following and appendix Figure 1 The second embodiment of this disclosure will now be described. Furthermore, in the second embodiment, the parts that differ from the first embodiment will be described. Common structural elements will be indicated by the same reference numerals.

[0098] The difference between the vehicle control system 1 in the second embodiment and the first embodiment is that the structure and connection check process of the vehicle control system 1 are changed.

[0099] like Figure 4As shown, the difference between the vehicle control system 1 of the second embodiment and the first embodiment is that the electronic fuse 14 is connected to the ECU 3, the ECU 5 and the sensor 50, and the electronic fuse 15 is connected to the actuator 60. The sensor 50 and the actuator 60 are mounted on the vehicle.

[0100] like Figure 5 As shown, in the connection check table 25 of the second embodiment, for the electronic fuse 14, the electronic fuse ID is set to "eFuse_1", the first connection load category is set to "ECU", the second connection load category is set to "ECU", and the third connection load category is set to "sensor". Furthermore, in the connection check table 25 of the second embodiment, the expected current consumption value for the first connection load is set to "500mA", the expected current consumption value for the second connection load is set to "200mA", and the expected current consumption value for the third connection load is set to "100mA".

[0101] For electronic fuse 15, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "actuator", and the expected current consumption value is set to "500mA".

[0102] Next, the sequence of the connection check processing in the second embodiment will be explained. The difference between the connection check processing in the second embodiment and the first embodiment is that the processing of S72, S82, and S112 is performed instead of S70, S80, and S110.

[0103] like Figure 6 As shown, when the processing of S60 ends, CPU21 performs a connection check on the i-th electronic fuse in S72.

[0104] Specifically, when a load is connected to the i-th electronic fuse, CPU21, like S70, determines "connection" if the current value shown in the current value information obtained by S60 is above the connection determination value, and determines "non-connection" if the current value shown in the current value information obtained by S60 is below the connection determination value.

[0105] Furthermore, when a load is connected to the i-th electronic fuse, if the current value shown in the current value information obtained by S60 is less than the assembly judgment value but greater than the connection judgment value, the CPU21 determines it as "incorrect assembly". "Incorrect assembly" refers to an incorrect connection of the load to the i-th electronic fuse. The assembly judgment value is obtained by multiplying the expected current consumption value of the i-th electronic fuse by a preset assembly check ratio. The assembly check ratio is, for example, 0.7. For example, since the expected current consumption value of the second electronic fuse is 500mA, the assembly judgment value of the second electronic fuse is 500 × 0.75 = 350 [mA].

[0106] Furthermore, when multiple loads are connected to the i-th electronic fuse, the CPU21 determines "connection" if the total expected current consumption of the multiple connected loads connected to the i-th electronic fuse is greater than or equal to the connection determination value, and determines "non-connection" if the total expected current consumption of the multiple connected loads connected to the i-th electronic fuse is less than the connection determination value. The connection determination value when multiple loads are connected is obtained by multiplying the total expected current consumption of the multiple connected loads by a preset connection check ratio.

[0107] Furthermore, when multiple loads are connected to the i-th electronic fuse, if the difference between the total expected current consumption of the multiple loads connected to the i-th electronic fuse and the current value shown in the current value information obtained by S60 is close to the expected current consumption of a single load connected to the i-th electronic fuse, the CPU21 determines that the corresponding load is "not connected". For example, the total expected current consumption of the three loads connected to the first electronic fuse (i.e., electronic fuse 14) is 500 + 200 + 100 = 800 [mA]. ​​And, if the current value shown in the current value information obtained by S60 is 600 [mA], the difference between the total expected current consumption and the current value shown in the obtained current value information is 200 [mA]. ​​This 200 [mA] is close to the expected current consumption of the second load (i.e., from ECU5). Therefore, the CPU21 determines that from ECU5 is "not connected".

[0108] When the processing of S72 ends, CPU21 stores the connection check result (i.e., the connection check result at S72) in storage unit 13 for the i-th electronic fuse in S82.

[0109] In addition, in S100, when the main ECU2 is connected to the fault diagnosis device 90, in S112, the CPU21 sends one or more connection check results stored in the storage unit 13 that have not been sent to the fault diagnosis device 90 to the fault diagnosis device 90, and ends the connection check process.

[0110] The main ECU2 of this disclosure is configured such that, when multiple connected loads (i.e., from ECUs 3, 5, and sensor 50) are connected to the electronic fuse 14, it determines the connected loads not connected to the electronic fuse 14 by comparing the sum of the multiple current consumption values ​​of each of the multiple connected loads with the difference between the current values ​​shown in the current value information and the multiple current consumption values. Thus, the main ECU2 can determine the connected loads not connected to the electronic fuse 14 even when multiple connected loads are connected to the electronic fuse 14.

[0111] In the embodiments described above, ECU3, 5, sensor 50 and actuator 60 are equivalent to connection loads, S72 is equivalent to the processing of the connection check unit, S82 is equivalent to the processing of the connection check result storage unit, and S112 is equivalent to the processing of the connection check result sending unit.

[0112] [Third Implementation Method]

[0113] The following and appendix Figure 1 The third embodiment of this disclosure will now be described. Furthermore, in the third embodiment, the parts that differ from the first embodiment will be described. Common structural elements will be indicated with the same reference numerals.

[0114] The difference between the vehicle control system 1 of the third embodiment and the first embodiment lies in the changes made to the structure of the vehicle control system 1 and the fact that communication connection check processing is performed instead of connection check processing.

[0115] like Figure 7 As shown, the difference between the vehicle control system 1 of the third embodiment and the first embodiment is that the storage unit 13 has a communication connection check table 27 instead of the connection check table 25.

[0116] Communication connection checklist 27 Figure 8 As shown, for each of the multiple electronic fuses 14 and 15 provided in the vehicle control system 1, an electronic fuse ID and an ECU ID for identifying the connected ECU are set.

[0117] In the communication connection checklist 27 of this embodiment, for electronic fuse 14, it is set as "eFuse_1" as electronic fuse ID and as "ECU_A" as ECU ID. For electronic fuse 15, it is set as "eFuse_2" as electronic fuse ID and as "ECU_B" as ECU ID.

[0118] Next, the sequence of communication connection check processes performed by the control unit 11 of the main ECU2 will be explained. The communication connection check process is a process that is repeatedly performed during the startup of the main ECU2.

[0119] When the communication connection check process is executed, the CPU 21 of the control unit 11, as follows: Figure 9 As shown, in S210, it is determined whether the main ECU2 is set to communication connection check mode. The control unit 11 of the main ECU2 is configured to set the main ECU2 to communication connection check mode when it receives a communication connection check command from the fault diagnosis device 90.

[0120] Here, if the main ECU2 is not set to communication connection check mode, CPU21 proceeds to S310. On the other hand, if the main ECU2 is set to communication connection check mode, CPU21 sets the electronic fuse indicator value i set in RAM23 to 0 in S220.

[0121] In S230, CPU21 increments the electronic fuse indicator value i.

[0122] In S240, CPU21 sets the i-th electronic fuse to the on state.

[0123] In the S250, CPU21 has a preset standby time in the on-state.

[0124] In S260, CPU21 sends an ID request to the ECU connected to the i-th electronic fuse.

[0125] In S270, CPU21 receives ECUID from the ECU connected to the i-th electronic fuse.

[0126] In step S280, CPU 21 performs a communication connection check on the i-th electronic fuse. Specifically, CPU 21 determines whether the ECUID received in step S270 matches the ECUID set for the i-th electronic fuse in the communication connection check table 27. If the ECUID received in step S270 does not match the ECUID set for the i-th electronic fuse in the communication connection check table 27, CPU 21 determines it as "incorrect assembly". Conversely, if the ECUID received in step S270 matches the ECUID set for the i-th electronic fuse in the communication connection check table 27, CPU 21 determines it as "correct assembly".

[0127] In S290, CPU21 stores the communication connection check result (i.e., the communication connection check result at S280) in storage unit 13 for the i-th electronic fuse.

[0128] In step S300, CPU21 determines whether the electronic fuse indicator value i is greater than or equal to the preset total number of electronic fuses n (2 in this embodiment). If the electronic fuse indicator value i is less than the total number of electronic fuses n, CPU21 proceeds to step S230.

[0129] On the other hand, when the electronic fuse indicator value i is greater than or equal to the total number of electronic fuses n, CPU21 switches to S310.

[0130] When transitioning to S310, CPU21 determines whether main ECU2 is connected to fault diagnosis device 90. If main ECU2 is not connected to fault diagnosis device 90, CPU21 terminates the communication connection check process.

[0131] On the other hand, when the main ECU2 is connected to the fault diagnosis device 90, in S320, the CPU21 sends the communication connection check results that were not sent to the fault diagnosis device 90 from one or more communication connection check results stored in the storage unit 13 to the fault diagnosis device 90, and ends the communication connection check process.

[0132] The main ECU2 is configured such that each of the electronic fuses 14 and 15 is set to the on state. The electronic fuses 14 and 15 are configured to switch between the on state that connects the power supply paths 9 and 10 and the off state that disconnects the power supply paths 9 and 10.

[0133] The main ECU2 is configured such that, for each of the electronic fuses 14 and 15, after the electronic fuses 14 and 15 become conductive, it sends an ID request to the slave ECUs 3 and 4 connected to the electronic fuses 14 and 15.

[0134] The main ECU2 is configured such that, for each of the electronic fuses 14 and 15, after sending an ID request, it receives the ECUID from the slave ECUs 3 and 4 connected to the electronic fuses 14 and 15 to identify the slave ECUs 3 and 4.

[0135] The main ECU2 is configured to perform a communication connection check, which is as follows: for each of the electronic fuses 14 and 15, if the ECUID that identifies a reasonable connection device that is pre-set as a device connected to the electronic fuses 14 and 15 is consistent with the received ECUID, it is determined that a reasonable connection device is connected to the electronic fuses 14 and 15; if they are inconsistent, it is determined that a reasonable connection device is not connected to the electronic fuses 14 and 15.

[0136] Because the main ECU2 can perform communication connection checks on whether the ECUs 3 and 4 are connected to the electronic fuses 14 and 15 without the use of special equipment, the efficiency of the connection check can be improved.

[0137] Furthermore, the main ECU2 is configured to store the communication connection check results. It is also configured to send the stored communication connection check results to a fault diagnosis device 90 located externally to the main ECU2. Thus, the main ECU2 can notify the operator performing the connection check of the communication connection check results.

[0138] In the embodiments described above, S220 to S230 are equivalent to the processing of the decision unit, S240 is equivalent to the processing of the conduction control unit, S260 is equivalent to the processing of the identification information request unit, S270 is equivalent to the processing of the identification information receiving unit, and S280 is equivalent to the processing of the connection check unit.

[0139] In addition, ECU3 and 4 are equivalent to connected loads, the ID requirement is equivalent to identification information requirement, the ECUID received by the main ECU2 is equivalent to load identification information and first verification information, and the ECUID set in the communication connection check table 27 is equivalent to reasonable identification information and second verification information.

[0140] In addition, S290 is equivalent to the processing of the communication connection check result storage unit, and S320 is equivalent to the processing of the communication connection check result sending unit.

[0141] [Fourth Implementation Method]

[0142] The following and appendix Figure 1 The fourth embodiment of this disclosure will now be described. Furthermore, in the fourth embodiment, the parts that differ from the first embodiment will be described. Common structural elements will be indicated with the same reference numerals.

[0143] The difference between the vehicle control system 1 in the fourth embodiment and the first embodiment is that the structure and connection check process of the vehicle control system 1 are changed.

[0144] like Figure 10 As shown, the vehicle control system 1 of the fourth embodiment differs from that of the first embodiment in that it has a voltage detection unit 17 instead of a current detection unit 16.

[0145] The voltage detection unit 17 is configured to, for example, detect the voltage value applied in the power supply paths 9 and 10 at a position downstream of the electronic fuses 14 and 15 (i.e., between the electronic fuses 14 and 15 and the slave ECUs 3 and 4), and output the power supply path voltage value information showing the detected voltage value to the master ECU 2.

[0146] like Figure 11 As shown, the connection check table 25 of the fourth embodiment sets the electronic fuse ID, the connected load type, and the desired power supply path voltage value (hereinafter referred to as the desired power supply path voltage value) for each of the plurality of electronic fuses 14, 15 provided in the vehicle control system 1.

[0147] In the connection checklist 25 of the fourth embodiment, for electronic fuse 14, the electronic fuse ID is set to "eFuse_1", the connected load category is set to "ECU", and the desired power supply path voltage value is set to "12V". For electronic fuse 15, the electronic fuse ID is set to "eFuse_2", the connected load category is set to "ECU", and the desired power supply path voltage value is set to "12V".

[0148] Next, the sequence of the connection check processing in the fourth embodiment will be explained. The difference between the connection check processing in the fourth embodiment and that in the first embodiment is that the processing in S64 and S74 is performed instead of S60 and S70.

[0149] like Figure 12 As shown, when the processing of S50 ends, the CPU21 obtains the power supply path voltage value information of the i-th electronic fuse from the voltage detection unit 17 in S64. Furthermore, the power supply path voltage value information of the first electronic fuse is the power supply path voltage value information of power supply path 9, and the power supply path voltage value information of the second electronic fuse is the power supply path voltage value information of power supply path 10.

[0150] In S74, CPU21 performs a connection check on the i-th electronic fuse. Specifically, if the voltage value shown in the power supply path voltage value information obtained in S64 is above the voltage connection determination value, CPU21 determines it as "connected"; if the voltage value shown in the power supply path voltage value information obtained in S64 is below the voltage connection determination value, it determines it as "not connected". The voltage connection determination value is obtained by multiplying the expected power supply path voltage value of the i-th electronic fuse by a preset connection check ratio. Furthermore, power supply paths 9 and 10 are configured such that, when ECUs 3 and 4 are connected to power supply paths 9 and 10, the voltage value at a position downstream of electronic fuses 14 and 15 (i.e., the position where the voltage detection unit 17 detects the voltage) is close to the expected power supply path voltage value; and when ECUs 3 and 4 are not connected to power supply paths 9 and 10, the voltage value at a position downstream of electronic fuses 14 and 15 is close to 0V.

[0151] When S74 finishes processing, CPU21 transfers the process to S80.

[0152] The main ECU2 is configured such that, for each of the electronic fuses 14 and 15, after the electronic fuses 14 and 15 become conductive, it acquires power supply path voltage value information showing the value of the voltage applied to the power supply paths 9 and 10.

[0153] The main ECU2 is configured to perform a connection check on whether the ECU3 and 4 are connected to the electronic fuses 14 and 15 by comparing a predetermined expected power supply path voltage value (which is the voltage applied to the power supply paths 9 and 10 connected to the electronic fuses 14 and 15) with the voltage value shown in the power supply path voltage value information for each of the electronic fuses 14 and 15.

[0154] Because the main ECU2 can perform connection checks on whether the ECUs 3 and 4 are connected to the electronic fuses 14 and 15 without the use of special equipment, the efficiency of the connection check can be improved.

[0155] In the embodiments described above, S64 and voltage detection unit 17 are equivalent to the processing of information acquisition unit, S74 is equivalent to the processing of connection inspection unit, power supply path voltage value information is equivalent to voltage value information and first verification information, and expected power supply path voltage value is equivalent to power supply path voltage value and second verification information.

[0156] [Fifth Implementation]

[0157] The following and appendix Figure 1The fifth embodiment of this disclosure will now be described. Furthermore, in the fifth embodiment, the parts that differ from the fourth embodiment will be described. Common structural elements will be indicated with the same reference numerals.

[0158] The difference between the vehicle control system 1 of the fifth embodiment and the fourth embodiment is that the connection check table 25 and the connection check process are changed.

[0159] like Figure 13 As shown, the connection checklist 25 of the fifth embodiment sets the electronic fuse ID, connected load type, desired current consumption value, and desired power supply path voltage value for each of the plurality of electronic fuses 14, 15 provided in the vehicle control system 1.

[0160] In the connection checklist 25 of the fifth embodiment, for electronic fuse 14, the electronic fuse ID is set to "eFuse_1", the connected load type is set to "ECU", the current consumption value is set to "500mA", and the expected power supply path voltage value is set to "12V". For electronic fuse 15, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "ECU", the expected current consumption value is set to "200mA", and the expected power supply path voltage value is set to "12V".

[0161] Next, the sequence of the connection check processing in the fifth embodiment will be explained. The difference between the connection check processing in the fifth embodiment and that in the fourth embodiment is that the processing of S66 and S76 is performed instead of S64 and S74.

[0162] like Figure 14 As shown, when the processing of S50 ends, CPU21 obtains current value information from the i-th electronic fuse in S66, and obtains power supply path voltage value information of the i-th electronic fuse from the voltage detection unit 17.

[0163] In step S76, CPU21 performs a connection check on the i-th electronic fuse. Specifically, if the current value obtained from step S66 is greater than or equal to the connection determination value, and the voltage value obtained from the power supply path voltage value obtained from step S66 is greater than or equal to the voltage connection determination value, CPU21 determines the fuse to be "connected". Conversely, if the current value obtained from step S66 is less than the connection determination value, or the voltage value obtained from the power supply path voltage value obtained from step S66 is less than the voltage connection determination value, CPU21 determines the fuse to be "not connected".

[0164] When S76 finishes processing, CPU21 transfers the process to S80.

[0165] The main ECU2 is configured such that, for each of the electronic fuses 14 and 15, after the electronic fuses 14 and 15 become in the on state, it acquires current value information showing the value of the current flowing through the power supply paths 9 and 10, and power supply path voltage value information showing the value of the voltage applied to the power supply paths 9 and 10.

[0166] The main ECU2 is configured to perform a connection check to determine whether the slave ECUs 3 and 4 are connected to the electronic fuses 14 and 15 by performing a first comparison and a second comparison. The first comparison is: for each of the electronic fuses 14 and 15, a pre-set current consumption value, which is the current value consumed by the slave ECUs 3 and 4 connected to the electronic fuses 14 and 15 and receiving power from the battery 7, is compared with the current value shown in the current value information. The second comparison is: for each of the electronic fuses 14 and 15, a pre-set desired power supply path voltage value, which is the voltage applied to the power supply paths 9 and 10 connected to the electronic fuses 14 and 15, is compared with the voltage value shown in the power supply path voltage value information.

[0167] Because the main ECU2 can perform connection checks on whether the ECUs 3 and 4 are connected to the electronic fuses 14 and 15 without the use of special equipment, the efficiency of the connection check can be improved.

[0168] In the embodiments described above, S66, electronic fuses 14 and 15, and voltage detection unit 17 are equivalent to the processing of the information acquisition unit, and S76 is equivalent to the processing of the connection inspection unit.

[0169] [Sixth Implementation Method]

[0170] The following and appendix Figure 1 The sixth embodiment of this disclosure will now be described. Furthermore, in the sixth embodiment, the parts that differ from the first embodiment will be described. Common structural elements will be indicated with the same reference numerals.

[0171] like Figure 15 As shown, the vehicle control system 1 of the sixth embodiment differs from that of the first embodiment in that it adds a smart sensor 501, a smart actuator 502, a wireless device 503, and electronic fuses 504 and 505.

[0172] The intelligent sensor 501 is a sensor with communication capabilities. The intelligent sensor 501 is connected to the communication bus 8.

[0173] The intelligent actuator 502 is an actuator with communication capabilities. The intelligent actuator 502 is connected to the communication bus 8.

[0174] Wireless device 503 is a wireless communication device used for wireless communication with an external communication device located outside the vehicle. Wireless device 503 is, for example, a DCM. DCM is an abbreviation for Data Communication Module.

[0175] Electronic fuse 504 is configured in the power supply path between battery 7 and smart sensor 501. Electronic fuse 505 is configured in the power supply path between battery 7 and smart actuator 502.

[0176] Electronic fuses 504 and 505 are configured to switch to either a conducting state (connecting the power supply path) or a disconnecting state (disconnecting the power supply path) according to instructions from the control unit 11.

[0177] Hereinafter, the main ECU2, slave ECUs3-5, smart sensor 501 and smart actuator 502 will be collectively referred to as nodes.

[0178] A CAN frame consists of a start frame, an arbitration field, a control field, a data field, a CRC field, an ACK field, and an end frame. Furthermore, the arbitration field consists of an 11-bit or 29-bit identifier (i.e., ID) and a 1-bit RTR bit.

[0179] The 11-bit identifier used in CAN communication is called the CANID. The CANID is pre-defined based on the content of the data included in the CAN frame, the source of the CAN frame, and the destination of the CAN frame.

[0180] The data field consists of a payload of 8 bits (i.e., 1 byte) of first, second, third, fourth, fifth, sixth, seventh, and eighth data.

[0181] The vehicle control system 1 forms a local network, which is a power supply control method based on the CAN protocol standard specified in ISO 11898-6. Therefore, the vehicle control system 1 individually transfers one or more nodes belonging to each communication group to either a wake-up state (i.e., start-up state) or a sleep state (i.e., sleep state) according to the communication groups described later, thereby achieving low power consumption. When a node is awake, it enters a normal operating state where it can utilize the functions allocated to it without restriction; when a node is sleep, it enters a low-power operating state where the functions that can be utilized are limited.

[0182] In the vehicle control system 1, when waking up a node in a dormant state, an NM frame is used. The NM frame is a CAN frame that includes start-up information for a specified start-up group. NM is an abbreviation for Network Management.

[0183] Startup information, such as Figure 16 It is set as shown. DLC is an abbreviation for Data Length Code, which is a region that expresses the size of the data field in a CAN frame in bytes. That is, the start information is stored in the data field of the CAN frame. Here, for simplicity, the case where the DLC is 1 byte (i.e., 8 bits) is shown. The start group is mapped to each bit of the 8 bits of data expressing the start information.

[0184] Regarding the startup information set in the NM frame, the bit corresponding to the startup group that becomes the startup target is set to 1.

[0185] Each node stores information indicating its membership in the startup group. This membership information has the same data length as the startup information, and the bit allocation is also the same. Furthermore, regarding the membership information, the bit corresponding to the startup group to which this node belongs is set to 1.

[0186] Each node determines whether its communication group is a target for startup by comparing the startup information extracted from the NM frame with the membership information stored in the node.

[0187] For example, Figure 16 The information shown indicates that the device belongs to the first, third, and fifth communication groups. Figure 16 The startup information shown indicates that the second, third, fourth, and fifth communication groups are started. This is because the third and fifth communication groups are included in... Figure 16 Based on the information shown regarding the ownership and the start-up information, this node is determined to be the start-up target for both the third and fifth communication groups.

[0188] like Figure 15 As shown, storage unit 13 stores management table 29. Furthermore, management table 29 can also be stored in ROM 22 or RAM 23.

[0189] Management Table 29 sets the correspondence between each of the multiple communication groups and one or more nodes belonging to the corresponding communication group (i.e., one or more nodes to be started).

[0190] For example, management table 29 sets the master ECU2 and slave ECUs 3 and 4 to belong to the first communication group.

[0191] For example, in management table 29, settings are configured for ECUs 3, 4, and 5 belonging to the second communication group.

[0192] Furthermore, the master ECU2 and slave ECUs 3 to 5 are configured such that when the start condition of each of the multiple events is detected to be met, an NM frame containing information showing the communication group related to the corresponding event is generated and sent as the aforementioned start information.

[0193] (Prerequisites)

[0194] The master ECU2 and slave ECU5 are always powered by battery 7 without passing through an electronic fuse, and can be switched to wake-up or sleep mode independently through this node. Hereinafter, master ECU2 and slave ECU5 will also be referred to as NM-equipped nodes. An NM-equipped node is a node with the function of generating NM frames.

[0195] Powered by ECUs 3 and 4, smart sensor 501, and smart actuator 502 via an electronic fuse, this node cannot be switched to wake-up or sleep mode independently. That is, it enters wake-up mode when the electronic fuse is turned on and sleep mode when the electronic fuse is turned off. Hereinafter, ECUs 3 and 4, smart sensor 501, and smart actuator 502 will also be referred to as nodes without NM (Network Module) functionality. Nodes without NM functionality do not have the ability to generate and interpret NM frames.

[0196] The absence of an NM node includes at least one of the actuators and sensors, in addition to the ECU which has control functions.

[0197] The power supply paths without NM nodes are connected to electronic fuses 14, 15, 504, and 505 of the main ECU2.

[0198] A node without NM can be connected to an electronic fuse one-to-one, or multiple nodes without NM can be connected to the same group (i.e., a group that starts at the same time) under a single electronic fuse.

[0199] The main ECU2 and the NM-mounted node have communication capabilities and can send and receive NM frames.

[0200] The NM-equipped node determines whether it is in a wake-up state or a sleep state based on the NM frames sent and received via the communication bus.

[0201] The main ECU2 sets the electronic fuses 14, 15, 504, and 505, which are connected to electronic fuses without NM nodes, to either the on or off state based on the NM frames transmitted and received via the communication bus.

[0202] The payload (i.e., data area) of the NM frames transmitted and received by the main ECU2 and the NM mount node stores one or more bits indicating which group to start.

[0203] There is more than one main ECU (i.e., ECU with built-in electronic fuse) in the vehicle.

[0204] like Figure 17As shown, one or more nodes belonging to each group are predetermined by the system developer. While it's possible to assign a group to each node, it's also possible to register multiple nodes within a single group. A group is woken up when the bit corresponding to that group is active (i.e., bit=1). In the case of the master ECU, waking up means turning on the electronic fuse.

[0205] (First startup case)

[0206] The first example of an action was to perform fault diagnosis on ECU3 based on a request from the cloud.

[0207] First, a connection request is generated from the base station (i.e., the cloud) to the vehicle's wireless unit 503.

[0208] Next, when the wireless unit 503 determines that the connection is valid, it transmits the event received from the cloud to the main ECU2.

[0209] Next, the master ECU2 determines the "fault diagnosis from ECU3" service based on the event. In order to enable ECU3 to start, an NM frame is generated that makes only the bits of the third group to which ECU3 belongs valid.

[0210] Next, the main ECU2 sends the generated NM frame to the communication bus 8.

[0211] Since there are no NM mounting nodes belonging to the third group on communication bus 8, the machines on the communication bus remain unchanged.

[0212] Next, the main ECU2 considers that it has received an NM frame that makes the bits of the third group valid at the same time as described above, and performs NM frame-based processing in the control unit 11.

[0213] Next, when the control unit 11 of the main ECU2 determines the wake-up instruction for the third group based on the NM frame, the electronic fuse 14 is set to the on state because the third group includes the electronic fuse 14.

[0214] When the electronic fuse 14 is turned on, it supplies power to the downstream ECU 3 to start the engine.

[0215] The master ECU2 waits for the slave ECU3 to start, requests diagnostic codes from the slave ECU3, and then the response from the slave ECU3 is sent to the base station via the wireless unit 503.

[0216] (Second starting case)

[0217] The second starting example is an action example of fault diagnosis from ECU5 performed by requesting from the cloud.

[0218] First, a connection request is generated from the base station (i.e., the cloud) to the vehicle's wireless unit 503.

[0219] Next, when the wireless unit 503 determines that the connection is valid, it transmits the event received from the cloud to the main ECU2.

[0220] Next, the master ECU2 determines the "fault diagnosis from ECU5" service based on the event. In order to enable ECU5 to start, an NM frame is generated that makes only the bits of the fourth group to which ECU5 belongs valid.

[0221] Next, the main ECU2 sends the generated NM frame to the communication bus 8.

[0222] Because there is a node on communication bus 8 belonging to the fourth group, ECU5 is woken up.

[0223] Next, the main ECU2 considers that it has received an NM frame that enables the bit of the fourth group at the same time as described above, and performs NM frame-based processing in the control unit 11.

[0224] Next, the control unit 11 of the main ECU2, based on the NM frame, decides to wake up the fourth group, but ignores it because the corresponding electronic fuse is not included in the fourth group.

[0225] When the slave ECU5 is started, the master ECU2 requests a diagnostic code from the slave ECU5 via the communication bus 8. The response from the slave ECU5 is then sent to the base station via the wireless unit 503.

[0226] (Third starting case)

[0227] The third startup example is a user remotely starting the air conditioner via their smartphone.

[0228] First, the user instructs the car's air conditioning to be turned on via their smartphone.

[0229] The wireless unit 503 receives an indication signal from a smartphone. When the wireless unit 503 determines that the indication signal is valid, it transmits the event (i.e., the indication signal) received from the cloud to the main ECU2.

[0230] The main ECU2 determines the "air conditioning service" based on events and generates an NM frame that will be activated as the second group of air conditioning users.

[0231] If the main ECU2 wants to continue its active state of periodically sending generated NM frames to the communication bus 8 until an air conditioning stop instruction is issued, it needs to continuously send NM frames periodically. At the same time, the control unit 11 of the main ECU2 performs processing based on the NM frames.

[0232] When an NM frame that activates the second group is generated on the communication bus 8, the ECU5 (i.e., the air conditioning ECU) belonging to the second group receives the NM frame and wakes up according to the received NM frame.

[0233] When the control unit 11 of the main ECU2 detects that the second group is active, it sets the electronic fuses 504 and 505 belonging to the second group to the on state.

[0234] When electronic fuses 504 and 505 are in the ON state, power is supplied to smart sensor 501 (i.e., temperature sensor) and smart actuator 502 (i.e., compressor).

[0235] This initiates power supply to the air conditioning ECU, smart sensor 501, and smart actuator 502, thereby enabling the vehicle's air conditioning to be turned on.

[0236] When the user instructs the vehicle's air conditioning to be turned off via their smartphone, the main ECU2 stops periodically sending NM frames.

[0237] When the NM frame is interrupted, ECU5 transitions to sleep mode, and main ECU2 disconnects electronic fuses 504 and 505. This stops the vehicle's air conditioning.

[0238] (Fourth starting case)

[0239] The fourth starting example is the action of starting the vehicle's air conditioning from ECU5.

[0240] Because ECU5 is always supplied with power even when the vehicle is stopped, it can be woken up even in sleep mode by detecting an input indicating that the start switch connected to ECU5 is turned on.

[0241] When the ECU5 is awakened and confirms the input that the vehicle air conditioning should be started, it generates an NM frame that turns on the bit corresponding to the second group.

[0242] The NM frame generated is sent from ECU5 via CAN communication unit 32. When the main ECU2 receives the NM frame, the main ECU2 sets the electronic fuses 504 and 505 belonging to the second group to the ON state.

[0243] When the vehicle's air conditioning start switch is turned off, ECU5 stops sending NM frames and transitions to sleep mode after a short while.

[0244] When the NM frame is interrupted, the main ECU2 sets the electronic fuses 504 and 505 to the open state after a short while, thereby ending the control.

[0245] If the main ECU2 determines that continued control is needed even after the transmission of the NM frame has stopped, the main ECU2 sends an NM frame that turns on the bits equivalent to the second group. Therefore, the slave ECU5 and electronic fuses 504 and 505 can also maintain their startup state until the transmission of the NM frame generated by the main ECU2 stops.

[0246] [Seventh Implementation Method]

[0247] The following and appendix Figure 1 The seventh embodiment of this disclosure will now be described. Furthermore, in the seventh embodiment, the parts that differ from the first embodiment will be described. Common structural elements will be indicated with the same reference numerals.

[0248] The vehicle control system 100 of the seventh embodiment is mounted on a vehicle, such as Figure 18 As shown, the system includes a central ECU 101, upstream power distribution units 102 and 103, regional ECUs 104, 105, 106, and 107, slave ECUs 108, 109, 110, 111, 112, 113, 114, 115, and 116, a battery 117, and a slave ECU 118. Hereinafter, the central ECU 101, regional ECUs 104 to 107, and slave ECUs 108 to 116 and 118 will be collectively referred to as nodes. Here, a regional ECU can be either an ECU bundled with a slave ECU located in a specified area within the vehicle, or an ECU bundled with a slave ECU belonging to a specified domain.

[0249] Battery 117 supplies power to various parts of the vehicle at a DC battery voltage (e.g., 12V). The central ECU 101, upstream power distribution units 102 and 103, regional ECUs 104 to 107, and ECUs 108 to 116 and 118 operate by receiving power from battery 117.

[0250] The upstream power distribution unit 102 receives power from the battery 117 through the power supply path 121 between the battery 117 and the upstream power distribution unit 102.

[0251] The upstream power distribution unit 103 receives power from the battery 117 through the power supply path 122 between the battery 117 and the upstream power distribution unit 103.

[0252] The regional ECUs 104 and 105 receive power from the battery 117 through power supply paths 123 and 124 between the upstream power distribution unit 102 and the regional ECUs 104 and 105, respectively.

[0253] The regional ECUs 106 and 107 receive power from the battery 117 through the power supply paths 125 and 126 between the upstream power distribution unit 103 and the regional ECUs 106 and 107, respectively.

[0254] ECUs 108 and 109 receive power from battery 117 through power supply paths 127 and 128 between region ECU 104 and ECUs 108 and 109, respectively.

[0255] ECUs 110 and 111 receive power from battery 117 through power supply paths 129 and 130 between region ECU 105 and ECUs 110 and 111, respectively.

[0256] ECUs 112, 113, and 114 receive power from battery 117 through power supply paths 131, 132, and 133 between region ECU 106 and ECUs 112, 113, and 114, respectively.

[0257] ECUs 115 and 116 receive power from battery 117 through power supply paths 134 and 135 between region ECU 107 and ECUs 115 and 116, respectively.

[0258] The ECU 118 receives power from the battery 117 via power supply path 136.

[0259] The central ECU 101 and the upstream power distribution unit 102 are connected via communication line 141 in a manner that enables them to communicate with each other.

[0260] The central ECU 101 and the upstream power distribution unit 103 are connected via communication line 142 in a manner that enables them to communicate with each other.

[0261] The central ECU 101 and the regional ECUs 104, 105, 106, and 107 are connected to each other via communication lines 143, 144, 145, and 146, respectively, in a manner that enables them to communicate with each other.

[0262] The regional ECU 104 and the sub-ECUs 108, 109, and 118 are connected via communication bus 147 in a manner that enables them to communicate with each other.

[0263] The regional ECU 105 and the slave ECUs 110 and 111 are connected to each other via the communication bus 148 in a manner that enables them to communicate with each other.

[0264] The regional ECU 106 and the ECUs 112, 113, and 114 are connected to each other via the communication bus 149 in a manner that enables them to communicate with each other.

[0265] The regional ECU 107 and the sub-ECUs 115 and 116 are connected via communication bus 150 in a manner that enables them to communicate with each other.

[0266] like Figure 19As shown, the central ECU 101 includes a control unit 151, communication units 152, 153, 154, 155, 156, 157 and a storage unit 158.

[0267] The control unit 151 is an electronic control device centered on a microcomputer including a CPU 161, ROM 162, and RAM 163. Various functions of the microcomputer are implemented by the CPU 161 executing programs stored on a non-transient physical recording medium. In this example, the ROM 162 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 161 via hardware. Additionally, the number of microcomputers constituting the control unit 151 can be one or more.

[0268] The communication unit 152 communicates with the upstream power distribution unit 102 connected to the communication line 141, for example, by sending and receiving communication frames based on the Ethernet communication protocol. Ethernet is a registered trademark.

[0269] The communication unit 153 communicates with the upstream power distribution unit 103 connected to the communication line 142, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0270] The communication unit 154 communicates with the area ECU 104 connected to the communication line 143, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0271] The communication unit 155 communicates with the area ECU 105 connected to the communication line 144, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0272] The communication unit 156 communicates with the area ECU 106 connected to the communication line 145, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0273] The communication unit 157 communicates with the area ECU 107 connected to the communication line 145, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0274] Storage unit 158 ​​is a storage device for storing various types of data. Storage unit 158 ​​stores the start table 165, which will be described later.

[0275] The upstream power distribution unit 102 includes a control circuit 171, a communication unit 172, and electronic fuses 173 and 174.

[0276] The control circuit 171 controls the switching of electronic fuses 173 and 174 between the on and off states based on instructions obtained from the central ECU 101 via the communication unit 172.

[0277] The communication unit 172 communicates with the central ECU 101 connected to the communication line 141, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0278] Electronic fuse 173 is configured between power supply path 121 and power supply path 123. Electronic fuse 174 is configured between power supply path 121 and power supply path 124.

[0279] The upstream power distribution unit 103 includes a control circuit 181, a communication unit 182, and electronic fuses 183 and 184.

[0280] The control circuit 181 controls the switching of electronic fuses 183 and 184 between the on and off states based on instructions obtained from the central ECU 101 via the communication unit 182.

[0281] The communication unit 182 communicates with the central ECU 101 connected to the communication line 142, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0282] Electronic fuse 183 is configured between power supply path 122 and power supply path 125. Electronic fuse 184 is configured between power supply path 122 and power supply path 126.

[0283] like Figure 20 As shown, the regional ECU 104 includes a control unit 191, a communication unit 192, a CAN communication unit 193, a storage unit 194, and electronic fuses 195 and 196.

[0284] The control unit 191 is an electronic control device centered on a microcomputer including a CPU 201, ROM 202, and RAM 203. Various functions of the microcomputer are implemented by the CPU 201 executing programs stored on a non-transient physical recording medium. In this example, the ROM 202 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 201 via hardware. Additionally, the number of microcomputers constituting the control unit 191 can be one or more.

[0285] The communication unit 192 communicates with the central ECU 101 connected to the communication line 143, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0286] The CAN communication unit 193 communicates with the slave ECUs 108 and 109 connected to the communication bus 147 by sending and receiving communication frames based on the CAN communication protocol.

[0287] Storage unit 194 is a storage device used to store various types of data.

[0288] Electronic fuse 195 is configured between power supply path 123 and power supply path 127. Electronic fuse 196 is configured between power supply path 123 and power supply path 128.

[0289] The regional ECU 105 includes a control unit 211, a communication unit 212, a CAN communication unit 213, a storage unit 214, and electronic fuses 215 and 216.

[0290] The control unit 211 is an electronic control device centered on a microcomputer including a CPU 221, ROM 222, and RAM 223. Various functions of the microcomputer are implemented by the CPU 221 executing programs stored on a non-transient physical recording medium. In this example, the ROM 222 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 221 through hardware. Additionally, the number of microcomputers constituting the control unit 211 can be one or more.

[0291] The communication unit 212 communicates with the central ECU 101 connected to the communication line 144, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0292] The CAN communication unit 213 communicates with the slave ECUs 110 and 111 connected to the communication bus 148 by sending and receiving communication frames based on the CAN communication protocol.

[0293] Storage unit 214 is a storage device used to store various types of data.

[0294] Electronic fuse 215 is configured between power supply path 124 and power supply path 129. Electronic fuse 216 is configured between power supply path 124 and power supply path 130.

[0295] like Figure 21 As shown, the regional ECU106 includes a control unit 231, a communication unit 232, a CAN communication unit 233, a storage unit 234, and electronic fuses 235, 236, and 237.

[0296] The control unit 231 is an electronic control device centered on a microcomputer including a CPU 241, ROM 242, and RAM 243. Various functions of the microcomputer are implemented by the CPU 241 executing programs stored on a non-transient physical recording medium. In this example, the ROM 242 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 241 via hardware. Additionally, the number of microcomputers constituting the control unit 231 can be one or more.

[0297] The communication unit 232 communicates with the central ECU 101 connected to the communication line 145, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0298] The CAN communication unit 233 communicates with the slave ECUs 112, 113, and 114 connected to the communication bus 149 by sending and receiving communication frames based on the CAN communication protocol.

[0299] Storage unit 234 is a storage device used to store various types of data.

[0300] Electronic fuse 235 is disposed between power supply path 125 and power supply path 131. Electronic fuse 236 is disposed between power supply path 125 and power supply path 132. Electronic fuse 237 is disposed between power supply path 125 and power supply path 133.

[0301] The regional ECU 107 includes a control unit 251, a communication unit 252, a CAN communication unit 253, a storage unit 254, and electronic fuses 255 and 256.

[0302] The control unit 251 is an electronic control device centered on a microcomputer including a CPU 261, ROM 262, and RAM 263. Various functions of the microcomputer are implemented by the CPU 261 executing programs stored on a non-transient physical recording medium. In this example, the ROM 262 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 261 via hardware. Additionally, the number of microcomputers constituting the control unit 251 can be one or more.

[0303] The communication unit 252 communicates with the central ECU 101 connected to the communication line 146, for example, by sending and receiving communication frames based on the Ethernet communication protocol.

[0304] The CAN communication unit 253 communicates with the slave ECUs 115 and 116 connected to the communication bus 150 by sending and receiving communication frames based on the CAN communication protocol.

[0305] Storage unit 254 is a storage device used to store various types of data.

[0306] Electronic fuse 255 is configured between power supply path 126 and power supply path 134. Electronic fuse 256 is configured between power supply path 126 and power supply path 135.

[0307] like Figure 22 As shown, ECUs 108, 109, and 118 include a control unit 271, a CAN communication unit 272, and a storage unit 273.

[0308] The control unit 271 is an electronic control device centered on a microcomputer including a CPU 281, ROM 282, and RAM 283. Various functions of the microcomputer are implemented by the CPU 281 executing programs stored on a non-transient physical recording medium. In this example, the ROM 282 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 281 via hardware. Additionally, the number of microcomputers constituting the control unit 271 can be one or more.

[0309] The CAN communication unit 272 communicates with the area ECU 104 connected to the communication bus 147 based on the CAN communication protocol.

[0310] Storage unit 273 is a storage device used to store various types of data.

[0311] The ECUs 110 and 111 include a control unit 291, a CAN communication unit 292, and a storage unit 293.

[0312] The control unit 291 is an electronic control device centered on a microcomputer including a CPU 301, ROM 302, and RAM 303. Various functions of the microcomputer are implemented by the CPU 301 executing programs stored on a non-transient physical recording medium. In this example, the ROM 302 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 301 via hardware. Additionally, the number of microcomputers constituting the control unit 291 can be one or more.

[0313] The CAN communication unit 292 communicates with the area ECU 105 connected to the communication bus 148 based on the CAN communication protocol.

[0314] Storage unit 293 is a storage device used to store various types of data.

[0315] ECUs 112, 113, and 114 each include a control unit 311, a CAN communication unit 312, and a storage unit 313.

[0316] The control unit 311 is an electronic control device centered on a microcomputer including a CPU 321, a ROM 322, and a RAM 323. Various functions of the microcomputer are implemented by the CPU 321 executing programs stored on a non-transient physical recording medium. In this example, the ROM 322 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 321 via hardware. Additionally, the number of microcomputers constituting the control unit 311 can be one or more.

[0317] The CAN communication unit 312 communicates with the area ECU 106 connected to the communication bus 149 based on the CAN communication protocol.

[0318] Storage unit 313 is a storage device used to store various types of data.

[0319] ECUs 115 and 116 include a control unit 331, a CAN communication unit 332, and a storage unit 333.

[0320] The control unit 331 is an electronic control device centered on a microcomputer including a CPU 341, ROM 342, and RAM 343. Various functions of the microcomputer are implemented by the CPU 341 executing programs stored on a non-transient physical recording medium. In this example, the ROM 342 is equivalent to the non-transient physical recording medium storing the program. Furthermore, by executing this program, the method corresponding to the program is executed. Alternatively, one or more ICs or the like can be used to construct part or all of the functions executed by the CPU 341 via hardware. Additionally, the number of microcomputers constituting the control unit 331 can be one or more.

[0321] The CAN communication unit 332 communicates with the area ECU 107 connected to the communication bus 150 based on the CAN communication protocol.

[0322] Storage unit 333 is a storage device used to store various types of data.

[0323] like Figure 23 As shown, in the start table 165 of the central ECU 101, a communication group (i.e., a start group) to be started is set for each event. The start table 165 further sets the correspondence between the start groups and the slave ECUs set to wake-up state. The start table 165 further sets the correspondence between the slave ECUs and the electronic fuses connected to the slave ECUs. Furthermore, the start table 165 can also be set in a form that indicates which region's ECU the slave ECU belongs to.

[0324] When the central ECU 101 detects an event, it determines the starting group based on the detected event and by referring to the starting table 165.

[0325] When the central ECU101 receives an NM frame, it determines that the communication group corresponding to the bit set to 1 in the received NM frame is the start group.

[0326] The central ECU 101 begins sending NM frames to the regional ECUs 104, 105, 106, and 107, indicating the start-up group as determined by the detection of the event or the reception of the NM frame. Once the transmission of NM frames begins, the central ECU 101 subsequently sends the same NM frames periodically.

[0327] The central ECU 101 sends an electronic fuse control instruction to the upstream power distribution units 102 and 103 and the regional ECUs 104, 105, 106, and 107 by referring to the start table 165. The electronic fuse control instruction instructs the electronic fuse corresponding to the start group determined by the detection of the event or the reception of the NM frame to be set to the on state, and instructs the electronic fuses other than the electronic fuse corresponding to the start group to be set to the off state.

[0328] Based on the received electronic fuse control instruction, the upstream power distribution unit 102 sets the electronic fuses 173 and 174 to the on or off state.

[0329] Based on the received electronic fuse control instruction, the upstream power distribution unit 103 sets the electronic fuses 183 and 184 to the on or off state.

[0330] Based on the received electronic fuse control instruction, the area ECU104 sets the electronic fuses 195 and 196 to the on or off state.

[0331] Based on the received electronic fuse control instruction, the area ECU105 sets the electronic fuses 215 and 216 to the on or off state.

[0332] Based on the received electronic fuse control instruction, the area ECU106 sets the electronic fuses 235, 236, and 237 to either the on or off state.

[0333] Based on the received electronic fuse control instruction, the area ECU107 sets the electronic fuses 255 and 256 to the on or off state.

[0334] The fault diagnosis device 90 of the first embodiment is connected to the central ECU101.

[0335] The fault diagnosis device 90 is configured to be detachable via a connector (not shown) and connected to the central ECU 101 during fault diagnosis. The fault diagnosis device 90 can obtain various information from the central ECU 101, regional ECUs 104-107, and ECUs 108-116, 118 via the central ECU 101, or can update the data stored in the central ECU 101, regional ECUs 104-107, and ECUs 108-116, 118.

[0336] like Figure 19 As shown, the storage unit 158 ​​of the central ECU 101 stores the storage connection checklist 167.

[0337] The upstream power distribution unit 102 further includes a current detection unit 175. The current detection unit 175 is configured to detect the current value flowing through the power supply paths 123 and 124, and output the power supply path current value information showing the detected current value to the central ECU 101 via the communication unit 172.

[0338] The upstream power distribution unit 103 further includes a current detection unit 185. The current detection unit 185 is configured to detect the current value flowing through the power supply paths 125 and 126, and output the power supply path current value information showing the detected current value to the central ECU 101 via the communication unit 172.

[0339] like Figure 20 As shown, the region ECU104 further includes a current detection unit 197. The current detection unit 197 is configured to detect the current value flowing through the power supply paths 127 and 128, and output the power supply path current value information showing the detected current value to the control unit 191.

[0340] The regional ECU 105 further includes a current detection unit 217. The current detection unit 217 is configured to detect the current value flowing through the power supply paths 129 and 130, and output the power supply path current value information showing the detected current value to the control unit 211.

[0341] like Figure 21As shown, the region ECU106 further includes a current detection unit 238. The current detection unit 238 is configured to detect the current values ​​flowing through the power supply paths 131, 132, and 133, and output the power supply path current value information showing the detected current values ​​to the control unit 231.

[0342] The regional ECU 107 further includes a current detection unit 257. The current detection unit 257 is configured to detect the current value flowing through the power supply paths 134 and 135, and output the power supply path current value information showing the detected current value to the control unit 251.

[0343] Connection checklist 167, etc. Figure 24 As shown, for each of the multiple electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 provided in the vehicle control system 100, the electronic fuse ID, the connected load type, and the desired current consumption value are set.

[0344] like Figure 24 As shown, in the connection check table 167 of this embodiment, for electronic fuse 195, the electronic fuse ID is set to "eFuse_1", the connection load category is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 108.

[0345] For electronic fuse 196, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "ECU", and the expected current consumption value is set to "150mA". This expected current consumption value corresponds to ECU 109.

[0346] For electronic fuse 215, the electronic fuse ID is set to "eFuse_3", the connected load type is set to "ECU", and the expected current consumption value is set to "100mA". This expected current consumption value corresponds to ECU 110.

[0347] For electronic fuse 216, the electronic fuse ID is set to "eFuse_4", the connected load type is set to "ECU", and the expected current consumption value is set to "250mA". This expected current consumption value corresponds to ECU 111.

[0348] For electronic fuse 235, the electronic fuse ID is set to "eFuse_5", the connected load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 112.

[0349] For electronic fuse 236, the electronic fuse ID is set to "eFuse_6", the connected load type is set to "ECU", and the expected current consumption value is set to "150mA". This expected current consumption value corresponds to ECU 113.

[0350] For electronic fuse 237, the electronic fuse ID is set to "eFuse_7", the connected load type is set to "ECU", and the expected current consumption value is set to "100mA". This expected current consumption value corresponds to ECU 114.

[0351] For electronic fuse 255, the electronic fuse ID is set to "eFuse_8", the connected load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 115.

[0352] For electronic fuse 256, the electronic fuse ID is set to "eFuse_9", the connected load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 116.

[0353] Next, the sequence of connection check processes performed by the control unit 151 of the central ECU 101 will be explained. The connection check process is a process that is repeatedly performed during the startup of the central ECU 101.

[0354] When the connection check process is executed, the CPU 161 of the control unit 151, as follows: Figure 25 As shown, in S410, it is determined whether the central ECU 101 is set to connection check mode. The control unit 151 of the central ECU 101 is configured to set the central ECU 101 to connection check mode when a connection check command is received from the fault diagnosis device 90.

[0355] Here, if the central ECU 101 is not set to connection check mode, the CPU 161 proceeds to S500. On the other hand, if the central ECU 101 is set to connection check mode, the CPU 161 sets the electronic fuse indicator value i set in RAM 163 to 0 in S420.

[0356] In S430, CPU161 increments the electronic fuse indicator value i (i.e., adds 1).

[0357] In step S440, CPU 161 sets the i-th electronic fuse (i.e., the electronic fuse whose electronic fuse ID is set to "eFuse_i") to the ON state. Furthermore, CPU 161 also sets the electronic fuse located upstream of the i-th electronic fuse to the ON state. For example, if electronic fuse 195 is set to the ON state, electronic fuse 173 is also set to the ON state.

[0358] In the S450, the CPU161 has a preset standby time in the on-state.

[0359] In S460, CPU161 acquires the power supply path current value information corresponding to the i-th electronic fuse. For example, the power supply path current value information corresponding to the first electronic fuse 195 is the power supply path current value information of power supply path 127, which is acquired from the current detection unit 197. Additionally, the power supply path current value information corresponding to the fifth electronic fuse 235 is the power supply path current value information of power supply path 131, which is acquired from the current detection unit 238.

[0360] In step S470, CPU161 performs a connection check on the i-th electronic fuse. Specifically, if the current value shown in the power supply path current value information obtained from S460 is above the connection determination value, CPU161 determines it to be "connected"; if the current value shown in the current value information obtained from S460 is below the connection determination value, it determines it to be "not connected". The connection determination value is obtained by multiplying the expected current consumption value of the i-th electronic fuse by a preset connection check ratio.

[0361] In S480, CPU161 stores the connection check result (i.e., the connection check result at S470) in storage unit 158 ​​for the i-th electronic fuse.

[0362] In S490, CPU161 determines whether the electronic fuse indicator value i is greater than or equal to the preset total number of electronic fuses n (9 in this embodiment). If the electronic fuse indicator value i is less than the total number of electronic fuses n, CPU161 proceeds to S430.

[0363] On the other hand, when the electronic fuse indicator value i is greater than or equal to the total number of electronic fuses n, the CPU161 switches to the S500.

[0364] When transitioning to S500, CPU161 determines whether the central ECU101 is connected to the fault diagnosis device 90. If the central ECU101 is not connected to the fault diagnosis device 90, CPU161 terminates the connection check process.

[0365] On the other hand, when the central ECU 101 is connected to the fault diagnosis device 90, the CPU 161 sends one or more connection check results stored in the storage unit 158 ​​that were not sent to the fault diagnosis device 90 to the fault diagnosis device 90 in S510, and ends the connection check process.

[0366] Furthermore, when a positive judgment is made in S490, the CPU161 of the central ECU101 sends a check completion notification indicating the end of the connection check process to the fault diagnosis device 90. The main ECU2 is configured to deactivate the connection check mode when it receives a connection check mode end command from the fault diagnosis device 90.

[0367] The central ECU 101 is configured to determine whether each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 is set to either an on or off state. The electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 are configured to switch between an on state that connects each of the power supply paths 127 to 135 and an off state that disconnects the power supply path, which supplies power from the battery 117 to the ECUs 108 to 116.

[0368] The central ECU 101 is configured to, in accordance with the above decision, set each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 to either an on or off state.

[0369] The central ECU 101 is configured such that, for each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256, after the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 become conductive, it acquires the power supply path current value information used to verify whether the ECUs 108 to 116 are connected to the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256.

[0370] Storage unit 158 ​​stores the expected current consumption value used for connection verification.

[0371] The central ECU 101 is configured to perform a connection check, which involves comparing the power supply path current value information with the expected current consumption value for each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 to determine whether ECUs 108 to 116 are connected to the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256.

[0372] Because such a central ECU101 can perform connection checks on whether ECUs108 to 116 are connected to electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 without the use of a special machine, the efficiency of connection checks can be improved.

[0373] In the embodiments described above, the central ECU 101 is equivalent to an inspection device and a second integrated control device, the battery 117 is equivalent to a power source, the ECUs 108 to 116 are equivalent to connecting loads and control devices, the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 are equivalent to power supply switching units, and the vehicle control system 100 is equivalent to an inspection system.

[0374] In addition, S420 to S430 are equivalent to the processing of the decision unit, S440 is equivalent to the processing of the conduction control unit, S460 is equivalent to the processing of the information acquisition unit, S470 is equivalent to the processing of the connection check unit, S480 is equivalent to the processing of the connection check result storage unit, and S510 is equivalent to the processing of the connection check result transmission unit.

[0375] In addition, the power supply path current value information is equivalent to the first verification information, the expected current consumption value is equivalent to the second verification information, and the area ECU104~107 is equivalent to the first integrated control device.

[0376] [Eighth Implementation Method]

[0377] The following and appendix Figure 1 The eighth embodiment of this disclosure will now be described. Furthermore, in the eighth embodiment, the parts that differ from the seventh embodiment will be described. Common structural elements will be indicated by the same reference numerals.

[0378] like Figure 26As shown, the difference between the vehicle control system 100 of the eighth embodiment and the seventh embodiment is that the structure of the start-up table 165 of the central ECU 101 is changed. That is, in the start-up table 165 of the eighth embodiment, a start-up group is set for each event. In other words, in the start-up table 165 of the eighth embodiment, the correspondence between the start-up group and the slave ECU set to the wake-up state is not set.

[0379] like Figure 27 As shown, the storage unit 194 of the region ECU104 further stores the start table 205, which will be described later, unlike the seventh embodiment.

[0380] The storage unit 214 of the region ECU105 further stores the start table 225, which will be described later, unlike the seventh embodiment.

[0381] like Figure 28 As shown, the storage unit 234 of the region ECU106 further stores the start table 245, which will be described later, unlike the seventh embodiment.

[0382] The storage unit 254 of the region ECU107 further stores the start table 265, which will be described later, unlike the seventh embodiment.

[0383] like Figure 26 As shown, in the start table 205, a correspondence is set between the start groups and the slave ECUs 108, 109, and 118 under the region ECU 104, which are set to be in a wake-up state. The start table 205 further sets a correspondence between the slave ECUs 108, 109, and 118 and the electronic fuses connected to them.

[0384] In the start table 225, a correspondence is set between the start groups and the slave ECUs 110 and 111 under the region ECU 105, and the slave ECUs set to the wake-up state. In the start table 225, a correspondence is further set between the slave ECUs 110 and 111 and the electronic fuses connected to the slave ECUs 110 and 111.

[0385] In Startup Table 245, a correspondence is set between the startup groups and the slave ECUs 112, 113, and 114 under Region ECU 106, which are set to be in a wake-up state. In Startup Table 225, a correspondence is further set between the slave ECUs 112, 113, and 114 and the electronic fuses connected to the slave ECUs 112, 113, and 114.

[0386] In Startup Table 265, a correspondence is set between the startup groups and the slave ECUs 115 and 116 under the region ECU 107, which are set to be in the wake-up state. In Startup Table 265, a correspondence is further set between the slave ECUs 115 and 116 and the electronic fuses connected to the slave ECUs 115 and 116.

[0387] When the central ECU 101 detects an event, it determines the starting group based on the detected event and by referring to the starting table 165.

[0388] When the central ECU101 receives an NM frame, it determines that the communication group corresponding to the bit set to 1 in the received NM frame is the start group.

[0389] The central ECU 101 begins processing NM frames indicating the start-up group determined by the detection of the event or the reception of NM frames to the regional ECUs 104, 105, 106, and 107. Once the central ECU 101 begins sending NM frames, it subsequently sends the same NM frames periodically thereafter.

[0390] When regional ECUs 104, 105, 106, and 107 receive an NM frame, they forward the received NM frame to their subordinate slave ECUs.

[0391] Based on the received NM frame, regional ECUs 104, 105, 106, and 107 refer to start tables 205, 225, 245, and 265 to set the electronic fuses corresponding to the start group shown in the NM frame to the ON state for their subordinate slave ECUs, and set the electronic fuses other than the electronic fuses corresponding to the start group to the OFF state.

[0392] like Figure 27 As shown, storage connection checklist 207 is for storage unit 194 of region ECU 104. Storage connection checklist 227 is for storage unit 214 of region ECU 105.

[0393] like Figure 28 As shown, storage connection checklist 247 is for storage unit 234 of region ECU 106. Storage connection checklist 267 is for storage unit 254 of region ECU 107.

[0394] like Figure 29 As shown, the connection checklist 207 sets the electronic fuse ID, connected load type, and expected current consumption value for each of the multiple electronic fuses 195, 196 provided in the region ECU 104.

[0395] In the connection checklist 207 of this embodiment, for electronic fuse 195, the electronic fuse ID is set to "eFuse_1", the connection load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 108.

[0396] For electronic fuse 196, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "ECU", and the expected current consumption value is set to "150mA". This expected current consumption value corresponds to ECU 109.

[0397] Connection checklist 227 sets the electronic fuse ID, connected load type, and expected current consumption value for each of the multiple electronic fuses 215, 216 provided in area ECU 105.

[0398] In the connection checklist 227 of this embodiment, for electronic fuse 215, the electronic fuse ID is set to "eFuse_1", the connection load type is set to "ECU", and the expected current consumption value is set to "100mA". This expected current consumption value corresponds to ECU 110.

[0399] For electronic fuse 216, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "ECU", and the expected current consumption value is set to "250mA". This expected current consumption value corresponds to ECU 111.

[0400] The connection checklist 247 sets the electronic fuse ID, connected load type, and expected current consumption value for each of the multiple electronic fuses 235, 236, and 237 in the region ECU 106.

[0401] In the connection checklist 247 of this embodiment, for electronic fuse 235, the electronic fuse ID is set to "eFuse_1", the connection load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 112.

[0402] For electronic fuse 236, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "ECU", and the expected current consumption value is set to "150mA". This expected current consumption value corresponds to ECU 113.

[0403] For electronic fuse 237, the electronic fuse ID is set to "eFuse_3", the connected load type is set to "ECU", and the expected current consumption value is set to "100mA". This expected current consumption value corresponds to ECU 114.

[0404] Connection checklist 267 sets the electronic fuse ID, connected load type, and expected current consumption value for each of the multiple electronic fuses 255, 256 provided in area ECU 107.

[0405] In the connection checklist 267 of this embodiment, for electronic fuse 255, the electronic fuse ID is set to "eFuse_1", the connection load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 115.

[0406] For electronic fuse 256, the electronic fuse ID is set to "eFuse_2", the connected load type is set to "ECU", and the expected current consumption value is set to "200mA". This expected current consumption value corresponds to ECU 116.

[0407] Next, the sequence of the connection check process in the eighth embodiment will be explained. The connection check process in the eighth embodiment is a process repeatedly executed by the control units 191, 211, 231, and 251 of the region ECUs 104, 105, 106, and 107 during the startup of the region ECUs 104, 105, 106, and 107. Hereinafter, the sequence of the connection check process will be explained by representing region ECU 104.

[0408] When the connection check process is executed, the CPU 161 of the control unit 191 of the area ECU 104, as follows: Figure 30 As shown, in S610, it is determined whether the central ECU 101 is set to connection check mode. The control unit 151 of the central ECU 101 is configured to set the central ECU 101 to connection check mode when a connection check command is received from the fault diagnosis device 90.

[0409] Here, if the central ECU 101 is not set to connection check mode, the CPU 201 proceeds to S700. On the other hand, if the central ECU 101 is set to connection check mode, the CPU 201 sets the electronic fuse indicator value i set in RAM 203 to 0 in S620.

[0410] In S630, CPU201 increments the electronic fuse indicator value i (i.e., adds 1).

[0411] In S640, CPU201 sets the i-th electronic fuse (i.e., the electronic fuse whose electronic fuse ID is set as "eFuse_i") to the ON state.

[0412] In the S650, CPU201 has a preset standby time in the on-state.

[0413] In S660, CPU201 acquires the power supply path current value information corresponding to the i-th electronic fuse. For example, the power supply path current value information corresponding to electronic fuse 195, which is the first electronic fuse, is the power supply path current value information of power supply path 127, which is acquired from the current detection unit 197. Similarly, the power supply path current value information corresponding to electronic fuse 196, which is the second electronic fuse, is the power supply path current value information of power supply path 127, which is also acquired from the current detection unit 197.

[0414] In step S670, CPU201 performs a connection check on the i-th electronic fuse. Specifically, if the current value shown in the power supply path current value information obtained from step S660 is above the connection determination value, CPU201 determines it to be "connected"; if the current value shown in the current value information obtained from step S660 is below the connection determination value, it determines it to be "not connected". The connection determination value is obtained by multiplying the expected current consumption value of the i-th electronic fuse by a preset connection check ratio.

[0415] In S680, CPU201 stores the connection check result (i.e., the connection check result at S670) in storage unit 194 for the i-th electronic fuse.

[0416] In S690, CPU201 determines whether the electronic fuse indicator value i is greater than or equal to the preset total number of electronic fuses n (2 in this embodiment). If the electronic fuse indicator value i is less than the total number of electronic fuses n, CPU201 proceeds to S630.

[0417] On the other hand, when the electronic fuse indicator value i is greater than or equal to the total number of electronic fuses n, the CPU161 switches to the S700.

[0418] When transitioning to S700, CPU201 determines whether the central ECU101 is connected to the fault diagnosis device 90. If the central ECU101 is not connected to the fault diagnosis device 90, CPU201 terminates the connection check process.

[0419] On the other hand, when the central ECU 101 is connected to the fault diagnosis device 90, the CPU 201 sends one or more connection check results stored in the storage unit 194 that were not sent to the fault diagnosis device 90 to the fault diagnosis device 90 in S710, and ends the connection check process.

[0420] The ECU 104 configured in this way determines whether each of the electronic fuses 195 and 196 is set to an on or off state. The electronic fuses 195 and 196 are configured to switch between an on state that connects the power supply from the battery 117 to each of the power supply paths 127 and 128 from the ECUs 108 and 109, and an off state that disconnects the power supply path.

[0421] The region ECU104 is configured to, in accordance with the above decision, set each of the electronic fuses 195 and 196 to either an on or off state.

[0422] The region ECU104 is configured such that, for each of the electronic fuses 195 and 196, after the electronic fuses 195 and 196 become in the on state, it acquires the power supply path current value information used for verifying whether the ECUs 108 and 109 are connected to the electronic fuses 195 and 196.

[0423] Storage unit 194 stores the expected current consumption value used for connection verification.

[0424] The region ECU104 is configured to perform a connection check, which is to determine whether ECU108 and 109 are connected to electronic fuses 195 and 196 by comparing the power supply path current value information with the expected current consumption value for each of the electronic fuses 195 and 196.

[0425] Because this area ECU104 can be checked without using special equipment to check whether ECU108 and 109 are connected to electronic fuses 195 and 196, the efficiency of connection checks can be improved.

[0426] In the embodiments described above, the regional ECUs 104 to 107 correspond to the inspection device and the first integrated control device, while the ECUs 108 to 116 correspond to the connected load and the slave control device.

[0427] In addition, S620 to S630 are equivalent to the processing of the decision unit, S640 is equivalent to the processing of the conduction control unit, S660 is equivalent to the processing of the information acquisition unit, S670 is equivalent to the processing of the connection check unit, S680 is equivalent to the processing of the connection check result storage unit, and S710 is equivalent to the processing of the connection check result transmission unit.

[0428] In addition, the power supply path current value information is equivalent to the first verification information, and the expected current consumption value is equivalent to the second verification information.

[0429] [Ninth Implementation Method]

[0430] The following and appendix Figure 1 The ninth embodiment of this disclosure will now be described. Furthermore, in the ninth embodiment, the parts that differ from the seventh embodiment will be described. Common structural elements will be indicated with the same reference numerals.

[0431] The difference between the vehicle control system 100 of the ninth embodiment and the seventh embodiment lies in the changes made to the structure of the vehicle control system 100 and the fact that communication connection check processing is performed instead of connection check processing.

[0432] like Figure 31 As shown, the difference between the vehicle control system 100 of the ninth embodiment and the seventh embodiment is that the storage unit 158 ​​has a communication connection check table 169 instead of the connection check table 167.

[0433] Communication connection checklist 169 Figure 32 As shown, for each of the multiple electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 provided in the vehicle control system 100, an electronic fuse ID and an ECUID for identifying the connected ECU are set.

[0434] In the communication connection checklist 169 of this embodiment, for the electronic fuse 195, it is set as “eFuse_1” as the electronic fuse ID and as “ECU_A” as the ECU ID.

[0435] For electronic fuse 196, the electronic fuse ID is set as "eFuse_2" and the ECU ID is set as "ECU_B".

[0436] For electronic fuse 215, it is set as “eFuse_3” as electronic fuse ID and as “ECU_C” as ECU ID.

[0437] For electronic fuse 216, it is set as “eFuse_4” as electronic fuse ID and as “ECU_D” as ECU ID.

[0438] For electronic fuse 235, it is set as “eFuse_5” as electronic fuse ID and as “ECU_E” as ECU ID.

[0439] For electronic fuse 236, it is set as “eFuse_6” as electronic fuse ID and as “ECU_F” as ECU ID.

[0440] For electronic fuse 237, it is set as “eFuse_7” as electronic fuse ID and as “ECU_G” as ECU ID.

[0441] For electronic fuse 255, the electronic fuse ID is set as "eFuse_8" and the ECU ID is set as "ECU_H".

[0442] For electronic fuse 256, it is set as “eFuse_9” as electronic fuse ID and as “ECU_I” as ECU ID.

[0443] Next, the sequence of communication connection check processes performed by the control unit 151 of the central ECU 101 will be explained. The communication connection check process is a process that is repeatedly performed during the startup of the central ECU 101.

[0444] When the communication connection check process is executed, the CPU 161 of the control unit 151, as follows: Figure 33 As shown, in S810, it is determined whether the central ECU 101 is set to communication connection check mode. The control unit 11 of the central ECU 101 is configured to set the central ECU 101 to communication connection check mode when it receives a communication connection check command from the fault diagnosis device 90.

[0445] Here, if the central ECU 101 is not set to communication connection check mode, the CPU 161 proceeds to S910. On the other hand, if the central ECU 101 is set to communication connection check mode, the CPU 161 sets the electronic fuse indicator value i set in RAM 163 to 0 in S820.

[0446] In the S830, CPU161 increments the electronic fuse indicator value i.

[0447] In S840, CPU161 sets the i-th electronic fuse to the ON state. Furthermore, CPU161 also sets the electronic fuse located upstream of the i-th electronic fuse to the ON state. For example, if electronic fuse 195 is set to the ON state, electronic fuse 173 is also set to the ON state.

[0448] In the S850, the CPU161 has a preset standby time in the on-state.

[0449] In the S860, CPU161 sends an ID request to the ECU connected to the i-th electronic fuse.

[0450] In the S870, CPU161 receives the ECUID from the ECU connected to the i-th electronic fuse.

[0451] In S880, CPU161 performs a communication connection check on the i-th electronic fuse. Specifically, CPU161 determines whether the ECUID received by S870 matches the ECUID set for the i-th electronic fuse in the communication connection check table 169. If the ECUID received by S870 does not match the ECUID set for the i-th electronic fuse in the communication connection check table 169, CPU161 determines it as "incorrect assembly". Conversely, if the ECUID received by S870 matches the ECUID set for the i-th electronic fuse in the communication connection check table 169, CPU161 determines it as "correct assembly".

[0452] In S890, CPU161 stores the communication connection check result (i.e., the communication connection check result at S880) in storage unit 158 ​​for the i-th electronic fuse.

[0453] In S900, CPU161 determines whether the electronic fuse indicator value i is greater than or equal to the preset total number of electronic fuses n (9 in this embodiment). If the electronic fuse indicator value i is less than the total number of electronic fuses n, CPU161 proceeds to S830.

[0454] On the other hand, when the electronic fuse indicator value i is greater than or equal to the total number of electronic fuses n, the CPU161 switches to the S910.

[0455] When transitioning to S910, CPU161 determines whether the central ECU101 is connected to the fault diagnosis device 90. If the central ECU101 is not connected to the fault diagnosis device 90, CPU161 terminates the communication connection check process.

[0456] On the other hand, when the central ECU 101 is connected to the fault diagnosis device 90, in S920, the CPU 161 sends the communication connection check results that were not sent to the fault diagnosis device 90 from one or more communication connection check results stored in the storage unit 158 ​​to the fault diagnosis device 90, and ends the communication connection check process.

[0457] The central ECU 101 is configured to determine whether each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 is set to either an on or off state. The electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 are configured to switch between an on state that connects each of the power supply paths 127 to 135 and an off state that disconnects the power supply path, which supplies power from the battery 117 to the ECUs 108 to 116.

[0458] The central ECU 101 is configured to, in accordance with the above decision, set each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 to either an on or off state.

[0459] The central ECU 101 is configured such that, for each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256, after the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 become conductive, it acquires an ECUID used for verifying whether ECUs 108 to 116 are connected to the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256.

[0460] Storage unit 158 ​​stores the ECUID used for connection verification.

[0461] The central ECU 101 is configured to perform a connection check, which involves comparing the acquired ECUID with the stored ECUID for each of the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 to determine whether ECUs 108 to 116 are connected to the electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256.

[0462] Because such a central ECU101 can perform connection checks on whether ECUs108 to 116 are connected to electronic fuses 195, 196, 215, 216, 235, 236, 237, 255, and 256 without the use of a special machine, the efficiency of connection checks can be improved.

[0463] In the embodiments described above, S820 to S830 are equivalent to the processing of the decision unit, S840 is equivalent to the processing of the conduction control unit, S860 is equivalent to the processing of the information acquisition unit, and S870 is equivalent to the processing of the connection check unit.

[0464] In addition, the ECUID received by the central ECU101 is equivalent to load identification information and first verification information, and the ECUID set in the communication connection check table 169 is equivalent to reasonable identification information and second verification information.

[0465] In addition, S890 is equivalent to the processing unit for storing communication connection check results, and S920 is equivalent to the processing unit for sending communication connection check results.

[0466] While one embodiment of the present disclosure has been described above, the present disclosure is not limited to the above embodiment and can be implemented in various ways.

[0467] [Variation Example 1]

[0468] In the above embodiment, the vehicle control system 1 is shown to have two electronic fuses 14 and 15. However, the vehicle control system 1 may be configured to have one electronic fuse or to have three or more electronic fuses.

[0469] [Variation Example 2]

[0470] In the above embodiment, a form indicating "connected" or "not connected" as a connection check result is shown. However, the connection check result may also include at least one of the following: current value information showing the current value measured by electronic fuses 14 and 15, and a judgment reason for determining that a connected load is not connected to electronic fuses 14 and 15 when it is determined that a connected load is not connected to electronic fuses 14 and 15. A judgment reason for determining that a connected load is not connected to electronic fuses 14 and 15 may be, for example, the judgment result at S70 and the judgment result at S72. That is, the judgment result at S70 is that the current value shown in the current value information is less than the connection determination value. The judgment result at S72 is that the difference between the total expected current consumption value of the multiple connected loads connected to the electronic fuse and the current value shown in the current value information is close to the expected current consumption value of one connected load connected to the electronic fuse.

[0471] [Variation Example 3]

[0472] In the above embodiment, the connection check result or communication connection check result is shown to be sent to the fault diagnosis device 90, but it can also be sent to a server located outside the main ECU2.

[0473] [Variation Example 4]

[0474] In the above embodiments, the electronic fuses 14 and 15 are shown to turn on or off the power supply paths 9 and 10, but relays can also be used instead of electronic fuses 14 and 15.

[0475] [Variation Example 5]

[0476] In the above embodiment, a connection check is shown using current value information obtained from electronic fuses 14 and 15, but connection checks can also be performed using power supply path current value information obtained from current detection unit 16.

[0477] [Variation Example 6]

[0478] The above embodiment illustrates a CAN communication configuration between the master ECU2 and slave ECUs 3, 4, and 5. However, the communication between the master ECU2 and slave ECUs 3, 4, and 5 is not limited to CAN; for example, it could also be Ethernet communication or LIN communication. LIN is an abbreviation for Local Interconnect Network. Ethernet is a registered trademark.

[0479] [Variation Example 7]

[0480] In the seventh embodiment described above, a configuration is shown in which the central ECU 101 performs connection check processing on its subordinate ECUs 108 to 116. However, it is also possible for the central ECU 101 to perform connection check processing on its subordinate regional ECUs 104 to 107. In this case, the central ECU 101 acts as a check device, and the regional ECUs 104 to 107 act as connection loads.

[0481] [Variation Example 8]

[0482] In the eighth embodiment described above, a configuration is shown where the regional ECU 104 performs connection check processing on its subordinate ECUs 108 and 109. However, the upstream power distribution unit 102 may also perform connection check processing on its subordinate regional ECUs 104 and 105. Alternatively, the upstream power distribution unit 103 may perform connection check processing on its subordinate regional ECUs 106 and 107. However, for the upstream power distribution units 102 and 103 to perform the connection check processing, they need to replace the control circuits 171 and 181 with a control unit centered on a microcomputer equipped with a CPU, ROM, and RAM. In this case, the upstream power distribution units 102 and 103 function as checking devices, and the regional ECUs 104 to 107 function as connection loads.

[0483] The control units 11, 151, 191 and their methods described in this disclosure can be implemented by a dedicated computer provided that consists of a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control units 11, 151, 191 and their methods described in this disclosure can be implemented by a dedicated computer provided that consists of a processor configured with one or more dedicated hardware logic circuits. Alternatively, the control units 11, 151, 191 and their methods described in this disclosure can be implemented by one or more dedicated computers composed of a processor and memory programmed to perform one or more functions and a processor configured with one or more hardware logic circuits. Furthermore, the computer program, as instructions executed by the computer, can be stored in a computer-readable, non-transient tangible recording medium. The methods for implementing the functions of each unit included in the control units 11, 151, 191 do not necessarily require software; all functions can be implemented using one or more hardware components.

[0484] In the above embodiments, the multiple functions of one component can be implemented by multiple components, or the single function of one component can be implemented by multiple components. Furthermore, the multiple functions of multiple components can be implemented by one component, or the single function implemented by multiple components can be implemented by one component. Additionally, a portion of the structure in the above embodiments can be omitted. Furthermore, at least a portion of the structure in the above embodiments can be added to or replaced with the structure of other above embodiments.

[0485] In addition to the main ECU2, central ECU101 and regional ECUs104-107 described above, this disclosure can be implemented in various forms, such as a system that includes the main ECU2, central ECU101 and regional ECUs104-107 as constituent elements, a program that enables the computer to function as the main ECU2, central ECU101 and regional ECUs104-107, a non-transient physical recording medium such as a semiconductor memory that records the program, and an inspection method.

[0486] [The technical concepts disclosed in this specification]

[0487] [Project 1]

[0488] An inspection device (2, 101-107) comprises:

[0489] The decision unit (S20-S30, S220-S230, S420-S430, S620-S630, S820-S830) is configured to determine whether to set each of one or more power supply switching units (14, 15, 173, 174, 183, 184, 195, 196, 215, 216, 235, 236, 237, 255, 256) to a conducting state or a disconnected state. The one or more power supply switching units are configured to switch between a conducting state that turns on each of one or more power supply paths (9, 10, 123-135) and a disconnected state that turns off the power supply path. The one or more power supply paths supply power from the power source (7, 117) to one or more connected loads (3, 4, 5, 50, 60, 104-116).

[0490] The conduction control unit (S40, S240, S440, S640, S840) is configured to set each of one or more of the power supply switching units to the conduction state or the disconnection state according to the decision made by the decision unit.

[0491] The information acquisition unit (S60, S64, S66, 14, 15, 16, 17, S260, S270, S460, S660, S870) is configured to acquire, for each of the one or more power supply switching units, first verification information for verifying whether the connected load is connected to the power supply switching unit after the power supply switching unit changes to the conducting state;

[0492] Storage units (13, 158, 194, 214, 234, 254) store second verification information (25, 27, 167, 169, 207, 227, 247, 267) used for the connection verification; and

[0493] The connection checking unit (S70, S72, S74, S76, S280, S470, S670, S880) is configured to perform a connection check to determine whether one or more of the connected loads are connected to the power supply switching unit by comparing the first verification information and the second verification information for each of the one or more power supply switching units.

[0494] [Project 2]

[0495] The inspection device as described in Project 1, wherein...

[0496] The first verification information is at least one of current value information showing the value of the current flowing through the power supply path and voltage value information showing the value of the voltage applied to the power supply path.

[0497] The second verification information is, for each of the one or more power supply switching units, one or more pre-set current consumption values ​​as the current consumption values ​​of one or more connected loads connected to the power supply switching unit and receiving power from the power source, and for each of the one or more power supply switching units, a pre-set power supply path voltage value as the voltage applied to the power supply path connected to the power supply switching unit.

[0498] The connection check unit (S70, S72, S74, S76, S470, S670) is configured to perform the connection check by comparing one or more of the consumed current values ​​with the current values ​​shown in the current value information for each of the one or more power supply switching units, and comparing the power supply path voltage value with the voltage value shown in the voltage value information for each of the one or more power supply switching units.

[0499] [Project 3]

[0500] The inspection device as described in Project 2, wherein...

[0501] The connection inspection unit (S72) is configured such that,

[0502] When multiple connected loads are connected to the power supply switching unit, the connected loads not connected to the power supply switching unit are determined by comparing the sum of the multiple current consumption values ​​of each of the multiple connected loads with the difference between the current values ​​shown in the current value information and the multiple current consumption values.

[0503] [Project 4]

[0504] The inspection device as described in Item 2 or Item 3 further comprises:

[0505] A connection check result storage unit (S80, S82, S480, S680), configured to store the check results obtained by the connection check unit; and

[0506] The connection inspection result sending unit (S110, S112, S510, S710) is configured to send the inspection result stored in the connection inspection result storage unit to an external device provided outside the inspection device.

[0507] [Project 5]

[0508] The inspection device as described in any one of items 2 to 4, wherein...

[0509] The inspection result obtained by the connection inspection unit includes at least one of the current value information and the judgment reason.

[0510] The reason for this judgment is that the connected load is not connected to the power supply switching unit when it is determined that the connected load is not connected to the power supply switching unit.

[0511] [Project 6]

[0512] The inspection device as described in Project 1, wherein...

[0513] The first verification information is load identification information used to identify the connection load.

[0514] The information acquisition unit (S270, S870) is configured to acquire the first verification information by receiving the load identification information from the connection load connected to the power supply switching unit for each of the one or more power supply switching units.

[0515] The second verification information is a pre-set reasonable identification information for each of one or more power supply switching units, which identifies a pre-set reasonable connection load as the connection load connected to the power supply switching unit.

[0516] The connection checking unit (S280, S880) is configured such that, as part of the connection checking, for each of the one or more power supply switching units, if the reasonable identification information matches the load identification information acquired by the information acquisition unit, it is determined that a reasonable connection load is connected to the power supply switching unit; if the reasonable identification information does not match the load identification information, it is determined that no reasonable connection load is connected to the power supply switching unit.

[0517] [Project 7]

[0518] The inspection device as described in Item 6 further comprises:

[0519] A communication connection check result storage unit (S290, S890) configured to store the check result obtained by the connection check unit; and

[0520] The communication connection check result sending unit (S320, S920) is configured to send the check result stored in the communication connection check result storage unit to an external device provided outside the check device.

[0521] [Project 8]

[0522] The inspection device as described in any one of items 1 to 7, wherein...

[0523] When the inspection device is set to a connection inspection mode for performing the connection inspection, the decision unit, the conduction control unit, the information acquisition unit, and the connection inspection unit are respectively configured to perform the processing of the decision unit, the conduction control unit, the information acquisition unit, and the connection inspection unit.

[0524] [Project 9]

[0525] An inspection system (1, 100) includes one or more power supply switching units (14, 15, 173, 174, 183, 184, 195, 196, 215, 216, 235, 236, 237, 255, 256) and inspection devices (2, 101-107). The one or more power supply switching units are configured to switch between an on state that turns on each of one or more power supply paths (9, 10, 123-135) and an off state that turns off the power supply path. The one or more power supply paths supply power from a power source (7, 117) to one or more connected loads (3, 4, 5, 50, 60, 104-116). The inspection devices are configured to control the operation of the one or more power supply switching units.

[0526] The inspection device includes:

[0527] The decision unit (S20-S30, S220-S230, S420-S430, S620-S630, S820-S830) is configured to determine whether to set to the on state or the off state for each of one or more of the power supply switching units (14, 15, 173, 174, 183, 184, 195, 196, 215, 216, 235, 236, 237, 255, 256).

[0528] The conduction control unit (S40, S240, S440, S640, S840) is configured to set each of one or more of the power supply switching units to the conduction state or the disconnection state according to the decision made by the decision unit.

[0529] The information acquisition unit (S60, S64, S66, 14, 15, 16, 17, S260, S270, S460, S660, S870) is configured to acquire, for each of the one or more power supply switching units, first verification information for verifying whether the connected load is connected to the power supply switching unit after the power supply switching unit changes to the conducting state;

[0530] Storage units (13, 158, 194, 214, 234, 254) store second verification information (25, 27, 167, 169, 207, 227, 247, 267) used for the connection verification; and

[0531] The connection checking unit (S70, S72, S74, S76, S280, S470, S670, S880) is configured to perform a connection check to determine whether one or more of the connected loads are connected to the power supply switching unit by comparing the first verification information and the second verification information for each of the one or more power supply switching units.

[0532] [Project 10]

[0533] The inspection system (1) described in Project 9, wherein,

[0534] The inspection system includes:

[0535] The slave control device (3, 4) serves as the connected load; and

[0536] The main control device (2) serves as the inspection device. The main control device is connected to the slave control device in a manner that enables data communication, and includes one or more of the power supply switching units (14, 15).

[0537] [Project 11]

[0538] The inspection system (100) described in Project 9, wherein,

[0539] The inspection system includes:

[0540] The slave control device (108-116) serves as the connected load;

[0541] A first integrated control device (104-107) is connected to the slave control device in a manner capable of data communication, and includes one or more of the power supply switching units (195, 196, 215, 216, 235, 236, 237, 255, 256); and

[0542] A second integrated control device (101) serves as the inspection device, and is connected to the first integrated control device in a manner capable of data communication.

[0543] The slave control device and the second integrated control device are connected via the first integrated control device in a manner that enables data communication between them.

[0544] [Project 12]

[0545] The inspection system (100) described in Project 9, wherein,

[0546] The inspection system includes:

[0547] The slave control device (108-116) serves as the connected load;

[0548] A first integrated control device (104-107), which serves as the inspection device, is connected to the slave control device in a manner capable of data communication, and includes one or more of the power supply switching units (195, 196, 215, 216, 235, 236, 237, 255, 256); and

[0549] A second integrated control device (101) is connected to the first integrated control device in a manner that enables data communication.

[0550] The slave control device and the second integrated control device are connected via the first integrated control device in a manner that enables data communication between them.

[0551] [Project 13]

[0552] The inspection system (100) described in Project 9, wherein,

[0553] The inspection system includes:

[0554] From the control device (108-116);

[0555] A first integrated control device (104-107) serves as the connected load, and the first integrated control device is connected to the slave control device in a manner that enables data communication.

[0556] An upstream power distribution unit (102, 103), the upstream power distribution unit comprising one or more of the aforementioned power switching units (173, 174, 183, 184); and

[0557] The second integrated control device (101) serves as the inspection device and is connected to the first integrated control device and the upstream power distribution unit in a manner that enables data communication.

[0558] [Project 14]

[0559] The inspection system (100) described in Project 9, wherein,

[0560] The inspection system includes:

[0561] From the control device (108-116);

[0562] A first integrated control device (104-107) serves as the connected load, and the first integrated control device is connected to the slave control device in a manner that enables data communication.

[0563] An upstream power distribution unit (102, 103), which serves as the inspection device, includes one or more of the power supply switching units (173, 174, 183, 184); and

[0564] The second integrated control device (101) is connected to the first integrated control device and the upstream power distribution unit in a manner that enables data communication.

Claims

1. An inspection device (2, 101-107), characterized in that, have: The decision unit (S20-S30, S220-S230, S420-S430, S620-S630, S820-S830) is configured to determine whether to set each of one or more power supply switching units (14, 15, 173, 174, 183, 184, 195, 196, 215, 216, 235, 236, 237, 255, 256) to a conducting state or a disconnected state. The one or more power supply switching units are configured to switch between a conducting state that turns on each of one or more power supply paths (9, 10, 123-135) and a disconnected state that turns off the power supply path. The one or more power supply paths supply power from the power source (7, 117) to one or more connected loads (3, 4, 5, 50, 60, 104-116). The conduction control unit (S40, S240, S440, S640, S840) is configured to set each of one or more of the power supply switching units to the conduction state or the disconnection state according to the decision made by the decision unit. The information acquisition unit (S60, S64, S66, 14, 15, 16, 17, S260, S270, S460, S660, S870) is configured to acquire, for each of the one or more power supply switching units, first verification information for verifying whether the connected load is connected to the power supply switching unit after the power supply switching unit changes to the conducting state; Storage units (13, 158, 194, 214, 234, 254) store second verification information (25, 27, 167, 169, 207, 227, 247, 267) used for the connection verification; and The connection checking unit (S70, S72, S74, S76, S280, S470, S670, S880) is configured to perform a connection check to determine whether one or more of the connected loads are connected to the power supply switching unit by comparing the first verification information and the second verification information for each of the one or more power supply switching units.

2. The inspection device as described in claim 1, characterized in that, The first verification information is at least one of current value information showing the value of the current flowing through the power supply path and voltage value information showing the value of the voltage applied to the power supply path. The second verification information is, for each of the one or more power supply switching units, one or more pre-set current consumption values ​​as the current consumption values ​​of one or more connected loads connected to the power supply switching unit and receiving power from the power source, and for each of the one or more power supply switching units, a pre-set power supply path voltage value as the voltage applied to the power supply path connected to the power supply switching unit. The connection check unit (S70, S72, S74, S76, S470, S670) is configured to perform the connection check by comparing one or more of the consumed current values ​​with the current values ​​shown in the current value information for each of the one or more power supply switching units, and comparing the power supply path voltage value with the voltage value shown in the voltage value information for each of the one or more power supply switching units.

3. The inspection device as described in claim 2, characterized in that, The connection checking unit (S72) is configured to determine, when multiple connection loads are connected to the power supply switching unit, a connection load that is not connected to the power supply switching unit by comparing the sum of the multiple current consumption values ​​of each of the multiple connection loads with the difference between the current values ​​shown in the current value information and the multiple current consumption values.

4. The inspection device as described in claim 2 or 3, characterized in that, Further features include: A connection check result storage unit (S80, S82, S480, S680), configured to store the check results obtained by the connection check unit; and The connection inspection result sending unit (S110, S112, S510, S710) is configured to send the inspection result stored in the connection inspection result storage unit to an external device provided outside the inspection device.

5. The inspection device as described in claim 2 or 3, characterized in that, The inspection result obtained by the connection inspection unit includes at least one of the current value information and the judgment reason. The reason for this judgment is that the connected load is not connected to the power supply switching unit when it is determined that the connected load is not connected to the power supply switching unit.

6. The inspection device as claimed in claim 1, characterized in that, The first verification information is load identification information used to identify the connection load. The information acquisition unit (S270, S870) is configured to acquire the first verification information by receiving the load identification information from the connection load connected to the power supply switching unit for each of the one or more power supply switching units. The second verification information is a pre-set reasonable identification information for each of one or more power supply switching units, which identifies a pre-set reasonable connection load as the connection load connected to the power supply switching unit. The connection checking unit (S280, S880) is configured such that, as part of the connection checking, for each of the one or more power supply switching units, if the reasonable identification information matches the load identification information acquired by the information acquisition unit, it is determined that a reasonable connection load is connected to the power supply switching unit; if the reasonable identification information does not match the load identification information, it is determined that no reasonable connection load is connected to the power supply switching unit.

7. The inspection device as claimed in claim 6, characterized in that, Further features include: A communication connection check result storage unit (S290, S890) configured to store the check result obtained by the connection check unit; and The communication connection check result sending unit (S320, S920) is configured to send the check result stored in the communication connection check result storage unit to an external device provided outside the check device.

8. The inspection device according to any one of claims 1, 2, and 6, characterized in that, When the inspection device is set to a connection inspection mode for performing the connection inspection, the decision unit, the conduction control unit, the information acquisition unit, and the connection inspection unit are respectively configured to perform the processing of the decision unit, the conduction control unit, the information acquisition unit, and the connection inspection unit.

9. An inspection system (1, 100) comprising one or more power supply switching units (14, 15, 173, 174, 183, 184, 195, 196, 215, 216, 235, 236, 237, 255, 256) and an inspection device (2, 101-107), wherein the one or more power supply switching units are configured to switch between an on state that turns on each of the one or more power supply paths (9, 10, 123-135) and an off state that turns off the power supply path, wherein the one or more power supply paths supply power from a power source (7, 117) to one or more connected loads (3, 4, 5, 50, 60, 104-116), and the inspection device is configured to control the operation of the one or more power supply switching units, characterized in that, The inspection device includes: The decision unit (S20-S30, S220-S230, S420-S430, S620-S630, S820-S830) is configured to determine whether to set to the on state or the off state for each of one or more of the power supply switching units (14, 15, 173, 174, 183, 184, 195, 196, 215, 216, 235, 236, 237, 255, 256). The conduction control unit (S40, S240, S440, S640, S840) is configured to set each of one or more of the power supply switching units to the conduction state or the disconnection state according to the decision made by the decision unit. The information acquisition unit (S60, S64, S66, 14, 15, 16, 17, S260, S270, S460, S660, S870) is configured to acquire, for each of the one or more power supply switching units, first verification information for verifying whether the connected load is connected to the power supply switching unit after the power supply switching unit changes to the conducting state; Storage units (13, 158, 194, 214, 234, 254) store second verification information (25, 27, 167, 169, 207, 227, 247, 267) used for the connection verification; and The connection checking unit (S70, S72, S74, S76, S280, S470, S670, S880) is configured to perform a connection check to determine whether one or more of the connected loads are connected to the power supply switching unit by comparing the first verification information and the second verification information for each of the one or more power supply switching units.

10. The inspection system (1) as claimed in claim 9, characterized in that, The inspection system includes: The slave control device (3, 4) serves as the connected load; and The main control device (2) serves as the inspection device. The main control device is connected to the slave control device in a manner that enables data communication, and includes one or more of the power supply switching units (14, 15).

11. The inspection system (100) as claimed in claim 9, characterized in that, The inspection system includes: The slave control device (108-116) serves as the connected load; A first integrated control device (104-107) is connected to the slave control device in a manner capable of data communication, and includes one or more of the power supply switching units (195, 196, 215, 216, 235, 236, 237, 255, 256); and A second integrated control device (101) serves as the inspection device, and is connected to the first integrated control device in a manner capable of data communication. The slave control device and the second integrated control device are connected via the first integrated control device in a manner that enables data communication between them.

12. The inspection system (100) as claimed in claim 9, characterized in that, The inspection system includes: The slave control device (108-116) serves as the connected load; A first integrated control device (104-107), which serves as the inspection device, is connected to the slave control device in a manner capable of data communication, and includes one or more of the power supply switching units (195, 196, 215, 216, 235, 236, 237, 255, 256); and A second integrated control device (101) is connected to the first integrated control device in a manner that enables data communication. The slave control device and the second integrated control device are connected via the first integrated control device in a manner that enables data communication between them.

13. The inspection system (100) as claimed in claim 9, characterized in that, The inspection system includes: From the control device (108-116); A first integrated control device (104-107) serves as the connected load, and the first integrated control device is connected to the slave control device in a manner that enables data communication. An upstream power distribution unit (102, 103), the upstream power distribution unit comprising one or more of the aforementioned power switching units (173, 174, 183, 184); and The second integrated control device (101) serves as the inspection device and is connected to the first integrated control device and the upstream power distribution unit in a manner that enables data communication.

14. The inspection system (100) as claimed in claim 9, characterized in that, The inspection system includes: From the control device (108-116); A first integrated control device (104-107) serves as the connected load, and the first integrated control device is connected to the slave control device in a manner that enables data communication. An upstream power distribution unit (102, 103), which serves as the inspection device, includes one or more of the power supply switching units (173, 174, 183, 184); and The second integrated control device (101) is connected to the first integrated control device and the upstream power distribution unit in a manner that enables data communication.

Images