Vehicle-mounted controller ID configuration method and device, vehicle-mounted controller ID verification method and device and electronic equipment

Abstract

The invention discloses a vehicle-mounted controller ID configuration and verification method and device and electronic equipment, the vehicle-mounted controller comprises multiple controllers connected to the same network, and the controllers are provided with configuration pins. Determining a reference flag bit corresponding to each controller in the multiple controllers according to the initial level data of the configuration pin; after the power-on cycle of the application layer is started, performing self-verification and mutual verification on the corresponding power-on flag bit according to the reference flag bit corresponding to each controller in the multiple controllers; and according to the power-on flag bit corresponding to each controller in the plurality of controllers, respectively configuring application IDs for the plurality of controllers. According to the method and the device, the configuration pins are added to the multiple controllers, and the level flag bits of the configuration pins are utilized to actively perform coding configuration and real-time verification on the multiple controllers, so that the multiple controllers can meet different control requirements under the same network, the same parts do not need to be distinguished and numbered manually, and the management and assembly cost can be reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle assembly management, and in particular to a method, device and electronic equipment for configuring and verifying an on-vehicle controller ID. Background Art

[0002] With the increasing demand for high-end models and the development of electric drive technology, wheel drive has become the mainstream design of high-end models. In the rear-wheel drive system, each set of drive wheels is equipped with a separate drive motor to meet the power output requirements of each drive wheel under different working conditions, such as increasing the power output of the ground wheels during off-roading, the driving ability requirements of the ground wheels on rugged roads, and the realization of on-the-spot steering. Each set of electric drives needs to be equipped with its own independent cooling and lubrication electric oil pump to meet the different lubrication requirements of each set of electric drives under different working conditions. The electric oil pumps equipped with the two sets of electric drives are the same, and in most cases the software is also the same. However, the cooling and lubrication requirements of each set of electric drives are different at the same time. Therefore, different controllers need to be configured for the two sets of electric drives.

[0003] At present, all parts on the vehicle are equipped with separate IDs to facilitate the management of parts. In high-end wheel drive models, two identical electric drive oil pumps are used as parts in the two electric drives of the rear wheels, respectively, and are distinguished by different part numbers, which increases unnecessary parts management costs and assembly costs. Summary of the invention

[0004] The present invention provides a vehicle controller ID configuration method, device and electronic device to solve the problem that in the existing vehicle electric drive system, different component numbers are used for the same components in different drive wheels, resulting in increased component management costs and assembly costs.

[0005] According to one aspect of the present invention, a method for configuring an on-board controller ID is provided, wherein the on-board controller includes multiple controllers connected to the same network, and any controller in the multiple controllers is provided with a configuration pin, and the method includes: when the multiple controllers are powered on for the first time, determining a reference flag bit corresponding to each controller in the multiple controllers according to initial level data of the configuration pin; after the application layer power-on cycle is started, obtaining a power-on flag bit corresponding to each controller in the multiple controllers, and performing self-checking and mutual check on the power-on flag bit according to the reference flag bit corresponding to each controller in the multiple controllers; and configuring application IDs for the multiple controllers respectively according to the power-on flag bit corresponding to each controller in the multiple controllers.

[0006] Optionally, the multi-controller includes a first electric drive controller and a second electric drive controller; wherein the first electric drive controller is provided with a first configuration pin, and the first configuration pin is electrically connected to a first output terminal of a power supply; the second electric drive controller is provided with a second configuration pin, and the second configuration pin is electrically connected to a second output terminal of the power supply; the electrical polarity of the first output terminal is opposite to that of the second output terminal.

[0007] Optionally, determining the reference flag corresponding to each controller in the multiple controllers according to the initial level data of the configuration pin includes: cyclically monitoring a first initial level state of the first configuration pin and a second initial level state of the second configuration pin; determining a first reference flag of the first electric drive controller according to the first initial level state; determining a second reference flag of the second electric drive controller according to the second initial level state; wherein the first initial level state and the second initial level state have opposite level polarities.

[0008] Optionally, the obtaining of the power-on flag corresponding to each controller in the multiple controllers, and self-checking and mutual-checking the power-on flag according to the reference flag corresponding to each controller in the multiple controllers, includes: cyclically monitoring the power-on status of the first configuration pin and the second configuration pin; determining the first power-on flag of the first electric drive controller according to the power-on status of the first configuration pin, and determining the second power-on flag of the second electric drive controller according to the power-on status of the second configuration pin; self-checking the first power-on flag based on the first reference flag stored in the first electric drive controller; self-checking the second power-on flag based on the second reference flag stored in the second electric drive controller; after the self-check passes, the first electric drive controller reads the second power-on flag, and mutual-checks the second power-on flag based on the first reference flag; the second electric drive controller reads the first power-on flag, and mutual-checks the first power-on flag based on the second reference flag.

