Management device and management system

Abstract

The management device (2) includes first and second conducting units (S40) and first and second identification information transmitting units (S60). The first conducting unit puts the first power supply switching unit (14) into a first conducting state. The first power supply switching unit (14) switches between a first conducting state that connects the first power supply path (9) and a first disconnecting state. The first power supply path supplies power from the power source (7) to the first control device (3). When the first transmitting condition is met, the first identification information transmitting unit transmits the first identification information to the first control device. After the first identification information is transmitted, the second conducting unit puts the second power supply switching unit (15) into a second conducting state. The second power supply switching unit (15) switches between a second conducting state that connects the second power supply path and a second disconnecting state. The second power supply path supplies power to the second control device (4). When the second transmitting condition is met, the second identification information transmitting unit transmits the second identification information to the second control device.

Description

[0001] Cross-reference of related applications

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

[0003] This disclosure relates to a management device and a management system for a management control device. Background Technology

[0004] Non-Patent Document 1 describes DHCP, a protocol used to automatically assign IP addresses to multiple communication devices connected to a network. DHCP is an abbreviation for Dynamic Host Configuration Protocol.

[0005] Existing technical documents

[0006] Non-patent literature

[0007] Non-patent document 1: Network Working Group, “RFC2131 Dynamic HostConfiguration Protocol”, [online], March 1997, [retrieved January 31, 2024], Internet <URL:https: / / www.rfc-editor.org / rfc / pdfrfc / rfc2131.txt.pdf>. Summary of the Invention

[0008] Vehicles are equipped with numerous electronic control units. Furthermore, a single vehicle may sometimes contain multiple electronic control units with identical hardware. For example, the electronic control unit controlling the driver's side door and the electronic control unit controlling the passenger side door may share the same hardware.

[0009] As a result of the inventor's detailed investigation, the following problem was discovered. When a vehicle is equipped with multiple electronic control units having identical hardware, it is impossible to make the software of these multiple electronic control units universal because each unit needs to be pre-programmed with its own identification information. Consequently, for each of the multiple electronic control units with identical hardware, a portion of different software needs to be installed, leading to reduced efficiency in the manufacturing process.

[0010] This disclosure improves operational efficiency in the manufacture of electronic control devices.

[0011] One aspect of this disclosure is a management device comprising a first conductive unit, a first identification information transmitting unit, a second conductive unit, and a second identification information transmitting unit.

[0012] The first conducting section is configured to enable the first power supply switching section to a first conducting state. The first power supply switching section is configured to switch between a first conducting state that enables the first power supply path and a first disconnecting state that disconnects the first power supply path. The first power supply path supplies power from the power source to the first control device.

[0013] The first identification information transmitting unit is configured such that, after the first power supply switching unit becomes in the first conduction state, if a first transmission condition is met, it transmits first identification information, which is pre-set and used to identify the first control device, corresponding to the first power supply switching unit, to the first control device.

[0014] The second conducting unit is configured to, after the first identification information is sent to the first control device, make the second power supply switching unit into a second conducting state. The second power supply switching unit is configured to switch between a second conducting state that makes the second power supply path conduct and a second disconnecting state that disconnects the second power supply path. The second power supply path supplies power from the power source to the second control device.

[0015] The second identification information transmitting unit is configured such that, after the second power supply switching unit becomes in the second conduction state, if a pre-set second transmitting condition is met, it transmits a second identification information, which is pre-set in accordance with the second power supply switching unit and is used to identify the second control device, to the second control device.

[0016] The management device of this disclosure, configured in this way, can set first identification information and second identification information for each of the first and second control devices after mounting the first and second control devices in a vehicle. Therefore, when the first and second control devices have identical hardware, the same software can be installed in both devices during their manufacturing. Thus, the management device of this disclosure can improve the efficiency of manufacturing electronic control devices.

[0017] Another aspect of this disclosure is a management system, which includes a first control device, a second control device, and a management device.

[0018] The first control device receives power from the power source via a first power supply switching unit, which is configured to switch between a first on state that turns on the first power supply path and a first off state that turns off the first power supply path.

[0019] The second control device receives power from the power source via a second power supply switching unit, which is configured to switch between a second on state that turns on the second power supply path and a second off state that turns off the second power supply path.

[0020] The management device is connected to the first control device and the second control device in a manner that enables data communication, and is configured to control the operation of the first power supply switching unit and the second power supply switching unit. The management device includes a first conduction unit, a first identification information transmission unit, a second conduction unit, and a second identification information transmission unit.

[0021] The management system of this disclosure, as configured in this way, is a system equipped with the management device of this disclosure and can achieve the same effect as the management device of this disclosure. Attached Figure Description

[0022] Figure 1 This is a block diagram showing the structure of a vehicle control system.

[0023] Figure 2 This is a diagram showing the structure of the configuration table.

[0024] Figure 3 This is a flowchart illustrating the ID setting process of the first embodiment.

[0025] Figure 4 This is a flowchart illustrating the ID setting process of the second embodiment.

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

[0027] Figure 6 This is an illustration of the example's associated information and startup information.

[0028] Figure 7 It is a diagram showing the correspondence between controlled objects and groups.

[0029] Figure 8 This is a block diagram illustrating the structure of the communication system according to the fourth embodiment.

[0030] Figure 9 This is a block diagram illustrating the structure of the central ECU and upstream power distribution unit in the fourth embodiment.

[0031] Figure 10 This is a first block diagram illustrating the structure of the regional ECU according to the fourth embodiment.

[0032] Figure 11 This is a second block diagram illustrating the structure of the regional ECU according to the fourth embodiment.

[0033] Figure 12This is a block diagram illustrating the construction of the ECU according to the fourth embodiment.

[0034] Figure 13 This is a diagram showing the structure of the start table according to the fourth embodiment.

[0035] Figure 14 This is a diagram showing the structure of the setting table in the fourth embodiment.

[0036] Figure 15 This is a flowchart illustrating the ID setting process of the fourth embodiment.

[0037] Figure 16 This is a diagram showing the structure of the setting table in the fifth embodiment.

[0038] Figure 17 This is a flowchart illustrating the ID setting process of the fifth embodiment. Detailed Implementation

[0039] [First Implementation]

[0040] The first embodiment of this disclosure is described below based on the accompanying drawings.

[0041] 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 ECUs3 and 4, and a battery 7. ECU is an abbreviation for Electronic Control Unit.

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

[0043] Battery 7 supplies power to various parts of the vehicle at a DC battery voltage (e.g., 12V). The main ECU 2 and slave ECUs 3 and 4 receive power from battery 7 and operate accordingly.

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

[0045] The control unit 11 is an electronic control device centered around a microcomputer, including a CPU 21, a ROM 22, and a 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 a non-transient physical recording medium storing the program. Furthermore, by executing this program, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 21 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 11 can be one or more.

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

[0047] Storage unit 13 is a storage device used to store various types of data. Storage unit 13 stores the setting table 25, which will be described later.

[0048] 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.

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

[0050] The control circuits of electronic fuses 14 and 15 are configured to, according to instructions from the control unit 11, turn on or off the power supply paths 9 and 10 by turning the switching elements to the on or off state.

[0051] ECUs 3 and 4 each have a control unit 31, a CAN communication unit 32, and a storage unit 33.

[0052] The control unit 31 is an electronic control device centered around a microcomputer, including a CPU 41, a ROM 42, and a 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, by executing this program, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 41 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 31 can be one or more.

