Power domain controller system for new energy engineering machinery and control method thereof

Abstract

The embodiment of the invention provides a power domain controller system for new energy engineering machinery and a control method thereof, and relates to the technical field of engineering machinery. The system comprises a multi-core main control chip, and function subsets obtained by dividing function components of function units in a power domain according to a function unit dimension and a function safety dimension are deployed on different cores in the multi-core main control chip; the storage resource is divided into a plurality of storage partitions, and the plurality of storage partitions at least comprise a shared storage partition which is used for sharing data by different cores in the multi-core main control chip; the software system is used for providing an application program running environment based on the multi-core main control chip and the storage resources; and the input and output interface is used for carrying out data interaction with external equipment of the system. According to the implementation mode provided by the invention, more efficient and more accurate control can be implemented, and most new energy engineering machinery application requirements are met.

Description

Technical Field

[0001] This application relates to the field of engineering machinery technology, specifically to a power domain controller system for new energy engineering machinery and a control method for the power domain controller system for new energy engineering machinery. Background Technology

[0002] As vehicle electronic and electrical architectures evolve from distributed to centralized, domain controllers have become a core technological path for achieving functional integration, enhancing computing power, and reducing system complexity and cost. Domain controllers typically employ high-performance multi-core system-on-a-chip (SoC) and integrate previously dispersed electronic control units (ECUs) through communication backbones such as high-speed Ethernet, forming a control domain with stronger computing power and higher integration. This effectively addresses the limitations of traditional distributed architectures in terms of cost, communication bandwidth, computing power allocation, and scalability.

[0003] Currently, mainstream chip suppliers such as Infineon, NXP, and Renesas have launched multiple high-performance domain controller chips and proposed centralized control solutions for the powertrain domain. Some solutions have completed prototype vehicle verification, and the chip platforms are maturing. In the passenger vehicle sector, controllers for the intelligent cockpit domain, autonomous driving domain, and body domain have achieved mass production and their market penetration continues to increase. At the powertrain domain level, the industry is actively promoting deep integration solutions. For example, BYD's next-generation platform based on Renesas' RH850 series chips plans to integrate the vehicle controller (VCU), dual motor controller (MCU), battery management system (BMS), on-board charger (OBC), and DC-DC converter (DCDC) into a single main control chip. Huawei is also developing a "ten-in-one" domain controller fusion solution based on its self-developed chips, aiming to significantly reduce the number of bills of materials (BOM), chip usage, and improve development efficiency.

[0004] However, existing power domain controller solutions are mainly designed for passenger vehicle applications, focusing on the integration of functions such as vehicle control, thermal management, battery management, and power distribution units. Examples include the power domain controller system disclosed in patent document CN202510834425.0, or the electric vehicle power domain control system integrating single motor control proposed in CN201910947719.9. Although dual-motor drive technology has made progress in transmission coupling, there are currently no power domain controller products specifically designed for the new energy needs of construction machinery, compatible with dual-motor cooperative drive, and possessing rich peripheral interfaces to adapt to complex working conditions.

[0005] In the field of construction machinery, traditional non-integrated power control systems often adopt a distributed architecture, in which the VCU and multiple motor controllers (such as MCU1, MCU2) typically interact via a CAN bus. Since the CAN communication cycle is usually on the order of 10ms, while the rate of change of signals such as current and voltage in the drive system is much faster than this communication delay, the VCU cannot acquire and respond to rapid energy feedback information in real time. This results in problems such as lag in power response, insufficient energy management accuracy, and decreased system efficiency, making it difficult to meet the stringent requirements of construction machinery for high dynamic performance and efficient energy management.

[0006] Therefore, there is an urgent need to develop a highly integrated power domain controller for engineering machinery that supports dual-motor drive, has high real-time performance and rich interfaces, in order to fill the technological gap in this field and improve the overall control performance and energy efficiency of the machine. Summary of the Invention