[0009] Optionally, configuring application IDs for the multiple controllers respectively according to the power-on flag corresponding to each controller in the multiple controllers includes: configuring a first application ID for the first electric drive controller according to the first power-on flag, and configuring a second application ID for the second electric drive controller according to the second power-on flag.

[0010] Optionally, when determining the reference flag corresponding to each controller in the multiple controllers according to the initial level data of the configuration pin, the method includes: configuring the diagnostic ID of the multiple controllers respectively according to the initial level data; and storing the diagnostic ID and the reference flag in a storage module.

[0011] Optionally, the vehicle controller ID configuration method further includes: when the self-check or the mutual check fails, clearing the diagnostic ID and the reference flag, and updating the diagnostic ID and the reference flag based on level data of the next power-on cycle.

[0012] Optionally, the storage module is an electrically erasable programmable read-only memory.

[0013] Optionally, the vehicle controller ID configuration method further includes: reporting a controller ID abnormality when either the self-check or the mutual check fails.

[0014] Optionally, the vehicle controller ID configuration method also includes: obtaining the state perception fault bit of the counterpart corresponding to each controller in the multiple controllers; clearing the reference flag bit after reporting the controller ID abnormality according to the state perception fault bit, and updating the reference flag bit based on the power-on level data of the next power-on cycle.

[0015] Optionally, the state-aware fault bit includes at least one of the following: the controller has no response after power-on, the response does not match the request, or the control effect does not meet expectations.

[0016] According to another aspect of the present invention, there is provided a vehicle-mounted controller ID verification method, which is applicable to multi-controller ID configuration verification, wherein the vehicle-mounted controller includes multiple controllers connected to the same network, and any controller in the multiple controllers is provided with a configuration pin, and the method includes: when the multiple controllers are powered on for the first time, determining the reference flag bit corresponding to each controller in the multiple controllers according to the initial level data of the configuration pin; after the application layer power-on cycle is started, obtaining the power-on flag bit corresponding to each controller in the multiple controllers, and performing self-verification and mutual verification on the power-on flag bit according to the reference flag bit corresponding to each controller in the multiple controllers.

[0017] According to another aspect of the present invention, there is provided a vehicle-mounted controller ID configuration and verification device, wherein the vehicle-mounted controller includes multiple controllers connected to the same network, and any controller in the multiple controllers is provided with a configuration pin, and the device includes: a storage module, used to store a reference flag bit corresponding to each controller in the multiple controllers, wherein the reference flag bit is determined based on the initial level data of the configuration pin when the multiple controllers are powered on for the first time; and a coding verification module, used to obtain the power-on flag bit corresponding to each controller in the multiple controllers after the application layer power-on cycle is started, and perform self-verification and mutual verification on the power-on flag bit according to the reference flag bit corresponding to each controller in the multiple controllers.

[0018] Optionally, the vehicle controller ID configuration and verification device also includes: a coding configuration module, which is used to configure the application ID of the multiple controllers respectively according to the power-on flag corresponding to each controller in the multiple controllers after the application layer power-on cycle is started.

[0019] According to another aspect of the present invention, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the above-mentioned vehicle controller ID configuration method; or, can execute the above-mentioned vehicle controller ID verification method.

[0020] The technical solution of the embodiment of the present invention sets configuration pins in controllers connected to the same network. When multiple controllers are powered on for the first time, the reference flag corresponding to each controller in the multiple controllers is determined according to the initial level data of the configuration pins. After the power-on cycle at the application layer is started, the power-on flag corresponding to each controller in the multiple controllers is obtained, and the power-on flag is self-checked and mutually checked according to the reference flag corresponding to each controller in the multiple controllers. After the self-check and mutual check are passed, the multiple controllers are respectively configured with application IDs according to the power-on flag corresponding to each controller in the multiple controllers, thereby solving the problem of using different component numbers for the same components in different drive wheels in the existing vehicle electric drive system, which leads to increased component management costs and assembly costs. After the same parts are assembled and applied, the coding configuration and real-time verification are actively completed, so that the multiple controllers can meet different control requirements under the same network without the need to manually distinguish and number the same components, thereby improving the accuracy and efficiency of the coding configuration and reducing the management and assembly costs.

[0021] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0023] Figure 1 A flowchart of a vehicle controller ID configuration method provided in Embodiment 1 of the present invention;

[0024] Figure 2A schematic diagram of the structure of a multi-controller provided in Embodiment 1 of the present invention;

[0025] Figure 3 A flowchart of a dual controller ID configuration method provided in Embodiment 1 of the present invention;

[0026] Figure 4 A flowchart of another vehicle controller ID configuration method provided in Embodiment 1 of the present invention;

