Container, Method and Control System

Abstract

A replaceable fluid container for an engine comprising: a reservoir for holding a fluid; a fluid coupling adapted to provide fluidic communication between the reservoir and a fluid circulation system of an engine; and a data provider arranged such that positioning the container to permit fluidic communication between the reservoir and the fluid circulation system of the engine arranges the data provider for data communication with an engine control device of the engine. There is also provided a method of facilitating control of an engine and an engine control system, apparatus and a vehicle.

Claims

1. A replaceable fluid container for an engine comprising: a reservoir for holding a fluid; a fluid coupling adapted to provide fluidic communication between the reservoir and a fluid circulation system of an engine; and a data provider arranged such that positioning the container to permit fluidic communication between the reservoir and the fluid circulation system of the engine arranges the data provider for data communication with an engine control device of the engine.

2. The container of claim 1 wherein the data communication comprises one of: providing data to the engine control device; and receiving data from the engine control device.

3. The container of claim 1 wherein the data provider is arranged to inhibit communication with the engine control device unless the reservoir is in fluidic communication with the fluid circulation system of the engine.

4. The container of claim 1 wherein the data provider is configured such that communication of data with the engine control device is dependent upon the presence of fluidic communication between the fluid container and a fluid circulation system of the engine.

5. The container of claim 1 wherein the fluid coupling comprises a self-sealing coupling arranged such that connecting the self-sealing coupling to the fluid circulation system arranges the data provider for communicating data with the engine control device.

6. The container of claim 1 in which the data provider is configured to communicate with the engine control device in response to the fluid coupling being coupled to the fluid circulation system of the engine.

7. The container of claim 1 comprising a sensor adapted to sense at least one property of a fluid in the reservoir of the container, wherein the data communicated with the engine control device comprises data based on the sensed property of the fluid.

8. The container of claim 7 in which the property of the fluid is at least one property selected from the group consisting of: the amount of fluid, the temperature of fluid, the pressure of fluid, the viscosity of fluid, the density of fluid, the electrical resistance of fluid, the dielectric constant of fluid, the opacity of fluid, the chemical composition of fluid and combinations of two or more thereof.

9. The container of claim 1 in which the data provider comprises a memory for storing data.

10. The container of claim 9 in which the stored data comprises at least one property of the fluid selected from the group consisting of: the amount of fluid, the temperature of fluid, the pressure of fluid, the viscosity of fluid, the viscosity index of the fluid, the density of fluid, the electrical resistance of fluid, the dielectric constant of fluid, the opacity of fluid, the chemical composition of fluid, the origin of the fluid and combinations of two or more thereof.

11. The container of claim 9 or 10 in which the stored data comprises data based upon at least one sensed property of the fluid.

12. The container of claim 9 in which the data provider is adapted to receive data from the engine control device and to perform an action selected from the list consisting of: storing the received data in the memory; and providing data to the engine control device in response to the received data.

13. A computer implemented method of facilitating control of an engine, the method comprising: receiving, at a fluid container, a signal indicating that the fluid container is coupled to the engine; in response to the received signal performing an action selected from the list comprising: providing data to an engine control device; and, providing data to a memory at the fluid container.

14. The computer implemented method of claim 13 wherein providing data to a memory at the fluid container comprises storing data obtained from the engine control device in the memory.

15. The computer implemented method of claim 13 comprising sensing at least one property of a fluid in a reservoir of the container, wherein the data is based on the sensed property.

16. The computer implemented method of claim 13 wherein providing data to an engine control device comprises obtaining the data from memory at the fluid container.

17. A computer readable medium comprising program instructions operable to program a processor-to perform the method of claim 13.

18. A replaceable fluid container for an engine comprising the computer readable medium of claim 17 and a reservoir for holding a fluid.

19. An engine control system adapted for use with a container as claimed in claim 1, wherein the engine control system is configured to perform an action selected from the list consisting of: controlling operation of the engine based on data obtained from the container; and sending data to the container for storage.

20. An apparatus comprising an engine control system according to claim 19 and an engine comprising a fluid circulation system adapted for fluidic communication with the reservoir of the container.

21-22. (canceled)

Description

[0119] Embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0120] FIG. 1 shows a schematic illustration of a vehicle; and

[0121] FIG. 2 shows a schematic illustration of components of the vehicle of FIG. 1

[0122] FIG. 3 shows in schematic elevation view, a replaceable fluid container for an engine and a partial section through a wall of the container.

[0123] In the drawings, like reference numerals are used to indicate like elements.

[0124] FIG. 1 shows a vehicle 6 comprising an engine 4, a fluid container 14 and an engine control device 2. The engine 4 comprises a fluid circulation system 8.

[0125] The fluid circulation system 8 is coupled to receive fluid from a supply line 10, and to return fluid that has circulated in the engine 4 via a fluid return line 12.

