Electric vehicle controller and electric vehicle

Abstract

The utility model relates to electric automobile controller and electric automobile belongs to electric automobile technical field. In electric automobile controller, power control peripheral circuit is used for gathering first state data;Battery management peripheral circuit is used for gathering second state data;Charging communication peripheral circuit is used for gathering third state data. Processor is used for executing the function logic of vehicle control unit according to first state data and obtains power control data, executes the function logic of battery management system according to second state data and obtains battery control data, executes the function logic of charging communication controller according to third state data and obtains charging control data;Power control peripheral circuit is used for outputting power control data to first external device;Battery management peripheral circuit is used for outputting battery control data to second external device;Charging communication peripheral circuit is used for outputting charging control data to third external device. The application effectively reduces the transmission load of CAN bus in vehicle control system.

Description

Technical Field

[0001] This utility model relates to the field of electric vehicle technology, and in particular to an electric vehicle controller and an electric vehicle. Background Technology

[0002] The Vehicle Control Unit (VCU), Battery Management System (BMS), and Electric Vehicle Communication Controller (EVCC) are three essential vehicle controllers in an electric vehicle's control system. Current vehicle control systems are typically distributed architectures, with units communicating via a Controller Area Network (CAN) bus. In this distributed architecture, the VCU, BMS, and EVCC are three independent controllers. They communicate with each other via the CAN bus to collaboratively control vehicle operation.

[0003] The signals transmitted on the CAN bus must conform to the standard CAN protocol. This means that when a single controller sends data via the CAN bus, it needs to encode the raw data to be sent into a standard CAN signal for output. Similarly, when a single controller receives data via the CAN bus, it also needs to parse the received standard CAN signal into raw data that the controller can understand in order to perform subsequent data processing. Furthermore, during communication between two controllers via the CAN bus, they need to repeatedly send CAN acknowledgment commands and receive CAN feedback status to maintain communication between devices, in accordance with the CAN bus acknowledgment mechanism. Clearly, the CAN bus transmission load between the VCU, BMS, and EVCC is high, resulting in a high CAN bus transmission load problem in the vehicle control system. Utility Model Content

[0004] In view of this, the present invention aims to provide an electric vehicle controller and an electric vehicle to solve or partially solve the technical problem of high transmission load of CAN bus in existing electric vehicles.

[0005] In a first aspect, this utility model provides an electric vehicle controller, which is applied to an electric vehicle including a first external device, a second external device, and a third external device. The electric vehicle controller includes: a processor, a power control peripheral circuit, a battery management peripheral circuit, and a charging communication peripheral circuit.

[0006] The power control peripheral circuit is connected to the processor and is used to collect and transmit first state data to the processor. The first state data is the data required to realize the function of the vehicle control unit.

[0007] The battery management peripheral circuit is connected to the processor and is used to collect and transmit second state data to the processor. The second state data is the data required to realize the functions of the battery management system.

[0008] The charging communication peripheral circuit is connected to the processor and is used to collect and transmit third state data to the processor. The third state data is the data required to realize the charging communication controller.

[0009] The processor is at least configured to execute the functional logic of the vehicle control unit according to the first state data, obtain and output power control data to the power control peripheral circuit, execute the functional logic of the battery management system according to the second state data, obtain and output battery control data to the battery management peripheral circuit, and execute the functional logic of the charging communication controller according to the third state data, obtain and output charging control data to the charging communication peripheral circuit.

[0010] The power control peripheral circuit is used to connect to the first external device and output the power control data to the first external device;

[0011] The battery management peripheral circuit is used to connect to the second device and output the battery control data to the second external device;

[0012] The charging communication peripheral circuit is used to connect to the third external device and output the charging control data to the third external device.

[0013] Secondly, embodiments of the present invention provide an electric vehicle, including the electric vehicle controller described in any of the first aspects.

[0014] This utility model discloses an electric vehicle controller comprising: a processor, a power control peripheral circuit, a battery management peripheral circuit, and a charging communication peripheral circuit. The power control peripheral circuit collects and transmits first state data to the processor. The battery management peripheral circuit collects and transmits second state data to the processor. The charging communication peripheral circuit collects and transmits third state data to the processor. The processor is at least used to execute the functional logic of the vehicle control unit based on the first state data, obtain and output power control data to the power control peripheral circuit, so that the power control peripheral circuit outputs power control data to a first external device. The processor is at least used to execute the functional logic of the battery management system based on the second state data, obtain and output battery control data to the battery management peripheral circuit, so that the battery management peripheral circuit outputs battery control data to a second external device. The processor is also at least used to execute the functional logic of the charging communication controller based on the third state data, obtain and output charging control data to the charging communication peripheral circuit, so that the charging communication peripheral circuit outputs charging control data to a third external device.

[0015] In this technical solution, the first state data is the data required to realize the function of the vehicle control unit. The second state data is the data required to realize the function of the battery management system. The third state data is the data required to realize the charging communication controller. The electric vehicle controller uses a processor, power control peripheral circuits, battery management peripheral circuits, and charging communication peripheral circuits to realize the functions of the vehicle control unit, battery management system, and charging communication controller. Therefore, compared with related technologies, it saves the CAN bus interconnection between the vehicle control unit, battery management system, and charging communication controller, and changes the data interaction between the vehicle control unit, battery management system, and charging communication controller based on the CAN bus to internal data calls within the devices, effectively reducing the transmission load of the CAN bus in the vehicle control system.

[0016] The above description is merely an overview of the technical solution of this utility model. In order to better understand the technical means of this utility model and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this utility model more obvious and understandable, specific embodiments of this utility model are given below. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this utility model, the drawings used in the description of the embodiments of this utility model will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this utility model. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1One of the structural schematic diagrams of the electric vehicle controller provided in this utility model embodiment;

[0019] Figure 2 A second schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the present utility model;

[0020] Figure 3 The third schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the utility model;

[0021] Figure 4 Fourth schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the utility model;

[0022] Figure 5 Fifth schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the utility model;

[0023] Figure 6 Sixth schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the present utility model;

[0024] Figure 7 Seventh schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the present utility model;

[0025] Figure 8 Eighth schematic diagram of the structure of the electric vehicle controller provided in this embodiment of the utility model;

[0026] Figure 9 Schematic diagram nine of the electric vehicle controller provided in this embodiment of the present utility model;

[0027] Figure 10 This is one of the functional diagrams of the various control units provided in the embodiments of this utility model at the application layer. Detailed Implementation

