The present invention relates to charging technologies of electric batteries, for example, electric vehicle batteries. Particularly, the present invention relates to charging groups of battery modules in series and also charging individual battery modules in the group.
Battery charging technologies are an important part of the development of new electric battery-powered devices, such as electric vehicles. For example, environment-friendly and energy-saving new energy electric vehicles are an emerging field of automobile development. Batteries within electric vehicles or other electric devices may be composed of a plurality of battery modules connected in series. For example, if a battery includes 10 battery modules in total, each battery module providing 40V voltage output, then a 400V voltage output may be obtained when all the battery modules are connected in series. In some charging systems, such battery modules may be connected in series to charge all of the modules together. However, in some such cases, battery modules charged in series may charge unbalancedly and certain individual battery modules might not fully charge, for example, due to differences in resistance and the like among the individual battery modules.
The present invention is intended to solve these and other above problems relating to charging battery modules within a battery of an electric device.
One object of the present invention is to provide battery packs for an electric vehicles and other electric devices, comprising a battery and a battery charging system, wherein the battery comprises a plurality of battery modules, each battery module is includes (or is provided with) one or more battery cells, and the plurality of battery modules are connected in series when providing electric power output, wherein the battery charging system comprises: a first charging circuit, the first charging circuit connects the plurality of battery modules in series, and the first charging circuit is used for charging the plurality of battery modules in the battery in series; second charging circuits, the second charging circuits are connected to the plurality of battery modules respectively, and the second charging circuits are used for charging at least one battery module in the plurality of battery modules.
Another object of the present invention is to provide battery charging stations, used for charging a battery, wherein the battery comprises a plurality of battery modules, each battery module includes one or more battery cells, and the plurality of battery modules are connected in series when providing electric power output, wherein the battery charging station comprises: a first charging circuit for charging the battery in series; second charging circuits for charging at least one battery module; the first charging circuit and the second charging circuits can work cooperatively with each other, or the first charging circuit and the second charging circuits work independently.
Yet another object of the present invention is to provide methods for charging batteries, wherein the battery comprises a plurality of battery modules, each battery module includes one or more battery cells, and the plurality of battery modules are connected in series when providing electric power output, wherein the method comprises the following steps: 1) measuring the voltage of the battery, judging whether the battery needs to be charged, if so, then: 2) using a first charging circuit to charge the battery modules in the battery in series; 3) measuring whether the voltage of the battery modules connected in series reaches a first preset voltage value; 4) if the voltage of the battery modules connected in series reaches the first preset voltage value, measuring whether the voltage of each battery module in the battery reaches a second preset voltage value; 5) selecting one or more battery modules not reaching the second preset voltage value; and 6) using the corresponding second charging circuits to charge the selected one or more battery modules until the voltages thereof reach the second preset voltage value.
In some embodiments of the battery packs, battery charging stations, and charging methods described herein, at least two sets of independent and/or cooperative charging circuits are used for charging the battery modules of the battery. For example, a first charging circuit may charge the entire battery at the same time in series, while a plurality of second charging circuits may independently charge individual battery modules in the battery according to their voltage states, in order to solve the problem of unbalance when charging in series.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of various embodiments of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form.
The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth in the appended claims.
Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
Various embodiments of the present invention will be described below with reference to the drawings constituting a part of the description. It should be understood that, although terms representing directions are used in the present invention, such as “front”, “rear”, “upper”, “lower”, “left”, “right”, and the like, for describing various exemplary structural parts and elements of the present invention, these terms are used herein only for the purpose of convenience of explanation and are determined based on the exemplary orientations shown in the drawings. Since the embodiments disclosed by the present invention can be arranged according to different directions, these terms representing directions are merely used for illustration and should not be regarded as limitation. Wherever possible, the same or similar reference marks used in the present invention refer to the same components.
The term “computer-readable medium” includes, but is not limited non-transitory media such as portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instruction(s) and/or data. A code segment or computer-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.
Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks may be stored in a computer-readable medium. A processor(s) may perform the necessary tasks.
Various techniques (e.g., systems, circuits, methods, non-transitory computer-readable storage memory storing a plurality of instructions executable by one or more processors, etc.) are described herein relating to battery packs of electric vehicles, batteries and battery charging systems. Batteries described herein may comprise a plurality of battery modules, wherein each battery module may include one or more battery cells, and the plurality of battery modules may be connected in series when providing electric power output. Battery charging systems described herein may comprise a charging circuit that connects a plurality of battery modules in series, and may be used for charging the plurality of battery modules in the battery in series. Additional charging circuits may be connected respectively to the plurality of battery modules, and the additional charging circuits may be used for charging at least one battery module in the plurality of battery modules.
Referring now to
As shown in
In this example, the first charging circuit 100, 100′ may be connected to the two ends of the battery 110, and may be used for connecting the plurality of battery modules 101.1, 101.2, . . . , 101.i, . . . , 101.N in the battery 110 in series. Each of the battery modules 101.1, 101.2, 101.3, . . . , 101.i, . . . 101.N is also individually connected to one of second charging circuits 111.1, 111.2, 111.3, . . . , 111.i, . . . 111.N, so that the second charging circuits 111.1, 111.2, 111.3, . . . , 111.i, . . . , 111.N may be used to independently charge one or more of the corresponding battery modules 101.i. In some embodiments, one or more of the second charging circuits may be connected not just to a single battery module, but to multiple battery modules in series. For instance, a second charging circuit 111 may be connected in series to two battery modules, or three battery modules, etc., or any other subset of the plurality of battery modules 101, thereby allowing the second charging circuit 111 to charge only that subset of the plurality of battery modules 101.
The battery charging system 10 may further include a battery voltage feedback circuit 102, 102′ and battery module voltage feedback circuits 121.1, 121.2, 121.3, . . . , 121.i, . . . , 121.N (which may be referred to individually or collectively as battery module voltage feedback circuit(s) 121). The battery voltage feedback circuit 102, 102′ in this example connects the two ends of the battery 110 with a battery detecting system (EMS) 210 (see
In addition, during charging, the control circuit 130 of the battery charging system 10 may be connected with an external charging pile/charging station 140 through, for example, a plug (omitted from the figure). The control circuit 130 may distribute the electric power of the charging pile/charging station 140 to the first charging circuit 100, 100′ and the second charging circuits 111.1, 111.2, 111.3, . . . , 111.i, . . . , 111.N as necessary for charging.
Referring now to
As shown in
In addition, the control circuit 130 in this example is further connected with external auxiliary chargers 214, 215 to obtain working electric power. Specifically, the control circuit 130 may be connected with the auxiliary charger 215 through the serial communication bus 211 to obtain a working power supply. The relays 220, 221.i may be connected with the auxiliary charger 214 through the input and output port 213 to obtain the working electric power.
In some embodiments, the control switches of the first charging circuit 100, 100′ and the second charging circuits 111.1, 111.2, 111.3, . . . , 111.i, . . . , 111.N may correspond to the relays 220, 221.i, which may be used as a circuit switches to control the switch-on/switch-off of the control circuit. The control switch also may be a triode and/or other electric elements for controlling the on/off of the circuit. In certain embodiments, the processing chip (MCU) 212 may be, for example, an AT89S51 micro control chip or the like. In these and other embodiments, the processing chip 212 may perform the various functions described herein via hardware circuitry and/or via computer-readable media storing computer-executable software instructions to perform the described functions.
The battery voltage feedback circuit 102, 102′ may monitor the voltage V at the two ends of the battery 110 in real time, and may send the voltage signal to the battery detecting system (EMS) 210. The battery detecting system (EMS) 210 may determine whether the battery 110 needs to be charged based on the received voltage signal. If the battery needs to be charged, the processing chip 212 may send a switch-on signal to the relay 220 through the input and output port 213, and the relay 220 may switch on the first charging circuit 100, 100′ to charge the battery modules 101.1, 101.2, . . . 101.i . . . 101.N in series by applying a first charging voltage V1. When the battery detecting system (EMS) 210 determines, based on periodic or continuous voltage monitoring, that the voltage V at the two ends of the battery reaches a first preset voltage value V01 (e.g., a voltage at which the battery 110 is regarded as fully charged) through the battery voltage feedback circuit 102, 102′, the processing chip 212 may send a switch-off signal to the relay 220 in order to switch off the first charging circuit 100, 100′. In some cases, a high voltage (the first charging voltage V1) may be used for charging the battery 110, so that the charging efficiency may be higher. However, as discussed above, due to individual differences in the battery modules 101.1, 101.2, . . . , 101.i, . . . , 101.N (e.g., difference in internal resistance, etc.), some of the battery modules may be charged unbalancedly. For example, a first battery module 101.i might not be fully charged to reach a second preset voltage value V02 (e.g., a voltage at which the battery module is regarded as fully charged). Thus, the individual battery module 101.i may also be independently charged, as described below.
The battery module voltage feedback circuits 121.1, 121.2, 121.3, . . . , 121.i, . . . , 121.N may be configured to detect the voltage Vi at the two ends of each respectively battery module 101.i, and to send the detected voltage signals to the battery detecting system (EMS) 210. The battery detecting system (EMS) 210 may determine/judge whether each of the individual battery module has reached the preset second preset voltage value V02. If the battery detecting system (EMS) 210 determines that one or more certain battery modules 101.i have not reached the second preset voltage value V02, the processing chip 212 may send an switch-on signal to the corresponding relays 221.i through the input and output port 213, and the one or more second charging circuits 111.i may independently charge any of the battery modules 101.i which were not fully charged when the battery modules where charged in series using the first charging circuit 100, 100′. For independently charging one or more of the battery modules 101, a second charging voltage V2 may be used until the individual voltage Vi of the battery module reaches the second preset voltage value V02. The charging process of each individual battery module may be the same, until all the battery modules 101.1, 101.2, . . . , 101.i, . . . , 101.N reach the second preset voltage value (V02). The charging of the one or more of individual battery modules that were not fully charged in series by the first charging circuit, may be performed using the appropriate second charging circuits, and may be perform all at the same time or at different times (e.g., in sequence starting with the least charged battery module first), in processes controlled by the configuration of the processing chip 212.
As noted above, when charging batteries for electric vehicles and other electric devices, a battery may be charged only using a single charging circuit and the individual battery modules might not be separately charged. However, in such cases, the electric quantity of each battery module may be different from the other modules, and when the modules are connected in series for use, the internal resistance of the entire battery may be increased by these voltage differences in the modules, which may reduce the overall efficiency of the battery. Therefore, in certain embodiments, the battery detecting system (EMS) 210, the battery voltage feedback circuit 102, 102′ and the battery module voltage feedback circuits 121.1, 121.2, 121.3, . . . , 121.i, . . . , 121.N may monitor the voltage states of the battery 110 as well as the voltages of the individual battery modules in real time. Each individual battery modules may be charged in at least two separate manners and with at least two different working voltages, for example, through the first charging circuit 100, 100′, and through its respective second charging circuit 111, thereby ensuring that each of the battery modules may be fully charged in order to improve the overall working efficiency of the battery 110. Additionally, as noted above, one or more of the second charging circuits may be connected not just to a single battery module 101, but to a subset of multiple battery modules (e.g., 2 battery modules, 3 battery modules, etc.) in series. Therefore, in some cases, the each individual battery modules may be charged in more than two separate manners and with more than two different working voltages. For example, a first battery module may be charged using the first charging circuit, and separately charged using a second charging circuit connected only to the single battery module, and also may be charged using another second charging circuit (not shown in the figures) that is connected in series to a subset two, three, four, etc. battery modules including the first battery module.
In some embodiments, one or more of the second charging circuits may be connected not just to a single battery module, but to multiple battery modules in series. For instance, a second charging circuit 111 may be connected in series to two battery modules, or three battery modules, etc., or any other subset of the plurality of battery modules 101, thereby allowing the second charging circuit 111 to charge only that subset of the plurality of battery modules 101.
Referring now to
As discussed above in reference to
Referring now to
The computer device 400 is shown comprising hardware elements that may be electrically coupled via a bus 402 (or may otherwise be in communication, as appropriate). The hardware elements may include a processing unit with one or more processors 404, including without limitation one or more general-purpose processors and/or one or more special-purpose processors (such as digital signal processing chips, graphics acceleration processors, and/or the like); one or more input devices 406, which may include without limitation a steering wheel, a climate control button or other user input receiving buttons, and/or the like; and one or more output devices 408, which may include without limitation a presentation device (e.g., a computer screen), a GPS, and/or the like.
The computer system 400 may further include (and/or be in communication with) one or more non-transitory storage devices 410, which may comprise, without limitation, local and/or network accessible storage, and/or may include, without limitation, a disk drive, a drive array, an optical storage device, a solid-state storage device, such as a random access memory, and/or a read-only memory, which may be programmable, flash-updateable, and/or the like. Such storage devices may be configured to implement any appropriate data stores, including without limitation, various file systems, database structures, and/or the like.
The computer device 400 might also include a communications subsystem 412, which may include without limitation a modem, a network card (wireless and/or wired), an infrared communication device, a wireless communication device and/or a chipset such as a Bluetooth™ device, 802.11 device, WiFi device, WiMax device, cellular communication facilities such as GSM (Global System for Mobile Communications), W-CDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), etc., and/or the like. The communications subsystem 412 may permit data to be exchanged with a network (such as the network described below, to name one example), other computer systems, and/or any other devices described herein. In many embodiments, the computer system 400 will further comprise a working memory 414, which may include a random access memory and/or a read-only memory device, as described above.
The computer device 400 also may comprise software elements, shown as being currently located within the working memory 414, including an operating system 416, device drivers, executable libraries, and/or other code, such as one or more application programs 418, which may comprise computer programs provided by various embodiments, and/or may be designed to implement methods, and/or configure systems, provided by other embodiments, as described herein. By way of example, one or more procedures described with respect to the method(s) discussed above, and/or system components might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer); in an aspect, then, such code and/or instructions may be used to configure and/or adapt a general purpose computer (or other device) to perform one or more operations in accordance with the described methods.
A set of these instructions and/or code might be stored on a non-transitory computer-readable storage medium, such as the storage device(s) 410 described above. In some cases, the storage medium might be incorporated within a computer system, such as computer system 400. In other embodiments, the storage medium might be separate from a computer system (e.g., a removable medium, such as flash memory), and/or provided in an installation package, such that the storage medium may be used to program, configure, and/or adapt a general purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer device 400 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 400 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.
It will be apparent that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both. Further, connection to other computing devices such as network input/output devices may be employed.
As mentioned above, in one aspect, some embodiments may employ a computer system (such as the computer device 400) to perform methods in accordance with various embodiments of the disclosure. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer system 400 in response to processor 404 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 416 and/or other code, such as an application program 418) contained in the working memory 414. Such instructions may be read into the working memory 414 from another computer-readable medium, such as one or more of the storage device(s) 410. Merely by way of example, execution of the sequences of instructions contained in the working memory 414 may cause the processor(s) 404 to perform one or more procedures of the methods described herein.
The terms “machine-readable medium” and “computer-readable medium,” as used herein, may refer to any non-transitory medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer device 400, various computer-readable media might be involved in providing instructions/code to processor(s) 404 for execution and/or might be used to store and/or carry such instructions/code. In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take the form of a non-volatile media or volatile media. Non-volatile media may include, for example, optical and/or magnetic disks, such as the storage device(s) 410. Volatile media may include, without limitation, dynamic memory, such as the working memory 414.
Example forms of physical and/or tangible computer-readable media may include a floppy disk, a flexible disk, hard disk, magnetic tape, or any other magnetic medium, a compact disc, any other optical medium, ROM, RAM, and etc., any other memory chip or cartridge, or any other medium from which a computer may read instructions and/or code. Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 404 for execution. By way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer system 400.
The communications subsystem 412 (and/or components thereof) generally will receive signals, and the bus 402 then might carry the signals (and/or the data, instructions, etc. carried by the signals) to the working memory 414, from which the processor(s) 404 retrieves and executes the instructions. The instructions received by the working memory 414 may optionally be stored on a non-transitory storage device 410 either before or after execution by the processor(s) 404.
It should further be understood that the components of computer device 400 can be distributed across a network. For example, some processing may be performed in one location using a first processor while other processing may be performed by another processor remote from the first processor. Other components of computer system 400 may be similarly distributed. As such, computer device 400 may be interpreted as a distributed computing system that performs processing in multiple locations. In some instances, computer system 400 may be interpreted as a single computing device, such as a distinct laptop, desktop computer, or the like, depending on the context.
In a first example embodiment, a battery pack (150) of an electric vehicle may comprise a battery (110) and a battery charging system (10), wherein the battery (110) comprises a plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N), each battery module (101.i) is provided with one or more battery cells, and the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) are connected in series when providing electric power output, wherein the battery charging system (10) comprises: a first charging circuit (100, 100′), the first charging circuit (100, 100′) connects the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) in series, and the first charging circuit (100, 100′) is used for charging the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) in the battery (110) in series; second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N), the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) are connected to the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) respectively, and the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) are used for charging at least one battery module (101.i) in the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N).
A second example embodiment may include the battery pack (150) of the first example embodiment, wherein the first charging circuit (100, 100′) and the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) can work cooperatively with each other, or the first charging circuit (100, 100′) and the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) can work independently.
A third example embodiment may include the battery pack (150) of the first example embodiment, wherein the first charging circuit (100, 100′) apply voltage and current to the two ends of the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) connected in series for charging.
A fourth example embodiment may include the battery pack (150) of the second example embodiment, wherein the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) selectively charge one battery module (101.i) in the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) by applying voltage and current to the two ends thereof.
A fifth example embodiment may include the battery pack (150) of the first example embodiment, further comprising a control circuit (130) for selectively switching on or switching off the first charging circuit (100, 100′) or the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N).
A sixth example embodiment may include the battery pack (150) of the fifth example embodiment, wherein the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) can select a certain battery module (101.i) in the battery (110) and charge the two ends of the selected battery module (101.i).
A seventh example embodiment may include the battery pack (150) of the sixth example embodiment, wherein the battery charging system (10) further comprises a battery voltage feedback circuit (102, 102′), the battery voltage feedback circuit (102, 102′) is connected with the control circuit (130) and used for sending a voltage signal reflecting the current voltage of the battery (110) to the control circuit (130); each one of the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) is connected to a battery module voltage feedback circuit (121.1, 121.2, . . . , 121.i, . . . , 121.N), and the battery module voltage feedback circuits (121.1, 121.2, . . . , 121.i, . . . , 121.N) are connected with the control circuit (130) and used for sending voltage signals reflecting the current voltages of the battery modules to the control circuit (130); the control circuit (130) starts or stops applying voltage and current for charging the two ends of the plurality of battery modules (101.1, 101.2, 101.i, . . . , 101.N) connected in series according to the current voltage of the battery (110); and the control circuit (130) selects a certain battery module (101.i) according to the current voltage of each battery module (101.i) to start or stop applying voltage and current for charging the selected battery module (101.i).
An eighth example embodiment may include the battery pack (150) of the seventh example embodiment, wherein the battery modules in the battery (110) are charged in series by using a first charging voltage (V1), and wherein the selected battery module in the battery (110) is charged independently by using a second charging voltage (V2).
A ninth example embodiment may include the battery pack (150) of the eighth example embodiment, the first charging voltage (V1) and the second charging voltage (V2) are different voltages.
A tenth example embodiment may include the battery pack (150) of the first example embodiment, wherein according to the voltage of the selected battery module (101.i), the second charging circuit (111.i) selects a proper voltage to charge the selected battery module (101.i) until the selected battery module (101.i) reaches a preset voltage.
A eleventh example embodiment may include the battery pack (150) of the seventh example embodiment, wherein the control circuit (130) further comprises: a battery detecting system (210) connected to the battery voltage feedback circuit (102, 102′) and the battery module voltage feedback circuits (121.1, 121.2, . . . , 121.i, . . . , 121.N) for receiving the voltage signal sent by the battery voltage feedback circuit (102, 102′) and the battery module voltage feedback circuits (121.1, 121.2, . . . , 121.i, . . . , 121.N) and controlling switch-on or switch-off of the first charging circuit (100, 100′) and/or the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N); a first circuit switch (220) connected to the first charging circuit (100, 100′) and the battery detecting system (210) for switching on or switching off of the first charging circuit (100, 100′) under the control of the battery detecting system (210); and second circuit switches (221.1, 221.2, 221.3, . . . 221.i . . . 221.N) connected to the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N), respectively, and the battery detecting system (210) for switching on or switching off of the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) under the control of the battery detecting system (210).
In a twelfth example embodiment, a battery charging station (20) may be used for charging a battery (110), wherein the battery (110) comprises a plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N), each battery module is provided with one or more battery cells, and the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) are connected in series when providing electric power output, wherein the battery charging station (20) comprises: a first charging circuit (100, 100′) for charging the battery (110) in series; second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) for charging at least one battery module; the first charging circuit (100, 100′) and the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) can work cooperatively with each other, or the first charging circuit (100, 100′) and the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) work independently.
A thirteenth example embodiment may include the battery charging station (20) of the twelfth example embodiment, wherein the first charging circuits (100, 100′) apply voltage and current for charging to the two ends of the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) connected in series.
A fourteenth example embodiment may include the battery charging station (20) of the twelfth example embodiment, further comprising: a control circuit (130) arranged in the battery charging station (20) and used for selectively switching on or switching off the first charging circuits (100, 100′) or the second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N).
In a fifteenth example embodiment, a method may be performed for charging a battery (110), wherein the battery (110) comprises a plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N), each battery module is provided with one or more battery cells, and the plurality of battery modules (101.1, 101.2, . . . , 101.i, . . . , 101.N) are connected in series when providing electric power output, wherein the method comprises the following steps: 1) measuring the voltage (V) of the battery (110), judging whether the battery needs to be charged, if so, then: 2) using a first charging circuit (100, 100′) to charge the battery modules in the battery (110) in series; 3) measuring whether the voltage (V) of the battery modules connected in series reaches a first preset voltage value (V01); 4) if the voltage (V) of the battery modules connected in series reaches the first preset voltage value (V01), measuring whether the voltage (V′) of each battery module in the battery (110) reaches a second preset voltage value (V02); 5) selecting one or more battery modules (101.i) not reaching the second preset voltage value (V02); and 6) using the corresponding second charging circuits (111.1, 111.2, . . . , 111.i, . . . , 111.N) to charge the selected one or more battery modules (101.i) until the voltages (V′) thereof reach the second preset voltage value (V02).
Although the present invention has been described with reference to the specific embodiments shown in the drawings, it should be understood that the charging system and the charging method provided by the present invention can have a variety of variations without departing from the spirit, scope and background of the present invention. Those of ordinary skill in the art should be still aware that, parameters in the embodiments disclosed by the present invention can be changed in different manners, and these changes shall fall within the spirit and scope of the present invention and the claims.
The present application is a non-provisional of and claims priority to U.S. Provisional Patent Application No. 62/133,991, filed Mar. 16, 2015, and entitled “IMPROVEMENTS TO ELECTRIC VEHICLES.” The present application is also a non-provisional of and claims priority to U.S. Provisional Patent Application No. 62/150,848, filed Apr. 22, 2015, and entitled “IMPROVEMENTS TO ELECTRIC VEHICLES.” The entire contents of each of the 62/133,991 and 62/150,848 provisional applications are incorporated herein by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
3723215 | Kessler | Mar 1973 | A |
3930192 | Dinkler | Dec 1975 | A |
4007315 | Brinkmann et al. | Feb 1977 | A |
4026468 | Tinder et al. | May 1977 | A |
4079275 | Fu | Mar 1978 | A |
4248383 | Savage et al. | Feb 1981 | A |
4281276 | Cutler et al. | Jul 1981 | A |
4324363 | Rauen, Jr. | Apr 1982 | A |
4693652 | Sweeney | Sep 1987 | A |
4848835 | DeRees | Jul 1989 | A |
4926105 | Mischenko et al. | May 1990 | A |
5115342 | Rowe et al. | May 1992 | A |
5121044 | Goldman | Jun 1992 | A |
5289890 | Toyoda et al. | Mar 1994 | A |
5345155 | Masaki et al. | Sep 1994 | A |
5585204 | Oshida et al. | Dec 1996 | A |
5619784 | Nishimoto et al. | Apr 1997 | A |
5666040 | Bourbeau | Sep 1997 | A |
5710504 | Pascual et al. | Jan 1998 | A |
5830308 | Reichard | Nov 1998 | A |
5875691 | Hata et al. | Mar 1999 | A |
5889342 | Hasebe et al. | Mar 1999 | A |
5969624 | Sakai | Oct 1999 | A |
6089034 | Lake et al. | Jul 2000 | A |
6126219 | Wilkinson et al. | Oct 2000 | A |
6272809 | Wycech | Aug 2001 | B1 |
6335078 | Venkataramani et al. | Jan 2002 | B2 |
6347528 | Iritani et al. | Feb 2002 | B1 |
6357541 | Matsuda et al. | Mar 2002 | B1 |
6367570 | Long, III et al. | Apr 2002 | B1 |
6450275 | Gabriel et al. | Sep 2002 | B1 |
6481230 | Kimishima et al. | Nov 2002 | B2 |
6504344 | Adams et al. | Jan 2003 | B1 |
6575258 | Clemmer | Jun 2003 | B1 |
6766036 | Pryor | Jul 2004 | B1 |
6772504 | Weidman et al. | Aug 2004 | B2 |
6899377 | Ghuman et al. | May 2005 | B2 |
6933076 | Ura et al. | Aug 2005 | B2 |
7208854 | Saban et al. | Apr 2007 | B1 |
7230404 | Kimoto et al. | Jun 2007 | B2 |
7289645 | Yamamoto et al. | Oct 2007 | B2 |
7325866 | Horton et al. | Feb 2008 | B2 |
7332242 | Sato et al. | Feb 2008 | B2 |
7335205 | Aeschlimann et al. | Feb 2008 | B2 |
7436139 | Maslov et al. | Oct 2008 | B2 |
7451808 | Busse et al. | Nov 2008 | B2 |
7789176 | Zhou | Sep 2010 | B2 |
7834500 | Savant | Nov 2010 | B2 |
7841431 | Zhou | Nov 2010 | B2 |
8020656 | Inoue et al. | Sep 2011 | B2 |
8159191 | Chang et al. | Apr 2012 | B2 |
8191618 | Gering et al. | Jun 2012 | B2 |
8336319 | Johnston et al. | Dec 2012 | B2 |
8344849 | Larsson et al. | Jan 2013 | B2 |
8450888 | Shafer et al. | May 2013 | B2 |
8479855 | Kim et al. | Jul 2013 | B2 |
8527130 | Kitahata et al. | Sep 2013 | B2 |
8556558 | Hunt | Oct 2013 | B1 |
8564246 | Wade | Oct 2013 | B2 |
8571738 | Potter et al. | Oct 2013 | B1 |
8625855 | El Dokor | Jan 2014 | B2 |
8641133 | Scaringe et al. | Feb 2014 | B1 |
8796881 | Davis | Aug 2014 | B2 |
8798832 | Kawahara et al. | Aug 2014 | B2 |
8818716 | El Dokor et al. | Aug 2014 | B1 |
8892281 | Suzuki et al. | Nov 2014 | B2 |
8896167 | McKinzie et al. | Nov 2014 | B2 |
8955345 | Meitinger et al. | Feb 2015 | B2 |
8983718 | Ricci | Mar 2015 | B2 |
8985680 | Mildner | Mar 2015 | B2 |
9180753 | Kim et al. | Nov 2015 | B2 |
9250020 | Vikstrom et al. | Feb 2016 | B2 |
9469350 | Wu | Oct 2016 | B2 |
9499067 | Dai | Nov 2016 | B2 |
9601733 | Sham | Mar 2017 | B2 |
9610857 | Dai | Apr 2017 | B2 |
20020005440 | Holt et al. | Jan 2002 | A1 |
20020134857 | Zimmer | Sep 2002 | A1 |
20020182493 | Ovshinsky et al. | Dec 2002 | A1 |
20030155001 | Hoetzer et al. | Aug 2003 | A1 |
20040080218 | Weidman et al. | Apr 2004 | A1 |
20040113589 | Crisp et al. | Jun 2004 | A1 |
20040195833 | Zoellner | Oct 2004 | A1 |
20050206511 | Heenan et al. | Sep 2005 | A1 |
20060021811 | Kuang et al. | Feb 2006 | A1 |
20060132101 | Ambrosio et al. | Jun 2006 | A1 |
20060175995 | Shinmura et al. | Aug 2006 | A1 |
20060211364 | Brotz et al. | Sep 2006 | A1 |
20070009787 | Straubel et al. | Jan 2007 | A1 |
20070077541 | Champagne et al. | Apr 2007 | A1 |
20070084484 | Porter et al. | Apr 2007 | A1 |
20070261787 | Malis | Nov 2007 | A1 |
20070278325 | Sato et al. | Dec 2007 | A1 |
20080024020 | Iund et al. | Jan 2008 | A1 |
20080042493 | Jacobs | Feb 2008 | A1 |
20080067965 | Bailey et al. | Mar 2008 | A1 |
20080116379 | Teder | May 2008 | A1 |
20080210780 | Discher et al. | Sep 2008 | A1 |
20090023056 | Adams et al. | Jan 2009 | A1 |
20090139781 | Straubel et al. | Jun 2009 | A1 |
20090146610 | Trigiani | Jun 2009 | A1 |
20090153087 | Lim et al. | Jun 2009 | A1 |
20090206689 | Harada et al. | Aug 2009 | A1 |
20090230921 | Hsu et al. | Sep 2009 | A1 |
20090250533 | Akiyama et al. | Oct 2009 | A1 |
20090278915 | Kramer et al. | Nov 2009 | A1 |
20100152936 | Wang et al. | Jun 2010 | A1 |
20100230991 | Fioravanti | Sep 2010 | A1 |
20100274480 | McCall et al. | Oct 2010 | A1 |
20110001456 | Wang | Jan 2011 | A1 |
20110031921 | Han | Feb 2011 | A1 |
20110073142 | Hattori et al. | Mar 2011 | A1 |
20110128543 | Choi | Jun 2011 | A1 |
20110128555 | Rotschild et al. | Jun 2011 | A1 |
20110159340 | Hu et al. | Jun 2011 | A1 |
20110229749 | Kim et al. | Sep 2011 | A1 |
20110241623 | Wade et al. | Oct 2011 | A1 |
20110246005 | King et al. | Oct 2011 | A1 |
20110266375 | Ono et al. | Nov 2011 | A1 |
20110292212 | Tanabe et al. | Dec 2011 | A1 |
20110309796 | Firehammer | Dec 2011 | A1 |
20120070701 | Gaben | Mar 2012 | A1 |
20120091964 | Vance et al. | Apr 2012 | A1 |
20120101690 | Srinivasan et al. | Apr 2012 | A1 |
20120105001 | Gallegos et al. | May 2012 | A1 |
20120116699 | Haag et al. | May 2012 | A1 |
20120163657 | Shellshear | Jun 2012 | A1 |
20120168125 | Johnston et al. | Jul 2012 | A1 |
20120222833 | Vikstrom et al. | Sep 2012 | A1 |
20120231316 | Sohn | Sep 2012 | A1 |
20120266922 | Krahn et al. | Oct 2012 | A1 |
20120291987 | Himmer et al. | Nov 2012 | A1 |
20120297809 | Carpenter | Nov 2012 | A1 |
20120303397 | Prosser | Nov 2012 | A1 |
20120313562 | Murao | Dec 2012 | A1 |
20130038151 | Ohashi et al. | Feb 2013 | A1 |
20130057117 | Suzuki et al. | Mar 2013 | A1 |
20130061630 | Schaefer et al. | Mar 2013 | A1 |
20130092758 | Tanaka et al. | Apr 2013 | A1 |
20130094086 | Bochenek | Apr 2013 | A1 |
20130117963 | Liu | May 2013 | A1 |
20130124038 | Naboulsi | May 2013 | A1 |
20130136975 | Uchida | May 2013 | A1 |
20130144470 | Ricci | Jun 2013 | A1 |
20130153338 | Yamauchi | Jun 2013 | A1 |
20130179061 | Gadh et al. | Jul 2013 | A1 |
20130217409 | Bridges et al. | Aug 2013 | A1 |
20130221926 | Furtner | Aug 2013 | A1 |
20130235381 | Kroekel et al. | Sep 2013 | A1 |
20130249317 | Kang et al. | Sep 2013 | A1 |
20140009615 | Kiyohara et al. | Jan 2014 | A1 |
20140017528 | Yuji et al. | Jan 2014 | A1 |
20140021924 | Abe et al. | Jan 2014 | A1 |
20140033865 | Suzuki et al. | Feb 2014 | A1 |
20140067323 | Skelton | Mar 2014 | A1 |
20140070013 | Stanek et al. | Mar 2014 | A1 |
20140077631 | Watanabe et al. | Mar 2014 | A1 |
20140081521 | Frojdh et al. | Mar 2014 | A1 |
20140089864 | Cheng et al. | Mar 2014 | A1 |
20140090673 | Atsumi et al. | Apr 2014 | A1 |
20140121927 | Hanita | May 2014 | A1 |
20140124159 | Kim | May 2014 | A1 |
20140141300 | Ronning et al. | May 2014 | A1 |
20140145933 | Chae et al. | May 2014 | A1 |
20140167655 | Chatroux et al. | Jun 2014 | A1 |
20140203782 | Xue | Jul 2014 | A1 |
20140216709 | Smith et al. | Aug 2014 | A1 |
20140223384 | Graumann | Aug 2014 | A1 |
20140247135 | Proud | Sep 2014 | A1 |
20140277936 | El Dokor et al. | Sep 2014 | A1 |
20140282271 | Lu et al. | Sep 2014 | A1 |
20140306826 | Ricci | Oct 2014 | A1 |
20140309849 | Ricci | Oct 2014 | A1 |
20140311704 | Yokoyama et al. | Oct 2014 | A1 |
20140333161 | Knoblauch | Nov 2014 | A1 |
20140354291 | Kikuchi et al. | Dec 2014 | A1 |
20140356652 | Boddakayala et al. | Dec 2014 | A1 |
20140365792 | Yun | Dec 2014 | A1 |
20150008931 | Sugeno et al. | Jan 2015 | A1 |
20150017642 | Pahl et al. | Jan 2015 | A1 |
20150022664 | Pflug et al. | Jan 2015 | A1 |
20150025917 | Stempora | Jan 2015 | A1 |
20150044522 | Camp et al. | Feb 2015 | A1 |
20150054933 | Wasiek et al. | Feb 2015 | A1 |
20150069974 | Okada et al. | Mar 2015 | A1 |
20150081135 | Gompert et al. | Mar 2015 | A1 |
20150088397 | Burton | Mar 2015 | A1 |
20150091698 | Du | Apr 2015 | A1 |
20150138357 | Romack et al. | May 2015 | A1 |
20150141043 | Abramson | May 2015 | A1 |
20150151722 | Gokan et al. | Jun 2015 | A1 |
20150168174 | Abramson | Jun 2015 | A1 |
20150171642 | Kato et al. | Jun 2015 | A1 |
20150188334 | Dao et al. | Jul 2015 | A1 |
20150203077 | Gokan | Jul 2015 | A1 |
20150317527 | Graumann et al. | Nov 2015 | A1 |
20150367859 | Roth et al. | Dec 2015 | A1 |
20160001330 | Romack et al. | Jan 2016 | A1 |
20160048725 | Holz et al. | Feb 2016 | A1 |
20160056510 | Takeuchi et al. | Feb 2016 | A1 |
20160086391 | Ricci | Mar 2016 | A1 |
20160271905 | Lo | Sep 2016 | A1 |
20160271926 | Lo | Sep 2016 | A1 |
20160272036 | Chen et al. | Sep 2016 | A1 |
20160272039 | Cheng | Sep 2016 | A1 |
20160272040 | Cheng | Sep 2016 | A1 |
20160272043 | Cheng | Sep 2016 | A1 |
20160272044 | Cheng | Sep 2016 | A1 |
20160272045 | Chen et al. | Sep 2016 | A1 |
20160272083 | Dai | Sep 2016 | A1 |
20160272084 | Chuang | Sep 2016 | A1 |
20160272085 | Dai | Sep 2016 | A1 |
20160272087 | Lai | Sep 2016 | A1 |
20160272164 | Hsiao et al. | Sep 2016 | A1 |
20160272165 | Hsiao et al. | Sep 2016 | A1 |
20160272242 | Sham | Sep 2016 | A1 |
20160272254 | Wu | Sep 2016 | A1 |
20160274668 | Hsaio et al. | Sep 2016 | A1 |
20160274669 | Hsiao et al. | Sep 2016 | A1 |
20160276638 | Sham | Sep 2016 | A1 |
20160276721 | Ho | Sep 2016 | A1 |
20160276722 | Ho | Sep 2016 | A1 |
20160276854 | Lai | Sep 2016 | A1 |
20160276855 | Lian | Sep 2016 | A1 |
20160276903 | Lai | Sep 2016 | A1 |
20160276905 | Lai | Sep 2016 | A1 |
20160276963 | Lai | Sep 2016 | A1 |
20160325638 | Dai | Nov 2016 | A1 |
20160339797 | Dai | Nov 2016 | A1 |
20170158059 | Dai | Jun 2017 | A1 |
Number | Date | Country |
---|---|---|
2008200543 | Aug 2009 | AU |
102118039 | Jul 2011 | CN |
102118041 | Jul 2011 | CN |
102709981 | Oct 2012 | CN |
205657447 | Oct 2016 | CN |
3837701 | May 1990 | DE |
1 386 828 | Feb 2004 | EP |
2 565 959 | Jun 2013 | EP |
2 670 018 | Dec 2013 | EP |
2725684 | Apr 2014 | EP |
2949520 | Dec 2015 | EP |
3331529 | Oct 1994 | JP |
2007253640 | Oct 2007 | JP |
2009294338 | Dec 2009 | JP |
2010057316 | Mar 2010 | JP |
2010273417 | Dec 2010 | JP |
2012 192543 | Oct 2012 | JP |
2013162597 | Aug 2013 | JP |
2014223867 | Dec 2014 | JP |
2011C89604 | Mar 2011 | KR |
2006124663 | Nov 2006 | WO |
2011067646 | Jun 2011 | WO |
2011126909 | Oct 2011 | WO |
2012105448 | Sep 2012 | WO |
2013015162 | Jan 2013 | WO |
2014103008 | Jul 2014 | WO |
2015103008 | Jul 2014 | WO |
2015035406 | Mar 2015 | WO |
Entry |
---|
U.S. Appl. No. 15/008,416, filed Jan. 27, 2016, Non-Final Office Action dated Jul. 6, 2016, all pages. |
U.S. Appl. No. 15/006,126, filed Jan. 26, 2016, Non-Final Office Action dated Jul. 25, 2016, all pages. |
U.S. Appl. No. 14/981,772, filed Dec. 28, 2015, Notice of Allowance dated Jul. 28, 2016, all pages. |
U.S. Appl. No. 14/981,772, filed Dec. 28, 2015, Non-Final Office Action dated May 26, 2016, all pages. |
U.S. Appl. No. 14/967,374, filed Dec. 14, 2015, Non-Final Office Action dated Jul. 13, 2016, all pages. |
U.S. Appl. No. 14/967,373, filed Dec. 14, 2015, Final Office Action dated Sep. 2, 2016, all pages. |
U.S. Appl. No. 14/967,373, filed Dec. 14, 2015, Non-Final Office Action dated Apr. 29, 2016, all pages. |
U.S. Appl. No. 14/967,372, filed Dec. 14, 2015, Non-Final Office Action dated Jul. 15, 2016, all pages. |
U.S. Appl. No. 14/967,371, filed Dec. 14, 2015, Notice of Allowance dated Aug. 29, 2016, all pages. |
U.S. Appl. No. 14/967,371, filed Dec. 14, 2015, Non-Final Office Action dated May 3, 2016, all pages. |
U.S. Appl. No. 14/967,370, filed Dec. 14, 2015, Notice of Allowance dated Aug. 30, 2016, all pages. |
U.S. Appl. No. 14/967,370, filed Dec. 14, 2015, Non-Final Office Action dated Apr. 29, 2016, all pages. |
U.S. Appl. No. 14/967,368, filed Dec. 14, 2015, Non-Final Office Action dated Apr. 22, 2016, all pages. |
U.S. Appl. No. 14/967,366, filed Dec. 14, 2015, Final Office Action dated Aug. 31, 2016, all pages. |
U.S. Appl. No. 14/967,366, filed Dec. 14, 2015, Non-Final Office Action dated Apr. 7, 2016, all pages. |
U.S. Appl. No. 14/967,364, filed Dec. 14, 2015, Final Office Action dated Aug. 2, 2016, all pages. |
U.S. Appl. No. 14/967,364, filed Dec. 14, 2015, Non-Final Office Action dated Mar. 7, 2016, all pages. |
U.S. Appl. No. 14/967,359, filed Dec. 14, 2015, Non-Final Office Action dated Apr. 1, 2016, all pages. |
U.S. Appl. No. 14/967,357, filed Dec. 14, 2015, Final Office Action dated Sep. 29, 2016, all pages. |
U.S. Appl. No. 14/967,357, filed Dec. 14, 2015, Non-Final Office Action dated Jun. 3, 2016, all pages. |
U.S. Appl. No. 14/967,356, filed Dec. 14, 2015, Final Office Action dated Aug. 3, 2016, all pages. |
U.S. Appl. No. 14/967,356, filed Dec. 14, 2015, Non-Final Office Action dated Apr. 15, 2016, all pages. |
U.S. Appl. No. 14/883,621, filed Oct. 15, 2015, Notice of Allowance dated Sep. 14, 2016, all pages. |
U.S. Appl. No. 14/883,621, filed Oct. 15, 2015, Non-Final Office Action dated Apr. 25, 2016, all pages. |
U.S. Appl. No. 14/883,605, filed Oct. 14, 2015, Notice of Allowance dated Aug. 31, 2016, all pages. |
U.S. Appl. No. 14/883,605, filed Oct. 14, 2015, Non-Final Office Action dated Apr. 14, 2016, all pages. |
U.S. Appl. No. 14/883,599, filed Oct. 14, 2015, Non-Final Office Action dated Apr. 5, 2016, all pages. |
U.S. Appl. No. 14/842,803, filed Sep. 1, 2015, Notice of Allowance dated Sep. 12, 2016, all pages. |
U.S. Appl. No. 14/842,803, filed Sep. 1, 2015, Non-Final Office Action dated Apr. 29, 2016, all pages. |
U.S. Appl. No. 14/821,789, filed Aug. 10, 2015, Non-Final Office Action dated Oct. 17, 2016, all pages. |
U.S. Appl. No. 14/816,065, filed Aug. 3, 2015, Notice of Allowance dated Aug. 26, 2016, all pages. |
U.S. Appl. No. 14/816,065, filed Aug. 3, 2015, Non-Final Office Action dated May 3, 2016, all pages. |
U.S. Appl. No. 14/816,064, filed Aug. 3, 2015, Notice of Allowance dated Aug. 31, 2016, all pages. |
U.S. Appl. No. 14/816,064, filed Aug. 3, 2015, Non-Final Office Action dated Apr. 29, 2016, all pages. |
U.S. Appl. No. 14/748,210, filed Jun. 23, 2015, Notice of Allowance dated Jun. 3, 2016, all pages. |
Shema Ann Mathew et al: “A smart wireless battery monitoring system for Electric Vehicles” Intelligent Systems Design and Applications (ISDA), 2012 12TH International Conference on, IEEE, Nov. 27, 2012 (Nov. 27, 2012), pp. 189-193. |
Matthias Schneider et al: “Automotive battery monitoring by wireless cell sensors”, 2013 IEEE International Instrumentation and Measurement Technology Conference (I2MTC) IEEE, May 13, 2012 (May 13, 2012), pp. 816-820. |
Damian Alonso et al: “Towards a Wireless Battery Management System: Evaluation of Antennas and Radio Channel Measurements Inside a Battery Emulator”, 2014 IEEE 80th Vehicular Technology Conference (VTC2014—Fall), Sep. 2014 (Sep. 2014), pp. 1-5. |
Roscher Valentin et al: “Synchronisation using wireless trigger-broadcast for impedance spectroscopy of battery cells” 2015 IEEE Sensors Applications Symposium (SAS), IEEE; Apr. 13, 2015 (Apr. 13, 2015), pp. 1-6. |
European Search Report dated Aug. 30, 2016 in European Patent Application No. 16160450.9, all pages. |
European Search Report for EP 16160467 dated Jul. 22, 2016, all pages. |
European Search Report for EP 16160441 dated Jul. 7, 2016, all pages. |
European Search Report for EP 16160486 dated Jul. 6, 2016, all pages. |
Specification for U.S. Appl. No. 62/133,991, filed Mar. 16, 2015, Inventor: Lai, et al., all pages. |
Specification for U.S. Appl. No. 62/150,848, filed Apr. 22, 2015, Inventor: Lai, et al., all pages. |
U.S. Appl. No. 14/967,359, filed Dec. 14, 2015, Final Rejection dated Nov. 7, 2016, all pages. |
U.S. Appl. No. 14/967,360, filed Dec. 14, 2015, Non-Final Rejection dated Dec. 1, 2016, all pages. |
U.S. Appl. No. 14/967,364, filed Dec. 14, 2015, Notice of Allowance dated Nov. 22, 2016, all pages. |
U.S. Appl. No. 15/006,126, filed Jan. 26, 2016, Non-Final Rejection dated Jul. 25, 2016, all pages. |
U.S. Appl. No. 15/006,126, filed Jan. 26, 2016, Notice of Allowance dated Nov. 7, 2016, all pages. |
Extended European Search Report dated Jul. 28, 2016, for European Patent Application No. 16160393.1, 9 pages. |
Final Office Action dated Aug. 3, 2016, for U.S. Appl. No. 14/967,360, 21 pages. |
Non-Final Office Action dated Apr. 4, 2016, for U.S. Appl. No. 14/967,360, 14 pages. |
Non-Final Office Action dated Aug. 8, 2016, for U.S. Appl. No. 15/063,435, 9 pages. |
U.S. Appl. No. 14/883,599, filed Oct. 14, 2015, Non-Final Rejection dated Mar. 24, 2017, all pages. |
Office Action for European Application No. 16 160 393.1 dated Aug. 4, 2017, 6 pages. |
First Office Action with Search Report for CN Appln. No. 201610146881 dated Nov. 6, 2017, 10 pages. |
U.S. Appl. No. 15/215,254, filed Jul. 20, 2016, Non-Final Rejection dated Sep. 18, 2017, all pages. |
U.S. Appl. No. 15/230,293, filed Aug. 5, 2016, Notice of Allowance dated Oct. 3, 2017, all pages. |
U.S. Appl. No. 14/883,599, filed Oct. 14, 2015, Final Rejection dated Oct. 5, 2017, all pages. |
U.S. Appl. No. 14/967,360, filed Dec. 14, 2015, Notice of Allowance dated Jun. 19, 2017, all pages. |
Number | Date | Country | |
---|---|---|---|
20160272082 A1 | Sep 2016 | US |
Number | Date | Country | |
---|---|---|---|
62150848 | Apr 2015 | US | |
62133991 | Mar 2015 | US |