[0027] Figure 5 A flowchart of a vehicle controller ID verification method provided in Embodiment 2 of the present invention;

[0028] Figure 6 A schematic diagram of the structure of a vehicle controller ID configuration and verification device provided in Embodiment 3 of the present invention;

[0029] Figure 7 It is a structural schematic diagram of an electronic device for implementing the vehicle controller ID configuration and verification method of an embodiment of the present invention. DETAILED DESCRIPTION

[0030] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. 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 should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof 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 necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0032] Embodiment 1

[0033] Figure 1A flowchart of a vehicle controller ID configuration method provided in Example 1 of the present invention. This embodiment is applicable to application scenarios in which ID configuration is performed on two or more groups of controllers with the same part number. The method can be executed by a vehicle controller ID configuration device, which can be implemented in the form of hardware and / or software, and can be configured in an electronic device.

[0034] Among them, ID is a number that represents the identity information of the part, and the ID of each controller is unique.

[0035] In the present application, the vehicle controller includes multiple controllers connected to the same network, and any of the multiple controllers is provided with a configuration pin, which is connected to the positive output terminal or the negative output terminal of the power supply. The configuration pin is used to configure and identify the controller ID (i.e., ID number). Typically, the configuration pin can be a select pin.

[0036] See also Figure 1 As shown, the vehicle controller ID configuration method of this application includes:

[0037] S1: When the multi-controller is powered on for the first time, the reference flag corresponding to each controller in the multi-controller is determined according to the initial level data of the configuration pin.

[0038] Among them, the first power-on of multiple controllers refers to the first power-on of the whole vehicle after the multiple controllers are assembled. In this embodiment, each controller in the multiple controllers has the same part number before assembly, and after assembly, it is controlled by different counterparts to meet different control requirements. For example, taking the rear-wheel electric drive system as an example, two groups of controllers are connected to the rear-wheel electric drive network, one group of controllers controls the cooling and lubricating electric oil pump of the left rear wheel, and the other group of controllers controls the cooling and lubricating electric oil pump of the right rear wheel. The two groups of controllers can execute the same control strategy.

[0039] Specifically, the configuration pins of each controller in the multi-controller are connected to different power output terminals (such as the positive output terminal or the negative output terminal). When powered on for the first time, the configuration pins of each controller present different level states. By judging the initial level data input by the configuration pins in each controller, the reference flag corresponding to each controller in the multi-controller is set. For example, if the configuration pin of the controller is connected to the positive output terminal of the power supply, the initial level data is in a high level state, and the corresponding reference flag position is 1; if the configuration pin of the controller is connected to the negative output terminal of the power supply, the initial level data is in a low level state, and the corresponding reference flag position is 0. Then, each controller stores its own reference flag in its own storage module.

[0040] S2: After the power-on cycle of the application layer is started, the power-on flag bit corresponding to each controller in the multi-controller is obtained, and the power-on flag bit is self-checked and mutually checked according to the reference flag bit corresponding to each controller in the multi-controller.

[0041] The application layer power-on cycle refers to any power-on cycle after the first power-on.

[0042] Among them, self-checking means comparing the reference flag stored in the controller itself with its own power-on flag. When the reference flag stored in the controller itself is consistent with its own power-on flag, the self-checking passes; when the reference flag stored in the controller itself is inconsistent with its own power-on flag, the self-checking fails.

[0043] Mutual verification means that the reference flag stored in the controller itself is compared with the power-on flag of other controllers in the same network. When the reference flag stored in the controller itself is inconsistent with the power-on flag of other controllers, the mutual verification passes; when the reference flag stored in the controller itself is consistent with the power-on flag of other controllers, the self-verification fails.

[0044] S3: configuring application IDs for the multiple controllers respectively according to the power-on flag bits corresponding to the multiple controllers.

[0045] In this embodiment, after the self-check and mutual check of each power-on cycle are passed, an application ID is configured for each controller in the multi-controller, and the application ID corresponds to each controller in the multi-controller one by one.

[0046] In this embodiment, before assembly, each controller in the multi-controller has the same part number; after the application ID configuration is completed, each controller has a unique application ID. During the operation of the controller, the vehicle controller sends control instructions and interactive data to the corresponding controller by querying the application ID. For example, taking the rear-wheel electric drive system as an example, two groups of controllers are connected to the rear-wheel electric drive network, one group of controllers controls the cooling and lubrication electric oil pump of the left rear wheel, and the other group of controllers controls the cooling and lubrication electric oil pump of the right rear wheel. After the application ID configuration is completed, the vehicle controller sends the control instructions of the left rear wheel to the left rear wheel controller based on the application ID, and sends the control instructions of the right rear wheel to the right rear wheel controller to meet the cooling and lubrication requirements of different electric drives.