[0007] The purpose of this application is to provide a power domain controller system and control method for new energy engineering machinery. By referencing the AUTOSAR software architecture, functional safety development concept and modular software and hardware development, the application software, underlying hardware and operating system are "decoupled", ensuring strong reusability of application software in subsequent iterations, so as to at least solve some of the problems in the background technology.

[0008] To achieve the above objectives, this application provides a power domain controller system for new energy engineering machinery. The system includes: a multi-core main control chip, wherein functional components of functional units in the power domain are deployed on different cores of the multi-core main control chip, and functional subsets are obtained by dividing them according to the functional unit dimension and the functional safety dimension; storage resources, which are divided into multiple storage partitions, including at least one shared storage partition for sharing data among different cores of the multi-core main control chip; a software system for providing an application runtime environment based on the multi-core main control chip and storage resources; and input / output interfaces for data interaction with external devices of the system.

[0009] Optionally, the functional units in the power domain include: a vehicle controller, a transmission controller, and multiple motor controllers.

[0010] Optionally, the functional components of the functional units in the power domain are deployed on different cores of the multi-core main control chip, which are divided into functional subsets according to the functional unit dimension and the functional safety dimension. These subsets include: a vehicle controller and a transmission controller are deployed on the first core of the multi-core main control chip; a functional subset of the transmission controller and multiple motor controllers with functional safety requirements are deployed on the second core of the multi-core main control chip; and functional subsets of different motor controllers with non-functional safety requirements are deployed on the remaining cores of the multi-core main control chip.

[0011] Optionally, the multi-core main control chip includes at least one lockstep core; a subset of functions with functional safety requirements is deployed to the lockstep core.

[0012] Optionally, each of the multiple storage partitions other than the shared storage partition is configured to have access only to one corresponding core or one lockstep core in the multi-core controller chip.

[0013] Optionally, the functional safety requirements and non-functional safety requirements data accessible by the same core in the multi-core main control chip are stored in different storage partitions.

[0014] Optionally, the software system includes: a real-time runtime environment layer, a basic software layer running below the real-time runtime environment layer, and an application layer running above the real-time runtime environment layer.

[0015] Optionally, the basic software layer includes: a system service layer for providing necessary system support and services for upper-layer applications; an ECU abstraction layer for encapsulating hardware interface services to decouple software and hardware; a microcontroller abstraction layer for encapsulating drivers for internal peripherals of the chip; and a complex device driver layer for providing hardware drivers for complex or special requirements.

[0016] Optionally, the application layer includes: a project adaptation layer for carrying differentiated code and data across different projects; a functional layer for carrying code and data that do not change with specific projects and hardware differences; a hardware adaptation layer for carrying code and data that change with hardware differences; an interface layer for carrying data interaction between the application layer and the real-time runtime environment layer and the basic software layer, as well as cross-core or software partition data interaction; and a data center layer for carrying data interaction between modules within the application layer, thereby decoupling the modules.

[0017] Optionally, the input / output interface includes: multiple power supply outputs, multiple analog inputs, multiple frequency signal inputs, multiple high-side inputs, multiple low-side outputs, multiple analog outputs, multiple PWM outputs, and multiple high-speed signal buses.

[0018] Optionally, the system further includes: for functions with high security impact levels, designing redundancy measures in the hardware design, software development, and / or program operation during the execution of the function.

[0019] This application also provides a control method for a power domain controller system for new energy construction machinery, employing the aforementioned power domain controller system for new energy construction machinery. The method includes: acquiring a control task; determining the functional units participating in the control based on the control task, and collecting corresponding parameters through input / output interfaces; the functional units participating in the control interact with data through a shared storage partition, and generating control instructions corresponding to the control task through preset logic and the collected parameters.

[0020] This application also provides an electronic device, including: at least one processor; and a memory connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor implements the aforementioned control method for a power domain controller system for new energy engineering machinery by executing the instructions stored in the memory.

[0021] This application also provides a machine-readable storage medium storing instructions that, when executed by a processor, configure the processor to perform the aforementioned control method for a power domain controller system for new energy engineering machinery.

