Vehicle system

Abstract

A vehicle system includes a vehicle processor for storing data including a vehicle location and vehicle data. The vehicle system also includes a server communicatively coupled to the vehicle processor. The server is configured to determine when the vehicle is stored based on the vehicle location and the vehicle data, and activate a storage mode when it is determined that the vehicle is being stored.

Description

[0001] The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent it is described in this section and in aspects of the description that may not qualify as prior art at the time of filing, is neither explicitly nor implicitly admitted to be prior art against the present disclosure. Technical Field

[0002] The present disclosure generally relates to a vehicle system configured to comply with state-of-charge limitations. Background Art

[0003] Many vehicles today are electric vehicles that use batteries to power their vehicles. Batteries, especially fully charged batteries, can pose a fire risk under certain conditions. Therefore, electric vehicles that are transported or stored are typically kept at a charge below the maximum charge and, ideally, within a safe charging capacity window to mitigate any fire risk. The safe charging capacity window is typically below the maximum charge but above zero charge because additional risks to the vehicle may occur if the vehicle battery life is at or near zero.

[0004] Some transport vehicles now require state of charge limits to help mitigate the risks associated with transporting electric vehicles. While some vehicles include a mode that limits charging to a certain percentage after leaving the manufacturing plant, the charging limit is removed once the vehicle reaches its destination (such as a dealer). Therefore, there remains a need to safely and easily store and / or transport vehicles while complying with state of charge limits. Summary of the invention

[0005] In one configuration, a vehicle system includes a vehicle processor for storing vehicle data including vehicle location and vehicle event data. The vehicle system also includes a server communicatively coupled to the vehicle processor. The server is configured to determine when the vehicle is stored based on the vehicle location and vehicle event data, and activate a storage mode when it is determined that the vehicle is being stored.

[0006] The vehicle system may include one or more of the following optional features. For example, the server may be configured to notify a user that the storage mode is activated. Additionally, the server may be configured to monitor vehicle battery life during storage mode. The server may also be configured to notify a user of low vehicle battery life during storage mode. Additionally, the server may be configured to check for post-storage mode tasks that may need to be completed prior to driving. Additionally, the server may be configured to notify a user of post-storage mode tasks. Additionally, the vehicle may include a vehicle system.

[0007] In another configuration, a vehicle system includes a vehicle processor for storing data including a vehicle location and vehicle data. The vehicle system also includes a server communicatively coupled to the vehicle processor. The server is configured to determine when the vehicle is being transported based on the vehicle location and the vehicle event data, and activate a transport mode when it is determined that the vehicle is being transported.

[0008] The vehicle system may also include one or more of the following optional features. For example, the vehicle location may include a global positioning system (GPS) location and route information. The server may also be configured to notify a user if it is determined that the vehicle is being transported. Additionally, the server may be configured to monitor vehicle battery life during transport mode. The server may also be configured to notify a user of low vehicle battery life during transport mode. Additionally, the server may be configured to pre-regulate the temperature of the vehicle battery to allow for faster charging after the transport mode is completed. Additionally, the vehicle may include a vehicle system.

[0009] In another configuration, the vehicle system includes a vehicle processor for storing data including vehicle location, vehicle data, and transport length. In addition, the vehicle system includes a server communicatively coupled to the vehicle processor. The server is communicatively coupled to the vehicle processor and is configured to initiate battery depletion activities based on the vehicle location, vehicle event data, and transport length. The battery depletion activities include one or more of: enabling maximum accessory load (including increased cooler operation, increased coolant flow rate), additional vehicle imaging, activating vehicle sensors to a high load mode, activating discharge of a cell group by activating a cell balancing resistor, and activating one or more of inefficient operation of vehicle components including one or more of a vehicle engine or a vehicle inverter. The server is also configured to determine which battery depletion activities to activate based on the vehicle location, vehicle event data, and transport length.

[0010] The vehicle system also includes one or more of the following optional features. For example, the vehicle location may include GPS location and route information. In addition, the server may be configured to notify the user if it is determined that the vehicle is being transported. The server may also be configured to monitor the vehicle battery life during the transport mode. In addition, the server may be configured to pre-regulate the temperature of the vehicle battery to allow faster charging after the transport mode is completed. In addition, the vehicle may include a vehicle system. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings described herein are for illustrative purposes only of selected configurations and are not intended to limit the scope of the present disclosure.