[0047] Specifically, multiple controllers are connected to the same network. When multiple controllers are powered on for the first time, the initial level data of the configuration pins of each controller is read, and the reference flag corresponding to the initial level data is stored in its own storage module. After the power-on cycle of the application layer is started, the power-on flag corresponding to each controller is compared with the pre-stored reference flag, and the power-on flag is self-checked and mutually checked. After the self-check and mutual check are passed, the application ID corresponding to each controller is configured according to the power-on flag read in the current power-on cycle, which solves the problem that the same parts in different drive wheels in the existing vehicle electric drive system use different parts numbers, resulting in increased parts management costs and assembly costs. After the same parts are assembled and applied, the coding configuration and real-time verification are actively completed, so that multiple controllers can meet different control requirements under the same network, without the need to manually distinguish and number the same parts, improve the accuracy and efficiency of coding configuration, and reduce management and assembly costs.

[0048] Figure 2 A schematic diagram of a multi-controller structure provided in Embodiment 1 of the present invention exemplarily shows a structure in which two groups of controllers are connected to the same network. The two groups of controllers respectively control actuators with the same performance (for example, electric oil pumps), one group of controllers is used for left rear wheel electric drive control, and the other group of controllers is used for right rear wheel electric drive control.

[0049] See also Figure 2 As shown, the multi-controller includes a first electric drive controller 100 and a second electric drive controller 200 connected to the same network. Among them, the first electric drive controller 100 is provided with a first configuration pin 100P, and the first configuration pin 100P is electrically connected to the first output end of the power supply; the second electric drive controller 200 is provided with a second configuration pin 200P, and the second configuration pin 200P is electrically connected to the second output end of the power supply. Among them, the electrical polarity of the first output end is opposite to that of the second output end. For example, the first output end is the positive end, or the positive end of the engine ignition switch; the second output end is the negative end, or the negative end of the engine ignition switch. In some embodiments, the first electric drive controller 100 is used to control the left rear wheel electric oil pump, and the second electric drive controller 200 is used to control the right rear wheel electric oil pump. The performance of the left rear wheel electric oil pump and the right rear wheel electric oil pump is the same, and corresponding working data can be output based on different lubrication and cooling requirements.

[0050] Figure 3 A flowchart of a dual-controller ID configuration method provided in Embodiment 1 of the present invention exemplarily shows a specific implementation method of performing ID configuration on two controllers.

[0051] See also Figure 2 and Figure 3 As shown, the above step S1 specifically includes the following steps:

[0052] S101: cyclically monitor a first initial level state of a first configuration pin and a second initial level state of a second configuration pin.

[0053] S102: Determine a first reference flag of a first electric drive controller according to a first initial level state, and determine a second reference flag of a second electric drive controller according to a second initial level state.

[0054] The first initial level state and the second initial level state have opposite level polarities.

[0055] See also Figure 2 and Figure 3 As shown, the above step S2 specifically includes the following steps:

[0056] S201: cyclically monitor the power-on status of the first configuration pin and the second configuration pin.

[0057] S202: Determine a first power-on flag of the first electric drive controller according to the power-on state of the first configuration pin, and determine a second power-on flag of the second electric drive controller according to the power-on state of the second configuration pin.

[0058] S203: Performing a self-check on a first power-on flag of the first electric drive controller based on a first reference flag stored in the first electric drive controller.

[0059] S204: Performing a self-check on a second power-on flag of the second electric drive controller based on a second reference flag stored in the second electric drive controller.

[0060] S205: After the self-check is passed, the first electric drive controller reads the second power-on flag and performs a mutual check on the second power-on flag based on the first reference flag; the second electric drive controller reads the first power-on flag and performs a mutual check on the first power-on flag based on the second reference flag.

[0061] See also Figure 2 and Figure 3 As shown, the above step S3 specifically includes the following steps:

[0062] S301: After the self-check and the mutual check are passed, a first application ID is configured for the first electric drive controller according to the first power-on flag, and a second application ID is configured for the second electric drive controller according to the second power-on flag.

