State control method and system of controller

Abstract

The embodiment of the invention provides a state control method and system of a controller, and relates to the technical field of new energy automobile charging. A mode of combining local wake-up and network wake-up is adopted, and flexible switching between a dormant state and a standby state of each controller is realized. The state control method of the controller is applied to a first controller unit of a state control system of the controller, the state control system of the controller further comprises a vehicle control unit (VCU), and the first controller unit comprises a vehicle-mounted charger (OBC) and a second controller which communicates with the OBC based on the architecture of the first controller unit. The method comprises the following steps: when a first controller unit acquires a connection signal between power supply equipment and the local through the OBC, sending a network management message to a second controller through the OBC to wake up the second controller; and feeding back a message signal to a vehicle control unit (VCU) through a local state mechanism fed back to the VCU after the second controller responds to the network management message to enter a standby state.

Description

[Technical field]

[0001] The embodiments of the present application relate to the field of new energy vehicle charging technology, and in particular, to a controller state control method and system. [Background technology]

[0002] As the functions of new energy vehicles increase, the network architecture of the whole vehicle becomes more and more complex, and the network communication interaction between controllers becomes more and more frequent. Taking the charging process of new energy vehicles as an example, there are many controllers involved in the charging process with different functions. The controllers remain awake for a long time, which increases the energy consumption of the whole vehicle. If the controllers of the whole vehicle cannot be awakened after sleeping, some functions of the whole vehicle cannot be realized. Therefore, it is necessary to flexibly switch the controllers between sleep and standby states.

[0003] If the controllers of the vehicle cannot be awakened after sleep, the problem is reflected in: when the vehicle is in OFF gear and plugged in for charging, the vehicle often cannot be awakened and cannot be charged. Or after charging is terminated or completed, the vehicle cannot sleep, resulting in problems such as vehicle power supply. [Summary of the invention]

[0004] The embodiments of the present application provide a controller state control method and system, which adopt a combination of local wake-up and network wake-up to achieve flexible switching of each controller between sleep state and standby state.

[0005] In the first aspect, an embodiment of the present application provides a controller state control method, which is applied to a first controller unit of a controller state control system, the controller state control system also including a vehicle controller VCU, the first controller unit including an on-board charger OBC and a second controller that communicates with the OBC based on the architecture of the first controller unit; the method includes: when the first controller unit collects a connection signal between a power supply device and a local area through the OBC, a network management message is sent to the second controller through the OBC to wake up the second controller; a local state mechanism in which the second controller responds to the network management message and then enters a standby state and then feeds back a message signal to the VCU.

[0006] The controller state control method proposed in the embodiment of the present application wakes up the OBC by identifying the connection signal based on the information interaction between the OBC and the charging device, wakes up the second controller by network wake-up based on the second controller supporting the message wake-up with the unified architecture between the OBC and the charging device, wakes up the VCU by the message sent by any controller based on the mechanism that the second controller will feedback the message to the VCU when it wakes up and enters the standby state, so that the VCU can monitor the state of each controller; finally, through the mechanism of the VCU and the second controller, the other controllers are hard-wired to wake up, and the multiple controllers involved in the charging process are switched from sleep to standby state. The whole process is based on the original mechanism of each controller to wake up the controller involved in the charging process when the vehicle is in the OFF gear, thereby reducing the energy consumption of the whole vehicle when each controller remains in the awake state for a long time, avoiding the use of a large battery solution, reducing the cost of vehicle development, solving the network management limitations and vehicle function development limitations brought by the local network management solution, and improving the comprehensive development of vehicle functions.

[0007] In one possible implementation, the second controller includes an interleaved parallel bidirectional converter BDC, and after sending the network management message to the second controller, the method further includes:

[0008] By controlling the accessory relay of the BDC to close, a hard-line wake-up signal is sent to the third controller to wake up the third controller; the third controller is at least one of the vehicle heater PTC and the clutch controller CCU.

[0009] In one possible implementation, the second controller includes: a battery management system BMS, a DC-DC bidirectional converter DC-DC, a vehicle display instrument IC, a remote communication terminal Tbox, and an interleaved parallel bidirectional converter BDC; a local state mechanism in which the second controller responds to the network management message and then enters a standby state and then feeds back a message signal to the vehicle controller VCU includes:

[0010] A message signal is fed back to the VCU through a target controller; the target controller is any one or more controllers among the BMS, the DC-DC, the IC, the Tbox and the BDC.

[0011] In one possible implementation, the method further includes:

[0012] When the first controller unit fails to collect a connection signal between the power supply device and the local area through the OBC, it stops sending network management messages through the OBC and starts executing a local sleep program through the OBC;

[0013] When the network management message is not received through the second controller, the local sleep program is started to be executed through the second controller.

[0014] In one possible implementation, the second controller includes a battery management system BMS and a DC-DC bidirectional converter DC-DC. When the network management message is not received by the second controller, the local sleep program is started to be executed by the second controller, including:

[0015] When the BMS or the DC-DC does not receive the network management message through the OBC and receives a power-off instruction sent by the vehicle controller VCU, it enters a sleep state.

[0016] In a second aspect, an embodiment of the present application provides a controller state control method, which is applied to a VCU of a controller state control system, wherein the controller state control system further includes a first controller unit, wherein the first controller unit includes an onboard charger OBC and a second controller communicating with the OBC based on the architecture of the first controller unit, wherein the method includes:

[0017] When the VCU receives a message signal fed back by any controller in the second controller, it starts to execute a program for entering a local standby state;