[0053] The CAN communication unit 32 communicates with the communication device connected to the communication bus 8 based on the CAN communication protocol.

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

[0055] A vehicle diagnostic device 90 (so-called diagnostic tester) is connected to the main ECU2.

[0056] 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 the slave ECUs 3 and 4 via the main ECU 2, or update the data stored in the main ECU 2 and the slave ECUs 3 and 4.

[0057] like Figure 2 As shown, setting table 25 sets the electronic fuse ID and the ECUID used to identify the connected ECU for each of the multiple electronic fuses 14, 15 provided in the vehicle control system 1.

[0058] In the setting table 25 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.

[0059] Next, the steps of the ID setting process performed by the control unit 11 of the main ECU2 will be explained. The ID setting process is a process that is repeatedly performed during the startup of the main ECU2.

[0060] When the ID setting process is executed, such as Figure 3 As shown, in S10, the CPU 21 of the control unit 11 determines whether the main ECU 2 is set to ID setting mode. The control unit 11 of the main ECU 2 is configured to, for example, set the main ECU 2 to ID setting mode when it receives an ID setting command from the fault diagnosis device 90.

[0061] Here, if the main ECU2 is not set to ID setting mode, the CPU21 ends the ID setting process. On the other hand, if the main ECU2 is set to ID setting mode, the CPU21 sets the electronic fuse indicator value i set in RAM23 to 0 in S20.

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

[0063] In S40, CPU21 makes the i-th electronic fuse (i.e., the electronic fuse whose electronic fuse ID is set to "eFuse_i") turn on.

[0064] In S50, CPU21 is set to a pre-defined standby time for the i-th on-state. That is, CPU21 is set to a first on-state standby time when the electronic fuse indicator value i = 1, and a second on-state standby time when the electronic fuse indicator value i = 2. The first and second on-state standby times are set to be longer than the startup time of the ECU connected to electronic fuses 14 and 15, respectively.

[0065] In S60, CPU21 extracts the ECUID corresponding to the i-th electronic fuse from the setting table 25 and sends the extracted ECUID from the CAN communication unit 12. That is, CPU21 sends "ECU_A" as the ECUID when the electronic fuse indication value i = 1, and sends "ECU_B" as the ECUID when the electronic fuse indication value i = 2.

[0066] In S70, CPU21 receives the i-th reception completion notification via CAN communication unit 12. The i-th reception completion notification is sent from the slave ECU connected to the i-th electronic fuse. Furthermore, the slave ECUs 3 and 4 connected to electronic fuses 14 and 15 are configured such that when the master ECU 2 receives "ECU_A" and "ECU_B" respectively, after storing "ECU_A" and "ECU_B" in storage unit 33, they send the first and second reception completion notifications to the master ECU 2.

[0067] In S80, CPU21 sends a notification from CAN communication unit 12 to make the i-th electronic fuse open.

[0068] In S90, CPU21 determines whether the i-th disconnect permission notification has been received via CAN communication unit 12. The i-th disconnect permission notification is sent from the slave ECU connected to the i-th electronic fuse. Furthermore, slave ECUs 3 and 4 connected to electronic fuses 14 and 15 are configured to send the first and second disconnect permission notifications to master ECU2 respectively when the first and second disconnect notifications are received.

[0069] Here, if the i-th disconnect permission notification is not received, CPU 21 repeats the process of S90 and remains in standby until the i-th disconnect permission notification is received. Furthermore, when the i-th disconnect permission notification is received, CPU 21 disconnects the i-th electronic fuse in S100.

[0070] In S110, 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.

[0071] 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 CPU21 deactivates the ID setting mode in S120 and ends the ID setting process.

[0072] The main ECU2 is configured such that the electronic fuse 14 is in a first conducting state, which is configured to switch between a first conducting state that turns on the power supply path 9 and a first disconnecting state that turns off the power supply path 9, which supplies power from the battery 7 to the ECU3.

[0073] The main ECU2 is configured such that, after the electronic fuse 14 becomes in the first conducting state and a preset first transmission condition is met, it sends the ECUID "ECU_A", which is preset to correspond to the electronic fuse 14 and is used to identify the slave ECU3, to the slave ECU3. In this embodiment, the first transmission condition is a preset first on-state standby time elapsed since the electronic fuse 14 becomes in the first conducting state.

[0074] The main ECU2 is configured such that after “ECU_A” is sent to the slave ECU3, the electronic fuse 15 is set to a second conducting state. The electronic fuse 15 is configured to switch between a second conducting state that turns on the power supply path 10 and a second disconnecting state that turns off the power supply path 10. The power supply path 10 supplies power from the battery 7 to the slave ECU4.

[0075] The main ECU2 is configured such that, after the electronic fuse 15 becomes in the second conducting state and a preset second transmission condition is met, it sends the ECUID "ECU_B", which is preset to correspond to the electronic fuse 15 and is used to identify the slave ECU4, to the slave ECU4. In this embodiment, the second transmission condition is a preset second on-state standby time elapsed since the electronic fuse 15 becomes in the second conducting state.

[0076] After the main ECU2 is installed in the vehicle from the secondary ECUs 3 and 4, it can assign "ECU_A" and "ECU_B" to each of the secondary ECUs 3 and 4 respectively. Therefore, since the secondary ECUs 3 and 4 have identical hardware, the same software can be installed in their manufacturing process. Thus, the main ECU2 improves the efficiency of ECU manufacturing.

[0077] Furthermore, the first and second transmission conditions respectively include a preset first and second on-state standby time after the electronic fuses 14 and 15 have entered the first and second conducting states, respectively. Therefore, the main ECU2 can send the ECUID to the slave ECUs 3 and 4 after power from the battery 7 is supplied to them and the slave ECUs 3 and 4 have started.

[0078] Furthermore, the main ECU2 is configured such that, after "ECU_A" is sent to the slave ECU3, if a pre-set first disconnection condition is met, the electronic fuse 14 is set to a first disconnected state. The main ECU2 is also configured such that, after "ECU_B" is sent to the slave ECU4, if a pre-set second disconnection condition is met, the electronic fuse 15 is set to a second disconnected state. Thus, the main ECU2 can prevent the occurrence of "ECU_B" being received from the slave ECU3 and set in the slave ECU3 when "ECU_B" is sent.

[0079] Furthermore, the master ECU2 is configured such that after sending "ECU_A" to the slave ECU3, it sends a first disconnect notification to the slave ECU3, indicating that the electronic fuse 14 is in a first disconnected state. The master ECU2 is also configured such that after sending "ECU_B" to the slave ECU4, it sends a second disconnect notification to the slave ECU4, indicating that the electronic fuse 15 is in a second disconnected state. Moreover, in this embodiment, the first and second disconnection conditions respectively include receiving pre-set first and second disconnection permission notifications from the slave ECUs 3 and 4 after sending the first and second disconnection notifications to them. Therefore, the master ECU2 can suppress the occurrence of the electronic fuses 14 and 15 being in the first and second disconnected states before the slave ECUs 3 and 4 have completed shutdown.

[0080] In the embodiments described above, the main ECU2 is equivalent to the management device and the main control device, the battery 7 is equivalent to the power source, the slave ECU3 is equivalent to the first control device, the electronic fuse 14 is equivalent to the first power supply switching unit and the power supply switching unit, and the power supply path 9 is equivalent to the first power supply path.

