Vehicle body domain controller and vehicle
By connecting the wake-up pin separately for important wake-up sources and realizing direct response to the wake-up source signal in the vehicle body domain controller, the response problem caused by initialization delay after wake-up in the prior art is solved, and the vehicle's user experience is improved.
Patent Information
- Application Number
- CN202420167415.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-23
- Publication Date
- 2025-02-11
- Estimated Expiration
- 2034-01-23
AI Technical Summary
The existing vehicle body domain controller needs to wait for the initialization to complete after wake-up before collecting the signal from the wake-up source, resulting in the user not waiting for the initialization to be completed when the function is triggered, and it will not be able to respond in time, which will affect the vehicle's user experience.
By connecting a wake-up pin separately for an important wake-up source, the basic chip wake-up controller can identify the wake-up source and send the trigger signal to the controller through the communication interface after wake-up, directly responding to the corresponding wake-up source.
It avoids the problem that the wake-up source needs to be triggered again to respond, improves the vehicle's user experience and ensures that the user-triggered functions can respond in a timely manner.
Smart Images
Figure CN222452152U_ABST
Abstract
Description
Technical Field
[0001] The utility model relates to the technical field of vehicles, and in particular to a vehicle body domain controller and a vehicle. Background Art
[0002] At present, the vehicle body domain controller adopts the SBC (system basic chip, powering the MCU and monitoring the wake-up source) + MCU implementation solution. The wake-up source is connected to the wake-up pin of the SBC, and multiple wake-up sources reuse the same wake-up pin of the SBC. In order to meet the static power consumption requirements of the whole vehicle, the KL30 power supply of the body domain controller MCU is directly cut off when the whole vehicle is in sleep mode. When the wake-up source is triggered, it will interrupt and wake up the SBC, and then the SBC will connect to the KL30 power supply of the MCU, and the MCU will wake up.
[0003] When the body domain controller MCU is dormant, if the user wants to use the vehicle, such as pressing the micro switch on the door to open the door, or pressing the hazard warning light switch to turn on the hazard warning light, the body domain controller MCU needs to be powered by KL30 first, and then wait for the body domain controller MCU to wake up and initialize before collecting the wake-up source status and responding to the function. However, the problem is that if the body domain controller is initialized and then collects the wake-up source signal, if the user is no longer triggering the switch, the function triggered by the user will not respond, causing user complaints and affecting the vehicle's user experience. Summary of the invention
[0004] Based on this, it is necessary to provide a body domain controller and a vehicle to address the above technical problems. An important wake-up source is separately connected to a wake-up pin. After the micro switch is triggered, the basic chip wakes up the controller. The controller can know which wake-up pin is awakened and can respond to the wake-up source corresponding to the wake-up pin. This avoids the need for the wake-up source to be triggered again to respond, avoids user complaints, and effectively improves the vehicle's user experience.
[0005] In a first aspect, a vehicle body domain controller is provided, comprising:
[0006] A basic chip, wherein the basic chip at least comprises a high-level wakeup source interface, a low-level wakeup source interface, a power supply interface and a communication interface, wherein the high-level wakeup source interface is connected to a high-level wakeup source, and the low-level wakeup source interface is connected to a low-level wakeup source;
[0007] A controller, the controller comprising a signal acquisition interface, the signal acquisition interface is connected to the high-level wake-up source and the low-level wake-up source, the controller is respectively connected to the power supply interface and the communication interface of the basic chip,
[0008] Among them, when the controller is in sleep mode, the high-level wake-up source interface of the basic chip wakes up the controller through the power supply interface after receiving the trigger signal of the high-level wake-up source, and sends the trigger signal of the high-level wake-up source to the controller for processing through the communication interface.
[0009] Furthermore, there are one or more high-level wakeup source interfaces, and one or more high-level wakeup source interfaces are connected to one or more high-level wakeup sources in a one-to-one correspondence.
[0010] Furthermore, the high-level wake-up source includes at least a door handle micro switch and a hazard warning light switch.
[0011] Furthermore, the door handle micro switch is connected to a high-level wake-up source interface, and the hazard warning light switch is connected to another high-level wake-up source interface.
[0012] Furthermore, there are one or more low-level wakeup sources, and the one or more low-level wakeup sources are all connected to the low-level wakeup source interface to reuse the low-level wakeup source interface.
[0013] Furthermore, the low-level wake-up source at least includes a passing light switch.
[0014] Furthermore, the communication interface of the basic chip includes an SPI communication interface. After the controller is awakened, the basic chip sends a trigger signal of the high-level wake-up source to the controller through the SPI communication interface.
[0015] Furthermore, the controller includes a timer. After the controller is awakened, the timer starts timing. If the controller does not receive a trigger signal from a high-level wakeup source and / or a low-level wakeup source within a predetermined time, the controller goes into sleep.
[0016] Furthermore, the basic chip includes a system basis chip SBC.
[0017] In a second aspect, a vehicle is provided, comprising: a body domain controller according to the first aspect.
[0018] With the implementation example of the utility model, an important wake-up source (such as a door handle microswitch) is separately connected to a wake-up pin. After the microswitch is triggered, the basic chip wakes up the controller. The controller can know which wake-up pin awakens it and can respond to the wake-up source corresponding to the wake-up pin. This avoids the need for the wake-up source to be triggered again to respond, avoids user complaints, and effectively improves the vehicle usage experience. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Other features, objects and advantages of the present invention will become more apparent by reading the detailed description of non-limiting embodiments made with reference to the following drawings:
[0020] Figure 1 A structural block diagram of a vehicle body domain controller provided by an embodiment of the utility model;
[0021] Figure 2 A schematic diagram of a vehicle body domain controller provided in an embodiment of the utility model. DETAILED DESCRIPTION
[0022] The utility model is further described in detail below in conjunction with the embodiments and drawings. It is understood that the specific embodiments described herein are only used to explain the relevant utility model, rather than to limit the utility model. It is also necessary to explain that, for the convenience of description, only the parts related to the utility model are shown in the drawings.
[0023] It should be noted that, in the absence of conflict, the embodiments of the present invention, that is, the features of the embodiments, can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0024] The body domain controller and the vehicle according to the embodiments of the present utility model are described in detail below with reference to the accompanying drawings.
[0025] Figure 1 FIG. 1 is a structural block diagram of a vehicle body domain controller according to an embodiment of the present utility model. Figure 1 As shown, the vehicle body domain controller according to an embodiment of the utility model includes: a basic chip 110 and a controller 120, wherein:
[0026] The basic chip 110 at least includes a high-level wake-up source interface 111, a low-level wake-up source interface 112, a power supply interface 113 and a communication interface 114, wherein the high-level wake-up source interface 111 is connected to the high-level wake-up source, and the low-level wake-up source interface 112 is connected to the low-level wake-up source. The controller 120 includes a signal acquisition interface 121, wherein the signal acquisition interface 121 is connected to the high-level wake-up source and the low-level wake-up source, and the controller 120 is respectively connected to the power supply interface 113 and the communication interface 114 of the basic chip 110, wherein when the controller 120 is dormant, the high-level wake-up source interface 111 of the basic chip 110 wakes up the controller 120 through the power supply interface 113 after receiving the trigger signal of the high-level wake-up source, and sends the trigger signal of the high-level wake-up source to the controller 120 through the communication interface 114 for processing.
[0027] When the controller 120 is not in sleep mode, the trigger signal of the high-level wakeup source and the trigger signal of the low-level wakeup source can be directly sent to the controller 120 through the signal acquisition interface 121 of the controller 120, so that the controller 120 can respond in time.
[0028] When the controller 120 is in sleep mode, the trigger signal of some high-level wake-up sources will be received by the high-level wake-up source interface 111 of the basic chip 110. After the high-level wake-up source interface 111 of the basic chip 110 receives the trigger signal, the controller 120 can be immediately woken up through the power supply interface 113. After the controller 120 wakes up, the basic chip 110 sends the trigger signal to the controller 120 through the communication interface 114 so that the controller 120 can respond.
[0029] Among them, high-level wake-up sources usually refer to the trigger sources of some important functions, such as: door handle micro switch, hazard warning light switch, etc. Correspondingly, low-level wake-up sources usually refer to the trigger sources of some relatively minor functions, such as: passing light switch, horn switch light.
[0030] In a specific example, there are one or more high-level wakeup source interfaces, and one or more high-level wakeup source interfaces are connected to one or more high-level wakeup sources in a one-to-one correspondence. For example, if there are three high-level wakeup sources, three high-level wakeup source interfaces can be set accordingly, and these three high-level wakeup source interfaces are connected to these three high-level wakeup sources in a one-to-one correspondence.
[0031] like Figure 2 As shown, the basic chip takes the system basic chip SBC as an example, and the controller 120 takes the MCU as an example. When the MUC is in sleep mode, when the SBC receives a trigger signal from a high-level wake-up source, the SBC supplies power to the MCU through the power supply interface 113 to wake up the MUC.
[0032] Assuming that there are two high-level wakeup sources, such as a door handle micro switch and a hazard warning light switch, correspondingly, the basic chip 110 includes two high-level wakeup source interfaces 111, which are recorded as Wakeup1 and Wakeup2. Among them, Wakeup1 is connected to the door handle micro switch, and Wakeup2 is connected to the hazard warning light switch. That is, the door handle micro switch is connected to one high-level wakeup source interface, and the hazard warning light switch is connected to another high-level wakeup source interface.
[0033] There are one or more low-level wakeup sources, and the one or more low-level wakeup sources are connected to the low-level wakeup source interface to reuse the low-level wakeup source interface. Figure 2As shown, the low-level wake-up source includes, for example, a passing light switch and a horn switch light. Taking the two passing light switches and the horn switch light as examples, the two passing light switches and the horn switch light are both connected to a low-level wake-up source interface 112, such as Figure 2 As shown, this low-level wakeup source interface 112 is recorded as Wakeup3, that is, the passing light switch and the horn switch light are both connected to Wakeup3.
[0034] Combination Figure 2 As shown, the communication interface 114 of the basic chip 110 includes an SPI communication interface. After the controller 120 wakes up, the basic chip 110 sends the trigger signal of the high-level wake-up source to the controller 120 through the SPI communication interface. That is, the basic chip 110 and the controller 120 implement SPI communication. After the controller 120 wakes up, the trigger signal of the high-level wake-up source just now is sent to the controller 120 through the SPI communication mode, so that the controller 120 can respond in time.
[0035] In one embodiment of the present invention, the controller 120 includes a timer. After the controller 120 is awakened, the timer counts, and if the controller 120 does not receive a trigger signal from a high-level wakeup source and / or a low-level wakeup source within a predetermined time, the controller 120 goes into sleep mode. The predetermined time is, for example, 5 seconds.
[0036] Combination Figure 1 and Figure 2 As a specific example, when in sleep mode, for important functions that users can achieve by short-touch switches or press-reset switches, such as door handle micro switches or hazard warning light switches, these important wake-up sources are connected to a wake-up pin of the SBC, that is, a high-level wake-up source interface, which does not share the wake-up source interface with other wake-up sources. For example: short-pressing the door handle micro switch to achieve the keyless entry function, the door handle micro switch is connected to a wake-up pin of the SBC.
[0037] The specific implementation process is as follows:
[0038] When the user short presses the door handle micro switch, an interrupt will be triggered to wake up the SBC. After the SBC wakes up, it will power the MCU. After the MCU wakes up, it can obtain the trigger signal of the SBC interrupt wakeup source through SPI communication, that is, obtain the trigger signal of the door handle micro switch, and then execute the function that the wakeup source wants to trigger according to the pre-defined wakeup source. In this way, even if the function trigger switch is no longer triggered after the MCU wakes up, it can ensure that the user's function trigger can be responded to in time.
[0039] For the wakeup source of the secondary function realized by the user through a short touch switch or pressing the reset switch during sleep, considering the limited wakeup pins of the SBC, multiple wakeup sources can share one wakeup pin. After being awakened by the MCU, a reasonable delayed sleep time can be defined to ensure that the user function can be responded to. For example, the user touches the switch again through a short touch or presses the reset switch. At this time, the controller 120 has been awakened, so the trigger signal of the wakeup source can be captured and responded. For example, for the overtaking light switch, the user usually accepts that the first trigger has no response, and then the second trigger function can be responded by the controller 120.
[0040] The specific implementation process is as follows:
[0041] After the user short-turns the overtaking light switch, the switch resets to the initial position. When the overtaking light switch is triggered, an interrupt will be triggered to wake up the SBC. After the SBC wakes up, it supplies power to the MCU. The MCU wake-up initialization is completed. At this time, if the overtaking light switch has been reset, the MCU will not be able to detect that the overtaking light switch is triggered and cannot respond to this function.
[0042] At this time, the MCU can be defined not to enter sleep mode again immediately, but to wait for 5 seconds to see if the user has any next operation. If the user finds that there is no response after the first switch is turned on, he will generally turn it on again. At this time, the MCU can detect that the overtaking light switch is triggered and then execute the corresponding function.
[0043] In the vehicle body domain controller of the embodiment of the utility model, different wake-up sources are connected to different wake-up pins of the SBC. For the more important wake-up sources in the short-touch switch or the reset switch, they are all connected to the wake-up pin of the SBC only, and the wake-up pin is not shared with other wake-up sources. In this way, after the MCU is awakened, even if the switch is not in the triggered state, the MCU can know who awakened it, and then respond to the function triggered by the wake-up source, and respond to user needs in a timely manner.
[0044] However, in the prior art, multiple wake-up sources are connected to the same wake-up pin. In this way, although the SBC can wake up the MCU, the MCU does not know which wake-up source wakes it up. The wake-up source needs to be triggered again after the MCU wakes up, so that the MCU can know the wake-up source that wakes it up and respond to the trigger function. If the wake-up source is not triggered again after the MCU is awakened, the MCU cannot respond. In this case, for important functions implemented by short-touch switches or push-to-reset switches, such as pressing a micro switch to open a car door, it will lead to failure to respond to user needs and user complaints.
[0045] In the present invention, an important wake-up source (such as a door handle micro switch) is separately connected to a wake-up pin. After the micro switch is triggered, the SBC wakes up the MCU. The MCU directly knows that it is awakened by the wake-up pin and can directly respond to the wake-up source corresponding to the wake-up pin. This avoids the problem that the door handle micro switch needs to be triggered again to respond.
[0046] For the secondary functions implemented by short-touch switches or push-to-reset switches, considering that the SBC wake-up pins are limited, multiple wake-up sources can share one wake-up pin, but after being awakened by the MCU, a reasonable delayed sleep time needs to be defined to ensure that it can respond to user functions. However, the user needs to trigger it twice before entering sleep again to capture it. For example, for the overtaking light switch, the user can accept that there is no response on the first trigger, and then the function can respond on the second trigger. It is within the user's tolerance range and will not cause user complaints.
[0047] According to the vehicle body domain controller of the embodiment of the utility model, an important wake-up source (such as a door handle micro switch) is separately connected to a wake-up pin. After the micro switch is triggered, the basic chip wakes up the controller. The controller can know which wake-up pin is awakened and can respond to the wake-up source corresponding to the wake-up pin. This avoids the need for the wake-up source to be triggered again to respond, avoids user complaints, and effectively improves the vehicle usage experience.
[0048] In addition, other structures and functions of the vehicle body domain controller according to the embodiment of the utility model are known to ordinary technicians in the field and will not be described here.
[0049] In one embodiment, a vehicle is provided, including: a body domain controller according to one of the above embodiments. An important wake-up source in the vehicle (such as a door handle micro switch) is connected to a wake-up pin separately. After the micro switch is triggered, the basic chip wakes up the controller. The controller can know which wake-up pin is awakened and can respond to the wake-up source corresponding to the wake-up pin separately, thus avoiding the need for the wake-up source to be triggered again to respond, avoiding user complaints, and effectively improving the vehicle's user experience.
[0050] In addition, other structures and functions of the vehicle according to the embodiment of the utility model are known to ordinary technicians in the field and will not be described in detail here.
[0051] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0052] The above embodiments only express several implementation methods of the utility model, and the descriptions are relatively specific and detailed, but they cannot be understood as limiting the scope of the utility model patent. It should be pointed out that for ordinary technicians in this field, several modifications and improvements can be made without departing from the concept of the utility model, which all belong to the protection scope of the utility model. Therefore, the protection scope of the utility model patent shall be based on the attached claims.
Claims
1. A vehicle body domain controller, characterized in that: include: A basic chip, wherein the basic chip at least comprises a high-level wakeup source interface, a low-level wakeup source interface, a power supply interface and a communication interface, wherein the high-level wakeup source interface is connected to a high-level wakeup source, and the low-level wakeup source interface is connected to a low-level wakeup source; A controller, the controller comprising a signal acquisition interface, the signal acquisition interface is connected to the high-level wake-up source and the low-level wake-up source, the controller is respectively connected to the power supply interface and the communication interface of the basic chip, Among them, when the controller is in sleep mode, the high-level wake-up source interface of the basic chip wakes up the controller through the power supply interface after receiving the trigger signal of the high-level wake-up source, and sends the trigger signal of the high-level wake-up source to the controller for processing through the communication interface.
2. The vehicle body domain controller according to claim 1, characterized in that: The number of the high-level wakeup source interfaces is one or more, and the one or more high-level wakeup source interfaces are connected to the one or more high-level wakeup sources in a one-to-one correspondence.
3. The vehicle body domain controller according to claim 2, characterized in that: The high-level wake-up source includes at least a door handle micro switch and a hazard warning light switch.
4. The vehicle body domain controller according to claim 3, characterized in that: The door handle micro switch is connected to a high-level wake-up source interface, and the hazard warning light switch is connected to another high-level wake-up source interface.
5. The vehicle body domain controller according to claim 1, characterized in that: There are one or more low-level wakeup sources, and the one or more low-level wakeup sources are all connected to the low-level wakeup source interface to reuse the low-level wakeup source interface.
6. The vehicle body domain controller according to claim 5, characterized in that: The low-level wake-up source at least includes a passing light switch.
7. The vehicle body domain controller according to any one of claims 1 to 6, characterized in that: The communication interface of the basic chip includes an SPI communication interface. After the controller wakes up, the basic chip sends a trigger signal of the high-level wake-up source to the controller through the SPI communication interface.
8. The vehicle body domain controller according to claim 1, characterized in that: The controller includes a timer. After the controller is awakened, the timer starts timing. If the controller does not receive a trigger signal from a high-level wakeup source and / or a low-level wakeup source within a predetermined time, the controller goes into sleep.
9. The vehicle body domain controller according to claim 1, characterized in that: The basic chip includes a system basis chip SBC.
10. A vehicle, characterized in that: include: A vehicle body domain controller according to any one of claims 1 to 9.