[0126] The fluid container 14 comprises a reservoir 9 for holding a fluid, and a data provider 1 for providing data about the fluid container 14. The data provider 1 is coupleable to provide data to the engine control device 2 via a first communication link 32. The fluid container 14 comprises a fluid outlet port 91 which is coupled to the reservoir 9. The outlet port 91 is coupleable to supply fluid to the engine's fluid circulation system 8 via a fluid supply line 10. The fluid inlet port 92 is coupleable to the fluid return line 12 to enable fluid to circulate from the reservoir 9, around the circulation system 8 of the engine 4, and back to the reservoir 9. The fluid container 14 is described in more detail below with reference to FIG. 2.

[0127] The ports 91, 92 of the fluid container 14 comprise self-sealing couplings, and the container comprises latches 101, 102 configured to secure the container 14 to the fluid supply line 10 and the fluid return line 12. The latches are operable to be released to enable the container 14 to be removed and replaced.

[0128] The engine control device 2 comprises a processor 96, and a memory 94 configured to store control data for the engine 4. The processor 96 is configured to monitor and to control the operation of the engine 4, via a second communication link 34. The processor 96 is configured to control operation of the engine 4 based on the monitoring, and based on the control data read from the memory 9. The engine control device 2 is further configured to obtain data from the data provider 1 via the communication link 32 and to control the engine based on the data obtained from the data provider 1.

[0129] In operation, the fluid container 14 is secured in fluid communication with the fluid circulation system 8 by the latches 101, 102. When the fluid container 14 is secured by the latches, the data provider 1 is coupled to communicate with the engine control device 2 by the first communication link 32. The engine control device 2 regulates operation of the engine 4 based on data obtained from the data provider 1 in combination with data obtained from monitoring operation of the engine 4, and data stored in the memory 94 of the engine control device 2.

[0130] FIG. 2 shows a fluid container 140, an engine control device 2, and an engine 4, the features of any of which may be used in combination with those of the example shown in FIG. 1.

[0131] The fluid container 140 comprises a reservoir 9 for holding a fluid, and a vent 23 to enable pressure to be equalised in the reservoir 9 as fluid is drawn into and out from the reservoir 9. The fluid container 140 comprises latches 101, 102 and a latch sensor 30 for sensing when the latches 101, 102 are engaged to retain the fluid container 140 in fluid communication with the fluid circulation system 8

[0132] The fluid sensor 22 comprises two metallic strips separated from one another on a dip tube of the fluid container 14. The fluid sensor 30 senses the oil level in the reservoir 9 based on the capacitance of the strips to provide a signal indicative of the oil level to the data provider 1. The fluid sensor 22 is further configured to sense an electrical resistance of the fluid thereby to provide an indication of the presence of impurities in the fluid.

[0133] The data provider 1 of the fluid container 140 comprises a processor 103 arranged to receive signals from the fluid sensor 22 and the connection sensor 30, and to communicate data to the engine control device 2 via the communication link 32. The data provider 1 further comprises a memory 104 for storing data describing the fluid. In particular, the memory 104 stores data including at least one of: the grade of fluid, the type of fluid, the date on which the fluid was filled or replaced, a unique identifier of the container 140, an indication of whether the container is new, or has previously been refilled or replaced, an indication of the vehicle mileage, the number of times the container has been refilled or reused, and the total mileage for which the container has been used.

[0134] The engine 4 shown in FIG. 2 comprises an engine communication interface 106 arranged to communicate operational parameters of the engine, such as engine speed and throttle position to the processor 96 of the engine control device 2 via the communication link 34. The engine communication interface 106 is further operable to receive engine commands from the engine control device 2 and to modify operation of the engine 4 based on the received commands.

[0135] The memory 94 of the engine control device 2 comprises non-volatile memory configured to store: [0136] identifiers of acceptable fluids for use in the engine 4; [0137] data defining a first container fluid level threshold and a second fluid level threshold; [0138] data indicative of an expected container oil level based on the mileage of the vehicle; [0139] data defining a service interval, wherein the service interval is the time period between performing maintenance operations for the vehicle such as replacing the fluid; [0140] the vehicle mileage; [0141] sets of engine configuration data for configuring the engine to operate in a selected way; [0142] an association (such as a look up table) associating fluid identifiers with the sets of engine configuration data; and, [0143] data indicative of an expected oil quality based on the mileage of the vehicle.

[0144] The processor 96 is operable to compare data stored in the memory 94 with data obtained from the data provider 1 of the container 140 and from the communication interface 106 of the engine 4.