[0012] Figure 1 is a perspective view of a vehicle including a vehicle system according to one aspect of the present disclosure; and

[0013] Figure 2 is an exemplary operational flow chart according to one aspect of the present disclosure.

[0014] Corresponding reference characters indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0015] Example configurations will now be described more fully with reference to the accompanying drawings. Example configurations are provided so that the present disclosure will be thorough and will fully convey the scope of the present disclosure to those of ordinary skill in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configurations of the present disclosure. It will be apparent to those of ordinary skill in the art that specific details need not be employed, that example configurations may be embodied in many different forms, and that the specific details and example configurations should not be construed as limiting the scope of the present disclosure.

[0016] The terms used herein are only used to describe the purpose of specific exemplary configurations and are not intended to be limiting. As used herein, the singular articles "a", "an" and "the" may also be intended to include plural forms unless the context clearly states otherwise. The terms "include", "comprise" and "have" are inclusive and therefore specify the presence of features, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, steps, operations, elements, parts and / or their groups. The method steps, processes and operations described herein should not be interpreted as necessarily requiring them to be performed in the specific order discussed or shown, unless specifically identified as an execution order. Additional or alternative steps may be adopted.

[0017] When an element or layer is referred to as being "on another element or layer," "engaged to," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, directly engaged with, connected to, attached to, or coupled to another element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on another element or layer," "directly engaged to," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, there may be no intermediate elements or layers. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.). As used herein, the term "and / or" includes any and all combinations of one or more associated listed items.

[0018] The terms "first", "second", "third", etc. may be used in this article to describe various elements, components, regions, layers and / or parts. These elements, components, regions, layers and / or parts should not be limited by these terms. These terms may only be used to distinguish an element, component, region, layer or part from another region, layer or part. Unless the context clearly indicates, terms such as "first", "second" and other numerical terms do not imply an order or sequence. Therefore, without departing from the teaching of the example configuration, the first element, component, region, layer or part discussed below may be referred to as a second element, component, region, layer or part.

[0019] In this application, including the definitions below, the term "module" may be replaced with the term "circuit". The term "module" may refer to, be a part of, or include an application specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; a memory (shared, dedicated, or group) that stores code executed by the processor; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0020] The term "code" as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class and / or an object. The term "shared processor" includes a single processor that executes some or all codes from multiple modules. The term "group processor" includes a processor that executes some or all codes from one or more modules in combination with an additional processor. The term "shared memory" covers a single memory that stores some or all codes from multiple modules. The term "group memory" includes a memory that stores some or all codes from one or more modules in combination with an additional memory. The term "memory" may be a subset of the term "computer-readable medium". The term "computer-readable medium" does not include transient electrical signals and electromagnetic signals propagated through the medium, and therefore can be considered to be tangible and non-transient memory. Non-limiting examples of non-temporary memory include tangible computer-readable media, which include non-volatile memory, magnetic memory, and optical memory.

[0021] The apparatus and methods described in this application may be implemented in part or in whole by one or more computer programs executed by one or more processors. The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include and / or rely on stored data.

[0022] Software applications (i.e., software resources) may refer to computer software that enables a computing device to perform tasks. Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0023] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disk or tape.

[0024] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0025] Various implementations of the systems and techniques described herein can be implemented in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system that includes at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device, and to send data and instructions to the storage system, at least one input device, and at least one output device.

[0026] The process and logic flow described in this specification can be performed by one or more programmable processors (also referred to as data processing hardware), which execute one or more computer programs to perform functions by operating on input data and generating output. The process and logic flow can also be performed by a dedicated logic circuit (e.g., FPGA (field programmable gate array) or ASIC (application-specific integrated circuit)). As an example, a processor suitable for executing a computer program includes both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operably connected to receive data from it or transmit data to it or both. However, a computer does not need to have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0027] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen) for displaying information to the user and optionally a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including sound, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0028] Reference now Figure 1-2 The example shown in FIG. 1 shows a vehicle system 100. The vehicle system 100 includes a vehicle processor 200 and a server 300 in communication with the vehicle processor 200. In some examples, such as Figure 1In the example shown, the vehicle system 100 is incorporated into a vehicle 10. The vehicle 10 may be an electric vehicle 10 (EV), such that the vehicle 10 includes a battery 12 and may include autonomous or semi-autonomous capabilities. Alternatively, the vehicle 10 may be a hybrid electric vehicle (HEV) that combines EV and internal combustion engine (ICE) components and capabilities. Although the vehicle 10 may be an EV or a HEV, the vehicle 10 will be described as including only EV components and capabilities.