[0081] In addition, ECU4 is equivalent to the second control device, electronic fuse 15 is equivalent to the second power supply switching unit and power supply switching unit, power supply path 10 is equivalent to the second power supply path, and vehicle control system 1 is equivalent to the management system.

[0082] In addition, "ECU_A" is equivalent to the first identification information, and "ECU_B" is equivalent to the second identification information.

[0083] In addition, S40 is equivalent to the processing of the first and second conduction units, and S60 is equivalent to the processing of the first identification information transmission unit and the second identification information transmission unit.

[0084] In addition, the first on-state standby time is equivalent to the first conduction standby time, the second on-state standby time is equivalent to the second conduction standby time, S100 is equivalent to the processing of the first disconnection unit and the second disconnection unit, and S80 is equivalent to the processing of the first disconnection notification unit and the second disconnection notification unit.

[0085] [Second Implementation]

[0086] 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 features are indicated by the same reference numerals.

[0087] The second embodiment of the vehicle control system 1 differs from the first embodiment in that the ID setting process is modified.

[0088] The ID setting process in the second embodiment is as follows: Figure 4 As shown, the process of S52 is performed instead of S50, and the process of S92 is added, which differs from the first embodiment.

[0089] That is, when the processing of S40 ends, CPU21 determines in S52 whether an ID setting request has been received via CAN communication unit 12. In addition, the slave ECUs 3 and 4 connected to electronic fuses 14 and 15 are configured to send an ID setting request to master ECU2 when starting from power supply from battery 7.

[0090] Here, if no ID setting request is received, CPU 21 repeats the process in S52 and remains in standby until an ID setting request is received. Then, when an ID setting request is received, CPU 21 proceeds to S60.

[0091] Furthermore, when a disconnect permission is received in S90, CPU 21 in S92 transitions to S100 after suspending the pre-set standby time for the i-th disconnected state. That is, CPU 21 suspends the first disconnected state standby time when the electronic fuse indicator value i = 1, and the second disconnected state standby time when the electronic fuse indicator value i = 2. The first and second disconnected state standby times are respectively set to be longer than the time required for the ECU connected to electronic fuses 14 and 15 to complete shutdown.

[0092] In the main ECU2 configured in this way, the first and second transmission conditions respectively include receiving a pre-set ID setting request from the slave ECUs 3 and 4 after the electronic fuses 14 and 15 are in the first and second conducting states, respectively. The ID setting request indicates that the slave ECUs 3 and 4 are in a state where they can receive ECUID. Thus, the main ECU2 can send ECUID to the slave ECUs 3 and 4 after power from the battery 7 is supplied to them and the slave ECUs 3 and 4 are started.

[0093] Furthermore, the first and second disconnection conditions in this embodiment include, respectively, a pre-set first and second disconnection state standby time elapsed after the first and second disconnection notifications are sent to the slave ECUs 3 and 4, from the time the slave ECUs 3 and 4 receive the first and second disconnection permission notifications. Thus, the master ECU 2 can suppress the occurrence of electronic fuses 14 and 15 being in the first and second disconnection states before the slave ECUs 3 and 4 complete the shutdown process.

[0094] In the embodiments described above, the ID setting request sent from ECU3 is equivalent to the first receiving permission information, the ID setting request sent from ECU4 is equivalent to the second receiving permission information, the first disconnected state standby time is equivalent to the first disconnected standby time, and the second disconnected state standby time is equivalent to the second disconnected standby time.

[0095] [Third Implementation]

[0096] 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 features are indicated by the same reference numerals.

[0097] The vehicle control system 1 of the third embodiment is as follows: Figure 5 As shown, the difference from the first embodiment lies in the addition of ECU5, smart sensor 501, smart actuator 502, wireless unit 503, and electronic fuses 504 and 505.

[0098] The ECU5 receives power from the battery 7 and operates accordingly. Like the ECUs 3 and 4, the ECU5 includes a control unit 31, a CAN communication unit 32, and a storage unit 33.

[0099] The CAN communication unit 32 of ECU5 is connected to the CAN communication unit 12 of main ECU2 via communication bus 8. Therefore, main ECU2 and slave ECUs 3, 4, and 5 are connected to each other via communication bus 8 in a manner that enables data communication.

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

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

[0102] Wireless device 503 is a wireless communication device used for communicating wirelessly with an external communication device located outside the vehicle. Wireless device 503 is, for example, a DCM (Data Communication Module).

[0103] 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.

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

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

[0106] 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.

[0107] 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.

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

[0109] 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, for each communication group (described later), the vehicle control system 1 individually transitions one or more nodes belonging to that communication group to either a wake-up state (i.e., start-up state) or a sleep state (i.e., sleep state), thereby achieving low power consumption. A node, upon wake-up, enters a normal operating state where the functions assigned to it are unrestricted; upon sleep, it enters a low-power operating state where the available functions are limited.

[0110] 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.

[0111] Startup information, such as Figure 6 It is configured 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.

[0112] The start information set in the NM frame has the bit corresponding to the start group that is the start target set to 1.

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

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

[0115] For example, Figure 6 The information shown indicates that the device belongs to the first communication group, the third communication group, and the fifth communication group. Figure 6 The startup information shown indicates the startup of the second, third, fourth, and fifth communication groups. Since the third and fifth communication groups are included... Figure 6 Based on the information shown in both the ownership information and the startup information, the self node is therefore determined to be the startup target of the third communication group and the fifth communication group.

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

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

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

[0119] For example, management table 29 is set to allow ECUs 3, 4, and 5 to belong to the second communication group.

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

[0121] (Prerequisites)

[0122] 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 state by the slave node alone. Hereinafter, the master ECU2 and slave ECU5 will also be referred to as NM-mounted nodes. An NM-mounted node is a node with the function of generating NM frames.

[0123] ECUs 3 and 4, smart sensor 501, and smart actuator 502 are powered via an electronic fuse and cannot be switched to wake-up or sleep state by a single node. That is, they enter wake-up state when the electronic fuse is turned on and sleep state when the electronic fuse is turned off. Hereinafter, ECUs 3 and 4, smart sensor 501, and smart actuator 502 will 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.

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

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

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

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

[0128] NM-enabled nodes determine whether a self-node is in a wake-up or sleep state based on NM frames sent and received via the communication bus.

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

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

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

[0132] like Figure 7 As shown, one or more nodes belonging to each group are predetermined by the system developer. Although each node can be assigned a group, multiple nodes can also be registered in 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.

[0133] (First startup case)

[0134] The first activation example is an action to perform fault diagnosis from ECU3 based on a request from the cloud.

[0135] First, a connection request is sent from the base station (i.e., the cloud) to the vehicle's radio 503.

[0136] Then, when the wireless unit 503 determines that the connection is valid, it will transmit the event received from the cloud to the main ECU2.

[0137] Next, the master ECU2 determines the "fault diagnosis from ECU3" service based on the event, and in order to start the slave ECU3, generates an NM frame that sets only the bits of the third group to which the slave ECU3 belongs to to be valid.

[0138] Then, the main ECU2 sends the generated NM frame to the communication bus 8.

[0139] Since the NM-mounted nodes belonging to the third group are not on communication bus 8, the devices on the communication bus remain unchanged.

[0140] Then, the main ECU2 receives an NM frame that sets the bits of the third group to valid simultaneously with the above, and performs NM frame-based processing in the control unit 11.