[0028] Exemplary embodiments of the present invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0029] The Vehicle Control Unit (VCU), Battery Management System (BMS), and Electric Vehicle Control Center (EVCC) are three essential vehicle controllers in the vehicle control system of an electric vehicle. Current vehicle control systems are typically distributed architecture systems, with units communicating via a CAN bus. In this distributed architecture, the VCU, BMS, and EVCC are three independent controllers. They communicate with each other via the CAN bus to collaboratively control vehicle operation. For example, the interaction between the VCU and BMS spans the entire lifecycle of the electric vehicle. The VCU sends wake-up, power-on / off commands, operating mode information, and retrieves information such as BMS and battery pack status, as well as vehicle fault status, to the BMS. This allows the BMS to respond with battery status information (such as State of Charge (SOC), State of Health (SOH), State of Power (SOP), charging control, thermal management requirements, etc.) and fault status information back to the VCU.

[0030] The signals transmitted on the CAN bus must conform to the standard CAN protocol. This requires a single controller to encode the raw data to be transmitted into a standard CAN signal output when sending data via the CAN bus. Similarly, when a single controller receives data via the CAN bus, it must parse the received standard CAN signal into raw data that the controller can understand in order to perform subsequent data processing. Furthermore, during communication between two controllers via the CAN bus, they need to repeatedly send CAN acknowledgment commands and receive CAN feedback status to maintain communication between devices in accordance with the CAN bus acknowledgment mechanism. Obviously, the CAN bus transmission load between the VCU, BMS, and EVCC is high, resulting in a high CAN bus transmission load problem in the vehicle control system. In addition, the three independent controllers of VCU, BMS, and EVCC have three sets of independently controlled software and interfaces, which also increases the workload of CAN bus matrix development, software interface development, signal diagnostics, etc., resulting in high development costs.

[0031] In particular, the charging and discharging process of electric vehicles is more complex, involving information exchange between the VCU and BMS, the BMS and EVCC, and the EVCC and VCU. Therefore, during the charging and discharging process of an electric vehicle, the VCU and BMS, the BMS and EVCC, and the EVCC and VCU need to repeatedly send CAN acknowledgment commands and receive CAN feedback status via CAN bus to maintain communication between devices, following the CAN bus acknowledgment mechanism. If any node experiences a communication failure such as signal frame loss, bus congestion, or communication loss, a charging and discharging failure will occur, triggering the charging and discharging function to malfunction. Clearly, the CAN bus transmission method between the VCU, BMS, and EVCC not only suffers from high CAN bus transmission load but also from high CAN bus communication latency and susceptibility to communication failures.

[0032] Please refer to Figure 1 This illustration shows a structural schematic diagram of an electric vehicle controller provided in an embodiment of this application. The electric vehicle controller 1 provided in this embodiment is applied to an electric vehicle. Figure 1 As shown, the electric vehicle controller 1 includes: a processor 12, a power control peripheral circuit 13, a battery management peripheral circuit 14, and a charging communication peripheral circuit 15.

[0033] The power control peripheral circuit 13 is connected to the processor 12. The power control peripheral circuit 13 is used to collect and transmit first state data to the processor 12. The battery management peripheral circuit 14 is connected to the processor 12. The battery management peripheral circuit 14 is used to collect and transmit second state data to the processor 12. The charging communication peripheral circuit 15 is connected to the processor 12. The charging communication peripheral circuit 15 is used to collect and transmit third state data to the processor 12. The first state data is the data required to implement the functions of the vehicle control unit. The second state data is the data required to implement the functions of the battery management system. The third state data is the data required to implement the charging communication controller.

[0034] The processor 12 is at least configured to execute the functional logic of the vehicle control unit based on the first state data, obtain and output power control data to the power control peripheral circuit 13. The processor 12 is also at least configured to execute the functional logic of the battery management system based on the second state data, obtain and output battery control data to the battery management peripheral circuit 14. The processor 12 is also at least configured to execute the functional logic of the charging communication controller based on the third state data, obtain and output charging control data to the charging communication peripheral circuit 15.

[0035] Accordingly, the electric vehicle includes a first external device, a second external device, and a third external device. The power control peripheral circuit 13 is also used to connect to the first external device and output power control data to the first external device, so that the first external device executes the vehicle power control operation corresponding to the power control data. The battery management peripheral circuit 14 is also used to connect to the second external device and output battery control data to the second external device, so that the second external device executes the electric vehicle battery control operation corresponding to the battery control data. The charging communication peripheral circuit 15 is also used to connect to the third external device and output charging control data to the third external device, so that the third external device executes the charging control operation corresponding to the charging control data.

[0036] In one or more embodiments, processor 12 can also be used to execute the functional logic of the vehicle control unit without relying on the first state data, thereby obtaining and outputting power control data to the power control peripheral circuit 13. Similarly, processor 12 can also be used to execute the functional logic of the battery management system without relying on the second state data, thereby obtaining and outputting battery control data to the battery management peripheral circuit 14. Processor 12 can also be used to execute the functional logic of the charging communication controller without relying on the third state data, thereby obtaining and outputting charging control data to the charging communication peripheral circuit 15. Optionally, processor 12 can be a microcontroller unit (MCU) or a central processing unit (CPU), etc.

[0037] Obviously, in the electric vehicle controller 1 provided in this application embodiment, the power control peripheral circuit 13 can provide the data acquisition function of the existing vehicle control unit, and send the acquired first state data for realizing the function of the vehicle control unit to the processor 12, so that the processor 12 can execute the functional logic of the existing vehicle control unit, generate power control data, and transmit it to the first external device through the power control peripheral circuit 13 to realize the function of the vehicle control unit.

[0038] Furthermore, the battery management peripheral circuit 14 can provide the data acquisition function of the existing battery management system and send the acquired second state data for implementing the functions of the battery management system to the processor 12, so that the processor 12 can execute the functional logic of the existing battery management system, generate battery control data, and transmit it to the second external device through the battery management peripheral circuit 14 to realize the functions of the battery management system.

[0039] Similarly, the charging communication peripheral circuit 15 can provide the data acquisition function of the existing charging communication controller and send the acquired third state data for implementing the function of the charging communication controller to the processor 12, so that the processor 12 can execute the functional logic of the existing charging communication controller, generate charging control data, and transmit it to the third external device through the charging communication peripheral circuit 15 to realize the function of the charging communication controller.