[0022] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned control method for a power domain controller system for new energy engineering machinery.

[0023] The above technical solution has the following beneficial effects: (1) The different cores of the multi-core processor are used for division of labor and data is shared through shared memory, which can achieve microsecond-level access. Compared with the traditional non-power domain controller where VCU and MCU1 and MCU2 exchange data through CAN communication, the decision-making speed and response speed are significantly improved.

[0024] (2) It provides the first power domain control platform for new energy construction machinery, which can simultaneously meet the application requirements of two motor controllers, generator controllers and drive motor controllers, solve the pain point that the same type of controller only controls one motor, and simultaneously meet the VCU / TCU control requirements, covering most of the application requirements of new energy construction machinery.

[0025] Other features and advantages of the embodiments of this application will be described in detail in the following detailed description section. Attached Figure Description

[0026] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings: Figure 1 This illustration schematically shows a structural diagram of a power domain controller system for new energy engineering machinery according to an embodiment of this application; Figure 2 The diagram illustrates the division of the dedicated power domain for construction machinery according to the functional unit dimension and the functional safety dimension in the embodiments of this application. Figure 3 The diagram illustrates the correspondence between the core and functional subsets according to the embodiments of this application; Figure 4 This illustration schematically shows an architecture diagram of a software system according to an embodiment of this application; Figure 5 This illustration schematically shows the interaction between a power domain controller system for new energy engineering machinery and external devices according to an embodiment of this application; Figure 6 The diagram schematically illustrates the internal structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0027] The specific embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for illustration and explanation only and are not intended to limit the embodiments of this application.

[0028] Figure 1 A schematic diagram illustrates the structure of a power domain controller system for new energy engineering machinery according to an embodiment of this application. For example... Figure 1 As shown, a power domain controller system for new energy engineering machinery includes: A multi-core main control chip, wherein functional components of functional units in the power domain are deployed on different cores of the multi-core main control chip, and functional subsets are divided according to the functional unit dimension and the functional safety dimension. The storage resources are divided into multiple storage partitions, and at least one of the multiple storage partitions includes a shared storage partition for sharing data among different cores in the multi-core main control chip. The software system provides an application runtime environment based on the multi-core main control chip and storage resources; and input / output interfaces are used for data interaction with external devices.

[0029] In this embodiment, the set obtained according to the functional unit dimension and the functional safety dimension includes: constructing a whole set by combining all functional components of all functional units in the dynamic domain according to all possible combinations of functional units and functional safety, and then partitioning this whole set to obtain functional subsets. This partitioning includes dividing into mutually disjoint subsets.

[0030] For example, in one embodiment, the functional units in the power domain include: a vehicle controller (VCU), a transmission controller (TCU), and multiple motor controllers. The multiple motor controllers may include: a first motor controller (MCU1) for controlling the drive motor, and a second motor controller (MCU2) for controlling the operating motor. In this scenario, the functional components in the power domain are categorized by functional unit dimension as the vehicle controller (VCU), the transmission controller (TCU), and the motor controllers (MCU1 and MCU2), and by functional safety dimension as non-safety functions and safety functions. Figure 2 This illustration schematically shows the division of the dedicated power domain for engineering machinery according to the functional unit dimension and the functional safety dimension in the embodiments of this application. For example... Figure 2 As shown, based on the above two dimensions, the functional components in the power domain are divided into VCU non-safe functions, VCU safe functions, TCU non-safe functions, TCU safe functions, MCU1 non-safe functions, MCU1 safe functions, MCU2 non-safe functions, and MCU1 safe functions, thus forming an overall set. Then, the overall set is divided into several functional subsets, the number of which corresponds to the number of cores in the multi-core main control chip. These functional subsets are then deployed to the corresponding cores of the multi-core main control chip.