[0018] The message signal is generated after the second controller enters a standby state in response to a network management message sent by the OBC; the OBC sends a network management message to the second controller when collecting a connection signal between the power supply device and the local area.

[0019] In one possible implementation, after starting to execute the program for entering the standby state locally, the method further includes:

[0020] Control the closing of the local accessory relay and send a hard-line wake-up signal to the fourth controller to wake up the fourth controller; the fourth controller includes a motor controller MCU and a generator controller GCU.

[0021] In one possible implementation, the second controller includes a battery management system BMS and a DC-DC bidirectional converter DC-DC; the method further includes:

[0022] When no working status message sent by any controller is received, an instruction to enter a sleep state is sent to the BMS, the DC-DC, the MCU, and the GCU;

[0023] When it is detected that all controllers stop sending message signals, it starts to enter the sleep state.

[0024] In one possible implementation, after executing the program for entering the standby state, the method further includes:

[0025] Sending a first online message to the OBC, the second controller, the motor controller MCU and the generator controller GCU via the CAN bus;

[0026] When the second online message fed back by any specific controller is not received, a fault reminder is output to the specific controller.

[0027] In a third aspect, an embodiment of the present application provides a controller state control system, the controller state control system comprising a first controller unit and a vehicle controller VCU; the first controller unit comprises an on-board charger OBC and a second controller communicating with the OBC based on the architecture of the first controller unit;

[0028] The OBC is used to collect the connection signal between the power supply device and the local area, and when the connection signal between the power supply device and the local area is collected, it enters the standby state and sends the network management message to the second controller;

[0029] The second controller is used to enter a standby state and feed back a message signal to the VCU when receiving the network management message;

[0030] When the VCU receives a message signal fed back by any second controller, it enters a standby state and sends a hard-line wake-up signal to the fourth controller.

[0031] It should be understood that the second and third aspects of the embodiments of the present application are consistent with the technical solutions of the first aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here.

Brief Description of the Drawings

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 is a schematic diagram of a state control system of a controller proposed in an embodiment of the present application;

[0034] Figure 2 This is a schematic diagram of information interaction between controllers when a controller-based state control system switches states in an example of the present application;

[0035] Figure 3is a flowchart of the state control method of the controller proposed in the embodiment of the present application;

[0036] Figure 4 This is an information flow diagram of an example OBC execution procedure for entering a standby state in the present application;

[0037] Figure 5 This is an information flow diagram of an example of a second controller executing a program for entering a standby state in the present application;

[0038] Figure 6 is another step flow chart of the state control method of the controller proposed in the embodiment of the present application;

[0039] Figure 7 This is an information flow diagram of a procedure for executing an example BDC to enter a standby state in the present application;

[0040] Figure 8 This is an information flow diagram of an exemplary third controller executing a program for entering a standby state in the present application;

[0041] Fig. 9 This is an information flow diagram of a procedure for executing an example VCU to enter a standby state in the present application;

[0042] Fig.10 This is an information flow diagram of an exemplary fourth controller executing a program for entering a standby state in the present application;

[0043] Fig.11 This is another step flow chart of the controller state control method proposed in the embodiment of the present application;

[0044] Fig.12 This is an information flow diagram of an example OBC entering a dormant state in the present application;

[0045] Fig.13 This is an information flow diagram of an example BMS entering a dormant state in this application;

[0046] Fig.14 This is an information flow diagram of an example DC-DC entering a dormant state in the present application;

[0047] Fig.15 This is an information flow diagram of an example BDC entering a dormant state in the present application;

[0048] Fig.16 This is an information flow diagram of an example Tbox entering a dormant state in this application;

[0049] Fig.17 This is an information flow diagram of an example IC entering a dormant state in the present application;

[0050] Fig.18This is an information flow diagram of an example VCU entering a sleep state in the present application;

[0051] Fig.19 This is an information flow diagram of an example of the third controller entering a dormant state in the present application;

[0052] Fig. 20 This is an information flow diagram of an example of the fourth controller entering a sleep state in the present application. [Specific implementation method]

[0053] In order to better understand the technical solution of this specification, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0054] It should be clear that the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0055] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit this specification. The singular forms of "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings.

[0056] In response to the problem that the controllers cannot be put into sleep or wake up in the OFF charging mode of the vehicle, an embodiment of the present application proposes a controller state control system, which can switch the controllers involved in the charging process between sleep state and standby state when the vehicle is not powered on, thereby reducing the energy consumption of the vehicle when each controller remains in the awake state for a long time.

[0057] Figure 1 is a schematic diagram of a state control system of a controller proposed in an embodiment of the present application, such as Figure 1 As shown, the controller's state control system includes a first controller unit and a vehicle control unit (VCU); the first controller unit includes an on-board charger (OBC) and a second controller that communicates with the OBC based on the architecture of the first controller unit.

[0058] In one example of the present application, the OBC and the second controller can communicate based on a multi-master automotive open system architecture (AutosarCAN, AUTOSAR).

[0059] The OBC is used to collect the connection signal between the power supply device and the local area. When the connection signal between the power supply device and the local area is collected, the OBC enters the standby state and sends a network management message to the second controller.

[0060] In one example of the present application, the power supply device may be a charging pile, and the charging gun of a new energy vehicle is inserted into the charging pile. When the power supply device establishes a connection with the new energy vehicle, the OBC can detect a connection signal, and the connection signal includes a CC resistance value and a CP signal. The CC resistance value signal detected by the OBC indicates that the cable connection between the charging gun and the charging pile is complete, and the CP signal detected by the OBC is a pulse signal, which can indicate the capacity of the power supply device. Therefore, the CC signal and the CP signal collected by the OBC indicate that a connection has been established with the power supply device.