[0063] Specifically, taking the dual-controller electric drive system as an example, the first electric drive controller is used to control the electric oil pump of the left rear wheel, and the second electric drive controller is used to control the electric oil pump of the right rear wheel. After the electric drive system is assembled, when it is powered on for the first time, the first initial level state of the first configuration pin and the second initial level state of the second configuration pin are cyclically monitored, a first reference flag is set based on the first initial level state, and the first reference flag is stored in the storage module of the first electric drive controller, a second reference flag is set based on the second initial level state, and the second reference flag is stored in the storage module of the second electric drive controller. In each power-on cycle after the first power-on, the power-on states of the first configuration pin and the second configuration pin are cyclically monitored to obtain the first power-on flag of the first electric drive controller and the second power-on flag of the second electric drive controller. The first electric drive controller performs self-verification on the first power-on flag based on the first reference flag stored in the first electric drive controller, reads the second power-on flag at the same time, and performs mutual verification on the second power-on flag based on the first reference flag; the second electric drive controller performs self-verification on the second power-on flag based on the second reference flag stored in the second electric drive controller, reads the first power-on flag at the same time, and performs mutual verification on the first power-on flag based on the second reference flag. When the first reference flag is consistent with the first power-on flag, and the first reference flag is inconsistent with the second power-on flag, and the second reference flag is consistent with the second power-on flag, and the second reference flag is inconsistent with the first power-on flag, the verification passes, and the first application ID is configured for the first electric drive controller according to the first power-on flag, and the second application ID is configured for the second electric drive controller according to the second power-on flag.

[0064] Optionally, when determining the reference flag corresponding to each controller in the multiple controllers according to the initial level data of the configuration pin, the vehicle controller ID configuration method of the present application also includes: configuring the diagnostic IDs of the multiple controllers respectively according to the initial level data; and storing the diagnostic ID and the reference flag in the storage module. The diagnostic ID of the present application can be used for remote flashing. Among them, the storage module is an electrically erasable programmable read-only memory (Electrically Erasable ProgrammableRead Only Memory, referred to as EEPROM). Specifically, see Figure 2 As shown, taking the dual controller as an example, the first electric drive controller is configured with a first diagnostic code according to the first initial level data of the first configuration pin, and the second electric drive controller is configured with a second diagnostic code according to the second initial level data of the second configuration pin.

[0065] Optionally, the vehicle controller ID configuration method of the present application also includes: when the self-check or mutual check fails, the diagnostic ID and the reference flag are cleared, and the diagnostic ID and the reference flag are updated based on the level data of the next power-on cycle. Specifically, when the self-check or mutual check fails, the diagnostic ID and the reference flag stored in the storage module are cleared. In the next power-on cycle, the level data of the configuration pin is read, the diagnostic ID and the reference flag are reassigned according to the level data, and the reassigned diagnostic ID and the reference flag are stored in the storage module. By setting the data update strategy of the storage module, the ID configuration failure caused by the failure of the check is avoided, and the accuracy and practicality of the ID configuration are improved.

[0066] Optionally, the vehicle controller ID configuration method further includes: when any of the self-checks or mutual checks fails, reporting the controller ID abnormality. Specifically, when the reference flag stored in any controller itself does not match its own power-on flag, it is determined that the self-check fails, the part coding fails, and the controller ID abnormality is reported. When the reference flag stored in any controller itself matches the power-on flag of other controllers, it is determined that the mutual check fails, the part coding fails, and the controller ID abnormality is reported.

[0067] Figure 4 This is a flow chart of another vehicle controller ID configuration method provided by the first embodiment of the present invention. Figure 4 As shown, the vehicle controller ID configuration method of the present application also includes:

[0068] S401: Obtain a status sensing fault bit corresponding to each controller in multiple controllers.

[0069] The state-sensing fault bit is a self-test fault bit of the counterpart of each controller (such as an oil pump) regarding the operating state of the controller.

[0070] Optionally, the state-aware fault bit includes at least one of the following: the controller does not respond after power-on, the response does not match the request, or the control effect does not meet expectations. Exemplarily, the response does not match the request includes but is not limited to: the first electric drive controller responds to the cooling and lubrication request of the second electric drive controller, and / or the second electric drive controller responds to the cooling and lubrication request of the first electric drive controller. The control effect that does not meet expectations includes but is not limited to: the cooling and lubrication performance of at least one electric drive controller does not meet expectations.

[0071] S402: Clear the reference flag bit after reporting the controller ID abnormality according to the state sensing fault bit, and update the reference flag bit based on the power-on level data of the next power-on cycle.

[0072] Specifically, during the ID configuration process, the controller simultaneously reads the fault flags related to cooling and lubrication of the counterpart (such as the oil pump), such as no response from the oil pump controller after power-on, the response does not match the request, and the cooling and lubrication effects do not meet expectations, and other faults related to the electric oil pump. When any of the multiple controllers reads the state-sensing fault bit, it reports the ID identification fault. After the controller reports the ID identification fault, the reference flag stored in the storage module is cleared to avoid comparison errors in subsequent comparison processes. By adding a self-check process, a mutual check process, and reading the state-sensing fault bits of the counterpart about the controller during each ID configuration, the problem of loss of lubrication and cooling of the electric drive due to ID configuration errors is avoided, thereby improving driving safety performance.

[0073] Embodiment 2

[0074] According to another aspect of the present invention, a vehicle controller ID verification method is provided, which is applicable to multi-controller ID configuration verification. The vehicle controller includes multiple controllers connected to the same network, and any controller in the multiple controllers is provided with a configuration pin.

