This disclosure relates generally to lubrication systems, and more particularly to automatic lubrication systems for vehicles.
Vehicles, such as commercial cargo trucks, construction equipment, buses, and other vehicles often utilize automatic lubrication systems to deliver lubricant to various components and systems of the vehicle, such as bearings, joints, braking systems, steering assemblies, or other lubricated regions of the vehicle. Often, such automatic lubrication systems utilize a controller device that actuates a pump to deliver controlled amounts of lubricant (using, e.g., a lubricant metering device) according to a defined lubrication schedule, such as at every hour of operation of the vehicle.
Lubrication schedules are typically manually programmed via a user interface of the controller, and are often based upon an expected operational use of the vehicle. For instance, because increased turning, braking, shifting, stopping and starting, as well as high temperatures and wet environments can result in increased deterioration and loss of lubricant, higher lubrication frequencies are often utilized when such operational scenarios are expected. In contrast, when expected operation of the vehicle includes fewer stops, starts, braking, shifting, etc., lower lubrication frequencies can be utilized.
Actual operational use of the vehicle, however, may deviate from the expected use. For instance, a particular commercial cargo truck (e.g., within a fleet) that is designated for use in long-haul scenarios, thereby utilizing a relatively low lubrication frequency, may actually be used at any given time for shorter trips including more frequent starts, stops, and gear changes. As such, a low lubrication frequency utilized by the lubrication system (i.e., according to a manually-programmed lubrication schedule) may not adequately meet the lubrication demands of the cargo truck in the operational scenario in which it is actually utilized. Similarly, operational scenarios of vehicles can change between or within working days, thereby decreasing the accuracy of predicted use scenarios and the corresponding lubrication schedules that are programmed into the lubrication system controller. Moreover, because programming of lubrication system controllers to modify lubrication schedules can be cumbersome and time-consuming, such lubrication schedule modifications are often overlooked or otherwise ignored.
Accordingly, typical automatic lubrication systems requiring manual programming of the lubrication schedules may provide lubricant to components at a frequency that does not correspond to actual operational use of the vehicle. As such, the use of manually-programmed automatic lubrication systems can, in certain cases, result in over-lubrication that can increase the build-up of heat within and around components, waste lubricant, and increase labor costs, as well as under-lubrication that can increase component wear, vehicle energy use, and overall operating costs of the vehicle.
In one example, a vehicle lubrication system includes a plurality of sensors disposed on the vehicle, a pump disposed on the vehicle, and a controller device operatively coupled to the pump. The plurality of sensors are configured to sense operational characteristics of the vehicle. The pump is configured to deliver lubricant to a plurality of lubricated regions of the vehicle. The controller device is configured to receive sensor data corresponding to the operational characteristics of the vehicle sensed by the plurality of sensors, and determine, based on the received sensor data, a lubricant delivery frequency at which lubrication is to be delivered to the plurality of lubricated regions of the vehicle. The controller is further configured to provide control commands to cause the pump to deliver the lubricant to the plurality of lubricated regions according to the determined lubricant delivery frequency.
In another example, a method includes sensing operational characteristics of a vehicle using a plurality of sensors disposed on the vehicle. The method further includes receiving, by a controller device, sensor data corresponding to the operational characteristics of the vehicle sensed by the plurality of sensors, and determining, by the controller device based on the received sensor data, a lubrication schedule defining a frequency of lubricant delivery to a plurality of lubricated regions of the vehicle. The method further includes providing control commands to cause a pump to deliver lubricant to the plurality of lubricated regions according to the lubrication schedule.
As described herein, a vehicle lubrication system adaptively determines a lubrication schedule (i.e., a frequency of lubricant delivery) for lubricated regions of the vehicle based on data corresponding to operational characteristics (e.g., vehicle usage characteristics, environmental characteristics, or other operational characteristics) sensed by a plurality of sensors disposed on the vehicle. Such sensors can include, e.g., temperature sensors, accelerometers, rotation sensors, brake actuation and/or wear sensors, speed sensors, pressure sensors, or any other type of sensor disposed on the vehicle and capable of sensing characteristics of the operational use of the vehicle and/or environment within which the vehicle operates. In some examples, the sensors may be disposed on the vehicle and configured to transmit the operational data to, e.g., an engine control module or other electronic control unit of the vehicle over a communications data bus, such as a Controller Area Network (CAN) bus. In such examples, the lubrication system controller can receive the sensor data via the communications data bus and can determine a lubricant delivery frequency based on the received data corresponding to the operational characteristics of the vehicle. Accordingly, a lubrication system implementing techniques of this disclosure can deliver lubricant to components of the vehicle at a frequency that corresponds to the actual operational use of the vehicle, thereby reducing the cost, maintenance efforts, and potential component wear that can result from under-lubrication and over-lubrication of the components.
In the example of
As is further described below, vehicle 10 includes a lubrication system that utilizes various sensors positioned about vehicle 10 that sense data corresponding to operational characteristics of vehicle 10. Operational characteristics can include vehicle usage characteristics corresponding to operational use of vehicle 10 (e.g., steering characteristics, braking characteristics, transmission operational characteristics, load characteristics, component temperature characteristics, or any other operational characteristics associated with operational use of vehicle 10) and/or environmental characteristics corresponding to an operational environment of vehicle 10, such as temperature, the presence and/or amount of liquid water in the operational environment, or any other characteristics of the environment in which vehicle 10 operates.
The lubrication system of vehicle 10, as is further described below, utilizes the data received from the various sensors via, e.g., a Controller Area Network (CAN) bus or other communications data bus to determine a lubricant delivery frequency at which lubrication is to be delivered to lubricated regions 12A-12M during operation of vehicle 10. The lubricant delivery frequency (or schedule) is therefore adaptively determined based on sensed data corresponding to actual operational use, rather than merely an expected use of vehicle 10. Accordingly, the lubrication system of vehicle 10 can deliver lubricant to lubricated regions 12A-12M at a frequency that more closely aligns with the lubrication needs under the actual operating scenario of vehicle 10, thereby reducing the occurrences of under-lubrication and/or over-lubrication of lubricated regions 12A-12M.
Controller 16 is configured to control operation of lubrication delivery system 14 (e.g., a pump of lubrication delivery system 14) to deliver lubricant to lubricated regions at a lubricant delivery schedule determined based on sensed data received from sensors 18, as is further described below. Controller 16 includes one or more processors and computer-readable memory encoded with instructions that, when executed by the one or more processors, cause controller 16 to operate in accordance with techniques described herein. Processor(s) of controller 16 are configured to implement functionality and/or process instructions for execution within controller 16. Examples of processor(s) of controller 16 can include any one or more of a microprocessor, a controller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other equivalent discrete or integrated logic circuitry.
Computer-readable memory of controller 16 can be configured to store information within controller 16 during operation. Computer-readable memory, in some examples, can be described as computer-readable storage media. In some examples, a computer-readable storage medium can include a non-transitory medium. The term “non-transitory” can indicate that the storage medium is not embodied in a carrier wave or a propagated signal. In certain examples, a non-transitory storage medium can store data that can, over time, change (e.g., in RAM or cache). Computer-readable memory of controller 16 can include volatile and non-volatile storage elements. Examples of volatile storage elements can include random access memories (RAM), dynamic random access memories (DRAM), static random access memories (SRAM), and other forms of volatile memories. Examples of non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
While illustrated in the example of
Sensors 18 include, e.g., temperature sensors, accelerometers, rotation sensors, brake actuation and/or wear sensors, speed sensors, pressure sensors, windshield wiper actuation sensors, or any other type of sensor capable of sensing characteristics of the operational use and/or environment within which vehicle 10 operates. Sensors 18 can be disposed at various locations of vehicle 10 to sense operational characteristics of various components of vehicle 10. In some examples, sensors 18 can be disposed at the various locations of vehicle 10 for sensing the operational characteristics and transmitting the sensed data to ECM 20, TCM 22, or other electronic control units of vehicle 10 for operational control of vehicle 10, health and usage management of the components, maintenance and/or fault diagnostics, and/or other operational control and maintenance management of vehicle 10. In certain examples, sensors 18 can be disposed at one or more components of lubrication delivery system 14 (e.g., a pump of lubrication delivery system 14) for use in determining a lubrication delivery schedule at which lubricant is delivered to lubricated regions of vehicle 10.
ECM 20 and TCM 22 are electronic control units that manage operational control of an engine of vehicle 10 (i.e., ECM 20) and a transmission (e.g., an automatic transmission) of vehicle 10 (i.e., TCM 22). For example, ECM 20 can be an electronic control unit that controls actuators, valves, ignition timing, fuel injection, air/fuel ratio, engine running and/or idling speed, or other operational parameters associated with control of the engine of vehicle 10. TCM 22 can be, for example, an electronic control unit that controls when and how to change gears of a transmission of vehicle 10 based on data received from ECM 20 and/or sensors 18 positioned about vehicle 10.
As illustrated in
ECM 20 and TCM 22 receive data from sensors 18 via the communications data bus for operational control of vehicle 10. Sensors 18, positioned about vehicle 10 and configured to sense data corresponding to operational characteristics of vehicle 10, transmit sensed data on the data bus. Data transmitted by sensors 18 is received by ECM 20 and TCM 22 and utilized for operational control of vehicle 10. ECM 20 and TCM 22 can, in certain examples, transmit data over the communications data bus for use by each other and/or other electronic control modules of vehicle 10. While illustrated and described as including control modules ECM 20 and TCM 22, it should be understood that vehicle 10, in certain examples, can include additional control modules, such as a battery control module or other control modules that can be communicatively coupled with any one or more of sensors 18 and/or controller 16 via the communications data bus. In other examples, vehicle 10 may not include one or more of ECM 20 and TCM 22.
Controller 16, as illustrated in
Controller 16 can store (e.g., at computer-readable memory of controller 16) information that relates each of the operational characteristics to a target lubrication schedule that defines a frequency of lubricant delivery based on a magnitude and/or state of the functional parameter. Information stored by controller 16 relating each of the operational characteristics to the corresponding target lubrication schedules can take the form of tables (e.g., look-up tables) or other data structures, functional equations, algorithms (e.g., fuzzy logic algorithms, artificial intelligence algorithms, or other algorithms), or any other form that relates the operational characteristics to a target lubrication schedule.
For example, controller 16 can store information that relates an operational characteristic corresponding to a frequency and/or degree of actuation of a steering system of vehicle 10 to a target frequency of lubricant delivery to the lubricated regions of vehicle 10. Increased frequency and/or degree of actuation of the steering system can correspond (e.g., linearly or non-linearly) to an increased target frequency of lubricant delivery. Decreased frequency and/or degree of actuation of the steering system can correspond to a decreased target frequency of lubricant delivery. Similarly, controller 16 can store information that relates each of a plurality of operational characteristics to a corresponding target frequency of lubricant delivery, such as braking characteristics, transmission characteristics, load characteristics, component temperature characteristics, tire pressure characteristics, speed characteristics, mileage characteristics, environmental temperature characteristics, liquid water characteristics, or any other vehicle usage and/or environmental characteristics of vehicle 10.
Braking characteristics indicating an increased frequency and/or degree of actuation of a braking system of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Transmission characteristics indicating an increased frequency and/or degree of actuation of a transmission system of vehicle 10 to change direction of motion or gear ratios of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Load characteristics indicating an increased operational weight of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Component temperature characteristics indicating an increased temperature of one or more components of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Tire pressure characteristics indicating a decreased air pressure within tires of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Speed characteristics indicating an increased speed of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Mileage characteristics indicating an increased distance traveled by vehicle 10 can correspond to an increased target frequency of lubricant delivery. Environmental temperature characteristics indicating an increased temperature of an operational environment of vehicle 10 can correspond to an increased target frequency of lubricant delivery. Liquid water characteristics indicating an increased amount and/or presence of liquid water in the operational environment of vehicle 10 (e.g., rain, submersion, or other presence of liquid water) can correspond to an increased target frequency of lubricant delivery.
Controller 16 determines a lubrication schedule defining a lubrication delivery frequency at which lubricant is to be delivered to lubricated regions 12A-12M (
In other examples, controller 16 can determine the lubrication schedule using an average, a weighted average, a mathematical mode, or other central tendency of the plurality of target frequencies corresponding to the associated operational characteristics. For instance, controller 16 can identify a target frequency of lubricant delivery corresponding to each of the operational characteristics of vehicle 10, and can determine the lubrication delivery schedule that is utilized for delivery of lubricant to lubricated regions 12A-12M (
As such, a lubrication system implementing techniques of this disclosure can deliver lubricant to components or other lubricated regions of vehicle 10 at a frequency that corresponds to sensed operational characteristics associated with actual use, rather than merely an expected use, of vehicle 10. Accordingly, techniques of this disclosure can reduce the cost, maintenance efforts, and potential component wear and breakdown that can result from under-lubrication and over-lubrication of the components.
Pump 24 is operatively connected (e.g., electrically and/or communicatively connected) to receive control commands from controller 16. Pump 24 is fluidly connected to each of lubricant reservoir 16 and lubricant metering device 28. Lubricant metering device 28 is fluidly connected to deliver a controlled volume of lubricant to each of lubricated regions 12A-12M via injectors 30A-30M.
Reservoir 26 is configured to store lubricant for delivery to lubricated regions 12A-12M via pump 24 and lubricant metering device 28. Pump 24 can be a positive displacement pump (e.g., a piston pump, a diaphragm pump, or other type of positive displacement pump), a centrifugal pump, or any other type of pump suitable for drawing lubricant from reservoir 26 and delivering the lubricant under pressure to metering device 28. Injectors 30A-30M are each configured (e.g., manually configured) to deliver a defined volume (e.g., same or different defined volumes) of lubricant to a corresponding one of lubricated regions 12A-12M. While illustrated and described as injectors, in other examples, any one or more of injectors 30A-30M can take the form of a divider valve, a piston distributor, or any other device capable of delivering a defined volume of lubricant to a corresponding one of lubricated regions 12A-12M.
In operation, controller 16 provides control commands (e.g., electrical and/or communicative control commands) to pump 24 to cause pump 24 to deliver lubricant to metering device 28 at a determined lubrication delivery schedule. Pump 24, in response to control commands received from controller 16, draws lubricant from reservoir 26 and delivers the lubricant under pressure to metering device 28. Injectors 30A-30M each receive lubricant via metering device 28 and deliver a defined volume of lubricant to a corresponding one of lubricated regions 12A-12M.
Accordingly, controller 16 provides control commands to lubrication delivery system 14 to cause lubricant to be delivered to each of lubricated regions 12A-12M at a lubrication delivery schedule that is adaptively determined based on sensed data corresponding to operational characteristics of vehicle 10. Techniques of this disclosure can therefore help to ensure that lubricant is delivered to lubricated regions 12A-12M at a frequency that corresponds to actual operational use of vehicle 10, thereby reducing the cost, maintenance efforts, and potential component wear that can result from under-lubrication and over-lubrication of the various lubricated regions.
While the invention has been described with reference to an exemplary embodiment(s), it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiment(s) disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.
This application claims priority from U.S. Provisional Application Ser. No. 62/416,451, filed Nov. 2, 2016, and entitled ELECTRIC ON ROAD MOBILE PUMP, which is hereby incorporated by reference in its entirety.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2017/059477 | 11/1/2017 | WO |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2018/085355 | 5/11/2018 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
3659675 | Edelstein | May 1972 | A |
4787479 | Ostermeyer et al. | Nov 1988 | A |
4967881 | Meuer | Nov 1990 | A |
5327347 | Hagenbuch | Jul 1994 | A |
5381874 | Hadank | Jan 1995 | A |
5417308 | Hartl | May 1995 | A |
5465810 | Peterson | Nov 1995 | A |
5482138 | Mori | Jan 1996 | A |
5485895 | Peterson | Jan 1996 | A |
6138065 | Kramer | Oct 2000 | A |
6253601 | Wang et al. | Jul 2001 | B1 |
6370454 | Moore | Apr 2002 | B1 |
6758266 | Sjunnesson | Jul 2004 | B1 |
6856879 | Arakawa et al. | Feb 2005 | B2 |
6959235 | Abdel-Malek et al. | Oct 2005 | B1 |
7017712 | Rake | Mar 2006 | B1 |
7140468 | Rake | Nov 2006 | B2 |
7286916 | Hoeflacher et al. | Oct 2007 | B2 |
7483774 | Grichnik et al. | Jan 2009 | B2 |
7535347 | Larson et al. | May 2009 | B2 |
7706938 | Palladino | Apr 2010 | B2 |
8131420 | Lynch et al. | Mar 2012 | B2 |
8196708 | Kung | Jun 2012 | B2 |
8285437 | Kubota et al. | Oct 2012 | B2 |
8306797 | Furem et al. | Nov 2012 | B2 |
8355836 | Silvester | Jan 2013 | B2 |
8400296 | Brinton et al. | Mar 2013 | B2 |
8478477 | Maisonneuve et al. | Jul 2013 | B2 |
8533018 | Miwa et al. | Sep 2013 | B2 |
8594883 | Gilbert | Nov 2013 | B2 |
8731766 | Artus | May 2014 | B2 |
8739932 | Ramler | Jun 2014 | B2 |
8794210 | Liimatta | Aug 2014 | B2 |
8810385 | McQuade et al. | Aug 2014 | B2 |
8844680 | Alguera | Sep 2014 | B2 |
8849475 | Sudolsky et al. | Sep 2014 | B1 |
9008895 | Patankar | Apr 2015 | B2 |
20020148528 | Matthews | Oct 2002 | A1 |
20060136105 | Larson | Jun 2006 | A1 |
20070261922 | Mullen | Nov 2007 | A1 |
20090057063 | Marek | Mar 2009 | A1 |
20090191060 | Bagepalli | Jul 2009 | A1 |
20100147627 | Lakomiak et al. | Jun 2010 | A1 |
20100321030 | Gale | Dec 2010 | A1 |
20130277148 | Beck | Oct 2013 | A1 |
20130336764 | Schmidt | Dec 2013 | A1 |
20140010668 | Sah | Jan 2014 | A1 |
20140048354 | Kolekar | Feb 2014 | A1 |
20140116808 | Kile | May 2014 | A1 |
20140238742 | Borek | Aug 2014 | A1 |
20160160713 | Reedy | Jun 2016 | A1 |
20160169448 | Holman | Jun 2016 | A1 |
20160298755 | Kotsuji | Oct 2016 | A1 |
20180371969 | McCormick | Dec 2018 | A1 |
20190301319 | Uyama | Oct 2019 | A1 |
20210402614 | Pavlik | Dec 2021 | A1 |
Number | Date | Country |
---|---|---|
20150102104 | Sep 2015 | KR |
Entry |
---|
International Preliminary Report on Patentability for International Application No. PCT/US2017/059477 dated May 7, 2019, 11 pages. |
International Search Report and Written Opinion for International Application No. PCT/US2017/059477 dated Feb. 26, 2018, 15 pages. |
Number | Date | Country | |
---|---|---|---|
20190263341 A1 | Aug 2019 | US |
Number | Date | Country | |
---|---|---|---|
62416451 | Nov 2016 | US |