Controller startup method, device, storage medium and electronic device

Abstract

The present disclosure relates to a controller startup method, device, storage medium, and electronic device. The controller startup method includes: after a target system is powered on, detecting a reset voltage of a controller in the target system; and after the reset voltage reaches the controller's operating voltage, detecting a controller fault. This disclosed technical solution can conserve computing power for controller testing, ensuring proper controller operation.

Description

Technical Field

[0001] The present disclosure relates to the field of controller technology, and in particular to a controller method, device, storage medium, and electronic device. Background Art

[0002] A controller is a device that controls the starting, speed regulation, braking, and reversing of a motor by changing the wiring of the main or control circuits and the resistance values ​​in a predetermined sequence. It is the "decision-making body" that issues commands, coordinating and directing the operations of the entire computer system. Therefore, a controller failure is crucial to the proper functioning of the associated control system.

[0003] Currently, controllers must be tested before operation to ensure they are functioning without any faults. In existing solutions, the controller is tested immediately after the system is powered on. However, because the controller's reset voltage has not yet reached its operating voltage, the internal functional modules are not fully activated. This necessitates continuous testing of these modules and repeated fault checks, wasting system computing power. Furthermore, due to this waste of computing power, the software may occasionally misjudge the controller, preventing it from operating or starting properly. Summary of the Invention

[0004] In order to solve the above technical problems, the present disclosure provides a controller startup method, device, storage medium and electronic device to save computing power for controller detection and ensure the normal operation of the controller.

[0005] In a first aspect, the present disclosure provides a controller startup method, comprising:

[0006] After the target system is powered on, detecting a reset voltage of a controller in the target system;

[0007] After the reset voltage reaches the operating voltage of the controller, a fault condition of the controller is detected.

[0008] In some embodiments, the method further comprises:

[0009] When the reset voltage reaches the operating voltage of the controller, entering a controller detection mode;

[0010] After the reset voltage reaches the operating voltage of the controller, detecting a fault condition of the controller includes:

[0011] When the duration of entering the controller detection mode reaches a preset duration, a fault condition of the controller is detected.

[0012] In some embodiments, detecting a fault condition of the controller includes:

[0013] Detect whether each functional module inside the controller is abnormal; if any functional module is abnormal, determine that the controller is faulty; if none of the functional modules are abnormal, determine that the controller is not faulty.

[0014] In some embodiments, detecting whether each functional module within the controller is abnormal includes:

[0015] Obtaining an output code of the controller;

[0016] If the output code matches a preset abnormality code, determining that an abnormality occurs in the functional module corresponding to the preset abnormality code;

[0017] If the output code does not match the preset abnormality code, it is determined that no abnormality occurs in the functional module.

[0018] In some embodiments, the method further comprises:

[0019] If a fault occurs in the controller, a fault code is recorded, or the fault code and the number of faults corresponding to the fault code are recorded.

[0020] In some embodiments, after recording the fault code, or recording the fault code and the number of faults corresponding to the fault code, the method further includes:

[0021] Return to executing the detection of whether each functional module inside the controller is abnormal. When the number of return executions reaches a preset number, or it is determined that the functional module is not abnormal, stop executing the detection of whether each functional module inside the controller is abnormal.

[0022] In some embodiments, the method further comprises:

[0023] If the controller does not fail, the user mode is entered.

[0024] In a second aspect, the present disclosure provides a controller starting device, comprising:

[0025] A voltage detection module, configured to detect a reset voltage of a controller in the target system after the target system is powered on;

[0026] A fault detection module is used to detect a fault condition of the controller after the reset voltage reaches the operating voltage of the controller.

[0027] In a third aspect, the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores a program or instruction, wherein the program or instruction enables a computer to execute the steps of any of the above methods.

[0028] In a fourth aspect, the present disclosure provides an electronic device, including:

[0029] one or more processors;

[0030] a memory for storing one or more programs or instructions;

[0031] The processor is configured to execute the steps of any of the above methods by calling the program or instructions stored in the memory.

[0032] The technical solution provided by the present disclosure has the following advantages compared with the existing technology:

[0033] The present disclosure provides a controller startup method, device, storage medium, and electronic device. After the target system is powered on, the reset voltage of the controller in the target system is first detected. When the reset voltage of the controller in the target system reaches the operating voltage of the controller, the fault condition of the controller is detected. In this way, the fault condition of the controller can be detected while ensuring that all functional modules inside the controller are fully started as much as possible, thereby reducing the number of controller detections and fault judgments, thereby saving system computing power and improving controller detection efficiency. At the same time, saving system computing power can effectively avoid abnormal software judgments and ensure the normal operation of the controller. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0035] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0036] Figure 1 A flowchart of a controller startup method provided in an embodiment of the present disclosure;