[0029] The vehicle processor 200 stores vehicle data 202 of the vehicle 10. The vehicle data 202 includes a vehicle location 204, vehicle event data 206, a vehicle mode 208, and a transport length 210. The vehicle location 204 is generally related to the location of the vehicle 10. The vehicle location 204 may include one or more of a current vehicle location and route information. The current vehicle location is generally related to the current location of the vehicle 10. The current vehicle location may be obtained from a global positioning system (GPS) or other navigation system and may be transmitted to the vehicle processor 200. Additionally or alternatively, the vehicle camera 14 and / or the sensor 16 may be used to obtain the current vehicle location. For example, the vehicle processor 200 may collect video data related to the current environment of the vehicle 10 to help the vehicle processor 200 and / or the server 300 determine the current vehicle location.

[0030] Route information generally relates to the route that the vehicle 10 is traveling, including origin and destination information. Route information may be collected from user input, a vehicle navigation system, or past driver activity, and may be transmitted to the vehicle processor 200. Additionally, route information may include the route that a transport vehicle is taking. A transport vehicle may include, but is not limited to, a car-carrying truck or trailer, a train, or a cargo ship. Route information may also include information related to the transport vehicle, including a transport vehicle schedule and / or weather conditions that may affect the travel of the transport vehicle. Additionally, route information may include data related to traffic information or road closures.

[0031] The vehicle event data 206 is generally related to the action taken by the vehicle 10. The vehicle event data 206 can be collected by any vehicle sensor 16 and / or vehicle camera 14, and can be transmitted to the vehicle processor 200 for further processing. For example, the vehicle event data 206 can include vehicle ignition state, Wi-Fi connection, vehicle speed, vehicle steering wheel angle, or other vehicle operation. More specifically, the vehicle ignition state can be related to the current ignition state (i.e., whether the vehicle 10 is turned on or off), or can be related to the amount of time that has passed since the last change in the ignition state. In addition, the Wi-Fi connection can be related to which Wi-Fi connections are connected to the vehicle 10 and how long the connection lasts. The vehicle speed can be related to the current speed of the vehicle 10, whether the vehicle 10 has stopped, whether the vehicle 10 has changed speed, accelerated or decelerated, and other vehicle speed-related events. The vehicle steering wheel angle can be related to the current angle of the steering wheel of the vehicle 10. The angle of the steering wheel can provide information about whether the vehicle 10 has turned or may be in a transportation event. For example, if the angle of the steering wheel changes, this can indicate that the vehicle 10 is moving and has turned. In a similar manner, if the steering wheel remains stationary while the position of vehicle 10 moves, such information may indicate that vehicle 10 is being transported. Additionally, vehicle event data 206 may be constantly changing, such that vehicle event data 206 may be continuously sensed and / or obtained during vehicle operation.

[0032] The vehicle mode 208 generally relates to one or more modes in which the vehicle 10 is currently operating. For example, the vehicle mode 208 may relate to any vehicle mode or operation that may affect the battery life of the vehicle 10. The vehicle mode 208 may include, but is not limited to, operating modes including accessory modes, operation of various vehicle components including a vehicle engine or a vehicle inverter, resistor modes, vehicle sensor modes, or other vehicle modes that require the use of the battery 12. In addition, the vehicle mode 208 may relate to a storage mode or a transport mode. The storage mode or the transport mode may be activated by a user through a vehicle dashboard or other vehicle components, through a third-party application, or through a user device such as a cellular phone or a tablet. In addition, it is conceivable that the storage mode or the transport mode may be activated by the server 300, as disclosed in more detail below. In addition, the vehicle mode 208 may be constantly changing so that the vehicle mode 208 may be continuously sensed and / or obtained during vehicle operation.

[0033] The transport length 210 is generally related to the distance or time of the transport. In some examples, the transport length 210 is input by the user before the transport. However, it is also conceivable that the transport length 210 can be determined or collected using route information and / or destination information.

