Electronic devices for use in a vehicle and methods of operating the same

Information

  • Patent Grant
  • 10850690
  • Patent Number
    10,850,690
  • Date Filed
    Monday, July 16, 2018
    5 years ago
  • Date Issued
    Tuesday, December 1, 2020
    3 years ago
Abstract
An electronic device for use in a vehicle and method for controlling the same are provided. The device includes a battery sensor configured to detect a battery voltage when connected to a vehicle's battery, and a processor in communication with the battery sensor. The processor is configured to monitor the battery voltage of a vehicle's battery using the battery sensor and identify at least one transition in the battery voltage. The processor is also configured to determine an operational state of the vehicle based on the transition and the battery voltage, and control the electronic device in accordance with the operational state of the vehicle.
Description
REFERENCE REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable


SEQUENTIAL LISTING

Not applicable


BACKGROUND
1. Field of the Invention

The present disclosure generally relates to automotive applications, and more specifically, to electronic devices for use in a vehicle and methods of operating the same.


2. Description of the Background of the Invention

Many modern electronic devices, including cell phones, tablets, laptops, and others, are often recharged using vehicle power. In addition, individuals often utilize personal volatile emitting devices in their vehicles, such as air fresheners, odor eliminators, or other devices designed to assist in eliminating pests, cleaning, or freshening the surrounding environment. In particular, many volatile emitting devices include a heat source or fan that that assist in the dispersion or release of the volatile from a cartridge. To operate heating elements, fans, and other circuitry, volatile emitting devices and other devices are designed to utilize power from the 12V accessory outlet of the vehicle.


However, many electronic devices may continue to draw power even after the vehicle has been turned off. If left connected for an extended period of time, this can result in unwanted battery drain and perhaps vehicle incapacitation, particularly for devices that draw high power. In the case of personal volatile emitting devices, volatiles may also be depleted prematurely. To avoid such difficulties, some technologies have attempted to include capabilities for determining whether a vehicle is on or off by incorporating vibration sensors, for instance. However, vibration sensors can produce errors due to their inability to discriminate vibrations unrelated to vehicle operation. In addition, vibration sensors increase device cost and design complexity.


Therefore, a need exists for a low cost, reliable way of controlling electronic devices based on the operational state of a vehicle.


SUMMARY

The present disclosure overcomes drawbacks of previous technologies. Features and advantages of the present disclosure will become apparent from the following description.


In one aspect of the present disclosure, a method for controlling an electronic device for use in a vehicle is provided. The method includes the steps of detecting a battery voltage of a vehicle's battery using a battery sensor connected thereto, and determining an operational state of the vehicle using the battery voltage. The method also includes the step of controlling an electronic device coupled to the vehicle's battery in accordance with the operational state of the vehicle.


In another aspect of the present disclosure, an electronic device for use in a vehicle is provided. The device includes a battery sensor configured to detect a battery voltage when connected to a vehicle's battery, and a processor in communication with the battery sensor. The processor is configured to sample the battery voltage detected by the battery sensor, and determine an operational state of the vehicle using the battery voltage. The processor is also configured to control the electronic device in accordance with the operational state of the vehicle.


In yet another aspect of the present disclosure, a volatile emitting device for use in a vehicle is provided. The device includes a cartridge having a volatile material therein and an electrical assembly. The device also includes a housing having a cavity configured to hold the cartridge and electrical assembly. The electrical assembly includes a battery sensor configured to detect a battery voltage when connected to a battery of the vehicle, and a processor in communication with the battery sensor. The processor is configured to sample the battery voltage detected by the battery sensor, and determine an operational state of the vehicle using the battery voltage. The processor is also configured to control a release of the volatile material in accordance with the operational state of the vehicle.


In yet another aspect of the present disclosure, a method for controlling an electronic device for use in a vehicle is provided. The method includes monitoring a battery voltage of a vehicle's battery using a battery sensor connected thereto, and identifying at least one transition in the battery voltage using a processor in communication with the battery sensor. The method also includes determining, using the processor, an operational state of the vehicle based on the transition and the battery voltage, and controlling, using the processor, an electronic device coupled to the vehicle's battery in accordance with the operational state of the vehicle.


In still another aspect of the present disclosure, an electronic device for use in a vehicle is provided. The device includes a battery sensor configured to detect a battery voltage when connected to a vehicle's battery, and a processor in communication with the battery sensor. The processor is configured to monitor the battery voltage of a vehicle's battery using the battery sensor and identify at least one transition in the battery voltage. The processor is also configured to determine an operational state of the vehicle based on the transition and the battery voltage, and control the electronic device in accordance with the operational state of the vehicle.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a flowchart setting forth steps of a process, in accordance with aspects of the present disclosure;



FIG. 2 is another flowchart setting forth steps of a process, in accordance with aspects of the present disclosure;



FIG. 3 is a schematic diagram of an electronic device, in accordance with aspects of the present disclosure;



FIG. 4 is a schematic diagram illustrating one embodiment of the electronic device shown in FIG. 3;



FIG. 5 is a schematic diagram of another embodiment, in accordance with aspects of the present disclosure;



FIG. 6 is perspective view of an example volatile emitting device, in accordance with aspects of the present disclosure;



FIG. 7 is a schematic diagram of an example electrical assembly implemented in the device shown in FIG. 6;



FIG. 8 is a flowchart setting forth steps of a process, in accordance with aspects of the present disclosure; and



FIG. 9 is a graphical illustration showing example battery voltages in different vehicle operation scenarios.





Other aspects and advantages of the present invention will become apparent upon consideration of the following detailed description, wherein similar structures have similar reference numerals.


DETAILED DESCRIPTION

The present disclosure is directed to a novel approach for controlling electronic devices for use in a vehicle. In particular, methods for operating devices based on the operational state of the vehicle are provided. As will become apparent from the description below, methods described herein may be advantageously implemented for a wide variety of electronic devices commonly used in vehicles, including volatile emitting devices, cell phones, tablets, laptops, GPS devices, navigation units, cameras, FM broadcasters, Bluetooth devices, AC adapters, video games, air compressors, and many others.