[0061] In response to the collected connection signal, the OBC starts executing the local program to enter the standby state, and enters the standby state from the dormant state. The hardware and underlying architecture of the second controller support the Autosar network management message wake-up, and sends the network management message to the second controller through the mechanism of sending the network management message after the OBC enters the standby state.

[0062] The second controller may include a battery management system (BMS), a DC-DC bidirectional converter DC-DC, a vehicle display instrument IC, a telematics box (Tbox) and a bidirectional DC-DC converter (BDC).

[0063] OBC determines the status of the charging pile and feeds back the judgment result to BMS. BMS determines whether the battery needs to be charged. DC-DC is used to convert the high-voltage direct current output by the power supply equipment into direct current used by the low-voltage electronic system. BDC is used for the output and input of the bidirectional regulation circuit.

[0064] The second controller is used to enter a standby state and feed back a message signal to the VCU when receiving the network management message;

[0065] Since the second controller will feedback a message signal to the VCU when it enters the standby state, the wake-up mechanism of the VCU is set to enter the standby state when the VCU receives a message signal from any second controller feedback or OBC. The VCU can also monitor the status of the second controller based on the message information fed back by different second controllers. The message signal fed back by the OBC to the VCU is not a network management message, but a message signal that feeds back its own working status.

[0066] At the same time, after the VCU enters the standby state, it can send a hard-wired wake-up signal to the fourth controller. The fourth controller includes a motor controller (MCU) and a generator controller (GCU). The MCU receives the vehicle driving control instructions from the VCU, controls the motor to output the specified torque and speed, drives the vehicle to drive, converts the DC power of the power battery into the required high-voltage AC power, and drives the motor body to output mechanical energy; the GCU is the core component of the extended-range electric vehicle, which is used to start the engine, convert the engine energy into electrical energy, and charge the battery; therefore, the MCU and GCU also need to be woken up during the charging process.

[0067] In the above wake-up methods, the original mechanisms and interaction habits of each controller are adopted. The OBC is awakened by local wake-up, and the second controller is awakened by the network management message sent by the OBC. The original working mode of further feedback of the message signal to the VCU by the second controller is used to wake up the VCU with the message signal fed back by the second controller. The VCU can further wake up the fourth controller through a hard-line signal, thereby realizing the state switching of the controllers involved in the charging process in the power-off state.

[0068] Another embodiment of the present application proposes a method for waking up a third controller, where the third controller is a car heater (Positive Temperature Coefficient, PTC) or a clutch controller (Clutch control unit, CCU), or both the PTC and the CCU.

[0069] After the BDC in the second controller enters the standby state, it can send a hard-line wake-up signal to the third controller, so that the third controller switches from the sleep state to the standby state.

[0070] Another embodiment of the present application proposes that after the second controller enters the standby state, it will feedback a message signal to the VCU. After the VCU enters the standby state in response to the message signal fed back by the second controller, the second controller, OBC, MCU, GCU, PTC and CCU will continue to send the second online message to the VCU. The VCU can monitor whether each controller is online according to the received second online message. When the VCU does not detect the signal of the GCU and MCU, the VCU determines that the MCU and GCU are faulty and will prohibit the normal operation of the vehicle; the VCU will also send the first online signal to the OBC, the second controller, MCU and GCU, OBC, so that the second controller, MCU and GCU can determine whether they are online, and output an alarm prompt in time when the VCU is not online.

[0071] The controller state control system proposed in the embodiment of the present application, OBC is also used to stop sending network management messages through the OBC and start executing the local sleep program through the OBC when the connection signal between the power supply equipment and the local is not collected. For BDC, Tbox, IC, it is detected that the program to enter the sleep state is started when the network management message is not received. BDC, Tbox, IC meets other judgment criteria and enters the sleep state. When BDC enters the sleep state, PTC and CCU can no longer obtain the hard-line wake-up signal sent by BDC, and PTC and CCU start to execute the program to enter the local sleep state.

[0072] After entering the sleep state, OBC stops sending network management messages to the second controller. The second controller does not detect the network management message and starts to execute the local sleep program. After entering the sleep state, the second controller no longer feeds back the message signal to the VCU. When the VCU detects that any controller does not send a message signal to the local, it determines that the charging program has failed and sends a command to enter the sleep state to the BMS, DC-DC, MCU and GCU. When the VCU detects that all controllers have not sent a message signal, it enters the sleep state; for DC-DC and BMS, after receiving the command to enter the sleep state sent by the VCU, the local sleep program starts to execute. The local sleep program of DC-DC and BMS includes: detecting whether the network management message is received and meeting other judgment criteria. Therefore, for DC-DC and BMS, when the BMS or the DC-DC does not receive the network management message through the OBC and receives the power-off command sent by the vehicle controller VCU, and meets other judgment criteria, it enters the sleep state.

[0073] The present application provides an example of a method in which the VCU sends an instruction to the MCU and the GCU to enter a sleep state, including: disconnecting an accessory relay for waking up the MCU, so that the MCU can no longer receive a hard-line wake-up signal.