[0075] Figure 5 This is a flow chart of a vehicle controller ID verification method provided in Embodiment 2 of the present invention.

[0076] like Figure 5 As shown, the vehicle controller ID verification method includes:

[0077] S501: When the multi-controller is powered on for the first time, the reference flag corresponding to each controller in the multi-controller is determined according to the initial level data of the configuration pin.

[0078] S502: After the power-on cycle of the application layer is started, the power-on flag corresponding to each controller in the multiple controllers is obtained, and the power-on flag is self-checked and mutually checked according to the reference flag corresponding to each controller in the multiple controllers.

[0079] The vehicle controller ID verification method of the present application avoids ID configuration errors caused by only performing ID configuration through high and low level identification by setting self-verification and mutual verification links, thereby improving the reliability of ID configuration results. Optionally, the multi-controller includes a first electric drive controller and a second electric drive controller; wherein the first electric drive controller is provided with a first configuration pin, the first configuration pin is electrically connected to the first output terminal of the power supply; the second electric drive controller is provided with a second configuration pin, the second configuration pin is electrically connected to the second output terminal of the power supply; the first output terminal and the second output terminal have opposite electrical polarities.

[0080] Optionally, a reference flag corresponding to each controller in a plurality of controllers is determined based on the initial level data of the configuration pin, including: cyclically monitoring a first initial level state of a first configuration pin and a second initial level state of a second configuration pin; determining a first reference flag of a first electric drive controller based on the first initial level state; determining a second reference flag of a second electric drive controller based on the second initial level state; wherein the first initial level state and the second initial level state have opposite level polarities.

[0081] Optionally, a power-on flag corresponding to each controller in the multiple controllers is obtained, and the power-on flag is self-checked and mutually checked according to the reference flag corresponding to each controller in the multiple controllers, including: cyclically monitoring the power-on status of the first configuration pin and the second configuration pin; determining the first power-on flag of the first electric drive controller according to the power-on status of the first configuration pin, and determining the second power-on flag of the second electric drive controller according to the power-on status of the second configuration pin; self-checking the first power-on flag based on the first reference flag stored in the first electric drive controller; self-checking the second power-on flag based on the second reference flag stored in the second electric drive controller; after the self-check passes, the first electric drive controller reads the second power-on flag, and mutually checks the second power-on flag based on the first reference flag; the second electric drive controller reads the first power-on flag, and mutually checks the first power-on flag based on the second reference flag.

[0082] Optionally, the vehicle controller ID verification method of the present application also includes: when the self-verification or mutual verification fails, reporting the ID abnormality, clearing the reference flag, and updating the reference flag based on the level data of the next power-on cycle.

[0083] Optionally, the vehicle controller ID verification method of the present application also includes: obtaining the status perception fault bit corresponding to each controller in the multiple controllers; clearing the reference flag bit after reporting the controller ID abnormality according to the status perception fault bit, and updating the reference flag bit based on the power-on level data of the next power-on cycle.

[0084] Optionally, the state-aware fault bit includes at least one of the following: the controller does not respond after power-on, the response does not match the request, or the control effect does not meet expectations.

[0085] Embodiment 3

[0086] Based on any of the above embodiments, embodiment three of the present invention provides a vehicle-mounted controller ID configuration and verification device, which includes multiple controllers connected to the same network, and any of the multiple controllers is provided with a configuration pin. The vehicle-mounted controller ID configuration and verification device of the present application can execute the vehicle-mounted controller ID configuration method provided in the above embodiment one, and the vehicle-mounted controller ID verification method provided in the above embodiment two, and has functional modules and beneficial effects corresponding to the execution method.

[0087] Figure 6 This is a schematic diagram of the structure of a vehicle controller ID configuration and verification device provided by Embodiment 3 of the present invention. Figure 6 As shown, the vehicle-mounted controller ID configuration and verification device of the present application includes: a storage module 101, which is used to store the reference flag corresponding to each controller in the multiple controllers, and the reference flag is determined based on the initial level data of the configuration pin when the multiple controllers are powered on for the first time; a coding verification module 102, which is used to obtain the power-on flag corresponding to each controller in the multiple controllers after the application layer power-on cycle is started, and perform self-verification and mutual verification on the power-on flag according to the reference flag corresponding to each controller in the multiple controllers.

[0088] See also Figure 6 As shown, the vehicle controller ID configuration and verification device also includes: a coding configuration module 103, which is used to configure application IDs for multiple controllers respectively according to the power-on flag bits corresponding to each controller in the multiple controllers after the application layer power-on cycle is started.