[0141] Next, the control unit 11 of the main ECU2 determines the wake-up instruction to the third group based on the NM frame. Since the third group includes the electronic fuse 14, the electronic fuse 14 is turned on.

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

[0143] 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.

[0144] (Second starting case)

[0145] The second startup example is an action to perform fault diagnosis from ECU5 based on a request from the cloud.

[0146] First, a connection request is sent from the base station (i.e., the cloud) to the vehicle's radio 503.

[0147] Then, when the wireless unit 503 determines that the connection is valid, it will transmit the event received from the cloud to the main ECU2.

[0148] Next, the master ECU2 determines the "fault diagnosis of slave ECU5" service based on the event, and in order to start slave ECU5, generates an NM frame that sets only the bits of the fourth group to which slave ECU5 belongs to to be valid.

[0149] Then, the main ECU2 sends the generated NM frame to the communication bus 8.

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

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

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

[0153] When the slave ECU5 starts, 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.

[0154] (Third starting case)

[0155] The third example of starting the air conditioner remotely is when a user starts the air conditioner via their smartphone.

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

[0157] 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 ECU 2.

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

[0159] 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.

[0160] When an NM frame that will activate 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.

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

[0162] 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).

[0163] Based on the above, power is supplied to the air conditioning ECU, smart sensor 501, and smart actuator 502, thereby enabling the vehicle air conditioning to be turned on.

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

[0165] 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.

[0166] (Fourth starting case)

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

[0168] Since 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 signal indicating that the start switch connected to ECU5 is turned on.

[0169] When the ECU5 is awakened and receives an input indicating that the vehicle's air conditioning should be started, an NM frame is generated that will connect the bit corresponding to the second group.

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

[0171] 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.

[0172] When the NM frame is interrupted, the main ECU2 will, after a short while, disconnect the electronic fuses 504 and 505, thereby ending the control.

[0173] If the main ECU2 determines that control needs to continue even after the transmission of the NM frame has stopped, it will send an NM frame that will turn on the bit corresponding to the second group. Therefore, the ECU5 and electronic fuses 504 and 505 can maintain their running state until the transmission of the NM frame generated by the main ECU2 stops.

[0174] [Fourth Implementation]

[0175] 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 configurations will be indicated with the same reference numerals.

[0176] The vehicle control system 100 of the fourth embodiment is mounted on a vehicle, such as Figure 8 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 an ECU that is bundled with a slave ECU located in a specified area within the vehicle, or it can be an ECU that is bundled with a slave ECU belonging to a specified domain.

[0177] 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 receive power from battery 117 and operate accordingly.

[0178] 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.

[0179] 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.

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

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

[0182] 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.

[0183] 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.

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

[0185] 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.

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

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

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

[0189] 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 data communication between them.

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

[0191] The regional ECU 105 and the 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.

[0192] 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.

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

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

[0195] The control unit 151 is an electronic control device centered around 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 161 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 151 can be one or more.

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

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

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

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

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

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

[0202] 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.

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

[0204] 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.

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

[0206] 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.

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

[0208] 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.

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

[0210] 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.

[0211] like Figure 10 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.

[0212] The control unit 191 is an electronic control device centered around a microcomputer, including a CPU 201, a ROM 202, and a 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 201 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 191 can be one or more.

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

[0214] 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.

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

[0216] 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.

[0217] 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.

[0218] The control unit 211 is an electronic control device centered around a microcomputer, including a CPU 221, a ROM 222, and a 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 221 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 211 can be one or more.

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

[0220] 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.

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

[0222] 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.

[0223] like Figure 11 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.

[0224] The control unit 231 is an electronic control device centered around a microcomputer, including a CPU 241, a ROM 242, and a 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 241 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 231 can be one or more.

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

[0226] 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.

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

[0228] 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.

[0229] 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.

[0230] The control unit 251 is an electronic control device centered around 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 a non-transient physical recording medium storing the program. Furthermore, by executing this program, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 261 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 251 can be one or more.

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

[0232] 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.

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

[0234] 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.

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

[0236] The control unit 271 is an electronic control device centered around a microcomputer including a CPU 281, a ROM 282, and a 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 a non-transient physical recording medium storing the program. Furthermore, by executing this program, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 281 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 271 can be one or more.

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

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

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

[0240] The control unit 291 is an electronic control device centered around a microcomputer, including a CPU 301, a ROM 302, and a 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 301 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 291 can be one or more.

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

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

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

[0244] The control unit 311 is an electronic control device centered around 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 321 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 311 can be one or more.

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

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

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

[0248] The control unit 331 is an electronic control device centered around a microcomputer, including a CPU 341, a ROM 342, and a 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, methods corresponding to the program are executed. Moreover, some or all of the functions executed by the CPU 341 can be implemented in hardware using one or more ICs. Additionally, the number of microcomputers constituting the control unit 331 can be one or more.

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

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

[0251] like Figure 13As shown, in the start-up table 165 of the central ECU 101, a communication group (i.e., a start-up group) is set for each event to initiate a start-up. The start-up table 165 further establishes the correspondence between the start-up groups and the slave ECUs that are in an awakened state. The start-up table 165 also establishes the correspondence between the slave ECUs and the electronic fuses connected to them. Furthermore, the start-up table 165 can also be set in a way that indicates which region's ECU the slave ECU belongs to.

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

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

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

[0255] 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.

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

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

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

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

[0260] 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.

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

[0262] A fault diagnosis device 90 according to the first embodiment is connected to the central ECU101.

[0263] 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 and 118 via the central ECU 101, or update the data stored in the central ECU 101, regional ECUs 104-107, and ECUs 108-116 and 118.

[0264] like Figure 9 As shown, the storage section 158 of the central ECU 101 stores the setting table 167.

[0265] like Figure 14 As shown, setting table 167 sets the electronic fuse ID and the ECUID used to identify the connected ECU for each of the multiple electronic fuses 195, 196 provided in the vehicle control system 100.

[0266] In the setting table 167 of this embodiment, the electronic fuse 195 is set as "eFuse_1" as the electronic fuse ID and as "ECU_A" as the ECU ID. "ECU_A" is the ECU ID corresponding to ECU 108.

[0267] Regarding electronic fuse 196, its electronic fuse ID is set as "eFuse_2", and its ECU ID is set as "ECU_B". "ECU_B" is the ECU ID corresponding to ECU 109.

[0268] Furthermore, ECU 108 is, for example, an electronic control device that controls the driver's side door, and ECU 109 is, for example, an electronic control device that controls the passenger side door. Therefore, both ECU 108 and ECU 109 are equipped with software adapted for door control. That is, ECU 108 and ECU 109 are configured to operate regardless of whether "ECU_A" or "ECU_B" is set.

[0269] Next, the steps of the ID setting process performed by the control unit 151 of the central ECU 101 will be explained. The ID setting process is a process that is repeatedly performed during the startup of the central ECU 101.

[0270] When the ID setting process is executed, such as Figure 15 As shown, in S210, the CPU 161 of the control unit 151 determines whether the central ECU 101 is set to ID setting mode. The control unit 151 of the central ECU 101 is configured to, for example, set the central ECU 101 to ID setting mode when it receives an ID setting command from the fault diagnosis device 90.

[0271] Here, if the central ECU 101 is not set to ID setting mode, the CPU 161 ends the ID setting process. On the other hand, if the central ECU 101 is set to ID setting mode, the CPU 161 sets the electronic fuse indicator value i set in RAM 163 to 0 in S220.

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