[0074] Figure 2 This is a schematic diagram of information interaction between controllers when a controller-based state control system switches states, such as Figure 2As shown, OBC detects CC resistance or CP signal in sleep state and wakes up to enter standby state; after waking up, OBC sends network management message to DC-DC, IC, Tbox, BDC, BMS through CAN line, DC-DC, IC, Tbox, BDC, BMS respond to the network management message transmitted by CAN line to switch from sleep to standby state; OBC, DC-DC, IC, Tbox, BDC, BMS will feedback the second online message to VCU through CAN line in standby state, and the VCU in sleep state receives the message signal fed back by any controller among OBC, DC-DC, IC, Tbox, BDC, BMS, and starts to execute the program of entering standby state locally; after BDC wakes up, the signal transmitted by hard line wakes up PTC and CCU, and after VCU wakes up, the signal transmitted by hard line wakes up MCU and GCU.

[0075] Figure 3 This is a flowchart of the controller state control method steps proposed in the embodiment of the present application, which is applied to the first controller unit in the controller state control system proposed in other embodiments of the present application. The controller state control system also includes a vehicle controller VCU. The first controller unit includes an onboard charger OBC and a second controller that communicates with the OBC based on the architecture of the first controller unit. Figure 3 As shown, the steps include:

[0076] Step S31: When the first controller unit collects the connection signal between the power supply device and the local through the OBC, it sends a network management message to the second controller through the OBC to wake up the second controller.

[0077] The OBC of the first controller unit collects the connection signal and starts to execute the program of entering the standby state. After the OBC enters the standby state, the first controller unit can send a network management message to the second controller through the OBC.

[0078] The second controller includes: BMS, DC-DC, IC, Tbox and BDC.

[0079] Step S32: After the second controller enters the standby state in response to the network management message, a local state mechanism is used to feed back a message signal to the vehicle controller VCU, so that the VCU responds to the message signal and executes a program to enter the standby state.

[0080] The second controller includes: a battery management system BMS, a DC-DC bidirectional converter DC-DC, a vehicle display instrument IC, a remote communication terminal Tbox, and an interleaved parallel bidirectional converter BDC; a local state mechanism in which the second controller responds to the network management message and then enters a standby state and feeds back a message signal to the vehicle controller VCU, including:

[0081] A message signal is fed back to the VCU through a target controller; the target controller is any one or more controllers among the BMS, the DC-DC, the IC, the Tbox and the BDC.

[0082] An example of the present application provides a process of executing a program to enter a standby state after the OBC collects a connection signal. Figure 4 This is an information flow diagram of an example OBC execution program entering the standby state of the present application, such as Figure 4 As shown, the process from when OBC starts to execute the program for entering the standby state to when it enters the standby state includes:

[0083] K41: Determine whether CC resistance or CP signal is detected through hard line;

[0084] K42: If CC resistance or CP signal is not detected, continue to detect; if CC resistance or CP signal is detected, OBC starts the wake-up program to determine whether the local initialization is completed;

[0085] K43: If the OBC initialization is completed, send a network management message to the BMS, DC-DC, IC, Tbox and BDC, and feedback to the VCU in the second online message. The second online message sent by the OBC contains data: the working mode of the OBC is no working mode, and the working state of the OBC is standby; if the OBC initialization is not completed, determine whether the waiting time exceeds 200ms;

[0086] K44: If the waiting time does not exceed 200ms, return to K43. If the waiting time exceeds 200ms, OBC outputs a prompt indicating that initialization failed.

[0087] This application provides an example of a process in which BMS, IC, Tbox, and DC-DC collect network management messages and execute a program to enter a standby state. Figure 5 This is an information flow diagram of an example of a second controller executing a program to enter a standby state in the present application, such as Figure 5 As shown, the process from when BMS, IC, Tbox, and DC-DC start to execute the program to enter the standby state to when entering the standby state includes:

[0088] K51: Determines whether a wake-up signal is detected by detecting whether a network management message is received;

[0089] K52: If a wake-up signal is detected, wake-up begins. BMS, IC, Tbox, and DC-DC determine whether local initialization is complete. If no network management message is received, detection continues.

[0090] K53: If the initialization of BMS, IC, Tbox, and DC-DC is completed, feedback is sent to VCU in the second online message. The second online message sent by BMS, IC, Tbox, and DC-DC contains data: the working status of BMS, IC, Tbox, and DC-DC is standby; if the initialization of BMS, IC, Tbox, and DC-DC is not completed, determine whether the waiting time exceeds 200ms;

[0091] K54: If the waiting time does not exceed 200ms, return to K53. If the waiting time exceeds 200ms, a prompt will appear indicating that the BMS, IC, Tbox, and DC-DC output initialization have failed.

[0092] Figure 6 is another step flow chart of the controller state control method proposed in the embodiment of the present application, such as Figure 6 As shown, the controller state control method includes the steps of:

[0093] Step S61: When the first controller unit collects the connection signal between the power supply device and the local through the OBC, it sends a network management message to the second controller through the OBC.

[0094] Step S62: Feedback a message signal to the vehicle control unit VCU through a local status mechanism in which the second controller enters a standby state in response to the network management message and then feeds back a message signal to the VCU.

[0095] Step S63: By controlling the accessory relay of the BDC to close, a hard-line wake-up signal is sent to the third controller to wake up the third controller; the third controller is at least one of the vehicle heater PTC and the clutch controller CCU.

[0096] After the BDC in the second controller enters the standby state, the first controller unit can send a hard-line wake-up signal to the third controller PTC and CCU through the accessory relay of the BDC. The PTC and CCU execute the program of entering the standby state locally in response to the hard-line wake-up signal.