Referring to FIG. 1, steps of a process 100 are shown, which may be carried out using any suitable device, apparatus, or system, including devices described in the present disclosure. Steps of the process 100 may be implemented as a program, firmware, or executable instructions stored in non-transitory computer readable media.


The process 100 may begin at process block 102 by detecting a battery voltage of a vehicle's battery. The battery voltage may be detected using a battery sensor connected or connectable to the vehicle's battery. The battery sensor may be electrically connected, but need not be physically connected, to the vehicle's battery. As will be described, in some embodiments, the battery sensor may be incorporated into, or may be part of, various electronic devices, such as portable electronic devices, volatile emitting devices, and others. In other embodiments, the battery sensor may be part of the vehicle circuitry.


In some aspects, the battery voltage detected by the battery sensor may be sampled over a predefined period of time, either intermittently or periodically using a predefined sampling frequency. By way of example, the predefined period of time may range approximately between a few seconds and 30 minutes. However, in some implementations, the period of time may be less than a second or longer than 30 minutes. Also, the predefined sampling frequency may range between approximately 0.1 Hz, or less, and 10,000 Hz, or more.


As used herein, the term approximately, when referring to a numerical value, allows for a positive or a negative variation of the numerical value by up to and including 10% of the numerical value. The battery voltage may then be analyzed by a processor to generate various information therefrom. Such information may include, for instance, maximum battery voltage, minimum battery voltage, average battery voltage, battery voltage standard deviation, rate of change of the battery voltage, and so forth.


Then, at process block 104, an operational state of the vehicle may be determined based on the battery voltage detected. In some aspects, the battery voltage may be compared to one or more predefined thresholds. In addition, information obtained from the analyzed battery voltage samples may be compared to predefined signatures. Such thresholds and signatures may be obtained by measuring battery voltage in various vehicle operation scenarios.


In general, the battery voltage level depends on whether the vehicle's engine is on or off. As such, battery voltage may be used as an indicator of the operational state of the vehicle's engine. Specifically, when the engine is off, battery voltage can range up to (or approximately to) a nominal voltage of 12.6V, depending upon the battery's age and charge level. When the engine is on, the vehicle alternator charges the battery, and the battery voltage rises to the operating voltage of the vehicle alternator, which is typically greater than 13.0V. Therefore, a battery voltage above a threshold of approximately 13.0V may indicate an “ON” state of the vehicle's engine.


However, some “smart” alternators can also drive a vehicle battery at an operating voltage below 13.0V. For instance, the battery voltage may be close to a voltage corresponding to the engine being off. Therefore, a measurement below 13.0V might not conclusively indicate whether the vehicle is in an “ON” or “OFF” state. To differentiate between the two operational states, a load may be applied to the battery for a period of time while the battery voltage is monitored. Specifically, a change in the battery voltage may then be used to determine the state. For instance, if the battery voltage rises, does not change at all, does not appreciably change, or drops slower than a predetermined rate, then the battery is charging, and the vehicle is in an “ON” state. Otherwise, if the battery voltage drops faster than the predetermined rate, the battery is not charging and the vehicle's engine is in an “OFF” state.


The period of time for monitoring the battery voltage may vary from a few seconds, or less, to 30 minutes, or more. In some aspects, the period of time may depend on the load being applied, the sampling rate of the battery voltage, as well as the time required to observe any appreciable changes in the battery voltage, if they should occur. In other aspects, the period of time may also depend on the type of vehicle. For instance, a hybrid vehicle may automatically turn off its engine at stop lights, railroad crossings, and so on, to conserve resources. Therefore, a period of time sufficient to distinguish operational states in such scenarios would be advantageous. This would allow operation of an electronic device to continue without interruption.


Although the description above makes reference to the state of the vehicle's engine, the operational state of the vehicle determined at process block 104 may also refer to a state of the ignition, for instance, in accordance with a position of an ignition key.


Referring again to FIG. 1, an electronic device coupled to the vehicle's battery may then be controlled at process block 106 in accordance with the operational state of the vehicle. The process of controlling the device may include adapting one or more functions or operational aspects of the device. In some implementations, those functions or operational aspects of the device requiring substantial power from the vehicle's battery may be turned off or converted to a low-power mode if the vehicle is in an “OFF” state or the vehicle's battery is discharged below a predetermined threshold. In one example, charging of the electronic device using the vehicle's battery may be modified or interrupted if the vehicle is determined to be in an “OFF” state. In another example, an electronic device, or various components therein, relying on power from the vehicle's battery may be turned off or entered into a low-power mode. Specifically, power to a heating element, fan or USB port of a volatile emitting device may be interrupted or reduced. It may be appreciated that these examples are not limiting, and a wide variety of a device's functions or operational aspects may be controlled based on what the operational state of the vehicle is determined to be.


In some aspects, a report may be generated, as indicated by process block 108. The report may be in any form and include any information. The report may be provided to an output, and/or stored in a memory. For example, the report may be provided using a display and/or LEDs, and so forth, and indicate various battery voltages detected, a determined operational state of the vehicle, a condition of a device, a communication link, and other data or information.


Turning now to FIG. 2, another flowchart setting forth steps of a process 200, in accordance with aspects of the present disclosure, is shown. The process 200 may be carried out using any suitable device, apparatus, or system, including devices described in the present disclosure. Steps of the process 200 may be implemented as a program, firmware, or executable instructions stored in non-transitory computer readable media.


The process 200 may begin at process block 202 by detecting the battery voltage of a vehicle. As described, battery voltage may be detected using a battery sensor coupled to the vehicle's battery and sampled intermittently or periodically over a predetermined period of time. Then, a determination is made whether the battery voltage is above a threshold, as indicated by decision block 204. As an example, the threshold may be approximately 13.0V, although other thresholds may be possible.


The determination at decision block 204 can be made based on one or more battery voltage samples obtained at process block 202, as described. In one example, the determination may be made based on whether an average battery voltage is above the threshold. If the battery voltage, or average battery voltage, is above the threshold, one or more functions or operational aspects of an electronic device coupled to the battery may be executed, as indicated by process block 206. Example functions may include charging the device, operating a heating element, operating a fan, and so on.


