Disconnection event detection and notification for vehicle

Abstract

A sensor system (1610, Fig. 1D) for a vehicle comprising: a tube 3611 defining a connection point; a sensor 3612 connected to the outside of the tube 3611; a connector 3613, such as a gasket, creating

Description

HELD

[0001] The present disclosure relates generally to enhancing the ability of a vehicle to detect disconnection events associated with its components. More particularly, the present disclosure relates to monitoring pressurized components on a vehicle while the vehicle is in use and sending notifications when a disconnection event in the vehicle occurs. BACKGROUND

[0002] Detecting disconnection events, such as fluid line disconnections, in vehicles, including electric vehicles (EVs), poses challenges due to the presence of high-voltage battery systems and potential hazards associated with pressurization. Traditional methods often rely on mechanical sensors and switches, which can add cost and complexity to vehicle design and maintenance. Another conventional approach uses conductive connectors that monitor continuity in electrical circuits to detect disconnections. However, these methods can also add complexity and potential failure points to the system. SUMMARY

[0003] Aspects and advantages of implementations of the present disclosure will be set forth in part in the following description, or may be learned from the description, or may be learned through practice of the implementations.

[0004] One example aspect of the present disclosure is directed to a sensor system of a vehicle. The sensor system includes a tube structure defining a connection point with a sensor connected to an outer portion of the tube structure. The sensor system is configured to have a connection mechanism defining a seal. The connection mechanism comprising a magnet connected to the connection mechanism. The sensor operable with the magnet to detect a change in a magnetic field of the magnet when a disconnection occurs.

[0005] In an example embodiment, the change in a magnetic field of the magnet comprises a reduction in a magnetic field strength.

[0006] In an example embodiment, the reduction in the magnetic field strength is indicative of an increase in a distance between the sensor and the magnet.

[0007] In an example embodiment, the sensor system further comprises a controller communicatively connected with the sensor, the controller operable to receive a signal from the sensor in response to the change in the magnetic field and output an alert notification.

[0008] In an example embodiment, the alert notification is indicative of a disconnection or a misalignment of the tube structure.

[0009] In an example embodiment, the controller is communicatively connected to a computing device and the controller is operable to output the alert notification to the computing device.

[0010] In an example embodiment, the computing device is a head unit device of the vehicle or a user computing device.

[0011] In an example embodiment, the sensor is a hall sensor.

[0012] In an example embodiment, the sensor and the magnet are separated by a wall of the tube structure.

[0013] In an example embodiment, wherein the tube structure comprises a fluid line associated with an engine of the vehicle.

[0014] In an example embodiment, the tube structure comprises a cooling line for a cooling fluid for a battery of the vehicle or a part of the crankcase ventilation for combustion engines.

[0015] In an example embodiment, the connection mechanism is a gasket.

[0016] Another example aspect of the present disclosure is directed to a control system. The control system includes, a controller and a sensor communicatively connected to the controller. The sensor of the control system, being connected to an outer portion of a tube structure defining a connection point. The control system is configured to have a connection mechanism defining a seal. The control system includes a magnet connected to the connection mechanism. The sensor operable with the magnet to detect a change in a magnetic field of the magnet, and transmit a signal to the controller based on the change in the magnetic field when a disconnection occurs.

[0017] In an embodiment, the controller of the control system is operable to output an alert notification based on the signal from the sensor.

[0018] In an embodiment, the alert notification is indicative of a disconnection or a misalignment of the tube structure.

[0019] In an embodiment, the magnet to detect a change in a magnetic field includes where the change in the magnetic field comprises a reduction in a magnetic field strength.

[0020] In an embodiment, the magnet to detect a change in a magnetic field strength is indicative of an increase in a distance between the sensor and the magnet.

[0021] In an embodiment, the sensor is a hall sensor.

[0022] In an embodiment, the sensor and the magnet are separated by a wall of the tube structure.

[0023] Yet another example aspect of the present disclosure is directed to a method. The method includes, receiving, by a controller, a signal from a sensor, the sensor connected to an outer portion of a tube structure defining a connection point. The method includes a signal which is in response to the sensor detecting a change in a magnetic field of a magnet, the magnet being connected to a connection mechanism defining a seal. The method includes determining, by the controller, an occurrence of a disconnection or a misalignment associated with the tube structure based on the signal from the sensor. The method includes outputting over a network, by the controller to a computing device, an alert notification indicative of the disconnection or misalignment associated with the tube structure.

[0024] Other example aspects of the present disclosure are directed to other systems, methods, vehicles, apparatuses, controllers, and devices for the technology described herein.

[0025] These and other features, aspects, and advantages of various implementations will become better understood to those skilled in the art with reference to the following description and appended claims. The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate implementations of the present disclosure and, together with the description, serve to explain the related principles. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Detailed discussion of implementations directed to one of ordinary skill in the art are set forth in the specification, which makes reference to the appended figures, in which:

[0027] FIG. 1A-D illustrates an example vehicle and vehicle systems according to an embodiment hereof.

[0028] FIG. 2 illustrates an example vehicle and vehicle display according to an embodiment hereof.

[0029] FIG. 3 illustrates an example of a typical crankcase according to an embodiment hereof.

[0030] FIG. 4 illustrates an example crankcase with a sensor system according to an embodiment hereof.

[0031] FIG. 5 illustrates an example crankcase with a sensor system according to an embodiment hereof.

[0032] FIG. 6 illustrates an example magnet and magnetic flux through it.

[0033] FIG. 7 illustrates an example system for thermal management showing a cooling line for a cooling fluid for a battery of a vehicle, with a sensor system according to an embodiment hereof.

[0034] FIG. 8 illustrates a diagram of an example system for disconnection event monitoring and notification, according to an embodiment hereof.