[0040] Therefore, the electric vehicle controller 1 provided in this application embodiment is a cross-domain integrated controller that integrates the functions of a vehicle control unit, a battery management system, and a charging communication controller. The electric vehicle controller integrates the functions of the vehicle control unit, battery management system, and charging communication controller—these high-voltage control components—into a single controller. This allows the processor 12 in the electric vehicle controller 1 to still execute the original functional logic of the vehicle control unit, battery management system, and charging communication controller, and to remain connected to the first external device, second external device, and third external device respectively via the power control peripheral circuit 13, battery management peripheral circuit 14, and charging communication peripheral circuit 15, maintaining the original connection relationships between the vehicle control unit, battery management system, and charging communication controller and their respective controlled devices. Therefore, the electric vehicle controller 1 provided in this application embodiment maintains consistency in its application layer strategy and distributed architecture under the functions of the vehicle control unit, battery management system, and charging communication controller, effectively ensuring the effective compatibility of the electric vehicle controller 1.

[0041] In some embodiments, the electric vehicle controller 1 can be a chip, which also includes a motherboard. The processor 12, power control peripheral circuit 13, battery management peripheral circuit 14, and charging communication peripheral circuit 15 are all located on the motherboard. The electric vehicle controller 1 provided in this application is a cross-domain integrated controller that integrates the functions of a vehicle control unit, a battery management system, and a charging communication controller. It integrates the vehicle control unit, battery management system, and charging communication controller onto the same motherboard and shares the same processor to process the functional logic of the three controllers, forming a single chip. Compared to a scheme where the vehicle control unit, battery management system, and charging communication controller are separated into three chips, this effectively saves on the chip cost and chip casing mold cost of electric vehicles, reduces the space occupied by the vehicle control system, simplifies vehicle components and wiring harnesses, and optimizes internal vehicle wiring.

[0042] For example, if the electric vehicle controller 1 provided in this application embodiment is divided according to function for ease of understanding, it can be considered that the electric vehicle controller 1 integrates a power control unit, a battery management main control unit, and a charging communication control unit.

[0043] The power control unit includes power control peripheral circuits 13 and a processor 12, supporting functions such as power-on / off control, gear control, vehicle drive control, vehicle cruise control, energy management, vehicle thermal management, high-voltage accessory management, network management, and fault diagnosis. The battery management main control unit includes battery management peripheral circuits 14 and a processor 12, supporting functions such as battery state of X (SOX) calculation, charging time calculation, charging control, battery balancing management, thermal management within the electric vehicle battery (i.e., the vehicle battery pack), and fault diagnosis related to the electric vehicle battery. The charging communication control unit includes charging communication peripheral circuits 15 and a processor 12, supporting functions such as charging protocol identification and conversion, intelligent charging management, charging protection, and charging metering and payment settlement.

[0044] In this embodiment, the electric vehicle controller includes a processor, a power control peripheral circuit, a battery management peripheral circuit, and a charging communication peripheral circuit. The power control peripheral circuit collects and transmits first state data to the processor. The battery management peripheral circuit collects and transmits second state data to the processor. The charging communication peripheral circuit collects and transmits third state data to the processor. The processor is at least configured to execute the functional logic of the vehicle control unit based on the first state data, obtain and output power control data to the power control peripheral circuit, so that the power control peripheral circuit outputs power control data to a first external device. The processor is at least configured to execute the functional logic of the battery management system based on the second state data, obtain and output battery control data to the battery management peripheral circuit, so that the battery management peripheral circuit outputs battery control data to a second external device. The processor is also at least configured to execute the functional logic of the charging communication controller based on the third state data, obtain and output charging control data to the charging communication peripheral circuit, so that the charging communication peripheral circuit outputs charging control data to a third external device.

[0045] In this technical solution, the first state data is the data required to realize the function of the vehicle control unit. The second state data is the data required to realize the function of the battery management system. The third state data is the data required to realize the charging communication controller. The electric vehicle controller uses a processor, power control peripheral circuits, battery management peripheral circuits, and charging communication peripheral circuits to realize the functions of the vehicle control unit, battery management system, and charging communication controller. Therefore, compared with related technologies, it saves the CAN bus interconnection between the vehicle control unit, battery management system, and charging communication controller, and changes the data interaction between the vehicle control unit, battery management system, and charging communication controller based on the CAN bus to internal data calls within the devices, effectively reducing the transmission load of the CAN bus in the vehicle control system.

[0046] In some embodiments of this application, such as Figure 2 As shown, the charging communication peripheral circuit 15 includes: multiple charging communication units 151.

[0047] Multiple charging communication units 151 are used to connect to charging piles (Electric Vehicle Supply Equipment, EVSE) 2 that support different charging communication protocols. They receive and transmit third-state data output by the charging pile 2 based on the charging communication protocol to the processor 12, and output charging control data output by the processor 12 based on the charging communication protocol to the charging pile 2. Since multiple charging communication units 151 can connect to charging piles 2 that support multiple different charging communication protocols, this effectively enables electric vehicles to be compatible with various charging piles 2 based on different charging communication protocols, improving the charging compatibility and convenience of electric vehicles and ensuring charging safety.

[0048] In one optional implementation, some of the multiple charging communication units 151 are used to connect to charging piles 2 that support different charging communication protocols, thereby supporting electric vehicles charging based on different charging communication protocols. It is easy to understand that the charging communication peripheral circuit 15 can contain at least two charging communication units 151 connected to charging piles 2 that support the same charging communication protocol. In this way, the electric vehicle controller can provide backup charging piles based on the same charging communication protocol, enabling the electric vehicle controller to support battery charging at charging piles using multiple charging communication protocols while effectively avoiding the problem of electric vehicles being unable to charge in a timely manner due to malfunction of a single charging communication unit 151, thus ensuring the electric vehicle's range.

[0049] In another alternative embodiment, each of the multiple charging communication units 151 is used to connect to a charging pile 2 that supports different charging communication protocols, so as to support electric vehicles charging based on different charging communication protocols.

[0050] Optionally, the plurality of charging communication units 151 may include: a plurality of first charging communication units. Each first charging communication unit is used to connect to a charging pile 2 that supports different charging communication protocols. Furthermore, each first charging communication unit is used to connect to a charging pile 2 that supports a target charging communication protocol, so that the electric vehicle can be adapted to the charging pile 2 that supports the target charging communication protocol for charging. The target charging communication protocol is a charging protocol other than the national standard communication protocol (GB / T charging protocol).

[0051] Accordingly, the processor 12 is further configured to convert the third state data based on the charging communication protocol into first general charging data, execute the functional logic of the charging communication controller according to the first general charging data to obtain general charging control data, convert the general charging control data into first charging control data, and output it to the first charging communication unit. The first general charging data is the third state data based on the national standard communication protocol. The general charging control data is the charging control data based on the national standard communication protocol. The first charging control data is the charging control data based on the charging communication protocol.