[0273] In S240, CPU161 makes the i-th electronic fuse (i.e., the electronic fuse whose electronic fuse ID is set to "eFuse_i") turn on.

[0274] In S250, CPU161 is set to a pre-defined standby time for the i-th on-state. That is, CPU161 is set to a first on-state standby time when the electronic fuse indicator value i = 1, and a second on-state standby time when the electronic fuse indicator value i = 2. The first and second on-state standby times are set to be longer than the startup time of the ECU connected to electronic fuses 14 and 15, respectively.

[0275] In S260, CPU161 extracts the ECUID corresponding to the i-th electronic fuse from the setting table 25 and sends the extracted ECUID from the CAN communication unit 12. That is, CPU161 sends "ECU_A" as the ECUID when the electronic fuse indication value i = 1, and sends "ECU_B" as the ECUID when the electronic fuse indication value i = 2.

[0276] In S270, CPU161 receives the i-th reception completion notification via communication unit 154. The i-th reception completion notification is sent from the slave ECU connected to the i-th electronic fuse. Furthermore, the slave ECUs 108 and 109 connected to electronic fuses 195 and 196 are respectively configured to send the first and second reception completion notifications to the central ECU 101 after storing "ECU_A" and "ECU_B" in storage unit 273 when they receive "ECU_A" and "ECU_B" from the central ECU 101.

[0277] In S280, CPU161 sends a notification from communication unit 154 to the i-th disconnect notification, which causes the i-th electronic fuse to become disconnected.

[0278] In S290, CPU161 determines whether the i-th disconnect permission notification has been received via communication unit 154. The i-th disconnect permission notification is sent from the slave ECU connected to the i-th electronic fuse. Furthermore, the slave ECUs 108 and 109 connected to electronic fuses 195 and 196 are respectively configured to send the first and second disconnect permission notifications to the central ECU 101 when the first and second disconnect notifications are received.

[0279] Here, if the i-th disconnect permission notification is not received, CPU 161 repeats the process of S290 and remains in standby until the i-th disconnect permission notification is received. Furthermore, when the i-th disconnect permission notification is received, CPU 161 disconnects the i-th electronic fuse in S300.

[0280] In step S310, CPU161 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, CPU161 proceeds to step S230.

[0281] 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 deactivates the ID setting mode in S320 and ends the ID setting process.

[0282] The central ECU 101 is configured such that the electronic fuse 195 is in a first conducting state, and the electronic fuse 195 is configured to switch between a first conducting state that turns on the power supply path 127 and a first disconnecting state that turns off the power supply path 127, the power supply path 127 supplying power from the battery 117 to the ECU 108.

[0283] The central ECU 101 is configured such that, after the electronic fuse 195 becomes in a first conducting state and a preset first transmission condition is met, it sends the ECUID "ECU_A", which is preset to correspond to the electronic fuse 195 and is used to identify the slave ECU 108, to the slave ECU 108. In this embodiment, the first transmission condition is a preset first on-state standby time elapsed since the electronic fuse 195 becomes in the first conducting state.

[0284] The central ECU 101 is configured such that after “ECU_A” is sent to the slave ECU 108, the electronic fuse 196 is set to a second conducting state. The electronic fuse 196 is configured to switch between a second conducting state that turns on the power supply path 128 and a second disconnecting state that turns off the power supply path 128. The power supply path 128 supplies power from the battery 117 to the slave ECU 109.

[0285] The central ECU 101 is configured such that, after the electronic fuse 196 becomes in the second conducting state and a preset second transmission condition is met, it sends the ECUID "ECU_B", which is preset to correspond to the electronic fuse 196 and is used to identify the slave ECU 109, to the slave ECU 109. In this embodiment, the second transmission condition is a preset second on-state standby time elapsed since the electronic fuse 196 becomes in the second conducting state.

[0286] After the central ECU 101 is installed in the vehicle from the ECUs 108 and 109, it can assign "ECU_A" and "ECU_B" to each of the ECUs 108 and 109 respectively. Therefore, since the ECUs 108 and 109 have identical hardware, the same software can be installed in the manufacturing process of the ECUs 108 and 109. Thus, the central ECU 101 can improve the efficiency of ECU manufacturing.

[0287] In the embodiments described above, the central ECU 101 is equivalent to a management device and a second integrated control device, the battery 117 is equivalent to a power source, the ECU 108 is equivalent to a first control device, the electronic fuse 195 is equivalent to a first power supply switching unit and a power supply switching unit, and the power supply path 127 is equivalent to a first power supply path.

[0288] In addition, ECU109 is equivalent to the second control device, electronic fuse 196 is equivalent to the second power supply switching unit and power supply switching unit, power supply path 128 is equivalent to the second power supply path, area ECU104 is equivalent to the first integrated control device, and vehicle control system 100 is equivalent to the management system.

[0289] In addition, S240 is equivalent to the processing of the first conducting unit and the second conducting unit, S260 is equivalent to the processing of the first identification information transmitting unit and the second identification information transmitting unit, S300 is equivalent to the processing of the first disconnecting unit and the second disconnecting unit, and S280 is equivalent to the processing of the first disconnecting notification unit and the second disconnecting notification unit.

[0290] [Fifth Implementation]

[0291] The following and appendix Figure 1 The 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 features are indicated by the same reference numerals.

[0292] The vehicle control system 100 of the fifth embodiment differs from that of the fourth embodiment in the structure of the setting table 167 and the point where the ID setting process is changed.

[0293] The setting table of the fifth embodiment is as follows: Figure 16 As shown, for each of the multiple electronic fuses 173, 174, 183, 184 provided in the vehicle control system 100, an electronic fuse ID and an ECUID for identifying the connected ECU are set.

[0294] In the setting table 167 of this embodiment, the electronic fuse 173 is set as "eFuse_1" as the electronic fuse ID and as "ECU_A" as the ECU ID. "ECU_A" is the ECU ID corresponding to region ECU104.

[0295] Regarding electronic fuse 174, it is set as "eFuse_2" as the electronic fuse ID and as "ECU_B" as the ECU ID. "ECU_B" is the ECU ID corresponding to region ECU105.

[0296] Regarding electronic fuse 183, it is set as "eFuse_3" as electronic fuse ID and as "ECU_C" as ECU ID. "ECU_C" is the ECU ID corresponding to region ECU106.

[0297] Regarding electronic fuse 184, it is set as "eFuse_4" as the electronic fuse ID and as "ECU_D" as the ECU ID. "ECU_D" is the ECU ID corresponding to region ECU107.

[0298] Furthermore, area ECU 104 is, for example, an electronic control device that controls the right front door of the vehicle; area ECU 105 is, for example, an electronic control device that controls the left front door of the vehicle; area ECU 106 is, for example, an electronic control device that controls the right rear door of the vehicle; and area ECU 107 is, for example, an electronic control device that controls the left rear door of the vehicle. Therefore, area ECUs 104, 105, 106, and 107 are equipped with software generalized for door control. That is, area ECUs 104, 105, 106, and 107 are configured to operate regardless of which of "ECU_A", "ECU_B", "ECU_C", and "ECU_D" is set.

[0299] Next, the steps of the ID setting process performed by the control unit 151 of the central ECU 101 will be explained. The ID setting process is a process that is repeatedly performed during the startup of the central ECU 101.