[0037] Figure 2 A structural block diagram of a controller starting device provided in an embodiment of the present disclosure;

[0038] Figure 3 A schematic diagram of the hardware structure of the electronic device provided in the present disclosure. DETAILED DESCRIPTION

[0039] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features therein can be combined with each other in the absence of conflict.

[0040] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0041] Figure 1 This is a flowchart of a controller startup method provided by an embodiment of the present disclosure. This method is applicable to the case where a fault detection is performed on a controller in a target system after the target system is powered on, and can be applied to vehicles. In some embodiments, the controller can be a microcontroller (MCU). This method can be executed by a controller detection device, which can be implemented in software and / or hardware. Figure 1 As shown, the method includes the following steps:

[0042] S110 : After the target system is powered on, detecting a reset voltage of a controller in the target system.

[0043] Among them, powering on the target system means that the power supply of the circuit part in the target system starts to supply power. At this time, the reset voltage is applied to the reset end of the controller in the target system, and current flows through the controller. After the target system is powered on, the various functional modules inside the controller are gradually started. After the reset is completed, the reset voltage of the controller reaches the starting voltage or the working voltage, and the controller starts to work. In some embodiments, the target system can be a system on the vehicle that includes a controller, such as a door system (including an electric suction door system and an electric door system, etc.), an air-conditioning system, a seat system, a window system, a throttle system, and a transmission system. Specifically, when the power supply of the target system starts to supply power, the voltage of the reset end of the controller is continuously detected to obtain a real-time reset voltage. In this way, it is possible to determine whether the reset voltage of the controller has reached the voltage required for the normal operation of the controller, that is, the working voltage.

[0044] S120: After the reset voltage reaches the operating voltage of the controller, detect a fault condition of the controller.

[0045] In the embodiment of the present disclosure, the controller can be reset at a low level or at a high level. After the target system is powered on, the reset voltage of the controller gradually approaches its operating voltage. During this process, the functional modules inside the controller gradually start up. When the reset voltage of the controller reaches its operating voltage, the functional modules inside the controller are basically started up. Afterwards, to ensure the normal operation of the controller, the controller is tested to determine whether the controller has a fault. In this way, the controller can be tested for faults after most or all functional modules are started, thereby reducing the number of controller tests. Specifically, after the target system is powered on, the reset voltage detection function is turned on to detect the reset voltage of the controller. When the reset voltage is detected, the reset voltage is compared with the operating voltage of the controller. If the reset voltage is lower than the operating voltage, the reset voltage is continued to be detected until the reset voltage is equal to the operating voltage, and the reset voltage detection is stopped. After that, the fault condition of the controller is detected. It should be noted that the embodiment of the present disclosure can use any current controller fault detection method to detect the fault condition of the controller, and this is not limited.

[0046] Exemplarily, the advantages of the disclosed technical solution over the existing solutions are illustrated by taking the self-priming lock system (i.e., the electric suction door system) as an example. The operating voltage of the controller in the self-priming lock system is 2.7V. In the existing solution, the self-priming lock system detects its controller after it is powered on, and in the process of the reset voltage of the controller rising from 0V to 2.7V, there is always a situation where some functional modules are started and other functional modules are not started. In order to ensure that all functions of the controller are normal, it is necessary to continuously detect the controller to eliminate the misjudgment caused by some functional modules not reaching the starting voltage (not started). Therefore, the existing solution needs to repeatedly detect and judge the controller, which wastes a lot of system computing power. In the disclosed technical solution, after the self-priming lock system is powered on, the reset voltage of the controller is monitored first. After the reset voltage reaches 2.7V (working voltage), the controller is tested. At this time, most of the functional modules in the controller (even if there are functional modules that are not fully started, they will be less than the functional modules that are not started in the existing solution, and only a second verification is required at this time) or all functional modules have been started, thereby reducing the number of controller tests during the use of the self-priming lock system, and even only needing to test the controller once. In this way, the system computing power is greatly reduced.

[0047] In some embodiments, the method further comprises:

[0048] When the reset voltage reaches the operating voltage of the controller, it enters the controller detection mode;

[0049] Accordingly, after the reset voltage reaches the operating voltage of the controller, the fault condition of the controller is detected, including:

[0050] When the time in the controller detection mode reaches a preset time, the controller is detected for fault conditions.

[0051] Entering the controller test mode allows you to test the controller's functionality to ensure that all functions are functioning properly before enabling it to operate normally. The preset duration can be set by the target system or configured by the user to ensure that all functional modules within the controller are fully activated during the test.

[0052] Specifically, when the reset voltage of the controller in the target system reaches the operating voltage, it enters the controller detection mode. At this time, the controller fault detection is not performed. After the controller has been in the controller detection mode for a preset time, the controller fault detection will begin. Therefore, after the controller reaches the operating voltage, the controller fault detection can be performed when all functional modules within the controller are activated. This can, to a certain extent, avoid the situation where the controller fault detection is performed when some functional modules are not activated, which may cause the controller to be mistakenly diagnosed as having a fault.

[0053] In other embodiments, when detecting fault conditions of different controllers, a preset time length can be set according to the specific situation of the controller to ensure that all internal functional modules of the controller that reaches the working voltage are started after the preset time length. This is not elaborated here and is not limited.

[0054] In some embodiments, detecting a fault condition of the controller includes:

[0055] Check whether the functional modules inside the controller are abnormal;

[0056] If any functional module is abnormal, it is determined that the controller is faulty;

[0057] If no abnormality occurs in any functional module, it is determined that the controller is not faulty.

[0058] Exemplarily, the functional modules inside the controller of the self-priming lock system include a clock functional module, a signal sampling functional module, a signal input and output functional module, and a motor control functional module.

[0059] Specifically, when detecting a controller fault, each functional module within the controller is detected. If one or more functional modules within the controller are abnormal, it can be determined that the controller has failed and needs to be repaired or adjusted. If all functional modules within the controller are normal, it can be determined that the controller is not faulty and can operate normally. Therefore, in a self-priming lock system, if the controller fault detection result is that the controller is normal, the normal operation of the controller can be guaranteed.

[0060] In other embodiments, the detection of whether functions within different controllers are abnormal can be determined based on the primary functional modules within the different controllers. For example, if the primary functional module within a controller is normal and a secondary functional module is abnormal, it can be determined that the controller is not faulty. The reliability of the fault detection results for different controllers can be guaranteed, and this is not limited here.

[0061] Based on the above embodiments, in some embodiments, detecting whether each functional module inside the controller is abnormal includes:

[0062] Get the output code of the controller;

[0063] If the output code matches the preset abnormality code, it is determined that the functional module corresponding to the preset abnormality code has an abnormality;

[0064] If the output code does not match the preset abnormality code, it is determined that no abnormality has occurred in the functional module.

[0065] The preset abnormality code may include at least one code for indicating an abnormality of a functional module within the controller. In some embodiments, the preset abnormality code includes multiple codes, and the multiple codes are used to indicate multiple abnormalities of various functional modules within the controller.

[0066] Specifically, during the process of detecting a controller fault, the controller generates and outputs a code representing the working conditions of each functional module, thereby obtaining an output code. The output code is then compared with a preset abnormality code stored in the software. For example, when the preset abnormality code includes multiple codes, the output code can be compared with each of the multiple codes one by one. If the output code and the preset abnormality code are the same, it can be determined that the functional module corresponding to the preset abnormality code with the same output code has an abnormality. If the output code and the preset abnormality code are different, it is determined that the functional module of the controller has no abnormality. Thus, after detecting the fault condition of the controller, the fault of the controller can be clearly understood so that the controller can be repaired or adjusted later.

[0067] It should be noted that the output code obtained can be one segment or multiple segments, depending on the actual fault condition of the controller.

[0068] For example, if the signal sampling module of the controller in a self-priming lock system experiences sampling signal distortion, the obtained output code will contain the same preset exception code. That is, the obtained output code contains the preset exception code corresponding to the sampling signal distortion of the controller signal sampling module. This way, during subsequent controller maintenance, maintenance personnel can use the output code to detect the sampling signal distortion failure of the controller's signal sampling module in the self-priming lock system and take appropriate maintenance measures.

[0069] In other embodiments, methods other than obtaining the output code may be used to determine the functional failure of the controller, as long as the functional failure of the controller can be clearly indicated. This will not be elaborated or limited here.

[0070] In some embodiments, the method further comprises:

[0071] If a fault occurs in the controller, the fault code is recorded, or the fault code and the number of faults corresponding to the fault code are recorded.

[0072] The fault code is the same as the preset abnormal code. You can refer to the preset abnormal code to understand the specific fault situation of the controller.