If the battery voltage, or average battery voltage, is below the threshold, another determination may be optionally made, as indicated by decision block 208. Specifically, it may be determined whether the battery voltage, or average battery voltage, is below the threshold for a time T1. In one example, T1 may be approximately 30 minutes, although T1 could be longer or shorter, and may depend on the sampling rate of the battery voltage, vehicle type, and other factors, as mentioned. This could help avoid, for instance, incorrect determinations based on voltage spikes or other transients. If the battery voltage, or average battery voltage, persists below the threshold for the time T1, a load may then applied to the battery, as indicated by process block 210. Otherwise, process block 202 may be repeated, as desired.


The battery voltage may then be monitored for a time T2 at process block 212. For example, the battery voltage may be monitored for approximately one minute, or less, or more. Then, a determination is made at decision block 214 with respect to any changes in the battery voltage. Specifically, if the battery voltage, or average battery voltage, rises, does not appreciably change, does not change at all, or drops slower than a predetermined rate as a result of the applied load, then the battery is charging. Thus, the vehicle is in an “ON” state, as indicated by process block 216. Otherwise, if the battery voltage drops faster than the predetermined rate, then the battery is not charging, and the vehicle is in an “OFF” state, as indicated by process block 218.


In some preferred implementations, the applied load and/or duration T2 for monitoring the battery voltage at process blocks 210 and 212 may be configured such that a determination at decision block 214 can be made without adversely affecting the battery. For instance, the applied load and/or duration T2 may be selected to induce a detectable change in the battery voltage when the vehicle is in an “OFF” state, and without significantly discharging the battery.


As indicated by process block 220, one or more device functions or operational aspects may be stopped or modified if the vehicle is determined to be in an “OFF” state. In one non-limiting example, operation of a heating element or fan may be stopped or reduced. In another non-limiting example, the device may be placed into a low-power state or device charging may be interrupted.


Turning now to FIG. 3, a schematic diagram of an electronic device 300, in accordance with aspects of the present disclosure, is shown. As illustrated, the device 300 is configured to cooperate with a vehicle 350. In general, the vehicle 350 may include an automobile, an aircraft, a boat, a drone, a golf cart, and others.


As shown, the device 300 may generally include a device interface 302, a battery sensor 304, a processor 306, and a number of function modules as 308. The device 300 may optionally include one or more input/output (I/O) modules 310, a power module 312, a memory 314, as well as other elements or circuitry. A communication network 316 may also be included in the device 300 and configured to facilitate the exchange of data, signals, and other information between the various elements of the device 300.


The device interface 302 may be configured to exchange data, signals, and other information with a variety of devices and/or a system. As shown in FIG. 3, in some embodiments, the device interface 302 allows communication of signals, data, and other information with the vehicle 350. In particular, the device interface 302 may be configured to provide an electrical wired or wireless connection between the battery of the vehicle 350 and various components in the device 300, such as the battery sensor 304, the power module 312, and others. In one example, the device interface 302 may include one or more electrical connectors configured to make an electrical contact with the vehicle 350. In some embodiments, the electrical connectors are configured to couple to a power socket of the vehicle 350, thereby electrically coupling or connecting the device 300, and various components therein, to the vehicle's battery.


The battery sensor 304 is in communication with the device interface 302 and configured to detect the battery voltage of the vehicle 350. In some implementations, the battery sensor 304 may include a voltage detector configured to at least detect voltages in a range applicable to vehicle battery voltages. Example voltage detectors may include voltmeters, data acquisition cards, Arduino boards, and other analog and/or digital circuitry. In addition, in some implementations, the battery sensor 304 may include a variety of other electronic components and hardware for acquiring, pre-processing, and/or modifying signals (e.g. voltages or currents) received via the device interface 302. In some implementations, such electronic components and hardware may be configured to sample, amplify, filter, scale, and digitize signals received by the battery sensor 304. The battery sensor 304 may also include various protective circuitry, fault detectors, switches, and so on, configured for protecting sensitive components in the device 300.


In addition to being configured to carry out various processes of the device 300, the processor 306 may be configured to execute steps, in accordance with methods of the present disclosure. Specifically, the processor 306 may include one or more processors or processing units configured to carry out steps to determine a state of operation of the vehicle 350 based on the battery voltage detected. The processor 306 may also control operation of the device 300 in accordance with the operational state, as described. In some aspects, the processor 306 may also determine and generate a report indicating a state of a vehicle's battery (e.g., discharged state, charging state, full state, and so on), as well as other information related to battery voltage detected and a vehicle's operational state(s). To do so, the processor 306 may execute hardwired instructions or programming. As such, the processor 306, or various processing units therein, may therefore be application-specific due to the hardwired instructions or programming therein. Alternatively, the processor 306 may execute non-transitory instructions stored in the memory 314, as well as instructions received via input. By way of example, the processor 306 may include one or more general-purpose programmable processors, such as central processing units (“CPUs”), graphical processing units (“GPUs”), microcontrollers, and the like.


In some aspects, the processor 306 may control one or more function modules 308 in the device 300. As shown in FIG. 3, the device 300 may include one or more function modules 308 that are configured to carry out specific functions in the device 300. In one non-limiting example, one function module 308 may be configured to control a heating element, or a fan in the device 300. In another non-limiting example, another function module 308 may be configured to control the charging of a battery in the device 300. In yet another non-limiting example, another function module 308 may be configured to control charging of an external battery connected to the device 300, where the external battery (e.g., of a cell phone or tablet) is connected via a USB port on the device 300. In yet another non-limiting example, yet another function module 308 may be configured to control the power module 312 to modify a power state of the device 300 (e.g., normal power state, low-power state, sleep state, and so forth). Alternatively, the power module 312 may be controlled directly by the processor 306. In yet another non-limiting example, another function module 308 may communicate with the I/O module(s) 310 to provide a report indicating a condition of the device 300. To this end, the one or more function modules 308 may include a variety of elements, circuitry, and hardware, including various signal sources, signal processors, integrated circuits, digital-to-analog (“DAC”) converters, analog-to-digital converters (“ADC”), pulse width modulation (“PWM”) generators, analog/digital voltage switches, analog/digital pots, relays, and other electrical components.