[0034] Transportation companies typically impose state of charge limits on electric vehicles, such as vehicle 10, before vehicle 10 is allowed to be loaded onto a transport vehicle. In some examples, the state of charge limit requires that the vehicle battery life is less than 60% of a full charge. In other examples, the state of charge limit requires that the vehicle battery life is between 10%-55% of a full charge. In other examples, the state of charge limit requires that the vehicle battery life is between 20%-50% of a full charge. In other examples, the state of charge limit requires that the vehicle battery life is between 20%-40% of a full charge. In addition, the state of charge limit can be based on the specific chemistry of the battery 12, so that the state of charge limit can vary between different vehicles. In addition, the state of charge limit can be collected, stored and / or determined by the vehicle processor 200 and / or the vehicle server 300.

[0035] The vehicle processor 200 is also configured to store vehicle battery life information. The vehicle battery life information generally relates to the amount of vehicle battery life remaining in the battery 12. In addition, the vehicle battery life information may be affected by one or more of the vehicle event data 206, the vehicle mode 208, the vehicle location 204, and the haul length 210. In addition, the vehicle battery life information may include whether the vehicle 10 is within the state of charge limits that can be achieved by the haul vehicles along the route. For example, the vehicle battery life information may include whether the vehicle battery life is within the acceptable charge limits for a particular haul vehicle.

[0036] Further references Figure 1 and Figure 2 , the server 300 is configured as a network and / or cloud-based system in communication with the vehicle processor 200. It is also contemplated that the vehicle processor 200 may transmit any or all of the vehicle data 202 to the server 300 for further processing and / or evaluation. In addition, the vehicle processor 200 and / or the server 300 may be continuously and / or periodically updated so that the vehicle data 202 is updated in real time.

[0037] The server 300 may also be configured to communicate with a third-party processor 500 to collect third-party data. For example, the third-party processor 500 may include, but is not limited to, a vehicle processor 200 along the route. Additionally or alternatively, the third-party processor 500 may include a third-party user device, such as a cellular phone and / or a tablet computer, within a vehicle along the route. In addition, the third-party processor 500 may include a third-party database, such as a database including a transportation vehicle schedule, weather information, and / or traffic conditions. It is generally contemplated that the third-party data may include information related to one or more of the vehicle location 204, vehicle event data 206, vehicle mode 208, and / or transportation length 210 from the third-party processor 500.

[0038] Still reference Figure 1 and Figure 2 In the example shown, the server 300 is configured to determine when the vehicle 10 is stored based on the vehicle location 204 and the vehicle event data 206. More specifically, the server 300 can use data collected from the vehicle processor 200 (such as GPS data, vehicle camera data, vehicle ignition status, and / or the time since the last vehicle ignition status change) to determine whether the vehicle 10 is being stored. For example, if the vehicle 10 has been at the same GPS location for a predetermined amount of time (which can be confirmed by data from the vehicle camera (one or more) 14), and has not changed the ignition status within the predetermined amount of time, the server 300 can determine that the vehicle 10 is being stored. In other examples, the vehicle camera (one or more) 14 can detect a vehicle hood or other indicator that helps the server 300 determine that the vehicle 10 may be being stored. In other examples, the vehicle event data 206 can indicate that the vehicle 10 has been connected to the same Wi-Fi connection for a predetermined period of time.

[0039] In addition, if the server 300 determines that the vehicle 10 is being stored, the server 300 can activate the storage mode. The storage mode may include activating additional features, including but not limited to monitoring the vehicle battery life and setting a low battery power timer. Monitoring the vehicle battery life may include keeping the battery life low enough to reduce the risk of fire, while setting a low battery power timer may be used to instruct the vehicle owner or user to charge the battery 12 to prevent the vehicle battery life from becoming too low and causing damage to the battery 12. In this way, if the vehicle 10 is connected to a charger, activating the storage mode may activate vehicle charging when in the storage mode. However, although the vehicle 10 can be charged when in the storage mode, the server 300 will be configured to keep the vehicle battery life within the charging state limit. In addition, the server 300 may be configured to notify the owner or user that the storage mode is activated and / or whether the battery 12 reaches a predetermined low vehicle battery life (i.e., close to zero charge).