[0073] Specifically, after a fault occurs in a controller of a self-priming locking system and fault detection is performed, the obtained fault code is recorded, or the obtained fault code and the number of times the fault corresponding to the fault code occurs are recorded. In this way, after a fault occurs in a controller of a self-priming locking system, the specific fault condition of the controller and the number of times the fault occurs can be understood, thereby determining the cause of the controller fault and determining the corresponding maintenance measures.

[0074] In some embodiments, after recording the fault code, or recording the fault code and the number of faults corresponding to the fault code, the method further includes:

[0075] Return to execute to detect whether each functional module inside the controller is abnormal. When the number of return executions reaches a preset number, or it is determined that the functional module has no abnormality, stop executing to detect whether each functional module inside the controller is abnormal.

[0076] The number of times the return execution can be performed is limited. In some embodiments, the return execution operation can be terminated by setting a preset number of times. Alternatively, the return execution operation can be terminated if no abnormality is found in the functional modules within the controller during the re-test. The preset number of times can be set by the user.

[0077] Specifically, if a controller fault occurs during the initial execution of the controller fault detection step, the controller fault detection step can be returned to continue until the number of returns reaches a preset number. This allows the controller fault condition to be accurately determined after repeated controller fault detection, minimizing the possibility of incorrect controller fault detection.

[0078] In some embodiments, the method further comprises:

[0079] If the controller is not faulty, it enters user mode.

[0080] Specifically, if it is determined that the controller has not failed, the user use mode can be entered to perform user operations. For example, when the user closes the car door, the controller of the self-priming lock system performs the door closing function.

[0081] The controller startup method provided by the present disclosure first detects the reset voltage of the controller in the target system after the target system is powered on. When the reset voltage of the controller in the target system reaches the operating voltage of the controller, the controller fault condition is detected. Thus, the controller fault condition can be detected while ensuring that all functional modules within the controller are fully started as much as possible, thereby reducing the number of controller detections and fault diagnosis times, thereby saving system computing power and improving controller detection efficiency. At the same time, the saved system computing power can effectively avoid software judgment anomalies and ensure the normal operation of the controller.

[0082] Corresponding to the controller startup method provided by the embodiment of the present disclosure, the embodiment of the present disclosure also provides a controller startup device. Figure 2 This is a structural block diagram of a controller startup device provided by an embodiment of the present disclosure, such as Figure 2 As shown, the controller starting device includes:

[0083] A voltage detection module 21 is used to detect the reset voltage of the controller in the target system after the target system is powered on;

[0084] The fault detection module 22 is used to detect a fault condition of the controller after the reset voltage reaches the operating voltage of the controller.

[0085] In some embodiments, the fault detection module is specifically configured to:

[0086] When the reset voltage reaches the operating voltage of the controller, it enters the controller detection mode;

[0087] When the time in the controller detection mode reaches a preset time, the controller is detected for fault conditions.

[0088] In some embodiments, the fault detection module is specifically configured to:

[0089] Check whether the functional modules inside the controller are abnormal;

[0090] If any functional module is abnormal, it is determined that the controller is faulty;

[0091] If no abnormality occurs in any functional module, it is determined that the controller is not faulty.

[0092] In some embodiments, the above apparatus further includes a functional abnormality detection module for:

[0093] Get the output code of the controller;

[0094] If the output code matches the preset abnormality code, it is determined that the functional module corresponding to the preset abnormality code has an abnormality;

[0095] If the output code does not match the preset abnormality code, it is determined that no abnormality has occurred in the functional module.

[0096] In some embodiments, the above device further includes a fault recording module for:

[0097] If a fault occurs in the controller, the fault code is recorded, or the fault code and the corresponding fault number are recorded.

[0098] In some embodiments, the above apparatus further includes a return detection module, configured to:

[0099] Return to execute to detect whether each functional module inside the controller is abnormal. When the number of return executions reaches a preset number, or it is determined that the functional module has no abnormality, stop executing to detect whether each functional module inside the controller is abnormal.

[0100] In some embodiments, the above apparatus further includes a mode switching module configured to:

[0101] If the controller is not faulty, it enters user mode.

[0102] The controller startup device disclosed in the above embodiments can execute the controller startup method disclosed in the above embodiments, and has the same or corresponding beneficial effects. To avoid repetition, they will not be described here.

[0103] The present disclosure also provides a computer-readable storage medium, which stores a program or instruction, and the program or instruction enables a computer to execute the steps of any of the above methods.

