Using method and device of double-vehicle-control-unit software architecture and storage medium
By determining the vehicle controller type and dividing the functions of the master and slave controllers, the problem of insufficient vehicle controller ports is solved, and functional expansion and cost reduction are achieved on the existing basis.
Patent Information
- Application Number
- CN202510959081.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-11
- Publication Date
- 2025-10-03
AI Technical Summary
As the functional requirements of the entire vehicle increase, the port resources of the vehicle controller are insufficient, resulting in the need to redevelop the controller with existing technology, which is time-consuming, costly and has uncertain performance.
By determining the type of vehicle controller as a master controller or a slave controller and verifying the A and B message information, the functional division of the master and slave controllers is achieved to meet actual needs.
Without developing a completely new controller, functional requirements can be met, R&D costs can be reduced, and system stability and efficiency can be improved.
Smart Images
Figure CN120742853A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of automobile control technology, and in particular to a method, apparatus, device, and computer-readable storage medium for using a dual vehicle controller software architecture. Background Art
[0002] The VCU, or Vehicle Control Unit, is a crucial control unit in new energy vehicles, responsible for implementing vehicle control decisions. Unlike conventional fuel vehicles, this device is specifically designed for new energy vehicles. The VCU interprets the driver's intentions by collecting signals such as the accelerator pedal, gear position, and brake pedal, and monitors information such as vehicle speed and temperature to make judgments and take action. It issues commands to the power battery system, controls the vehicle's operating status, and manages the operating mode of the accessory power supply system. The VCU is also responsible for fault diagnosis, protection, and data storage for the entire vehicle system.
[0003] The VCU's hardware resources include analog inputs, digital inputs, sensor power supplies, PWM inputs and outputs, high-side and low-side drivers, H-bridge drivers, and a range of other drive and control resources. By properly controlling the outputs of these pins, the associated valves and actuators are controlled, thereby enabling the operation of the entire vehicle and its various subsystems and components.
[0004] However, as vehicle functionality requirements increase, sensors, vehicle controller driver components, and other components are increasingly needed, and the demand for port resources on the vehicle controller is also increasing. For currently used vehicle controllers, different types of control resources are limited. When developing VCUs, companies generally consider the lifecycle and product cost, and appropriately expand requirements based on current actual needs. However, as functional requirements continue to increase, the reserved ports often become insufficient, necessitating the need for more acquisition and driver interfaces.
[0005] In existing technology, developing a new controller from scratch is often the best approach. This new controller perfectly meets current needs, which is the most practical approach from a practical perspective. A less-than-ideal approach is to abandon some component layouts, forgoing certain functions and control accuracy to meet current control needs. However, this approach is less acceptable to customers in an increasingly competitive environment.
[0006] Therefore, companies often choose the first approach—redevelopment. However, developing a completely new vehicle controller is time-consuming, often requiring at least six months. It's also expensive. Third, performance and stability are uncertain, requiring extensive testing and adaptation. This approach is especially uneconomical and time-consuming when the product being developed isn't ready for mass shipment. Therefore, a solution to these problems is urgently needed. Summary of the Invention
[0007] The present application provides a method, device, equipment and computer-readable storage medium for using a dual vehicle controller software architecture, which can solve the technical problem in the prior art that as the functional requirements of the vehicle continue to increase, the reserved ports of the vehicle controller are often insufficient.
[0008] In a first aspect, an embodiment of the present application provides a method for using a dual vehicle controller software architecture, the method for using the dual vehicle controller software architecture comprising: Determining the type of the vehicle controller according to an input signal of a first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; If it is determined that the type of the vehicle controller includes a master controller and a slave controller, verifying whether the master controller has successfully confirmed the failure based on the A message information sent by the master controller; Verify whether the slave controller has successfully confirmed the failure based on the B message information received from the slave controller; If both the master controller and the slave controller are confirmed to be successful, the control functions of the master controller and / or the slave controller are divided according to actual needs to use the dual vehicle controller software architecture.
[0009] In combination with the first aspect, in one embodiment, determining the type of the vehicle controller according to the input signal of the first port of the vehicle controller includes: If it is detected that the input signal of the first port of the vehicle controller is a voltage signal, confirming that the type of the vehicle controller is a main controller; If it is detected that the input signal of the first port of the vehicle controller is a ground signal, it is determined that the type of the vehicle controller is a slave controller.
[0010] In combination with the first aspect, in one embodiment, verifying whether the main controller has successfully confirmed the failure based on obtaining the A message information sent by the main controller includes: Reading a first status code from the A message information by the slave controller to verify whether the master controller confirms success; If the first status code is confirmed to be the first main status code, the main controller confirms success.
[0011] With reference to the first aspect, in one embodiment, verifying whether the confirmation by the slave controller is successful based on obtaining the B message information sent by the slave controller includes: Reading a second status code from the B message information by the master controller to verify whether the slave controller confirms successfully; If it is confirmed that the second status code is the second slave status code, the slave controller confirms successfully.
[0012] In conjunction with the first aspect, in one embodiment, dividing the control functions of the master controller and / or the slave controller according to actual needs includes: Formulate control function division strategy based on actual needs; According to the control function division strategy, the sensors to be connected to the master controller and / or the slave controller are divided, so as to perform control function division on the master controller and / or the slave controller.
[0013] In conjunction with the first aspect, in one embodiment, formulating a control function division strategy according to actual needs includes: If the actual requirement is to quickly implement multiple control functions based on the same sensor signal, the control function division strategy is: evenly divide the multiple control functions implemented by the same sensor signal into the master and slave controllers; If the actual requirement is to reduce the wiring between the master and slave controllers and the sensors, the control function division strategy is to divide the control function corresponding to the same sensor into the master controller or the slave controller.
[0014] In combination with the first aspect, in one embodiment, before both the master controller and the slave controller confirm success, the method further includes: If the first status code is not the first main status code, the slave controller reads the status of the life signal from the A message information; or if the second status code is not a second slave status code, the slave controller reads the status of the life signal from the B message information; If it is determined that the state of the life signal is a continuous state, the master controller and / or the slave controller confirms failure and then tries to connect again; If it is determined that the state of the life signal is not a continuous state, then a communication failure occurs in the system, and then communication failure information is recorded and reported.
[0015] In a second aspect, an embodiment of the present application provides a device for using a dual vehicle controller software architecture, the device for using the dual vehicle controller software architecture comprising: a confirmation module, configured to determine a type of the vehicle controller according to an input signal of a first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; A first verification module is configured to, if it is determined that the type of the vehicle controller includes a master controller and a slave controller, verify whether the master controller has successfully confirmed the failure based on the A message information obtained from the master controller; A second verification module is used to verify whether the confirmation of the slave controller is successful based on the B message information obtained from the slave controller; A division module is used to divide the control functions of the master controller and / or the slave controller according to actual needs if both the master controller and the slave controller are confirmed to be successful, so as to use a dual vehicle controller software architecture.
[0016] In a third aspect, an embodiment of the present application provides a device for using a dual vehicle controller software architecture, wherein the device for using the dual vehicle controller software architecture includes a processor, a memory, and a program for using the dual vehicle controller software architecture stored in the memory and executable by the processor, wherein when the program for using the dual vehicle controller software architecture is executed by the processor, the steps of the method for using the dual vehicle controller software architecture as described above are implemented.
[0017] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program for using the dual vehicle controller software architecture is stored. When the program for using the dual vehicle controller software architecture is executed by a processor, the steps of the method for using the dual vehicle controller software architecture as described above are implemented.
[0018] The beneficial effects of the technical solutions provided in the embodiments of the present application include: The type of the vehicle controller is determined based on the input signal of the first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; if the type of the vehicle controller is determined to include a master controller and a slave controller, the master controller is verified to be successful based on the A message information sent by the master controller; the slave controller is verified to be successful based on the B message information sent by the slave controller; if both the master controller and the slave controller are confirmed to be successful, the control functions of the master controller and the slave controller are divided according to actual needs, thereby solving the technical problem in the related art that as the functional requirements of the vehicle continue to increase, the reserved ports of the vehicle controller are often insufficient. The present application provides a method for using a dual vehicle controller software architecture, which can meet the functional requirements of the vehicle without developing a completely new vehicle controller, thereby achieving the technical effect of meeting user needs while reducing R&D costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 This is a flowchart of an embodiment of a method for using the dual vehicle controller software architecture of the present application; Figure 2 For this application Figure 1 Detailed flow chart of step S40; Figure 3This is a functional module diagram of an embodiment of a device for using the dual vehicle controller software architecture of the present application; Figure 4 This is a schematic diagram of the hardware structure of the device using the dual vehicle controller software architecture involved in the embodiment of the present application. DETAILED DESCRIPTION
[0020] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0021] First, some technical terms in this application are explained to facilitate those skilled in the art to understand this application.
[0022] In order to make the objectives, technical solutions and advantages of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.
[0023] In a first aspect, an embodiment of the present application provides a method for using a dual vehicle controller software architecture.
[0024] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the method for using the dual vehicle controller software architecture of this application. Figure 1 As shown, the use of the dual vehicle controller software architecture includes: Step S10: determining the type of the vehicle controller according to an input signal of the first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; For example, the vehicle controller includes a master controller and a slave controller. A voltage signal is typically a high-level signal (e.g., 12V or 5V), indicating that the controller needs to perform a specific function or enter a certain operating mode. A ground signal is a low-level signal (0V), indicating that the controller needs to perform another function or enter another operating mode.
[0025] The type of controller can be determined based on the input signal. The following are some common methods of determination: Example 1: Decision based on voltage signal If the input signal is 12V, the vehicle controller identifies itself as the master controller. The master controller includes core vehicle control functions, such as powertrain management and CAN bus communication. The master controller is typically directly connected to key functional modules (such as the powertrain and instrument panel).
[0026] Example 2: Decision based on ground signal The input signal is grounded (0V): The vehicle controller is recognized as a slave controller.
[0027] The functions of the slave controller include auxiliary functions, such as sensor signal acquisition, processing of some communication protocols, etc.
[0028] The slave controller is usually connected to non-core functional modules (such as _BLUETOOTH winger).
[0029] No input signal: The vehicle controller is identified as an undefined controller.
[0030] In this case, the controller may enter a default state, awaiting further configuration or initialization.
[0031] When the vehicle starts, the master and slave controllers determine the vehicle type based on the input signal (e.g., 12V or ground) at the first port. The master controller is responsible for core vehicle control functions, such as powertrain management and CAN bus communication. The slave controller is responsible for auxiliary functions, such as sensor signal acquisition and processing of some communication protocols.
[0032] In some cases, it may be necessary to add new functional modules to the vehicle system. By changing the input signal of the first port, some vehicle controllers can be dynamically configured as master controllers or slave controllers to meet the new functional requirements.
[0033] Voltage signals are often used for controllers that require high-priority functions. For example, a main controller may require a high-level signal (such as 12V) to activate its core functions.
[0034] Ground signals are often used for auxiliary functions of controllers. For example, a slave controller may use a ground signal (0V) to perform its auxiliary functions.
[0035] No input signal is typically used when the controller is in an undefined or default state, awaiting further configuration or initialization.
[0036] Specifically, confirming the type of the vehicle controller based on the input signal of the first port of the vehicle controller includes: if it is detected that the input signal of the first port of the vehicle controller is a voltage signal, confirming that the type of the vehicle controller is a master controller; if it is detected that the input signal of the first port of the vehicle controller is a ground signal, confirming that the type of the vehicle controller is a slave controller.
[0037] For example, ensure that the first port of the vehicle controller is correctly connected to the corresponding signal source. The master controller is connected to a voltage signal (e.g., 12V) and the slave controller is connected to a ground signal (0V). After power-on, both controllers start simultaneously and begin detecting the input signal at the first port. The master controller detects a high voltage signal (e.g., 12V), identifies itself as the master controller, and is responsible for executing core functions. The slave controller detects a ground signal (0V), identifies itself as the slave controller, and is responsible for auxiliary functions. The master and slave controllers communicate via the CAN bus to ensure the correct transmission of information and the coordinated operation of the system. The slave controller sends the collected data to the master controller, which processes it and then feeds back instructions. The system continuously monitors the input signals and the status of the vehicle controller to ensure that the master and slave roles are clear and the function allocation is reasonable.
[0038] Step S20: If it is determined that the type of the vehicle controller includes a master controller and a slave controller, verify whether the master controller has successfully confirmed the failure based on the A message information sent by the master controller; For example, receiving an A message: The slave controller receives an A message from the master controller via a communication bus (such as a CAN bus). The A message contains status information about the master controller, such as the master-slave status code and the life signal status. If the status code read by the slave controller is 1, the master controller is confirmed to be successful. If the status code is not 1, the life signal status is further checked. If the life signal status is continuous, the master controller has failed to confirm and may require resynchronization or troubleshooting. If the life signal status is discontinuous, the system may have a communication failure and require troubleshooting.
[0039] Based on the verification results, the main controller records the confirmation status. This notifies other system modules to facilitate subsequent functional division and operation. If the main controller fails to confirm, the system may attempt to reinitialize or restart. If communication fails, the system triggers appropriate error handling mechanisms to ensure overall system stability.
[0040] After successful confirmation, the system continuously monitors the status of the main controller and regularly receives and verifies the life signals sent by the main controller to ensure its normal operation.
[0041] Specifically, the verification of whether the main controller has successfully confirmed based on obtaining the A message information sent by the main controller includes: reading the first status code from the A message information through the slave controller to verify whether the main controller has successfully confirmed; if the first status code is confirmed to be the first main status code, the main controller has successfully confirmed.
[0042] For example, in an autonomous driving system, the master controller is responsible for vehicle navigation and path planning. The slave controller is responsible for vehicle speed and braking control. The master controller sends an A message containing: Master-Slave Status Code = 1, Life Signal Status = Continuous. The slave controller receives the A message, interprets the Master-Slave Status Code as 1, and confirms the master controller's success. The slave controller then sends a confirmation message, notifying the system that the master controller has successfully confirmed the transaction.
[0043] If the master-slave status code in message A is 0, the system continues to check whether the life signal status is continuous. If it is continuous, the master controller determines that the master controller confirmation has failed, and the system triggers the resynchronization mechanism to try to reconnect to the master controller. If it is discontinuous, the system considers a communication failure and may reinitialize the communication module.
[0044] Step S30: Verify whether the slave controller confirms successfully based on the B message information received from the slave controller; Exemplarily, after startup, the slave controller sends a B message via the communication bus, including a status code and a life signal. The master controller receives the B message from the slave controller via the communication bus. The master controller extracts the status code from the B message and checks it. If the status code is a preset success value (such as 2), the slave controller is confirmed to have successfully started. If the status code is not a success value, the master controller continues to check the life signal status. The master controller checks whether the life signal sent by the slave controller is continuous. If the life signal is continuous, the master controller confirms that the slave controller has failed to confirm. If the life signal is discontinuous, the master controller confirms that a communication failure has occurred in the system.
[0045] If the slave controller confirms successfully, the master controller allows it to execute the assigned control function. If the confirmation fails or the communication fails, the master controller triggers the corresponding fault handling mechanism, including reinitializing the slave controller, switching to the backup controller, or recording the error log for subsequent analysis.
[0046] Specifically, the method of verifying whether the slave controller has successfully confirmed based on obtaining the B message information sent by the slave controller includes: reading a second status code from the B message information through the master controller to verify whether the slave controller has successfully confirmed; if the second status code is confirmed to be a second slave status code, the slave controller has successfully confirmed.
[0047] For example, in a vehicle electronic control system, after startup, a slave controller periodically sends B messages containing its status to the master controller. The master controller receives and parses the B messages and reads the status code. If the status code is 2, the slave controller is confirmed to have successfully authenticated and is allowed to control the vehicle's lighting system.
[0048] If the status code is not 2 or the life signal is abnormal, the main controller can record the error information for subsequent troubleshooting.
[0049] Step S40: If both the master controller and the slave controller confirm success, the control functions of the master controller and / or the slave controller are divided according to actual needs to use a dual vehicle controller software architecture.
[0050] Exemplarily, the control function division of the master controller and the slave controller according to actual needs includes: assigning tasks to controllers with lower loads according to the current system load to improve overall efficiency; and assigning critical tasks to controllers with higher reliability according to the importance and timeliness of the tasks.
[0051] For example, the control functions of the master controller include global scheduling and monitoring, high-level decision-making and path planning, and overall coordination of system status. The control functions of the slave controller include specific execution functions such as mechanical transmission, sensor data acquisition, localized data processing and feedback control, and direct interaction with actuators.
[0052] Implementation of dynamic adjustment: Monitoring module: Continuously monitor key indicators such as system load, resource usage, and task completion.
[0053] Evaluation module: Based on the preset strategy, regularly or in real time evaluates whether the current functional division is optimal.
[0054] Adjust modules: Based on the evaluation results, adjust function allocation and redefine task modules to optimize system performance.
[0055] Exception handling mechanism: Fault detection: Monitor the status and response of each controller in real time to detect abnormal situations in a timely manner.
[0056] Quick response: When a fault is detected, the backup function allocation mechanism is quickly activated to avoid system service interruption.
[0057] Recovery procedure: After the fault is resolved, gradually restore the original functional division or reallocate tasks according to the new system status.
[0058] Result feedback and optimization: Data collection: During the functional division and operation process, collect various key data, including task completion time, resource utilization efficiency, system response, etc.
[0059] Analysis and optimization: Regularly analyze the collected data to identify potential optimization areas, further optimize the functional division strategy, and improve the overall system performance.
[0060] User interface and operation: Visual interface: Provides system administrators or operators with an intuitive interface that displays information such as the current functional division status, system load, and resource usage.
[0061] Manual Intervention: Allows administrators to manually adjust functional divisions when needed to address special situations or for testing.
[0062] Log records: Record the adjustment of each functional division in detail, including time, adjustment content, execution results, etc., to facilitate subsequent audit and analysis.
[0063] Specifically, if both the master controller and the slave controller confirm success, the method further includes: If the first status code is not the first master status code, the slave controller reads the status of the life signal from the A message information; or if the second status code is not the second slave status code, the slave controller reads the status of the life signal from the B message information; if it is determined that the status of the life signal is a continuous state, the master controller and / or the slave controller confirms the failure, and then resynchronizes or troubleshoots the problem; if it is determined that the status of the life signal is not a continuous state, a communication failure occurs in the system, and then the communication fault information is recorded and reported and fault diagnosis is performed.
[0064] Exemplarily, if the first status code is not 1 (the first master status code), the life signal status is checked. If the first status code is not 1, the slave controller continues to read the life signal status in the A message. If the life signal status is continuous, the master controller confirms that the confirmation has failed. If the life signal status is not continuous, a communication failure is confirmed in the system.
[0065] For example, in an autonomous driving system, the master controller sends an A message via the CAN bus, containing a first status code of 1 and a continuous life signal. Upon receiving the message, the slave controller confirms that the master controller is functioning normally and continues system operation. If the master controller sends an A message with a first status code of 0 and a continuous life signal, the slave controller determines that the master controller has failed, triggering reinitialization or troubleshooting. If the master controller sends a damaged or incomplete A message and the life signal is discontinuous, the slave controller detects a communication failure and initiates communication fault diagnosis and recovery procedures.
[0066] In this embodiment, the type of the vehicle controller is determined based on the input signal of the first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; if it is determined that the type of the vehicle controller includes a master controller and a slave controller, the master controller is verified to be successful based on the A message information sent by the master controller; the slave controller is verified to be successful based on the B message information sent by the slave controller; if both the master controller and the slave controller are confirmed to be successful, the control functions of the master controller and the slave controller are divided according to actual needs, which solves the problem in related technologies that as the functional requirements of the vehicle continue to increase, the reserved ports of the vehicle controller are often insufficient. This embodiment provides a method for using a dual vehicle controller software architecture, which can meet the functional requirements of the vehicle without developing a completely new vehicle controller, thereby achieving the technical effect of meeting user needs while reducing R&D costs.
[0067] Furthermore, in one embodiment, referring to Figure 2 , Figure 2 For this application Figure 1 Detailed flow chart of step S40 in FIG. Figure 2 As shown, the control function division of the master controller and the slave controller according to actual needs includes: Step S41: Formulate a control function division strategy based on actual needs; For example, centralize key functional modules (such as ABS, ESP, and engine control) within the main controller, ensuring that the main controller has sufficient port resources to directly connect to necessary devices (such as accelerometers and brake sensors). These critical functions typically require high real-time performance and low latency, and are connected directly to the main controller through dedicated ports to ensure reliable communication and fast response.
[0068] Assign auxiliary function modules (such as air conditioning control, seat adjustment, and entertainment systems) to slave controllers, which then exchange data with the master controller via bus communications (such as CAN and LIN). This approach not only reduces the master controller's port usage but also reduces its load, improving overall system efficiency.
[0069] Comprehensively plan communication function modules to ensure a reasonable allocation of communication resources between key functions and auxiliary functions. For example, you can configure communication for key functions to be given a high priority to ensure that they receive priority communication resources even under high load conditions.
[0070] Specifically, the control function division strategy formulated according to actual needs includes: if the actual need is to quickly realize multiple control functions based on the same sensor signal, the control function division strategy is: divide the multiple control functions realized by the same sensor signal evenly into the master and slave controllers; if the actual need is to reduce the wiring between the master and slave controllers and the sensors, the control function division strategy is: divide the control functions corresponding to the same sensor into the master controller or the slave controller.
[0071] For example, if the actual requirement is to quickly implement multiple control functions based on the same sensor signal, the control function division strategy is to evenly divide the multiple control functions implemented by the same sensor signal into the master and slave controllers, including: It is determined that the signal of a certain sensor can be used to implement multiple control functions. For example, the signal of the vehicle speed sensor can be used for cruise control, anti-lock braking system (ABS), electronic stability program (ESP), etc.
[0072] Determine the real-time requirements and resource requirements for each control function. For example, ABS requires high-speed response and high priority, while cruise control may operate at a steady speed and does not require such high real-time requirements.
[0073] Functions are evenly distributed between the master and slave controllers based on their priority and resource requirements. For example, ABS and ESP are assigned to the master controller, while cruise control and speed-related information display are assigned to the slave controller.
[0074] Ensure efficient communication between the master and slave controllers to achieve real-time data sharing and functional coordination. For example, use the CAN bus to achieve two-way communication to ensure the rapid transmission of vehicle speed data and control instructions.
[0075] Comprehensive testing is performed on the divided functions to ensure that all control functions can work in coordination under various operating conditions to meet the requirements of fast response and efficient processing.
[0076] If the actual requirement is to reduce the wiring between the master and slave controllers and the sensors, the control function division strategy is: the control function corresponding to the same sensor is divided into the master controller or the slave controller, including: Make sure that the signal provided by each sensor is used only for a specific control function. For example, the signal from the rain sensor is used only for automatic wiper control and headlight adjustment.
[0077] Assign all control functions related to the same sensor to a single controller, eliminating the need to connect that sensor to multiple controllers. For example, connect a rain sensor to a slave controller and assign automatic wiper control and headlight adjustment functions to the slave controller as well.
[0078] If the sensor itself supports multiple signal outputs or multiple functions, consider implementing multiple functions through software configuration without adding hardware connections. For example, with a bus-type sensor, different signal types can be selected through software commands.
[0079] Reasonably plan the functional distribution of controllers in the entire system to ensure balanced load on each controller while meeting the need to reduce wiring.
[0080] Test the divided functions to ensure that all control functions can still operate normally while reducing wiring and that sensor signals can be accurately transmitted and processed.
[0081] Step S42: dividing the sensors to be connected to the master controller and / or the slave controller according to the control function division strategy, so as to perform control function division on the master controller and / or the slave controller; Exemplarily, if the control function division strategy is to evenly divide multiple control functions implemented by the same sensor signal between the master and slave controllers, the method for dividing the sensors to be connected to the master controller and the slave controller includes: Determine that the signals of certain sensors can be used by multiple control functions. For example, the signal of the vehicle speed sensor can be used by ABS, ESP, cruise control and other systems.
[0082] Upgrading control functions ensures that critical functions (such as ABS and ESP) are assigned to the master controller, while auxiliary functions (such as cruise control) are assigned to the slave controller.
[0083] Multiple control functions implemented by the same sensor signal are evenly distributed to the master controller and slave controllers to balance the load and optimize the response speed.
[0084] Use a high-speed communication bus (such as CAN bus) to achieve real-time data sharing and fast response between the master controller and the slave controller.
[0085] Based on real-time load monitoring and system requirements, the distribution of control functions is dynamically adjusted to ensure efficient operation of the system under different driving conditions.
[0086] For example, the ABS (anti-lock braking system) and ESP (electronic stability program) functions implemented by the vehicle speed sensor are assigned to the master controller, while adaptive cruise control and speed-related driver assistance functions (such as speed warnings) are assigned to the slave controller. During emergency braking, the master controller quickly responds to ABS and ESP to ensure vehicle stability. During high-speed cruising, the slave controller adjusts cruise control based on vehicle speed to enhance driving comfort.
[0087] If the control function division strategy is to divide the control function corresponding to the same sensor into the same controller, the method of dividing the sensors to be connected to the master controller and the slave controller includes: It is determined that the signals of certain sensors are only used for specific related control functions. For example, the signal of the rain sensor is used for automatic wipers and headlight adjustment.
[0088] Allocate all control functions related to the same sensor to the same controller to avoid connecting the sensor to multiple controllers.
[0089] Use bus communication (such as LIN bus) to achieve centralized processing of multiple control functions under the same sensor, reducing physical connections.
[0090] Reasonably plan the functional distribution of controllers in the system to ensure that the functional division is consistent with wiring optimization.
[0091] Ensure that the divided sensor connections and functions meet system requirements, reducing wiring without affecting functional performance.
[0092] For example, a rain sensor connects only to a slave controller, offloading all its control functions (such as automatic wiper control and headlight adjustment) to the slave controller. Connecting the rain sensor to the slave controller reduces the number of physical connections to the master controller. The slave controller handles all rain-related functions, simplifying the system architecture and improving reliability.
[0093] In this embodiment, a control function division strategy is formulated according to actual needs; according to the control function division strategy, the sensors that need to be connected to the master controller and the slave controller are divided; by dividing the sensors that need to be connected to the master controller and the slave controller, the control function division of the master controller and the slave controller is completed, thereby solving the technical problem of unreasonable function division of multiple vehicle controllers in related technologies, resulting in slow control function response speed and complex wiring between the vehicle controller and the sensors. Through this embodiment, the control function of the vehicle controller is reasonably divided according to actual needs, thereby achieving the technical effect of fast control function response speed and simple and efficient wiring between the vehicle controller and the sensors.
[0094] In a second aspect, an embodiment of the present application also provides a device for using a dual vehicle controller software architecture.
[0095] In one embodiment, referring to Figure 3 , Figure 3 This is a functional module diagram of an embodiment of a device for using the dual vehicle controller software architecture of this application. Figure 3 As shown, the device using the dual vehicle controller software architecture includes: Confirmation module 01, used to determine the type of the vehicle controller according to the input signal of the first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; The first verification module 02 is used to verify whether the confirmation of the master controller is successful based on the A message information sent by the master controller if it is determined that the type of the vehicle controller includes a master controller and a slave controller; The second verification module 03 is used to verify whether the confirmation of the slave controller is successful based on the B message information sent by the slave controller; The division module 04 is used to divide the control functions of the master controller and / or the slave controller according to actual needs if both the master controller and the slave controller are confirmed to be successful, so as to use the dual vehicle controller software architecture.
[0096] Furthermore, in one embodiment, the confirmation module 01 is further configured to: If it is detected that the input signal of the first port of the vehicle controller is a voltage signal, confirming that the type of the vehicle controller is a main controller; If it is detected that the input signal of the first port of the vehicle controller is a ground signal, it is determined that the type of the vehicle controller is a slave controller.
[0097] Furthermore, in one embodiment, the first verification module 02 is further configured to: Reading a first status code from the A message information by the slave controller to verify whether the master controller confirms success; If the first status code is confirmed to be the first main status code, the main controller confirms success.
[0098] Furthermore, in one embodiment, the second verification module 03 is further configured to: Reading a second status code from the B message information by the master controller to verify whether the slave controller confirms successfully; If it is confirmed that the second status code is the second slave status code, the slave controller confirms successfully.
[0099] Furthermore, in one embodiment, the division module 04 is further configured to: Formulate control function division strategy based on actual needs; According to the control function division strategy, the sensors to be connected to the master controller and / or the slave controller are divided, so as to perform control function division on the master controller and / or the slave controller.
[0100] Furthermore, in one embodiment, the division module 04 is further configured to: If the actual requirement is to quickly implement multiple control functions based on the same sensor signal, the control function division strategy is: evenly divide the multiple control functions implemented by the same sensor signal into the master and slave controllers; If the actual requirement is to reduce the wiring between the master and slave controllers and the sensors, the control function division strategy is to divide the control function corresponding to the same sensor into the master controller or the slave controller.
[0101] Furthermore, in one embodiment, the first verification module 02 is further configured to: If the first status code is not the first main status code, the slave controller reads the status of the life signal from the A message information; or if the second status code is not a second slave status code, the slave controller reads the status of the life signal from the B message information; If it is determined that the state of the life signal is a continuous state, the master controller and / or the slave controller confirms the failure and then resynchronizes or troubleshoots the failure; If it is determined that the state of the life signal is not a continuous state, then a communication failure occurs in the system, and then the communication failure information is recorded and reported and a fault diagnosis is performed.
[0102] Among them, the functional implementation of each module in the above-mentioned device for using the dual vehicle controller software architecture corresponds to the various steps in the embodiment of the method for using the above-mentioned dual vehicle controller software architecture, and its functions and implementation processes will not be repeated here one by one.
[0103] On the third aspect, an embodiment of the present application provides a device for using a dual vehicle controller software architecture. The device for using the dual vehicle controller software architecture can be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.
[0104] Reference Figure 4 , Figure 4 Schematic diagram of the hardware structure of the device using the dual vehicle controller software architecture involved in the embodiment of the present application. In the embodiment of the present application, the device using the dual vehicle controller software architecture may include a processor, a memory, a communication interface and a communication bus.
[0105] The communication bus may be of any type and is used to interconnect the processor, memory, and communication interface.
[0106] Communication interfaces include input / output (I / O), physical, and logical interfaces, used to interconnect components within the device implementing the dual vehicle controller software architecture, as well as to connect the device to other devices (such as other computing devices or user devices). Physical interfaces can include Ethernet, fiber, or ATM interfaces; user devices can include displays and keyboards.
[0107] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0108] The processor may be a general-purpose processor that can invoke a program for using the dual vehicle controller software architecture stored in memory and execute the method for using the dual vehicle controller software architecture provided in the embodiments of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the program for using the dual vehicle controller software architecture is invoked can be referenced from the various embodiments of the method for using the dual vehicle controller software architecture of the present application and will not be further described here.
[0109] Those skilled in the art will understand that Figure 4 The hardware structure shown in the figure does not constitute a limitation to the present application and may include more or fewer components than shown in the figure, or a combination of certain components, or a different arrangement of components.
[0110] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.
[0111] The computer-readable storage medium of the present application stores a program for using the dual vehicle controller software architecture, wherein when the program for using the dual vehicle controller software architecture is executed by a processor, the steps of the method for using the dual vehicle controller software architecture as described above are implemented.
[0112] Among them, the method implemented when the program using the dual vehicle controller software architecture is executed can refer to the various embodiments of the method for using the dual vehicle controller software architecture of the present application, and will not be repeated here.
[0113] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.
[0114] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit the "first", "second" and "third" to different types.
[0115] In the description of the embodiments of this application, the words "exemplary," "for example," or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary," "for example," or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.
[0116] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.
[0117] In some processes described in the embodiments of the present application, multiple operations or steps are included that appear in a specific order. However, it should be understood that these operations or steps may not be performed in the order in which they appear in the embodiments of the present application or may be performed in parallel. The sequence numbers of the operations are only used to distinguish between different operations, and the sequence numbers themselves do not represent any order of execution. In addition, these processes may include more or fewer operations, and these operations or steps may be performed in sequence or in parallel, and these operations or steps may be combined.
[0118] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, or the part that contributes to the existing technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above and includes a number of instructions for enabling a terminal device to execute the methods described in each embodiment of this application.
[0119] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A method for using a dual vehicle controller software architecture, characterized in that: The method for using the dual vehicle controller software architecture includes: Determining the type of the vehicle controller according to an input signal of a first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; If it is determined that the type of the vehicle controller includes a master controller and a slave controller, verifying whether the master controller has successfully confirmed the failure based on the A message information sent by the master controller; Verify whether the slave controller has successfully confirmed the failure based on the B message information received from the slave controller; If both the master controller and the slave controller are confirmed to be successful, the control functions of the master controller and / or the slave controller are divided according to actual needs to use the dual vehicle controller software architecture.
2. The method for using the dual vehicle controller software architecture according to claim 1, wherein: The determining the type of the vehicle controller according to the input signal of the first port of the vehicle controller includes: If it is detected that the input signal of the first port of the vehicle controller is a voltage signal, confirming that the type of the vehicle controller is a main controller; If it is detected that the input signal of the first port of the vehicle controller is a ground signal, it is determined that the type of the vehicle controller is a slave controller.
3. The method for using the dual vehicle controller software architecture according to claim 1, wherein: The verifying whether the main controller confirms successfully according to the obtained A message information sent by the main controller includes: Reading a first status code from the A message information by the slave controller to verify whether the master controller confirms success; If the first status code is confirmed to be the first main status code, the main controller confirms success.
4. The method for using the dual vehicle controller software architecture according to claim 1, wherein: The verifying whether the slave controller confirms successfully according to the acquired B message information sent by the slave controller includes: Reading a second status code from the B message information by the master controller to verify whether the slave controller confirms successfully; If it is confirmed that the second status code is the second slave status code, the slave controller confirms successfully.
5. The method for using the dual vehicle controller software architecture according to claim 1, wherein: The dividing of control functions of the master controller and / or the slave controller according to actual needs includes: Formulate control function division strategy based on actual needs; According to the control function division strategy, the sensors to be connected to the master controller and / or the slave controller are divided, so as to perform control function division on the master controller and / or the slave controller.
6. The method for using the dual vehicle controller software architecture according to claim 5, characterized in that: The control function division strategy formulated according to actual needs includes: If the actual requirement is to quickly implement multiple control functions based on the same sensor signal, the control function division strategy is: evenly divide the multiple control functions implemented by the same sensor signal into the master and slave controllers; If the actual requirement is to reduce the wiring between the master and slave controllers and the sensors, the control function division strategy is to divide the control function corresponding to the same sensor into the master controller or the slave controller.
7. The method for using the dual vehicle controller software architecture according to claim 1, wherein: If both the master controller and the slave controller confirm success, the method further includes: If the first status code is not the first main status code, the slave controller reads the status of the life signal from the A message information; or if the second status code is not the second slave status code, the slave controller reads the status of the life signal from the B message information; If it is determined that the state of the life signal is a continuous state, the master controller and / or the slave controller confirms failure and then tries to connect again; If it is determined that the state of the life signal is not a continuous state, then a communication failure occurs in the system, and then communication failure information is recorded and reported.
8. A device for using a dual vehicle controller software architecture, characterized in that: The device for using the dual vehicle controller software architecture includes: a confirmation module, configured to determine a type of the vehicle controller according to an input signal of a first port of the vehicle controller, wherein the input signal includes a voltage signal and a ground signal; A first verification module is configured to, if it is determined that the type of the vehicle controller includes a master controller and a slave controller, verify whether the master controller has successfully confirmed the failure based on the A message information obtained from the master controller; A second verification module is used to verify whether the confirmation of the slave controller is successful based on the B message information obtained from the slave controller; A division module is used to divide the control functions of the master controller and / or the slave controller according to actual needs if both the master controller and the slave controller are confirmed to be successful, so as to use the dual vehicle controller software architecture.
9. A device using a dual vehicle controller software architecture, characterized in that: The device for using the dual vehicle controller software architecture includes a processor, a memory, and a program for using the dual vehicle controller software architecture stored in the memory and executable by the processor. When the program for using the dual vehicle controller software architecture is executed by the processor, the steps of the method for using the dual vehicle controller software architecture as described in any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a program for using the dual vehicle controller software architecture, wherein when the program for using the dual vehicle controller software architecture is executed by the processor, the steps of the method for using the dual vehicle controller software architecture as described in any one of claims 1 to 7 are implemented.