[0300] When the ID setting process is executed, such as Figure 17 As shown, the CPU 161 of the control unit 151 determines in S410 whether the central ECU 101 is set to ID setting mode. The control unit 151 of the central ECU 101 is configured to, for example, set the central ECU 101 to ID setting mode when it receives an ID setting command from the fault diagnosis device 90.

[0301] Here, if the central ECU 101 is not set to ID setting mode, the CPU 161 ends the ID setting process. On the other hand, if the central ECU 101 is set to ID setting mode, the CPU 161 sets the electronic fuse indicator value i set in RAM 163 to 0 in S420.

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

[0303] In S440, CPU161 makes the i-th electronic fuse (i.e., the electronic fuse whose electronic fuse ID is set to "eFuse_i") turn on.

[0304] In S450, CPU161 has a pre-set standby time for the i-th on-state. For example, CPU161 has a first on-state standby time when the electronic fuse indicator value i = 1, and a second on-state standby time when the electronic fuse indicator value i = 2. The standby times for the first, second, third, and fourth on-states are set to be longer than the startup time of the ECUs connected to electronic fuses 173, 174, 183, and 184, respectively.

[0305] In S460, CPU161 extracts the ECUID corresponding to the i-th electronic fuse from the setting table 167 and sends the extracted ECUID from the CAN communication unit 12. That is, for example, CPU161 sends "ECU_A" as ECUID when the electronic fuse indication value i = 1, and sends "ECU_B" as ECUID when the electronic fuse indication value i = 2.

[0306] In S470, CPU161 receives the i-th reception completion notification via communication unit 154. The i-th reception completion notification is sent from the region ECU connected to the i-th electronic fuse. Furthermore, the region ECUs 104, 105, 106, and 107 connected to electronic fuses 173, 174, 183, and 184 are respectively configured such that when they receive “ECU_A”, “ECU_B”, “ECU_C”, and “ECU_D” from the central ECU 101, after storing “ECU_A”, “ECU_B”, “ECU_C”, and “ECU_D” in storage units 194, 214, 234, and 254, they send the first, second, third, and fourth reception completion notifications to the central ECU 101.

[0307] In S480, CPU161 sends a notification from communication unit 154 to the i-th disconnect notification, which causes the i-th electronic fuse to become open.

[0308] In S490, CPU161 determines whether the i-th disconnect permission notification has been received via communication unit 154. The i-th disconnect permission notification is sent from the area ECU connected to the i-th electronic fuse. Furthermore, the area ECUs 104, 105, 106, and 107 connected to electronic fuses 173, 174, 183, and 184 are respectively configured to send the first, second, third, and fourth disconnect permission notifications to the central ECU 101 upon receiving the first, second, third, and fourth disconnect notifications, respectively.

[0309] Here, if the i-th disconnect permission notification is not received, the CPU 161 repeats the process of S490 and remains in standby until the i-th disconnect permission notification is received. Furthermore, when the i-th disconnect permission notification is received, the CPU 161 disconnects the i-th electronic fuse in S500.

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

[0311] 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 deactivates the ID setting mode in S520 and ends the ID setting process.

[0312] The central ECU 101 is configured such that the electronic fuse 173 is in a first conducting state, which is configured to switch between a first conducting state that turns on the power supply path 123 that supplies power from the battery 117 to the regional ECU 104 and a first disconnecting state that turns off the power supply path 123.

[0313] The central ECU 101 is configured such that, after the electronic fuse 173 becomes in a first conducting state and a preset first transmission condition is met, it sends the ECUID "ECU_A", which is preset and used to identify the area ECU 104, corresponding to the electronic fuse 173. In this embodiment, the first transmission condition is a preset first on-state standby time elapsed since the electronic fuse 173 becomes in the first conducting state.

[0314] The central ECU 101 is configured such that after “ECU_A” is sent to the regional ECU 104, the electronic fuse 174 is put into a second conducting state. The electronic fuse 174 is configured to switch between a second conducting state that turns on the power supply path 124 and a second disconnecting state that turns off the power supply path 124. The power supply path 124 supplies power from the battery 117 to the regional ECU 105.

[0315] The central ECU 101 is configured such that, after the electronic fuse 174 becomes in the second conducting state and a preset second transmission condition is met, it sends the ECUID "ECU_B", which is preset to correspond to the electronic fuse 174 and used to identify the area ECU 105, to the area ECU 105. In this embodiment, the second transmission condition is a preset second on-state standby time elapsed since the electronic fuse 174 becomes in the second conducting state.

[0316] After the central ECU 101 is installed in the vehicle along with the regional ECUs 104 and 105, it can assign "ECU_A" and "ECU_B" to each of the regional ECUs 104 and 105 respectively. Therefore, since the regional ECUs 104 and 105 have identical hardware, the same software can be installed in their manufacturing process. Thus, the central ECU 101 improves the efficiency of ECU manufacturing.

[0317] After ECUs 104, 105, 106, and 107 are assigned the ECU IDs "ECU_A", "ECU_B", "ECU_C", and "ECU_D" respectively, they use these assigned ECU IDs for data communication. Specifically, "ECU_A", "ECU_B", "ECU_C", and "ECU_D" can be, for example, "1101", "1102", "1103", and "1104" respectively. Therefore, the data source can be identified during data communication between ECUs 104 and 107.

[0318] In the embodiments described above, the central ECU 101 is equivalent to a management device and a second integrated control device, the battery 117 is equivalent to a power source, the regional ECU 104 is equivalent to a first control device and a first integrated control device, the electronic fuse 173 is equivalent to a first power supply switching unit and a power supply switching unit, and the power supply path 123 is equivalent to a first power supply path.

[0319] In addition, the area ECU105 is equivalent to the second control device and the first integrated control device, the electronic fuse 174 is equivalent to the second power supply switching unit and the power supply switching unit, the power supply path 124 is equivalent to the second power supply path, and the electronic fuses 183 and 184 are equivalent to the power supply switching unit.

[0320] In addition, S440 is equivalent to the processing of the first conducting unit and the second conducting unit, S460 is equivalent to the processing of the first identification information transmitting unit and the second identification information transmitting unit, S500 is equivalent to the processing of the first disconnecting unit and the second disconnecting unit, and S480 is equivalent to the processing of the first disconnecting notification unit and the second disconnecting notification unit.

[0321] The above describes one embodiment of the present disclosure, but the present disclosure is not limited to the above embodiment and can be implemented in various modifications.

[0322] [Variation Example 1]

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

[0324] [Modification Example 2]

[0325] In the above embodiment, an ID setting request is shown being sent from ECU3 and 4. However, ECU3 and 4 may also send a wake-up notification indicating that the system has started, instead of an ID setting request.

[0326] [Modification Example 3]

[0327] In the above embodiment, the example shows the master ECU2 sending the ECUID to the slave ECUs 3 and 4 via CAN communication. However, when LIN communication is used between the master ECU2 and the slave ECUs 3 and 4, the master ECU2 can also send the NAD instead of the ECUID. LIN is an abbreviation for Local Interconnect Network. NAD is an abbreviation for Node Address.