[0097] This application provides an example of a process in which a BDC collects network management messages and executes a program to enter a standby state. Figure 7 This is an information flow diagram of an example BDC execution program entering the standby state of the present application, such as Figure 7 As shown, the process from when the BDC starts executing the program for entering the standby state to when it enters the standby state includes:

[0098] K71: Determine whether the network management message is received;

[0099] K72: If a network management message is received, the BDC determines whether the local initialization is completed. If no network management message is received, the detection continues;

[0100] K73: If BDC initialization is completed, BDC outputs a hard-wired wake-up signal to PTC and CCU;

[0101] K74: Feedback is sent to VCU in the second online message. The second online message sent by BDC contains data: the working status of BDC.

[0102] Figure 8 This is an information flow diagram of an example of a third controller executing a program to enter a standby state in the present application, such as Figure 8 As shown, the process from when PTC and CCU start to execute the program to enter the standby state to when they enter the standby state includes:

[0103] K81: collects the hard-wire wake-up signal, starts the wake-up process, and determines whether the local initialization is completed;

[0104] K82: If the initialization of PTC and CCU is completed, feedback is sent to VCU in the second online message. The second online message sent by PTC and CCU contains data: the working state of OBC is standby state. If the initialization of PTC and CCU is not completed, it is determined whether the waiting time exceeds 300ms.

[0105] K83: If the waiting time does not exceed 300ms, return to K82. If the waiting time exceeds 300ms, PTC and CCU output initialization failure prompts.

[0106] according to Figure 4 , Figure 5 , Figure 7 , Figure 8 In the controller wake-up example shown, the controller will feedback a message signal to the VCU. Fig. 9 This is an information flow diagram of an example VCU executing a program to enter the standby state in this application. The VCU receives a message signal feedback from any controller to wake up the process as shown in FIG. Fig. 9 As shown:

[0107] K91: VCU determines whether a wake-up signal is detected by detecting whether a message signal sent by any controller is received;

[0108] K92: If a wake-up signal is detected, the wake-up process starts to determine whether the local initialization is completed. If no message signal is detected, the detection continues;

[0109] K93: If initialization is completed, VCU outputs a wake-up signal to MCU and GCU through the main relay hard line; if initialization is not completed, determine whether the waiting time exceeds 200ms. If the waiting time does not exceed 200ms, return to K92. If the waiting time exceeds 200ms, VCU outputs a prompt indicating that initialization failed.

[0110] K94: After the VCU is initialized, it performs mode recognition to determine whether it is currently in charging mode;

[0111] K95: If it is not recognized as charging mode, VCU jumps to other modes. If it is recognized as charging mode, it sends the first online message to other controllers via CAN line. Other controllers may include OBC, BDC, DC-DC, IC, Tbox, etc.

[0112] An example of the present application provides a process in which the fourth controller MCU and the GCU collect network management messages and execute a program to enter a standby state. Fig.10 This is an information flow diagram of an example of a fourth controller executing a program to enter a standby state in the present application, such as Fig.10 As shown in the figure, the process from when the MCU and GCU start to execute the program to enter the standby state to when they enter the standby state includes:

[0113] K101: MCU and GCU receive the wake-up signal sent by VCU through the hard line, start the wake-up process, and determine whether the local initialization is completed. If the initialization is completed, the second online message is sent to VCU through the CAN line. The second online message sent by MCU and GCU includes data: initialization completion flag = initialization passed; if the initialization is not completed, determine whether the waiting time exceeds 300ms;

[0114] K102: If the waiting time does not exceed 300ms, return to K101. If the waiting time exceeds 300ms, the MCU and GCU output prompts that initialization failed.

[0115] Fig.11 It is another step flow chart of the state control method of the controller proposed in the embodiment of the present application, which is applied to the first controller unit in the state control system of the controller proposed in other embodiments of the present application, such as Fig.11 As shown, the steps include:

[0116] Step S111: determining whether a connection signal between the power supply device and the local area is collected;

[0117] Step S112: When the first controller unit collects the connection signal between the power supply device and the local through the OBC, it sends a network management message to the second controller through the OBC to wake up the second controller.

[0118] Step S1121: After the second controller enters the standby state in response to the network management message, a local state mechanism that feeds back to the vehicle controller VCU is used to feed back a message signal to the VCU, so that the VCU responds to the message signal and executes a program to enter the standby state.

[0119] Step S113: when the first controller unit fails to collect a connection signal between the power supply device and the local area through the OBC, it stops sending network management messages through the OBC and starts executing a local sleep program through the OBC;

[0120] Step S1131: when the network management message is not received by the second controller, the local sleep program is started to be executed by the second controller.

[0121] Among them, the BMS and DC-DC in the second controller will comprehensively judge whether to enter the sleep state according to the network management message and the instruction sent by the VCU. When the BMS or the DC-DC does not receive the network management message through the OBC and receives the power-off instruction sent by the vehicle controller VCU, it enters the sleep state.

[0122] If the OBC fails to collect the connection signal between the power supply equipment and the local area, it will execute its local sleep program and stop sending network management messages to the second controller. If the BDC, IC, and Tbox of the second controller detect that they have not received the network management message, they will start to execute the local sleep program.

[0123] After the second controller completes the execution of the local sleep program and enters the sleep state, it stops sending feedback messages to the VCU. When the VCU does not receive any feedback message signals from any controller, it starts to execute the local sleep program, which includes sending instructions to enter the sleep state to the BMS, the DC-DC, the MCU, and the GCU. When the VCU does not receive feedback message signals from all controllers, it completes the local sleep program and enters the sleep state.

