Description:TECHNICAL FIELD
[0001] The present disclosure relates, in general, to battery management in vehicles. Particularly, the present disclosure relates to a method of preventing battery usage for the vehicle starting purpose during a low State of Charge (SOC) condition of the battery.
BACKGROUND
[0002] The function of battery in a vehicle is to provide the electrical power supply to different electrical loads as per defined logic for respective vehicle systems. The battery is one of the critical components, which plays a major role in vehicle starting system. In an engine-based vehicle, there may be chances of low battery State of Charge (SOC). If the vehicle is cranked in the low battery and/or low SOC condition, starter motor and associated circuits of the vehicle get overloaded, drawing maximum current and subsequently causing failure of starting and charging system of the vehicle.
[0003] Also, the battery has different failure modes in various field conditions. During the vehicle usage, there may be the chances of battery abuse due to low battery SOC condition. Consequently, when the battery SOC is below a certain threshold limit, the vehicle will not get started. If a user of the vehicle tries to start the engine in the low battery SOC condition, the starter motor windings get overheated and components like armature, field coil etc., may also get burn out. This will, in turn, impact starting of the vehicle, causing inconvenience to the users of the vehicle.
[0004] The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
SUMMARY
[0005] Disclosed herein is a method of preventing battery usage for vehicle starting purpose during low State of Charge (SOC) condition of the battery in the vehicle. The method comprises determining, by a control module, an ignition off time of the vehicle based on a position of an ignition switch of the vehicle. Further, the method comprises determining an Open Circuit Voltage (OCV) value of the battery when the ignition off time is greater than a predefined duration. Thereafter, the method comprises determining a low SOC condition of the battery by determining if the OCV value is less than a predefined OCV value, determining if a battery dip voltage during cranking of vehicle engine is less than a predefined dip voltage and determining if an average cranking voltage is less than a threshold cranking voltage for a threshold time period from the cranking of the vehicle engine. Finally, the method comprises generating an alert upon determining the low SOC condition to prevent the battery usage for the vehicle starting purpose during the low SOC condition.
[0006] Further, the present disclosure relates to a control module for preventing battery usage for vehicle starting purpose during low State of Charge (SOC) condition of the battery in the vehicle. The control module is configured to determine an ignition off time of the vehicle based on a position of an ignition switch of the vehicle. Further, the control module is configured to determine an Open Circuit Voltage (OCV) value of the battery when the ignition off time is greater than a predefined duration. Thereafter, the control module is configured to determine a low SOC condition of the battery by determining if the OCV value is less than a predefined OCV value, determining if a battery dip voltage during cranking of vehicle engine is less than a predefined dip voltage and determining if an average cranking voltage is less than a threshold cranking voltage for a threshold time period from the cranking of the vehicle engine. Finally, the control module is configured to generate an alert upon determining the low SOC condition to prevent the battery usage for the vehicle starting purpose during the low SOC condition.
[0007] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
[0008] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate exemplary embodiments and, together with the description, explain the disclosed principles. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the figures to reference like features and components. Some embodiments of system and/or methods in accordance with embodiments of the present subject matter are now described, by way of example only, and regarding the accompanying figures, in which:
[0009] FIG. 1 shows an overview of functioning of the proposed control module, in accordance with some embodiments of the present disclosure.
[0010] FIG. 2 shows a detailed block diagram of the proposed control module, in accordance with some embodiments of the present disclosure.
[0011] FIG. 3A shows a flowchart illustrating a method of preventing battery usage for vehicle starting purpose during low State of Charge (SOC) condition of the battery in the vehicle, in accordance with some embodiments of the present disclosure.
[0012] FIG. 3B shows a flowchart illustrating a method of determining a low SOC condition of the battery, in accordance with some embodiments of the present disclosure.
[0013] FIG. 4 shows a system level architecture of the vehicle, in accordance with some embodiments of the present disclosure.
[0014] It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and executed by a computer or processor, whether such computer or processor is explicitly shown.
DETAILED DESCRIPTION
[0015] In the present document, the word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or implementation of the present subject matter described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
[0016] While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the specific forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the scope of the disclosure.
[0017] The terms “comprises”, “comprising”, “includes”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the system or method.
[0018] A vehicle may remain in an idle condition for a long duration. During this time, the battery will get discharged due to leakage current consumption from multiple vehicle controllers. This leakage current impacts battery State of charge (SOC), a battery voltage, internal resistance of the battery and the like. During ignition off condition, some of the vehicle loads will continuously consume current through the battery, which is called the leakage current. This reduces the battery Open Circuit Voltage (OCV). The reduction in the OCV results into the reduction of battery SOC. Also, if the leakage current persists for a longer time, the battery drains quickly. If the vehicle starter gets operated at this condition with low voltage battery input, the starter tries to consume more current through the battery and the battery will not be able to provide the suf?cient power to the engine during the starting of the engine.
[0019] In an embodiment, using the ignition off time input and position of an ignition switch, the vehicle idle condition time can be estimated. The present disclosure determines the OCV value based on vehicle idle time. Further, based on the OCV value, the battery SOC may be predicted. If the OCV value is less than the predefined OCV value, the control module may generate an alert and also generate a Diagnostic Trouble Code (DTC) and store the DTC in the memory for low SOC condition. The alert helps in preventing the cranking of the starter motor. Further, if the OCV value is at a boundary limit, then cranking may be possible. In this condition, a voltage dip due to starter inrush current will be monitored. If the dip voltage is less than a predefined dip voltage, then the alert may be generated, and the DTC will be raised and stored in the memory for low SOC condition, thereby preventing the starter motor cranking. Furthermore, if the dip voltage is just above the battery limit, then an average battery voltage may be monitored during the cranking. If the battery voltage gets dropped below a threshold cranking voltage for a threshold time period from the cranking of the vehicle engine, then the alert may be generated and the DTC will be raised and stored in the memory for low SOC condition, thereby preventing the starter motor cranking. The DTC may be used by a technician to resolve the battery issue.
[0020] In other words, the present disclosure aims to prevent battery usage for the vehicle starting purpose during the low State of Charge (SOC) condition and alerting the user. That is, the proposed disclosure determines a low SOC condition before cranking of the engine, during cranking of the engine and after cranking of the engine.
[0021] In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.
[0022] FIG. 1 shows an overview of functioning of the proposed control module in accordance with some embodiments of the present disclosure.
[0023] In an embodiment, a vehicle may be configured with a control module 101 and the control module 101 may be configured for preventing battery usage for the vehicle starting purpose during a low State of Charge (SOC) condition of the battery in the vehicle. As an example, the vehicle may be a passenger vehicle such as a car, a van, a bus and/or a commercial vehicle such as pick-up trucks. In an embodiment, the control module 101 may be a computing unit dedicated for preventing battery usage during low SOC condition of the battery in the vehicle. In an embodiment, the control module 101 may be communicatively interfaced with an Electronic Control Unit (ECU) 105 of the vehicle through Controller Area Network (CAN) communication 103 for exchanging any data/instructions with the ECU 105 during operation of the control module 101. In an embodiment, an existing ECU 105 of the vehicles may be upgraded to perform functionalities of the control module 101, in accordance with the embodiments of the present disclosure. Alternatively, the control module 101 may be configured on a remote system, such that the control module 101 is communicatively connected to the vehicle (for example, via a wireless network and/or over Internet) for continuously monitoring the status of the battery SOC and subsequently prevent usage of the battery during the low SOC condition.
[0024] In an embodiment, the control module 101 may be configured to determine an ignition off time of the vehicle based on a position of ignition switch 107 of the vehicle. In an embodiment, when the ignition off time is greater than a predefined duration, an Open Circuit Voltage (OCV) value of the battery is determined by the Control module 101. As an example, the predefined duration may be 2 hours. That is, if the vehicle is turned off for more than 2 hours, the OCV value may be determined. In an embodiment, the OCV value may be used to predict a State of Charge (SOC) value.
[0025] In an embodiment, after determining the OCV value of the battery, the control module 101 determines a low SOC condition of the battery. In an embodiment, the control module 101 determines if the OCV value is less than a predefined OCV value. In an embodiment, if the OCV value is less than the predefined OCV value then the control module 101 determines that the battery is in the low SOC condition. Further, the control module 101 generates an alert using an alert generation module 109.
[0026] In an embodiment, after determining that the OCV value is less than the predefined OCV value, the control module 101 determines if a battery dip voltage during cranking of the vehicle engine is less than a predefined dip voltage. As an example, the predefined dip voltage may be equal to and/or greater than 6.5 Volts (V). In an embodiment, before cranking of an engine of the vehicle, if the OCV value is not less than the predefined OCV value, the control module 101 may allow cranking and/or engine cranking of the vehicle. As an example, the predefined OCV value may be in a predetermined range of 8 Volts (V) to 10V. In an embodiment, when the user of the vehicle turns ON the vehicle, the cranking of the starter motor may consume a high inrush current from the battery as an input power. In an embodiment, during the high inrush current the battery voltage may go at a lowest point during starter motor engagement. In an embodiment, if the battery dip voltage during cranking of vehicle engine is less than the predefined dip voltage, the alert generation module 109 may generate the alert upon determining the low SOC condition to prevent the battery usage for a vehicle starting purpose during the low SOC condition.
[0027] In an embodiment, after determining the battery dip voltage during cranking of the engine, the control module 101 determines if an average cranking voltage is less than a threshold cranking voltage for a threshold time period from the cranking of the vehicle engine. As an example, the threshold cranking voltage may be 5 Volts (V) and the threshold time period may be 50 milliseconds (ms). In an embodiment, if the battery dip voltage during cranking of vehicle engine is greater than the predefined dip voltage, the control module 101 may allow engine cranking of the vehicle. In an embodiment, during engine cranking of the vehicle, the starter may consume more current than the normal cranking current to maintain a required torque. In an embodiment, if the OCV value is low, the required power may not be supplied to the starter motor. In an embodiment, if the average cranking voltage is less than the threshold cranking voltage for the threshold time period from the cranking of the vehicle engine and if the vehicle engine has not reached a predefined idle Revolutions Per Minute (RPM) count, the alert generation module 109 may generate the alert upon determining the low SOC condition to prevent the battery usage for a vehicle starting purpose during the low SOC condition. As an example, the predefined RPM may be 2000 RPM. Further, the control module 101 prevents subsequent cranking of the vehicle engine when the RPM count of the vehicle engine is less than the predefined idle RPM count. In an embodiment, if the RPM count of the vehicle engine is more than the predefined idle RPM count, the control module 101 may facilitate charging of the battery using an alternator associated with the battery.
[0028] In an embodiment, upon determining the low SOC condition of the battery, the control module 101 generates the alert to prevent the battery usage for the vehicle starting purpose during the low SOC condition. In an embodiment, the alert may be generated by the alert generation module 109. In an embodiment, the alert may be notified to the user of the vehicle using at least one of a voice messaging system configured in the vehicle, an infotainment system of the vehicle and a cloud computing service configured in the vehicle. As an example, the voice messaging system may alert the user of the vehicle by playing a pre-recorded and/or prestored alert message. Alternatively, the infotainment system may show a message alerting the user of the vehicle about the low SOC condition. Similarly, the cloud computing service configured in the vehicle may alert the user of the vehicle through a mobile application notification, a web page alert and/or by sending an alert message on an instant messaging application used by the user. As an example, the alert about the low SOC condition may be provided on one or more smart devices (such as a smartwatch) worn by the user.
[0029] In an embodiment, in addition to the alerts, the control module 101 may also generate a Diagnostic Trouble Code (DTC) corresponding to one or more issues causing the low SOC condition. In an embodiment, the DTC may be stored in a memory associated with the control module 101 and may be accessed by a technician of the vehicle for analysis through an On-Board Diagnostics (OBD) technique. In an embodiment, after the engine of the vehicle is started, the DTC may be cleared from the memory.
[0030] FIG. 2 shows a detailed block diagram of a control module 101, in accordance with some embodiments of the present disclosure.
[0031] In an embodiment, the control module 101 may include an I/O Interface 201 and a memory 202. 202The I/O interface 201 may be configured for receiving and transmitting an input signal or/and an output signal related to one or more operations of the control module 101. In an embodiment, the memory 202 may store data 203 and one or more modules 205 of the control module 101.
[0032] In an embodiment, the data 203 stored in the memory 202 may include, without limitation, values/texts related to an alert 207, an Open Circuit Voltage (OCV) 209, a predefined duration 211, a predefined OCV value 213, a predefined dip voltage 215, a threshold cranking voltage 217 and other data 219. In some implementations, the data 203 may be stored within the memory 202 in the form of various data structures. Additionally, the data 203 may be organized using data models, such as relational or hierarchical data models. The other data 219 may include various temporary data and files generated by the different components of the control module 101.
[0033] In an embodiment, the alert 207 may be generated by an alert generation module 109 to notify a user of the vehicle about the low SOC condition, to prevent the battery usage for the vehicle starting purpose during the low SOC condition. In an embodiment, the alert may be notified to the user of the vehicle using at least one of a voice messaging system configured in the vehicle, an infotainment system of the vehicle or a cloud computing service configured in the vehicle.
[0034] In an embodiment, the OCV value 209 is a value associated with the battery, which may be used to determine the State of Charge (SOC) value. In an embodiment, the OCV value 209 of the battery may be determined when the ignition off time is greater than a predefined duration 211.
[0035] In an embodiment, the predefined duration 211 is a duration corresponding to the ignition off time. In an embodiment, the control module 101 determines the OCV value 209 only when the ignition off time is greater than the predefined duration 211. As an example, the predefined duration 211 may be 2 hours.
[0036] In an embodiment, the predefined OCV value 213 is a voltage value corresponding to the battery of the vehicle. In an embodiment, when the OCV value 209 is less than the predefined OCV value 213, a low SOC condition may be determined. As an example, the predefined OCV value 213 may be in a predetermined range of 8V to 10V.
[0037] In an embodiment, the predefined dip voltage 215 is a voltage value of the battery of the vehicle when the user is cranking the engine. In an embodiment, when a dip voltage is less than the predefined dip voltage 215, the low SOC condition may be determined. As an example, the predefined dip voltage 215 may be equal and greater than 6.5 Volts (V).
[0038] In an embodiment, the threshold cranking voltage 217 is a voltage value of the battery of the vehicle after cranking of the engine to maintain a predefined idle Revolutions Per Minute (RPM) count. In an embodiment, when an average cranking voltage is less than the threshold cranking voltage 217, the low SOC condition may be determined. As an example, the threshold cranking voltage 217 may be 5 Volts (V).
[0039] In an embodiment, the data 203 may be processed by the one or more modules 205 of the control module101. In some implementations, the one or more modules 205 may be communicatively coupled to the ECU 105 for performing one or more functions of the control module 101. In an implementation, the one or more modules 205 may include, without limiting to, an ignition switch 107, a determining module 211, an alert generation module 109 and other modules 223. In an embodiment, the other modules 223 may be used to perform various miscellaneous functionalities of the control module 101. It will be appreciated that such one or more modules 205 may be represented as a single module or a combination of different modules.
[0040] In an embodiment, the ignition switch 107 may be used for determining an ignition off time of the vehicle. In an embodiment, the determining module 211 may be configured for determining an Open Circuit Voltage (OCV) value 209 of the battery when the ignition off time is greater than a predefined duration 211. Further, the determining module 211 may be configured to determine a low SOC condition of the battery. The low SOC condition of the battery may be determined when the OCV value 209 is less than a predefined OCV value 213, or a battery dip voltage during cranking of vehicle engine is less than a predefined dip voltage 215 and/or when an average cranking voltage is less than a threshold cranking voltage 217 for a threshold time period from the cranking of the vehicle engine. In an embodiment, the alert generation module 109 may be configured for generating an alert 207 upon determining the low SOC condition to prevent the battery usage for the vehicle starting purpose during the low SOC condition. In an embodiment, the alert generation module 109 notifies the user using at least one of a voice messaging system configured in the vehicle, an infotainment system of the vehicle or a cloud computing service configured in the vehicle. Further, the alert generation module 109 generates a Diagnostic Trouble Code (DTC) corresponding to one or more issues causing the low SOC condition.
[0041] FIG. 3A shows a flowchart illustrating a method of preventing battery usage for vehicle starting purpose during low State of Charge (SOC) condition of the battery in the vehicle, in accordance with some embodiments of the present disclosure.
[0042] As illustrated in FIG. 3A, the method 300 may include one or more blocks illustrating a method of preventing battery usage for vehicle starting purpose during low State of Charge (SOC) condition of the battery in the vehicle. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, and functions, which perform specific functions or implement specific abstract data types.
[0043] The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or combination thereof.
[0044] At block 301, the method 300 includes determining, by a control module 101, an ignition off time of the vehicle based on a position of an ignition switch 107.
[0045] At block 303, the method 300 includes determining, by the control module 101, an Open Circuit Voltage (OCV) value 209 of the battery when the ignition off time is greater than a predefined duration 211. In an embodiment, when the ignition off time is greater than the predefined duration 211 the control module 101 may allow engine cranking of the vehicle.
[0046] At block 305, the method 300 includes determining, by the control module 101, a low SOC condition of the battery. In an embodiment, the SOC may be predicted using the OCV value 209. In an embodiment, the low SOC condition may be due to at least one of the OCV value 209 is less than a predefined OCV value 213, a battery dip voltage during cranking of vehicle engine is less than a predefined dip voltage 215 and an average cranking voltage is less than a threshold cranking voltage 217 for a threshold time period from the cranking of the vehicle engine.
[0047] At block 307, the method 300 includes generating, by the control module 101, an alert 207 upon determining the low SOC condition to prevent the battery usage for a vehicle starting purpose during the low SOC condition. In an embodiment, generating the alert 207 may also comprise generating a Diagnostic Trouble Code (DTC) corresponding to one or more issues causing the low SOC condition. In an embodiment, the alert 207 may be notified to a user of the vehicle using at least one of a voice messaging system configured in the vehicle, an infotainment system of the vehicle or a cloud computing service configured in the vehicle.
[0048] FIG. 3B shows a flowchart illustrating a method of determining a low SOC condition of the battery, in accordance with some embodiments of the present disclosure.
[0049] In an embodiment, at step 323, it is checked if an ignition off time of the vehicle is greater than a predefined duration 211. In an embodiment, if the ignition off time is less than the predefined duration 211, the vehicle operation will continue as per normal operations (step 325). Alternatively, if the ignition of time is greater than the predefined duration 211, the battery OCV value 209 is determined. At step 327, the battery OCV value 209 is compared with the predefined OCV value 213. In an embodiment, if the OCV value 209 is less than the predefined OCV value 213, the control module 101 may not allow cranking of the engine and an error is generated and stored in the memory 202 (step 329). On the other hand, if the OCV value 209 is more than the predefined OCV value 213, the control module 101 checks if the engine is cranked and if the battery dip voltage is less than a predefined dip voltage 215 (step 331). In an embodiment, at step 333, if the battery dip voltage is less than the predefined dip voltage 215, the error is generated and stored in the memory 202. Alternatively, in step 335, if the battery voltage dip is more than the predefined dip voltage 215, then the control module 101 determines an average cranking voltage. Further, in step 337, the average cranking voltage is compared with threshold cranking voltage 217 for a threshold time period from the cranking of the vehicle engine. In an embodiment, if the average cranking voltage is more than the threshold cranking voltage 217, the vehicle operation will continue as per normal operations (step 337). Alternative, at step 339, when the average cranking voltage is less than threshold cranking voltage 217, the control module 101 checks if the engine has reached a predefined idle Revolutions Per Minute (RPM). If the engine has not reached the predefined idle RPM, the control module 101 will not allow the next crank and the error is generated and stored in the memory 202. In an embodiment, if the engine has reached the predefined idle RPM, an alternator is used to charge the battery.
[0050] FIG. 4 shows a system level architecture of the vehicle, in accordance with some embodiments of the present disclosure.
[0051] In an embodiment, the control module 101 may use a cloud computing service 415 to alert low battery State of Charge (SOC) condition to a user of the vehicle. The cloud computing service 415 may send a notification to the user on a user device. Also, the control module 101 may communicate with a voice messaging system 411 using Controller Area Network (CAN) communication 103. The voice messaging system 411 may alert the user through a voice message. Also, the battery 403 management unit 101 may communicate with an infotainment system 413 to display an alert message to the user of the vehicle. In an embodiment, the crank position sensor 107 is used to determine the ignition off time of a vehicle. In an embodiment, the starter motor 405 is used to determine cranking of the engine. The ignition switch 107 is used to turn ON/OFF the vehicle. In an embodiment, one or more electric loads 409 may consume current from the battery 403 when the vehicle is in the ON/OFF state. In an embodiment, an alternator 407 may be used to charge the battery 403 after the vehicle is turned ON and required RPM has been reached.
[0052] Advantages of the embodiments of the present disclosure are illustrated herein.
[0053] In an embodiment, the present disclosure determines low State of Charge (SOC) battery condition in the vehicles. This helps in preventing battery abuse and overheating of starter motor windings.
[0054] In an embodiment, the present disclosure generates a Diagnostic Trouble Code (DTC). This helps in determining a root cause for the failure and also improve the reliability of the battery.
[0055] In an embodiment, the present disclosure determines the cause of the vehicle breakdown. This helps in determining if the breakdown is due to battery abuse.
[0056] In light of the technical advancements provided by the disclosed method and the control module, the claimed steps, as discussed above, are not routine, conventional, or well-known aspects in the art, as the claimed steps provide the aforesaid solutions to the technical problems existing in the conventional technologies. Further, the claimed steps clearly bring an improvement in the functioning of the system itself, as the claimed steps provide a technical solution to a technical problem.
[0057] The terms "an embodiment", "embodiment", "embodiments", "the embodiment", "the embodiments", "one or more embodiments", "some embodiments", and "one embodiment" mean "one or more (but not all) embodiments of the invention(s)" unless expressly specified otherwise.
[0058] The terms "including", "comprising", “having” and variations thereof mean "including but not limited to", unless expressly specified otherwise.
[0059] The enumerated listing of items does not imply that any or all the items are mutually exclusive, unless expressly specified otherwise. The terms "a", "an" and "the" mean "one or more", unless expressly specified otherwise.
[0060] A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary, a variety of optional components are described to illustrate the wide variety of possible embodiments of the invention.
[0061] When a single device or article is described herein, it will be clear that more than one device/article (whether they cooperate) may be used in place of a single device/article. Similarly, where more than one device/article is described herein (whether they cooperate), it will be clear that a single device/article may be used in place of the more than one device/article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of invention need not include the device itself.
[0062] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based here on. Accordingly, the embodiments of the present invention are intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
[0063] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Referral Numerals:
Reference Number Description
101 Control module
103 Controller Area Network (CAN) communication
105 Electronic Control Unit (ECU)
107 Ignition switch
109 Alert generation module
201 I/O Interface
202 Memory
203 Data
205 Modules
207 Alert
209 Open Circuit Voltage value
211 Predefined duration
213 Predefined OCV value
215 Predefined dip voltage
217 Threshold cranking voltage
219 Other data
221 Determining module
223 Other modules
400 Vehicle level system architecture
403 Battery
405 Starter motor
407 Alternator
409 Electric loads
411 Voice messaging system
413 Infotainment system
415 Cloud computing service
417 Cloud communication
, Claims:WE CLAIM:

1. A method of preventing battery usage for vehicle cranking during low State of Charge (SOC) condition of the battery in the vehicle, the method comprising:
determining, by a control module, an ignition off time of the vehicle based on a position of an ignition switch of the vehicle;
determining, by the control module, an Open Circuit Voltage (OCV) value of the battery when the ignition off time is greater than a predefined duration;
determining, by the control module, a low SOC condition of the battery by:
determining if the OCV value is less than a predefined OCV value;
determining if a battery dip voltage during cranking of vehicle engine is less than a predefined dip voltage; and
determining if an average cranking voltage is less than a threshold cranking voltage for a threshold time period from the cranking of the vehicle engine; and
generating, by the control module, an alert upon determining the low SOC condition to prevent the battery usage for the vehicle starting purpose during the low SOC condition.

2. The method as claimed in claim 1, wherein generating the alert comprises generating a Diagnostic Trouble Code (DTC) corresponding to one or more issues causing the low SOC condition.

3. The method as claimed in claim 2, wherein generating the alert further comprises notifying the alert to a user of the vehicle using at least one of a voice messaging system configured in the vehicle, an infotainment system of the vehicle or a cloud computing service configured in the vehicle.

4. The method as claimed in claim 1, wherein determining the average cranking voltage further comprises verifying if the vehicle engine has reached a predefined idle Revolutions Per Minute (RPM) count.