[0035] FIG. 9 illustrates a flowchart diagram of an example method according to an embodiment hereof.

[0036] FIG. 10 illustrates a diagram of an example control ecosystem with computing components according to an embodiment hereof. DETAILED DESCRIPTION

[0037] Example aspects of the present disclosure are directed to monitoring a vehicle for the occurrence of a disconnection or misalignment event and broadcasting a related message to a computing device. In some embodiments, the vehicle may comprise one or more of a turbocharger, intake and exhaust valves, a crankcase, coolant passages, and the like. In some embodiments, the vehicle may comprise a battery and motor.

[0038] For example, a disconnection event that may occur is a cooling line disconnection for a cooling fluid for a battery of the vehicle. Other disconnection events may include tube or seal failure, deformation, partial disconnection, misalignment, vibration, abrasion, wear, clamp or fastener failure, thermal expansion or contraction, chemical degradation, or pressure fluctuations, as non-limiting examples.

[0039] In some circumstances, these disconnection events may lead to costly repairs. For instance, a disconnection event can cause a loss of coolant, fuel, or hydraulic pressure. Other examples result in leaks at the connection point, which can cause system contamination, loss of pressure, fluid leakage, or cause reduced system performance, overheating, or pressure build-up.

[0040] The technology of the present disclosure allows for monitoring a vehicle, determining the occurrence of a disconnection or misalignment event, such as a cooling line disconnection, and broadcasting a related message to a computing device. For example, an EV uses a liquid-cooled thermal management system for the battery. The cooling line can be monitored, and a disconnection event can be detected. In some instances, the present disclosure relates to a sensor system to perform the monitoring. The sensor system may, e.g., include a magnet and include a sensor (e.g., hall sensor) operable to detect a change in a magnetic field of the magnet. The sensor may, for instance, be attached to a tube structure of the cooling line, while the magnet may be attached to a connection mechanism, such as a gasket. In some implementations, a disconnection event, such as between a cooling line and a gasket, may cause the sensor to detect a change in the magnetic field of the magnet, or more specifically a reduction in magnetic field strength. The sensor may generate a signal which indicates a likelihood of the disconnection.

[0041] A signal indicating that the disconnection event occurred can be utilized to share information about the disconnection event to computing devices within the vehicle. For example, in response to determining that the disconnection event occurred, a message about the disconnection event can be generated and sent to a display device in the vehicle.

[0042] A signal indicating that the disconnection event occurred can be utilized to share information about the disconnection event to computing devices outside the vehicle. For instance, in response to determining that the disconnection event occurred, a message about the disconnection event can be generated and sent to the vehicle passengers or users that are remote from the vehicle (e.g., a vehicle owner that is away from the vehicle). As a result, the vehicle passengers and users that are remote from the vehicle can take an appropriate action.

[0043] The message may include information about the disconnection event and the state of the vehicle components, such as information indicating that disconnection event is occurring in the vehicle battery. The message can be output to computing devices that are outside of the vehicle. For example, the message can be sent over the air to user devices (e.g., the driver’s phone and / or the passengers’ phones) and computing devices (e.g., computers, phones, laptops, tablets, wearable devices, etc.) associated with emergency providers, vehicle assistance services, or another entity associated with the vehicle (e.g., maintenance provider, monitoring service).

[0044] The present disclosure provides a number of technical effects and sensing improvements. For instance, the systems and methods of the present disclosure can increase the disconnection monitoring capabilities of the computing systems onboard the vehicle by externally monitoring the connection points. As such, the technology of the present disclosure improves the ability of the vehicle to determine that a disconnection event has occurred at any time. This may be particularly useful when the vehicle has sealed components in order to improve accessibility. This may also help avoid damage caused by failure of a sensor in a disconnection event because external sensors minimize the risk of contamination or damage to internal components, particularly in systems dealing with fluids like fuel, coolant, or brake fluid. Sensors placed outside the tubes or seals are less exposed to the harsh internal conditions, such as high pressure, temperature, and corrosive fluids, potentially extending their lifespan.

[0045] The technology of the present disclosure also improves the sensor systems onboard the vehicle. For instance, external magnetic sensors may reduce the need for complex modifications or data interpretation involving other sensors, leading to simpler and more cost-effective designs.

[0046] Reference now will be made in detail to embodiments, one or more examples of which are illustrated in the drawings. Each example is provided by way of explanation of the embodiments, not limitation of the present disclosure. In fact, it will be apparent to those skilled in the art that various modifications and variations may be made to the embodiments without departing from the scope or spirit of the present disclosure. For instance, features illustrated or described as part of one embodiment may be used with another embodiment to yield a still further embodiment. Thus, it is intended that aspects of the present disclosure cover such modifications and variations.

[0047] As stated above, one aspect of the present disclosure relates to detecting a disconnection event for a cooling line in a vehicle. FIG. 1A provides a block diagram of an example vehicle 1000, such as a car or van. In this example, the vehicle 1000 includes an engine / motor 1300, a battery 1200 used to power the motor 1300 and / or to power electronic components in the vehicle 1000, a thermal management system 1100 for cooling or otherwise controlling a temperature of the engine / motor 1300 or other components in the vehicle, and a vehicle control system 1600 for sensing and / or controlling various components of the vehicle 1000. In some embodiments, such as that illustrated in FIG. IB, the thermal management system 1100 may include coolant stored in a coolant reservoir 1110, and may include a cooling line 1140 (e.g., a tube) for circulating the coolant, and a pump 1140 for moving the coolant through the cooling line 1140.