[0031] The number of functional subsets corresponds to the number of cores in a multi-core controller chip. This includes removing cores with specific uses, such as lockstep cores, and using the remaining cores as the number of functional subsets. For example, a multi-core controller chip has 6 cores, each with a binary index from 0 to 5. The first core (0) and the second core (1) each have one lockstep core, therefore their functional subsets in the system should be 4. An example of this division is shown below.

[0032] In this embodiment, functional components of the power domain functional units are deployed on different cores of the multi-core main control chip, which are functional subsets divided according to the functional unit dimension and the functional safety dimension. These include: deploying a vehicle controller and a transmission controller on the first core of the multi-core main control chip; deploying a functional subset of the transmission controller and multiple motor controllers with functional safety requirements on the second core of the multi-core main control chip; and deploying functional subsets of different motor controllers with non-functional safety requirements on the remaining cores of the multi-core main control chip. Figure 3 A schematic diagram illustrating the correspondence between core components and functional subsets according to an embodiment of this application is provided. For example... Figure 3As shown, core 0 is allocated to the VCU and TCU, and further divided into functional safety components and non-functional safety components; core 1 serves as the main functional safety core, deploying the functional safety monitoring modules of MCU1, MCU2, and TCU. Core 2 and core 3 deploy the non-functional safety related functional modules of MCU1. A shared data interface is set up for all three cores to access, and calibration data, cross-core transmission interfaces, and reentrant user library functions are deployed.

[0033] By employing different cores of a multi-core processor for task allocation and sharing data via shared memory, microsecond-level access can be achieved. This significantly improves decision-making and response speed compared to the traditional non-power domain controllers where the VCU and MCU1 / MCU2 exchange data via CAN communication. Furthermore, compared to the 10ms-level latency caused by CAN communication between the VCU and MCU in traditional distributed architectures, the inter-core communication latency in this solution can be reduced to the microsecond level.

[0034] In some embodiments of this application, the multi-core main control chip includes at least one lockstep core; a subset of functions with functional safety requirements is deployed to the lockstep core. Again, taking the aforementioned scenario as an example, the first core 0 and the second core 1 each have one lockstep core. The lockstep core and its corresponding core synchronously execute the same instruction stream, and compare their results to achieve error detection and correction. If inconsistent results are found, the system can take corresponding measures, such as re-executing instructions or switching to a backup core, to ensure stable system operation. This achieves a balance between control accuracy, response speed, and system safety. In some optional embodiments, a subset of core power control functions with high functional safety requirements, such as those requiring ASIL-C or ASIL-D levels, is deployed to run on the lockstep core. In some embodiments of this application, the storage resources are divided into multiple storage partitions, as shown in the following example. The storage resources are divided into the following six partitions: Partition VF, Partition VQ, Partition FS, Partition M1, Partition M2, and Partition Public. Partition VF is accessible only to Core 0 and deploys common functions such as CAN communication parsing, diagnostics, packaging, NVM storage, system basic chip management, and the functional safety module of the VCU. Partition VQ is accessible only to Core 0 and deploys QM-level functional modules for the VCU and TCU. Partition FS is accessible only to Core 1 and deploys functional safety monitoring modules for MCU1, MCU2, and TCU. Partition M1 is accessible only to Core 2 and deploys QM-level functional modules for MCU1. Partition M2 is accessible only to Core 3 and deploys QM-level functional modules for MCU2. Partition Public is accessible to all three cores and deploys calibration data, cross-core transmission interfaces, reentrant user library functions, etc.

[0035] As can be seen from the above division and access relationship configuration: VCU / MCU / TCU are memory isolated, and information exchange is carried out through shared memory; each of the multiple storage partitions other than the shared storage partition is configured to have access relationship only with one corresponding core or one lockstep core in the multi-core main control chip. Furthermore, the functional safety requirements and non-functional safety requirements data accessible by the same core in the multi-core main control chip are stored in different storage partitions. Through this innovative software deployment scheme, the functional safety and non-functional safety parts of each control unit are distinguished. Functions with high functional safety levels are deployed to the chip core with a lockstep core to achieve a higher level of functional safety; at the same time, the data of each control unit is divided into data that can only be accessed by its own core and shared memory data (which can be accessed by each other), making data interaction more secure and data flow clearer.

