Classifications

• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60C—VEHICLE TYRES; TYRE INFLATION; TYRE CHANGING; CONNECTING VALVES TO INFLATABLE ELASTIC BODIES IN GENERAL; DEVICES OR ARRANGEMENTS RELATED TO TYRES
  • B60C23/00—Devices for measuring, signalling, controlling, or distributing tyre pressure or temperature, specially adapted for mounting on vehicles; Arrangement of tyre inflating devices on vehicles, e.g. of pumps or of tanks; Tyre cooling arrangements
  • B60C23/02—Signalling devices actuated by tyre pressure
  • B60C23/04—Signalling devices actuated by tyre pressure mounted on the wheel or tyre
  • B60C23/0408—Signalling devices actuated by tyre pressure mounted on the wheel or tyre transmitting the signals by non-mechanical means from the wheel or tyre to a vehicle body mounted receiver
  • B60C23/0479—Communicating with external units being not part of the vehicle, e.g. tools for diagnostic, mobile phones, electronic keys or service stations
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60C—VEHICLE TYRES; TYRE INFLATION; TYRE CHANGING; CONNECTING VALVES TO INFLATABLE ELASTIC BODIES IN GENERAL; DEVICES OR ARRANGEMENTS RELATED TO TYRES
  • B60C23/00—Devices for measuring, signalling, controlling, or distributing tyre pressure or temperature, specially adapted for mounting on vehicles; Arrangement of tyre inflating devices on vehicles, e.g. of pumps or of tanks; Tyre cooling arrangements
  • B60C23/02—Signalling devices actuated by tyre pressure
  • B60C23/04—Signalling devices actuated by tyre pressure mounted on the wheel or tyre
  • B60C23/0408—Signalling devices actuated by tyre pressure mounted on the wheel or tyre transmitting the signals by non-mechanical means from the wheel or tyre to a vehicle body mounted receiver
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60C—VEHICLE TYRES; TYRE INFLATION; TYRE CHANGING; CONNECTING VALVES TO INFLATABLE ELASTIC BODIES IN GENERAL; DEVICES OR ARRANGEMENTS RELATED TO TYRES
  • B60C23/00—Devices for measuring, signalling, controlling, or distributing tyre pressure or temperature, specially adapted for mounting on vehicles; Arrangement of tyre inflating devices on vehicles, e.g. of pumps or of tanks; Tyre cooling arrangements
  • B60C23/02—Signalling devices actuated by tyre pressure
  • B60C23/04—Signalling devices actuated by tyre pressure mounted on the wheel or tyre
  • B60C23/0408—Signalling devices actuated by tyre pressure mounted on the wheel or tyre transmitting the signals by non-mechanical means from the wheel or tyre to a vehicle body mounted receiver
  • B60C23/0422—Signalling devices actuated by tyre pressure mounted on the wheel or tyre transmitting the signals by non-mechanical means from the wheel or tyre to a vehicle body mounted receiver characterised by the type of signal transmission means
  • B60C23/0433—Radio signals
  • B60C23/0447—Wheel or tyre mounted circuits
  • B60C23/0455—Transmission control of wireless signals
  • B60C23/0461—Transmission control of wireless signals externally triggered, e.g. by wireless request signal, magnet or manual switch
• • B—PERFORMING OPERATIONS; TRANSPORTING
  • B60—VEHICLES IN GENERAL
  • B60C—VEHICLE TYRES; TYRE INFLATION; TYRE CHANGING; CONNECTING VALVES TO INFLATABLE ELASTIC BODIES IN GENERAL; DEVICES OR ARRANGEMENTS RELATED TO TYRES
  • B60C23/00—Devices for measuring, signalling, controlling, or distributing tyre pressure or temperature, specially adapted for mounting on vehicles; Arrangement of tyre inflating devices on vehicles, e.g. of pumps or of tanks; Tyre cooling arrangements
  • B60C23/02—Signalling devices actuated by tyre pressure
  • B60C23/04—Signalling devices actuated by tyre pressure mounted on the wheel or tyre
  • B60C23/0408—Signalling devices actuated by tyre pressure mounted on the wheel or tyre transmitting the signals by non-mechanical means from the wheel or tyre to a vehicle body mounted receiver
  • B60C23/0471—System initialisation, e.g. upload or calibration of operating parameters