[0048] In an embodiment, the vehicle control system 1600 may be configured to monitor various parts of the vehicle, and control those parts based on the monitoring. FIG. IC illustrates an example vehicle control system 1600. The vehicle 1000 may include a communications unit 1620 configured to allow the vehicle 1000 (and its vehicle control system 1600) to communicate with other computing devices. The vehicle control system 1600 may use the communications unit 1620 to communicate with one or more other remote computing devices over a network (e.g., via one or more wireless signal connections). For example, the vehicle control system 1600 may utilize the communications unit 1620 to receive platform data 1652. This may include, for example, an over-the-air (OTA) software update for the operating system of the vehicle control system 1600. Additionally, or alternatively, the vehicle control system 1600 may utilize the communications unit 1620 to send vehicle data 1653 to a computing platform. The vehicle data 1653 may include any data acquired onboard the vehicle including, for example, sensor data 1651, location data, diagnostic data, user input data, data indicative of current software versions or currently running applications, occupancy data, data associated with the user of the vehicle 1000, or other types of data obtained (e.g., acquired, accessed, generated, downloaded, etc.) by the vehicle control system 1600.

[0049] In some implementations, the communications unit 1620 may allow communication among one or more of the systems on-board the vehicle 1000.

[0050] In an embodiment, the communications unit 1620 may be configured to allow the vehicle 1000 to communicate with or otherwise receive data from a user device. The communications unit 1620 may utilize various communication technologies such as, for example, Bluetooth low energy protocol, radio frequency signaling, or other short range or near filed communication technologies. The communications unit 1620 may include any suitable components for interfacing with one or more networks, including, for example, transmitters, receivers, ports, controllers, antennas, or other suitable components that may help facilitate communication.

[0051] In an embodiment, the vehicle control system 1600 may include one or more human-machine interfaces (HMIs) 1630. The human-machine interfaces 1630 may include a display device 2630, as described herein. The display device (e.g., touchscreen) may be viewable by a user of the vehicle 1000.

[0052] As further illustrated in FIG. IC, the vehicle control system 1600 may include a power management system 1640. The power management system 1640 may monitor one or more batteries or engine components used by the vehicle 1000. The power management system 1640 may be configured to obtain power data (such as engine or battery data), related to the one or more batteries or engine components used by the vehicle 1000. The power data 1654 may include a charge level, voltage, capacity, leakage, gas levels, internal resistance, and temperature of a battery and the cells of a battery, as well as the state of the battery case, as non-limiting examples. The power data 1654 may be used by various systems of the vehicle control system 1600 or another computing device (e.g., the head unit 2632). For example, the vehicle control system 1600 may utilize the communications unit 1620 to send the power data 1653 to a user device.

[0053] FIG. IC further illustrates the vehicle control system 1600 having a plurality of vehicle functions 1670A-C. A vehicle function 1670A-C may be a functionality that the vehicle 1000 is configured to perform based on a detected input. The vehicle functions 1670A-C may include one or more: (i) vehicle comfort functions; (ii) vehicle staging functions; (iii) vehicle climate functions; (vi) vehicle navigation functions; (v) drive style functions; (v) vehicle parking functions; or (vi) vehicle entertainment functions. The user may interact with a vehicle function 1670A-C through user input (e.g., to an adjustable input device, UI element) that specifies a setting of the vehicle function 1670A-C selected by the user.

[0054] Each vehicle function may include a controller I660A C associated with that particular vehicle function 1670A-C. The controller 1660AC for a particular vehicle function may include control circuitry configured to operate its associated vehicle function 1670A-C. For example, a controller may include circuitry configured to turn the seat heating function on, to turn the seat heating function off, set a particular temperature or temperature level, etc.

[0055] In an embodiment, a controller 1660A-C for a particular vehicle function may include or otherwise be associated with a sensor that captures data indicative of the vehicle’s power system. For example, a sensor may be a pressure sensor or a motion sensor. The pressure sensor may be a piezoelectric sensor configured to capture mechanical stress input from a vehicle 1000. For example, a user may see a cue relating to a low tire pressure indicator function of the vehicle 1000 signaling to the user to fill the tires with air. The motion sensor may be a visual sensor (e.g., camera), infrared, RADAR, etc. configured to capture a gesture input from the user. For example, the user may provide a hand gesture motion to adjust a temperature function of the vehicle 1000 to lower the temperature of the vehicle interior.

[0056] The controllers 1660A-C may be configured to send signals to another onboard system. The signals may encode data associated with a respective vehicle function. The encoded data may indicate, for example, a function setting, timing, etc. In an example, such data may be used to generate content for presentation via the display device 2630 (e.g., showing a current setting). Additionally, or alternatively, such data can be included in vehicle data 1653 and transmitted to a cloud computing platform of the vehicle 1000.

[0057] As illustrated in FIG. IC, the vehicle control system 1600 may include a sensor system 1610 configured to detect, measure, or otherwise sense a state or parameter of components in the vehicle 1000. FIG. ID provides an example of the sensor system 1610. In this example, the sensor system 1610 may be configured to detect at least a disconnection event, such as an event in which two components in the vehicle which were previously connected to each other (directly or indirectly) become disconnected. For instance, the sensor system 1610 may detect a disconnection between components of a cooling line. More specifically, the sensor system 1610 may include a sensor 1612 attached to a tube structure 1611, and include a magnet 1614 attached to a connection mechanism 1613. The tube structure 1611 may be, e.g., an end portion of a cooling line, and may be connected to the connection mechanism 1613 (e.g., gasket). As described below in more detail in FIG. 3, the sensor 1612 may be configured to detect a disconnection between the tube structure 1611 and the connection mechanism 1613 by detecting a change in a magnetic field emanating from the magnet 1614.