[0104] Exemplarily, the program or instructions cause a computer to execute a controller startup method, the method comprising:

[0105] After the target system is powered on, the reset voltage of the controller in the target system is detected;

[0106] After the reset voltage reaches the operating voltage of the controller, the fault condition of the controller is detected.

[0107] Optionally, when executed by a computer processor, the computer executable instructions can also be used to execute the technical solutions of any of the above-mentioned controller startup methods provided in the present disclosure to achieve corresponding beneficial effects.

[0108] Through the above description of the implementation methods, those skilled in the art can clearly understand that the present disclosure can be implemented with the help of software and necessary general-purpose hardware, and of course it 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 the present disclosure is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment of the present disclosure.

[0109] The present disclosure also provides an electronic device, comprising: one or more processors; a memory for storing one or more programs or instructions; the processor calls the programs or instructions stored in the memory to execute the steps of any of the above methods to achieve corresponding beneficial effects.

[0110] Figure 3 Schematic diagram of the hardware structure of the electronic device provided by the present disclosure. Figure 3 As shown, the electronic device includes one or more processors 301 and a memory 302 .

[0111] The processor 301 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

[0112] The memory 302 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory (cache), etc. The non-volatile memory may include, for example, read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 301 may execute the program instructions to implement the controller startup method of the embodiment of the present disclosure described above, and / or other desired functions. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage medium.

[0113] In one example, the electronic device may further include: an input device 303 and an output device 304 , and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0114] In addition, the input device 303 may also include, for example, a keyboard, a mouse, and the like.

[0115] The output device 304 can output various information to the outside, including determined distance information, direction information, etc. The output device 304 can include, for example, a display, a speaker, a printer, a communication network and its connected remote output device, etc.

[0116] Of course, to simplify, Figure 3 Only some of the components related to the present disclosure in the electronic device are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, the electronic device may further include any other appropriate components according to specific application scenarios.

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

[0118] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments described herein, but rather to be construed in the broadest manner consistent with the principles and novel features disclosed herein.

Claims

1. A controller startup method, characterized in that: Applied to vehicles, including: After the target system is powered on, detecting a reset voltage of a controller in the target system; After the reset voltage reaches the operating voltage of the controller, detecting a fault condition of the controller; The detecting a fault condition of the controller includes: Check whether each functional module inside the controller is abnormal.

2. The method according to claim 1, characterized in that The method further comprises: When the reset voltage reaches the operating voltage of the controller, entering a controller detection mode; After the reset voltage reaches the operating voltage of the controller, detecting a fault condition of the controller includes: When the duration of entering the controller detection mode reaches a preset duration, a fault condition of the controller is detected.

3. The method according to claim 1, characterized in that After detecting whether each functional module inside the controller is abnormal, the method further includes: If any of the functional modules is abnormal, it is determined that the controller is faulty; If no abnormality occurs in any of the functional modules, it is determined that no fault occurs in the controller.

4. The method according to claim 3, characterized in that The detecting whether each functional module inside the controller is abnormal includes: Obtaining an output code of the controller; If the output code matches a preset abnormality code, determining that an abnormality occurs in the functional module corresponding to the preset abnormality code; If the output code does not match the preset abnormality code, it is determined that no abnormality occurs in the functional module.

5. The method according to claim 3, characterized in that The method further comprises: If a fault occurs in the controller, a fault code is recorded, or the fault code and the number of faults corresponding to the fault code are recorded.

6. The method according to claim 5, characterized in that After recording the fault code, or recording the fault code and the number of faults corresponding to the fault code, the method further includes: Return to executing the detection of whether each functional module inside the controller is abnormal. When the number of return executions reaches a preset number, or it is determined that the functional module is not abnormal, stop executing the detection of whether each functional module inside the controller is abnormal.

7. The method according to claim 1, characterized in that The method further comprises: If the controller does not fail, the user mode is entered.

8. A controller starting device, characterized in that: Applied to vehicles, including: A voltage detection module, configured to detect a reset voltage of a controller in the target system after the target system is powered on; a fault detection module, configured to detect a fault condition of the controller after the reset voltage reaches the operating voltage of the controller; The fault detection module is specifically used to detect whether each functional module inside the controller is abnormal.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a program or instruction, and the program or instruction enables a computer to execute the steps of the method according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: one or more processors; a memory for storing one or more programs or instructions; The processor is configured to execute the steps of the method according to any one of claims 1 to 7 by calling the program or instructions stored in the memory.

Images