As mentioned, the device 300 may optionally include I/O module(s) 310 configured to receive a variety of data, information, as well as selections, and operational instructions from an operator. To this end, the I/O module(s) 310 may also include various drives, ports, receptacles, and elements for providing input, including a touchpad, touch screen, buttons, switches, toggles, flash-drives, USB ports/drives, CD/DVD drives, communication ports, modules, and connectors, and so on. The I/O module(s) 310 may also be configured to provide a report by way of various output elements, including screens, LEDs, LCDs, alarm sources, and so on.


The power module 312 may be configured to provide power to various elements of the device 300. In some implementations, the power module 312 may power the various elements by way of a vehicle battery. Additionally, or alternatively, the power module 312 may include an internal source of power, including a rechargeable or replaceable battery. To this end, the power module 312 may control the charging of the battery, as well as dissemination of power provided by the vehicle 350 and/or battery. In some implementations, the power module 312 may also provide power to an external device, or control the charging of the external device, connected to the device 300 using a USB port, for example.


The memory 314 may store a variety of information and data, including, for example, operational instructions, data, and so on. In some aspects, the memory 314 may include non-transitory computer readable media having instructions executable by the processor 306. The memory 314 may also store data corresponding to detected battery voltages and information generated therefrom, including battery states, vehicle operational states, and so on.


The communication network 316 may include a variety of communication capabilities and circuitry, including various wiring, components, and hardware for electronic, radiofrequency (“RF”), optical, and other communication methods. By way of example, the communication network 316 may include parallel buses, serial buses, and combinations thereof. Example serial buses may include serial peripheral interface (SPI), I2C, DC-BUS, UNI/O, 1-Wire, and others. Example parallel buses may include ISA, ATA, SCSI, PIC, IEEE, and others.


One embodiment of the device 300 described above is illustrated in FIG. 4. Specifically, the battery sensor 304 may be electrically coupled to the vehicle battery 402 and vehicle alternator 404 via the device interface 302 and a vehicle interface 406. Such coupling may be achieved using a wired, and optionally grounded, connection, as shown in FIG. 4, as well as a wireless connection. In one implementation, the vehicle interface 406 may include an accessory outlet of the vehicle 350 (e.g., a 12V power socket) and the device interface 302 may include a plug configured to electrically and mechanically engage the accessory outlet. As shown, the battery sensor 304 may include a voltage divider 408 having a first resistor R1 and a second resistor R2. Selection of R1 and R2 may depend upon the battery voltage supplied by the vehicle battery 402, as well as on the specifics of the processor 306. For example, R1 and R2 may depend upon the voltage range capability of the processor 306.


As shown, the processor 306 is also connected to a load circuit 410 configured to apply a load to the vehicle battery 402. Specifically, the load circuit 410 may include a load 412 and a switch 414 configured to engage the load 414, as directed by the processor 306. In some implementations, the load 412 may be a resistor R3 (e.g., a heating element or resistive wire) and the switch 414 may be a transistor element. It may be readily appreciated, however, that the load 412 and switch 414 may include any elements or hardware designed to achieve the same or a similar functionality. For example, the load 412 may include any element or component that can draw power from the vehicle battery 402, and the switch 414 may include any element or component that can engage the load 412 to the vehicle battery 402. In some implementations, the load circuit 410 may include, or be part of, a function module 308, as described with reference to FIG. 3. For example, the load circuit 410 may be an electric circuit having a heating element configured to control or assist in the dispensing of a volatile material.


Referring again to FIG. 4, the processor 306 may then receive, sample, and process signals (e.g. voltage signals) from the vehicle battery 402 by way of the battery sensor 304, and determine an operational state of the vehicle 350. As described, the processor 306 may also control the load circuit 410 in determining the operational state of the vehicle 350. The processor 306 may then control the device 300, and various function modules 308 therein, as described with reference to FIG. 3.


In some embodiments, as illustrated in FIG. 5, the battery sensor 304, processor 306, and load circuit 410 may be incorporated in the vehicle 350, rather than the device 300. As shown, the processor 306 may also be connected to a battery power module 502 configured to provide power to the device 300 by way of the vehicle interface 406 and device interface 302. As described, the processor 306 may be configured to determine an operational state of the vehicle 350 based on battery voltages detected using the battery sensor 304. The processor 306 may then communicate with the battery power module 502 to control power provided by the vehicle battery 402 to the device 300. For example, if it is determined that the vehicle is in an “OFF” state, or the battery is discharged below a predetermined threshold, the processor 306 may generate and send control signals to the battery power module 502 to interrupt power available to the device 300 at the vehicle interface 406. The processor 306 may also generate a report and communicate the report via the vehicle interface 406. In some aspects, the report may include an indication of battery state or vehicle operational state, as well as other information, such as operational instructions for the device 300. For example, the operational instructions may include instructions for the device 300 to enter a low-power mode.



FIG. 6 shows one embodiment of a volatile material device 600 for use in a vehicle, in accordance with aspects of the present disclosure. As appreciated from the description above, FIG. 6 is provided for purposes of illustrating devices and methods, and does not limit the present disclosure in any way.


In general, the device 600 shown in FIG. 6 includes a housing 602 providing a cavity configured to hold a cartridge having a volatile material therein (not shown). The housing 602 may also be configured to hold therein an electrical assembly (not shown), as well as other elements and components. In some implementations, the electrical assembly is configured to control a release of the volatile material from the cartridge. The electrical assembly is configured to interact with a power outlet of a vehicle via socket contacts 604.


Referring specifically to FIG. 7, an example electrical assembly 700 for use in the device 600 is shown. The electrical assembly 700 includes a power stage 702, a controller stage 704, and a heating element 706. In particular, the power stage 702 is configured to receive power from a vehicle's battery by way of input leads 708 that are connected to the socket contacts 604 shown in FIG. 6. The power stage 702 is also configured to manage the received power to operate various electrical components of the electrical assembly 700, such as the heating element 706.