[0058] FIG. 2 illustrates an example vehicle 2000 (which may be an embodiment of the vehicle 1000) with an example display device 2630 according to an embodiment hereof. The display device 2630 may be a component of the vehicle head unit 2632 or infotainment system. Such a component may be referred to as a display device of the infotainment system or be considered as a device for implementing an embodiment that includes the use of an infotainment system. For illustrative and example purposes, such a component may be referred to herein as a head unit display device (e.g., positioned in a front / dashboard area of the vehicle interior), a rear unit display device (e.g., positioned in the back passenger area of the vehicle interior), an infotainment head unit or rear unit, or the like. The display device 2630 may be located on, form a portion of, or function as a dashboard of the vehicle. The display device 2630 may include a display screen, CRT, LCD, plasma screen, touch screen, TV, projector, tablet, and / or other suitable display components.

[0059] The display device may display a variety of content to the user including information about the vehicle 2000, prompts for user input, etc. The display device may include a touchscreen through which the user may provide user input to a user interface.

[0060] For example, the display device 2630 may include user interface rendered via a touch screen that presents various content. The content may include vehicle speed, mileage, fuel level, charge range, navigation / routing information, audio selections, streaming content (e.g., video / image content), internet search results, comfort settings (e.g., temperature, humidity, seat position, seat massage), or other vehicle 2000 data. The display device 2630 may render content to facilitate the receipt of user input. For instance, the user interface of the display device 2630 may present one or more soft buttons with which a user can interact to adjust various vehicle functions (e.g., navigation, audio / streaming content selection, temperature, seat position, seat massage, etc.). Additionally, or alternatively, the display device 2630 may be associated with an audio input device (e.g., microphone) for receiving audio input from the user. The vehicle 2000 may include a head unit 2632 defined as a computing device, and a control system as further described with respect to FIG 2.

[0061] FIG. 3 illustrates an example of a sensor system 3610, which may be an embodiment of the sensor system 1610. In this example, the sensor system 3610 may have components attached to a crankcase 3300 according to an embodiment hereof. The crankcase 3300 may include a tube structure 3611 (e.g., a raw air intake tube ), and a connection mechanism 3613 (e.g., a gasket). FIG. 4 illustrates an example of the inside of the crankcase 3300, and shows the tube structure 3611 (e.g., raw air intake tube) and the connection mechanism 3613 (e.g., gasket). As a person skilled in the art would appreciate that the crankcase 3300 includes other parts and components that are not labeled or described, since they do not form part of the underlying invention disclosed herein. The sensor system 3610 in this example may include a sensor and a magnet. More specifically, FIGS.5 and 6 illustrate a sensor 3612 and an example magnet 3614 and the magnetic flux 3619 in relation to the magnet 3614. The magnet may be any shape, and in this embodiment, a toroidal magnet shape is chosen in order to apply a perpendicular magnetic field to the sensor 3612. As one who is skilled in the art knows, the optimum position for sensor 3612 (e.g., hall sensor) is dependent on the magnet 3614 position, and the scope of the invention is not intended to be limited to any particular position of sensor 3612 or magnet 3614.

[0062] FIG. 5 illustrates crankcase 3300 with a sensor 3612 and a magnet 3614 according to an embodiment hereof. According to some embodiments, the sensor 3612 may be composed of a hall sensor. A person skilled in the art would appreciate, a hall sensor is known in the art and is a device which is used to measure a magnetic field, more specifically, a hall sensor operates based on the hall effect, which is the production of a voltage difference across an electrical conductor when a magnetic field is applied perpendicular to the current flowing through the conductor. In operation, the hall sensor is configured to sense the magnetic flux 3619 being generated and provide or send a signal that is received by a controller, which can use the signal to determine a disconnection event. The vehicle 2000 may include one or more sensor systems 1610, and a module for processing sensor data 1651 associated with the sensor configured to acquire the sensor data 1651, in this instance the sensor data 1651 configured to relate to the hall sensor data.

[0063] FIG. 7 illustrates an example system for thermal management 1100 showing a cooling line 3140 for a cooling fluid for a battery 1200 of a vehicle 2000, with a sensor system 1610 according to an embodiment hereof. Pump 3130 is configured to circulate the cooling fluid through the cooling line 3140 with a gasket 3613 defining a connection mechanism with a magnet 3614 connected to the gasket 3613. In operation, the sensor 3612 is configured to sense the magnetic flux 3619 being generated and provide or send a signal that is received by a controller, which can use the signal to determine a disconnection event. FIG. 7 is a simplified illustration of a thermal management system 1100 for a battery 1200 of a vehicle 2000, and one skilled in the art would appreciate that the thermal management system 1100 includes other parts and components that are not labeled or described, since they do not form part of the underlying invention disclosed herein.

[0064] FIG. 8 illustrates a diagram of an example system 4000 for disconnection event monitoring and notification, according to an embodiment hereof. The vehicle 2000 may be configured to obtain the power data 1654 of the vehicle 2000. The power data 1654 can be indicative of a state of a battery 1200 or engine 1300 onboard the vehicle 2000. For instance, the power management system 1640 may monitor the battery temperature (e.g., via sensors of the vehicle 2000 and the sensor systems 1610) and the power data 1654 can indicate that the battery cooling tube is not connected.

[0065] The power data 1654 can be obtained from the power management system 1640 of the vehicle control system 1600 of the vehicle 2000. For instance, the power data 1654 may be shared between the power management system 1640 and other components of the vehicle control system 1600 of the vehicle 2000. As a result, components of the vehicle control system 160, such as the communications unit 1620, can utilize the power data 1654 to send information about the battery 1200 to computing devices. Based on the power data 1654, the vehicle 2000 (e.g., the power management system 1640) can determine that a disconnection event 1655 has occurred onboard the vehicle 2000.