[0036] In some embodiments of this application, the software design of the system is based on the AUTOSAR architecture, and the detailed software solution is as follows. Figure 4 A schematic diagram illustrating the architecture of a software system according to an embodiment of this application is shown. For example... Figure 4As shown, the software system includes: a real-time runtime environment layer, a basic software layer running below the real-time runtime environment layer, and an application layer running above the real-time runtime environment layer. Each control unit's function is divided into two parts: basic function (QM, non-functional safety) and functional safety (FS). Based on the resource requirements of the dual MCUs, VCU, and TCU, power supply circuits, CAN communication, and system basic chips are shared. Data FLASH is used to simulate EEPROM, reducing board size and improving utilization.

[0037] In some embodiments of this application, the basic software layer includes: a system service layer for providing necessary system support and services for upper-layer applications; an ECU abstraction layer for encapsulating hardware interface services to decouple software and hardware; a microcontroller abstraction layer for encapsulating drivers for internal peripherals of the chip; and a complex device driver layer for providing hardware drivers for complex or special requirements.

[0038] Furthermore, the application layer includes: a project adaptation layer for carrying differentiated code and data across different projects; a functional layer for carrying code and data that do not change with specific projects and hardware differences; a hardware adaptation layer for carrying code and data that change with hardware differences; an interface layer for carrying data interaction between the application layer and the real-time runtime environment layer and the basic software layer, as well as cross-core or software partition data interaction; and a data center layer for carrying data interaction between modules within the application layer, thereby decoupling the modules.

[0039] In some embodiments of this application, the input / output interface includes: 8 channels of 5V power supply for external sensors and 4 channels of 12V power supply output; 60 sets of analog inputs (voltage type, resistance type, and current type); 32 analog inputs; 15 frequency signal inputs; 16 high-side inputs and 6 low-side outputs; 5 analog outputs and 40 PWM outputs; and 6 high-speed CAN channels, providing abundant control resources. This system features rich analog, digital, and frequency input detection and output control, overcoming the shortcomings of other similar controllers with limited or insufficient resources.

[0040] In some embodiments of this application, the system further includes: for functions with high safety impact levels, redundancy measures are designed in the hardware design, software development, and / or program operation during the execution of the function. Specifically, based on ISO26262 functional safety requirements and considering cost and implementation methods, functions with high safety impact levels are selected, and comprehensive consideration is given from the perspectives of hardware design and software development to ensure safety performance. For example, hardware design measures include: dual-circuit sampling verification of key signals such as bus voltage sampling and phase current sampling; CPU: built-in fault detection module, voltage / clock monitoring; PMIC: selected with ERROR monitoring, voltage output monitoring, and reset / fault status entry signal output pins; MCU: current / voltage dual sampling; VCU: throttle / brake / gear / key signals, etc., dual sampling; TCU: shift motor drive current and voltage signals, dual sampling. Software development measures include: using two different calculation methods to verify and monitor key signals, for example: VCU: comprehensive judgment and verification of torque requests and brake / throttle signals in CAN messages; MCU: real-time torque is monitored for safety using two different estimation methods: flux linkage estimation + phase voltage and current estimation. The program operation measures include: all VCU / TCU functions and MCU monitoring functions run on the lockstep core (2-cycle staggered operation); and hardware redundancy is used to detect permanent and temporary faults in the TriCore CPU.

[0041] The above implementation provides the first power domain control platform for new energy construction machinery, which can simultaneously meet the application requirements of two motor controllers, a generator controller and a drive motor controller, solve the pain point that the same type of controller can only control one motor, and simultaneously meet the VCU / TCU control requirements, covering most of the application requirements of new energy construction machinery.