[0124] MCU and GCU cannot receive the hard-wired wake-up signal sent by VCU, and will start to execute the local sleep program. PTC and CCU cannot receive the hard-wired wake-up signal sent by BDC, and will start to execute the local sleep program.

[0125] This application provides an example of the process of OBC executing the local sleep program. Fig.12 This is an example of an information flow diagram of an OBC entering a dormant state in this application, such as Fig.12 As shown, the process from when OBC starts to execute the program for entering the standby state to when it enters the standby state includes:

[0126] K121: Determine whether CC resistance or CP signal is collected;

[0127] K122: If the CC resistance value or CP signal is collected, determine whether the timing wait time exceeds 5 minutes; if the timing wait time exceeds 5 minutes, OBC stops sending network management messages to the second controller, and detects whether the CC resistance value or CP signal can still be collected. If the CC resistance value or CP signal can continue to be collected, power on again and enter the standby state. If the CC resistance value or CP signal cannot continue to be collected, OBC enters the sleep state.

[0128] K123: If the CC resistance value or CP signal cannot be collected, determine whether the waiting time exceeds 10s. If the waiting time exceeds 10s, OBC stops sending network management messages to the second controller and detects whether the CC resistance value or CP signal can still be collected. If the CC resistance value or CP signal can continue to be collected, power on again and enter the standby state. If the CC resistance value or CP signal cannot continue to be collected, OBC enters the sleep state.

[0129] This application provides an example of a process in which a BMS executes a local sleep program. Fig.13 This is an example of the information flow diagram of the BMS entering the dormant state in this application, such as Fig.13 As shown, the process from when the BMS starts to execute the program to enter the standby state to when it enters the standby state includes:

[0130] K131: Receive the power-off command sent by the VCU, which includes data: battery operation enable = no, the BMS feeds back the current status data to the VCU, and determines whether the wake-up signal is detected by detecting whether the network management message is received;

[0131] K132: If a network management message is received, determine whether the local area meets the re-wake-up condition. If the re-wake-up condition is met, power on again and enter the standby state. If the re-wake-up condition is not met, return to K131 to determine whether the network management message is received;

[0132] K133: If the network management message is not received, determine whether the waiting time exceeds 1s. If the waiting time does not exceed 1s, return to K131 to determine whether the network management message is received. If the waiting time exceeds 1s, check whether the network management message is still not received to determine whether the network management message is stopped. The number of times the network management message cannot be received can be preset.

[0133] K134: If it is determined that the network management message has stopped being sent, the BMS enters a dormant state. If it is determined that the network management message has not stopped being sent, it returns to K133 to check whether the network management message still cannot be received.

[0134] This application provides an example of a process in which a DC-DC executes a local sleep program. Fig.14This is an example of the information flow diagram of a DC-DC entering a dormant state in the present application, such as Fig.14 As shown, the process from the DC-DC starting to execute the procedure of entering the standby state to entering the standby state includes:

[0135] K141: Receives the power-off command sent by the VCU, which includes data: DC-DC is not enabled. When the DC-DC detects that the local is not enabled, it stops outputting and feeds back the current status data to the VCU, and determines whether the network management message is stopped by detecting whether the network management message cannot be received continuously; the number of times the network management message cannot be received continuously can be preset;

[0136] K142: If it is determined that the network management message stops being sent, the DC-DC enters a dormant state. If it cannot be determined that the network management message stops being sent, the process returns to K141 to detect whether the network management message continues to be unable to be received.

[0137] This application provides an example of a process in which a BDC executes a local sleep program. Fig.15 This is an example of the information flow diagram of the BDC entering the dormant state in this application, such as Fig.15 As shown, the process from when the BDC starts executing the program for entering the standby state to when it enters the standby state includes:

[0138] K151: Determines whether a wake-up signal is detected by detecting whether a network management message is collected;

[0139] K152: If no network management message is detected, stop outputting the accessory relay hard-wire wake-up signal to the PTC and CCU, and determine whether the BDC meets the sleep condition by detecting whether the network management message cannot be received continuously;

[0140] K153: If the sleep condition is met, the BDC enters the sleep state. If the sleep condition is not met, it returns to K152 to determine whether the BDC meets the sleep condition by detecting whether it continues to be unable to receive network management messages.

[0141] This application provides an example of the process of Tbox executing the local sleep program. Fig.16 This is an example of the information flow diagram of the Tbox entering the dormant state in this application, such as Fig.16 As shown, the process from Tbox starting to execute the program to enter the standby state to entering the standby state includes:

[0142] K161: Determine whether a wake-up signal is detected by detecting whether a network management message is received;

[0143] K162: If a wake-up signal is detected, the local conditions are judged to determine whether the conditions for re-wake-up are met. If the conditions for re-wake-up are met, Tbox re-executes Figure 5The program shown here enters the standby state locally; if it is not satisfied, wake up again and return to K161;

[0144] K163: If the wake-up signal is not detected, the network management message is determined to be stopped by judging whether the wake-up signal is continuously collected. If it is determined that the network management message is stopped, the Tbox determines whether the data is sent completely. If it cannot be determined that the network management message is stopped, the Tbox continues to try to collect the network management message.

[0145] K164: If data transmission is completed, Tbox enters sleep mode. If data transmission is not completed, Tbox continues to send data.