[0066] In response to determining that the disconnection event 1655 has occurred, the vehicle 2000 (e.g., the power management system 1640) may generate a message 1621 associated with the power source (e.g., engine or battery) of the vehicle 2000 that corresponds to the disconnection event 1655. The message 1621 may be indicative of at least one of the disconnection event 1655. For example, the message 1621 may indicate that the state of the power system 1624, in this example a battery, is that a cooling tube is disconnected and that the disconnection event 1655 is complete disconnection of the tube.

[0067] A disconnection event 1655 can be detected by the power management system 1640 by measuring characteristics of a sensor 3612, such as voltage, change in magnetic field strength, and loss of signal, which may be stored as the power data 1654. For example, a voltage decrease or an impedance fluctuation may be detected by sensors in the battery 1200 (e.g., sensors of the vehicle 2000 and the sensor systems 1610) and the power management system 1640 may determine that the voltage is anomalous and may indicative of a disconnection event 1655.

[0068] The vehicle 2000 (e.g., the communications unit 1620) may output the message 1621 to one or more computing devices 2505 within the vehicle 2000. The computing devices 2505 from the vehicle 2000 can include the head unit 2630.

[0069] The vehicle 2000 (e.g., the communications unit 1620) may output the message 1621 to one or more computing devices 2505 remote from the vehicle 2000. The computing devices 2505 remote from the vehicle 2000 can include the user device 2505. For example, the message 1621 may be sent over the air from the vehicle 2000 to the user device 2505 associated with the user of the vehicle 2000. The computing devices 2505 remote from the vehicle 2000 can also include a plurality of user devices associated with users of the vehicle. For instance, the message 1621 may be sent over the air from the vehicle 2000 (e.g., the communications unit 1620) to the user devices (e.g., computers, phones, laptops, tablets, wearable devices, etc.) associated with the driver and the passengers of the vehicle 2000. In some implementations, the user, such as the owner of the vehicle 2000, can use a mobile application associated with the vehicle 2000 to identify the users and user devices to send the message 1621 notifying the user of a disconnection event 1623. In other implementations, users in addition to the owner of the vehicle 2000 can use a mobile application associated with the vehicle 2000 to configure their user device 25055 to receive the message 1621 of a disconnection event 1623 when the disconnection event 1655 occurs onboard the vehicle 2000.

[0070] In some examples, the vehicle 2000 (e.g., the power management system 1640) may be configured to predict that the disconnection event 1655 will occur. The vehicle 2000 (e.g., the communications unit 1620) may output the message 1621 to the one or more computing devices 2505, and the message 1621 can be an initial message 1621, regarding a disconnection event 1655 that indicates that the disconnection event is predicted to occur, via a disconnection event prediction 1622. For example, the power management system 1640 may monitor the voltage (e.g., via sensors of the vehicle 2000 and the sensor systems 1610) and the power data 1654 can indicate that the voltage fluctuations (rather than voltage loss) indicates the disconnection event 1655 is predicted to occur.

[0071] FIG. 9 illustrates a flowchart diagram of an example method 4100 according to an embodiment hereof. The method 4100 may be performed by a control system described with reference to the other figures. In an embodiment, the method 4100 may be performed by a controller of the vehicle control system 1600 of FIG. 7. One or more portions of the method 4100 may be implemented as an algorithm on the hardware components of the devices described herein. For example, the steps of method 4100 may be implemented as operations / instructions that are executable by computing hardware.

[0072] FIG. 9 illustrates elements performed in a particular order for purposes of illustration and discussion. Those of ordinary skill in the art, using the disclosures provided herein, will understand that the elements of any of the methods discussed herein may be adapted, rearranged, expanded, omitted, combined, or modified in various ways without deviating from the scope of the present disclosure. FIG. 9 is described with reference to elements / terms described with respect to other systems and figures for example illustrated purposes and is not meant to be limiting. One or more portions of method 4100 may be performed additionally, or alternatively, by other systems. For example, method 4100 may be performed by a controller of the vehicle control system 1600.

[0073] In an embodiment, the method 4100 may begin with or otherwise include an operation 4105, in which, the vehicle control system 1600 may determine that the vehicle 2000 has received a signal in response to a sensor detecting a change in a magnetic field of a magnet.

[0074] The method 1621 in an embodiment may include an operation 4110, in which the vehicle control system 1600 may obtain, power data 1654 indicative of a state of a battery cooling tube onboard the vehicle 2000. For example, the vehicle control system 1600 of the vehicle 2000 may obtain power data 1654 indicating that the tube structure within the vehicle is such that it is not connected.

[0075] The method 4100 in an embodiment may include an operation 4115, in which the vehicle control system 1600 in response to determining the occurrence of the disconnection event 1655, generates a message 1621 associated with the vehicle 2000. For example, the message 1621 may indicate that the state 1624 of the power system, in this example a battery, is that a cooling tube is disconnected and that the disconnection event 1655 is complete disconnection of the tube.

[0076] The method 4100, in an embodiment may include an operation 4115, where the vehicle 2000 (e.g., the power management system 1640) may be configured to predict that the disconnection event 1655 will occur. The vehicle 2000 (e.g., the communications unit 1620) may output the message 1621 to the one or more computing devices 2505, and the message 1621 can be an initial message with a disconnection event prediction 1622 that indicates that the disconnection event 1655 is predicted to occur. For example, the power management system 1640 may monitor the voltage (e.g., via sensors of the vehicle 2000 and the sensor systems 16101610) and the power data 1654 can indicate that the voltage fluctuations (rather than voltage loss) indicate the disconnection event 1655 is predicted to occur.