[0042] Based on the same inventive concept, this application also provides a control method for a power domain controller system for new energy engineering machinery. Using the aforementioned power domain controller system for new energy engineering machinery, the method includes: acquiring a control task; determining the functional units participating in the control based on the control task, and collecting corresponding parameters through input / output interfaces; the functional units participating in the control interact with data through a shared storage partition, and generate control instructions corresponding to the control task through preset logic and the collected parameters. Figure 5 This illustration schematically depicts the interaction between a power domain controller system for new energy engineering machinery and external devices according to an embodiment of this application. For example... Figure 5 As shown, the power domain controller system for new energy engineering machinery realizes its corresponding functions through interaction with external devices.

[0043] Taking VCU management as an example, the VCU receives signals from external components such as the accelerator, pedal, ABS, and engine, and combines them with real-time information from internal MCU1, MCU2, and TCU to perform calculations on vehicle torque, braking control distribution, and energy management, and sends the corresponding control commands to each component for execution.

[0044] Specifically, for energy management and torque vector control: The VCU accesses real-time current, torque, and power information from MCU1 (generator controller) via shared memory in microseconds. Combined with external signals such as throttle and brake, it performs rapid demand and real-time feedback power balance calculations and sends the target torque command to MCU1 (generator controller) and MCU2 (drive motor controller). When the driver's torque demand increases and the throttle opening increases, the VCU can send the target command to the MCU2 calculation module in microseconds after calculation. Based on the real-time power feedback from MCU2, it quickly adjusts the power generation of MCU1 to achieve rapid power response and energy management for the entire vehicle.

[0045] The TCU collects motor speed data from the motor controller and acceleration signals from the VCU to select the appropriate target gear. Once a gear shift is needed, the TCU sends the required motor operating mode to the motor controller. The drive motor adjusts accordingly based on the received request information. Simultaneously, the TCU controls the shift motor to perform the corresponding shift action and provides feedback control based on the shift displacement sensor signal value.

[0046] The MCU receives control mode commands, speed commands, torque commands, and active discharge commands from the VCU. It also collects data such as bus voltage, motor phase current, motor rotor position signal, motor temperature, switching device temperature, and power supply voltage. The MCU diagnoses the health status of the motor control system and reports it to the VCU. Based on the health status of the motor control system, the MCU controls the motor control system to cut off the output or respond to the VCU's command to output torque or respond to the VCU's torque to perform active discharge.

[0047] As can be seen from the above process, the VCU accesses real-time current, torque, power, and other information from MCU1 (generator controller) in microseconds via shared memory. Combined with external signals such as throttle and brake, it performs rapid demand and real-time feedback power balance calculations and sends the target torque command to MCU1 (generator controller) and MCU2 (drive motor controller). When the driver's torque demand increases and the throttle opening increases, the VCU can send the target command to the MCU2 calculation module in microseconds after calculation. Based on the real-time power feedback from MCU2, it quickly adjusts the power generation of MCU1, achieving rapid power response and energy management for the entire vehicle.

[0048] The specific limitations of each functional step in the control method of the power domain controller system for new energy construction machinery described above can be found in the limitations of the power domain controller system for new energy construction machinery mentioned above, and will not be repeated here. Each module in the above system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the corresponding operations of each module. This also achieves the beneficial effect of meeting the control requirements of VCU / TCU and covering most of the application needs of new energy construction machinery.

[0049] In some embodiments of this application, an electronic device is also provided, comprising: at least one processor; and a memory connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, which executes the aforementioned control method for a power domain controller system for new energy engineering machinery. Its internal structure diagram can be shown as follows. Figure 6 As shown. Figure 6 The diagram schematically illustrates the internal structure of an electronic device according to an embodiment of this application. The electronic device includes a processor A01, a network interface A02, a memory (not shown), and a database (not shown) connected via a system bus. The processor A01 provides computing and control capabilities. The memory includes internal memory A03 and a non-volatile storage medium A04. The non-volatile storage medium A04 stores an operating system B01, a computer program B02, and a database (not shown). The internal memory A03 provides an environment for the operation of the operating system B01 and the computer program B02 stored in the non-volatile storage medium A04. The network interface A02 is used for communication with external terminals via a network connection. When the computer program B02 is executed by the processor A01, it implements a control method for a power domain controller system for new energy engineering machinery.