[0089] Optionally, the multi-controller includes a first electric drive controller and a second electric drive controller; wherein the first electric drive controller is provided with a first configuration pin, and the first configuration pin is electrically connected to the first output terminal of the power supply; the second electric drive controller is provided with a second configuration pin, and the second configuration pin is electrically connected to the second output terminal of the power supply; the electrical polarity of the first output terminal is opposite to that of the second output terminal.

[0090] Optionally, the reference flag is determined based on the initial level data of the configuration pin when the multiple controllers are powered on for the first time, including: cyclically monitoring a first initial level state of a first configuration pin and a second initial level state of a second configuration pin; determining a first reference flag of the first electric drive controller according to the first initial level state; determining a second reference flag of the second electric drive controller according to the second initial level state; wherein the first initial level state has opposite level polarity to the second initial level state.

[0091] Optionally, the encoding verification module 102 is specifically used to: cyclically monitor the power-on status of the first configuration pin and the second configuration pin; determine the first power-on flag of the first electric drive controller according to the power-on status of the first configuration pin, and determine the second power-on flag of the second electric drive controller according to the power-on status of the second configuration pin; self-check the first power-on flag based on the first reference flag stored in the first electric drive controller; self-check the second power-on flag based on the second reference flag stored in the second electric drive controller; after the self-check passes, the first electric drive controller reads the second power-on flag, and mutually checks the second power-on flag based on the first reference flag; the second electric drive controller reads the first power-on flag, and mutually checks the first power-on flag based on the second reference flag.

[0092] Optionally, the encoding configuration module 103 is specifically configured to: configure a first application ID for the first electric drive controller according to the first power-on flag, and configure a second application ID for the second electric drive controller according to the second power-on flag.

[0093] Optionally, the storage module 101 is further used to store a diagnostic ID, where the diagnostic ID is determined based on initial level data of the configuration pin when the multi-controller is powered on for the first time.

[0094] Optionally, the vehicle controller ID configuration and verification device of the present application is also used to: clear the diagnostic ID and reference flag when self-verification or mutual verification fails, and update the diagnostic ID and reference flag based on the level data of the next power-on cycle.

[0095] Optionally, the storage module 101 is an electrically erasable programmable read-only memory.

[0096] Optionally, the vehicle-mounted controller ID configuration and verification device of the present application is also used to report a controller ID abnormality when any of the self-verification or mutual verification fails.

[0097] Optionally, the vehicle-mounted controller ID configuration and verification device of the present application is also used to: obtain the status perception fault bit corresponding to each controller in the multiple controllers; clear the reference flag bit after reporting the controller ID abnormality according to the status perception fault bit, and update the reference flag bit based on the power-on level data of the next power-on cycle.

[0098] Embodiment 4

[0099] Based on any of the above embodiments, embodiment four of the present invention provides an electronic device, the electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the vehicle controller ID configuration method provided in embodiment one; or, can execute the vehicle controller ID verification method provided in embodiment two.

[0100] Figure 7 A schematic diagram of the structure of an electronic device that can be used to implement the vehicle controller ID configuration and verification method of an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0101] like Figure 7 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage module 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0102] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage module 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0103] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the vehicle controller ID configuration method, or the vehicle controller ID verification method.

[0104] In some embodiments, the above-mentioned vehicle controller ID configuration method, or the vehicle controller ID verification method, can be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage module 18. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the vehicle controller ID configuration method or the vehicle controller ID verification method described above can be executed. Alternatively, in other embodiments, the processor 11 can be configured to execute the above-mentioned vehicle controller ID configuration method or the vehicle controller ID verification method in any other appropriate manner (for example, by means of firmware).

[0105] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0106] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0107] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0108] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0109] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0110] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0111] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0112] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A vehicle controller ID configuration method, characterized in that: The vehicle-mounted controller includes multiple controllers connected to the same network, any of the multiple controllers is provided with a configuration pin, and the method includes: When the multi-controller is powered on for the first time, determining the reference flag corresponding to each controller in the multi-controller according to the initial level data of the configuration pin; After the application layer power-on cycle is started, the power-on flag bit corresponding to each controller in the multiple controllers is obtained, and the power-on flag bit is self-checked and mutually checked according to the reference flag bit corresponding to each controller in the multiple controllers; The multiple controllers are respectively configured with application IDs according to the power-on flag bits corresponding to the respective controllers in the multiple controllers; the application IDs correspond one-to-one to the respective controllers in the multiple controllers.

2. The vehicle controller ID configuration method according to claim 1, characterized in that: The multi-controller includes a first electric drive controller and a second electric drive controller; Wherein, the first electric drive controller is provided with a first configuration pin, and the first configuration pin is electrically connected to a first output terminal of a power supply; The second electric drive controller is provided with a second configuration pin, and the second configuration pin is electrically connected to the second output terminal of the power supply; The first output terminal and the second output terminal have opposite electrical polarities.