[0077] The method 4100, in an embodiment may include an operation 4115, where the vehicle 2000 may output the message 1621 to one or more computing devices 2505 remote from the vehicle 2000. For instance, the message 1621 may be sent over the air from the vehicle 2000 (e.g., the communications unit 1620) to the user devices (e.g., computers, phones, laptops, tablets, wearable devices, etc.) associated with the driver and the passengers of the vehicle 2000. In some implementations, the user, such as the owner of the vehicle 2000, can use a mobile application associated with the vehicle 2000 to identify the users and user devices to send the message 1621 notifying the user of a disconnection event 1655, via a message of the disconnection event 1623. In other implementations, users in addition to the owner of the vehicle 2000 can use a mobile application associated with the vehicle 2000 to configure their user device 2505 to receive the message 1621 when the disconnection event 1655 occurs onboard the vehicle 2000.

[0078] FIG. 10 illustrates a diagram of an example control ecosystem 4200 with computing components according to an embodiment hereof. The control ecosystem 4200 includes a computing system 4300 (e.g., a computing system onboard a vehicle), a server computing system 4400 (e.g., a remote computing system, cloud computing platform), and a user device 4500 that are communicatively coupled over one or more networks 4435.

[0079] The computing system 4300 may include one or more computing devices 4305 or circuitry. For instance, the computing system 4300 may include a control circuit 4310 and a non-transitory computer-readable medium 4315, also referred to herein as memory. In an embodiment, the control circuit 4310 may include one or more processors (e.g., microprocessors), one or more processing cores, a programmable logic circuit (PLC) or a programmable logic / gate array (PLA / PGA), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other control circuit. In some implementations, the control circuit 4310 may be part of, or may form, a vehicle control unit (also referred to as a vehicle controller) that is embedded or otherwise disposed in a vehicle (e.g., a Mercedes-Benz® car or van). For example, the vehicle controller may be or may include an infotainment system controller (e.g., an infotainment head-unit), a telematics control unit (TCU), an electronic control unit (ECU), a central powertrain controller (CPC), a charging controller, a central exterior &interior controller (CEIC), a zone controller, or any other controller. In an embodiment, the control circuit 4310 may be programmed by one or more computer-readable or computer-executable instructions stored on the non-transitory computer-readable medium 4315.

[0080] In an embodiment, the non-transitory computer-readable medium 4315 may be a memory device, also referred to as a data storage device, which may include an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. The non-transitory computer-readable medium 4315 may form, e.g., a hard disk drive (HDD), a solid state drive (SDD) or solid state integrated memory, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), dynamic random access memory (DRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), and / or a memory stick.

[0081] The non-transitory computer-readable medium 4315 may store information that may be accessed by the control circuit 4310. For instance, the non-transitory computer-readable medium 4315 (e.g., memory devices) may store data 4320 that may be obtained, received, accessed, written, manipulated, created, and / or stored. The data 4320 may include, for instance, any of the data or information described herein. In some implementations, the computing system 4300 may obtain data from one or more memories that are remote from the computing system 4300.

[0082] The non-transitory computer-readable medium 4315 may also store computer readable instructions 4325 that may be executed by the control circuit 4310. The instructions 4325 may be software written in any suitable programming language or may be implemented in hardware. The instructions may include computer-readable instructions, computer-executable instructions, etc. As described herein, in various embodiments, the terms “computer-readable instructions” and “computer-executable instructions” are used to describe software instructions or computer code configured to carry out various tasks and operations. In various embodiments, if the computer-readable or computer-executable instructions form modules, the term “module” refers broadly to a collection of software instructions or code configured to cause the control circuit 4310 to perform one or more functional tasks. The modules and computer readable / executable instructions may be described as performing various operations or tasks when the control circuit 4310 or other hardware component is executing the modules or computer-readable instructions.

[0083] The instructions 4325 may be executed in logically and / or virtually separate threads on the control circuit 4310. For example, the non-transitory computer-readable medium 4315 may store instructions 4325 that when executed by the control circuit 4310 cause the control circuit 4310 to perform any of the operations, methods and / or processes described herein. In some cases, the non-transitory computer-readable medium 4315 may store computerexecutable instructions or computer-readable instructions, such as instructions to perform at least a portion of the method of FIG. 9.

[0084] The computing system 4300 may include one or more communication interfaces 4330. The communication interfaces 4330 may be used to communicate with one or more other systems. The communication interfaces 4330 may include any circuits, components, software, etc. for communicating via one or more networks (e.g., networks 4435). In some implementations, the communication interfaces 4330 may include for example, one or more of a communications controller, receiver, transceiver, transmitter, port, conductors, software and / or hardware for communicating data / information.

[0085] The computing system 4300 may also include one or more user input components 4335 that receives user input. For example, the user input component 4335 may be a touch sensitive component (e.g., a touch-sensitive display screen or a touch pad) that is sensitive to the touch of a user input object (e.g., a finger or a stylus). The touch-sensitive component may serve to implement a virtual keyboard. Other example user input components include a microphone, a traditional keyboard, cursor-device, joystick, or other devices by which a user may provide user input.

[0086] The computing system 4300 may include one or more output components 4340. The output components 4340 may include hardware and / or software for audibly or visually producing content. For instance, the output components 4340 may include one or more speakers, earpieces, headsets, handsets, etc. The output components 4340 may include a display device, which may include hardware for displaying a user interface and / or messages for a user. By way of example, the output component 4340 may include a display screen, CRT, LCD, plasma screen, touch screen, TV, projector, tablet, and / or other suitable display components.