[0052] Optionally, the plurality of charging communication units 151 may further include a second charging communication unit. The second charging communication unit is used to connect to the charging pile 2 that supports the national standard communication protocol, so that the electric vehicle can be adapted to the charging pile 2 that supports the national standard communication protocol for charging.

[0053] The processor 12 is also used to execute the functional logic of the charging communication controller based on the second general charging data output by the charging pile, obtain the second charging control data, and output the second charging control data to the second charging communication unit. The second general charging data is third state data based on the national standard communication protocol. The second charging control data is charging control data based on the national standard communication protocol.

[0054] In some embodiments, the third state data output by the charging pile 2 and the charging control data output by the processor 12 to the charging communication unit 151 refer to the charging and discharging interaction data between the charging pile and the charging communication controller during the charging and discharging process of the electric vehicle using the charging pile, including handshake, identification, parameter configuration, charging / discharging start, and charging / discharging end.

[0055] For example, such as Figure 3 As shown, the multiple first charging communication units include: a first charging communication module 1511, a second charging communication module 1512, and a third charging communication module 1513.

[0056] The first charging communication module 1511 may include a powerline carrier (PLC) communication device 15111. The powerline communication device 15111 is used to connect to a charging pile 2 that supports the CCS protocol, enabling the electric vehicle to be compatible with the CCS-compliant charging pile 2 for charging. Optionally, the powerline communication device 15111 conforms to communication protocols such as IEC 61851-24, DIN 70121, ISO 15118, and the SAE J1772 standard communication protocol.

[0057] It should be noted that the CCS protocol includes derivative charging protocols such as CCS1 and CCS2, which are used to adapt to different regions. Therefore, in some embodiments, the power line communication device 15111 can be used to connect to a charging pile 2 that supports at least one of the charging protocols CCS, CCS1, and CCS2.

[0058] The second charging communication module 1512 may include a first CAN transceiver 15121. The first CAN transceiver 15121 is used to connect to the charging pile 2 that supports the CHAdeMo protocol, so that the electric vehicle can be adapted to the charging pile 2 that supports the CHAdeMo protocol for charging. Optionally, the electric vehicle controller 1 generates third state data and charging control data based on the CHAdeMo protocol during the charging and discharging process with the charging pile 2 via the first CAN transceiver 15121. For example, the third state data based on the CHAdeMo protocol may include: charging sequence control signals (Charging sequence signal 1_PWM, Charging sequence signal 2_PWM) and charging gun engagement status detection signals (Connector Proximity detection_PWM). The charging control data may include charging permission signals (Vehicle charge permission_PWM), etc.

[0059] The third charging communication module 1513 includes a second CAN transceiver 15131. The second CAN transceiver 15131 is used to connect to the charging pile 2 that supports the Chaoji protocol, so that the electric vehicle can be adapted to the charging pile 2 that supports the Chaoji protocol for charging.

[0060] It should be noted that, Figure 3 In this designation, CCS EVSE represents a charging pile 2 supporting the CCS protocol, Chaoji EVSE represents a charging pile 2 supporting the Chaoji protocol, and CHAdeMo EVSE represents a charging pile 2 supporting the CHAdeMo protocol. Since the charging communication peripheral circuit 15 includes a power line communication device 15111, a first CAN transceiver 15121, and a second CAN transceiver 15131, electric vehicles can be adapted to charging piles based on the CCS, CHAdeMo, and Chaoji protocols for charging their batteries. This effectively enriches the types of charging piles that electric vehicles can access, improving the convenience and compatibility of electric vehicle charging.

[0061] For further examples, please refer to [link / reference]. Figure 3 ,exist Figure 3 Based on the charging communication peripheral circuit 15 shown, the number of second charging communication units in the charging communication peripheral circuit 15 can be two. The two second charging communication units include: a fourth charging communication module 1514 and a fifth charging communication module 1515.

[0062] The fourth charging communication module 1514 includes a third CAN transceiver 15141. The third CAN transceiver 15141 is used to connect to the DC charging pile 2 that supports the national standard communication protocol, so that the electric vehicle can be adapted to the DC charging pile 2 that supports the national standard communication protocol for charging.

[0063] The fifth charging communication module 1515 includes a fourth CAN transceiver 15151. The fourth CAN transceiver 15151 is used to connect to the AC charging pile 2 that supports the national standard communication protocol, so that the electric vehicle can be adapted to the AC charging pile 2 that supports the national standard communication protocol for charging. The AC charging pile 2 provides DC power supply signals. The AC charging pile 2 provides AC power supply signals.

[0064] It should be noted that, Figure 3 In this document, GB / T AC EVSE is used to represent an AC charging pile 2 that supports the national standard communication protocol, and GB / T DC EVSE is used to represent a DC charging pile 2 that supports the national standard communication protocol. Since the charging communication peripheral circuit 15 includes a third CAN transceiver 15141 and a fourth CAN transceiver 15151, electric vehicles can be adapted to both DC and AC charging piles based on the national standard communication protocol for charging their batteries. This further enriches the types of charging piles that electric vehicles can access, improving the convenience and compatibility of electric vehicle charging.

[0065] In some embodiments of this application, such as Figure 4 As shown, the electric vehicle also includes: a temperature sensor for the charging port socket, a charging current sensor, and a charging voltage sensor. The charging communication peripheral circuit 15 may also include: a charging port acquisition unit 152.

[0066] The charging port acquisition unit 152 is used to connect to the temperature sensor 6, the charging current sensor 7, and the charging voltage sensor 8. The charging port acquisition unit 152 is used to acquire target detection data from the temperature sensor 6, the charging current sensor 7, and the charging voltage sensor 8, and output third status data including the target detection data to the processor 12.

[0067] The target detection data includes at least the temperature data of the charging port detected by temperature sensor 6, the current data of the charging port detected by charging current sensor 7, and the voltage data of the charging port detected by charging voltage sensor 8. Optionally, the charging port acquisition unit 152 can be an analog-to-digital (AD) converter module. The AD converter module is used to acquire the target detection data, which are analog signals output by temperature sensor 6, charging current sensor 7, and charging voltage sensor 8, and to perform analog-to-digital conversion on the target detection data to obtain target detection data as digital signals. The AD converter module is used to output third state data to processor 12, which includes the target detection data as digital signals corresponding to temperature sensor 6, charging current sensor 7, and charging voltage sensor 8, facilitating digital processing by processor 12.

