US20160253849A1 - Unknown on-board diagnostics (obd) protocol interpreter and conversion system - Google Patents
Unknown on-board diagnostics (obd) protocol interpreter and conversion system Download PDFInfo
- Publication number
- US20160253849A1 US20160253849A1 US14/634,496 US201514634496A US2016253849A1 US 20160253849 A1 US20160253849 A1 US 20160253849A1 US 201514634496 A US201514634496 A US 201514634496A US 2016253849 A1 US2016253849 A1 US 2016253849A1
- Authority
- US
- United States
- Prior art keywords
- obd
- protocol
- unknown
- interpreter
- unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 42
- 238000004458 analytical method Methods 0.000 claims abstract description 42
- 238000012544 monitoring process Methods 0.000 claims abstract description 36
- 238000011161 development Methods 0.000 claims abstract description 31
- 238000004891 communication Methods 0.000 claims description 16
- 238000001514 detection method Methods 0.000 claims description 5
- 238000010801 machine learning Methods 0.000 claims description 5
- 230000001413 cellular effect Effects 0.000 claims description 4
- 230000001133 acceleration Effects 0.000 claims description 3
- 239000012080 ambient air Substances 0.000 claims description 3
- 238000013473 artificial intelligence Methods 0.000 claims description 3
- 238000012546 transfer Methods 0.000 claims description 2
- 238000000034 method Methods 0.000 description 11
- 238000013500 data storage Methods 0.000 description 8
- 238000011156 evaluation Methods 0.000 description 8
- 230000000875 corresponding effect Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 239000000446 fuel Substances 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 5
- 239000004065 semiconductor Substances 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 238000007405 data analysis Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000002596 correlated effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/005—Testing of electric installations on transport means
- G01R31/006—Testing of electric installations on transport means on road vehicles, e.g. automobiles or trucks
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01R—MEASURING ELECTRIC VARIABLES; MEASURING MAGNETIC VARIABLES
- G01R31/00—Arrangements for testing electric properties; Arrangements for locating electric faults; Arrangements for electrical testing characterised by what is being tested not provided for elsewhere
- G01R31/005—Testing of electric installations on transport means
- G01R31/006—Testing of electric installations on transport means on road vehicles, e.g. automobiles or trucks
- G01R31/007—Testing of electric installations on transport means on road vehicles, e.g. automobiles or trucks using microprocessors or computers
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C2205/00—Indexing scheme relating to group G07C5/00
- G07C2205/02—Indexing scheme relating to group G07C5/00 using a vehicle scan tool
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Definitions
- the present invention generally relates to remote real-time vehicle on-board diagnostics (OBD) monitoring. More specifically, various embodiments of the present invention relate to an on-board diagnostics (OBD) protocol interpreter and conversion system for decoding incompatible OBD output data from a vehicle OBD unit.
- OBD on-board diagnostics
- OBD on-board diagnostics
- ECU engine control unit
- fuel consumption instruments fuel consumption instruments
- vehicle sensors and other devices in the vehicle.
- OBD unit As a factory-standard device at the point of vehicle manufacturing, the OBD unit was originally conceived to make vehicle maintenance, diagnostics, and repairs simpler at an authorized service facility that has a corresponding OBD data reader unit.
- OBD data formats have been developed in the past several decades, and many of them were originally intended to be standardized for OBD data reader compatibility among a plurality of OBD data readers.
- SAE Society of Automotive Engineers
- ISO International Organization for Standardization
- SAE J1850 PWM SAE J1850 VPW
- ISO 9141-2 ISO 9141-2
- ISO 14230-4 ISO 14230-4
- ISO 15765-4 ISO 9141-2
- SAE J1939, SAE J1587, and SAE J1708 have been created for on-board diagnostics data readout from heavy duty trucks.
- an unknown on-board diagnostics In one embodiment of the invention, an unknown on-board diagnostics
- This unknown OBD protocol interpreter and conversion system comprises: a vehicle on-board diagnostics (OBD) unit connected to an engine control unit or a vehicular control chipset of a vehicle to record, diagnose, and generate vehicle speed data, acceleration and deceleration data, ambient air temperature data, and other vehicle diagnostics data as a raw OBD data stream; an on-board diagnostics (OBD) protocol converter unit connected to the vehicle on-board diagnostics unit, wherein the on-board diagnostics protocol converter unit is configured to decode an unknown OBD protocol to an OBD protocol library as well as a known OBD protocol to the OBD protocol library, wherein the unknown OBD protocol is correctly decoded by saving the raw OBD data stream, transmitting the raw OBD data stream and a request for analysis of the unknown OBD protocol to a remote monitoring station located remotely outside of the vehicle, receiving installable new OBD interpreter codes from a new OBD interpreter development unit in the remote monitoring station, and interpreting the unknown OBD
- FIG. 1 shows an unknown on-board diagnostics (OBD) protocol interpreter and conversion system for remote vehicle OBD monitoring, in accordance with an embodiment of the invention.
- OBD on-board diagnostics
- FIG. 2 shows a data flow diagram for dynamically interpreting an unknown on-board diagnostics (OBD) protocol from a vehicle in an OBD protocol interpreter and conversion system, in accordance with an embodiment of the invention.
- OBD on-board diagnostics
- FIG. 3 shows an internal components diagram for an on-board diagnostics protocol converter (OPC) unit, in accordance with an embodiment of the invention.
- OPC on-board diagnostics protocol converter
- FIG. 4 shows an operational flowchart for an unknown on-board diagnostics (OBD) interpreter and conversion system for remote vehicle OBD monitoring, in accordance with an embodiment of the invention.
- OBD on-board diagnostics
- OBD protocol converter OBD protocol converter
- references herein to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention.
- the appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
- separate or alternative embodiments are not necessarily mutually exclusive of other embodiments.
- the order of blocks in process flowcharts or diagrams representing one or more embodiments of the invention do not inherently indicate any particular order nor imply any limitations in the invention.
- a term “vehicle on-board diagnostics (OBD) unit” is defined as an electronic device installed in a vehicle to collect and/or analyze a variety of vehicle-related data.
- the vehicle OBD unit outputs many data parameters in real-time, such as vehicle diagnostic information (e.g. engine temperature, oil level, OBD codes, and etc.), fuel consumption-related information, vehicle speed information, vehicle acceleration and deceleration information (i.e. measured in g-force or in SI units), ambient air temperature information, engine rotation-per-minute (RPM) information, vehicle location information, and other vehicle-related data.
- vehicle diagnostic information e.g. engine temperature, oil level, OBD codes, and etc.
- fuel consumption-related information e.g. engine temperature, oil level, OBD codes, and etc.
- vehicle speed information e.g. measured in g-force or in SI units
- vehicle acceleration and deceleration information i.e. measured in g-force or in SI units
- ambient air temperature information i.e. measured in
- OBD on-board diagnostics protocol converter unit
- OPC on-board diagnostics protocol converter unit
- the existing library of OBD protocols may contain one or more commonly-utilized and standardized OBD data format decoders and any related extension data format decoders.
- the OPC may be a standalone dongle that plugs into a vehicle on-board diagnostics (OBD) unit and/or a generic or proprietary OBD data reader unit that analyzes and transmits real-time vehicle data information to a remote monitoring station unit outside the vehicle.
- OBD vehicle on-board diagnostics
- the OPC may be integrated into the vehicle on-board diagnostics (OBD) unit.
- the OPC and its internal components may comprise semiconductor chips and/or software executables stored in a memory unit or a data storage unit.
- remote monitoring station unit is defined as a vehicle fleet monitoring location for one or more commercial vehicles in operation.
- remote monitoring station units include, but are not limited to, a commercial vehicle operation control center, a vehicle monitoring service center, and a fleet vehicle employer's information technology (IT) control center.
- IT information technology
- a term “computer server” is defined as a physical computer system, another hardware device, a software module executed in an electronic device, or a combination thereof.
- a computer server is connected to one or more data networks, such as a local area network (LAN), a wide area network (WAN), a cellular network, and the Internet.
- LAN local area network
- WAN wide area network
- cellular network a cellular network
- the Internet a computer server can be utilized by a vehicle monitoring personnel for gathering and analyzing vehicle-related data by executing a vehicle condition analytics unit and a vehicle information database.
- One aspect of the present invention is providing a novel OBD protocol interpreter and conversion system that can dynamically decode commonly-known standard OBD formats as well as esoterically-customized and/or non-standard OBD formats that are initially unrecognized by a generic OBD data reader unit connected to the novel OBD protocol interpreter and conversion system.
- another aspect of the present invention is providing an OBD protocol converter unit that can be plugged to a vehicle OBD unit for seamlessly converting any types of standard and non-standard OBD formats to an OBD format compatible for real-time remote vehicle monitoring.
- another aspect of the present invention is providing a method of processing a non-standard and/or unknown OBD protocol for correct decoding by the novel OBD protocol interpreter and conversion system.
- FIG. 1 shows an unknown on-board diagnostics (OBD) protocol interpreter and conversion system ( 100 ) for remote vehicle OBD monitoring, in accordance with an embodiment of the invention.
- the unknown on-board diagnostics (OBD) protocol interpreter and conversion system ( 100 ) comprises a vehicle on-board diagnostics (OBD) unit ( 103 ), an OBD protocol converter unit (i.e.
- OBC also referred herein as the “OPC”) ( 105 ), an OBD data transceiver unit ( 107 ), a data communication network ( 109 ), an unknown OBD protocol analysis module ( 113 ), a new OBD protocol interpreter development unit for deciphering the unknown OBD protocol ( 115 ), and installable new OBD interpreter codes ( 111 ).
- the vehicle on-board diagnostics (OBD) unit ( 103 ), the OBD protocol converter unit ( 105 ), and the OBD data transceiver unit ( 107 ) are typically installed inside a vehicle ( 101 ), such as a truck, a van, a bus, a taxi, a passenger car, or another automobile.
- a vehicle such as a truck, a van, a bus, a taxi, a passenger car, or another automobile.
- the vehicle OBD unit ( 103 ) is typically a standard factory-installed device at the point of auto manufacturing, with OBD data outputs designed to inform a driver or an auto mechanic vehicle-related data parameters through the vehicle's instrument panel or through a maker-specific, region-specific, and/or model-specific vehicle diagnostics machine
- the vehicle OBD unit ( 103 ) is also typically connected to an engine control unit and other vehicular control chipsets to record, diagnose, and generate a variety of engine, vehicle dynamics, and fuel consumption data as a real-time data stream.
- This real-time data stream from the vehicle OBD unit ( 103 ) can be transmitted remotely to a remote monitoring station unit outside the vehicle for remote real-time vehicle condition and fuel consumption analysis, after a data format interpretation and conversion of a native and raw OBD data format from the vehicle OBD unit ( 103 ) to a standardized and compatible OBD data format that the remote monitoring station unit can properly comprehend for data analysis.
- Some vehicle OBD units may generate commonly-known standard OBD format data, while other vehicle OBD units may generate highly-customized, non-standard, region-specific, and/or manufacturer-specific OBD format data that are not readily decodable with a standard OBD decoding library in a generic OBD data reader unit.
- the data format interpretation and conversion is performed in part by the OPC ( 105 ) and also in part by the unknown OBD protocol analysis module ( 113 ) and the new OBD protocol interpreter development unit ( 115 ), if a detailed interpretation of non-standard codes is necessary before data conversion by the OPC ( 105 ).
- the OBD protocol converter unit, or the “OPC,” ( 105 ) is an electronic sub-system, which is designed to detect, determine, and convert all types of OBD data formats.
- the OPC ( 105 ) is configured to process and decode “known” OBD protocols that are recognized by an existing library of OBD protocols accessed by the OPC ( 105 ). More importantly, the OPC ( 105 ) is also capable of processing and eventually decoding “unknown” OBD protocols that cannot be decoded using the existing library of OBD protocols.
- the OPC ( 105 ) may be a standalone dongle that plugs into the vehicle OBD unit ( 103 ) and/or a generic or proprietary OBD data reader unit that analyzes and transmits real-time vehicle data information to a remote monitoring station unit outside the vehicle.
- the OPC ( 105 ) may be integrated into the vehicle OBD unit ( 103 ).
- the OPC ( 105 ) and its internal components may comprise semiconductor chips and/or software executables stored in a memory unit or a data storage unit.
- the eventual decoding of unknown OBD protocols in the OPC ( 105 ) is accomplished by locally storing a sampled stream of an unknown OBD protocol generated by the vehicle OBD unit ( 103 ), after which the sampled stream, a request for an unknown OBD protocol analysis, and a corresponding OPC decoder update request for new OBD protocol interpreter codes are wirelessly transmitted to the unknown OBD protocol analysis module ( 113 ) located remotely outside the vehicle.
- the wireless transmission of the sampled stream of an unknown OBD protocol from the OPC ( 105 ) utilizes the OBD data transceiver unit ( 107 ) installed in the vehicle ( 101 ) and the data communication network ( 109 ), which may be any combination of cellular, satellite, land-mobile radio, landline, or another data communication medium.
- the unknown OBD protocol analysis module ( 113 ) located remotely outside the vehicle receives the sampled stream of the unknown OBD protocol, the request for the unknown OBD protocol analysis, and the corresponding OPC decoder update request for new OBD protocol interpreter codes from the OPC ( 105 ), the unknown OBD protocol analysis module ( 113 ) can provide computerized analysis and preliminary evaluation of the unknown OBD protocol to the new OBD protocol interpreter development unit ( 115 ) for deciphering the unknown OBD protocol.
- the new OBD protocol interpreter development unit ( 115 ) comprises one or more firmware software engineers capable of creating new OBD interpreter codes by inspecting the sampled stream of the unknown OBD protocol and by utilizing the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module ( 113 ).
- the new OBD protocol interpreter development unit ( 115 ) is a machine-learning module with artificial intelligence operating on a computer server, which can autonomously generate the new OBD interpreter codes without human intervention by comparing one or more standardized OBD parameter formats known to the machine-learning module, the sampled stream of the unknown OBD protocol, and the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module ( 113 ).
- the new OBD interpreter codes created from the new OBD protocol interpreter development unit ( 115 ) are then packaged, modified, and transmitted as the installable new OBD interpreter codes ( 111 ) to the OPC ( 105 ), which subsequently performs a firmware update or a decoder update to one or more modules in the OPC ( 105 ).
- a first OBD interpreter chip is utilized in the OPC ( 105 ) for decoding a known set of standard OBD data formats with a standard OBD format library
- a second OBD interpreter chip is utilized in the OPC ( 105 ) for decoding an unknown set of non-standard OBD data formats after requesting, downloading, and incorporating the installable new OBD interpreter codes ( 111 ) from the new OBD protocol interpreter development unit ( 115 ) through the data communication network ( 109 ) and the OBD data transceiver unit ( 107 ).
- a dynamic OBD library associated with the first and/or the second OBD interpreter chips may also be updated to recognize and readily decode the previously-unknown OBD data format without requesting assistance to the new OBD protocol interpreter development unit ( 115 ) in the future.
- a single OBD interpreter chip in the OPC may be capable of processing and decoding both the known set and the unknown set of OBD data formats by accessing the standard OBD format library in case of decoding of the known set of OBD data formats, and by requesting, downloading, and incorporating the installable new OBD interpreter codes ( 111 ) in case of decoding of the unknown set of OBD data formats.
- the OPC ( 105 ) may exist entirely or at least partly as one or more software modules executed in a memory unit and a CPU of an OBD data reader or another computing unit, with the novel capability to process and decode both the known set and the unknown set of OBD data formats using the OBD data transceiver unit ( 107 ), the data communication network ( 109 ), the unknown OBD protocol analysis module ( 113 ), the new OBD protocol interpreter development unit ( 115 ), and the installable new OBD interpreter codes ( 111 ), as described in other embodiments of the invention.
- FIG. 2 shows a data flow diagram ( 200 ) for dynamically interpreting an unknown on-board diagnostics (OBD) protocol from a vehicle in an OBD protocol interpreter and conversion system, in accordance with an embodiment of the invention.
- in-vehicle functional components ( 207 ) for dynamically interpreting the unknown OBD protocol comprise a vehicle on-board diagnostics (OBD) unit ( 103 ), an OBD protocol converter unit ( 105 ), an “Installer A” unit ( 201 ), and an “Installer B” unit ( 203 ), as shown in FIG. 2 .
- external components ( 205 ) that are located remotely away from the vehicle comprise an unknown OBD protocol analysis module ( 113 ), a new OBD interpreter development unit ( 115 ) for deciphering the unknown OBD protocol, and installable new OBD interpreter codes ( 111 ), as also shown in FIG. 2 .
- the external components ( 205 ) may be part of a remote monitoring station unit, which is intended to monitor and analyze vehicle dynamics, fuel consumption, safety, and other vehicular data parameters generated by the vehicle OBD unit ( 103 ) in real-time.
- the vehicle on-board diagnostics (OBD) unit ( 103 ) first generates native and “raw” OBD data outputs.
- the native and raw OBD data outputs from the vehicle OBD unit ( 103 ) may be incomprehensible or incompatible to an OBD decoding scheme utilized by a generic (i.e. not specific to a particular model, make, and/or region) OBD data reader unit, because the native and raw OBD data outputs may have been originally intended to be decoded only by a make and/or vehicle-specific diagnostic machine
- the native and raw OBD data outputs from the vehicle OBD unit ( 103 ) are fed into the OBD protocol converter (OPC) unit ( 105 ), which is typically installed as an aftermarket unit inside a vehicle.
- OPC OBD protocol converter
- the OPC ( 105 ) is a novel electronic sub-system, and is uniquely designed to detect, determine, and convert all types of OBD data formats.
- the OPC ( 105 ) is configured to process and decode “known” OBD protocols that are recognized by an existing library of OBD protocols accessed by the OPC ( 105 ).
- the existing library of OBD protocols may contain one or more commonly-utilized and standardized OBD data format decoders and any related extension data format decoders.
- the OPC ( 105 ) is also capable of processing and eventually decoding “unknown” OBD protocols that cannot be decoded using the existing library of OBD protocols.
- An OBD protocol is determined by the OPC ( 105 ) to be “unknown,” if the OBD protocol does not match a data format stored in a standard OBD format library.
- a sample stream of the unknown OBD protocol and its related log data are then stored in a local memory unit or a data storage associated with the OPC ( 105 ).
- the saved sample stream of the unknown OBD protocol and its related log data are associated with the “Installer A” unit ( 201 ), as shown in FIG. 2 .
- the “Installer A” unit ( 201 ) may be a firmware update management and transmission module executed by a memory unit and a CPU in the OPC ( 105 ). In another embodiment of the invention, the “Installer A” unit ( 201 ) may be a semiconductor chip or another hardware component functioning as a dedicated firmware update chip.
- the “Installer A” unit ( 201 ) is configured to transmit the saved sample stream of the unknown OBD protocol and the related log data to the external components ( 205 ) through a data communication network (e.g. 109 of FIG. 1 ), along with a request for an unknown OBD protocol analysis and a corresponding OPC decoder update request for new OBD protocol interpreter codes. In the preferred embodiment, vehicle-identifying and OPC-identifying information are also transmitted to the external components ( 205 ), when the saved sample stream of the unknown OBD protocol and the related log data are transmitted.
- the unknown OBD protocol analysis module ( 113 ) located remotely outside the vehicle receives the saved sample stream of the unknown OBD protocol, the request for the unknown OBD protocol analysis, and the corresponding OPC decoder update request for new OBD protocol interpreter codes from the OPC ( 105 ), the unknown OBD protocol analysis module ( 113 ) can provide computerized analysis and preliminary evaluation of the unknown OBD protocol to the new OBD protocol interpreter development unit ( 115 ) for deciphering the unknown OBD protocol.
- the unknown OBD protocol analysis module ( 113 ) may compare and contrast data format differences between the saved sample stream of the unknown OBD protocol and one or more commonly-known standardized OBD formats that are likely to be a base data structure for formulation of the unknown OBD protocol by a particular auto manufacturer.
- the unknown OBD protocol analysis module ( 113 ) may also determine a likely base data structure format for the unknown OBD protocol by comparing the vehicle model and make information in the vehicle OBD unit ( 103 ) fetched from the OPC ( 105 ) against a database of regional OBD data customizations by auto manufacturers.
- the new OBD protocol interpreter development unit ( 115 ) includes one or more software engineers who are capable of creating new OBD interpreter codes by inspecting the sampled stream of the unknown OBD protocol and by utilizing the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module ( 113 ).
- the new OBD protocol interpreter development unit ( 115 ) is a machine-learning module with artificial intelligence, which can autonomously generate the new OBD interpreter codes without human intervention by comparing one or more standardized OBD parameter formats known to the machine-learning module, the sampled stream of the unknown OBD protocol, and the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module ( 113 ).
- the new OBD interpreter codes created from the new OBD protocol interpreter development unit ( 115 ) are then packaged, modified, and transmitted as the installable new OBD interpreter codes ( 111 ) to the “Installer B” unit ( 203 ) associated with the OPC ( 105 ) in the in-vehicle functional components ( 207 ).
- the “Installer B” unit ( 203 ) is a download tool for the new OBD protocol interpreter, and the OPC ( 105 ) subsequently performs a firmware update or a decoder update to one or more modules in the OPC ( 105 ).
- a first OBD interpreter chip is utilized in the OPC ( 105 ) for decoding a known set of standard OBD data formats with a standard OBD format library
- a second OBD interpreter chip is utilized in the OPC ( 105 ) for decoding an unknown set of non-standard OBD data formats after requesting, downloading, and incorporating the installable new OBD interpreter codes ( 111 ) from the new OBD protocol interpreter development unit ( 115 ) through the data communication network (e.g. 109 in FIG. 1 ) and the OBD data transceiver unit (e.g. 107 in FIG. 1 ).
- a dynamic OBD library associated with the first and/or the second OBD interpreter chips may also be updated to recognize and readily decode the previously-unknown OBD data format without requesting assistance to the new OBD protocol interpreter development unit ( 115 ) in the future.
- a single OBD interpreter chip in the OPC may be capable of processing and decoding both the known set and the unknown set of OBD data formats by accessing the standard OBD format library in case of decoding of the known set of OBD data formats, and by requesting, downloading, and incorporating the installable new OBD interpreter codes ( 111 ) in case of decoding of the unknown set of OBD data formats.
- the OPC ( 105 ) may exist entirely or at least partly as one or more software modules executed in a memory unit and a CPU of an OBD data reader or another computing unit, with the novel capability to process and decode both the known set and the unknown set of OBD data formats using the OBD data transceiver unit (e.g. 107 in FIG. 1 ), the data communication network (e.g. 109 in FIG. 1 ), the unknown OBD protocol analysis module ( 113 ), the new OBD protocol interpreter development unit ( 115 ), and the installable new OBD interpreter codes ( 111 ), as described in other embodiments of the invention.
- the OBD data transceiver unit e.g. 107 in FIG. 1
- the data communication network e.g. 109 in FIG. 1
- the unknown OBD protocol analysis module 113
- the new OBD protocol interpreter development unit 115
- the installable new OBD interpreter codes 111
- FIG. 3 shows an internal components diagram ( 300 ) for an on-board diagnostics protocol converter (OPC) unit ( 105 ), in accordance with an embodiment of the invention.
- the internal components of the OPC ( 105 ) comprise a “known” OBD protocol interpreter module ( 301 ), an OBD protocol detection module ( 303 ), a vehicle OBD unit connector module ( 305 ), an OBD data transceiver unit connector module ( 307 ), an “unknown” OBD protocol interpreter module ( 309 ), an “unknown” OBD protocol capture module ( 311 ), an “unknown” OBD protocol upload module ( 313 ), and a new OBD interpreter download module for the “unknown” OBD protocol ( 315 ).
- the OPC ( 105 ) is a novel electronic sub-system capable of detecting, determining, and converting all types of OBD data formats.
- the OPC ( 105 ) plugs into a vehicle OBD unit through an OBD connector, and the vehicle OBD unit connector module ( 305 ) is a data interface unit configured to receive and transmit information between the OPC ( 105 ) and the vehicle OBD unit.
- the OPC ( 105 ) further processes an incoming OBD data stream received by the vehicle OBD unit connector module ( 305 ) in the OBD protocol detection module ( 303 ) by comparing an existing library of “known” OBD protocols in a memory unit or a data storage of the OPC ( 105 ) with the incoming OBD data stream.
- the OBD protocol detection module ( 303 ) may be able to readily detect and determine a specific OBD data format for the incoming OBD data stream, if there is a match between the incoming OBD data stream and the existing library of “known” OBD protocols in the memory unit or the data storage of the OPC ( 105 ).
- the “known” OBD protocol interpreter module ( 301 ), at its discretion, can convert the incoming OBD data stream into a more convenient OBD data format for communication with the rest of the system.
- the “known” OBD protocol interpreter module ( 301 ) may want to convert the incoming OBD data stream into a different OBD protocol format for a seamless data analysis compatibility in the remote monitoring station for vehicle dynamics, fuel consumption, and safety monitoring.
- the “known” OBD protocol interpreter module ( 301 ) may simply transmit the incoming OBD data stream to the remote monitoring station through the OBD data transceiver unit connector module ( 307 ) in the OPC ( 105 ), which is operatively connected to the OBD data transceiver unit (e.g. 107 in FIG. 1 ).
- the OBD protocol detection module ( 303 ) determines that the incoming OBD data stream is an “unknown” OBD data protocol, and forwards the incoming OBD data stream to the “unknown” OBD protocol capture module ( 311 ).
- the “unknown” OBD protocol capture module ( 311 ) in the OPC ( 105 ) stores the incoming OBD data stream in a local memory unit or a data storage, and then prompts the “unknown” OBD protocol upload module ( 313 ) to transmit the saved incoming OBD data stream, a request for an unknown OBD protocol analysis, and a corresponding OPC decoder update request for new OBD protocol interpreter codes to an external component, such as the unknown OBD protocol analysis module (e.g. 113 in FIG. 1 ) located remotely outside the vehicle.
- the unknown OBD protocol analysis module e.g. 113 in FIG. 1
- the transmission of the saved incoming OBD data stream and the new interpreter codes requests is performed through a vehicle-integrated OBD data transceiver unit (e.g. 107 in FIG. 1 ) and a data communication network (e.g. 109 in FIG. 1 ), which may be any combination of cellular, satellite, land-mobile radio, landline, or another data communication medium.
- a vehicle-integrated OBD data transceiver unit e.g. 107 in FIG. 1
- a data communication network e.g. 109 in FIG. 1
- the unknown OBD protocol analysis module located remotely outside the vehicle receives the saved incoming OBD data stream and the new interpreter codes requests
- the unknown OBD protocol analysis module e.g. 113 in FIG. 1
- the new OBD protocol interpreter development unit (e.g. 115 in FIG. 1 ) then creates new OBD interpreter codes by inspecting a sampled stream of the unknown OBD protocol and by utilizing the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module (e.g. 113 in FIG. 1 ). Then, the new OBD interpreter codes created from the new OBD protocol interpreter development unit (e.g. 115 in FIG. 1 ) are then packaged, modified, and transmitted as the installable new OBD interpreter codes (e.g. 111 in FIG. 1 ) to the new OBD interpreter download module ( 315 ) in the OPC ( 105 ), as shown in FIG. 3 .
- the new OBD interpreter download module ( 315 ) integrates or is associated with an installer unit (e.g. the “Installer B” unit ( 203 )) for performing a firmware update or a decoder update to the “unknown” OBD protocol interpreter module ( 309 ) in the OPC ( 105 ).
- the “unknown” OBD protocol interpreter module ( 309 ) is configured to contain a new OBD data format decoder created from the installable new OBD interpreter codes (e.g. 111 in FIG. 1 ), which are downloaded from the new OBD protocol interpreter development unit (e.g. 115 in FIG. 1 ).
- the “unknown” OBD protocol interpreter module ( 309 ) can also build a new OBD data format library with multiple types of new OBD interpreter codes downloaded from the new OBD protocol interpreter development unit (e.g. 115 in FIG. 1 ) through a multiple number of unknown OBD protocol encounters from the incoming OBD data stream.
- various modules contained in the OPC ( 105 ) may be implemented on one or more semiconductor chips.
- various modules contained in the OPC ( 105 ) may be implemented as software modules, which are executable on a CPU and a memory unit of the OPC ( 105 ) or another electronic system.
- various modules contained in the OPC ( 105 ) may be implemented as a combination of hardware and software modules.
- the functionality of each module shown in the internal components diagram ( 300 ) may be combined or integrated in a smaller or larger number of hardware and/or software modules.
- FIG. 4 shows an operational flowchart ( 400 ) for an unknown on-board diagnostics (OBD) protocol interpreter and conversion system for remote vehicle OBD monitoring, in accordance with an embodiment of the invention.
- OBD protocol converter unit OPC
- STEP 401 an OBD protocol converter unit
- STEP 402 the OPC attempts to detect a known OBD protocol by comparing an incoming stream of OBD data from the vehicle OBD unit with an existing library of OBD protocols in the OPC, as shown in STEP 402 .
- the OPC determines that the incoming stream of OBD data is an unknown OBD protocol. Subsequently, the OPC saves the incoming stream of the unknown OBD protocol to a local memory or another data storage in the OPC, as shown in STEP 405 . A sample of the unknown OBD protocol stream is then wirelessly transmitted to an unknown protocol analysis module, which is remotely located outside the vehicle, as shown in STEP 406 .
- new OBD interpreter codes are created for proper conversion of the unknown OBD protocol to an output format compatible to various components of the vehicle OBD monitoring system, as shown in STEP 407 .
- the new OBD interpreter development unit then transmits the new OBD interpreter codes to the OPC, which subsequently utilizes an installer tool to install the new OBD interpreter codes and update the OPC's library of OBD protocols, as shown in STEP 408 .
- the OPC is now capable of decoding what was previously determined as the “unknown” OBD protocol by accessing the new OBD interpreter codes in the OPC's updated library of OBD protocols.
- the OPC can generate a preferred data output format compatible to the rest of the vehicle OBD monitoring system using the updated library of OBD protocols, as shown in STEP 404 .
- the OPC can proceed straight to STEP 404 , instead of taking STEPs 405 ⁇ 408 first, to convert the known OBD protocol in the OPC to a preferred output format compatible to the rest of the vehicle OBD monitoring system using the existing library of OBD protocols.
- Various embodiments of the present invention provide several key advantages over conventional OBD data readout methods using a maker-specific, region-specific, and/or model-specific proprietary diagnostic reader or a generic conventional OBD data reader.
- One advantage of an embodiment of the present invention is providing a novel OBD protocol interpreter and conversion system that can dynamically decode commonly-known standard OBD formats as well as esoterically-customized and/or non-standard OBD formats that are initially unrecognized by a generic OBD data reader unit connected to the novel OBD protocol interpreter and conversion system.
- another advantage of an embodiment of the present invention is providing an OBD protocol converter unit that can be plugged to a vehicle OBD unit for seamlessly converting any types of standard and non-standard OBD formats to an OBD format compatible for real-time remote vehicle monitoring.
- another advantage of an embodiment of the present invention is providing a method of processing a non-standard and/or unknown OBD protocol for correct decoding by the novel OBD protocol interpreter and conversion system.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Chemical & Material Sciences (AREA)
- Combustion & Propulsion (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
- The present invention generally relates to remote real-time vehicle on-board diagnostics (OBD) monitoring. More specifically, various embodiments of the present invention relate to an on-board diagnostics (OBD) protocol interpreter and conversion system for decoding incompatible OBD output data from a vehicle OBD unit.
- A modern vehicle manufactured in recent decades typically integrates an on-board diagnostics (OBD) unit, which is connected to an engine control unit (ECU), fuel consumption instruments, vehicle sensors, and other devices in the vehicle. As a factory-standard device at the point of vehicle manufacturing, the OBD unit was originally conceived to make vehicle maintenance, diagnostics, and repairs simpler at an authorized service facility that has a corresponding OBD data reader unit. A variety of OBD data formats have been developed in the past several decades, and many of them were originally intended to be standardized for OBD data reader compatibility among a plurality of OBD data readers. As a result, the Society of Automotive Engineers (SAE) and the International Organization for Standardization (ISO) have created numerous OBD data format standards, such as SAE J1850 PWM, SAE J1850 VPW, ISO 9141-2, ISO 14230-4, and ISO 15765-4, which are utilized for “OBD2” and “EOBD” regional standards. Furthermore, SAE J1939, SAE J1587, and SAE J1708 have been created for on-board diagnostics data readout from heavy duty trucks.
- The usage of these existing OBD standards tends to be regionally fragmented, with some standards being more heavily utilized in one region (e.g. North America) over another (e.g. Europe). Furthermore, despite the original intent of compatibility for data readout regardless of particular names and makes of vehicles, many automakers customize OBD data formats to be maker-specific or even model-specific that can only be decoded properly by a corresponding maker-specific OBD reader device at a manufacturer-authorized service facility. For example, “2012-Mack-GU813E” is a Mack truck model-specific OBD protocol for use in Chile, and “2011-Mercedes Benz-Axor” is a Mercedes-specific OBD protocol for use in Brazil. These region and manufacturer-specific OBD protocols are typically not decipherable by a generic “universal” OBD data reader unit.
- Thus, the pervasive practice of customizing OBD data formats by region and/or by automakers present significant challenges to a generic “universal” OBD data reader unit that attempts to decipher all types of OBD data formats, including the esoterically-customized OBD data by regions, makes, and models. The lack of OBD format compatibility may be especially problematic in a current automotive technological evolution for connected cars and remote vehicle monitoring, because a real-time OBD data readout for vehicle dynamics, fuel consumption, and condition analysis may require an integration or installation of a generic “universal” OBD data reader unit that can decode all kinds of OBD data formats, regardless of regions, makes, and models.
- Therefore, it may be desirable to devise a novel OBD protocol interpreter and conversion system that can dynamically decode a known set of standard OBD formats as well as esoterically-customized and/or non-standard OBD formats that are unrecognized by a generic OBD data reader unit. Furthermore, it may also be desirable to devise an OBD protocol converter unit that can be plugged to a vehicle OBD unit for seamlessly converting any types of standard and non-standard OBD formats to an OBD format compatible for real-time remote vehicle monitoring. In addition, it may also be desirable to devise a method of processing a non-standard and/or unknown OBD protocol for correct decoding by the novel OBD protocol interpreter and conversion system.
- Summary and Abstract summarize some aspects of the present invention. Simplifications or omissions may have been made to avoid obscuring the purpose of the Summary or the Abstract. These simplifications or omissions are not intended to limit the scope of the present invention.
- In one embodiment of the invention, an unknown on-board diagnostics
- (OBD) protocol interpreter and conversion system for remote vehicle OBD monitoring is disclosed. This unknown OBD protocol interpreter and conversion system comprises: a vehicle on-board diagnostics (OBD) unit connected to an engine control unit or a vehicular control chipset of a vehicle to record, diagnose, and generate vehicle speed data, acceleration and deceleration data, ambient air temperature data, and other vehicle diagnostics data as a raw OBD data stream; an on-board diagnostics (OBD) protocol converter unit connected to the vehicle on-board diagnostics unit, wherein the on-board diagnostics protocol converter unit is configured to decode an unknown OBD protocol to an OBD protocol library as well as a known OBD protocol to the OBD protocol library, wherein the unknown OBD protocol is correctly decoded by saving the raw OBD data stream, transmitting the raw OBD data stream and a request for analysis of the unknown OBD protocol to a remote monitoring station located remotely outside of the vehicle, receiving installable new OBD interpreter codes from a new OBD interpreter development unit in the remote monitoring station, and interpreting the unknown OBD protocol with the installable new OBD interpreter codes updated in the on-board diagnostics protocol converter unit; an on-board data transceiver unit connected to the on-board diagnostics protocol converter unit, wherein the on-board data transceiver unit is configured to transmit information to or receive the information from the new OBD interpreter development unit via a data communication network; and the data communication network configured to provide a wireless data information transfer between the OBD data transceiver unit and the on-board diagnostics protocol converter unit.
-
FIG. 1 shows an unknown on-board diagnostics (OBD) protocol interpreter and conversion system for remote vehicle OBD monitoring, in accordance with an embodiment of the invention. -
FIG. 2 shows a data flow diagram for dynamically interpreting an unknown on-board diagnostics (OBD) protocol from a vehicle in an OBD protocol interpreter and conversion system, in accordance with an embodiment of the invention. -
FIG. 3 shows an internal components diagram for an on-board diagnostics protocol converter (OPC) unit, in accordance with an embodiment of the invention. -
FIG. 4 shows an operational flowchart for an unknown on-board diagnostics (OBD) interpreter and conversion system for remote vehicle OBD monitoring, in accordance with an embodiment of the invention. - Specific embodiments of the invention will now be described in detail with reference to the accompanying figures. Like elements in the various figures are denoted by like reference numerals for consistency.
- In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a more thorough understanding of the invention. However, it will be apparent to one of ordinary skill in the art that the invention may be practiced without these specific details. In other instances, well-known features have not been described in detail to avoid unnecessarily complicating the description.
- The detailed description is presented largely in terms of description of shapes, configurations, and/or other symbolic representations that directly or indirectly resemble one or more on-board diagnostics (OBD) interpreter and conversion systems, OBD protocol converter (OPC) units that operate within the OBD protocol interpreter and conversion systems, and one or more related methods of operation. These descriptions and representations are the means used by those experienced or skilled in the art to most effectively convey the substance of their work to others skilled in the art.
- Reference herein to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Furthermore, separate or alternative embodiments are not necessarily mutually exclusive of other embodiments. Moreover, the order of blocks in process flowcharts or diagrams representing one or more embodiments of the invention do not inherently indicate any particular order nor imply any limitations in the invention.
- For the purpose of describing the invention, a term “vehicle on-board diagnostics (OBD) unit” is defined as an electronic device installed in a vehicle to collect and/or analyze a variety of vehicle-related data. In one example, the vehicle OBD unit outputs many data parameters in real-time, such as vehicle diagnostic information (e.g. engine temperature, oil level, OBD codes, and etc.), fuel consumption-related information, vehicle speed information, vehicle acceleration and deceleration information (i.e. measured in g-force or in SI units), ambient air temperature information, engine rotation-per-minute (RPM) information, vehicle location information, and other vehicle-related data. These data parameters may also be correlated to timestamps generated by an electronic clock associated with the vehicle OBD unit. In one embodiment of the invention, the data parameters may be generated by the vehicle OBD unit in a region-specific, maker-specific, and/or model-specific format, which requires interpretation and conversion to a compatible output format decodable by a remote vehicle OBD monitoring system.
- Furthermore, for the purpose of describing the invention, a term “on-board diagnostics protocol converter unit,” or “OPC,” is defined as an electronic sub-system designed to detect, determine, and convert all types of OBD data formats, including “known” OBD protocols that are recognized by an existing library of OBD protocols accessed by the OPC, as well as “unknown” OBD protocols that cannot be decoded using the existing library of OBD protocols. The existing library of OBD protocols may contain one or more commonly-utilized and standardized OBD data format decoders and any related extension data format decoders. In one embodiment of the invention, the OPC may be a standalone dongle that plugs into a vehicle on-board diagnostics (OBD) unit and/or a generic or proprietary OBD data reader unit that analyzes and transmits real-time vehicle data information to a remote monitoring station unit outside the vehicle. In another embodiment of the invention, the OPC may be integrated into the vehicle on-board diagnostics (OBD) unit. The OPC and its internal components may comprise semiconductor chips and/or software executables stored in a memory unit or a data storage unit.
- Furthermore, for the purpose of describing the invention, a term “remote monitoring station unit” is defined as a vehicle fleet monitoring location for one or more commercial vehicles in operation. Examples of remote monitoring station units include, but are not limited to, a commercial vehicle operation control center, a vehicle monitoring service center, and a fleet vehicle employer's information technology (IT) control center.
- In addition, for the purpose of describing the invention, a term “computer server” is defined as a physical computer system, another hardware device, a software module executed in an electronic device, or a combination thereof. Furthermore, in one embodiment of the invention, a computer server is connected to one or more data networks, such as a local area network (LAN), a wide area network (WAN), a cellular network, and the Internet. Moreover, a computer server can be utilized by a vehicle monitoring personnel for gathering and analyzing vehicle-related data by executing a vehicle condition analytics unit and a vehicle information database.
- One aspect of the present invention is providing a novel OBD protocol interpreter and conversion system that can dynamically decode commonly-known standard OBD formats as well as esoterically-customized and/or non-standard OBD formats that are initially unrecognized by a generic OBD data reader unit connected to the novel OBD protocol interpreter and conversion system.
- Furthermore, another aspect of the present invention is providing an OBD protocol converter unit that can be plugged to a vehicle OBD unit for seamlessly converting any types of standard and non-standard OBD formats to an OBD format compatible for real-time remote vehicle monitoring.
- Moreover, another aspect of the present invention is providing a method of processing a non-standard and/or unknown OBD protocol for correct decoding by the novel OBD protocol interpreter and conversion system.
-
FIG. 1 shows an unknown on-board diagnostics (OBD) protocol interpreter and conversion system (100) for remote vehicle OBD monitoring, in accordance with an embodiment of the invention. In a preferred embodiment of the invention, the unknown on-board diagnostics (OBD) protocol interpreter and conversion system (100) comprises a vehicle on-board diagnostics (OBD) unit (103), an OBD protocol converter unit (i.e. also referred herein as the “OPC”) (105), an OBD data transceiver unit (107), a data communication network (109), an unknown OBD protocol analysis module (113), a new OBD protocol interpreter development unit for deciphering the unknown OBD protocol (115), and installable new OBD interpreter codes (111). - In the preferred embodiment of the invention as shown in
FIG. 1 , the vehicle on-board diagnostics (OBD) unit (103), the OBD protocol converter unit (105), and the OBD data transceiver unit (107) are typically installed inside a vehicle (101), such as a truck, a van, a bus, a taxi, a passenger car, or another automobile. Furthermore, the vehicle OBD unit (103) is typically a standard factory-installed device at the point of auto manufacturing, with OBD data outputs designed to inform a driver or an auto mechanic vehicle-related data parameters through the vehicle's instrument panel or through a maker-specific, region-specific, and/or model-specific vehicle diagnostics machine The vehicle OBD unit (103) is also typically connected to an engine control unit and other vehicular control chipsets to record, diagnose, and generate a variety of engine, vehicle dynamics, and fuel consumption data as a real-time data stream. This real-time data stream from the vehicle OBD unit (103) can be transmitted remotely to a remote monitoring station unit outside the vehicle for remote real-time vehicle condition and fuel consumption analysis, after a data format interpretation and conversion of a native and raw OBD data format from the vehicle OBD unit (103) to a standardized and compatible OBD data format that the remote monitoring station unit can properly comprehend for data analysis. Some vehicle OBD units may generate commonly-known standard OBD format data, while other vehicle OBD units may generate highly-customized, non-standard, region-specific, and/or manufacturer-specific OBD format data that are not readily decodable with a standard OBD decoding library in a generic OBD data reader unit. In the preferred embodiment of the invention, the data format interpretation and conversion is performed in part by the OPC (105) and also in part by the unknown OBD protocol analysis module (113) and the new OBD protocol interpreter development unit (115), if a detailed interpretation of non-standard codes is necessary before data conversion by the OPC (105). - Continuing with
FIG. 1 , the OBD protocol converter unit, or the “OPC,” (105) is an electronic sub-system, which is designed to detect, determine, and convert all types of OBD data formats. The OPC (105) is configured to process and decode “known” OBD protocols that are recognized by an existing library of OBD protocols accessed by the OPC (105). More importantly, the OPC (105) is also capable of processing and eventually decoding “unknown” OBD protocols that cannot be decoded using the existing library of OBD protocols. In one embodiment of the invention, the OPC (105) may be a standalone dongle that plugs into the vehicle OBD unit (103) and/or a generic or proprietary OBD data reader unit that analyzes and transmits real-time vehicle data information to a remote monitoring station unit outside the vehicle. In another embodiment of the invention, the OPC (105) may be integrated into the vehicle OBD unit (103). Furthermore, the OPC (105) and its internal components may comprise semiconductor chips and/or software executables stored in a memory unit or a data storage unit. - In the preferred embodiment of the invention as shown in
FIG. 1 , the eventual decoding of unknown OBD protocols in the OPC (105) is accomplished by locally storing a sampled stream of an unknown OBD protocol generated by the vehicle OBD unit (103), after which the sampled stream, a request for an unknown OBD protocol analysis, and a corresponding OPC decoder update request for new OBD protocol interpreter codes are wirelessly transmitted to the unknown OBD protocol analysis module (113) located remotely outside the vehicle. In the preferred embodiment, the wireless transmission of the sampled stream of an unknown OBD protocol from the OPC (105) utilizes the OBD data transceiver unit (107) installed in the vehicle (101) and the data communication network (109), which may be any combination of cellular, satellite, land-mobile radio, landline, or another data communication medium. - Once the unknown OBD protocol analysis module (113) located remotely outside the vehicle receives the sampled stream of the unknown OBD protocol, the request for the unknown OBD protocol analysis, and the corresponding OPC decoder update request for new OBD protocol interpreter codes from the OPC (105), the unknown OBD protocol analysis module (113) can provide computerized analysis and preliminary evaluation of the unknown OBD protocol to the new OBD protocol interpreter development unit (115) for deciphering the unknown OBD protocol. In one embodiment of the invention, the new OBD protocol interpreter development unit (115) comprises one or more firmware software engineers capable of creating new OBD interpreter codes by inspecting the sampled stream of the unknown OBD protocol and by utilizing the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module (113). In another embodiment of the invention, the new OBD protocol interpreter development unit (115) is a machine-learning module with artificial intelligence operating on a computer server, which can autonomously generate the new OBD interpreter codes without human intervention by comparing one or more standardized OBD parameter formats known to the machine-learning module, the sampled stream of the unknown OBD protocol, and the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module (113).
- The new OBD interpreter codes created from the new OBD protocol interpreter development unit (115) are then packaged, modified, and transmitted as the installable new OBD interpreter codes (111) to the OPC (105), which subsequently performs a firmware update or a decoder update to one or more modules in the OPC (105). In one embodiment of the invention, a first OBD interpreter chip is utilized in the OPC (105) for decoding a known set of standard OBD data formats with a standard OBD format library, while a second OBD interpreter chip is utilized in the OPC (105) for decoding an unknown set of non-standard OBD data formats after requesting, downloading, and incorporating the installable new OBD interpreter codes (111) from the new OBD protocol interpreter development unit (115) through the data communication network (109) and the OBD data transceiver unit (107). Once the installable new OBD interpreter codes (111) are downloaded and updated in the second OBD interpreter chip, a dynamic OBD library associated with the first and/or the second OBD interpreter chips may also be updated to recognize and readily decode the previously-unknown OBD data format without requesting assistance to the new OBD protocol interpreter development unit (115) in the future.
- In another embodiment of the invention, a single OBD interpreter chip in the OPC (105) may be capable of processing and decoding both the known set and the unknown set of OBD data formats by accessing the standard OBD format library in case of decoding of the known set of OBD data formats, and by requesting, downloading, and incorporating the installable new OBD interpreter codes (111) in case of decoding of the unknown set of OBD data formats. Yet in another embodiment of the invention, the OPC (105) may exist entirely or at least partly as one or more software modules executed in a memory unit and a CPU of an OBD data reader or another computing unit, with the novel capability to process and decode both the known set and the unknown set of OBD data formats using the OBD data transceiver unit (107), the data communication network (109), the unknown OBD protocol analysis module (113), the new OBD protocol interpreter development unit (115), and the installable new OBD interpreter codes (111), as described in other embodiments of the invention.
-
FIG. 2 shows a data flow diagram (200) for dynamically interpreting an unknown on-board diagnostics (OBD) protocol from a vehicle in an OBD protocol interpreter and conversion system, in accordance with an embodiment of the invention. In this embodiment, in-vehicle functional components (207) for dynamically interpreting the unknown OBD protocol comprise a vehicle on-board diagnostics (OBD) unit (103), an OBD protocol converter unit (105), an “Installer A” unit (201), and an “Installer B” unit (203), as shown inFIG. 2 . Furthermore, external components (205) that are located remotely away from the vehicle comprise an unknown OBD protocol analysis module (113), a new OBD interpreter development unit (115) for deciphering the unknown OBD protocol, and installable new OBD interpreter codes (111), as also shown inFIG. 2 . The external components (205) may be part of a remote monitoring station unit, which is intended to monitor and analyze vehicle dynamics, fuel consumption, safety, and other vehicular data parameters generated by the vehicle OBD unit (103) in real-time. - As shown by the data flow diagram (200) in this embodiment of the invention, the vehicle on-board diagnostics (OBD) unit (103) first generates native and “raw” OBD data outputs. The native and raw OBD data outputs from the vehicle OBD unit (103) may be incomprehensible or incompatible to an OBD decoding scheme utilized by a generic (i.e. not specific to a particular model, make, and/or region) OBD data reader unit, because the native and raw OBD data outputs may have been originally intended to be decoded only by a make and/or vehicle-specific diagnostic machine
- In accordance with an embodiment of the invention, the native and raw OBD data outputs from the vehicle OBD unit (103) are fed into the OBD protocol converter (OPC) unit (105), which is typically installed as an aftermarket unit inside a vehicle. The OPC (105) is a novel electronic sub-system, and is uniquely designed to detect, determine, and convert all types of OBD data formats. The OPC (105) is configured to process and decode “known” OBD protocols that are recognized by an existing library of OBD protocols accessed by the OPC (105). The existing library of OBD protocols may contain one or more commonly-utilized and standardized OBD data format decoders and any related extension data format decoders. Furthermore, the OPC (105) is also capable of processing and eventually decoding “unknown” OBD protocols that cannot be decoded using the existing library of OBD protocols. An OBD protocol is determined by the OPC (105) to be “unknown,” if the OBD protocol does not match a data format stored in a standard OBD format library. A sample stream of the unknown OBD protocol and its related log data are then stored in a local memory unit or a data storage associated with the OPC (105). In the preferred embodiment of the invention, the saved sample stream of the unknown OBD protocol and its related log data are associated with the “Installer A” unit (201), as shown in
FIG. 2 . - In one embodiment of the invention, the “Installer A” unit (201) may be a firmware update management and transmission module executed by a memory unit and a CPU in the OPC (105). In another embodiment of the invention, the “Installer A” unit (201) may be a semiconductor chip or another hardware component functioning as a dedicated firmware update chip. The “Installer A” unit (201) is configured to transmit the saved sample stream of the unknown OBD protocol and the related log data to the external components (205) through a data communication network (e.g. 109 of
FIG. 1 ), along with a request for an unknown OBD protocol analysis and a corresponding OPC decoder update request for new OBD protocol interpreter codes. In the preferred embodiment, vehicle-identifying and OPC-identifying information are also transmitted to the external components (205), when the saved sample stream of the unknown OBD protocol and the related log data are transmitted. - Then, as shown in
FIG. 2 , once the unknown OBD protocol analysis module (113) located remotely outside the vehicle receives the saved sample stream of the unknown OBD protocol, the request for the unknown OBD protocol analysis, and the corresponding OPC decoder update request for new OBD protocol interpreter codes from the OPC (105), the unknown OBD protocol analysis module (113) can provide computerized analysis and preliminary evaluation of the unknown OBD protocol to the new OBD protocol interpreter development unit (115) for deciphering the unknown OBD protocol. For example, the unknown OBD protocol analysis module (113) may compare and contrast data format differences between the saved sample stream of the unknown OBD protocol and one or more commonly-known standardized OBD formats that are likely to be a base data structure for formulation of the unknown OBD protocol by a particular auto manufacturer. The unknown OBD protocol analysis module (113) may also determine a likely base data structure format for the unknown OBD protocol by comparing the vehicle model and make information in the vehicle OBD unit (103) fetched from the OPC (105) against a database of regional OBD data customizations by auto manufacturers. - In one embodiment of the invention, the new OBD protocol interpreter development unit (115) includes one or more software engineers who are capable of creating new OBD interpreter codes by inspecting the sampled stream of the unknown OBD protocol and by utilizing the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module (113). In another embodiment of the invention, the new OBD protocol interpreter development unit (115) is a machine-learning module with artificial intelligence, which can autonomously generate the new OBD interpreter codes without human intervention by comparing one or more standardized OBD parameter formats known to the machine-learning module, the sampled stream of the unknown OBD protocol, and the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module (113).
- The new OBD interpreter codes created from the new OBD protocol interpreter development unit (115) are then packaged, modified, and transmitted as the installable new OBD interpreter codes (111) to the “Installer B” unit (203) associated with the OPC (105) in the in-vehicle functional components (207). The “Installer B” unit (203) is a download tool for the new OBD protocol interpreter, and the OPC (105) subsequently performs a firmware update or a decoder update to one or more modules in the OPC (105). In one embodiment of the invention, a first OBD interpreter chip is utilized in the OPC (105) for decoding a known set of standard OBD data formats with a standard OBD format library, while a second OBD interpreter chip is utilized in the OPC (105) for decoding an unknown set of non-standard OBD data formats after requesting, downloading, and incorporating the installable new OBD interpreter codes (111) from the new OBD protocol interpreter development unit (115) through the data communication network (e.g. 109 in
FIG. 1 ) and the OBD data transceiver unit (e.g. 107 inFIG. 1 ). Once the installable new OBD interpreter codes (111) are downloaded and updated in the second OBD interpreter chip, a dynamic OBD library associated with the first and/or the second OBD interpreter chips may also be updated to recognize and readily decode the previously-unknown OBD data format without requesting assistance to the new OBD protocol interpreter development unit (115) in the future. - In another embodiment of the invention, a single OBD interpreter chip in the OPC (105) may be capable of processing and decoding both the known set and the unknown set of OBD data formats by accessing the standard OBD format library in case of decoding of the known set of OBD data formats, and by requesting, downloading, and incorporating the installable new OBD interpreter codes (111) in case of decoding of the unknown set of OBD data formats. Yet in another embodiment of the invention, the OPC (105) may exist entirely or at least partly as one or more software modules executed in a memory unit and a CPU of an OBD data reader or another computing unit, with the novel capability to process and decode both the known set and the unknown set of OBD data formats using the OBD data transceiver unit (e.g. 107 in
FIG. 1 ), the data communication network (e.g. 109 inFIG. 1 ), the unknown OBD protocol analysis module (113), the new OBD protocol interpreter development unit (115), and the installable new OBD interpreter codes (111), as described in other embodiments of the invention. -
FIG. 3 shows an internal components diagram (300) for an on-board diagnostics protocol converter (OPC) unit (105), in accordance with an embodiment of the invention. In this embodiment of the invention, the internal components of the OPC (105) comprise a “known” OBD protocol interpreter module (301), an OBD protocol detection module (303), a vehicle OBD unit connector module (305), an OBD data transceiver unit connector module (307), an “unknown” OBD protocol interpreter module (309), an “unknown” OBD protocol capture module (311), an “unknown” OBD protocol upload module (313), and a new OBD interpreter download module for the “unknown” OBD protocol (315). As described previously in association withFIGS. 1-2 , the OPC (105) is a novel electronic sub-system capable of detecting, determining, and converting all types of OBD data formats. First, the OPC (105) plugs into a vehicle OBD unit through an OBD connector, and the vehicle OBD unit connector module (305) is a data interface unit configured to receive and transmit information between the OPC (105) and the vehicle OBD unit. - Then, the OPC (105) further processes an incoming OBD data stream received by the vehicle OBD unit connector module (305) in the OBD protocol detection module (303) by comparing an existing library of “known” OBD protocols in a memory unit or a data storage of the OPC (105) with the incoming OBD data stream. The OBD protocol detection module (303) may be able to readily detect and determine a specific OBD data format for the incoming OBD data stream, if there is a match between the incoming OBD data stream and the existing library of “known” OBD protocols in the memory unit or the data storage of the OPC (105). If the incoming OBD data stream is determined to be a “known” OBD protocol, then the “known” OBD protocol interpreter module (301), at its discretion, can convert the incoming OBD data stream into a more convenient OBD data format for communication with the rest of the system.
- For example, the “known” OBD protocol interpreter module (301) may want to convert the incoming OBD data stream into a different OBD protocol format for a seamless data analysis compatibility in the remote monitoring station for vehicle dynamics, fuel consumption, and safety monitoring. Alternatively, if the incoming OBD data stream is already in a recognized data format for the rest of the system (e.g. various components in the remote monitoring station), then the “known” OBD protocol interpreter module (301), at its discretion, may simply transmit the incoming OBD data stream to the remote monitoring station through the OBD data transceiver unit connector module (307) in the OPC (105), which is operatively connected to the OBD data transceiver unit (e.g. 107 in
FIG. 1 ). - On the other hand, if there is no match or association between the incoming
- OBD data stream and the existing library of “known” OBD protocols in the memory unit or the data storage of the OPC (105), the OBD protocol detection module (303) determines that the incoming OBD data stream is an “unknown” OBD data protocol, and forwards the incoming OBD data stream to the “unknown” OBD protocol capture module (311). In one embodiment of the invention, the “unknown” OBD protocol capture module (311) in the OPC (105) stores the incoming OBD data stream in a local memory unit or a data storage, and then prompts the “unknown” OBD protocol upload module (313) to transmit the saved incoming OBD data stream, a request for an unknown OBD protocol analysis, and a corresponding OPC decoder update request for new OBD protocol interpreter codes to an external component, such as the unknown OBD protocol analysis module (e.g. 113 in
FIG. 1 ) located remotely outside the vehicle. - In one embodiment of the invention, the transmission of the saved incoming OBD data stream and the new interpreter codes requests is performed through a vehicle-integrated OBD data transceiver unit (e.g. 107 in
FIG. 1 ) and a data communication network (e.g. 109 inFIG. 1 ), which may be any combination of cellular, satellite, land-mobile radio, landline, or another data communication medium. Once the unknown OBD protocol analysis module (e.g. 113 inFIG. 1 ) located remotely outside the vehicle receives the saved incoming OBD data stream and the new interpreter codes requests, the unknown OBD protocol analysis module (e.g. 113 inFIG. 1 ) can provide computerized analysis and preliminary evaluation of the unknown OBD protocol to the new OBD protocol interpreter development unit (e.g. 115 inFIG. 1 ) for deciphering the unknown OBD protocol. - The new OBD protocol interpreter development unit (e.g. 115 in
FIG. 1 ) then creates new OBD interpreter codes by inspecting a sampled stream of the unknown OBD protocol and by utilizing the computerized analysis and preliminary evaluation of the unknown OBD protocol from the unknown OBD protocol analysis module (e.g. 113 inFIG. 1 ). Then, the new OBD interpreter codes created from the new OBD protocol interpreter development unit (e.g. 115 inFIG. 1 ) are then packaged, modified, and transmitted as the installable new OBD interpreter codes (e.g. 111 inFIG. 1 ) to the new OBD interpreter download module (315) in the OPC (105), as shown inFIG. 3 . The new OBD interpreter download module (315) integrates or is associated with an installer unit (e.g. the “Installer B” unit (203)) for performing a firmware update or a decoder update to the “unknown” OBD protocol interpreter module (309) in the OPC (105). The “unknown” OBD protocol interpreter module (309) is configured to contain a new OBD data format decoder created from the installable new OBD interpreter codes (e.g. 111 inFIG. 1 ), which are downloaded from the new OBD protocol interpreter development unit (e.g. 115 inFIG. 1 ). The “unknown” OBD protocol interpreter module (309) can also build a new OBD data format library with multiple types of new OBD interpreter codes downloaded from the new OBD protocol interpreter development unit (e.g. 115 inFIG. 1 ) through a multiple number of unknown OBD protocol encounters from the incoming OBD data stream. - In one embodiment of the invention, various modules contained in the OPC (105) may be implemented on one or more semiconductor chips. In another embodiment of the invention, various modules contained in the OPC (105) may be implemented as software modules, which are executable on a CPU and a memory unit of the OPC (105) or another electronic system. Yet in another embodiment of the invention, various modules contained in the OPC (105) may be implemented as a combination of hardware and software modules. Furthermore, the functionality of each module shown in the internal components diagram (300) may be combined or integrated in a smaller or larger number of hardware and/or software modules.
-
FIG. 4 shows an operational flowchart (400) for an unknown on-board diagnostics (OBD) protocol interpreter and conversion system for remote vehicle OBD monitoring, in accordance with an embodiment of the invention. In this embodiment of the invention, an OBD protocol converter unit (OPC) is first plugged into a vehicle OBD unit using a data connector, as shown inSTEP 401. Then, the OPC attempts to detect a known OBD protocol by comparing an incoming stream of OBD data from the vehicle OBD unit with an existing library of OBD protocols in the OPC, as shown inSTEP 402. - If the OPC cannot find a suitable match between the existing library of OBD protocols and the incoming stream of OBD data from the vehicle OBD unit, as shown in
STEP 403, then the OPC determines that the incoming stream of OBD data is an unknown OBD protocol. Subsequently, the OPC saves the incoming stream of the unknown OBD protocol to a local memory or another data storage in the OPC, as shown inSTEP 405. A sample of the unknown OBD protocol stream is then wirelessly transmitted to an unknown protocol analysis module, which is remotely located outside the vehicle, as shown inSTEP 406. With a computerized analytical output from the unknown protocol analysis module and new codes development from a new OBD interpreter development unit, new OBD interpreter codes are created for proper conversion of the unknown OBD protocol to an output format compatible to various components of the vehicle OBD monitoring system, as shown inSTEP 407. - The new OBD interpreter development unit then transmits the new OBD interpreter codes to the OPC, which subsequently utilizes an installer tool to install the new OBD interpreter codes and update the OPC's library of OBD protocols, as shown in
STEP 408. Then, the OPC is now capable of decoding what was previously determined as the “unknown” OBD protocol by accessing the new OBD interpreter codes in the OPC's updated library of OBD protocols. The OPC can generate a preferred data output format compatible to the rest of the vehicle OBD monitoring system using the updated library of OBD protocols, as shown inSTEP 404. - Continuing with the operational flowchart (400) in
FIG. 4 , if the incoming stream of OBD data atSTEP 403 was initially determined as a “known” OBD protocol based on a successful matching between the existing library of OBD protocols and the incoming stream of OBD data, then the OPC can proceed straight to STEP 404, instead of takingSTEPs 405˜408 first, to convert the known OBD protocol in the OPC to a preferred output format compatible to the rest of the vehicle OBD monitoring system using the existing library of OBD protocols. - Various embodiments of the present invention provide several key advantages over conventional OBD data readout methods using a maker-specific, region-specific, and/or model-specific proprietary diagnostic reader or a generic conventional OBD data reader. One advantage of an embodiment of the present invention is providing a novel OBD protocol interpreter and conversion system that can dynamically decode commonly-known standard OBD formats as well as esoterically-customized and/or non-standard OBD formats that are initially unrecognized by a generic OBD data reader unit connected to the novel OBD protocol interpreter and conversion system.
- Furthermore, another advantage of an embodiment of the present invention is providing an OBD protocol converter unit that can be plugged to a vehicle OBD unit for seamlessly converting any types of standard and non-standard OBD formats to an OBD format compatible for real-time remote vehicle monitoring. Moreover, another advantage of an embodiment of the present invention is providing a method of processing a non-standard and/or unknown OBD protocol for correct decoding by the novel OBD protocol interpreter and conversion system.
- While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this disclosure, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as disclosed herein. Accordingly, the scope of the invention should be limited only by the attached claims.
Claims (13)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/634,496 US9443360B1 (en) | 2015-02-27 | 2015-02-27 | Unknown on-board diagnostics (OBD) protocol interpreter and conversion system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/634,496 US9443360B1 (en) | 2015-02-27 | 2015-02-27 | Unknown on-board diagnostics (OBD) protocol interpreter and conversion system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20160253849A1 true US20160253849A1 (en) | 2016-09-01 |
US9443360B1 US9443360B1 (en) | 2016-09-13 |
Family
ID=56799051
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/634,496 Active US9443360B1 (en) | 2015-02-27 | 2015-02-27 | Unknown on-board diagnostics (OBD) protocol interpreter and conversion system |
Country Status (1)
Country | Link |
---|---|
US (1) | US9443360B1 (en) |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107517257A (en) * | 2017-08-25 | 2017-12-26 | 同方(深圳)云计算技术股份有限公司 | A kind of car networking service system |
CN108199942A (en) * | 2018-01-08 | 2018-06-22 | 深圳市道通科技股份有限公司 | Vehicle diagnosis method, device, equipment, system and diagnosis connection equipment |
CN108390863A (en) * | 2018-01-31 | 2018-08-10 | 深圳市元征科技股份有限公司 | A kind of data processing method and device |
WO2019018308A1 (en) * | 2017-07-15 | 2019-01-24 | Cytk, Llc | Universal virtual professional toolkit |
NL2019682B1 (en) * | 2017-10-06 | 2019-04-15 | Beijer Invest B V | Vehicle data unlocking device for unlocking vehicle data in a vehicle. |
CN109671184A (en) * | 2018-12-25 | 2019-04-23 | 深圳市元征科技股份有限公司 | A kind of vehicle data stream method for recording, system and relevant device |
US10306428B1 (en) * | 2018-01-03 | 2019-05-28 | Honda Motor Co., Ltd. | System and method of using training data to identify vehicle operations |
CN110049137A (en) * | 2019-04-25 | 2019-07-23 | 广东工业大学 | A kind of instruction transmission method, collecting method and relevant apparatus |
CN112015453A (en) * | 2020-09-14 | 2020-12-01 | 德明通讯(上海)有限责任公司 | Firmware upgrading method for OBD (on-Board diagnostics) embedded equipment |
CN112039875A (en) * | 2020-08-28 | 2020-12-04 | 山东中瑞电气有限公司 | Protocol converter |
CN113721591A (en) * | 2021-09-03 | 2021-11-30 | 深圳市元征科技股份有限公司 | OBD equipment inspection method, device, terminal and storage medium |
CN113743482A (en) * | 2021-08-20 | 2021-12-03 | 郑州云智信安安全技术有限公司 | Vehicle safety detection method based on-board diagnostics (OBD) data of Internet of vehicles |
CN114202004A (en) * | 2020-08-26 | 2022-03-18 | 亿美Ai私人有限公司 | Agent interpreter for upgrading an automated reservation system |
US20220207933A1 (en) * | 2020-12-31 | 2022-06-30 | Jaswinder Kaur | Central controller and modular device |
US20220300362A1 (en) * | 2021-03-22 | 2022-09-22 | Hitachi, Ltd. | Distributed system and diagnostic method |
US20220317671A1 (en) * | 2019-05-28 | 2022-10-06 | Zte Corporation | On-board diagnostics device and system, and detection method and readable storage medium |
US11496567B2 (en) * | 2018-12-26 | 2022-11-08 | Apollo Intelligent Driving Technology (Beijing) Co., Ltd. | Data processing method, apparatus, device and storage medium based on unmanned vehicle |
US20220394112A1 (en) * | 2020-02-19 | 2022-12-08 | HELLA GmbH & Co. KGaA | Device and method for connecting a service-oriented device to a signal-based device |
GB2622576A (en) * | 2022-09-13 | 2024-03-27 | Oxa Autonomy Ltd | System, processor assembly, remote device, and method |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11158141B2 (en) | 2018-04-02 | 2021-10-26 | Innova Electronics Corporation | System and method for proactive vehicle diagnosis and operational alert |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6295492B1 (en) * | 1999-01-27 | 2001-09-25 | Infomove.Com, Inc. | System for transmitting and displaying multiple, motor vehicle information |
US6701233B2 (en) * | 2001-06-01 | 2004-03-02 | Actron Manufacturing Company | Scan tool with dropped communications detection and recovery and improved protocol selection |
US6529808B1 (en) | 2002-04-22 | 2003-03-04 | Delphi Technologies, Inc. | Method and system for analyzing an on-board vehicle computer system |
US20050182535A1 (en) | 2004-02-17 | 2005-08-18 | David Huang | Device and method for identifying a specific communication protocol used in an on-board diagnostic tool |
US7305289B2 (en) * | 2004-05-28 | 2007-12-04 | Spx Corporation | Universal translator for vehicle information |
US9117319B2 (en) * | 2005-06-30 | 2015-08-25 | Innova Electronics, Inc. | Handheld automotive diagnostic tool with VIN decoder and communication system |
US20080167772A1 (en) | 2007-01-04 | 2008-07-10 | Sterling Du | Method and system for processing and transmitting automotive emission data |
US8788139B2 (en) * | 2011-03-21 | 2014-07-22 | Webtech Wireless Inc. | Multi-protocol vehicle diagnostic interface device and method |
-
2015
- 2015-02-27 US US14/634,496 patent/US9443360B1/en active Active
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3655854A4 (en) * | 2017-07-15 | 2020-08-12 | Cytk Llc | Universal virtual professional toolkit |
WO2019018308A1 (en) * | 2017-07-15 | 2019-01-24 | Cytk, Llc | Universal virtual professional toolkit |
CN111108477A (en) * | 2017-07-15 | 2020-05-05 | Cytk有限责任公司 | Universal virtual professional toolkit |
CN107517257A (en) * | 2017-08-25 | 2017-12-26 | 同方(深圳)云计算技术股份有限公司 | A kind of car networking service system |
NL2019682B1 (en) * | 2017-10-06 | 2019-04-15 | Beijer Invest B V | Vehicle data unlocking device for unlocking vehicle data in a vehicle. |
US10306428B1 (en) * | 2018-01-03 | 2019-05-28 | Honda Motor Co., Ltd. | System and method of using training data to identify vehicle operations |
CN108199942A (en) * | 2018-01-08 | 2018-06-22 | 深圳市道通科技股份有限公司 | Vehicle diagnosis method, device, equipment, system and diagnosis connection equipment |
CN108390863A (en) * | 2018-01-31 | 2018-08-10 | 深圳市元征科技股份有限公司 | A kind of data processing method and device |
CN109671184A (en) * | 2018-12-25 | 2019-04-23 | 深圳市元征科技股份有限公司 | A kind of vehicle data stream method for recording, system and relevant device |
US11496567B2 (en) * | 2018-12-26 | 2022-11-08 | Apollo Intelligent Driving Technology (Beijing) Co., Ltd. | Data processing method, apparatus, device and storage medium based on unmanned vehicle |
CN110049137A (en) * | 2019-04-25 | 2019-07-23 | 广东工业大学 | A kind of instruction transmission method, collecting method and relevant apparatus |
US20220317671A1 (en) * | 2019-05-28 | 2022-10-06 | Zte Corporation | On-board diagnostics device and system, and detection method and readable storage medium |
US20220394112A1 (en) * | 2020-02-19 | 2022-12-08 | HELLA GmbH & Co. KGaA | Device and method for connecting a service-oriented device to a signal-based device |
CN114202004A (en) * | 2020-08-26 | 2022-03-18 | 亿美Ai私人有限公司 | Agent interpreter for upgrading an automated reservation system |
CN112039875A (en) * | 2020-08-28 | 2020-12-04 | 山东中瑞电气有限公司 | Protocol converter |
CN112015453A (en) * | 2020-09-14 | 2020-12-01 | 德明通讯(上海)有限责任公司 | Firmware upgrading method for OBD (on-Board diagnostics) embedded equipment |
US20220207933A1 (en) * | 2020-12-31 | 2022-06-30 | Jaswinder Kaur | Central controller and modular device |
US20220300362A1 (en) * | 2021-03-22 | 2022-09-22 | Hitachi, Ltd. | Distributed system and diagnostic method |
CN113743482A (en) * | 2021-08-20 | 2021-12-03 | 郑州云智信安安全技术有限公司 | Vehicle safety detection method based on-board diagnostics (OBD) data of Internet of vehicles |
CN113721591A (en) * | 2021-09-03 | 2021-11-30 | 深圳市元征科技股份有限公司 | OBD equipment inspection method, device, terminal and storage medium |
GB2622576A (en) * | 2022-09-13 | 2024-03-27 | Oxa Autonomy Ltd | System, processor assembly, remote device, and method |
Also Published As
Publication number | Publication date |
---|---|
US9443360B1 (en) | 2016-09-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9443360B1 (en) | Unknown on-board diagnostics (OBD) protocol interpreter and conversion system | |
US20110071725A1 (en) | Remotely interacting with a vehicle to perform servicing and engineering functions from a nomadic device or computer | |
US20080015748A1 (en) | System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port | |
US20080082221A1 (en) | System for monitoring, controlling, and reporting vehicle operation through onboard diagnostic port | |
US7979178B2 (en) | Method of flash programming scan tools and pass thru devices over wireless communications | |
CN110471393B (en) | Apparatus, system and method for remotely capturing, monitoring and controlling diagnostic information of an automobile | |
US11321399B1 (en) | Systems and methods for asset type fingerprinting and data message decoding | |
EP3616168B1 (en) | Method and system to determine vehicle type identification trough diagnostic port | |
US20100185356A1 (en) | Compiling Source Information From A Motor Vehicle Data System and Configuring A Telematic Module | |
US11757676B2 (en) | Systems and methods for asset type fingerprinting and data message decoding | |
US20170190233A1 (en) | Parked Vehicle Interior Lifeform Recognition | |
CN111464651A (en) | Vehicle diagnosis system and method | |
US20220311640A1 (en) | Systems and methods for data message decoding and asset type fingerprinting | |
US20200394850A1 (en) | Vehicle fault diagnosis and analysis based on augmented design failure mode and effect analysis (dfmea) data | |
US20150210288A1 (en) | System for using short text messaging for remote diagnostic | |
EP4270335A1 (en) | Systems and methods for diagnostic tool detection in a telematics device | |
CN108390863B (en) | Data processing method and device | |
JP2016203933A (en) | Obd adapter and attachment method thereof | |
EP3616366B1 (en) | Method to write requests on a vehicle diagnostic bus | |
EP4064652A1 (en) | Systems and methods for asset type fingerprinting and data message decoding | |
KR20140147298A (en) | Digital taco graph and method for data transformaing theirof | |
WO2019051045A1 (en) | Facilitating cross-platform transportation arrangements with third party providers | |
KR20170087703A (en) | System, method and program for providing the data of vehicle driving | |
CN112613514A (en) | Information feedback method and device based on vehicle identification number | |
US20230145354A1 (en) | System and Method for Dynamically Improving Vehicle Diagnostic Systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TRUELITE TRACE, INC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KWAK, SUNGBOK;REEL/FRAME:035057/0567 Effective date: 20150227 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2552); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 8 |