[0087] The remote (server) computing system 4400 may include one or more computing devices 44540. In an embodiment, the server computing system 4400 may include or is otherwise implemented by one or more server computing devices. In instances in which the server computing system 4400 includes plural server computing devices, such server computing devices may operate according to sequential computing architectures, parallel computing architectures, or some combination thereof.

[0088] The server computing system 4400 may include a control circuit 4410 and a non-transitory computer-readable medium 4415, also referred to herein as memory 4415. In an embodiment, the control circuit 4410 may include one or more processors (e.g., microprocessors), one or more processing cores, a programmable logic circuit (PLC) or a programmable logic / gate array (PLA / PGA), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other control circuit. In an embodiment, the control circuit 4410 may be programmed by one or more computer-readable or computer executable instructions stored on the non-transitory computer-readable medium 4415.

[0089] In an embodiment, the non-transitory computer-readable medium 4415 may be a memory device, also referred to as a data storage device, which may include an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. The non-transitory computer-readable medium may form, e.g., a hard disk drive (HDD), a solid state drive (SDD) or solid state integrated memory, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), dynamic random access memory (DRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), and / or a memory stick.

[0090] The non-transitory computer-readable medium 4415 may store information that may be accessed by the control circuit 4410. For instance, the non-transitory computer-readable medium 4415 (e.g., memory devices) may store data 4420 that may be obtained, received, accessed, written, manipulated, created, and / or stored. The data 4420 may include, for instance, any of the data or information described herein. In some implementations, the server computing system 4400 may obtain data from one or more memories that are remote from the server computing system 4400.

[0091] The non-transitory computer-readable medium 4415 may also store computer readable instructions 4425 that may be executed by the control circuit 4410. The instructions 4425 may be software written in any suitable programming language or may be implemented in hardware. The instructions may include computer-readable instructions, computer-executable instructions, etc. As described herein, in various embodiments, the terms “computer-readable instructions” and “computer-executable instructions” are used to describe software instructions or computer code configured to carry out various tasks and operations. In various embodiments, if the computer-readable or computer-executable instructions form modules, the term “module” refers broadly to a collection of software instructions or code configured to cause the control circuit 4410 to perform one or more functional tasks. The modules and computer readable / executable instructions may be described as performing various operations or tasks when the control circuit 4410 or other hardware component is executing the modules or computer-readable instructions.

[0092] The instructions 4425 may be executed in logically and / or virtually separate threads on the control circuit 4410. For example, the non-transitory computer-readable medium 4415 may store instructions 4425 that when executed by the control circuit 4410 cause the control circuit 4410 to perform any of the operations, methods and / or processes described herein. In some cases, the non-transitory computer-readable medium 4415 may store computerexecutable instructions or computer-readable instructions, such as instructions to perform at least a portion of the method of FIG. 9.

[0093] The server computing system 4400 may include one or more communication interfaces 4430. The communication interfaces 4430 may be used to communicate with one or more other systems. The communication interfaces 4430 may include any circuits, components, software, etc. for communicating via one or more networks (e.g., networks 4435). In some implementations, the communication interfaces 4430 may include for example, one or more of a communications controller, receiver, transceiver, transmitter, port, conductors, software and / or hardware for communicating data / information.

[0094] The computing system 4300 and / or the server computing system 4400 may also be in communication with a user device 4500 that is communicatively coupled over the networks 4435.

[0095] The user device 4500 may include one or more computing devices 4505. The user device 4500 may include a control circuit 4510 and a non-transitory computer-readable medium 4515, also referred to herein as memory 4515. In an embodiment, the control circuit 4510 may include one or more processors (e.g., microprocessors), one or more processing cores, a programmable logic circuit (PLC) or a programmable logic / gate array (PLA / PGA), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or any other control circuit. In an embodiment, the control circuit 4510 may be programmed by one or more computer-readable or computer-executable instructions stored on the non-transitory computer-readable medium 4515.

[0096] In an embodiment, the non-transitory computer-readable medium 8020 may be a memory device, also referred to as a data storage device, which may include an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. The non-transitory computer-readable medium may form, e.g., a hard disk drive (HDD), a solid state drive (SDD) or solid state integrated memory, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), dynamic random access memory (DRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), and / or a memory stick.

[0097] The non-transitory computer-readable medium 4515 may store information that may be accessed by the control circuit 4510. For instance, the non-transitory computer-readable medium 4515 (e.g., memory devices) may store data 4520 that may be obtained, received, accessed, written, manipulated, created, and / or stored. The data 4520 may include, for instance, any of the data or information described herein. In some implementations, the user device 4500 may obtain data from one or more memories that are remote from the user device4500.

[0098] The non-transitory computer-readable medium 4515 may also store computer-readable instructions 4525 that may be executed by the control circuit 4510. The instructions 4525 may be software written in any suitable programming language or may be implemented in hardware. The instructions may include computer-readable instructions, computer-executable instructions, etc. As described herein, in various embodiments, the terms “computer-readable instructions” and “computer-executable instructions” are used to describe software instructions or computer code configured to carry out various tasks and operations. In various embodiments, if the computer-readable or computer-executable instructions form modules, the term “module” refers broadly to a collection of software instructions or code configured to cause the control circuit 4510 to perform one or more functional tasks. The modules and computer-readable / executable instructions may be described as performing various operations or tasks when the control circuit 4510 or other hardware component is executing the modules or computer-readable instructions.

[0099] The instructions 4525 may be executed in logically or virtually separate threads on the control circuit 4510. For example, the non-transitory computer-readable medium 4515 may store instructions 4525 that when executed by the control circuit 4510 cause the control circuit 4510 to perform any of the operations, methods and / or processes described herein. In some cases, the non-transitory computer-readable medium 4515 may store computer-executable instructions or computer-readable instructions, such as instructions to perform at least a portion of the method of FIG. 9.