Definitions

• the present invention relates to vehicle monitoring systems, especially wheel monitoring systems such as Tire Pressure Monitoring Systems (TPMS).
• TPMS Tire Pressure Monitoring Systems
• the invention relates particularly to tools for communicating with wheel mounted units of such systems.
• a wheel mounted unit comprising one or more appropriate sensor(s) is located at each wheel, typically inside the tire, which measures the relevant characteristic(s) and transmits corresponding information to a remote central monitoring station.
• wheel mounted units which for example presently includes the EZ sensor (trade mark) provided by Schrader Electronics Limited of Antrim, Northern Ireland.
• EZ sensor trade mark
• Such wheel mounted units, including the EZ sensor, are configurable to allow the user to program them to emulate the OEM unit that was removed from the wheel.
• the communications unit being configured for communication with a vehicle monitoring device
• said control unit is incorporated into a portable computing device comprising at least one communications device for allowing the control unit to communicate with said at least one server across said network
• said communications unit comprises at least one communications device for communicating with said vehicle monitoring device
• said control unit supports a user interface and is configured to communicate with said at least one server and/or to cause said communications unit to communicate with said vehicle monitoring device in response to user commands received by said user interface.
• a fifth aspect of the invention provides a tool control client, typically comprising computer program code, for said control unit. Preferred features are recited in the dependent claims.
• components of a smart phone, or other mobile computing device are used to provide a relatively low cost alternative to a dedicated LF tool, e.g. a TPM service tool.
• a dedicated LF tool e.g. a TPM service tool.
• the hardware typically provided in such mobile devices is of a higher specification than any conventional LF tool and this is beneficial for preferred embodiments as well as significantly lowering costs.
• These benefits may include high resolution graphics, a touch screen interface, 3G WiFi connectivity, increased memory and storage and GPS.
• Computer software can also be obtained and updated by the tools embodying the invention utilising, for example, an on-line software marketplaces such as those currently provided for existing smart phone operating systems.
• Preferred tools embodying the invention can advantageously use internet connectivity to access and store commands, e.g. LF commands, for wheel units such as TPM devices, and preferably also obtain software loads for programmable aftermarket TPM devices or other wheel units.
• the tool and in particular the control unit, may be configured to allow a user to obtain (typically download and install) diagnostic computer software from a remote server.
• the diagnostic software can be used in combination with the communications tool in order to obtain diagnostic information from the wheel unit.
• the diagnostic information can be stored on the tool and/or uploaded to a remote server for analysis.
• the diagnostic (software) application can be configured to provide a plurality of levels of diagnostic service.
• a basic diagnostic function may quickly check the high level functions of the wheel unit.
• a more detailed diagnostic function may check some of the more advanced features of the wheel unit.
• Figure 1 is a block diagram of a support system embodying one aspect of the invention, said system including a wheel monitoring system tool embodying another aspect of the invention;
• Figure 2 is a schematic diagram of the wheel monitoring system tool shown in Figure 1 , the tool being shown in communication with a wheel mounted unit;
• Figure 3 is a block diagram of an embodiment of a control unit being part of said wheel monitoring system tool
• FIG. 5 is a block diagram of an alternative embodiment of the wheel monitoring tool comprising a combined control and communications unit
• Figure 6 is a flowchart showing an example of how a tool control client supported by said control unit may initialise
• Figure 7 is a flowchart showing an example of how the tool control client may request data from a server
• Figure 8 is a flowchart showing an example of how the tool control client may use data stored at said control unit
• Figure 9 is a flowchart showing an example of how the tool control client may perform a diagnostic function
• Figure 10 is a flowchart showing an example of how the tool control client may report a problem
• Figure 1 1 is a flowchart showing an example of how the tool control client may handle bundled computer program applications; and Figures 12 and 13 show a flowchart illustrating how the tool control client may perform a diagnostic function.
• the tool 20 comprises a TPMS service tool.
• the tool 20 is capable of communication with the or each wheel mountable unit 22 of a wheel monitoring system (not shown), especially when the wheel unit 22 is installed on a wheel (typically inside the tire).
• the wheel unit 22 typically comprises a tire monitoring device having one or more sensors for monitoring one or more tire characteristics, typically including tire pressure and temperature, and being equipped to transmit corresponding tire data for reception and processing by a control unit (not shown but usually comprising the vehicle's ECU) that forms part of the wheel monitoring system.
• TPMS Tire Pressure Monitoring System
• the wheel mounted unit 22 may be referred to as a tire pressure monitoring device.
• TPMS Tire Pressure Monitoring System
• the system 10 further includes at least one server 24, for example including one or more telephony server 24A and one or more data server 24B or web server 24C.
• the telephony server(s) 24A are typically connected to one or more telephone end points 26 which may be manned by a human operator or serviced by an automated (computer) telephone operator. Human operators may provide customer support services.
• the tool 20 comprises a control unit 30 and a communications unit 32.
• the control unit 30 is configured for communication with the servers 24 across the network 28.
• the communications unit 32 is configured for communication with the wheel unit 22.
• the control unit 30 comprises a computing device comprising a programmable processor, typically a microprocessor, computer memory and one or more communications devices for allowing the tool 20, and in particular the control unit 30, to communicate with other devices including the servers 24.
• the control unit 30 comprises a portable, preferably hand held computing device.
• the computing device comprises a mobile computing platform supporting a mobile computing operating system (OS).
• OS mobile computing operating system
• the computing device preferably includes means for communicating with other devices via a mobile (cellular) telephone network, and may for example comprise a mobile (cellular) telephone or a tablet computer.
• the computing device comprises a smart phone.
• smart phones are internet enabled, i.e. capable of communicating with other devices, e.g. servers 24, across the internet, for example using GSM (Global System for Mobile Communications) technology. This can be achieved using a mobile (cellular) telephone network.
• GSM Global System for Mobile Communications
• Smart phones are typically also equipped with other telecommunications devices, e.g. a WiFi transceiver, to allow communication across the internet via other means, e.g. a public standard telephone network or data network.
• the computing device may be a dedicated device designed for use in or as the wheel monitoring tool 20, e.g. a dedicated TPMS service tool.
• the computing device may be provided with other input devices (not shown), for example a camera, a GPS device and/or a microphone, any one or more of which can be used to obtain data that can be of use to the tool 20 and which may be sent to the server(s)24 or the unit 22, as required.
• the control unit 30 and the communications unit 32 comprise separable units, as illustrated in Figure 2, in which the control unit 30 is illustrated in the preferred form of a smart phone.
• the units 30, 32 are capable of communicating with one another, typically by means of one or more data channels 34.
• the communication between the units 30, 32 may be wireless and/or wired, the units 30, 32 being equipped with a wireless communication device and/or one or more ports for a wired connection, e.g. a cable, as appropriate.
• the units 30, 32 are adapted to removably interconnect with each other.
• each unit 30, 32 may be provided in a respective housing 36, 38 ( Figure 1 ), the housings including respective mutually interengagable connectors for establishing a releasable mechanical connection between the housings 36, 38.
• the housing 38 for the communications unit 32 is configured to serve as a docking station for the control unit 30.
• the housing 38 may be shaped and dimensioned to define a bed 40 for receiving the housing 36.
• the bed 40 is preferably shaped to receive the reverse face (not visible) of the housing 36, the housing 38 being shaped and dimensioned to be hand held.
• the obverse face 44 of the housing 36 (which face 44 typically includes the user interface 46, e.g. a touch screen interface and/or one or more buttons) is exposed.
• One or more retaining devices 48 e.g. clamps or clips, may be provided for releasably securing the control unit 30 to the communications unit 32.
• the housing may be adapted to receive any one of a plurality of inserts, each insert being shaped and dimensioned to receive a respective control unit housing 36.
• the units 30, 32 may communicate during use by a wired, but
• the connection may comprise a data cable connectable between respective data ports (e.g. USB ports) provided in each housing 36, 38, or any other convenient non-wireless connection means.
• the data channel(s) 34 may be supported by wireless communication means, e.g. respective Bluetooth devices provided in each unit 30, 32.
• the communications unit 32 comprises wireless communications means for
• the communication means comprises a low frequency (LF) transmitter 50 for communicating with a corresponding LF receiver or transceiver (usually a transponder device) provided in the wheel unit 22.
• the unit 32 may include any other suitable wireless transmitter(s), receiver(s) or transceiver(s) as required, for example an RF receiver 51 as shown in Figure 2.
• the transmitter 50 may comprise a signal generating circuit 52 coupled to an antenna 54.
• the receiver 51 may comprise an antenna 53 coupled to a signal receiving circuit 55.
• the unit 32 sends signals to the unit 22 using the LF transmitter 50 and receives signals from the unit via the RF receiver 51.
• the communications unit 32 advantageously also comprises a processor 56, conveniently a microprocessor, configured to control the operation of the transmitter 50 and receiver 51 and also to communicate with the control unit 30 via the data channel(s) 34.
• a processor 56 conveniently a microprocessor, configured to control the operation of the transmitter 50 and receiver 51 and also to communicate with the control unit 30 via the data channel(s) 34.
• FIG 3 there is shown a block diagram of one embodiment of the control unit 30, indicated in Figure 3 as 130, where it is assumed that the control unit is separate from the communications unit 32.
• the control unit 130 is assumed to comprise a smart phone and as such includes devices such as a camera 152, sensors 154 and audio devices 156 that are not necessary for the implementation of the invention and may be omitted in alternative embodiments.
• the control unit 130 includes one or more processors 158, typically suitable programmed microprocessors, and computer memory 160 (including in this example RAM and flash memory for application storage) for use by the processor(s) 158.
• the processor(s) 158 are configured to control a display driver 162 which drives a display 164, which may be coupled with a touch screen 165 for use in the provision of a user interface.
• the user interface may also, or alternatively, comprise one or more keys 167.
• the control unit 130 further includes communications devices 161 for communicating with other devices such as the server(s) 24 and the communications unit 32.
• the communications devices may include any one or more of: a USB device 166 or other port device for supporting communication via a wired link; an audio socket 163; a mobile (cellular) data connection device 168, e.g. a GSM device; a Bluetooth device 170; a WiFi device 172; and a Near Field Communication (NFC) device 174.
• a power supply 176 typically a battery, is also provided.
• the communications unit 132 includes one or more processors 156, typically suitable programmed microprocessors, and computer memory 182 (including in this example RAM and flash memory) for use by the processor(s) 156.
• the communications unit 132 further includes at least one
• the communications device 184 comprises a Bluetooth device.
• the communications devices 186 may typically include any one or more of: an LF transmitter or transceiver 150 (typically comprising an LF driver 152 and an LF transponder 154); an RF receiver or transceiver 188 (typically comprising an RF driver 189 and an RF transponder 190); and a Near Field Communication (NFC) device 191.
• One or more antennas may be provided in association with the respective communications device(s) as required.
• a power supply 192 typically a battery, is also provided.
• Figure 5 shows an alternative embodiment of the tool 20 in which the control unit and the communications unit are integrated, for example provided on the same computing device, e.g. smart phone or dedicated TPM service tool running a mobile operating system.
• the control unit is indicated generally as 230 and the communications unit is indicated generally as 232.
• the embodiment of Figure 5 is a combination of the control unit 130 of Figure 3 and the communications devices 186 of Figure 4 (which are conveniently controlled by the processor(s) 256).
• the control unit 30 supports a tool control client 92 comprising one or more computer programs.
• the client 92 is configured to control the operation of the tool 20.
• the client 92 is configured to control, facilitate and/or support, as required, any one or more of: communication between the control unit 30 and the server(s) 24; communication between the control unit 30 and the communications unit 32; the provision and operation of the tool's user interface (which typically includes rendering information to the user (e.g. via the display 164) and handling user inputs (e.g. via keys 167 and/or touch screen 165).
• the client 92 can be downloaded from a server (assumed to be web server 24C in this example) across network 28. It may conveniently be stored in local memory 160 and executed by processor(s) 158. The functionality supported by the client 92 may vary.
• the client 92 may be configured to support any one or more of the following functions: 1. operate the communications unit 32 to communicate with the wheel unit 22. This may involve causing the communications unit 32 to transmit an activation signal and/or an interrogation signal and/or a configuration signal to the wheel unit and/or to receive signals from the wheel unit 22, for example signals generated by the wheel unit in response to the activation and/or interrogation signal and/or configuration signal; 2.
• the communications unit 32 communicates data to the communications unit 32 for example for use in the activation and/or operation and/or interrogation and/or configuration of the wheel unit.
• This data may be used to configure the activation signal and/or interrogation signal and/or configuration signal as applicable; 3. receive data from the communications unit 32 for example relating to the activation and/or operation and/or interrogation and/or configuration of the wheel unit 22. This may involve obtaining data received from the wheel unit 22; 4. communicating data to the server(s) 24, for example data relating to the activation, operation, interrogation and/or configuration of the wheel unit, optionally including the data received from the wheel unit or data derived therefrom, and optionally comprising any other data from the control unit 30 or communications unit 32 including for example location (e.g.
• GPS GPS
• image data e.g. a photograph
• video data e.g. a photograph
• audio data e.g. any user inputted data
• rendering via the user interface e.g. the display 164
• data for example relating to the activation, operation, interrogation and/or configuration of the wheel unit 22 optionally including the data received from the wheel unit or data derived therefrom, and/or relating to the configuration or operation of the communications unit 32
• 6. obtaining via the user interface (e.g. via the touch screen 165 and/or keys 167) user input data, for example relating to the activation, operation, interrogation and/or configuration of the wheel unit 22 and/or relating to the configuration or operation of the communications unit 32; 7.
• the server(s) 24 obtaining from the server(s) 24 data, for example relating to the activation and/or operation and/or, interrogation and/or configuration of the wheel unit 22, and/or relating to the configuration or operation of the communications unit 32; 8. obtaining from the server(s) 24 computer program updates for the client 92; 9. causing the control unit 30 to connect with the telephony server 24A to allow the user to communicate with a human or automated telephone operator.
• the client 92 may be configured to allow the tool 20 to perform various tasks in relation to the wheel unit 22 including activation or operation of the wheel unit, configuration (e.g.
• the client 92 may be configured to control one of the communication devices 161 of the control unit 30, e.g. smart phone, in order to cause the communications unit 32 to transmit a low frequency electromagnetic signal modulated in such a manner that it causes activation or configuration (e.g. programming) of the wheel unit, or obtains diagnostic related data from the wheel unit.
• Possible communication channels may include, but are not limited to, Bluetooth, WiFi, MicroUSB, proprietary interface, Near field communication or audio socket. Depending on the communication channel used, it may also be possible to communicate information back to the control unit
• the client 92 is configured to provide a menu type user interface to allow the user to obtain LF (or other, e.g. configuration settings) commands (e.g. from server 24B) for use by the communications unit 32 when communicating with the wheel unit 22, and/or to obtain software loads either stored on the control unit 30 or at a remote server (e.g. servers 24B or 24C).
• the control unit 30 may then stream corresponding data, typically serially to modulate the communication units 32 carrier frequency, which in turn excites the transmitting device 52, 152, creating a constant or modulated signal e.g. LF field.
• the LF field, or other appropriate signal in turn activates, configures or otherwise operates the wheel unit 22, as applicable.
• the user may operate the client 92 to download, from the server(s), e.g. server 24B, a diagnostic test script and to cause same to be
• Diagnostic related data may be obtained from the wheel unit 22 by the communications unit 32 and communicated to the control unit 30.
• the control unit 30 may then communicate the diagnostic information, or information derived therefrom to a server 24 configured to serve a diagnostic function.
• the diagnostic server 24 may be configured make a determination of the nature of the fault and send the information back to the control unit 30. A suitable message can then be rendered to the user by the client 92.
• the client 92 is typically configured to establish data channel 24. This may be achieved in any convenient conventional manner. For example, in a typical smart phone, assuming that a Bluetooth channel 24 is to be established, the client 92 may be configured to use the relevant API(s) (Application Programming Interfaces) provided by the operating system to set up and manage the wireless connection. Typically the client 92 calls the API and uses it to perform the following: check for valid connected devices; prompt the user to scan for devices; establish the RF communication channel between the Smart phone and communications unit 32; and transfer data wirelessly between the smart phone and unit 32.
• API Application Programming Interfaces
• the user uses the user interface supported by the client 92 (typically a GUI (graphical user interface)) to determine the data to be sent to the communications device 32, and/or received from or sent to a server 24.
• Typical processes are out lined in the flow diagrams of Figures 6 to 1 1.
• Figure 6 is a flowchart showing an example of how the tool control client 92 may initialise.
• Figure 7 is a flowchart showing an example of how the tool control client 92 may request data from a server 24.
• the user may be prompted to select a desired data type, e.g. tool command data or software load (701 , 702).
• the user may then be prompted to provide details of the vehicle (703 to 708).
• the client 92 may check if the requested data is available (709). If it is not available, the user may be informed and the client returns to the main menu (710, 71 1 ).
• the user may be asked if he wants to store the data on the tool 20 or to use the data now (712). If the data is stored, the user may be asked if he wants to use it now (713).
• the client causes the data to be obtained from the server 24, sent to the communications device 32 and transmitted to the wheel unit 22 (714).
• the client may then check if a response has been received from the wheel unit 22 (715). If so, it may be rendered to the user (directly or after processing by the client) (716) and/or communicated to an appropriate server.
• the user may be asked if he wants to send the data to the wheel unit again and, if so, causes the data to be sent again and the response processed, rendered etc as required.
• Figure 8 is a flowchart showing an example of how the tool control client 92 may use data stored at the control unit 30, 130.
• the user may be prompted to select a desired data type, e.g. tool command data or software load (801 , 802).
• the user may then be prompted to provide details of the vehicle (803 to 808).
• the client 92 may check if the requested data is available (809). If it is not available, the user may be informed and the client returns to the main menu (810, 81 1 ), or asked if he wants to select new data. If the data is available, the client causes the data to be obtained (e.g. from local memory), sent to the communications device 32 and transmitted to the wheel unit 22 (814).
• the client may then check if a response has been received from the wheel unit 22 (815). If so, it may be rendered to the user (directly or after processing by the client) (816) and/or communicated to an appropriate server. The user may be asked if he wants to send the data to the wheel unit again and, if so, causes the data to be sent again and the response processed, rendered etc as required.
• Figure 9 is a flowchart showing an example of how the tool control client 92 may initiate a diagnostic function.
• the user is prompted to initiate a diagnostic function and in response to user initiation the client 92 causes a diagnostic interrogation command to be transmitted to the wheel unit 22 by the communications device 32 (901 to 903).
• the client checks for a response from the wheel unit 22 (904). If a response is received, it may be communicated to an appropriate server 24, a response may be received from the server 24 and rendered to the user (905 to 907). Alternatively, the wheel unit response may be processed by the client 92 and a response rendered to the user. The user may be asked if he wants to initiate a diagnostic function again (908).
• Figure 10 is a flowchart showing an example of how the tool control client 92 may report a problem to for example a customer support agent via the telephony server 24A.
• the user is prompted to identify the problem using the user interface (1001 to 1008).
• the problem details are communicated to the telephony server 24A (1009), whereupon it may be rendered to an operator 26.
• the operator may reply, especially where the tool 20 comprises a telephone, by telephoning the user, or sending a telephonic, e.g. SMS, message to the user.
• the server 24A is a web server
• the operator may reply by email or other electronic message.
• Figure 1 1 is a flowchart showing an example of how the tool control client 92 may handle bundled computer program applications.
• the user may be asked to select a bundled application, e.g. a pressure converter, a tyre/wheel guide, a VIN look up and/or a rim offset calculator (1 101 , 1 102).
• a bundled application e.g. a pressure converter, a tyre/wheel guide, a VIN look up and/or a rim offset calculator (1 101 , 1 102).
• the user selects a bundled application and the client causes it to be instantiated on the tool 20 (1 103, 1 104).
• the user may close the application (1 105, 1 106).
• the client 92 may obtain corresponding data from a remote server 24, e.g. server 24B, and/or from local memory at the unit 30, and cause it to be sent over the data channel 24 to the communications unit 32.
• the unit 32 modulates the data to be transferred over an LF (or other appropriate) channel to the wheel unit.
• the control unit 30 may also transfer data specific to the RF frame that the wheel unit will transmit in reply. This data may include data encoding, data rate, modulation type, modulation frequency, preamble format and C.R.C. type of the RF frame. This information may be used to configure the receiver part communications unit 32.
• LF transmitter e.g. server 24B
• the RF receiver 188 is used to receive signals from the wheel unit.
• Figures 12 and 13 show a flow chart illustrating how a typical diagnostic session may be implemented by the client 92.
• the relevant diagnostic application is not available to the tool 20, it may be downloaded from a server 24 (1201 , 1203). When available, the application is instantiated and diagnostic options may be selected (1204, 1205).
• the wheel unit supports configurable software
• the pre-programmed software is recorded (1206) and a diagnostic test script is loaded onto the wheel unit via the communications unit 32 (1207).
• the wheel unit 22 runs the test script and its response data is received by the tool 20 (1208, 1209). If advanced diagnostics is required, the response data is sent to an appropriate server 24 which processes the data and sends reply data to the tool 20 (1210 to 1213).
• the user could conduct a check to ensure that the correct software for the vehicle has been loaded onto the wheel unit. This could be done by either scanning the vehicle's VIN number or manually entering the make, model and year of the vehicle. The software version of the wheel unit can then be determined and a comparison made to ensure that the software that was originally downloaded onto the wheel unit is the correct version for the vehicle that it has been fitted to.
• Various levels of diagnostic function could be implemented. For example, a basic diagnostic session may involve a check of battery status, temperature information, motion switch check etc. An advanced diagnostic session may include more advanced features such as analog to digital converter (ADC) check, RF crystal start up time, frequencies of internal oscillators, PLL current and so on.
• ADC analog to digital converter
• Embodiments of the invention can be further enhanced by using the smart phone hardware and operating system in conjunction with a web server 24 to create an infrastructure that allows bi-directional "always-on" communication with a central data source. This ensures that the latest software and data is always available and allows for central live management of services such as stock levels or diagnostics. This means that the user does not need to connect to a traditional computer system in order to update the software or data files on the tool 20. It also means that there is no storage limit on the tool 20, since all data is accessible via a central server 24. The always on connection allows live data to be streamed back to the central server 24 for logging and diagnostic purposes. This may be used to monitor dealer stocks and predict short term sales forecasts.
• control unit 30 may comprise a mobile device OS market place (e.g. Apple Appstore, Android Market, Windows Mobile Marketplace, Blackberry App World) on to the control unit 30, which is assumed to support the appropriate mobile device OS.
• the control unit 30 may comprise a mobile device OS market place (e.g. Apple Appstore, Android Market, Windows Mobile Marketplace, Blackberry App World) on to the control unit 30, which is assumed to support the appropriate mobile device OS.
• the control unit 30 may comprise a mobile device OS market place (e.g. Apple Appstore, Android Market, Windows Mobile Marketplace, Blackberry App World) on to the control unit 30, which is assumed to support the appropriate mobile device OS.
• the control unit 30 may comprise a mobile device OS market place (e.g. Apple Appstore, Android Market, Windows Mobile Marketplace, Blackberry App World) on to the control unit 30, which is assumed to support the appropriate mobile device OS.
• the control unit 30 may comprise a mobile device OS market place (e.g. Apple Appstore, Android Market, Windows Mobile Marketplace, Blackberry App World) on to the control unit 30, which is assumed
• Smartphone a tablet computing device or dedicated computing device. Updates to the software may be pushed out to the unit 30 through the market place, ensuring users have access to the latest software and features.
• the user can request relevant software loads and commands from the central data server 24 for the vehicle of their choice. This data can be stored on the unit 30/tool 20 for use if a network connection is not available, or it may be discarded depending on the user's preference.
• a message can be sent back to the central server 24 for marketing and production planning purposes. If the unit 30 is not successfully programmed, a central customer support service can interrogate the detail of the failure to help reduce unnecessary warranty returns.
• Preferred embodiments of the invention provide a low cost solution for users who do not want to outlay the initial investment to buy the currently available tools that will enable them to program aftermarket sensors.
• Advantages of preferred embodiments of the invention include: lower cost hardware (assuming that the user already owns a smart phone or other mobile device with a supported OS.); automatic updates to the client software; the user interface can change depending on a menu rather than being confined to a few fixed buttons; users can report problems or give feedback directly within the client application; the user interface is capable of providing high resolution graphics (such as OEM logos).
• the software application marketplace may provide feedback and ratings information.
• the tool and in particular the control unit, may be configured to allow a user to obtain (typically download and install) diagnostic computer software from a remote server (e.g. as client 92).
• the diagnostic software can be used in combination with the communications unit 32 in order to obtain diagnostic information from the wheel unit 22.
• the diagnostic information can be stored on the tool and/or uploaded to a remote server for analysis.
• the device 99 may comprise a removable hardware or firmware device that is connectable to the vehicle's electronic system or communication network or wheel unit / tyre monitor 22.
• the remote device 99 may be connectable to, or comprise part of, a vehicle's diagnostic system.
• the device 99 may comprise a removable OBD (on board diagnostics) dongle, or other removable device, connectable to the vehicle's electronic system.
• OBD on board diagnostics
• the tool 20 may communicate with the device 99 to perform any one or more of the functions described above in relation to the wheel unit 22, including any one or more of the diagnostic related functions.
• diagnostic related data may be communicated to the device 99 from vehicle's electronic system or communication network or wheel unit / tyre monitor 22, as applicable, and then communicated to the tool 20.
• the relevant data may be available from the device 99 itself.
• the data may be processed by the tool 20 and/or communicated to a server 24 for processing.
• Data may also be communicated to the device 99, e.g. for the purposes of activation or configuration.
• any other type of data e.g. test data, status data, activation data and/or configuration data, may be communicated between the tool 20 and the device 99.
• the client 92 and/or an application running on a server or client included in the system may be configured to process, and render to the user, data obtained by the tool 20 in any manner that suits the application.
• the client 92 or other application may be used to manage data, e.g. tyre pressure measurements or other tyre data, in respect of a fleet of vehicles.

Landscapes

• Engineering & Computer Science (AREA)
• Mechanical Engineering (AREA)
• Computer Networks & Wireless Communication (AREA)
• Arrangements For Transmission Of Measured Signals (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=46160047

Family Applications (1)

Country Status (2)

Cited By (2)

Families Citing this family (18)

Citations (3)

Family Cites Families (8)

• 2012
  • 2012-03-30 GB GB1205707.1A patent/GB2500697A/en not_active Withdrawn
• 2013
  • 2013-03-28 WO PCT/EP2013/056663 patent/WO2013144274A1/fr not_active Ceased

Patent Citations (3)

Also Published As

Similar Documents

Legal Events