[0068] In this embodiment, the power control peripheral circuit 13 is used to collect and transmit first state data to the processor 12, and to output power control data to the first external device so that the first external device performs the vehicle power control operation corresponding to the power control data.

[0069] Optionally, such as Figure 5 As shown, the first external device includes the downstream controller 3 of the vehicle control unit. The power control peripheral circuit 13 includes: a power control communication unit 131.

[0070] The power control communication unit 131 is used for electrical connection with the downstream controller 3. The power control communication unit 131 is used to collect and transmit first status data output by the downstream controller 3 to the processor 12, and to output power control data to the downstream controller 3, so that the downstream controller 3 of the vehicle control unit executes the power control operation corresponding to the power control data.

[0071] For example, please continue to refer to Figure 5 The downstream controller 3 includes: chassis domain controller 31, vehicle high-voltage controller 32, and body controller 33. The power control communication unit 131 includes: fifth CAN transceiver 1311, sixth CAN transceiver 1312, and seventh CAN transceiver 1313.

[0072] The fifth CAN transceiver 1311 is connected to the chassis domain controller 31 via a CAN bus. The fifth CAN transceiver 1311 is used to acquire and transmit first status data output by the chassis domain controller 31 to the processor 12, and to output power control data to the chassis domain controller 31. Optionally, the chassis domain controller 31 includes: an airbag controller, an active damping controller, an electric power steering controller, a brake controller, an air suspension controller, an ADAS controller, etc.

[0073] The sixth CAN transceiver 1312 is connected to the vehicle high-voltage controller 32 via a CAN bus. The sixth CAN transceiver 1312 is used to acquire and transmit the first status data output by the vehicle high-voltage controller 32 to the processor 12, and to output power control data to the vehicle high-voltage controller 32. Optionally, the chassis domain controller 31 includes: a compressor controller, a drive motor controller, a high-voltage distribution box, a PTC, a DC-DC converter, etc.

[0074] The seventh CAN transceiver 1313 is connected to the body controller 33 via a CAN bus. The seventh CAN transceiver 1313 is used to collect and transmit the first status data output by the body controller 33 to the processor 12, and to output power control data to the body controller 33.

[0075] In some embodiments of the electric vehicle controller 1 provided in this application, the power control communication unit 131 can provide data acquisition function for the downstream controller 3 connected to the existing vehicle control unit, and send the acquired first state data to the processor 12 so that the processor 12 can execute the functional logic of the existing vehicle control unit, generate power control data, and transmit it to the downstream controller 3 connected to the existing vehicle control unit through the power control communication unit 131, thereby supporting the interaction between the electric vehicle controller 1 and the downstream controller 3 to realize the function of the vehicle control unit.

[0076] In some embodiments of this application, such as Figure 6 As shown, the power control peripheral circuit 13 may further include an Ethernet transceiver 132. The Ethernet transceiver 132 is communicatively connected to the cockpit domain controller 4 of the electric vehicle. The Ethernet transceiver 132 is used to collect and transmit first status data output by the cockpit domain controller 4 to the processor 12, and to output power control data to the cockpit domain controller 4, interacting with the cockpit domain controller 4 to achieve control of the cockpit domain controller 4. Optionally, the Ethernet transceiver 132 can be an Ethernet transceiver based on the 100BASE-T1 standard, or an Ethernet transceiver based on the 10BASE-T1S standard, etc.

[0077] In this embodiment, the battery management peripheral circuit 14 is used to collect and transmit second state data to the processor 12, and to output battery control data to the second external device so that the second external device performs the electric vehicle battery control operation corresponding to the battery control data.

[0078] Optionally, such as Figure 7 As shown, the second external device includes the slave controller 5 of the battery management system. The slave controller 5 of the battery management system is a distributed acquisition unit of the BMS, which is mainly responsible for the status monitoring and management of each individual battery cell in the battery pack of the electric vehicle battery.

[0079] The battery management peripheral circuit 14 may include a battery control communication unit 141. The battery control communication unit 141 is electrically connected to the slave controller 5. The battery control communication unit 141 is used to acquire and transmit second status data output from the slave controller 5 to the processor 12, and to output battery control data to the slave controller 5, so that the slave controller 5 of the battery management system executes the battery control data corresponding to the charging control data.

[0080] In some embodiments, the second state data collected by the battery control communication unit 141 from the slave controller 5 of the battery management system may include the current, voltage, temperature, etc. of the electric vehicle battery. The processor 12 is used to generate charging control data based on the second state data and send it to the slave controller 5 through the battery control communication unit 141, which may include voltage adjustment data, current adjustment data, etc. of the electric vehicle battery.

[0081] For example, please continue to refer to Figure 7 The battery control communication unit 141 may include an eighth CAN transceiver 1411. The eighth CAN transceiver 1411 is connected to the slave controller 5 of the battery management system via a CAN bus. The eighth CAN transceiver 1411 is used to collect and transmit second status data output by the slave controller 5 of the battery management system to the processor 12, and to output battery control data to the slave controller 5 of the battery management system. It should be noted that in some embodiments, the specific structures of the first CAN transceiver 15121 to the eighth CAN transceiver 1411 can all refer to the structures of CAN transceivers in related technologies, and this application does not limit them in this regard.

[0082] In some embodiments of the electric vehicle controller 1 provided in this application, the battery control communication unit 141 can provide a data acquisition function for the slave controller 5 connected to the existing battery management system, and send the acquired second state data to the processor 12 so that the processor 12 can execute the functional logic of the existing battery management system, generate battery control data, and transmit it to the slave controller 5 connected to the existing battery management system through the battery control communication unit 141, thereby supporting the interaction between the electric vehicle controller 1 and the slave controller 5 to realize the functions of the battery management system.

[0083] In some embodiments of this application, such as Figure 8 As shown, the electric vehicle controller 1 also includes an input processing unit 16 and an output processing unit 17.

[0084] Input processing unit 16 is connected to processor 12 and is used to receive at least one of first state data, second state data, and third state data. Output processing unit 17 is connected to processor 12 and is used to connect to at least one of first external device, second external device, and third external device. Output processing unit 17 is used to output power control data, battery control data, and charging control data.

[0085] Alternatively, please continue to refer to Figure 8 The electric vehicle also includes a first sensor and a second sensor. The first sensor is used to collect at least one of first state data, second state data, and third state data as analog signals. The second sensor is used to collect at least one of first state data, second state data, and third state data as digital signals. The input processing unit 16 may include: an analog sensor input module 161, a digital sensor input module 162, and a wake-up signal input module 163.