[0040] In addition, when the storage mode is manually ended by the user or the storage mode is deactivated by changing the ignition state (i.e., turning on the vehicle), the server 300 is configured to check the post-storage mode tasks that may need to be completed before driving. Storage mode tasks may include, but are not limited to, checking whether the vehicle 10 needs an oil change, fuel level and life, tire rotation status, tire pressure monitoring, and windshield fluid inspection. In addition, the server 300 may be configured to notify the user of any post-storage mode tasks that need attention. For example, if the server 300 activates the storage mode, the server 300 will monitor the vehicle battery life, and if connected to the vehicle charger, the server 300 will keep the vehicle battery life within the charge state limit. In addition, when the user wants to use the vehicle 10 again, the user can turn on the vehicle 10, which will prompt the server 300 to deactivate the storage mode and notify the user of the post-storage tasks that need attention. For example, if the tire pressure is low, the server 300 will send a notification to a user device such as a cellular phone or a tablet and / or to the vehicle dashboard to remind the user to put more air into the tire as soon as possible.

[0041] The server 300 is also configured to determine whether the vehicle 10 is being transported based on the vehicle location 204 and the vehicle data 202. For example, if the server 300 detects that the vehicle 10 is changing position based on the GPS location but the vehicle 10 is not started or has no vehicle speed, the server 300 can determine that the vehicle 10 is being transported. In addition, the server 300 can also be configured to notify the user that the vehicle 10 is currently being transported. In this way, if the server 300 determines that the vehicle is being transported and the server 300 notifies the user of the transport, the user can prepare for vehicle delivery or know that the vehicle 10 is currently being towed.

[0042] In addition, if the server 300 determines that the vehicle is being transported, the server 300 may be configured to activate the transport mode. In the transport mode, the server 300 is configured to monitor the vehicle battery life and compare it with the maximum state of charge limit of the transport vehicle. If the current vehicle battery life is greater than the maximum state of charge limit, the server 300 may be configured to warn the user of the situation to limit the charging capacity when the vehicle 10 is connected to the charging station, and / or start energy reduction activities. In addition, the server 300 may be configured to notify the user of the potentially dangerous low vehicle battery life during the transport mode. The notification may be through a third-party application, a user device, a vehicle dashboard, or other vehicle systems. In addition, the server 300 may be configured to pre-regulate the temperature of the battery 12 to allow faster charging after the transport mode is completed. The server 300 may be configured to use route information such as vehicle destination information or user input to determine when pre-regulation should occur. For example, during winter transportation in cold climates, the server 300 may be configured to heat the battery 12 during the transport mode to allow faster charging when arriving at the destination.

[0043] Additionally, the server 300 may be configured to initiate a battery depletion activity based on the vehicle location 204, the vehicle event data 206, and the transport length 210. For example, if the transport length 210 is known, the server 300 may use the current vehicle location 204 and the vehicle event data 206 to determine how much battery depletion is required and how long the battery depletion activity should be deployed. Additionally, once the transport mode has been activated, the server 300 will check the current battery life and determine if it is within the state of charge limit for transport on the particular transport vehicle. If the server 300 determines that the current battery life is above the state of charge limit for transport, the server 300 will immediately prevent any further charging activity and initiate the battery depletion activity.

[0044] The battery depletion activities may include one or more of: enabling maximum accessory load (including one or more of increased cooler operation or increased coolant flow rate), additional vehicle imaging, activating vehicle sensors to a high load mode, activating discharge of a cell group by activating a cell balancing resistor, and activating inefficient operation of vehicle components including one or more of a vehicle engine or a vehicle inverter. Additionally, the server 300 may be configured to determine which battery depletion activities to activate based on the vehicle location 204, the vehicle data 202, and the transport length 210, as not all battery depletion activities may be operated simultaneously. Additionally, it is expected that the battery depletion activities may continue until the server 300 determines that the current battery life is within the state of charge limits for the transport. For example, if the server 300 determines that the inefficient operation of the vehicle engine should be activated, the server 300 may continue to run the inefficient operation of the vehicle engine until the current vehicle battery life is within the state of charge limits.

[0045] Additionally, if an upcoming transport event is known, the server 300 may prevent charging of the vehicle. For example, if the user has indicated that the vehicle 10 will be transported the next day and begins charging the vehicle 10, the server 300 may completely prevent charging of the vehicle 10, or may only allow charging to a certain vehicle battery life such that the battery 12 still meets the state of charge limits during the next day's transport.