5. The method as claimed in claim 4 further comprises:
preventing subsequent cranking of the vehicle engine when the RPM count of the vehicle engine is less than the predefined idle RPM count; or
facilitating charging of the battery using an alternator of the vehicle when the RPM count of the vehicle engine is more than the predefined idle RPM count.

6. A control module to prevent battery usage for vehicle cranking during low State of Charge (SOC) condition of the battery in the vehicle, the control module configured to:

determine an ignition off time of the vehicle based on a position of an ignition switch of the vehicle;
determine an Open Circuit Voltage (OCV) value of the battery when the ignition off time is greater than a predefined duration;
determine a low SOC condition of the battery by:
determining if the OCV value is less than a predefined OCV value;
determining if a battery dip voltage during cranking of vehicle engine is less than a predefined dip voltage; and
determining if an average cranking voltage is less than a threshold cranking voltage for a threshold time period from the cranking of the vehicle engine; and
generate an alert upon determining the low SOC condition to prevent the battery usage for the vehicle starting purpose during the low SOC condition.

7. The control module as claimed in claim 6, wherein the control module generates the alert by generating a Diagnostic Trouble Code (DTC) corresponding to one or more issues causing the low SOC condition.

8. The control module as claimed in claim 7, wherein generating the alert by the control module further comprises notifying the alert to a user of the vehicle using at least one of a voice messaging system configured in the vehicle, an infotainment system of the vehicle or a cloud computing service configured in the vehicle.

9. The control module as claimed in claim 6, wherein determining the average cranking voltage by the control module further comprises verifying if the vehicle engine has reached a predefined idle Revolutions Per Minute (RPM) count.

10. The control module as claimed in claim 9 further comprises:
preventing subsequent cranking of the vehicle engine when the RPM count of the vehicle engine is less than the predefined idle RPM count; or
facilitating charging of the battery using an alternator of the vehicle when the RPM count of the vehicle engine is more than the predefined idle RPM count.