[0146] This application provides an example of the process of IC executing the local sleep program. Fig.17 This is an information flow diagram of an example IC entering a sleep state in this application, such as Fig.17 As shown, the process from when the IC starts to execute the program to enter the standby state to when it enters the standby state includes:

[0147] K171: Determines whether a wake-up signal is detected by detecting whether a network management message is received;

[0148] K172: If a wake-up signal is detected, the local conditions are judged to determine whether the conditions for re-wake-up are met. If the conditions for re-wake-up are met, the IC re-executes Figure 5 The program shown here enters the standby state locally; if it is not satisfied, wake up again and return to K171;

[0149] K173: If the wake-up signal is not detected, the IC determines whether the network management message has stopped being sent by judging whether the wake-up signal is continuously collected. If it is determined that the network management message has stopped being sent, the IC determines whether the data has been sent. If it cannot be determined that the network management message has stopped being sent, the IC continues to try to collect network management messages.

[0150] This application provides an example of a process in which a VCU executes a local sleep program. Fig.18 This is an example of an information flow diagram of a VCU entering a sleep state in the present application, such as Fig.18 As shown, the process from when the VCU starts to execute the program for entering the standby state to when it enters the standby state includes:

[0151] K181: By detecting whether the BMS sends the information that the BMS working state = standby, it is determined whether the BMS is in the standby state. By detecting whether the DC-DC sends the information that the DC-DC working state = standby, it is determined whether the DC-DC is in the standby state. Fig.13 and Fig.14As shown, BMS and DC-DC receive the instruction to enter the sleep state sent by VCU, and start to execute the local program to enter the standby state. When VCU does not receive the working status message fed back by any controller, it sends an instruction to enter the sleep state to BMS and DC-DC. The instruction to enter the sleep state can be a low-voltage standby instruction.

[0152] K182: If the BMS and DC-DC are in standby mode, determine whether a wake-up signal is detected by determining whether all controller feedback messages are received; if the BMS and DC-DC are not in standby mode, determine whether the waiting time of the last feedback message from the BMS and DC-DC exceeds 500ms. If it exceeds 500ms, determine whether a wake-up signal is detected by determining whether all controller feedback messages are received. If it does not exceed 500ms, return to K181.

[0153] K183: If a wake-up signal is detected, Fig. 9 The process shown determines whether the re-awakening condition is satisfied. If the re-awakening condition is satisfied, the VCU executes the procedure for entering the standby state. If the re-awakening condition is not satisfied, the process returns to K172.

[0154] K184: If the wake-up signal is not detected, determine whether the time for which the wake-up signal is not detected exceeds 0.1s. If it does not exceed 0.1s, continue to detect whether the wake-up signal is collected. If it exceeds 0.1s, stop outputting the hard-line wake-up signal to the MCU and GCU.

[0155] K185: Determine whether the network management message stops being sent by judging whether the message signals fed back by all controllers are continuously collected. If it is determined that the network management message stops being sent, the VCU enters the sleep state.

[0156] This application provides an example of a process in which the third controller PTC and CCU execute a local sleep program. Fig.19 This is an example of an information flow diagram of the third controller entering a dormant state in the present application, such as Fig.19 As shown, the process from when PTC and CCU start to execute the program to enter the standby state to when they enter the standby state includes:

[0157] K191: Determines whether a wake-up signal is detected by detecting whether a hard-line signal sent by BCD is received;

[0158] K192: If a wake-up signal is detected, return to K191. If no wake-up signal is detected, determine whether the duration of not detecting the wake-up signal exceeds 0.1s. If it exceeds 0.1s, PTC and CCU enter the sleep state.

[0159] This application provides an example of a process in which the fourth controller MCU and GCU execute a local sleep program. Fig. 20This is an example of an information flow diagram of the fourth controller entering a dormant state in the present application, such as Fig. 20 As shown in the figure, the process from when the MCU and GCU start to execute the program to enter the standby state to when they enter the standby state includes:

[0160] K201: Determines whether a wake-up signal is detected by detecting whether a hard-line signal sent by the VCU is received;

[0161] K202: If a wake-up signal is detected, return to K201. If no wake-up signal is detected, determine whether the duration of not detecting the wake-up signal exceeds 0.2s. If it exceeds 0.2s, the MCU and GCU enter the sleep state.

[0162] The state control method of the controller provided in the above-mentioned embodiment is used to execute the technical solution of the above-mentioned method embodiment. Its implementation principle and technical effects can be further referred to the relevant description in the embodiment of the state control system of the controller, which will not be repeated here.

[0163] Another embodiment of the present application proposes a state control method of a controller applied to a VCU, which is applied to a VCU of a state control system of a controller proposed in other embodiments of the present application, wherein the state control system of the controller further includes a first controller unit, wherein the first controller unit includes an on-board charger OBC and a second controller communicating with the OBC based on the architecture of the first controller unit, and the method includes:

[0164] When the VCU receives a message signal fed back by any controller in the second controller, it starts to execute a program for entering a local standby state;

[0165] The message signal is generated after the second controller enters a standby state in response to a network management message sent by the OBC; the OBC sends a network management message to the second controller when collecting a connection signal between the power supply device and the local area.

[0166] Optionally, after starting to execute the program for entering the standby state locally, the method further includes:

[0167] Control the closing of the local accessory relay and send a hard-line wake-up signal to the fourth controller to wake up the fourth controller; the fourth controller includes a motor controller MCU and a generator controller GCU.

[0168] Optionally, the second controller includes a battery management system BMS and a DC-DC bidirectional converter DC-DC; the method further includes:

[0169] When no working status message sent by any controller is received, an instruction to enter a sleep state is sent to the BMS, the DC-DC, the MCU, and the GCU;

[0170] When it is detected that all controllers stop sending message signals, it starts to enter the sleep state.

[0171] Optionally, after executing the procedure for entering the standby state, the method further includes:

[0172] Sending a first online message to the OBC, the second controller, the motor controller MCU and the generator controller GCU via the CAN bus;

[0173] When the second online message fed back by any specific controller is not received, a fault reminder is output to the specific controller.

[0174] The optional examples of the state control method of the controller in the embodiment of the present application have been described in the embodiment applied on the first controller unit side, and the embodiment on the VCU side will not be repeated.

[0175] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0176] In the description of the embodiments of the present application, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of this specification. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradicting each other.

[0177] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the description of this specification, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0178] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of this specification includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of this specification belong.

[0179] The word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0180] It should be noted that the terminals involved in the embodiments of the present application may include but are not limited to personal computers (PCs), personal digital assistants (PDAs), wireless handheld devices, tablet computers, mobile phones, MP3 players, MP4 players, etc.

[0181] In the several embodiments provided in this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0182] In addition, each functional unit in each embodiment of this specification may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0183] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform some steps of the method described in each embodiment of this specification. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, and other media that can store program codes.

[0184] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A controller state control method, characterized in that: A first controller unit applied to a state control system of a controller, wherein the state control system of the controller further comprises a vehicle controller VCU, wherein the first controller unit comprises an on-board charger OBC and a second controller communicating with the OBC based on the architecture of the first controller unit; the method comprises: When the first controller unit collects the connection signal between the power supply device and the local through the OBC, it sends a network management message to the second controller through the OBC to wake up the second controller; The local status mechanism through which the second controller responds to the network management message and enters the standby state and then feeds back the message signal to the vehicle controller VCU.

2. The method according to claim 1, characterized in that The second controller includes a staggered parallel bidirectional converter BDC. After sending the network management message to the second controller, the method further includes: By controlling the accessory relay of the BDC to close, a hard-line wake-up signal is sent to the third controller to wake up the third controller; the third controller is at least one of the vehicle heater PTC and the clutch controller CCU.

3. The method according to claim 1, characterized in that The second controller includes: a battery management system BMS, a DC-DC bidirectional converter DC-DC, a vehicle display instrument IC, a remote communication terminal Tbox, and an interleaved parallel bidirectional converter BDC; a local state mechanism in which the second controller responds to the network management message and then enters a standby state and feeds back a message signal to the vehicle controller VCU, including: A message signal is fed back to the VCU through a target controller; the target controller is any one or more controllers among the BMS, the DC-DC, the IC, the Tbox and the BDC.

4. The method according to claim 1, characterized in that The method further comprises: When the first controller unit fails to collect a connection signal between the power supply device and the local area through the OBC, it stops sending network management messages through the OBC and starts executing a local sleep program through the OBC; When the network management message is not received through the second controller, the local sleep program is started to be executed through the second controller.

5. The method according to claim 4, characterized in that The second controller includes a battery management system BMS and a DC-DC bidirectional converter DC-DC. When the network management message is not received by the second controller, the local sleep program is started to be executed by the second controller, including: When the BMS or the DC-DC does not receive the network management message through the OBC and receives a power-off instruction sent by the vehicle controller VCU, it enters a sleep state.

6. A controller state control method, characterized in that: A VCU applied to a state control system of a controller, wherein the state control system of the controller further comprises a first controller unit, wherein the first controller unit comprises an on-board charger OBC and a second controller communicating with the OBC based on an architecture of the first controller unit, wherein the method comprises: When the VCU receives a message signal fed back by any controller in the second controller, it starts to execute a program for entering a local standby state; The message signal is generated after the second controller enters a standby state in response to a network management message sent by the OBC; the OBC sends a network management message to the second controller when collecting a connection signal between the power supply device and the local area.

7. The method according to claim 6, characterized in that After starting to execute the procedure of entering the standby state locally, the method further includes: Control the closing of the local accessory relay and send a hard-line wake-up signal to the fourth controller to wake up the fourth controller; the fourth controller includes a motor controller MCU and a generator controller GCU.

8. The method according to claim 7, characterized in that The second controller includes a battery management system BMS and a DC-DC bidirectional converter DC-DC; the method further includes: When no working status message sent by any controller is received, an instruction to enter a sleep state is sent to the BMS, the DC-DC, the MCU, and the GCU; When it is detected that all controllers stop sending message signals, it starts to enter the sleep state.

9. The method according to claim 6, characterized in that After executing the procedure for entering the standby state, the method further includes: Sending a first online message to the OBC, the second controller, the motor controller MCU and the generator controller GCU via the CAN bus; When the second online message fed back by any specific controller is not received, a fault reminder is output to the specific controller.

10. A state control system of a controller, characterized in that: The state control system of the controller includes a first controller unit and a vehicle controller VCU; the first controller unit includes an on-board charger OBC and a second controller communicating with the OBC based on the architecture of the first controller unit; The OBC is used to collect the connection signal between the power supply device and the local area, and when the connection signal between the power supply device and the local area is collected, it enters the standby state and sends a network management message to the second controller; The second controller is used to enter a standby state and feed back a message signal to the VCU when receiving the network management message; When the VCU receives a message signal fed back by any second controller, it enters a standby state and sends a hard-line wake-up signal to the fourth controller.

Images