[0046] Reference now Figure 2In the example shown, the vehicle system 100 begins operation at step 700. In step 702, the server 300 determines whether the user has selected the storage mode. If the user has not selected the storage mode, the server 300 determines whether the user has selected the transport mode at step 704. If the user has not selected the transport mode, the vehicle 10 collects the vehicle data 202 at step 706. The vehicle data 202 is then analyzed by the server 300 at step 708 to determine whether a storage event is detected at step 710. If a storage event is not detected, the server 300 will determine whether a transport event is detected at step 712. However, if a storage event is detected by the user selecting the storage mode at step 702 or by the server 300 determining that the vehicle 10 is being stored at step 710, the vehicle system 100 will start a storage power timer at step 714 to determine how much time is available in the battery life. Then, at step 716, the server 300 determines whether the vehicle 10 is connected to a charger. If the vehicle 10 is connected to a charger, the server 300 is configured to keep the battery 12 within a safe storage range at step 718. Additionally, the server 300 is configured to monitor post-storage mode tasks that may be required prior to driving at step 720. If the vehicle 10 is not connected to a charger, the server 300 is configured to monitor the vehicle battery life at step 722 and determine if the battery 12 is approaching low vehicle battery life at step 724. If the battery 12 is approaching low vehicle battery life, the user is warned of low battery charge and potential danger at step 726.

[0047] In addition, if the user selects a transport mode at step 704 or if a transport event is detected at step 712, the server 300 is configured to disable charging at step 728 until the vehicle 10 is out of transport mode. In addition, the server 300 is configured to analyze the composition of the battery 12 at step 730 to determine the state of charge limit. Next, the server 300 is configured to determine whether the current vehicle battery life is greater than the determined state of charge limit at step 732. If the current vehicle battery life is greater than the determined state of charge limit, the server 300 is configured to warn the user that transportation is in progress and warn the current vehicle battery life at step 734. The server 300 is also configured to take mitigation actions at step 736 to reduce the vehicle battery life to below the state of charge limit. If the timing of the transport event is not known at step 738, the program ends once the mitigation action reduces the vehicle battery life to below the state of charge limit. However, if the timing of the transport event is known at step 738 , the server 300 determines when the transport event is over within a predetermined amount of time at step 740 and begins battery temperature operations at step 742 to enable rapid charging when the transport event is complete.

[0048] Many vehicles today are electric vehicles that use batteries for power. Batteries, especially fully charged batteries, pose a potential fire risk under certain conditions. Therefore, it is often advantageous to provide an electric vehicle being transported or stored with less than the maximum charge safety level to mitigate any fire risk. The vehicle system 100 as described herein provides a user-friendly way to safely and easily store and / or transport the vehicle 10 while complying with state of charge limits.

[0049] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of the present disclosure. Therefore, other embodiments are within the scope of the appended claims.

[0050] The foregoing description is provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable where applicable and can be used in a selected configuration, even if not specifically shown or described. It can also be varied in many ways. Such variations should not be considered as departing from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. A vehicle system for a vehicle, the vehicle system comprising: a vehicle processor for storing vehicle data including vehicle location and vehicle event data; as well as A server communicatively coupled to the vehicle processor and configured to: determining when the vehicle is stored based on the vehicle location and the vehicle event data; as well as When it is determined that the vehicle is being stored, a storage mode is activated.

2. The vehicle system according to claim 1, wherein: The server is configured to notify the user that the storage mode is activated.

3. The vehicle system according to claim 1, wherein: The server is configured to monitor vehicle battery life during the storage mode.

4. The vehicle system according to claim 3, wherein: The server is configured to notify a user of low vehicle battery life during the storage mode. 5 . The vehicle system of claim 1 , wherein the server is configured to check for post-storage mode tasks that may need to be completed prior to driving. 6 . The vehicle system of claim 5 , wherein the server is configured to notify a user of the post-storage mode task.

7. The vehicle system of claim 1, wherein the server is configured to activate a battery depletion activity if the vehicle battery life is above a state of charge limit based on the vehicle location, the vehicle event data, and the haul length.

8. The vehicle system according to claim 7, wherein: The battery depletion activities include one or more of: enabling maximum accessory load including one or more of increased cooler operation or increased coolant flow rate, additional vehicle imaging, activating vehicle sensors to a high load mode, activating discharge of a cell pack by activating cell balancing resistors, and activating inefficient operation of vehicle components including one or more of a vehicle engine or a vehicle inverter. 9 . The vehicle system of claim 8 , wherein the server is further configured to determine which battery depletion activities to activate based on the vehicle location, the vehicle event data, and the haul length.

10. A vehicle comprising the vehicle system according to claim 1.

Images