[0050] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0051] In one embodiment provided in this application, a machine-readable storage medium is provided, on which instructions are stored, which, when executed by a processor, cause the processor to be configured to perform the aforementioned control method for a power domain controller system for new energy engineering machinery.

[0052] In one embodiment provided in this application, a computer program product is provided, including a computer program that, when executed by a processor, implements the aforementioned control method for a power domain controller system for new energy engineering machinery.

[0053] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0054] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, produce a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0055] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0056] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0057] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0058] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0059] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0060] It should also be noted that 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 process, method, article, or apparatus. Unless otherwise specified, 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 that element.

[0061] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A power domain controller system for a new energy construction machine, characterized by, The system comprises: a multi-core master chip, different cores in the multi-core master chip are deployed with functional subsets of functional components of functional units in a power domain, the functional subsets being divided according to a functional unit dimension and a functional safety dimension; a storage resource, the storage resource is divided into a plurality of storage partitions, at least one shared storage partition in the plurality of storage partitions is used for sharing data by different cores in the multi-core master chip; a software system, used for providing an application program running environment based on the multi-core master chip and the storage resource; and an input and output interface, used for data interaction with external devices of the system.

2. The system of claim 1, wherein, The functional subsets of the functional components of the functional units in the power domain deployed on different cores in the multi-core master chip comprise: deploying a vehicle controller and a gearbox controller on a first core in the multi-core master chip; deploying the gearbox controller and a functional subset with functional safety requirements of a plurality of motor controllers on a second core in the multi-core master chip; deploying functional subsets without functional safety requirements of different motor controllers on the remaining cores in the multi-core master chip respectively.

3. The system of claim 1, wherein, The multi-core master chip comprises at least one lockstep core; the functional subset with functional safety requirements is deployed to the lockstep core.

4. The system of claim 3, wherein, Each storage partition in the plurality of storage partitions except the shared storage partition is configured to have an access relationship with only one corresponding core or one lockstep core in the multi-core master chip.

5. The system of claim 4, wherein, Data with functional safety requirements and data without functional safety requirements that can be accessed by the same core in the multi-core master chip are respectively stored to different storage partitions.

6. The system of claim 1, wherein, The software system comprises: a real-time running environment layer, a basic software layer running below the real-time running environment layer, and an application program layer running above the real-time running environment layer.

7. The system of claim 6, wherein, The basic software layer comprises: a system service layer, used for providing necessary system support and services for an upper layer application; an ECU abstraction layer, used for encapsulating hardware interface service decoupling software and hardware; a microcontroller abstraction layer, used for encapsulating driving of internal peripherals of a chip; a complex device driving layer, used for providing hardware driving with complex or special requirements.

8. The system of claim 6, wherein, The application program layer comprises: a project adaptation layer, used for carrying difference codes and data of different projects; a functional layer, used for carrying codes and data that do not change with specific project and hardware differences; a hardware adaptation layer, used for carrying codes and data that change with hardware differences; an interface layer, used for carrying data interaction of the application program layer through the real-time running environment layer and the basic software layer, data interaction across cores or software partitions; a data center layer, used for carrying data interaction between modules in the application program layer, and realizing decoupling between the modules.

9. The system of claim 1, wherein, The input and output interface comprises: multi-path power supply output, multi-path analog input, multi-path frequency signal input, multi-path high-side input, multi-path low-side output, and multi-path analog output, multi-path PWM output, and multi-path high-speed signal bus.

10. A control method for a power domain controller system of a new energy construction machine, characterized by, The method for the power domain controller system of the new energy engineering machinery comprises: acquiring a control task; Determine the functional units participating in the control based on the control task, and collect corresponding parameters through an input-output interface; The functional units participating in the control interact data through a shared storage partition, and generate control instructions corresponding to the control task through preset logic and the collected parameters.

Images