3. The vehicle controller ID configuration method according to claim 2, characterized in that: The step of determining the reference flag corresponding to each controller in the multi-controller according to the initial level data of the configuration pin comprises: cyclically monitoring a first initial level state of the first configuration pin and a second initial level state of the second configuration pin; Determining a first reference flag of the first electric drive controller according to the first initial level state; Determine a second reference flag of the second electric drive controller according to the second initial level state; The first initial level state and the second initial level state have opposite level polarities.

4. The vehicle controller ID configuration method according to claim 2, characterized in that: The obtaining of the power-on flag corresponding to each controller in the multiple controllers, and performing self-checking and mutual-checking on the power-on flag according to the reference flag corresponding to each controller in the multiple controllers, comprises: cyclically monitoring the power-on status of the first configuration pin and the second configuration pin; Determining a first power-on flag of the first electric drive controller according to the power-on state of the first configuration pin, and determining a second power-on flag of the second electric drive controller according to the power-on state of the second configuration pin; Performing a self-check on the first power-on flag based on a first reference flag stored in the first electric drive controller; Performing a self-check on the second power-on flag based on a second reference flag stored in the second electric drive controller; After the self-check is passed, the first electric drive controller reads the second power-on flag and performs a mutual check on the second power-on flag based on the first reference flag; the second electric drive controller reads the first power-on flag and performs a mutual check on the first power-on flag based on the second reference flag.

5. The vehicle controller ID configuration method according to claim 4, characterized in that: The configuring application IDs for the multiple controllers respectively according to the power-on flag bits corresponding to the multiple controllers includes: A first application ID is configured for the first electric drive controller according to the first power-on flag, and a second application ID is configured for the second electric drive controller according to the second power-on flag.

6. The vehicle controller ID configuration method according to claim 1, characterized in that: When determining the reference flag corresponding to each controller in the multiple controllers according to the initial level data of the configuration pin, the method includes: According to the initial level data, the multiple controllers are respectively configured with a diagnostic ID; and, The diagnostic ID and the reference flag are stored in a storage module.

7. The vehicle controller ID configuration method according to claim 6, characterized in that: Also includes: When the self-check or the mutual check fails, the diagnosis ID and the reference flag are cleared, and the diagnosis ID and the reference flag are updated based on the level data of the next power-on cycle.

8. The vehicle controller ID configuration method according to claim 6, characterized in that: The storage module is an electrically erasable programmable read-only memory.

9. The vehicle controller ID configuration method according to any one of claims 1 to 8, characterized in that: Also includes: When any one of the self-check or the mutual check fails, a controller ID abnormality is reported.

10. The vehicle controller ID configuration method according to any one of claims 1 to 8, characterized in that: Also includes: Obtaining a state-aware fault bit corresponding to each controller in the multiple controllers; After the controller ID is abnormal according to the state sensing fault bit, the reference flag bit is cleared, and the reference flag bit is updated based on the power-on level data of the next power-on cycle.

11. The vehicle controller ID configuration method according to claim 10, characterized in that: The state-aware fault bit includes at least one of the following: the controller does not respond after power-on, the response does not match the request, or the control effect does not meet expectations.

12. A vehicle controller ID verification method, characterized in that: Applicable to multi-controller ID configuration verification, the vehicle-mounted controller includes multiple controllers connected to the same network, any of the multiple controllers is provided with a configuration pin, and the method includes: When the multi-controller is powered on for the first time, determining the reference flag corresponding to each controller in the multi-controller according to the initial level data of the configuration pin; After the application layer power-on cycle is started, the power-on flag bit corresponding to each controller in the multiple controllers is obtained, and the power-on flag bit is self-checked and mutually checked according to the reference flag bit corresponding to each controller in the multiple controllers.

13. A vehicle controller ID configuration and verification device, characterized in that: The vehicle-mounted controller includes multiple controllers connected to the same network, any of the multiple controllers is provided with a configuration pin, and the device includes: A storage module, used for storing a reference flag corresponding to each controller in the multi-controller, wherein the reference flag is determined based on initial level data of the configuration pin when the multi-controller is powered on for the first time; The coding verification module is used to obtain the power-on flag corresponding to each controller in the multiple controllers after the application layer power-on cycle is started, and perform self-verification and mutual verification on the power-on flag according to the reference flag corresponding to each controller in the multiple controllers.

14. The vehicle controller ID configuration and verification device according to claim 13, characterized in that: Also includes: The coding configuration module is used to configure application IDs for the multiple controllers respectively according to the power-on flag corresponding to each controller in the multiple controllers.

15. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the vehicle controller ID configuration method according to any one of claims 1 to 11; or, The vehicle controller ID verification method according to claim 12 can be executed.

Images