Some conventional electric vehicles run on power from lead acid batteries. For these vehicles, operators are able to continue using the vehicles as long as there is sufficient charge available from the lead acid batteries.
To recharge the lead acid batteries of these vehicles, the operators simply connect the lead acid batteries to an external power source (e.g., street power). Once the lead acid batteries have been recharged, the operators are able to return to using the vehicles.
It should be understood that there are deficiencies to the above-described conventional electric vehicles which run on power from lead acid batteries. Along these lines, lead acid batteries are inferior to lithium batteries from certain perspectives. For example, lead acid batteries tend to weigh more, have shorter cycle life, and provide less consistent voltage, among other things.
Unfortunately, it would be unsafe to simply substitute lithium batteries in place of lead acid batteries. For example, if one were to simply replace a lead acid battery with a lithium battery in an electric vehicle, it may be possible to deeply discharge and then recharge the lithium battery. However, recharging a lithium battery that has been over-discharged may make the lithium battery unstable and thus susceptible to a hazardous event.
Improved techniques are directed to electronically controlling electrical access to lithium batteries on utility vehicles. Such techniques provide the ability to automatically disconnect the lithium batteries from loads in response to certain situations such as fault conditions, timeouts, and sleep events. Such operation prevents the lithium batteries from discharging even due to parasitic loads while the utility vehicles are idle. As a result, such operation robustly and reliably prevents the lithium batteries from being recharged after being over-discharged and thus safeguards the lithium batteries against becoming unstable.
One embodiment is directed to a battery management system that controls lithium battery access on a utility vehicle. The battery management system includes a lithium battery interface configured to couple to a lithium battery, a power delivery interface configured to couple to a set of loads of the utility vehicle, and control circuitry coupled with the lithium battery interface and the power delivery interface. The control circuitry is configured to mechanically disconnect the lithium battery interface from the power delivery interface in response to a sleep event. The control circuitry is further configured to, after the lithium battery interface is mechanically disconnected from the power delivery interface, mechanically reconnect the lithium battery interface to the power delivery interface in response to a wakeup event. The control circuitry is configured to, after the lithium battery interface is mechanically reconnected to the power delivery interface, maintain connection between the lithium battery interface and the power delivery interface to convey power from the lithium battery to the set of loads of the utility vehicle through the lithium battery interface and the power delivery interface.
In some arrangements, the control circuitry includes a contactor having source contacts configured to couple to the lithium battery interface, target contacts configured to couple to the power delivery interface, and an electromagnetic actuator, and a wakeup circuit coupled with the electromagnetic actuator of the contactor. The wakeup circuit is configured to (i) actuate the electromagnetic actuator to a first position that connects the source contacts to the target contacts in response to the wakeup event, and (ii) release the electromagnetic actuator to a second position that disconnects the source contacts from the target contacts in response to the sleep event. The second position is different from the first position.
In some arrangements, the wakeup circuit is further configured to release the electromagnetic actuator to the second position that disconnects the source contacts from the target contacts in response to a low capacity event in which the lithium battery has discharged to a predefined low capacity level.
In some arrangements, the wakeup circuit includes a timer which the wakeup circuit is configured to start in response to the wakeup event. In these arrangements, the wakeup circuit is further configured to (i) output an actuation signal to the electromagnetic actuator of the contactor once the timer starts and before the timer expires and (ii) terminate output of the actuation signal to the electromagnetic actuator of the contactor in response to expiration of the timer, the electromagnetic actuator being spring biased from the first position toward the second position to separate the source contacts from the target contacts in response to the wakeup circuit terminating output of the actuation signal.
Another embodiment is directed to a utility vehicle which includes a utility vehicle body, a lithium battery supported by the utility vehicle body, a motor supported by the utility vehicle body, a motor controller coupled with the motor, and a battery management system configured to control lithium battery access on the utility vehicle. The battery management system includes: (i) a lithium battery interface that couples with the lithium battery, (ii) a power delivery interface that couples with the motor controller, and (iii) control circuitry coupled with the lithium battery interface and the power delivery interface. The control circuitry is constructed and arranged to:
Yet another embodiment is directed to a method of controlling lithium battery access in a utility vehicle. The method includes:
Yet another embodiment is directed to a computer program product having at least one non-transitory computer readable medium, the at least one non-transitory computer readable medium having stored thereon a set of instructions to control lithium battery access on a utility vehicle. The set of instructions, when carried out by control circuitry, causes the control circuitry to perform a method of:
Other embodiments are directed to higher and lower level systems, assemblies, apparatus, processing circuits, etc. Some embodiments are directed to various processes, electronic components and circuitry which are involved in controlling electrical access to a lithium battery on a utility vehicle.
This Summary is provided merely for purposes of summarizing some example embodiments so as to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above described example embodiments are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. Other embodiments, aspects, and advantages will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the described embodiments.
The foregoing and other objects, features and advantages will be apparent from the following description of particular embodiments of the present disclosure, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of various embodiments of the present disclosure.
Overview
An improved technique is directed to controlling electrical access to a lithium battery on a utility vehicle. Such a technique provides the ability to automatically disconnect the lithium battery from loads in response to timeout (or sleep) events. Such operation prevents the lithium battery from discharging even due to a parasitic load while the utility vehicle is idle. As a result, such operation robustly and reliably prevents the lithium battery from being recharged after being over-discharged (since the lithium battery is never over-discharged) and thus protects the lithium battery against becoming unstable.
The various individual features of the particular arrangements, configurations, and embodiments disclosed herein can be combined in any desired manner that makes technological sense. Additionally, such features are hereby combined in this manner to form all possible combinations, variants and permutations except to the extent that such combinations, variants and/or permutations have been expressly excluded or are impractical. Support for such combinations, variants and permutations is considered to exist in this document.
The motion control system 26 controls vehicle movement such as drive provided by the set of tires 24, speed control, braking, and so on thus enabling the utility vehicle 20 to perform useful work. The motion control system 26 of the illustrated embodiments includes, among other things, a motor system 30, a lithium battery system 32, and additional components 34 such as a set of user controls 36 (e.g., a foot pedal, a keyed switch, a maintenance switch, etc.) and cabling 38. As will be explained in further detail below, the utility vehicle 20 runs on power from a lithium battery and is equipped with a sleep/wakeup feature that automatically disconnects the lithium battery in response to certain timeout conditions thus preventing the lithium battery from further discharging. Further details will now be provided with reference to
As shown in
The lithium battery system 32 includes a battery management system (BMS) 50 and a lithium battery 52. The BMS 50 controls electrical access to the lithium battery 52. Additionally, as will be explained in further detail shortly, the BMS 50 responds to various events such as sleep events (e.g., timeouts) to prevent excessive discharging of the lithium battery 52 thus safeguarding the lithium battery 52 from becoming over discharged. The BMS 50 responds to other events as well such as wakeup events (e.g., actuation of the user controls 36), charging situations, fault conditions, and so on to properly and safely control charging and discharging of the lithium battery 52.
It should be understood that a variety of form factors are suitable for the lithium battery 52. For example, the lithium battery 52 may include multiple lithium battery cells, a single battery pack, combinations thereof, and so on.
The additional components 34 may, for example, include the set of user controls 36 (e.g., pedals, switches, etc.), the cabling 38, a charging receptacle 60, and perhaps other electrical components 62 (e.g., lights, a global positioning system (GPS), specialized equipment, etc.). In some arrangements, the cabling 38 includes a communications bus, such as, for example, a controller area network (CAN) bus through which the motor system 30 and the lithium battery system 32 exchange communications 70 such as electronic CAN messages in accordance with the CAN protocol.
As shown in
The power delivery interface 100 couples with the motor system 30. Similarly, the lithium battery interface 102 couples with the lithium battery 52. The wakeup circuit 104 controls closing and opening of the contactor 106 to electrically connect the motor system 30 to the lithium battery 52 and disconnect the motor system 30 from the lithium battery 52, respectively. During such operation, the charge regulation circuit 108 controls signal conditioning during discharging and charging of the lithium battery 52.
As further shown in
The wakeup circuit 104 includes control logic 130 and a timer 132 which operate to manage access to the lithium battery 52. As will be explained in further detail shortly, such operation may be based on a variety of inputs 134 from the motor system 30, from the user controls 36 (directly or indirectly), and so on. Along these lines, in response to a wakeup event (e.g., a user turning on the BMS 50), the wakeup circuit 104 outputs an actuator signal 136 that actuates the electromagnetic actuator 124 in a first direction 140 from a first position to a second position that connects respective source contacts 122 to corresponding target contacts 120 to electrically connect the motor system 30 to the lithium battery 52. Along these lines, the electromagnetic actuator 124 may be provisioned with a solenoid or coil that closes the contactor 106 in response to the actuator signal 136.
Additionally, in response to a sleep event (e.g., encountering a predefined time period of non-use while the BMS 50 is awake), the wakeup circuit 104 terminates output of the actuator signal 136 which releases the electromagnetic actuator 124. In particular, the electromagnetic actuator 124 is spring biased in a second direction 142 which is opposite the first direction 140. Accordingly, termination of the actuator signal 136 enables the electromagnetic actuator 124 to return back from the second position to the first position thus automatically separating the source contacts 122 from the target contacts 120 when the wakeup circuit 104 terminates output of the actuation signal 136 thus disconnecting the motor system 30 from the lithium battery 52. As a result, there are no parasitic loads placed on the lithium battery 52 that could otherwise further discharge the lithium battery 52 to an over-depleted state.
In other embodiments, the wakeup circuit 104 does not need to constantly maintain the actuator signal 136. Instead, the wakeup circuit 104 controls engagement and disengagement of the contactor 106 using discrete engagement and disengagement signals. With such use of a dedicated release signal, maintenance of a signal and termination for release is not required.
Wakeup/Sleep
As shown in
The communications interface 202 is constructed and arranged to connect the wakeup circuitry 200 to one or more communications media such as a controller area network (CAN) bus (also see the cabling 38 in
The memory 204 stores a variety of memory constructs 220 including an operating system 222, specialized battery management code 224, configuration data 226 (e.g., identification data, predefined timeout settings, charging settings, version data, model data, etc.), and other software constructs, code and data 228 (e.g., activity/event logs, utilities, tools, etc.). Although the memory 204 is illustrated as a single block in
The processing circuitry 206 is configured to run in accordance with instructions of the various memory constructs 220 stored in the memory 204. In particular, the processing circuitry 206 runs the operating system 222 to manage various computerized resources (e.g., processor cycles, memory allocation, etc.). Additionally, the processing circuitry 206 runs the specialized battery management code 224 to electronically control access to the lithium battery 52 (
The additional circuitry 208 represents other circuitry of the wakeup circuitry 200. Such circuitry may include hardware counters, signal drivers, connectors, sensors, and so on. In some arrangements, where the utility vehicle is specialized equipment (e.g., a food and beverage vehicle, an ATV, etc.) the additional circuitry 208 may represent other components such as an electronic thermostat, lighting control, and so on.
With reference to
With reference to
In some embodiments, the park brake release switch 290 is formed by an actual physical switching device that a user can move to different positions. In other embodiments, the park brake release switch 290 is formed by a set of jumpers (e.g., connectors, cables, etc.) that are switchable or arrangeable into different connecting configurations (e.g., a normal configuration, a tow configuration, etc.).
It should be understood that the control logic 130 and the timer 132 of the wakeup circuit 104 (
During operation, the wakeup circuit 104 monitors operation of the user controls 36 to determine whether to electrically connect the lithium battery 52 to the motor system 30 or electrically disconnect the lithium battery 52 from the motor system 30. For example, suppose that a human operator (or user) wishes to operate the utility vehicle 20 after an extended period of non-use such as a 24-hour period. In such a situation, the utility vehicle 20 is initially in a sleep (or unawake) mode or state in which the wakeup circuit 104 (
Further details of wakeup/sleep operation will now be provided with reference to some embodiments in connection with
At this time and in accordance with some embodiments, both the BMS 50 and the motor system 30 perform various self-tests. For example, the BMS 50 checks the amount of charge remaining in the lithium battery 52 and, if the amount of charge is below a predefined minimum charge threshold, the BMS 50 terminates (e.g., immediately terminates) the actuation signal 136 to electrically disconnect the lithium battery 52 from the motor system 30. Such operation prevents the lithium battery 52 from becoming over-discharged. It should be understood that, while the BMS 50 remains awake, the BMS 50 continues to monitor charge remaining in the lithium battery 52 and terminates the actuation signal 136 to disconnect the lithium battery 52 from the motor system 30 if the remaining charge reaches (or falls below) the predefined minimum charge threshold to safeguard the battery against becoming over-discharged. In particular, there is still safety margin between the predefined minimum charge threshold and an over-discharged level.
In some embodiments, after passing their respective self-tests, the BMS 50 and the motor system 30 communicate with each other (e.g., exchange communications 70 such as CAN messages) to verify configuration information (e.g., model numbers, versions, status, etc.). In some arrangements, the motor system 30 may be one of multiple models and the wakeup circuit 104 operates using different configuration settings depending on the particular model identified via communications with the motor system 30.
Also, at this time, the control logic 130 of the wakeup circuit 104 starts the timer 132 (
However, after BMS 50 has woken up, suppose that the user inserts a physical key into the keyed switch 270 and moves the keyed switch 270 from the OFF position to the ON position before the timer 132 reaches the predefined idle time threshold. In response to this sensed user activity, the control logic 130 restarts the timer 132 to the initial time value. Accordingly, the timer 132 is prevented from reaching the predefined idle time threshold and expiring.
Likewise, suppose that the user actuates the accelerator pedal 280 (e.g., moves the pedal 280 from its non-depressed position) before the timer 132 reaches the predefined idle time threshold. In response to this sensed user activity, the control logic 130 restarts the timer 132 to the initial time value. Again, the timer 132 is prevented from reaching the predefined idle time threshold and expiring. It should be understood that moving the accelerator pedal 280 may further signal the motor system 30 to operate the motor 42 (e.g., rotate the motor 42 in a particular direction and at a particular speed based on other factors).
However, if the user leaves the utility vehicle 20 unattended and the timer 132 expires by reaching the predefined idle time threshold, the timer 132 expires (a sleep event) and sends a sleep event signal to the control logic 130. In response to the sleep event signal, the control logic 130 terminates output of the actuation signal 136 thus opening the contactor 106 to disconnect the lithium battery 52 from the motor system 30 (
In accordance with some embodiments, if the BMS 50 has fallen asleep and the maintenance switch 260 (
In some embodiments and with reference to
Similarly, when the keyed switch 270 is in the OFF position, the accelerator pedal 280 is unable to provide input to the control logic 130 of the wakeup circuit 104. Accordingly, the user cannot wake up the BMS 50 simply by pushing on the accelerator pedal 280 while the keyed switch 270 is in the OFF position.
In some embodiments, while the maintenance switch 260 is in the ON position and the BMS 50 is awake, the motor system 30 and the BMS 50 operate to provide a walkaway protection feature that prevents the utility vehicle 20 from inadvertently rolling away at a high rate of speed. Along these lines, suppose that the user forgets to mechanically engage a brake to hold the utility vehicle 20 in place. If the utility vehicle 20 is perched on a hill and begins to roll, the motor system 30 senses that the utility vehicle 20 is moving but that the user is not pressing on the accelerator pedal 280. Accordingly, the motor system 30 of such embodiments provides proactive speed control and regenerative power. The proactive speed control maintains motor rotation at a low speed thus enabling the user to walk up to and stop the utility vehicle 20. Furthermore, the regenerative power recharges the lithium battery 52 thus improving efficiency.
Charging
As further shown in
While the lithium battery 52 charges in response to receipt of the charge signal 340 and in accordance with some embodiments, the BMS 50 monitors the lithium battery 52 to prevent overcharging. In particular, in response to sensing that the lithium battery 52 has charged to a predefined maximum charge threshold (or level), the BMS 50 deactivates the charge regulation circuit 108, e.g., sets the duty cycle of pulse width modulation (PWM) circuitry back to 0%, where other pulse widths determine different charging rates. In some arrangements, the BMS 50 then immediately goes to sleep. In other arrangements, the BMS imposes a timeout (e.g., 30 minutes) and goes to sleep if the timeout period expires without further user activity.
Further Details
At 402, the BMS 50 mechanically disconnects a lithium battery interface from a power delivery interface in response to a sleep event. The lithium battery interface couples with a lithium battery supported by the utility vehicle, and the power delivery interface couples with a set of loads of the utility vehicle. For example, a timer of the wakeup circuit may expire after a period of non-use thus indicating that the BMS 50 may disconnect the lithium battery 52 without interfering with a user of the utility vehicle 20. Such disconnection prevents parasitic loads from further draining the lithium battery 52.
At 404, after the lithium battery interface is mechanically disconnected from the power delivery interface, the BMS 50 mechanically reconnects the lithium battery interface to the power delivery interface in response to a wakeup event. For example, in accordance with some embodiments and in response to certain conditions, the user may press an accelerator pedal or cycle a keyed switch to wakeup the BMS 50.
At 406, after the lithium battery interface is mechanically reconnected to the power delivery interface, the BMS 50 maintains connection between the lithium battery interface and the power delivery interface to convey power from the lithium battery 52 to the set of loads of the utility vehicle through the lithium battery interface and the power delivery interface. In particular, the BMS 50 may start a timer to measure a period of non-use and maintain lithium battery access as long as the timer does not expire and as long as the lithium battery does not discharge below a predefined safe level.
As described above, improved techniques are directed to controlling electrical access to lithium batteries 52 on utility vehicles 20. Such techniques provide the ability to automatically disconnect the lithium batteries 52 from loads in response to timeout or sleep events. Such operation prevents the lithium batteries 52 from discharging even due to parasitic loads while the utility vehicles 20 are idle. Accordingly, the lithium batteries 52 will not discharge to unnecessarily low levels (e.g., safeguard levels). As a result, such operation robustly and reliably prevents the lithium batteries 52 from being recharged after being over-discharged and thus safeguards the lithium batteries 52 against becoming unstable.
While various embodiments of the present disclosure have been particularly shown and described, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims.
In accordance with some arrangements and as disclosed above, it should be understood that the BMS 50 has the ability to disconnect the lithium battery 52 from loads if unsafe conditions are sensed. The disconnect mechanism is the contactor 106 which consumes energy when engaged. To conserve energy, the BMS 50 disconnects the lithium battery 52 after some timeout period. A wakeup signal is required to reconnect the lithium battery 52 for charging and normal use. That is, the lithium vehicle control system wakeups the BMS 50 to use the utility vehicle 20. Such a wakeup is accomplished without additional operator input.
In some embodiments, the BMS 50 and motor controller 40 routinely communicate (e.g., over the CAN bus). Accordingly, the BMS 50 understands the current status of the motor controller 40 and vice versa. Additionally, as mentioned earlier, the BMS 50 monitors the status of a variety of switch inputs, e.g., a maintenance switch, a keyed switch, a pedal switch, etc.
During operation, the BMS 50 disconnects itself from all electrical loads on the utility vehicle 20 by opening its contactor 106. Events that cause the BMS 50 to close its contactor 106 may be referred to as wakeup events, or simply wakeups. The BMS 50 of some embodiments includes multiple inputs for wakeup signals. Along these lines, users may expect the utility vehicle 20 to go when the key is on and the pedal is pressed—whether the utility vehicle 20 has sat for a long time or not. Accordingly, the maintenance switch, the keyed switch, and the throttle pedal switch are all capable of waking up the BMS 50 of some embodiments.
When the keyed switch is in the OFF position, the motor controller 40 of some embodiments provides a walkaway feature while the BMS 50 remains awake. This walkaway feature prevents the utility vehicle 20, if unattended, from rolling down a slope rapidly. When walkaway protection is active, the motor controller 40 senses vehicle movement and causes the motor 42 to apply braking torque. This walkway protection lasts until the BMS 50 eventually times out (e.g., after 12 hours).
In embodiments including a maintenance switch, the maintenance switch is configured to interrupt power to the motor controller 42 to disable the walkaway feature and enable towing. For example, in some embodiments, the maintenance switch is wired in series with the keyed switch and pedal. Accordingly, the maintenance switch interrupts a wakeup signal to the BMS 50, and interrupts power to the other wakeup switches, thereby preventing the keyed and pedal switches from waking up the BMS 50 while the utility vehicle is in tow mode. Otherwise, cycling the keyed switch wakes up a BMS 50 that was asleep with the maintenance switch closed in the ON position. Likewise, pressing the pedal wakes up a BMS 50 that was asleep with the key in the ON position.
In some embodiments, the same BMS 50 may support operation of different types of motor controllers 40. To this end, the motor controller 40 of some embodiments sends a message (e.g., a CAN message) to the BMS 50 that includes controller type. Upon receipt, the BMS 50 of some embodiments stores the controller type in non-volatile memory. The BMS 50 uses the controller type to determine timeout values, and responses to wakeup signals. The first time the BMS 50 is connected to a different type motor controller 40, the BMS 50 may not wakeup exactly as desired. To minimize the differences between wakeup protocols, wakeup signals may be re-assigned. For example, the BMS' first wakeup signal may be connected to the keyed switch on for a first controller type, and the maintenance switch on a second controller type. Similarly, the second wakeup signal may be connected to the throttle pedal for the first controller type and the keyed switch for the second controller type. Furthermore, the third wakeup signal may be connected to the park brake release connectors for the first controller type and the throttle pedal switch for the second controller type. These input assignments minimize the logic differences between wakeup. The most common wakeup methods of turning on the first controller type key switch and the second controller type maintenance switch will work properly regardless of the vehicle type memorized by the BMS 50. As long as this wakeup happens once, the BMS 50 will continue to wakeup and sleep properly until it is transferred to another utility vehicle 20 that uses the other controller type.
When the charger is plugged into the utility vehicle 20, charging initiates regardless of whether the BMS 50 is asleep or awake. If the BMS 50 is awake, plugging in the charger asserts a charger interlock signal from the charge receptacle to the motor controller 40. The motor controller 40 may be configured to send a signal to the BMS 50 informing the BMS 50 that the charger is plugged in. For example, in some embodiments, the motor controller 40 may inform the BMS 50 that the charger is plugged in via a status bit in a message, such as a CAN message.
The BMS 50, in some embodiments, may be configured in response to the signal from the motor controller 40 to activate a charging mode. In these embodiments, the BMS 50 then sets a signal (e.g., a PWM signal) appropriately (when not charging, the BMS 50 sets the PWM signal to a fault mode as a failsafe). Charging can then take place. The BMS 50 stays awake until charging is complete, and goes to sleep shortly after charging is complete.
In some embodiments, if the charger is plugged into a utility vehicle 20 where the BMS 50 is asleep, then the charger provides power to the vehicle's electrical system. This wakes up the BMS 50 and motor controller 40. If the BMS 50 receives a communication (e.g., a CAN message) from the motor controller 40 with the charging status bit set, then it will close its contactor 106 and set the signal (e.g., the PWM signal) appropriately. Charging then commences.
Additionally, it should be understood that the keyed switch was described above as being used in certain example embodiments. It will be appreciated that the keyed switch is just one example of an ignition switch that may be used in various embodiments. For example, in other example embodiments, the vehicle uses a keyless, push-button ignition rather than a keyed switch. Such ignition is enabled when an “electronic key” (e.g., an RF device) on the passenger's person is within range of a wireless sensor of the vehicle. Here, an actuation of the switch occurs through presence of the electronic key in combination with physical actuation of the button.
Furthermore, in some embodiments, the BMS 50 utilizes an inactivity timer that measures inactivity time based on current (also see the timer 132 in
This application is a continuation of U.S. application Ser. No. 16/713,554 having a filing date of Dec. 13, 2019, and having “Controlling Electrical Access to a Lithium Battery on a Utility Vehicle” as a title, the contents and teachings of which are herein incorporated by reference in their entirety. This application is related to U.S. application Ser. No. 16/407,329 having a filing date of May 9, 2019, and having “Controlling Electrical Access to a Lithium Battery on a Utility Vehicle” as a title, the contents and teachings of which are herein incorporated by reference in their entirety. This application is also related to U.S. application Ser. No. 15/395,245 having a filing date of Dec. 30, 2016, and having “Controlling Electrical Access to a Lithium Battery on a Utility Vehicle” as a title, the contents and teachings of which are herein incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3767966 | Bell | Oct 1973 | A |
5089762 | Sloan | Feb 1992 | A |
5332958 | Sloan | Jul 1994 | A |
5343137 | Kitaoka et al. | Aug 1994 | A |
5431607 | Alder | Jul 1995 | A |
5433512 | Aoki | Jul 1995 | A |
5467275 | Takamoto | Nov 1995 | A |
5686819 | Iwatani et al. | Nov 1997 | A |
5713939 | Nedungadi et al. | Feb 1998 | A |
5934051 | Hahn | Aug 1999 | A |
5936317 | Sasanouchi et al. | Aug 1999 | A |
5980420 | Sakamoto | Nov 1999 | A |
RE36454 | Ball | Dec 1999 | E |
6097112 | Kondo | Aug 2000 | A |
6109009 | Benson | Aug 2000 | A |
6198955 | Axelgaard et al. | Mar 2001 | B1 |
6260934 | Lee | Jul 2001 | B1 |
6328672 | Eguchi | Dec 2001 | B1 |
6339916 | Benson | Jan 2002 | B1 |
6346064 | Hada | Feb 2002 | B1 |
6358182 | Eguchi | Mar 2002 | B1 |
6593845 | Friedman et al. | Jul 2003 | B1 |
6616573 | Mcleod et al. | Sep 2003 | B2 |
6625553 | Modgil | Sep 2003 | B1 |
6885535 | Hummert et al. | Apr 2005 | B2 |
7032697 | Lee | Apr 2006 | B2 |
7332881 | Clark et al. | Feb 2008 | B2 |
7471064 | Sobue et al. | Dec 2008 | B2 |
7560882 | Clark et al. | Jul 2009 | B2 |
7778746 | Mcleod et al. | Aug 2010 | B2 |
7800345 | Yun et al. | Sep 2010 | B2 |
7825616 | Clark et al. | Nov 2010 | B2 |
7926889 | Bell, Jr. et al. | Apr 2011 | B2 |
7952381 | Kobayakawa | May 2011 | B2 |
D652349 | Kristensen | Jan 2012 | S |
8120291 | Clark et al. | Feb 2012 | B2 |
8201897 | Bell, Jr. et al. | Jun 2012 | B2 |
8596391 | Kshatriya | Dec 2013 | B2 |
8604749 | Kwag et al. | Dec 2013 | B2 |
8692509 | Shook et al. | Apr 2014 | B2 |
8714572 | Singletary et al. | May 2014 | B1 |
9026303 | Ferguson et al. | May 2015 | B1 |
9050899 | Seol | Jun 2015 | B2 |
9190782 | King et al. | Nov 2015 | B2 |
9199546 | King | Dec 2015 | B2 |
9225183 | King | Dec 2015 | B2 |
9371067 | Dao et al. | Jun 2016 | B2 |
9387775 | Baek et al. | Jul 2016 | B2 |
9436261 | Yun | Sep 2016 | B2 |
9508982 | Kim et al. | Nov 2016 | B2 |
9553460 | Dao et al. | Jan 2017 | B2 |
9592743 | Haug | Mar 2017 | B2 |
9595847 | Dao et al. | Mar 2017 | B2 |
9721447 | Mese et al. | Aug 2017 | B2 |
9764643 | Ono | Sep 2017 | B2 |
9806341 | Lee et al. | Oct 2017 | B2 |
9806545 | Fink | Oct 2017 | B2 |
9847658 | Kuhlmann et al. | Dec 2017 | B2 |
9908461 | Gasper | Mar 2018 | B2 |
10017169 | Harvey et al. | Jul 2018 | B1 |
10046652 | Yoshida et al. | Aug 2018 | B2 |
10110053 | Brackx et al. | Oct 2018 | B2 |
10195953 | Harvey | Feb 2019 | B2 |
10654372 | Harvey | May 2020 | B2 |
10890923 | O'Hara et al. | Jan 2021 | B2 |
20020029943 | Totsuka | Mar 2002 | A1 |
20020111756 | Modgil | Aug 2002 | A1 |
20020169522 | Kanno | Nov 2002 | A1 |
20030090272 | Bertness | May 2003 | A1 |
20030221881 | Lee | Dec 2003 | A1 |
20050003926 | Hanada | Jan 2005 | A1 |
20050023072 | Kodama et al. | Feb 2005 | A1 |
20050187671 | Nada | Aug 2005 | A1 |
20050194931 | Sobue et al. | Sep 2005 | A1 |
20050211478 | Sakuma | Sep 2005 | A1 |
20080190680 | Kaneko | Aug 2008 | A1 |
20090000839 | Ishii | Jan 2009 | A1 |
20090055157 | Soffer | Feb 2009 | A1 |
20090060684 | Nakamoto | Mar 2009 | A1 |
20090125184 | Oakes | May 2009 | A1 |
20090143931 | Sekiya | Jun 2009 | A1 |
20090195217 | Choi et al. | Aug 2009 | A1 |
20090206798 | Choi et al. | Aug 2009 | A1 |
20090298642 | Choi | Dec 2009 | A1 |
20090299557 | Farnsworth | Dec 2009 | A1 |
20100121513 | Itoh et al. | May 2010 | A1 |
20100123438 | Harada | May 2010 | A1 |
20100201293 | Yoshida et al. | Aug 2010 | A1 |
20100297482 | Yoon et al. | Nov 2010 | A1 |
20110172868 | Marcus | Jul 2011 | A1 |
20110178666 | Marcus | Jul 2011 | A1 |
20110285356 | Maluf et al. | Nov 2011 | A1 |
20110316548 | Ghantous et al. | Dec 2011 | A1 |
20120013304 | Murase et al. | Jan 2012 | A1 |
20120072063 | Kato et al. | Mar 2012 | A1 |
20120098489 | Arai et al. | Apr 2012 | A1 |
20120131367 | Kamijima | May 2012 | A1 |
20120142491 | Gwon | Jun 2012 | A1 |
20120159916 | Ishii | Jun 2012 | A1 |
20120176082 | Lee et al. | Jul 2012 | A1 |
20120200266 | Berkowitz et al. | Aug 2012 | A1 |
20120303397 | Prosser | Nov 2012 | A1 |
20130038274 | Forsythe | Feb 2013 | A1 |
20130085631 | Kim | Apr 2013 | A1 |
20130088198 | Masuda | Apr 2013 | A1 |
20130197731 | Schum | Aug 2013 | A1 |
20130241502 | Sowden | Sep 2013 | A1 |
20130249493 | Kim et al. | Sep 2013 | A1 |
20130297120 | Reed | Nov 2013 | A1 |
20140002020 | Geber et al. | Jan 2014 | A1 |
20140067121 | Brooks et al. | Mar 2014 | A1 |
20140068288 | Robinson et al. | Mar 2014 | A1 |
20140091764 | Kinomura et al. | Apr 2014 | A1 |
20140225559 | Sugano | Aug 2014 | A1 |
20140225621 | Kimura et al. | Aug 2014 | A1 |
20140277887 | Slattery et al. | Sep 2014 | A1 |
20150057859 | Yamamoto | Feb 2015 | A1 |
20150084597 | Kim et al. | Mar 2015 | A1 |
20150130414 | Izumi | May 2015 | A1 |
20150191098 | Chang et al. | Jul 2015 | A1 |
20150318723 | Brockman | Nov 2015 | A1 |
20160094056 | Dulle | Mar 2016 | A1 |
20160207523 | Kotsuji | Jul 2016 | A1 |
20160212885 | Ikeda et al. | Jul 2016 | A1 |
20160227628 | Lydecker et al. | Aug 2016 | A1 |
20160347302 | Niwa et al. | Dec 2016 | A1 |
20170104353 | Zhao et al. | Apr 2017 | A1 |
20170182893 | Hayashizaki et al. | Jun 2017 | A1 |
20170242079 | Duan et al. | Aug 2017 | A1 |
20170267107 | Miyashita et al. | Sep 2017 | A1 |
20170267243 | Chang | Sep 2017 | A1 |
20170358937 | Huang et al. | Dec 2017 | A1 |
20180047219 | Buswell et al. | Feb 2018 | A1 |
20180186241 | Harvey et al. | Jul 2018 | A1 |
20180186244 | Harvey et al. | Jul 2018 | A1 |
20180186316 | Harvey | Jul 2018 | A1 |
20180186355 | Harvey et al. | Jul 2018 | A1 |
20180257492 | O'Hara et al. | Sep 2018 | A1 |
20180281821 | Spenk et al. | Oct 2018 | A1 |
20180366968 | Magagnin et al. | Dec 2018 | A1 |
20190051947 | Scheucher | Feb 2019 | A1 |
20190064849 | O'Hara et al. | Feb 2019 | A1 |
20190067961 | King et al. | Feb 2019 | A1 |
20190135130 | Hornischer | May 2019 | A1 |
20190319472 | Lebreux | Oct 2019 | A1 |
20190337497 | Scheuerell | Nov 2019 | A1 |
20190356134 | Ohashi | Nov 2019 | A1 |
20200023850 | Burford | Jan 2020 | A1 |
20200130187 | Iwayama | Apr 2020 | A1 |
20200130531 | Wang et al. | Apr 2020 | A1 |
20200148051 | Keppler et al. | May 2020 | A1 |
20210384750 | Gohier | Dec 2021 | A1 |
20220227241 | Harvey | Jul 2022 | A1 |
Number | Date | Country |
---|---|---|
112019013516 | Jan 2020 | BR |
112018001862 | Jul 2022 | BR |
101141076 | Mar 2008 | CN |
101445039 | Jun 2009 | CN |
103314477 | Sep 2013 | CN |
103818265 | May 2014 | CN |
104417556 | Mar 2015 | CN |
104578260 | Apr 2015 | CN |
104763696 | Jul 2015 | CN |
205044671 | Nov 2015 | CN |
103863437 | Mar 2016 | CN |
205087870 | Mar 2016 | CN |
107521476 | Dec 2017 | CN |
108263213 | Jul 2018 | CN |
108263227 | Jul 2018 | CN |
109149675 | Jan 2019 | CN |
110481383 | Nov 2019 | CN |
110682831 | Jan 2020 | CN |
109591622 | Aug 2021 | CN |
115723584 | Mar 2023 | CN |
10324328 | Feb 2004 | DE |
102012207815 | May 2012 | DE |
1535790 | Jun 2005 | EP |
1564880 | Aug 2005 | EP |
1655830 | May 2006 | EP |
2436573 | Apr 2012 | EP |
2570313 | Mar 2013 | EP |
2821277 | Jan 2015 | EP |
2858202 | Apr 2015 | EP |
3043417 | Jul 2016 | EP |
3107178 | Dec 2016 | EP |
3342623 | Jul 2018 | EP |
3342631 | Jul 2018 | EP |
3342654 | Jul 2018 | EP |
2389090 | Dec 2003 | GB |
2590959 | Jul 2021 | GB |
H05115105 | May 1993 | JP |
H06261418 | Sep 1994 | JP |
2001018689 | Jan 2001 | JP |
2001047893 | Feb 2001 | JP |
2004215447 | Jul 2004 | JP |
2005051834 | Feb 2005 | JP |
4133349 | Aug 2008 | JP |
2009255840 | Nov 2009 | JP |
2012070674 | Apr 2012 | JP |
2015532621 | Nov 2015 | JP |
20110041876 | Oct 2009 | KR |
20210149941 | Dec 2021 | KR |
2699204 | Sep 2019 | RU |
2723661 | Jun 2020 | RU |
2005091965 | Mar 2005 | WO |
20130024533 | Feb 2013 | WO |
20130129217 | Sep 2013 | WO |
20160133453 | Aug 2016 | WO |
2019228921 | May 2019 | WO |
2020200897 | Oct 2020 | WO |
Entry |
---|
“Hardware building blocks of a hierarchical battery management system for a fuel cell HEV;” Baronti et al. IECON 2012—38th Annual Conference on IEEE Industrial Electronics Society (pp. 4041-4047); Oct. 1, 2012. (Year: 2012). |
“Research and design of control strategy for on-board charging system in electric vehicle;” Qiufeng et al.; 2017 29th Chinese Control And Decision Conference (CCDC) (pp. 6901-6905); May 1, 2017. (Year: 2017). |
“Review on Energy Management System of Electric Vehicles;” Aruna et al.; 2019 2nd International Conference on Power and Embedded Drive Control (ICPEDC) (pp. 371-374); Apr. 17, 2020 (Year: 2020). |
Garia, “Introducing the New Garia Golf”, http://www.garia.com/news/introducing-the-new-garia-golf/, Sep. 15, 2016. |
Anonymous: “SAE Electric Vehicle and Plug in Hybrid Electric Vehicle Conductive Charge Coupler”, SAE Standard, SAE International, US vol. J1772_201210, Oct. 15, 2012, pp. 1-93. |
Number | Date | Country | |
---|---|---|---|
20220227241 A1 | Jul 2022 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16713554 | Dec 2019 | US |
Child | 17715265 | US | |
Parent | 16407329 | May 2019 | US |
Child | 16713554 | US | |
Parent | 15395245 | Dec 2016 | US |
Child | 16407329 | US |