As shown in FIG. 7, the power stage 702 may include a pushbutton switch 710 having an “on” and an “off” position, for example, and a voltage regulator 712. The power stage 702 may also include a number of other electrical components, including capacitors, resistors, inductors, diodes, and so forth. In addition, as shown in FIG. 7, the power stage 702 may also include a number of fuses 714, such as electrical and thermal fuses, for protecting circuit components of the electrical assembly 700 in case of electrical or thermal spikes, transients, or overload.


Still referring to FIG. 7, the control stage 704 includes a processor 716 (e.g. a microcontroller) programmed to control the operation of the heating element 706, and other electrical components. In addition, the control stage 704 also includes a slide switch 718 for selecting the mode of operation. Specifically, the power switch 718 activates inputs to the processor 716 to indicate a target temperature for the heating element 706. By way of example, the slide switch 718 may include an “off” position, and a number of “on” positions, such as a “low,” “medium,” and “high” position, indicating an intensity level for dispersing volatile material. The position of the slide switch 718 may be indicated by LEDs 720 included in the control stage 704 circuitry, as shown in FIG. 7. In some implementations, the same or different LEDs 720 may additionally, or alternatively, indicate an “OFF” or “ON” state of the vehicle.


When the pushbutton switch 710 and slide switch 718 are activated to an “on” position, the processor 716 can direct electric current to flow to the heating element 706, using activation element 722 and power supplied by the power stage 702. In some aspects, a PWM algorithm may be used by the processor 716 to allow the heating element 706 to heat up quickly, which in turn would allow a faster fragrance or volatile material release. In some implementations, the processor 716 may also be programmed such that if the slide switch 718 is inadvertently moved to an intermediate position that is a position between allowable settings, as described above, the electrical assembly 700, or portions thereof, may be disabled, to avoid unpredictable behavior.


As shown in FIG. 7, the control stage 704 may include a battery sensor 724 in communication with the processor 716. The battery sensor 724 is configured to detect battery voltage of the vehicle's battery, as described. The processor 716 may be configured to control a sampling of the battery voltage detected by the battery sensor 724, and determine an operational state of the vehicle using the battery voltage, as described. Based on the operational state, the processor 716 can affect the operation of the heating element 706, as well as other electrical components. In particular, the processor 716 may generate and send a control signal to the activation element 722, which would either prevent or allow power being provided to the heating element 706. For example, the processor 716 may de-energize the heating element 706 when a vehicle is in an “OFF” state. A determination of an “ON” or “OFF” state may be reported to a user, for example, using the LEDs 720.


In some modes of operation, the processor 716 may temporarily energize the heating element 706 to apply a load to the vehicle's battery. This may be desirable in the case that the battery voltage detected using the battery sensor 724 is below a predetermined threshold (e.g. about 13.0V). As described with reference to FIG. 4, applying a load (in this case the heating element 706) and monitoring battery voltage for a predetermined period of time allows for determining the operational state of the vehicle. As described, the period of time may depend on the nature of the load (e.g. power draw) and other factors.


In some embodiments, the heating element 706 may include a thermistor 726 that is coupled to the processor 716, and allows the processor 716 to shut off specific electronic components, including the heating element 706, for a predetermined amount of time if a predetermined temperature is exceeded.


Although a particular implementation is shown in FIG. 7 for the power stage 702 and controller stage 704 for managing and controlling power provided to the heating element 706, any number of modifications and variations are possible to provide functionalities as described above, as well as other functionalities. Additionally, the heating element 706 is shown to include a single resistive wire, yet it may be readily appreciated that any variation, such as two or more resistive wires, in accordance with the present disclosure may also be possible.


Turning to FIG. 8, another process 800, in accordance with aspects of the present disclosure, is shown. Steps of the process 800 may be carried out using any suitable device, apparatus, or system, including devices described in the present disclosure. Also, steps of the process 800 may be implemented as a program, firmware, or instructions stored in non-transitory computer readable media, executable by a processor or computer.


The process 800 may begin at process block 802 by monitoring the battery voltage of a vehicle's battery. The battery voltage may be detected using a battery sensor connected or connectable to the vehicle's battery. The battery sensor may be electrically connected, but need not be physically connected, to the vehicle's battery. As described, the battery sensor may be incorporated into, or may be part of, various electronic devices, such as portable electronic devices, volatile emitting devices, and others. In other embodiments, the battery sensor may be part of the vehicle circuitry.


The battery voltage may then be analyzed to determine the operational state of the vehicle. Specifically, the battery voltage may be analyzed to identify at least one transition therein, as indicated by process block 804. Transitions may be positive, reflecting rises in the battery voltage, or a negative, reflecting drops in the battery voltage. By way of example, a positive transition may be in a range between approximately +0.1 Volts per minute and approximately +60.0 Volts per minute, and a negative transition may be in a range between approximately −60.0 Volts per minute and approximately −0.1 Volts per minute. The operational state of the vehicle may then be determined at process block 806 based on the identified transition(s).


In some aspects, the battery voltage may also be used to determine the operational state of the vehicle, as indicated by process block 806. For instance, battery voltage detected at particular points in time (e.g. before, during, or after transitions in battery voltage), or an average battery voltage detected over a period of time, may be compared to one or more battery voltage thresholds to determine the state of the vehicle.


To illustrate how an operational state of a vehicle may be determined using battery voltages and transitions in battery voltage, a non-limiting example is provided in FIG. 9. The figure shows different battery voltage signatures based on whether the vehicle is in a first operational state 902 (e.g. engine on), a second operational state 904 (e.g. engine off, ignition off) or a third operational state 906 (e.g. engine off, ignition on). As shown, transitions in the battery voltage occur when the vehicle operational state is changed. Specifically, a first transition 908 occurs between the first operational state 902 and the second operational state 904, a second transition 910 occurs between the second operational state 904 and the third operational state 906, and a third transition 912 occurs between the third operational state 906 and the first operational state 902.