[0145] In operation, the processor 104 of the data provider 1 of the container provides an identifier of the fluid to the processor 96 of the engine control device 2. The processor 96 determines whether the correct fluid is in use based on the fluid identifier from the data provider 1, and the identifiers stored in the memory 94. In the event that the processor 96 determines that the container does not comprise an acceptable fluid, the processor 96 is configured to alert the user of the vehicle and/or to prevent operation of the engine 4. In the event that the processor 96 determines that the container does comprise an acceptable fluid, the engine control device 2 enables operation of the engine 2. This provides an electronic lock to inhibit unsafe or sub-optimal operation of the engine, and may detect and inhibit the use of counterfeit fluid products, or unauthorised refilling of the container 140.

[0146] If operation of the engine is enabled, the processor 96 obtains a set of configuration data for the engine 2 from the memory 94 based on the stored associations, and the fluid identifier provided by the data provider 1. This enables the operation of the engine to be configured or reconfigured according to the characteristics of the fluid. When the engine is running, the processor 96 is configured to communicate with the data provider 1, and in the event that the data provider indicates that the characteristics of the fluid have changed, the configuration of the engine may be adjusted in response to these changes. This enables the engine to adapt to real-time changes in the characteristics of the fluid.

[0147] The processor 103 of the container 140 is configured to obtain data indicating the expected fluid level based on the mileage since the fluid was last refilled, and to compare the fluid level sensed by the sensor 22 with stored data. In the event that this comparison indicates that the fluid level is changing more quickly than expected, the data provider 1 can be configured to send a signal to the engine control device 2 to modify a service interval for the vehicle based on this comparison.

[0148] The fluid may be any type of fluid circulated in the engine 4 to support a function of the engine, which may be an ancillary function of the engine. For example the fluid may be lubricant, or coolant, or de-icer, or any other fluid associated with the engine. As many different types and grades of such fluid are available, the data provider may comprise an identifier of the fluid.

[0149] The data provider 1 may comprise a memory storing an identifier of the fluid, and a communication interface to enable data stored in the memory of the data provider 1 to be passed via the communication link 32 to the processor 96 of the engine control device. The data provider 1 may comprise a computer readable identifier for identifying the fluid, the identifier may be an electronic identifier, such as a near field RF communicator, for example a passive or active RFID tag, or an NFC communicator.

[0150] The data provider 1 may be configured for one way communication. For example the data provider 1 may be configured only to receive data from the engine control device, so that the data can be provided to memory at the container. Alternatively the data provider 1 may be configured only to provide data to the engine control device. In some possibilities the data provider 1 is adapted to provide data to and receive data from the engine control device. The receiving and providing of data may be to, from or between (i) a memory/memories and/or processor(s) of the engine control device and (ii) the data provider and/or sensor(s) of the data provider and/or a memory/memories of the data provider.

[0151] The memory can store data comprising at least one property of the fluid selected from the group consisting of: the amount of fluid, the temperature of fluid, the pressure of fluid, the viscosity of fluid, the viscosity index of the fluid, the density of fluid, the electrical resistance of fluid, the dielectric constant of fluid, the opacity of fluid, the chemical composition of fluid, the origin of the fluid and combinations of two or more thereof. The memory may also be configured to receive data from an engine control device. This enables data to be stored at the container. Such stored data can then be provided from the memory to diagnostic devices during servicing and/or during replacement of the container. The amount of fluid includes the absence of the fluid.

[0152] The memory is optional. The computer readable identifier may be an optical identifier, such as a barcode, for example a two-dimensional barcode, or a colour coded marker, or optical identifier on the container. The computer readable identifier may be provided by a shape or configuration of the container 14. Regardless of how it is provided, the identifier may be encrypted.

[0153] The communication link 32 may be any wired or wireless communication link, and may comprise an optical link.

[0154] The latches 101, 102, are optional and the container 14, 140 may simply be fluid coupled to the circulation system. The container 14, 140 can be secured by gravity, an interference fit, a bayonet coupling, or any appropriate fixture. The data provider 1 may be positioned on the container 140 so that, when the container is coupled in fluidic communication with the fluid circulation system of the engine, the data provider 1 is also arranged to communicate data with the engine control device, and if the container is not positioned for fluidic communication with the fluid circulation system, communication with the data provider is inhibited.

[0155] The container 140 has been described as comprising particular types of sensors. However, one or both of these sensors may be omitted, e.g. as in FIG. 1 above. Where sensors are used any type of sensor, or combination of sensors can be used. For example, to sense the level of fluid in the container: a mechanical float, a position sensor, an electrical coil, capacitive sensors, resistivity sensors, ultrasonic level detection, visible or infra-red light detection, pressure sensing, or other sensors. The sensing system may provide information about the level in a continuous range between two fixed points or as discrete levels (e.g. full, half full, empty). Additionally, if the level of the liquid increased rapidly it could indicate some form of failure in the engine and provide an early warning mechanism to help prevent further damage to the engine. The containers 14, 140 may comprise sensors configured to sense at least one of a temperature, pressure, viscosity, density, electrical resistance, dielectric constant, opacity, chemical composition or amount of the container oil. It will further be appreciated that a plurality of fluid sensors could be provided, each to sense a different property of the fluid.