[0328] The control units 11 and 151 and their methods described in this disclosure can be implemented using a dedicated computer, which is provided by comprising a processor programmed to perform one or more functions embodied in a computer program and a memory. Alternatively, the control units 11 and 151 and their methods described in this disclosure can also be implemented using a dedicated computer, which is provided by comprising a processor composed of one or more dedicated hardware logic circuits. Alternatively, the control units 11 and 151 and their methods described in this disclosure can also be implemented using one or more dedicated computers, which are configured by a combination of a processor programmed to perform one or more functions and a memory, and a processor composed of one or more hardware logic circuits. Furthermore, the computer program, as instructions executed by a computer, can be stored in a computer-readable, non-transient tangible recording medium. In the methods for implementing the functions of the units included in control units 11 and 151, software is not necessarily required; all functions can be implemented using one or more hardware components.

[0329] In the above embodiments, multiple functions of one component can be implemented by multiple components, and one function of one component can also be implemented by multiple components. Furthermore, multiple functions of multiple components can be implemented by one component, and one function implemented by multiple components can also be implemented by one component. Additionally, a portion of the structure in the above embodiments may be omitted. Furthermore, at least a portion of the structure in the above embodiments may be added to or replaced relative to the structures of other above embodiments.

[0330] In addition to the main ECU2 and central ECU101 described above, the present disclosure may also be implemented in various forms, including a system that uses the main ECU2 and central ECU101 as constituent elements, a program for enabling a computer to function as the main ECU2 and central ECU101, a non-transient physical recording medium such as a semiconductor memory that records the program, and a management method.

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

[0332] [Project 1]

[0333] A management device (2, 101) comprising:

[0334] The first conducting section (S40, S240, S440) is configured to enable the first power supply switching section (14, 173, 195) to be in a first conducting state. The first power supply switching section is configured to switch between the first conducting state that enables the first power supply path (9, 123, 127) to be conducted and the first disconnecting state that disconnects the first power supply path. The first power supply path supplies power from the power source (7, 117) to the first control device (3, 104, 108).

[0335] The first identification information sending unit (S60, S260, S460) is configured to send first identification information, which is pre-set and used to identify the first control device, to the first control device after the first power supply switching unit becomes the first conduction state and a pre-set first sending condition is met.

[0336] The second conducting unit (S40, S240, S440) is configured to, after the first identification information is sent to the first control device, cause the second power supply switching unit (15, 174, 196) to enter a second conducting state. The second power supply switching unit is configured to switch between a second conducting state that connects the second power supply path (10, 124, 128) and a second disconnecting state that disconnects the second power supply path. The second power supply path supplies power from the power source to the second control device (4, 105, 109).

[0337] The second identification information sending unit (S60, S260, S460) is configured to send second identification information, which is pre-set and used to identify the second control device, to the second control device after the second power supply switching unit becomes the second conduction state and a pre-set second sending condition is met.

[0338] [Project 2]

[0339] The management device as described in Project 1,

[0340] The first transmission condition includes a preset first conduction standby time elapsed since the first power supply switching unit enters the first conduction state.

[0341] The second transmission condition includes a preset second conduction standby time elapsed since the second power supply switching unit becomes the second conduction state.

[0342] [Project 3]

[0343] The management device as described in Project 1,

[0344] The first transmission condition includes receiving a pre-set first reception permission information from the first control device after the first power supply switching unit becomes the first conduction state. This first reception permission information indicates that the first control device is in a state where it can receive the first identification information.

[0345] The second transmission condition includes receiving a pre-set second reception permission information from the second control device after the second power supply switching unit becomes the second conduction state. The second reception permission information indicates that the second control device is in a state where it can receive the second identification information.

[0346] [Project 4]

[0347] The management device as described in any one of Items 1 to 3 further comprises:

[0348] The first disconnection section (S100, S300, S500) is configured such that, after the first identification information is sent to the first control device, if a preset first disconnection condition is met, the first power supply switching section is set to the first disconnection state; and

[0349] The second disconnection unit (S100, S300, S500) is configured such that, after the second identification information is sent to the second control device, the second power supply switching unit is set to the second disconnection state when a preset second disconnection condition is met.

[0350] [Project 5]

[0351] The management device described in Project 4 also includes:

[0352] The first disconnection notification unit (S80, S280, S480) is configured to, after sending the first identification information to the first control device, send a first disconnection notification to the first control device that notifies the first power supply switching unit to be in the first disconnection state; and

[0353] The second disconnection notification unit (S80, S280, S480) is configured to send a second disconnection notification to the second control device after sending the second identification information to the second control device, which then sends the notification to cause the second power supply switching unit to enter the second disconnection state.

[0354] The first disconnection condition includes receiving a pre-set first disconnection permission notification from the first control device after sending the first disconnection notification to the first control device.

[0355] The second disconnection condition includes receiving a pre-set second disconnection permission notification from the second control device after sending the second disconnection notification to the second control device.

[0356] [Project 6]

[0357] The management device as described in Project 5

[0358] The first disconnection condition includes a preset first disconnection standby time elapsed since the first control device receives the first disconnection permission notification after the first disconnection notification has been sent to the first control device.

[0359] The second disconnection condition includes a pre-set second disconnection standby time elapsed since the second control device receives the second disconnection permission notification after the second disconnection notification is sent to the second control device.

[0360] [Project 7]

[0361] A management system (1, 100) has the following features:

[0362] The first control device (3, 104, 108) receives power from the power source (7, 117) via a first power supply switching unit (14, 173, 195), which is configured to switch between a first conducting state that turns on the first power supply path and a first disconnecting state that turns off the first power supply path (9, 123, 127).

[0363] A second control device (4, 105, 109) receives power from the power source via a second power supply switching unit (15, 174, 196), the second power supply switching unit being configured to switch between a second conducting state that connects the second power supply path (10, 124, 128) and a second disconnecting state that disconnects the second power supply path; and

[0364] Management device (2, 101), which is connected to the first control device and the second control device in a manner capable of data communication, is configured to control the operation of the first power supply switching unit and the second power supply switching unit.

[0365] The management device includes:

[0366] The first conducting section (S40, S240, S440) is configured to enable the first power supply switching section to the first conducting state.

[0367] The first identification information sending unit (S60, S260, S460) is configured to send first identification information, which is pre-set and used to identify the first control device, to the first control device after the first power supply switching unit becomes the first conduction state and a pre-set first sending condition is met.

[0368] The second conductive section (S40, S240, S440) is configured to, after the first identification information is sent to the first control device, cause the second power supply switching section to enter the second conductive state; and

[0369] The second identification information sending unit (S60, S260, S460) is configured to send second identification information, which is pre-set and used to identify the second control device, to the second control device after the second power supply switching unit becomes the second conduction state and a pre-set second sending condition is met.

[0370] [Project 8]

[0371] The management system described in Project 7

[0372] In addition to the first control device and the second control device, the management system also includes one or more control devices (5, 104 to 118).

[0373] The first control device and the second control device are pre-set as objects for the management device to perform the processing of the first communication unit, the first identification information transmission unit, the second communication unit, and the second identification information transmission unit.

[0374] [Project 9]

[0375] The management system described in Project 7 or Project 8

[0376] Both the first and second control devices are equipped with standardized software.

[0377] The first control device and the second control device are configured to operate regardless of whether either the first identification information or the second identification information is set.

[0378] [Project 10]

[0379] The management system (1) as described in any one of Projects 7 to 9.

[0380] The management system includes:

[0381] As two slave control devices (3, 4) of the first control device and the second control device; and

[0382] As the main control device (2) of the management device, the main control device is connected to the slave control device in a manner that enables data communication, and has one or more power supply switching units (14, 15).