As described, the operational state of the vehicle may be determined by comparing the battery voltage measured at various points in time to various battery voltage thresholds 914-916. For instance, it may be determined that the vehicle is in the first operational state 902 if the battery voltage, or average battery voltage, exceeds a first battery voltage threshold 914. However, comparing battery voltage to various thresholds might not always be sufficient to indicate the vehicle state, as described. For example, a measurement of around 13 V might not conclusively determine whether the vehicle is in the first operational state 902, the second operational state 904, or the third operational state 906. Therefore, transitions in the battery voltage may be also be used. For example, the first transition 908, indicating a drop in the battery voltage (i.e. negative transition), may be used to determine if the engine has been turned off. Similarly, the third transition 912, indicating a rise in the battery voltage (i.e. positive transition), may be used to determine if the engine has been turned on.


As seen in FIG. 9, both the first transition 908 and the second transition 910 indicate drops in the battery voltage. Therefore, discerning whether the ignition is off or on may also include analyzing battery voltage. For instance, a battery voltage above a second battery voltage threshold 916 combined with a negative voltage drop could directly indicate the operational state where the engine is off and the ignition is off.


It may be readily appreciated that the battery voltage pattern in FIG. 9 is for illustrative purposes, and therefore non-limiting. Indeed, the number and type of operational states, battery voltages and transitions may vary depending upon the particulars of the vehicle and vehicle operation, battery age and charging, as well as other factors.


Referring again to FIG. 8, an electronic device coupled to the vehicle's battery may then be controlled at process block 808 in accordance with the determined operational state of the vehicle. As described, this step may include controlling various device functions or operational aspects of the electronic device, such as interrupting or modifying device charging or changing a mode of operation.


As shown, a report may be optionally provided at process block 810. The report may be in any form and include any information. The report may be provided to an output, and/or stored in a memory. For example, the report may be provided using a display and/or LEDs, and so forth, and indicate various battery voltages detected, operational state(s) of the vehicle, condition of devices, a communication link, and other data or information.


INDUSTRIAL APPLICABILITY

Devices and methods are presented that provide a novel approach for controlling electronic devices for use in a vehicle based on the operational state of the vehicle.


Numerous modifications to the present invention will be apparent to those skilled in the art in view of the foregoing description. Accordingly, this description is to be construed as illustrative only and is presented for the purpose of enabling those skilled in the art to make and use the invention and to teach the best mode of carrying out same. The exclusive rights to all modifications which come within the scope of the appended claims are reserved.

Claims
  • 1. A method for controlling an electronic device for use in a vehicle, the method comprising: monitoring a battery voltage of a vehicle's battery using a battery sensor connected thereto;identifying at least one transition in the battery voltage using a processor in communication with the battery sensor;determining, using the processor, an operational state of the vehicle based on the transition and the battery voltage by: controlling a load circuit using the processor to apply a load to the vehicle's battery; anddetermining the operational state of the vehicle based on a change in the battery voltage due to the load; andcontrolling, using the processor, an electronic device coupled to the vehicle's battery in accordance with the operational state of the vehicle.
  • 2. The method of claim 1, wherein the method further comprises sensing the battery voltage intermittently or continuously using the battery sensor.
  • 3. The method of claim 1, wherein the method further comprises comparing the battery voltage to at least one battery voltage threshold to determine the operational state of the vehicle.
  • 4. The method of claim 3, wherein the method further comprises analyzing the transition in the battery voltage to determine the operational state of the vehicle.
  • 5. The method of claim 4, wherein the method further comprises identifying a positive transition in the battery voltage.
  • 6. The method of claim 5, wherein the positive transition is in a range between approximately +0.1 Volts per minute and approximately +60.0 Volts per minute.
  • 7. The method of claim 4, wherein the method further comprises identifying a negative transition in the battery voltage.
  • 8. The method of claim 5, wherein the negative transition is in a range between approximately −60.0 Volts per minute and approximately −0.1 Volts per minute.
  • 9. The method of claim 1, wherein the method further comprises controlling at least one device function of the electronic device.
  • 10. An electronic device for use in a vehicle, the device comprising: a battery sensor configured to detect a battery voltage when connected to a vehicle's battery; anda processor in communication with the battery sensor that is configured to: monitor the battery voltage of a vehicle's battery using the battery sensor;identify at least one transition in the battery voltage;determine an operational state of the vehicle based on the transition and the battery voltage by:controlling a load circuit connected to the vehicle's battery to apply a load to the vehicle's battery; anddetermining the operational state of the vehicle based on a change in the battery voltage due to the load; andcontrol the electronic device in accordance with the operational state of the vehicle.
  • 11. The device of claim 10, wherein battery sensor is further configured to sense the battery voltage intermittently or continuously.
  • 12. The device of claim 10, wherein the processor is further configured to compare the battery voltage to at least one battery voltage threshold to determine the operational state of the vehicle.
  • 13. The device of claim 12, wherein the processor is further configured to analyze the transition in the battery voltage to determine the operational state of the vehicle.
  • 14. The device of claim 13, wherein the processor is further configured to identify a positive transition in the battery voltage.
  • 15. The device of claim 14, wherein the positive transition is in a range between approximately +0.1 Volts per minute and approximately 60.0 Volts per minute.
  • 16. The device of claim 13, wherein the processor is further configured to identify a negative transition in the battery voltage.
  • 17. The device of claim 16, wherein the negative transition is in a range between approximately −60.0 Volts per minute and approximately −0.1 Volts per minute.
  • 18. The device of claim 10, wherein the processor is further configured to control at least one device function of the electronic device.
CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No. 15/873,681 filed Jan. 17, 2018.