[0156] Information about the oil quality may be obtained through simple capacitance or resistivity measurements. These might, for example, indicate the presence of water in the oil or of metallic or carbonaceous particulates suspended in the oil.

[0157] The fluid container 14, 140 may be a container for an engine lubricating oil composition, a heat exchange fluid for cooling at least some working components of the engine 4, and/or heating some working components of the engine 4.

[0158] In the context of the present disclosure, those skilled in the art will appreciate that the fluid ports of the fluid container 14, 140 could comprise any suitable coupling for retaining the fluid container 14, 140 in fluid communication with the fluid circulation system 8. The port couplings could be arranged to be remotely decoupled from the fluid lines 10, 12 to place the fluid container 14 in its uncoupled configuration. It will further be appreciated that the fluid container 14 could comprise an actuator to decouple the fluid container 14, 140 from the circulation system 8.

[0159] Although circulated engine oil is described as being returned to the fluid container 14, 140 for recirculation, in the context of the present disclosure, those skilled in the art will appreciate that circulated engine oil could be collected and stored in a container coupled to the engine 4 and, when convenient, emptied from or otherwise removed from the vehicle 6.

[0160] Although the metallic strips of the sensor 22 are described as being on an oil dip tube, they may be located on an inner wall of the fluid container 14, 140.

[0161] A position sensor could be configured to provide signals indicative of a continuous range of oil levels between two predetermined values, for example a first value indicating the fluid container is full and a second value indicating the container is empty, or only for predetermined oil levels, such as “full”, “half full” or “empty”. The position sensor 30 could be configured to communicate continuously with the container module 16 or at selected time intervals or in response to a signal from the processor 96 of the engine control device.

[0162] FIG. 3 shows an elevation view of a fluid container 300 and a partial section through a wall of the container 300. The container 300 comprises a body 304, and a base 306. The body 304 is secured to the base by a lip 302. A data provider 308 is carried in the lip 302.

[0163] The lip 302 includes a data coupling 310 to enable the data provider 308 to be coupled to an interface 312 for communicating data with an engine control device (not shown in FIG. 3). The interface 312 comprises connectors 314 for connecting the interface 312 with the data provider 308 of the container 300.

[0164] The base 306 of the container 300 comprises a fluid coupling (not shown in FIG. 3) for coupling fluid from a reservoir of the fluid container with a fluid circulation system of an engine. The fluid coupling and the data coupling 310 are arranged so that connecting the fluid coupling in fluidic communication with the fluid circulation system of an engine also couples the data provider 308 for data communication with the engine control device via the interface 312 by seating the connectors 314 of the interface in the data coupling 310 on the container 310.

[0165] The interface 312 and the connectors 314 provide electrical connections for eight (8) channels which provide measurements for fluid temperature, fluid pressure, fluid quality, fluid type, and the level (e.g. amount) of fluid in the container. The connectors 314 may be arranged to provide electrical power to the data provider 308.

[0166] Although the example shown in FIG. 3 comprises conductive electrical connections 314 for communicating with the data provider 308 a contactless connection may also be used. For example, inductive or capacitive coupling can be used to provide contactless communication. One example of inductive coupling is provided by RFID, however other near field communications technology may also be used. Such couplings may enable electrical power to be transferred to the data provider 308, and also have the advantage that the data connection does not require any complex mechanical arrangement and the presence of dirt or grease on the couplings 310, 314 is less likely to inhibit communication with the data provider 308.

[0167] The container 300 may comprise a power provider such as a battery for providing electrical power to the data provider 308 this may enable the container 300 to be provided with a range of sensors, including sensors for fluid temperature, pressure and electrical conductivity. Where the container 300 comprises a filter sensors may be arranged to sense these parameters of the fluid as the fluid flows into the filter, and after the fluid has flowed through the filter.

[0168] The data provider 308 may be configured to provide information relating to the fluid in the container, for example, where the fluid is oil, the oil grade and/or type. The data provider may also provide data indicating the date on which the container was refilled, a unique serial number of the container, the length of time (e.g. number of hours) for which the container has been used, and whether the container holds new or refilled fluid.

[0169] The function of the processors 103, 96 may be provided by any appropriate controller, for example by analogue and/or digital logic, field programmable gate arrays, FPGA, application specific integrated circuits, ASIC, a digital signal processor, DSP, or by software loaded into a programmable general purpose processor. Aspects of the disclosure provide computer program products, and tangible non-transitory media storing instructions to program a processor to perform any one or more of the methods described herein.

[0170] Other variations and modifications of the apparatus will be apparent to persons of skill in the art in the context of the present disclosure.