Techniques are provided for operating a vehicle in a first vehicle mode; operating at least one component of the vehicle in a first component mode; detecting a first change in operation of the vehicle from the first vehicle mode to a second vehicle mode different from the first vehicle mode; based on the detected the first change in the operation of the vehicle, predicting a second change in operation of the vehicle; in response to predicting the second change in operation of the vehicle, operating the at least one component in a second component mode different from the first component mode prior to the predicted second change in operation of the vehicle.
|
1. A method comprising:
operating a vehicle with an engine of the vehicle in a running state and a battery charging system in an operating state;
operating at least one component of the vehicle in a first component mode, the at least one component operating on a normal voltage supplied by a battery connected to the battery charging system when operating the at least one component in the first component mode;
detecting a first change in operation of the vehicle, the first change in operation of the vehicle comprising the engine of the vehicle transitioning from the running state to a non-running state, the battery charging system being in a non-operating state when operating the vehicle with the engine in the non-running state;
in response to detecting the first change in operation of the vehicle, predicting a second change in operation of the vehicle, the second change in operation of the vehicle comprising a crank event including transitioning the engine of the vehicle from the non-running state to the running state;
in response to predicting the second change in operation of the vehicle, operating the at least one component in a second component mode different from the first component mode, the second component mode enabling the at least one component to continue to function during the crank event based on a low voltage supplied by the battery connected to the battery charging system.
27. A non-transitory computer readable storage medium that stores instructions configured to cause a processing device to:
detect that a vehicle is operating with an engine of the vehicle in a running state and a battery charging system in an operating;
in response to detecting that the vehicle is operating with the engine in the running state, cause at least one component of the vehicle to operate in a first component mode, the at least one component operating on a normal voltage supplied by a battery connected to the battery charging system when operating the at least one component in the first component mode;
detect a first change in operation of the vehicle with the engine transitioning from the running state to a non-running state, the battery charging system being in a non-operating state when operating the vehicle with the engine in the non-running state;
in response to detecting the first change in operation of the vehicle, predict a second change in operation of the vehicle, the second change in operation of the vehicle comprising a crank event including transitioning the engine of the vehicle from the non-running state to the running state;
in response to predicting the second change in operation of the vehicle, cause the at least one component to operate in a second component mode different from the first component mode, the second component mode enabling the at least one component to continue to function during the crank event based on a low voltage supplied by the battery connected to the battery charging system.
17. A system comprising:
a processing device configured to execute a mode selector module, said module configured to:
detect that a vehicle is operating with an engine of the vehicle in a running state and a battery charging system in an operating state;
in response to detecting that the vehicle is operating with the engine in the running state and the battery charging system in an operating state, cause at least one component of the vehicle to operate in a first component mode, the at least one component operating on a normal voltage supplied by a battery connected to the battery charging system when operating the at least one component in the first component mode;
detect a first change in operation of the vehicle with the engine transitioning from the running state to a non-running state, the battery charging system being in a non-operating state when operating the vehicle with the engine in the non-running state;
in response to detecting the first change in operation of the vehicle, predict a second change in operation of the vehicle, the second change in operation of the vehicle comprising a crank event including transitioning the engine of the vehicle from the non-running state to the running state;
in response to predicting the second change in operation of the vehicle, cause the at least one component to operate in a second component mode different from the first component mode, the second component mode enabling the at least one component to continue to function during the crank event based on a low voltage supplied by the battery connected to the battery charging system.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
after the second change in operation of the vehicle, operating the at least one component of the vehicle in the first component mode.
10. The method of
11. The method of
12. The method of
13. The method of
14. The method of
15. The method of
16. The method of
18. The system of
19. The system of
20. The system of
21. The system of
22. The system of
23. The system of
24. The system of
25. The system of
26. The system of
|
This disclosure generally relates to automotive vehicles. More specifically, this disclosure relates to techniques for operating vehicle components.
Techniques are provided for operating a vehicle in a first vehicle mode; operating at least one component of the vehicle in a first component mode; detecting a first change in operation of the vehicle from the first vehicle mode to a second vehicle mode different from the first vehicle mode; based on the detected the first change in the operation of the vehicle, predicting a second change in operation of the vehicle; in response to predicting the second change in operation of the vehicle, operating the at least one component in a second component mode different from the first component mode prior to the predicted second change in operation of the vehicle.
A system is provided that includes a mode selector module, said module configured to detect that a vehicle is operating in a first vehicle mode; in response to detecting that the vehicle is operating in a first vehicle mode, cause at least one component of the vehicle to operate in a first component mode; detect a first change in operation of the vehicle from the first vehicle mode to a second vehicle mode different from the first vehicle mode; in response to detecting the first change in the operation of the vehicle, predict a second change in operation of the vehicle; in response to predicting the second change in operation of the vehicle, cause the at least one component to operate in a second component mode different from the first component mode prior to the predicted second change in operation of the vehicle.
These and other aspects, features, and implementations can be expressed as methods, apparatus, systems, components, program products, means or steps for performing a function, and in other ways.
Further features and advantages will appear more clearly on a reading of the following detailed description of the preferred embodiment, which is given by way of non-limiting example only and with reference to the accompanying drawings.
The present invention will now be described, by way of example with reference to the accompanying drawings, in which:
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. It will be appreciated that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
‘One or more’ includes a function being performed by one element, a function being performed by more than one element, e.g., in a distributed fashion, several functions being performed by one element, several functions being performed by several elements, or any combination of the above.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used in the description of the various described embodiments herein is for describing embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Traditional automotive vehicles are configured such that the car engine runs continually while operated by a driver, until the driver him/herself turns of the vehicle engine. The engine of such a traditional vehicle continues to run even when the vehicle is temporarily stopped moving, for example when the driver stops at a stoplight or stop or stop sign, or stops for any other reason. In some examples, in order to save energy, some modern automotive vehicles have been adapted such that electronics associated with the vehicle detect when the vehicle has stopped moving (e.g., detected vehicle speed or detected actuation of brake pedals), and causes the vehicle engine to shut down temporarily while the vehicle is in a motionless state. Once the vehicle receives an indication that the driver desires to resume travelling with the vehicle (e.g., the brake pedal is released, and/or the accelerator pedal is actuated), the vehicle electronics detect the indication and restart the engine. This allows the user to travel as desired, but minimizes an amount of time that the vehicle engine is running, thereby reducing energy consumption of the vehicle.
In some examples, a vehicle may include one or more components that require a stable power supply in order to function correctly. For example, some electrical components may cease to function altogether if a power supply for the component is drops below a certain voltage or current level. In other examples, an electrical component may be configured to automatically reset, or reboot, should a supply voltage or current drop below a suitable level for operation or a predetermined level. Such components may be operated to reset, or reboot, to ensure longevity and/or consistent operation of the component. As one non-limiting example, a communications device (e.g., a Vehicle to Everything (V2X) communications module) of a vehicle may be configured to reboot in response to a reduced power supply level, to ensure that the drop in power supply level does not damage one or more components of the communications device, such as a memory component.
While automotive vehicles configured to automatically react to stopping of the vehicle by turning off the vehicle engine when the vehicle is stopped advantageously reduce power consumption of the vehicle, restarting a vehicle engine from a stopped state causes a relatively large amount of current to be drawn from the electrical system of the vehicle, and therefore a reduction in voltage level of the power supply used by components of the vehicle. Such a vehicle engine startup is referred to as a “crank event” herein. While some vehicle components may continue to function properly though such a crank event, other vehicle components (as described above), may not continue to function properly, and/or may be configured to automatically restart and/or reboot when the power supply (e.g., voltage level) drops.
To address this issue, some vehicles are designed with dedicated circuitry or other components intended to minimize the impact of a temporary reduction in power supply caused, for example, by a crank event. For example, some automotive vehicles may be equipped with relatively large storage capacitors configured to store electrical charge that may be provided to one or more vehicle components when the vehicle power supply drops. In other examples, automotive vehicles may be equipped with voltage regulation (e.g., linear voltage regulator) and/or power regulation component (e.g., DCDC boost converters) configured to increase a voltage level of a power supplied to a component in response to a detected drop in power supply voltage level. The above-mentioned techniques for addressing power supply voltage drops in vehicles may be undesirable, as they may increase cost, complexity, and flexibility in manufacture of the vehicle.
This disclosure is directed to techniques for improving an ability of automotive vehicle components to withstand the negative effects described above in light of a temporarily reduced power supply, which may be caused, in one example, by a crank event.
In some examples, mode selector module 10 may be part of component 14, may be separate from component 14, or may be part of other electrical or computing systems of the vehicle 12. In any of these cases, mode selector module 10 is configured to receive information indicative of a state of vehicle 18, and based on such information, determine that a crank event is likely to occur in the future. For example, the vehicle may be operated in a first mode, for example a mode in which the vehicle engine is running according to typical operation of the vehicle. At the same time, a component 14 of the vehicle is operated in a first component mode. As a non-limiting example, the component may be a communications device of the vehicle, such as a vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and/or vehicle to everything (V2X) transceiver component. According to this example, the mode selector module 10 may detect that a first change in operation of the vehicle, for example a change from the first vehicle mode where the vehicle engine is running, to a second vehicle mode where the vehicle engine has been stopped. Based on detecting the first change in operation, the mode selector module 10 may predict a second change in operation of the vehicle. In some examples, the second change in operation of the vehicle may be a change from the second vehicle mode (engine stopped), to the first vehicle mode (engine is started). In some examples, the second change in operation of the vehicle may include a crank event, where the vehicle engine is started from a stopped state.
In some examples, predicting the second change in operation of the vehicle includes determining when the second change in operation will occur (e.g., when the vehicle engine will be restarted), and/or a duration of the second change in operation (e.g., where the second change in operation is a crank event, how long the crank event will last).
Based on predicting the second change in operation of the vehicle, mode selector module 10 causes component 14 to operate in a second component mode prior to the predicted second change in operation of the vehicle 12. For example, where the second change in operation of the vehicle is a crank event, mode selector module 10 may cause component 14 to operate in a low power mode where the component consumes less power than in the first component mode. Mode selector module 10 may cause the component to operate in the low power mode throughout a duration of the second change in operation of the vehicle (e.g., throughout a duration of a crank event).
In some examples, mode selector module 10 is configured to send an indication of an anticipated second change in operation of the vehicle to component 14, and component 14 is specifically configured to operate in a low power mode in response to the indication. In other examples, mode selector module 10 is configured to control operation of component 14, for example to control a signal transmission rate of component 14 when component 14 is a transmitter/transceiver device. According to such examples, mode selector module 10 may directly modify operation of component 14 to operate in the low power mode in response to determining a likely crank event.
As used herein, the phrase “low voltage mode” refers to a mode of operation in which the component 14 can continue to function, albeit in some examples with reduced functionality or performance, during a low supply voltage event (which may be caused by, for example, a crank event as described above). In one example, the component 14 is a transmitter or a transceiver that includes a transmitter. While operating with reduced function, the transmitter transmits with lower power and/or transmits with a reduced transmit repetition rate during a crank event. The transmitter consumes power with each communication signal output by the transmitter. In some examples, the transmitter is configurable to operate in a normal mode outputting communications signals at a typical rate. As one non-limiting example, such a normal rate is ten times per second, and the normal power level is one Watt (1 W). According to the techniques described herein, based on predicting a crank event, the transmitter is operated in a low voltage mode, where the transmitter outputs communications signals at a reduced rate relative to the above-described normal rate. For example, the reduced rate is one time per second, instead of 10 times per second. According to this non-limiting example, operating component 14 at such a reduced rate may consume one tenth ( 1/10th) of a Watt, instead of one Watt at the normal rate. In this manner, because the transmitter component 14 consumes less power during the crank event by reducing a data transmission rate of the transmitter component, transmitter component 14 does not automatically reset as a result of the reduction in power supply. As such, functionality provided by component 14 is not unduly disrupted as a result of the temporary reduction in power supply
Examples of a component 14 that may be operated in a low power mode as described herein may include a transmitter or transceiver device configured to enable a vehicle to communicate such as a vehicle to vehicle (V2V) communications device, a vehicle to everything communications device (V2V) and/or vehicle to infrastructure (V2I) communications device. In other examples, component 14 may include other types of communications devices, such as a cellular network transceiver, a Wi-Fi transmitter, or a Bluetooth transmitter. It will be appreciated that the techniques of this disclosure are not limited to any of the above-described communication devices, or any type of devices in general including devices not associated with communications. It will be appreciated that the techniques described herein, which include causing a vehicle component to operate in a low power mode based on predicting a likely crank event, may be applied to any vehicle component for which it is desirable to minimize disruption as a result of a temporary reduction in supply voltage. These techniques may provide benefits by not relying on expensive and/or difficult to implement alternatives, such as the addition of storage capacitors, power regulators, power converters, or other devices or circuitry to minimize the impact of a temporary reduction in power supply.
As discussed above, mode selector module 10 is configured to predict, or anticipate, a likely crank event prior to when it occurs. A crank event occurs when a vehicle engine is started, i.e. when the engine transitions from an off state to an on state.
In some examples, for purposes of saving energy, a vehicle system (e.g., an engine control unit (ECU) of the vehicle 12) is configured to turn off the engine 16 automatically when, or shortly after, the vehicle 12 stops moving, such as when the vehicle 12 has stopped at a traffic signal. The vehicle system may then then automatically restart the engine 16 in response to, for example, releasing the brake pedal, or pressing the accelerator pedal, by an operator of the vehicle 12. If the vehicle 12 is an automated vehicle, i.e. an autonomous or driverless vehicle, the automated controls of the vehicle 12 may control the operation of the brakes and/or accelerator.
In some examples, mode selector module 10 is configured to determine a first change in operation of the vehicle (e.g., when the vehicle engine has been turned off). For example, mode selector module 10 may receive an indication from an engine control unit (ECU) of the vehicle that the vehicle engine has been turned off. In other examples, mode selector module 10 may instead itself determine when the vehicle engine has been turned off, based on data available from other systems of the vehicle. For example, mode selector module 10 may be communicatively coupled to a communications bus (e.g., a controller area network (CAN) bus) via which mode selector module receives data indicating a state of the vehicle or vehicle components. For example, actuation or compression of a brake pedal may provide an indication that the vehicle engine has, or will be, turned off. According to this example, mode selector module 10 may determine, based on brake actuation data transmitted by the brake system of the vehicle via the communications bus of the vehicle, that the brakes have been applied. According to another example, the vehicle engine, or sensors or components associated with the vehicle engine, may output a state indication whether the engine is running or not. Mode selector module 10 may determine, based on such engine state information, that the vehicle engine has been turned off.
If mode selector module 10 detects a first change in operation of the vehicle (e.g., that the vehicle engine has turned off), mode selector module 10 may then attempt to predict when the vehicle engine will again be turned on. In this manner, mode selector module 10 uses the vehicle turn off as a trigger to predict a second change in operation of the vehicle (e.g., an upcoming crank event).
Mode selector module 10 may predict or anticipate a forthcoming crank event based on various information dependent on the driving context in which the vehicle engine was shut off. The techniques described herein are not limited to any particular situation based on specific examples described. As such, any mechanism to anticipate a crank event is within the scope of this disclosure.
In some examples, as described above, a vehicle is configured to automatically shut off the vehicle engine when the vehicle is stopped (e.g., at a stop signal, a stop sign, etc.), and turn on the vehicle engine when the operator (e.g., human or autonomous driver) indicates a desire to again travel with the vehicle (e.g., releases brake pedal or actuates accelerator pedal). In such a scenario, the vehicle operator may likely indicate a desire to again travel with a vehicle previously stopped due to a stop light, when that stop light turns from red to green.
In such circumstances, mode selector module 10 may anticipate or predict a second change in operation of the vehicle (e.g., an upcoming crank event) based on when the traffic light, which caused the vehicle to stop by turning red, will again turn to green, because the vehicle operator will likely seek to again travel with the vehicle when the traffic light turns green. In some examples, mode selector module 10 may predict when the second change in operation of the vehicle will occur based data indicating a light change interval for the traffic light. For example, mode selector module 10 may be configured to access publicly available data provided over a network such as the internet that indicates a light change schedule for the traffic light. Such data may be published by a local traffic authority, or may be included with publicly available digital map data used by navigation systems to, for example, determine a travel time along a defined route. According to other examples, where such data is not readily available, mode selector module 10 may attempt to predict when the light will change by data historically captured by the vehicle itself based on previous encounters with the traffic light, or by multiple vehicles based on previous encounters with the traffic light, where such data is available to mode selector module via a network (e.g., cloud based data). In still other examples, a traffic light is associated with one or more roadside communications module(s) (e.g., V2I module) configured to transmit traffic information to vehicles on a roadway. According to these examples, mode selector module 10 may, via a V2X, V2V, or V2I communications module of the vehicle, or other communications protocols available to the vehicle, to receive data from the roadside communications module and use that data to determine when the traffic light will change from red to green.
In other examples, the mode selector module 10 predicts a second change in operation of the vehicle (e.g., a crank event) based on information from perception sensors (e.g. camera, radar, lidar) on board the vehicle 12 and/or other sensors proximate to the vehicle 12. In one example, the other sensors are mounted on other vehicles and the information is communicated using V2V communications. In another example, the perception sensors are part of infrastructure (e.g. a traffic camera) and the information is communicated using V2I or other communications techniques. In another example, a camera on the vehicle 12 is used by the mode selector module 10 to determine that the brake lights of the forward vehicle have turned off, and uses that information as an indicator that the traffic signal has turned green, i.e. that a crank event is about to occur. In another example, the mode selector module 10 detects that the forward vehicle has begun to move as an indicator that the traffic signal has turned green. A perception sensor on the vehicle 12 may be used to determine that the forward vehicle is moving.
The above paragraphs described on example of how mode selector module 10 may anticipate an upcoming crank event in the scenario where the vehicle stops at a traffic light. Once the mode selector module 10 determines that a crank event is likely to occur, and/or when that crank event is likely to occur, mode selector module 10 causes component 14 to operate in a low power mode prior to the expected crank event. For example, where the component 14 is a transceiver component (e.g., a V2X transceiver), mode selector module 10 may cause the component to operate with a reduced transmission rate, thereby temporarily reducing power consumption of the component 14 for the duration of the crank event. Once the crank event is complete, and the vehicle engine is fully running, mode selector module 10 may cause the component 14 to again operate in a normal state (e.g., when the component is a transceiver component, at a normal transmission frequency).
As described above, mode selector module 10 may anticipate a crank event in scenarios other than a vehicle engine that is stopped at a traffic light. One such example is when a vehicle is stopped due to heavy “stop and go” traffic. According to this example, mode selector module 10 may predict the crank event based one or more perception sensors (camera, radar, lidar, etc.) identifying that brake lights of one or more surrounding vehicles (vehicles on the same or adjacent roadways) have changed (e.g., turned off), or that one or more surrounding vehicles have begun to again travel. In another example, the mode selector module 10 predicts the crank event based on a vehicle-to-vehicle (V2X, V2V, V2I) communication from surrounding vehicles, transportation infrastructure, or other signaling that indicates traffic is or will soon move.
The mode selector module 10 may be implemented via hardware, software, firmware, and the like, or any combination thereof. In cases where mode selector module 10 are implemented in software and/or firmware, the respective modules described herein may comprise program instructions stored in a tangible medium (e.g., short term memory, long term storage, and the like) and executable by one or more processors to implement the functionality described herein. According to examples where mode selector module 10 are implemented in software, the respective modules may comprise separate instructions which may be executed by a single processor device, or multiple discrete processor devices, which may reside in a single location (e.g., within the electrical system of a transport vehicle), or multiple distributed locations communicatively coupled to one another via a network.
As described herein, mode selector module 10 is configured to predict a second change in operation of a vehicle (e.g., an upcoming crank event), and cause component 14 to operate in a low power mode for at least a majority of the duration of the second change in operation of the vehicle. In some examples, mode selector module 10 may be a standalone hardware component, or software executing on a standalone hardware component, that is in communications with component 14 and configured to cause component 14 to operate in the low power mode. In other examples, mode selector module 10 may be implemented as part of other components of the vehicle, such as one or more electronic control systems of the vehicle, for example an engine control unit (ECU) of the vehicle. In still other examples, mode selector module 10 may be part of component 14 itself, either as a standalone component housed within the same housing as component 14, or as software executed on a processor associated with component 14. In some examples, mode selector module 10 is configured to output a signal or flag indicating that component 14 should operate in a low power mode, and component 14 is specifically configured to receive such instructions and control itself to operate in the low power mode. In other examples, mode selector module 10 may be included with, or otherwise capable of, controlling circuitry and/or software capable of directly controlling operation of component 14 (e.g., where component 14 is a transceiver, to control a transmission frequency of the transceiver component).
Based on predicting when the crank event will occur, the mode selector module 10 operates to cause the component 14 to begin operating in the low voltage mode prior to the crank event. For example, where the component 14 is a transceiver component, mode selector module 10 may signal, or otherwise cause the component to operate with a reduced transmission frequency in comparison to normal operation for the component. According to the example of
As shown in
As shown in
The method 100 also includes, based on the detected the first change in the operation of the vehicle 12, predicting a second change in operation of the vehicle. The mode selector module 10 may predict whether the second change in operation of vehicle 12 will occur, and/or when the second change in operation of vehicle 12 will occur (step 140). In one example, the second change in operation of the vehicle includes turning on (i.e. starting) the engine 16.
As shown in
In another example of the method 100, the at least one component of the vehicle is a transmitter device. In this example, operating the at least one component in the first component mode includes at least one of operating the transmitter device at a first transmission power level and operating the transmitter device at a first repetition rate. In one example, the first component mode is defined by the first transmission power level being 1 Watt. In another example, the first component mode is defined by the first repetition rate being 10 transmits per second. In yet another example, the first component mode is defined by both the first transmission power level being 1 Watt and the first repetition rate being 10 transmits per second.
In one example, operating the at least one component in the second component mode includes at least one of operating the transmitter device at a second transmission power level different than the first transmission power level and/or operating the transmitter device at a second repetition rate different than the first repetition rate. In one example, the second component mode is defined by the second transmission power level being 0.1 Watt. In another example, the second component mode is defined by the second repetition rate being 1 transmit per second. In yet another example, the second component mode is defined by both the second transmission power level being 0.1 Watt and the second repetition rate being 1 transmit per second. That is, the second transmission power level is less than the first transmission power level, and/or the second repetition rate is less than the first repetition rate.
In one example of the method 100, the transmitter device is part of one of a vehicle to everything (V2X) transceiver, a vehicle to infrastructure (V2I) transceiver, and a vehicle to vehicle (V2V) transceiver. In other examples, the transmitter device is part of a cellular network transceiver or a Wi-Fi network transceiver.
Operating the transmitter device in the second component mode prior to the predicted second change in operation (e.g. the crank event) allows the transmitter device to continue functioning during the reduction in the voltage level supplied to the transmitter device caused by the predicted second change in operation of the vehicle 12.
The second component mode is used so the component 14 can at least maintain volatile memory and/or maintain minimal operation. As one example, the crank event causes a momentary, typically less than 1 second, reduction in the supply voltage 28 to, for example, 6V from greater than 12V. As used herein, a momentary reduction in the supply voltage 28 is different from a long-term reduction in the supply voltage 28. In one example, a long-term reduction in the supply voltage 28 is defined as the supply voltage 28 being less than 2V for more than 60 seconds.
In some examples, not depicted in
Described herein is a non-tangible computer readable storage medium 36 that stores instructions configured to cause a processing device 34 to: detect that a vehicle 12 is operating in a first vehicle mode; in response to detecting that the vehicle 12 is operating in a first vehicle mode, cause at least one component 14 of the vehicle 12 to operate in a first component mode; detect a first change in operation of the vehicle 12 from the first vehicle mode to a second vehicle mode different from the first vehicle mode; in response to detecting the first change in the operation of the vehicle 12, predict a second change in operation of the vehicle 12; in response to predicting the second change in operation of the vehicle 12, cause the at least one component to operate in a second component mode different from the first component mode prior to the predicted second change in operation of the vehicle 12.
While this invention has been described in terms of the preferred embodiments thereof, it is not intended to be so limited, but rather only to the extent set forth in the claims that follow.
Ruppel, Christopher D., Imboden, David J., Kuhlman, Gregory C., Pande, Amit K.
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
6856654, | Sep 15 1997 | Malikie Innovations Limited | Power supply system for a packet-switched radio transmitter |
7741805, | Aug 14 2007 | GM Global Technology Operations LLC | Method and apparatus for managing power flow of an electric power storage device |
7941110, | Jul 23 2007 | SHENZHEN XINGUODU TECHNOLOGY CO , LTD | RF circuit with control unit to reduce signal power under appropriate conditions |
8032189, | Oct 14 2005 | Malikie Innovations Limited | System and method for managing battery slump during wireless communications using signal triggered voltage monitoring |
8938332, | Sep 11 2013 | Cisco Technology, Inc | Startup control of devices |
20050268632, | |||
20120004996, | |||
20130158838, | |||
20140257637, | |||
20190071067, | |||
20190093581, | |||
20190327580, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Aug 05 2019 | PANDE, AMIT K | Aptiv Technologies Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 050278 | /0674 | |
Aug 06 2019 | RUPPEL, CHRISTOPHER D | Aptiv Technologies Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 050278 | /0674 | |
Aug 26 2019 | KUHLMAN, GREGORY C | Aptiv Technologies Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 050278 | /0674 | |
Aug 27 2019 | IMBODEN, DAVID J | Aptiv Technologies Limited | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 050278 | /0674 | |
Sep 05 2019 | Aptiv Technologies Limited | (assignment on the face of the patent) | / | |||
Aug 18 2023 | Aptiv Technologies Limited | APTIV TECHNOLOGIES 2 S À R L | ENTITY CONVERSION | 066746 | /0001 | |
Oct 05 2023 | APTIV TECHNOLOGIES 2 S À R L | APTIV MANUFACTURING MANAGEMENT SERVICES S À R L | MERGER | 066566 | /0173 | |
Oct 06 2023 | APTIV MANUFACTURING MANAGEMENT SERVICES S À R L | Aptiv Technologies AG | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 066551 | /0219 |
Date | Maintenance Fee Events |
Sep 05 2019 | BIG: Entity status set to Undiscounted (note the period is included in the code). |
Date | Maintenance Schedule |
May 24 2025 | 4 years fee payment window open |
Nov 24 2025 | 6 months grace period start (w surcharge) |
May 24 2026 | patent expiry (for year 4) |
May 24 2028 | 2 years to revive unintentionally abandoned end. (for year 4) |
May 24 2029 | 8 years fee payment window open |
Nov 24 2029 | 6 months grace period start (w surcharge) |
May 24 2030 | patent expiry (for year 8) |
May 24 2032 | 2 years to revive unintentionally abandoned end. (for year 8) |
May 24 2033 | 12 years fee payment window open |
Nov 24 2033 | 6 months grace period start (w surcharge) |
May 24 2034 | patent expiry (for year 12) |
May 24 2036 | 2 years to revive unintentionally abandoned end. (for year 12) |