US Referenced Citations (179)
Number Name Date Kind
2786406 White Mar 1957 A
2898649 Murray Aug 1959 A
4574181 Spector Mar 1986 A
4808347 Dawn Feb 1989 A
D304299 Sakamoto Oct 1989 S
4921137 Heijenga May 1990 A
4968456 Muderlak et al. Nov 1990 A
D315202 Kunze Mar 1991 S
5007863 Xuan Apr 1991 A
D336034 Rebilas Jun 1993 S
5373581 Smith Dec 1994 A
5394506 Stein et al. Feb 1995 A
5484086 Pu Jan 1996 A
5529224 Chan et al. Jun 1996 A
5605308 Quan et al. Feb 1997 A
5788931 Munoz Quintana Aug 1998 A
5833929 Watson et al. Nov 1998 A
D407640 Nelson et al. Apr 1999 S
6021254 Hunter Feb 2000 A
6085027 Sexton Jul 2000 A
6090349 Hirano Jul 2000 A
6099137 McCormack et al. Aug 2000 A
6197263 Blount Mar 2001 B1
D442078 Fuquen May 2001 S
D445674 Pritchett Jul 2001 S
D447054 Hill Aug 2001 S
6278840 Basaganas Millan Aug 2001 B1
6285830 Basaganas Millan Sep 2001 B1
D448661 Kerr et al. Oct 2001 S
6354710 Nacouzi Mar 2002 B1
6374044 Freidel Apr 2002 B1
6443434 Prather Sep 2002 B1
6446583 Vieira Sep 2002 B2
6466739 Ambrosi et al. Oct 2002 B2
D469348 Demus et al. Jan 2003 S
6580875 Rymer Jun 2003 B2
6592828 Quintana Munoz Jul 2003 B2
D481949 Pinnavaia Nov 2003 S
6643897 Chang Nov 2003 B2
6661967 Levine et al. Dec 2003 B2
D484972 Steele, IV et al. Jan 2004 S
D486213 Novak Feb 2004 S
6782194 Schneiderbauer Aug 2004 B2
6796340 Ferris et al. Sep 2004 B1
6854717 Millan Feb 2005 B2
6859615 Yip et al. Feb 2005 B2
D503343 Canino Mar 2005 S
6862403 Pedrotti et al. Mar 2005 B2
6917754 Pedrotti et al. Jul 2005 B2
6931202 Pedrotti et al. Aug 2005 B2
6950607 Yip et al. Sep 2005 B2
D513433 Lemaire Jan 2006 S
6996335 Zobele Feb 2006 B2
D520130 Miro May 2006 S
D525352 Lemaire Jul 2006 S
7082259 Zobele Jul 2006 B2
D527264 Haley et al. Aug 2006 S
7109850 Kawazoe et al. Sep 2006 B2
7141215 Guan et al. Nov 2006 B2
7190888 Wolf et al. Mar 2007 B2
7209650 Caserta et al. Apr 2007 B2
D553499 Lavelli Oct 2007 S
D556603 Barnes et al. Dec 2007 S
D557396 Cheng Dec 2007 S
D564650 Hasik et al. Mar 2008 S
7341698 Pedrotti et al. Mar 2008 B2
7350720 Jaworski et al. Apr 2008 B2
7389943 Jaworski Jun 2008 B2
D573037 Murray Jul 2008 S
7462329 Wefler Dec 2008 B2
7469844 Conway et al. Dec 2008 B2
7497685 Kubicek et al. Mar 2009 B2
7503668 Porchia et al. Mar 2009 B2
7534406 Takemura May 2009 B2
7544331 Pettaway Jun 2009 B1
D598299 Isogai et al. Aug 2009 S
7610118 Schramm et al. Oct 2009 B2
D606882 Sharp et al. Dec 2009 S
D610910 Simmons et al. Mar 2010 S
7687744 Walter et al. Mar 2010 B2
D620809 Caldwell et al. Aug 2010 S
D623073 Caldwell et al. Sep 2010 S
7824627 Michaels et al. Nov 2010 B2
D632566 Caldwell et al. Feb 2011 S
D632569 Caldwell et al. Feb 2011 S
D634643 Caldwell et al. Mar 2011 S
7931213 Ousley Apr 2011 B2
7932482 Norwood et al. Apr 2011 B2
7938338 Janakat et al. May 2011 B2
7954667 Furner et al. Jun 2011 B2
7962017 Viera Jun 2011 B2
D643737 Handy Aug 2011 S
8005349 Deflorian et al. Aug 2011 B2
D646572 Koeleman Oct 2011 S
D646926 Willat et al. Oct 2011 S
8061562 Carpenter et al. Nov 2011 B2
D652319 Cohen et al. Jan 2012 S
8091734 Furner et al. Jan 2012 B2
8196902 Pystin Jun 2012 B1
8197761 Miller-Larry Jun 2012 B1
D663618 Cohen et al. Jul 2012 S
D671004 Kelly et al. Nov 2012 S
D671409 Cohen et al. Nov 2012 S
8342363 Carpenter et al. Jan 2013 B2
8371310 Brenneise Feb 2013 B2
8386199 Goff Feb 2013 B2
D680208 Gordon Apr 2013 S
D680882 Logue Apr 2013 S
8412029 Browder et al. Apr 2013 B2
8437908 Goff et al. May 2013 B2
D685076 Gordon Jun 2013 S
8463114 Garcia Fabrega et al. Jun 2013 B2
D686922 Davis et al. Jul 2013 S
8498524 Ruiz Ballesteros et al. Jul 2013 B2
8662480 Irvin Mar 2014 B1
8678233 Furner et al. Mar 2014 B2
8718454 Caserta et al. May 2014 B2
D706644 Ruiz, Sr. et al. Jun 2014 S
8750694 Porretta et al. Jun 2014 B1
8787739 Hsiao Jul 2014 B2
8887954 Carpenter et al. Nov 2014 B2
8983277 Hsiao Mar 2015 B2
8983278 Ruiz Ballesteros et al. Mar 2015 B2
8983279 Adair et al. Mar 2015 B2
9031392 Hsiao May 2015 B2
9042712 Irvin et al. May 2015 B2
D752391 Hatherell Mar 2016 S
D758206 Hoeke et al. Jun 2016 S
9388994 Hidaka et al. Jul 2016 B2
9393337 Gruenbacher et al. Jul 2016 B2
9399080 Irvin et al. Jul 2016 B2
9408936 Esses Aug 2016 B2
D772070 Broen et al. Nov 2016 S
9522208 Esses Dec 2016 B2
D781150 Zoppas Mar 2017 S
D786684 McGreevy et al. May 2017 S
20020176704 Roe Nov 2002 A1
20030184935 Enzinna et al. Oct 2003 A1
20040229110 Tsai Nov 2004 A1
20060188238 Kent Aug 2006 A1
20060193610 Han Aug 2006 A1
20060292110 Reinhardt Dec 2006 A1
20070235555 Helf et al. Oct 2007 A1
20090041442 Rouse, Jr. Feb 2009 A1
20090078253 Bao Mar 2009 A1
20090232710 Kinsey Sep 2009 A1
20090302019 Selenski et al. Dec 2009 A1
20100209081 Rymer Aug 2010 A1
20100326280 Hicks Dec 2010 A1
20110106373 Hergesheimer et al. May 2011 A1
20110132995 Perman Jun 2011 A1
20120018529 Gammon et al. Jan 2012 A1
20120201523 Tebe Poves et al. Aug 2012 A1
20120224995 McMinn Sep 2012 A1
20140091487 Belongia Apr 2014 A1
20140126892 Hsiao May 2014 A1
20140193764 Pizzini Jul 2014 A1
20160015847 Irvin et al. Jan 2016 A1
20160022855 Esses Jan 2016 A1
20160022857 Esses Jan 2016 A1
20160107186 Chao et al. Apr 2016 A1
20160152117 Backman et al. Jun 2016 A1
20160161367 Chu Jun 2016 A1
20160256585 Esses Sep 2016 A1
20160279278 Gruenbacher et al. Sep 2016 A1
20160325605 Irvin et al. Nov 2016 A1
20170112191 Sur et al. Apr 2017 A1
20170112194 Sur et al. Apr 2017 A1
20170112195 Sur et al. Apr 2017 A1
20170112196 Sur et al. Apr 2017 A1
20170112955 Bourne Apr 2017 A1
20170128608 Hsiao May 2017 A1
20170150757 Worm et al. Jun 2017 A1
20170167739 Williams Jun 2017 A1
20170209612 Westphal et al. Jul 2017 A1
20170232128 Esses Aug 2017 A1
20170252476 Koontz et al. Sep 2017 A1
20170282722 Abou-Zeid Oct 2017 A1
20170310804 Rhyne Oct 2017 A1
Foreign Referenced Citations (90)
Number Date Country
3841769 Jun 1990 DE
20302097 Jul 2003 DE
20302098 Jul 2003 DE
10305480 Aug 2004 DE
10305481 Aug 2004 DE
102005041986 Mar 2007 DE
000277660-0002 Jan 2005 EM
000395389-0002 Aug 2005 EM
000668785-0001 Feb 2007 EM
000758743-0022 Jul 2007 EM
000758743-0024 Jul 2007 EM
001118384-0011 Apr 2009 EM
001154470-0001 Jul 2009 EM
001215875-0001 May 2010 EM
001215875-0002 May 2010 EM
001215875-0003 May 2010 EM
001750373-0001 Sep 2010 EM
001292627-0001 Sep 2011 EM
002005181-0001 Mar 2012 EM
002280933-0004 Jul 2013 EM
002280933-0007 Jul 2013 EM
002306704-0001 Sep 2013 EM
002366609-0001 Dec 2013 EM
002444570-0001 Apr 2014 EM
002521591-0004 Aug 2014 EM
002646554-0007 Mar 2015 EM
002646554-0008 Mar 2015 EM
002664839-0003 Mar 2015 EM
002677765-0001 Apr 2015 EM
002677765-0002 Apr 2015 EM
002678821-0021 Apr 2015 EM
002678821-0022 Apr 2015 EM
002688143-0001 Apr 2015 EM
002738773-0003 Jul 2015 EM
002760538-0001 Aug 2015 EM
003037548-0007 Mar 2016 EM
003122761-0003 May 2016 EM
003456482-0001 Nov 2016 EM
003456821-0001 Nov 2016 EM
003763689-0001 Feb 2017 EM
003814508-0001 Mar 2017 EM
003814508-0002 Mar 2017 EM
003814508-0003 Mar 2017 EM
003847151-0001 Apr 2017 EM
003847151-0002 Apr 2017 EM
003847151-0003 Apr 2017 EM
003847151-0004 Apr 2017 EM
003847151-0005 Apr 2017 EM
003847151-0006 Apr 2017 EM
003847151-0007 Apr 2017 EM
003847151-0008 Apr 2017 EM
003847177-0001 Apr 2017 EM
003847177-0002 Apr 2017 EM
003847177-0003 Apr 2017 EM
003847177-0004 Apr 2017 EM
003847177-0005 Apr 2017 EM
003847177-0006 Apr 2017 EM
003847177-0007 Apr 2017 EM
003847177-0008 Apr 2017 EM
003849975-0001 Apr 2017 EM
003849975-0002 Apr 2017 EM
003850718-0001 Apr 2017 EM
003850718-0002 Apr 2017 EM
003997030-0001 May 2017 EM
004096386-0001 Jul 2017 EM
325468 Jun 1991 EP
2985738 Feb 2016 EP
2328315 Sep 2010 ES
2227665 Apr 1992 GB
2443925 May 2008 GB
1997039778 Oct 1997 WO
2003077961 Sep 2003 WO
2005092399 Oct 2005 WO
2007018402 Feb 2007 WO
2007083042 Jul 2007 WO
2011020491 Feb 2011 WO
DM080 572 Apr 2013 WO
2013106982 Jul 2013 WO
2014022164 Feb 2014 WO
2014055478 Apr 2014 WO
2014087173 Jun 2014 WO
DM089 369 Feb 2016 WO
2016083165 Jun 2016 WO
2016096272 Jun 2016 WO
2016155333 Oct 2016 WO
2016180663 Nov 2016 WO
DM094 995 Jan 2017 WO
2017070039 Apr 2017 WO
2017131942 Aug 2017 WO
2017151322 Sep 2017 WO
Non-Patent Literature Citations (2)
Entry
International Search Report and Written Opinion issued in corresponding International Application No. PCT/US2019/013046, dated Jul. 19, 2019, 18 pages.
International Search Report and Written Opinion issued in corresponding International Application No. PCT/US2019/038483, dated Sep. 6, 2019, 13 pages.
Related Publications (1)
Number Date Country
20190217795 A1 Jul 2019 US
Continuation in Parts (1)
Number Date Country
Parent 15873681 Jan 2018 US
Child 16036461 US