[0086] The analog sensor input module 161 is used to connect to the first sensor and receive data collected by the first sensor. In some embodiments, the first sensor may be a sensor that provides analog signals and is connected to an existing vehicle control unit, battery management system, or charging communication controller. Accordingly, the specific structure of the analog sensor input module 161 can refer to the specific structure of target modules supporting the same function in the vehicle control unit, battery management system, or charging communication controller in related technologies, and this application does not limit it in this regard.

[0087] For example, the first sensor may include at least one of the following: an accelerator pedal travel sensor, an atmospheric pressure detection sensor, a vacuum pump, a thermal management-related sensor, etc.

[0088] The digital sensor input module 162 is used to connect to the second sensor and receive data collected by the second sensor. In some embodiments, the second sensor can be a sensor connected to an existing vehicle control unit, battery management system, or charging communication controller for providing data signals. Accordingly, the specific structure of the digital sensor input module 162 can refer to the specific structure of target modules supporting the same function in the vehicle control unit, battery management system, or charging communication controller in related technologies, and this application does not limit it in this regard.

[0089] For example, the second sensor may include at least one of the following: gear position sensor, brake pedal sensor, wheel speed sensor, charging gun related sensor, cruise function related sensor, driving module management related sensor, etc.

[0090] The wake-up signal input module 163 is used to receive the charging wake-up signal and the ignition (IGN) wake-up signal. The charging wake-up signal is third-state data, and the ignition wake-up signal is first-state data and second-state data.

[0091] Alternatively, please continue to refer to Figure 8 The output processing unit 17 may include: a high-side and low-side switch signal output module 171, a pulse-width modulation (PWM) signal output module 172, and an H-bridge control signal output module 173.

[0092] The high / low side switch signal output module 171 is used to output high / low side switch signals from power control data, battery control data, and charging control data. The high / low side switch signals include at least one of the following: a high-voltage relay switch control signal, an emergency stop signal, a charging gun electronic lock switch control signal, an electronic controller wake-up signal, a charging indicator light operating signal, and a thermal management valve switch control signal.

[0093] The PWM signal output module 172 is used to output PWM signals from power control data, battery control data, and charging control data. The PWM signals include at least one of the following: a water pump operating signal, a fan operating signal, a high-voltage interlock signal, and a collision test control signal.

[0094] The H-bridge control signal output module 173 is used to output H-bridge control signals from power control data, battery control data, and charging control data. The H-bridge control signals include at least one of the following: a damper fan operating signal, a wheel-end disconnect motor operating signal, and a parking motor operating signal.

[0095] In some embodiments, the specific structures of the high-side switch signal output module 171, the PWM signal output module 172, and the H-bridge control signal output module 173 can all refer to the specific structures of target modules supporting the same functions in vehicle control units, battery management systems, or charging communication controllers in related technologies, and this application does not limit them in this regard.

[0096] In some embodiments of this application, such as Figure 9 As shown, the electric vehicle controller 1 also includes a system base chip (SBC) 18. The system base chip is the power management hub of the automotive electronic system. Its main functions include: integrated multiplex voltage conversion, watchdog timer, and high-side drive capability.

[0097] The system base chip 18 is electrically connected to the electric vehicle battery 9, processor 12, power control peripheral circuit 13, battery management peripheral circuit 14, and charging communication peripheral circuit 15. The system base chip 18 supplies power to the processor 12, power control peripheral circuit 13, battery management peripheral circuit 14, and charging communication peripheral circuit 15. In some embodiments, the specific structure of the SBC 18 can refer to the specific structure of target modules supporting the same functions in vehicle control units, battery management systems, or charging communication controllers in related technologies; this application does not limit this aspect.

[0098] Alternatively, please continue to refer to Figure 9 The electric vehicle controller 1 further includes a local interconnect network transceiver 19. The local interconnect network transceiver 19 is electrically connected to the processor 12 and to the electric vehicle battery 9 via a load short-circuit switch chip 10. The local interconnect network transceiver 19, under the control of the processor 12, outputs a battery control signal to the load short-circuit switch chip 10. The battery control signal is used by the load short-circuit switch chip 10 to control the electric vehicle battery 9 to supply power to the system base chip 18, or to stop supplying power to the system base chip 18. In some embodiments, the specific structure of the local interconnect network transceiver 19 may refer to the specific structure of target modules supporting the same function in vehicle control units, battery management systems, or charging communication controllers in related technologies; this application does not limit this aspect.

[0099] In some embodiments, the electric vehicle controller 1 can also be connected to a body slave node (LIN BodySlave, LBS) via a LIN bus. The LBS can be a door lock module, interior lighting module, etc., used to control the state of the body slave node. LIN bus stands for Local Interconnect Network, which is a bus for transmitting data based on a low-cost, low-speed in-vehicle serial communication protocol.

[0100] For example, as mentioned above, the electric vehicle controller 1 provided in this application embodiment can be considered to integrate a power control unit, a battery management main control unit, and a charging communication control unit, based on its function. Please refer to... Figure 10 It shows a functional diagram of each control unit provided in the embodiments of this application at the application layer.

[0101] like Figure 10 As shown, the power control unit supports the functions of the vehicle control unit, including power-on / off control, gear control, vehicle drive control, vehicle cruise control, energy management, vehicle thermal management, high-voltage accessory management, network management, and fault diagnosis.

[0102] The system includes the following functions: Power-on / off control function, which controls at least the low-voltage and high-voltage power-on / off of the entire vehicle; Gear shift control function, which controls at least the P, N, R, and D gear shifting functions and the gear position display on the instrument panel; Vehicle drive control function, which controls at least accelerator pedal response, brake pedal response, torque management, vehicle mode management, and energy recovery management; Cruise control function, which controls at least the cruise speed; Energy management function, which controls at least the operation of the vehicle's high-voltage and low-voltage accessories; Network management function, which controls at least the sleep / wake-up and network communication functions of the vehicle control unit; and Fault diagnosis function, which covers the diagnosis of the safe operation of all vehicle components except the electric vehicle battery.

[0103] The battery management main control unit supports functions of the battery management system, such as SOX calculation, charge and discharge management, cell balancing management, thermal management within the electric vehicle battery, and fault diagnosis related to the electric vehicle battery.

[0104] The charging communication control unit supports the functions of charging communication controllers, such as charging protocol identification and conversion, charging process management, charging protection, charging metering and fee settlement, and charging electronic lock drive control.

