Patent Application
20230311882
The subject matter disclosed herein relates to one-pedal driving and more particularly relates to assisting a driver with one-pedal driving.
One-pedal driving allows the driver of a regenerative braking vehicle to conveniently control the acceleration and braking of a vehicle with a single pedal. One-pedal driving typically uses a regenerative braking system to slow the vehicle as well as to regenerate electricity, which can be used to recharge the vehicle's regenerative battery system. When one-pedal driving, drivers don't know when to start regenerative braking, which can result in slowing down too soon or too late. Drivers can learn this “skill” at low speeds within a few weeks, but it is very difficult to master one-pedal driving at speeds above 35 mph even after many months of driving.
Apparatuses, methods, systems, and program products are disclosed for assisting a driver with one-pedal driving. An apparatus, in one embodiment, includes a processor in a regenerative braking vehicle that has a one-pedal control and a memory, coupled to the processor, that stores code executable by the processor to detect a change in a driving context, monitor a regenerative battery system of the vehicle, and notify a driver of the vehicle to begin modifying pressure upon the one-pedal control based at least in part upon the change in the driving context and the regenerative battery system.
A method, in one embodiment, includes detecting a change in driving context for a regenerative braking vehicle that has a one-pedal control, monitoring a regenerative battery system of the vehicle, and notifying a driver of the vehicle to begin modifying pressure upon the one-pedal control based at least in part upon the change in the driving context and the regenerative battery system.
A program product, in one embodiment, includes computer readable storage medium that stores code executable by a processor. In one embodiment, the code is executable by the processor to detect a change in a driving context for a regenerative braking vehicle that has a one-pedal control, monitor a regenerative battery system of the vehicle, and notify a driver of the vehicle to begin modifying pressure upon the one-pedal control based at least in part upon the change in the driving context and the regenerative battery system.
A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be limiting of scope, the embodiments will be described and explained with additional specificity and detail using the accompanying drawings, in which:
As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
Many of the functional units described in this specification have been labeled as modules, to emphasize their implementation independence more particularly. For example, a module may be implemented as a hardware circuit comprising custom very large scale integrated (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as a field programmable gate array (“FPGA”), programmable array logic, programmable logic devices or the like.
Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, comprise one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.
Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.
Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
Code for carrying out operations for embodiments may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, R, Java, Java Script, Smalltalk, C++, C sharp, Lisp, Clojure, PHP, or the like, and conventional procedural programming languages, such as the “C” programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
The embodiments may transmit data between electronic devices. The embodiments may further convert the data from a first format to a second format, including converting the data from a non-standard format to a standard format and/or converting the data from the standard format to a non-standard format. The embodiments may modify, update, and/or process the data. The embodiments may store the received, converted, modified, updated, and/or processed data. The embodiments may provide remote access to the data including the updated data. The embodiments may make the data and/or updated data available in real time. The embodiments may generate and transmit a message based on the data and/or updated data in real time. The embodiments may securely communicate encrypted data. The embodiments may organize data for efficient validation. In addition, the embodiments may validate the data in response to an action and/or a lack of an action.
Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise. The term “and/or” indicates embodiments of one or more of the listed elements, with “A and/or B” indicating embodiments of element A alone, element B alone, or elements A and B taken together.
Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.
The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions of the code for implementing the specified logical function(s).
It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
The apparatuses, methods, systems, program products, and their respective embodiments disclosed herein facilitate and assist one-pedal driving. The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
vehicle 102 may be used for the same purposes that combustion engine vehicles are used and may include similar features. For example, in addition to the one-pedal, vehicle 102 may include a mechanical, hydraulic, air, friction or other type of brake system, (e.g., brake calipers, brake pads, rotors, etc.), and a clutch pedal on manual shifted vehicles 102. In many embodiments, as an added safety measure, such braking systems continue to be relied upon for emergency stops and for parking brake purposes. Also, when a driver uses regenerative braking, the brake lights engage just as if the driver were using the mechanical brake system. vehicle 102 may also include gauges, displays, cameras, stereos, speakers, etc., that are typically found on combustion engine vehicles.
In some embodiments, the vehicle 102 may include after-market devices, which are either installed permanently or are readily removable. In certain embodiments, the vehicle 102 may be configured to mount, hold, or otherwise couple to a mobile device (e.g., smart phone or navigation device), which may become part of the computing, communication, navigation, or display device for the vehicle 102. In some embodiments, the smart phone, or other mobile device, may be operably coupled to the vehicle 102 to enable a driver to interact with the smart phone, receive data from the vehicle 102, turn on/off using controls on the vehicle 102, and/or the like. Otherwise, the computing, communication, navigation, or display device may be integrated into the vehicle 102 to form a single unit. The computing device may comprise various processors or processor cores, memory, storage, network connectivity chips, graphics chips, audio chips, and/or the like. The vehicle 102 may be configured to receive or send electronic signals and process data inputs, such as camera inputs and the like.
Some RBV's 102, in one embodiment, implement a one-pedal control 104. The one-pedal control 104 enables the driver to accelerate and decelerate using a single pedal (e.g., accelerator), paddle, lever, or the like. For purposes of this document, “one-pedal control” will be used to refer to any or all of these various implementations. The one-pedal control 104 may be controlled by the driver's hand, foot, etc., which accommodates and facilitates driving for unimpaired and impaired drivers.
In one embodiment, the driver may modify (i.e., release, maintain, or increase) pressure upon the one-pedal control 104, which adjusts a motor torque of the vehicle 102 by dynamically transferring power between an accelerator and a regenerative braking system of the vehicle 102. Drivers may slow the vehicle 102 or even come to a full stop without using a mechanical brake pedal and an associated mechanical braking system (i.e., brake calipers, brake pads, rotors, etc.). Rather, the one-pedal control 104 can conveniently be used to control both positive and negative torque on an electric motor. Positive torque propels (i.e., accelerates) the vehicle 102 and negative torque (braking) slows the vehicle 102. In other words, if the driver applies pressure upon the one-pedal control 104, the vehicle 102 accelerates. If the driver maintains the pressure, the vehicle 102 maintains its acceleration, speed, or “coasts.” If the driver lifts the pressure, the vehicle 102 decelerates. In some embodiments, RBV's 102 may also have a brake pedal (and/or clutch pedal), which would engage an associated mechanical braking system, which can be used in case of emergency stops, for example.
In one embodiment, increasing the negative torque increases the RBV motor's magnetic resistance, which not only slows the RBV's drivetrain, but as previously mentioned, can also be used to convert the vehicle's kinetic energy into electricity, which the vehicle 102 uses to recharge its regenerative battery system 107.
Both acceleration and deceleration may be controlled in gradient levels or ranges of pressure upon the one-pedal control 104. For example, if the driver “floors” the pedal, the vehicle 102 will accelerate at a maximum rate. If the driver reduces pressure upon the pedal to 50% for example, the vehicle 102 may coast, if the driver further releases pressure to 25%, for example, the vehicle 102 may begin slowing, and so on. These percentages may be adjusted to accommodate a driver's personal settings, which may be stored by the driver notification apparatus 106, which is discussed in more detail below.
As discussed above, the one-pedal vehicle 102 may include a single pedal or multiple pedals (e.g., accelerator, brake, clutch, paddle shifter), but getting comfortable with relying upon a single pedal for driving can be challenging, especially for those just learning to drive using a one-pedal vehicle 102. When one-pedal driving, drivers often don't know how and when to start regenerative braking to achieve optimal performance, safety, and proper driving protocol. For example, drivers may slow down too soon or too late, which may be annoying and dangerous for the driver, but may also annoy or endanger surrounding drivers, pedestrians, property, etc. This can also be very inefficient, which can reduce the overall mileage traveled before needing another charge. Drivers must also learn how to judge stopping distances and properly modify pressure on the one-pedal control 104 to come to a slow or stop the vehicle 102 smoothly and consistently. Drivers can often learn these “skills” at low speeds within a few weeks, but it is very difficult to master one-pedal driving at higher speeds (e.g., above 35 mph) even after many months of driving a one-pedal vehicle 102.
The embodiments discussed herein may provide comfort, safety, reassurance, and convenience to drivers of one-pedal vehicles 102 (and less frustration and greater safety for others) and can help train new vehicle 102 drivers to adapt to one-pedal driving more quickly. Other benefits of these embodiments include, but are not limited to, optimizing the maximum travel distance without a recharge through optimal energy conservation, extending the lifetime of the mechanical brake system, providing environmental advantages of less brake dust emission and less frequent energy consumption at recharge, providing smoother and safer slowing and stopping (i.e., less driver error due to overly slow stops or re-accelerating during a stop), and so on.
The system 100, in one embodiment, includes a driver notification apparatus 106. A hardware appliance of the driver notification apparatus 106 may include a power interface, a wired and/or wireless network interface, a wired or wireless sensor interface that attaches to one or more sensors, a wired or wireless interface that attaches to a haptic device, a graphical interface that attaches to a gauge or display (e.g., LED lights), a video interface that attaches to a camera or cameras, and/or a semiconductor integrated circuit device as described below, configured to perform the functions described herein with regard to the driver notification apparatus 106.
The driver notification apparatus 106, in such an embodiment, may include a semiconductor integrated circuit device (e.g., one or more chips, die, or other discrete logic hardware), or the like, such as a field-programmable gate array (“FPGA”) or other programmable logic, firmware for an FPGA or other programmable logic, microcode for execution on a microcontroller, an application-specific integrated circuit (“ASIC”), a processor, a processor core, or the like. In one embodiment, the driver notification apparatus 106 may be mounted on a printed circuit board with one or more electrical lines or connections (e.g., to volatile memory, a non-volatile storage medium, a network interface, a peripheral device, a graphical/display interface, or the like). The hardware appliance may include one or more pins, pads, or other electrical connections configured to send and receive data (e.g., in communication with one or more electrical lines of a printed circuit board or the like), and one or more hardware circuits and/or other electrical circuits configured to perform various functions of the driver notification apparatus 106.
The semiconductor integrated circuit device or other hardware appliance of the driver notification apparatus 106, in certain embodiments, includes and/or is communicatively coupled to one or more volatile memory media, which may include but is not limited to random access memory (“RAM”), dynamic RAM (“DRAM”), cache, or the like. In one embodiment, the semiconductor integrated circuit device or other hardware appliance of the driver notification apparatus 106 includes and/or is communicatively coupled to one or more non-volatile memory media, which may include but is not limited to: NAND flash memory, NOR flash memory, nano random access memory (nano RAM or “NRAM”), nanocrystal wire-based memory, silicon-oxide based sub-10 nanometer process memory, graphene memory, Silicon-Oxide-Nitride-Oxide-Silicon (“SONOS”), resistive RAM (“RRAM”), programmable metallization cell (“PMC”), conductive-bridging RAM (“CBRAM”), magneto-resistive RAM (“MRAM”), dynamic RAM (“DRAM”), phase change RAM (“PRAM” or “PCM”), magnetic storage media (e.g., hard disk, tape), optical storage media, or the like. The driver notification apparatus 106 is described in more detail below with reference to
In general, the driver notification apparatus 106 is configured to notify the driver to modify pressure upon the one-pedal control 104. In one embodiment, the driver notification apparatus 106 is configured to detect a change in a driving context and notify the driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context. In another embodiment, the driver notification apparatus 106 is configured to detect a change in a driving context, monitor a regenerative battery system 107 of the vehicle 102, and notify a driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context and a regenerative battery system 107.
In certain embodiments, the driver notification apparatus 106 is coupled to RBV 106 either by a wired connection (e.g., hardwired, a universal serial bus (“USB”) connection, or other communication bus that is physically attached to the RBV 106) or a wireless connection (e.g., Bluetooth®, Wi-Fi, WAN, or the like). The wireless connection may also employ a Wi-Fi network based on any one of the Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 standards.
Driver notification apparatus 106, in certain embodiments, may notify the driver if a warning or danger threshold is exceeded. Driver notification apparatus 106, in one embodiment, may be configured to calculate this threshold using well known mathematics and physics equations (e.g., v=d/t, velocity=displacement (distance)/time) and data collected from these and similar sensors. Such data may include any one or combination of driving contexts 112 discussed herein.
vehicle 102 may include a regenerative battery system 107. The regenerative battery system 107 may include various battery systems for RBV vehicles 102. For example, many RBV vehicles 102 include banks of Li+ cell batteries in daisy-chained parallel configuration as well as the hardware (e.g., circuitry, components, buses, microcontrollers, and microprocessors) and software modules to control and maintain the battery cells.
One challenge for drivers of RBVs 102, especially drivers inexperienced with driving an vehicle 102, is that the driver of may not know when to modify pressure upon the one-pedal control 104 to control the vehicle's speed properly, nor may the driver know when to modify pressure upon the one-pedal control 104 to efficiently recharge the battery supply of the regenerative battery system 107. It is also unlikely that the driver will know when to modify the one-pedal control 104 to optimize the regenerative aspect of the regenerative braking system 107.
The driver notification apparatus 106 is configured to facilitate one-pedal driving. The driver notification apparatus 106, in one embodiment, monitors the regenerative battery system 107 and assists the driver by maintaining an optimal balanced charge level of the regenerative battery system 107 over the duration of travel. In travel, this can fluctuate based upon a variety of circumstances and conditions. These may include, for example, the duration of travel, the type of travel (e.g., city/open freeway), the ambient temperature, the driver's driving style (e.g., choppy/smooth starts or braking), etc. Temperature extremes, for example, can adversely affect efficiency and optimization. Throughout the driving process, the driver notification apparatus 106 notifies the driver as to the appropriate time to modify pressure upon the one-pedal control 104.
The regenerative battery system 107 is described in more detail below with reference to
The data network 108, in one embodiment, includes a digital communication network that transmits digital communications. The data network 108 may include a wireless network, such as a wireless cellular network, a local wireless network, such as a Wi-Fi network, a Bluetooth® network, a near-field communication (“NFC”) network, an ad hoc network, and/or the like. The data network 108 may include a wide area network (“WAN”), a storage area network (“SAN”), a local area network (“LAN”) (e.g., a home network), an optical fiber network, the internet, or other digital communication network. The data network 108 may include two or more networks. The data network 108 may include one or more servers, routers, switches, and/or other networking equipment. The data network 108 may also include one or more computer readable storage media, such as a hard disk drive, an optical drive, non-volatile memory, RAM, or the like.
In embodiments where the wireless connection is a mobile telephone/cellular network, the network may be configured as a 4G network, a 5G network, a long-term evolution (“LTE”) based network, and/or the like. In such an embodiment, the mobile telephone network may create and manage wireless connections between base access units for the network and user equipment (“UE”) devices for the user. The wireless connection may also employ a Wi-Fi network based on any one of the Institute of Electrical and Electronics Engineers (“IEEE”) 802.11 standards.
The one or more servers 110, in one embodiment, may be embodied as blade servers, mainframe servers, tower servers, rack servers, and/or the like. The one or more servers 110 may be configured as mail servers, web servers, application servers, FTP servers, media servers, data servers, web servers, file servers, virtual servers, and/or the like. The one or more servers 110 may store, transmit, and/or the like content to be presented on the vehicle 102.
The driver notification apparatus 106, in one embodiment, is configured to detect a change in a driving context 112. The driving context 112 may include a wide variety of settings, conditions, or circumstances. A list of some examples of the driving context 112 may include any one or a combination of the following: weather conditions (e.g., ambient temperature (hot/cold), sunshine, fog, rain, snow, sleet, freezing rain, ice); road conditions (e.g., curved, sloped, surface viscosity, potholes, gravel, surface type (e.g., gravel, asphalt); distance to an object in an oncoming path of the vehicle 102, either fixed (stop sign or signal, debris (e.g., downed tree, powerline, any object), stopped or slowing vehicle, emergency lights) or moving (e.g., change in object's velocity—slowing car in front of vehicle 102); signals or data received from an object in an oncoming path of the vehicle 102 via data network 108 and/or server 110 (e.g., velocity change alerts, turning signals, road sign or traffic light notifications, debris notifications); other types of signals or data received via data network 108 and/or server 110 (e.g., artificial intelligence, weather channel updates); input from on-board vehicle 102 devices, modules, apparatuses, or systems (e.g., onboard navigation system; current velocity, weight, stopping force, input from cameras (e.g., brake lights of car ahead of vehicle 102, traffic signal change, emergency lights, driver eye movements)); social media or navigation data received via data network 108 and/or server 110 (e.g., Waze, Google Maps), crowd-sourcing, or other such metrics; driver specific data (e.g., reaction time, customized driver settings or preferences); and so on.
The driver notification apparatus 106, in one embodiment, is configured to notify a driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context 112 and the regenerative battery system 107. To make this determination, the driver notification apparatus 106 analyzes data retrieved from modules that detect changes in driving context 112 as well as data retrieved from monitoring the vehicle's battery system and determines when to notify the driver to speed up or slow down or to maintain speed. Referring back to
The driver notification apparatus 106, in one embodiment, is configured to notify a driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context 112 and the regenerative battery system 107.
Notification or alerts to the driver may be implemented in various ways, including but not limited to visual devices such as gauges, lights, etc., haptic feedback devices located in close contact to the driver, such as on the steering mechanism or pedal, paddle, lever, seat, etc. As discussed further herein, the driver notification apparatus 106 assists the driver by alerting or notifying the driver when to initiate slowing or stopping due to a driving context 112, which, as mentioned above, could include an upcoming traffic light, turn, exit, stop sign, object, vehicle, pedestrian, etc., in its projected route or upcoming path. In some embodiments, the driver notification apparatus 106 is configured to optimize notification to the driver by analyzing data received from the detector module 202 and monitor module 204 as explained in more detail below with respect to these modules.
The detector module 202, in one embodiment, may be integrated with or coupled to a processor and memory and may be configured to detect a change in the driving context 112 relative to a vehicle, such as the vehicle 102 described above with reference to
Driver notification apparatus 106, in the
The detector module 202 may also be configured to use radar (e.g., Doppler radar), which, in contrast to camera and LiDAR, uses radio wave technology, so it can “see” through inclement weather. In some embodiments, the detector module 202 combines different sensor technologies to obtain a clearer view of the oncoming roadway and any potentially dangerous objects within intended path of the vehicle 102.
The driver notification apparatus 106, in one embodiment shown in
The detector module 202, in one embodiment, may include a radar sensor or device. For example, detector module 202 may include a radar device mounted on the vehicle 102. If the oncoming path of the vehicle 102 involved a corner turn with a building blocking the driver's view, for example, the detector module 202 senses objects (e.g., bicycles, people, cars, etc.) approaching that are beyond the driver's view or even other detector systems, such as LiDAR or cameras. The detector module 202 may bounce radio waves off objects like buildings, parked cars, and the like, which waves may then bounce off other objects, and eventually some of those waves bounce back to a detector mounted on the vehicle 102. In one embodiment, the detector transmits the collected data to the detector module 202. The detector module 202 communicates this data to the driver notification apparatus 106. The driver notification apparatus 106 may use the collected data to notify the driver of the upcoming objects within the anticipated route of the vehicle 102.
The detector module 202, in one embodiment, may use various eye tracking algorithms, image processing algorithms, and/or sensors, e.g., cameras, motion sensors, and/or the like. These may be permanently or temporarily mounted to the vehicle 102 may track the driver's eyes to detect how and when the driver's eyes move (e.g., suddenly toward a point in the upcoming path of the vehicle 102, such as a person running into the street or a car slamming on its brakes or an emergency vehicle's siren; or casually in the direction of a point or area in or near the upcoming path such as an intended turn or driveway).
In one embodiment, the detector module 202 may combine various sensors such as LiDAR, radar, and/or the like to detect a change in driving context 112.
The driver notification apparatus 106, in one embodiment, includes a monitor module 204, which is configured to monitor the regenerative battery system 107 of the vehicle 102. The monitor module 204 may have a centralized architecture or a distributed or modular architecture. Monitor module 204 may be connected in series with battery cells in some embodiments and may be connected in parallel in other embodiments.
As explained above, the driver of vehicle 102 may not know how or when to modify pressure upon the one-pedal control 104 to control the vehicle 102 properly, nor may the driver know when to modify pressure upon the one-pedal control 104 to efficiently recharge the regenerative battery system 107. It is also unlikely that the driver will know when to modify the one-pedal control 104 to optimize the regenerative aspect of the regenerative braking system 107.
The monitor module 204, in one embodiment, assists the driver by maintaining an optimal balanced charge level of the regenerative battery system 107 over the duration of travel. The monitor module 204 monitors the regenerative battery system 107. The monitor module 204 may monitor a variety of factors (e.g., battery temperatures, cell voltages, leakage current, etc.) with appropriate control modules, sensors, circuitry, and/or methods. These may include various software and hardware devices such as temperature sensors, voltage regulators, voltage sensors, high-speed buses, and similar circuitry. The monitor module 204 may also be configured monitor proper charge and discharge of the cells, maintain a proper charge level, balance cells, maintain cell health, and control wear leveling of the regenerative battery system 107. In some embodiments, the monitor module 204 may be configured to avoid overvoltage, undervoltage, and excessive leakage current. In some embodiments, the monitor module 204 regulates the amount of current coming into the battery cells for charging and the amount of current going out upon discharge. Monitor module 204 works in conjunction with a motor control module 308, which is described below with regard to
The monitor module 204, in one embodiment, communicates with a processor or microprocessor, which may be included in monitor module 204 or as a separate device. The microprocessor analyzes the data to adjust the regenerative battery system 107. Each millivolt may translate into lost efficiency of the regenerative battery system 107.
Monitor module 204, in one embodiment, is configured to communicate with the driver notification apparatus 106 concerning the status of the regenerative battery system 107. If for example, the regenerative battery system 107 is at or near an optimal level of charge, the monitor module 204 may communicate to the driver notification apparatus 106 that no regenerative power is needed at that moment. In contrast, if the regenerative battery system 107 is below an optimal level of charge, the monitor module 204 may communicate to the driver notification apparatus 106 that regenerative power is needed. The driver notification apparatus 106 is configured to use this information to generate the notification to the driver to modify pressure upon the one-pedal control 104.
The driver notification apparatus 106, in one embodiment, may analyze other information or data (e.g., a change in the driving context 112) to determine an optimal time to notify the driver, however. For example, where the driver releases pressure upon the one-pedal control 104 prematurely or too aggressively in anticipation of a change in driving context 112 (e.g., change to redlight), the driver notification apparatus 106 may use this information to augment the notification to the driver to increase pressure upon the one-pedal control 104. This facilitates inexperienced and even experienced drivers in achieving smooth slowing transitions over the distance d2, in
In certain embodiments, the driver notification apparatus 106 is coupled to RBV 106 either by a wired connection (e.g., hardwired, a universal serial bus (“USB”) connection, or other communication bus that is physically attached to the RBV 106) or a wireless connection (e.g., Bluetooth®, Wi-Fi, WAN, or the like); that attaches to an electronic display device (e.g., a television or monitor using an HDMI port, a DisplayPort port, a Mini DisplayPort port, VGA port, DVI port, or the like); and/or the like. and may also attach to a device such as a laptop computer, a server 110, a tablet computer, a smart phone, a vehicle security system, a router or switch, or the like, A hardware appliance of the driver notification apparatus 106 may include a power interface, a wired and/or wireless network interface, a graphical interface that attaches to a display, and/or a semiconductor integrated circuit device as described below, configured to perform the functions described herein with regard to the driver notification apparatus 106. The displays, for example, may include miniaturized and may include cathode ray tubes (“CRT”), liquid crystal displays (“LCDs”), liquid crystal on silicon (“LCos”), or organic light-emitting diodes (“OLED”).
The apparatus 200, in one embodiment, may include a processor in the vehicle 102 that has the one-pedal control 104 and a memory, coupled to the processor, that stores code executable to detect a change in a driving context 112, monitor a regenerative battery system 107, and notify the driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context 112 and the regenerative battery system 107. In the apparatus 200, in further embodiments, the code is executable by the processor to augment notification to the driver to further modify pressure upon the one-pedal control 104 to optimize battery regeneration. In the apparatus 200, in further embodiments, the code is executable by the processor to notify the driver by haptic feedback. In the apparatus 200, in one embodiment, the code is executable by the processor to notify the driver by a visual display.
In the apparatus 200, in one embodiment, the driving context 112 includes the current velocity of the vehicle 102. In the apparatus 200, in one embodiment, the driving context 112 includes a distance to an object in an oncoming path of the vehicle 102. In the apparatus 200, in a further embodiment, the driving context 112 includes a distance to a moving object in an oncoming path of the vehicle 102. In the apparatus 200, in one embodiment, the driving context 112 includes a weather condition. In the apparatus 200, in one embodiment, the driving context 112 includes a road condition. In the apparatus 200, in one embodiment, the driving context 112 includes a stopping force of the vehicle 102. In the apparatus 200, in one embodiment, the driving context 112 includes a customized driver setting.
In one embodiment, the motor control module 308 is a combination of power devices and embedded micro-computers or micro-processors. Many different configurations are possible depending upon the application and type of vehicle 102.
In one embodiment, motor control module 308 may be integrated into driver notification apparatus 106 or it may be a separate modular unit. In this embodiment, motor control module 308 is part of driver notification apparatus 106.
Motor control module 308 may be coupled to various components within vehicle 102, including for example, the motor, the start/stop button, the one-pedal control 104, forward/reverse controls, the regenerative battery system 107, monitor module 204, and others. As mentioned above, however, the motor control module 308 works in conjunction with the monitor module 204 to ensure that the motor supplies the optimal amount of power to the regenerative braking system 107.
The motor control module 308, in one embodiment, may start/stop the motor, select forward/reverse, control speed, torque, and regenerative braking, and as mentioned above, guard against current or voltage overloads.
In certain embodiments, the method 500 may monitor 504 a regenerative battery system 107 of the vehicle 102. In some embodiments, the method 500 may notify 506 a driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context 112 and the regenerative battery system 107. In some embodiments, the method 500 may alert 506a the driver by haptic feedback. In certain embodiments, the method 500 may alert 506b the driver by visual feedback.
In further embodiments, the method 500 augments 508 notification to the driver to further modify pressure upon the one-pedal control 104 to optimize the regenerative battery system 107. In one embodiment, the detector module 202, the monitor module 204, and the notification module 206 perform the various steps of the method 500.
A method, in one embodiment, includes detecting 402 a change in driving context 112 for a regenerative braking vehicle 102 that has a one-pedal control 104, monitoring a regenerative battery system 107 of the vehicle 102, and notifying a driver of the vehicle 102 to begin modifying pressure upon the one-pedal control 104 based at least in part upon the change in the driving context 112 and the regenerative battery system 107.
A method, in such embodiment further including augmenting notification to the driver to further modify pressure upon the one-pedal control 104 to optimize the regenerative battery system 107. A method in some embodiments, wherein notifying the driver comprises alerting the driver by visual display. A method in certain embodiments, wherein the driving context 112 includes the vehicle's current velocity. A method in some embodiments, wherein the driving context 112 includes a distance to an object in an oncoming path of the vehicle 102. A method in such embodiment, wherein the object is moving.
A method in several embodiments, wherein the driving context 112 includes a weather condition. A method in some embodiments, wherein the driving context 112 includes a road condition.
Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