[0383] [Project 11]

[0384] The management system (100) as described in any one of Projects 7 to 9.

[0385] The management system includes:

[0386] As two slave control devices (108, 109) of the first control device and the second control device.

[0387] A first integrated control device (104) is connected to the slave control device in a manner capable of data communication, and includes multiple power supply switching units (195, 196); and

[0388] As a second integrated control device (101) of the management device, the second integrated control device is connected to the first integrated control device in a manner that enables data communication.

[0389] 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.

[0390] [Project 12]

[0391] The management system (100) as described in any one of Projects 7 to 9.

[0392] The management system includes:

[0393] One or more slave control devices (108-116);

[0394] As two first integrated control devices (104, 105) of the first control device and the second control device, the two first integrated control devices are connected to the slave control device in a manner that enables data communication.

[0395] An upstream power distribution unit (102, 103), the upstream power distribution unit having one or more power supply switching units (173, 174, 183, 184); and

[0396] As a second integrated control device (101) of the management device, the second integrated control device is connected to the first integrated control device and the upstream power distribution unit in a manner that enables data communication.

Claims

1. A management device (2, 101), characterized in that, have: The first conducting section (S40, S240, S440) is configured to enable the first power supply switching section (14, 173, 195) to be in a first conducting state. The first power supply switching section is configured to switch between the first conducting state that enables the first power supply path (9, 123, 127) to be conducted and the first disconnecting state that disconnects the first power supply path. The first power supply path supplies power from the power source (7, 117) to the first control device (3, 104, 108). The first identification information sending unit (S60, S260, S460) is configured to send first identification information, which is pre-set and used to identify the first control device, to the first control device after the first power supply switching unit becomes the first conduction state and a pre-set first sending condition is met. The second conducting unit (S40, S240, S440) is configured to, after the first identification information is sent to the first control device, cause the second power supply switching unit (15, 174, 196) to be in a second conducting state. The second power supply switching unit is configured to switch between a second conducting state that turns on the second power supply path (10, 124, 128) and a second disconnecting state that disconnects the second power supply path. The second power supply path supplies power from the power source to the second control device (4, 105, 109). as well as The second identification information sending unit (S60, S260, S460) is configured to send second identification information, which is pre-set and used to identify the second control device, to the second control device after the second power supply switching unit becomes the second conduction state and a pre-set second sending condition is met.

2. The management device as described in claim 1, characterized in that: The first transmission condition includes a preset first conduction standby time elapsed since the first power supply switching unit enters the first conduction state. The second transmission condition includes a preset second conduction standby time elapsed since the second power supply switching unit becomes the second conduction state.

3. The management device as described in claim 1, characterized in that: The first transmission condition includes receiving a pre-set first reception permission information from the first control device after the first power supply switching unit becomes the first conduction state. This first reception permission information indicates that the first control device is in a state where it can receive the first identification information. The second transmission condition includes receiving a pre-set second reception permission information from the second control device after the second power supply switching unit becomes the second conduction state. The second reception permission information indicates that the second control device is in a state where it can receive the second identification information.

4. The management device as described in any one of claims 1 to 3, characterized in that, It also has: The first disconnection section (S100, S300, S500) is configured such that after the first identification information is sent to the first control device, the first power supply switching section is made to the first disconnection state when a preset first disconnection condition is met. as well as The second disconnection unit (S100, S300, S500) is configured such that, after the second identification information is sent to the second control device, the second power supply switching unit is set to the second disconnection state when a preset second disconnection condition is met.

5. The management device as described in claim 4, characterized in that, It also has: The first disconnection notification unit (S80, S280, S480) is configured to send a first disconnection notification to the first control device after sending the first identification information to the first control device, which notifies the first power supply switching unit to be in the first disconnection state. as well as The second disconnection notification unit (S80, S280, S480) is configured to send a second disconnection notification to the second control device after sending the second identification information to the second control device, which then sends the notification to cause the second power supply switching unit to enter the second disconnection state. The first disconnection condition includes receiving a pre-set first disconnection permission notification from the first control device after sending the first disconnection notification to the first control device, and the second disconnection condition includes receiving a pre-set second disconnection permission notification from the second control device after sending the second disconnection notification to the second control device.

6. The management device as described in claim 5, characterized in that: The first disconnection condition includes a preset first disconnection standby time elapsed since the first control device receives the first disconnection permission notification after the first disconnection notification has been sent to the first control device. The second disconnection condition includes a pre-set second disconnection standby time elapsed since the second control device receives the second disconnection permission notification after the second disconnection notification is sent to the second control device.

7. A management system (1, 100), characterized in that, have: The first control device (3, 104, 108) receives power from the power source (7, 117) via a first power supply switching unit (14, 173, 195), which is configured to switch between a first conducting state that turns on the first power supply path and a first disconnecting state that turns off the first power supply path (9, 123, 127). The second control device (4, 105, 109) receives power from the power source via the second power supply switching unit (15, 174, 196), which is configured to switch between a second on state that turns on the second power supply path (10, 124, 128) and a second off state that turns off the second power supply path. as well as Management device (2, 101), which is connected to the first control device and the second control device in a manner capable of data communication, is configured to control the operation of the first power supply switching unit and the second power supply switching unit. The management device includes: The first conducting section (S40, S240, S440) is configured to enable the first power supply switching section to the first conducting state. The first identification information sending unit (S60, S260, S460) is configured to send first identification information, which is pre-set and used to identify the first control device, to the first control device after the first power supply switching unit becomes the first conduction state and a pre-set first sending condition is met. The second conductive section (S40, S240, S440) is configured to enable the second power supply switching section to the second conductive state after the first identification information is sent to the first control device. as well as The second identification information sending unit (S60, S260, S460) is configured to send second identification information, which is pre-set and used to identify the second control device, to the second control device after the second power supply switching unit becomes the second conduction state and a pre-set second sending condition is met.

8. The management system as described in claim 7, characterized in that: In addition to the first control device and the second control device, the management system also includes one or more control devices (5, 104 to 118). The first control device and the second control device are pre-set as objects for the management device to perform the processing of the first communication unit, the first identification information transmission unit, the second communication unit, and the second identification information transmission unit.

9. The management system as described in claim 7 or 8, characterized in that: Both the first and second control devices are equipped with standardized software. The first control device and the second control device are configured to operate regardless of whether either the first identification information or the second identification information is set.

10. The management system (1) as described in claim 7 or 8, characterized in that: The management system includes: As two slave control devices (3, 4) of the first control device and the second control device; and As the main control device (2) of the management device, the main control device is connected to the slave control device in a manner that enables data communication, and has one or more power supply switching units (14, 15).

11. The management system (100) as described in claim 7 or 8, characterized in that: The management system includes: As two slave control devices (108, 109) of the first control device and the second control device. A first integrated control device (104) is connected to the slave control device in a manner capable of data communication, and includes multiple power supply switching units (195, 196); and As a second integrated control device (101) of the management device, the second integrated control device 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.

12. The management system (100) as described in claim 7 or 8, characterized in that: The management system includes: One or more slave control devices (108-116); As two first integrated control devices (104, 105) of the first control device and the second control device, the two first integrated control devices are 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 having one or more power supply switching units (173, 174, 183, 184); and As a second integrated control device (101) of the management device, the second integrated control device is connected to the first integrated control device and the upstream power distribution unit in a manner that enables data communication.

Images