[0105] The charging protocol identification and conversion function supports identifying the charging communication protocols supported by the charging station after the electric vehicle is connected to the charging station. If the charging battery supports the CHAdeMO protocol, it converts CHAdeMO-based data (third-state data / charging control data) to data based on the national standard communication protocol, and vice versa. Similarly, if the charging battery supports the CCS protocol, it converts CCS-based data (third-state data / charging control data) to data based on the national standard communication protocol, and vice versa.

[0106] The charging process management function is used to exchange information with the charging pile and the power grid through the charging communication control unit, so as to monitor the charging process in real time and accurately control the charging parameters to ensure the charging safety and efficiency of the electric vehicle battery. The charging process management function is used at least to establish a connection between the electric vehicle and the charging pile, negotiate charging parameters, dynamically adjust charging, and handle the end of charging.

[0107] The system comprises the following components: Establishing a connection between the electric vehicle (EV) and the charging station: This involves establishing a handshake communication between the EV controller and the charging station to confirm their respective statuses and prepare for subsequent charging. Negotiating charging parameters: This allows the EV controller and the charging station to jointly negotiate charging parameters, ensuring the charging process meets the needs of both parties. Dynamic charging adjustment: During the charging process, the system dynamically controls and adjusts the output current and voltage of the charging station based on the actual conditions of both the EV and the charging station, improving charging efficiency and safety. Charging completion processing: This notifies the charging station to stop charging and records relevant information for billing and management. Charging protection: This implements at least multiple protection functions such as overcurrent protection, overvoltage protection, and temperature protection to handle abnormal charging situations and ensure the safety of the charging process. Charging metering and billing: This records the amount of electricity charged and calculates billing information based on the amount charged, enabling EV users and charging station operators to manage charging.

[0108] In this embodiment, the electric vehicle controller includes a processor, a power control peripheral circuit, a battery management peripheral circuit, and a charging communication peripheral circuit. The power control peripheral circuit collects and transmits first state data to the processor. The battery management peripheral circuit collects and transmits second state data to the processor. The charging communication peripheral circuit collects and transmits third state data to the processor. The processor is at least configured to execute the functional logic of the vehicle control unit based on the first state data, obtain and output power control data to the power control peripheral circuit, so that the power control peripheral circuit outputs power control data to a first external device. The processor is at least configured to execute the functional logic of the battery management system based on the second state data, obtain and output battery control data to the battery management peripheral circuit, so that the battery management peripheral circuit outputs battery control data to a second external device. The processor is also at least configured to execute the functional logic of the charging communication controller based on the third state data, obtain and output charging control data to the charging communication peripheral circuit, so that the charging communication peripheral circuit outputs charging control data to a third external device.

[0109] In this technical solution, the first state data is the data required to realize the function of the vehicle control unit. The second state data is the data required to realize the function of the battery management system. The third state data is the data required to realize the charging communication controller. The electric vehicle controller uses a processor, power control peripheral circuits, battery management peripheral circuits, and charging communication peripheral circuits to realize the functions of the vehicle control unit, battery management system, and charging communication controller. Therefore, compared with related technologies, it saves the CAN bus interconnection between the vehicle control unit, battery management system, and charging communication controller, and changes the data interaction between the vehicle control unit, battery management system, and charging communication controller based on the CAN bus to internal data calls within the devices, effectively reducing the transmission load of the CAN bus in the vehicle control system.

[0110] This application also provides an electric vehicle. The electric vehicle includes the electric vehicle controller provided in this application embodiment. In the electric vehicle provided in this application embodiment, the electric vehicle controller includes: a processor, a power control peripheral circuit, a battery management peripheral circuit, and a charging communication peripheral circuit. The power control peripheral circuit is used to collect and transmit first state data to the processor. The battery management peripheral circuit is used to collect and transmit second state data to the processor. The charging communication peripheral circuit is used to collect and transmit third state data to the processor. The processor is at least used to execute the functional logic of the vehicle control unit based on the first state data, obtain and output power control data to the power control peripheral circuit, so that the power control peripheral circuit outputs power control data to a first external device. The processor is at least used to execute the functional logic of the battery management system based on the second state data, obtain and output battery control data to the battery management peripheral circuit, so that the battery management peripheral circuit outputs battery control data to a second external device. The processor is also at least used to execute the functional logic of the charging communication controller based on the third state data, obtain and output charging control data to the charging communication peripheral circuit, so that the charging communication peripheral circuit outputs charging control data to a third external device.

[0111] In this technical solution, the first state data is the data required to realize the function of the vehicle control unit. The second state data is the data required to realize the function of the battery management system. The third state data is the data required to realize the charging communication controller. The electric vehicle controller uses a processor, power control peripheral circuits, battery management peripheral circuits, and charging communication peripheral circuits to realize the functions of the vehicle control unit, battery management system, and charging communication controller. Therefore, compared with related technologies, it saves the CAN bus interconnection between the vehicle control unit, battery management system, and charging communication controller, and changes the data interaction between the vehicle control unit, battery management system, and charging communication controller based on the CAN bus to internal data calls within the devices, effectively reducing the transmission load of the CAN bus in the vehicle control system.

[0112] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0113] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. For embodiments of devices, electronic devices, computer-readable storage media, and computer program products containing instructions, the descriptions are relatively simple because they are basically similar to the method embodiments; relevant parts can be referred to the descriptions of the method embodiments.

[0114] The above description is merely a preferred embodiment of this utility model and is not intended to limit the scope of protection of this utility model. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this utility model are included within the scope of protection of this utility model.

Claims

1. An electric vehicle controller, characterized in that, The electric vehicle controller (1) is applied to an electric vehicle including a first external device, a second external device and a third external device. The electric vehicle controller (1) includes: a processor (12), a power control peripheral circuit (13), a battery management peripheral circuit (14) and a charging communication peripheral circuit (15). The power control peripheral circuit (13) is connected to the processor (12) and is used to collect and transmit first state data to the processor (12). The first state data is the data required to realize the function of the vehicle control unit. The battery management peripheral circuit (14) is connected to the processor (12) and is used to collect and transmit second state data to the processor (12). The second state data is the data required to realize the functions of the battery management system. The charging communication peripheral circuit (15) is connected to the processor (12) and is used to collect and transmit third state data to the processor (12). The third state data is the data required to realize the charging communication controller. The processor (12) is at least used to execute the functional logic of the vehicle control unit according to the first state data, obtain and output power control data to the power control peripheral circuit (13), execute the functional logic of the battery management system according to the second state data, obtain and output battery control data to the battery management peripheral circuit (14), and execute the functional logic of the charging communication controller according to the third state data, obtain and output charging control data to the charging communication peripheral circuit (15). The power control peripheral circuit (13) is used to connect to the first external device and output the power control data to the first external device; The battery management peripheral circuit (14) is used to connect to the second external device and output the battery control data to the second external device; The charging communication peripheral circuit (15) is used to connect to the third external device and output the charging control data to the third external device.