[0100] The user device 4500 may include one or more communication interfaces 4530. The communication interfaces 4530 may be used to communicate with one or more other systems. The communication interfaces 4530 may include any circuits, components, software, etc. for communicating via one or more networks (e.g., networks 4435). In some implementations, the communication interfaces 4530 may include for example, one or more of a communications controller, receiver, transceiver, transmitter, port, conductors, software and / or hardware for communicating data / information.

[0101] The user device 4500 may also include one or more user input components 4535 that receives user input. For example, the user input component 4535 may be a touch-sensitive component (e.g., a touch-sensitive display screen or a touch pad) that is sensitive to the touch of a user input object (e.g., a finger or a stylus). The touch-sensitive component may serve to implement a virtual keyboard. Other example user input components include a microphone, a traditional keyboard, cursor-device, joystick, or other devices by which a user may provide user input.

[0102] The user device 4500 may include one or more output components . The output components 4540 may include hardware and / or software for audibly or visually producing content. For instance, the output components 4540 may include one or more speakers, earpieces, headsets, handsets, etc. The output components 4540 may include a display device, which may include hardware for displaying a user interface and / or messages for a user. By way of example, the output component 4540 may include a display screen, CRT, LCD, plasma screen, touch screen, TV, projector, tablet, and / or other suitable display components.

[0103] The one or more networks 4435 may be any type of communications network, such as a local area network (e.g., intranet), wide area network (e.g., Internet), or some combination thereof and may include any number of wired or wireless links. In general, communication over a network 4435 may be carried via any type of wired and / or wireless connection, using a wide variety of communication protocols (e.g., TCP / IP, HTTP, SMTP, FTP), encodings or formats (e.g., HTML, XML), and / or protection schemes (e.g., VPN, secure HTTP, SSL).

Claims

1. A sensor system (1610) for a vehicle comprising:a tube structure (3611) defining a connection point (3612);a sensor (3612) connected to an outer portion of the tube structure;a connection mechanism (3613) defining a seal; anda magnet (3614) connected to the connection mechanism (3613),the sensor (3612) operable with the magnet (3614) to detect a change in a magnetic field (3619) of the magnet when a disconnection occurs.

2. The sensor system (1610) of claim 1, wherein the change in the magnetic field (3619) comprises a reduction in a magnetic field (3619) strength.

3. The sensor system (1610) of claim 1, wherein the reduction in the magnetic field (3619) strength is indicative of an increase in a distance between the sensor (3612) and the magnet (3614).

4. The sensor system (1610) of claim 1, further comprising:a controller (1660A-C) communicatively connected with the sensor (3612), the controller (1660A-C) operable to receive a signal from the sensor (3612) in response to the change in the magnetic field (3619) and output an alert notification.

5. The sensor system (1610) of claim 4, wherein the alert notification is indicative of a disconnection or a misalignment of the tube structure.

6. The sensor system (1610) of claim 4, wherein the controller (1660A-C) is communicatively connected to a computing device and the controller (1660A-C) is operable to output the alert notification to the computing device.

7. The sensor system (1610) of claim 6, wherein the computing device is a head unit (2632) device of the vehicle or a user computing device (2500).

8. The sensor system (1610) of claim I, wherein the sensor (3612) is a hall sensor.

9. The sensor system (1610) of claim 1, wherein the sensor (3612) and the magnet (3614)are separated by a wall of the tube structure.

10. The sensor system (1610) of claim 9, wherein the tube structure comprises a fluid line associated with an engine 1300 of the vehicle.

11. The sensor system (1610) of claim 9, wherein the tube structure comprises a cooling line (3140) for a cooling fluid for a battery 1200 of the vehicle.

12. The sensor system (1610) of claim 1, wherein the connection mechanism (3613) is a gasket.

13. A control system comprising:a controller (1660A-C);a sensor (3612) communicatively connected to the controller (1660A-C). the sensor (3612) being connected to an outer portion of a tube structure defining a connection point (3612);a connection mechanism (3613) defining a seal; anda magnet (3614) connected to the connection mechanism (3613),the sensor (3612) operable with the magnet (3614) to detect a change in a magnetic field (3619) of the magnet (3614), and transmit a signal to the controller (1660A-C) based on the change in the magnetic field (3619) when a disconnection (1655) occurs.

14. The control system of claim 13, wherein the controller (1660A-C) is operable to outputan alert notification based on the signal from the sensor (3612).

15. The control system of claim 14, wherein the alert notification is indicative of a disconnection or a misalignment (1655) of the tube structure.

16. The control system of claim 13, wherein the change in the magnetic field (3619) comprises a reduction in a magnetic field (3619) strength.

17. The control system of claim 13, wherein the reduction in the magnetic field (3619)strength is indicative of an increase in a distance between the sensor (3612) and the magnet(3614).

18. The control system of claim 13, wherein the sensor (3612) is a hall sensor.

19. The control system of claim 13, wherein the sensor (3612) and the magnet (3614) areseparated by a wall of the tube structure.

20. A computer-implemented method comprising:receiving, by a controller (1660A-C), a signal from a sensor (3612), wherein the sensor (3612) is connected to an outer portion of a tube structure defining a connection point (3612), and wherein the signal is in response to the sensor (3612) detecting a change in a magnetic field (3619) of a magnet (3614), the magnet (3614) being connected to a connection mechanism (3613) defining a seal;determining, by the controller (1660A-C), an occurrence of a disconnection or a misalignment (1655) associated with the tube structure based on the signal from the sensor (3612); andoutputting over a network (4435), by the controller (1660A-C) to a computing device, an alert notification (1621) indicative of the disconnection or misalignment (1655) associated with the tube structure (3611).

Images