2. The electric vehicle controller according to claim 1, characterized in that, The charging communication peripheral circuit (15) includes: multiple charging communication units (151); The plurality of charging communication units (151) are used to connect to charging piles (2) that support different charging communication protocols, receive and transmit the third state data output by the charging pile (2) based on the charging communication protocol to the processor (12), and output the charging control data output by the processor (12) based on the charging communication protocol to the charging pile (2).

3. The electric vehicle controller according to claim 2, characterized in that, The plurality of charging communication units (151) includes: a plurality of first charging communication units; each of the first charging communication units is used to connect to a charging pile (2) that supports different charging communication protocols; The processor (12) is further configured to convert the third state data based on the charging communication protocol into first general charging data, execute the functional logic of the charging communication controller according to the first general charging data to obtain general charging control data, convert the general charging control data into first charging control data, and output it to the first charging communication unit. The first general charging data is the third state data based on the national standard communication protocol, the general charging control data is the charging control data based on the national standard communication protocol, and the first charging control data is the charging control data based on the charging communication protocol.

4. The electric vehicle controller according to claim 3, characterized in that, The plurality of first charging communication units include: a first charging communication module (1511), a second charging communication module (1512), and a third charging communication module (1513). The first charging communication module (1511) includes a power line communication device (15111), which is used to connect to a charging pile that supports the CCS protocol. The second charging communication module (1512) includes a first CAN transceiver (15121), which is used to connect to a charging pile that supports the CHAdeMo protocol. The third charging communication module (1513) includes a second CAN transceiver (15131), which is used to connect to a charging pile that supports the Chaoji protocol.

5. The electric vehicle controller according to claim 2, characterized in that, The plurality of charging communication units (151) further includes: a second charging communication unit; the second charging communication unit is used to connect to a charging pile (2) that supports the national standard communication protocol; The processor (12) is further configured to execute the functional logic of the charging communication controller based on the second general charging data output by the charging pile, obtain the second charging control data, and output the second charging control data to the second charging communication unit. The second general charging data is the third state data based on the national standard communication protocol, and the second charging control data is the charging control data based on the national standard communication protocol.

6. The electric vehicle controller according to claim 5, characterized in that, The number of the second charging communication units is two; the two second charging communication units include: a fourth charging communication module (1514) and a fifth charging communication module (1515). The fourth charging communication module (1514) includes a third CAN transceiver, which is used to connect to a DC charging pile (2) that supports the national standard communication protocol. The fifth charging communication module (1515) includes a fourth CAN transceiver, which is used to connect to an AC charging pile (2) that supports the national standard communication protocol.

7. The electric vehicle controller according to any one of claims 1 to 6, characterized in that, The electric vehicle also includes: a temperature sensor for the charging port, a charging current sensor, and a charging voltage sensor; the charging communication peripheral circuit (15) also includes: a charging port acquisition unit (152). The charging port acquisition unit (152) is used to connect to the temperature sensor, the charging current sensor and the charging voltage sensor, acquire the target detection data of the temperature sensor, the charging current sensor and the charging voltage sensor, and output third state data including the target detection data to the processor.

8. The electric vehicle controller according to any one of claims 1 to 6, characterized in that, The first external device includes the downstream controller (3) of the vehicle control unit; the power control peripheral circuit (13) includes: a power control communication unit (131). The power control communication unit (131) is used to electrically connect with the downstream controller (3), collect and transmit the first status data output by the downstream controller (3) to the processor (12), and output the power control data to the downstream controller (3).

9. The electric vehicle controller according to any one of claims 1 to 6, characterized in that, The second external device includes the slave controller (5) of the battery management system; the battery management peripheral circuit (14) includes: a battery control communication unit (141); The battery control communication unit (141) is used to be electrically connected to the slave controller (5), collect and transmit the second status data output by the slave controller (5) to the processor (12), and output the battery control data to the slave controller (5).

10. The electric vehicle controller according to any one of claims 1 to 6, characterized in that, The electric vehicle controller (1) further includes an input processing unit (16) and an output processing unit (17). The input processing unit (16) is connected to the processor (12) and is used to receive at least one of the first state data, the second state data, and the third state data; The output processing unit (17) is connected to the processor (12) and is used to connect to at least one of the first external device, the second external device and the third external device, for outputting at least one of the power control data, the battery control data and the charging control data.

11. The electric vehicle controller according to claim 10, characterized in that, The electric vehicle further includes a first sensor and a second sensor. The first sensor is used to collect at least one of the first state data, the second state data and the third state data as analog signals. The second sensor is used to collect at least one of the first state data, the second state data and the third state data as digital signals. The input processing unit (16) includes: an analog sensor input module (161), a digital sensor input module (162) and a wake-up signal input module (163). The analog sensor input module (161) is used to connect to the first sensor and receive data collected by the first sensor; The digital sensor input module (162) is used to connect to the second sensor and receive data collected by the second sensor; The wake-up signal input module (163) is used to receive a charging wake-up signal and an ignition wake-up signal. The charging wake-up signal is the third state data, and the ignition wake-up signal is the first state data and the second state data.

12. The electric vehicle controller according to claim 11, characterized in that, The output processing unit (17) includes: a high-low side switch signal output module (171), a pulse width modulation (PWM) signal output module (172), and an H-bridge control signal output module (173). The high and low side switch signal output module (171) is used to output the high and low side switch signals in the power control data, the battery control data, and the charging control data. The high and low side switch signals include at least one of the following: the switch control signal of the high voltage relay, the emergency stop signal, the switch control signal of the charging gun electronic lock, the wake-up signal of the electronic controller, the working signal of the charging indicator light, and the switch control signal of the thermal management valve. The PWM signal output module (172) is used to output the PWM signal in the power control data, the battery control data, and the charging control data. The PWM signal includes at least one of the following: water pump working signal, fan working signal, high voltage interlock signal, and collision test control signal. The H-bridge control signal output module (173) is used to output the power control data, the battery control data, and the H-bridge control signal in the charging control data. The H-bridge control signal includes at least one of the following: the working signal of the damper fan, the working signal of the wheel-end disconnect motor, and the working signal of the parking motor.

13. An electric vehicle, characterized in that, Includes an electric vehicle controller as described in any one of claims 1 to 12.

Images