KR20190054640A - A terminal and a method of collecting CAN date of vehicle using a OBD-Ⅱ - Google Patents

Abstract

By providing a universal terminal which includes hardware and an application which are both capable of automatically collecting controller area network (CAN) data of a vehicle from an on-board diagnostic version II (OBD-II) scanner or a connector regardless of vehicle types and a method thereof, anyone can obtain vehicle data regardless of vehicle types. The hardware of the terminal includes: a vehicle communication unit (10); a power determining unit (20); a protocol determining unit (30); a calculation/analysis determining unit (40); a database unit (50); a file storage unit (60); a file transmission unit (70); an external communication unit (80); and a display unit (90). In addition, the application includes a communication module, a determining module, a file management module, a security module, and a display control module.

Description

[0002] The present invention relates to an automatic OBD-II vehicle terminal and a method for collecting CAN data,

The present invention relates to an automatic vehicle CAN data collecting terminal and a collecting method using the OBD-II, and more particularly, it analyzes current CAN (Controller Area Network) communication protocol and selects CAN models individually to collect CAN data (CAN), SAEJ1850 (PWM / VPWM), and can automatically collect data by developing hardware and applications according to communication specifications. The present invention relates to a vehicle automatic data collection terminal and a collection method using the OBD-II.

CAN (Controller Area Network) was first developed in 1985 by Bosch for vehicle networks. CAN provides an economical and reliable network for multiple CAN devices to communicate with each other. The advantage of such a network is that electronic control units (ECUs) have only a single CAN interface, rather than having analog and digital inputs for each device in the system. Thus, the overall cost and weight of the vehicle were also reduced. Each device on the network has a CAN controller chip, which is very intelligent, and every device on the network checks every message sent. Each device determines whether the message is relevant or filtered. Also, since all messages have priority, when two nodes transmit messages at the same time, high priority messages are sent first and low priority messages are delayed.

On-Board Diagnostics, or OBD, is a term used in the automotive industry to describe a device that self-diagnoses and reports the results. Recently produced vehicles are equipped with sensors for various measurement and control, and these devices are controlled by ECU (Electronic Control Unit). The original purpose of the ECU was to precisely control the engine's core functions such as ignition timing and fuel injection, variable valve timing, idling, and threshold setting. However, with the development of vehicle and computer performance, automatic transmission control, System, steering system, and so on. These electronic diagnostic systems have been developed and recently established as a standardized diagnostic system called OBD-II (On-Board Diagnostic version II).

Since January 2005, the OBD-II system has become mandatory for all passenger cars sold in Korea. As a result, the market for OBD-II systems is expected to increase sharply every year. In addition, with the spread of automobiles and the issue of environmental pollution becoming serious, OBD-II is anticipated to become more effective in managing the emission-related management functions. If an abnormality is detected in the exhaust gas related parts, the OBD-II sensor transmits the signal to the ECU of the vehicle, and the ECU enters the engine check in the instrument panel to detect the excessive exhaust gas in advance and manage the driver. The system is being developed.

All cars under the OBD-II standard have adopted standardized Diagnostic Trouble Codes and interface (ISO J1962), but since then, worldwide compatibility has been recognized in the US market, the world's largest automotive market since 2008 All of the automobiles specified to use the standard ISO 15765-4. Accordingly, domestic automobiles are being tailored accordingly.

The connector for connecting the ECU of the vehicle to the external device was in various positions such as the bottom of the dashboard or the hood of the vehicle manufactured before the OBD-II standard. However, the vehicle manufactured by the OBD- Or the position near the ashtray is limited, so that the public can easily find the connector.

When connecting the ISO J1962 connector, which is the current standard, to an external scanner, it is possible to communicate with the ECU using the CAN software installed on the PC or PDA and the OBD-II standard. The OBD-IIS CAN system is capable of diagnosing the function of the level of the vehicle exhaust gas, misfire of a specific cylinder, and abnormality of a three-way catalytic converter.

OBD-II informs the fault through the 5-digit fault diagnosis code in the event of an automobile fault. The types of faults and fault codes are also standardized. In general car repair shops, faults in automobiles can be easily detected using the fault code defined by the OBD-II standard and applied to repairs.

The above-mentioned OBD-II and CAN-based telematics (a compound of Telecommunications and Informatics) are used for location-based services (LBS) via mobile communication network, satellite confirmation system (GPS) and advanced geographic information system ), Intelligent transportation system (ITS), etc., to the driver's vehicle, thereby providing driving route guidance, vehicle accident or theft detection, traffic and various convenience information to the driver in real time.

A variety of protocols, connectors, scanners and terminals are being developed to provide various information utilizing OBD-II and CAN to the driver. Here, the terminal is used as a term including an ODB terminal, an IOT terminal, and the like.

The currently available Monster Gauge OBD II car scanner is connected automatically at the moment of plugging into the vehicle and collects the CAN data of OBD II and outputs various information to the ODB terminal through Bluetooth communication. This information includes information such as vehicle battery level, battery voltage information, tire pressure, fuel consumption, engine failure notification, oil consumption, travel speed / distance / time, coolant temperature, fuel cut / , And gear ratio.

Depending on the manufacturer, grade, and model of passenger cars, commercial vehicles and vehicles, the ECUs applied to the vehicle are different, and thus the diagnostic signals that can be acquired from the OBD II also differ from vehicle to vehicle. The monster gauge described above operates only when a software or a device suitable for an ECU of various vehicles is installed in a scanner or a terminal in advance.

In order to develop and install the software for OBD II scanner and ODB terminal, it is necessary to update the OBD II scanner and update the software installed in the ODB terminal, that is, the application. In this case, the user tends to purchase a new scanner and a new terminal in consideration of the time and expense of updating the old scanner and the terminal.

 The OBD II connector provides two standard hardware interfaces for connection interfaces (ISO J1962): Type A and Type B. The A-type connector is used for vehicles using 12V voltage and the B-type connector is used for 24V voltage and they are incompatible with each other and have means to distinguish them. That is, a structure in which the male type of the A-type connector can not fit into the male type of the B-type connector, and they are distinguished from each other by color. Therefore, it is inconvenient to use them separately.

The OBD-II interface allows for several signaling protocols (usually five). Most vehicles implement only one of the protocols. Therefore, when collecting vehicle CAN data using OBD-II, CAN data must be collected using the OBD-II connector that matches the protocol installed in the vehicle.

In the patent registration No. 10-1282417 (June 28, 2013) (apparatus and method for generating a CAN data file for test), the driving variable setting value of the vehicle is inputted, and the control parameter The method for generating the test CAN data file for updating the reference CAN data for the inter-element communication control and updating the linked CAN data based on the updated reference CAN data, even if the expensive hardware device or the software simulator is not used, It is possible to generate test CAN data that is the same as that at the time of operation of the vehicle, so that the test process can be performed more easily in the product development stage.

Here again, separate test CAN data must be generated according to the vehicle, and no general data generation method is mentioned at all.

Therefore, in the prior art, since the vehicle type is always known, the scanner is installed, the data is collected, the corresponding terminal displays it, and external communication is established, so that the use of the OBD terminal or the IoT terminal has been limited.

Accordingly, in the related technical field, development of technology of OBD terminal or IoT terminal which can be used for general purpose has been continuously demanded.

Patent Registration No. 10-1282417 (Registration date June 28, 2013)

It is an object of the present invention to provide an automatic vehicle CAN data collection terminal and a collection method using the OBD-II.

A more specific object of the present invention is to provide a general-purpose terminal including hardware and an application capable of automatically collecting vehicle CAN data from an OBD-II scanner or a connector regardless of the type of vehicle.

A more specific object of the present invention is to provide a method of automatically collecting vehicle CAN data from an OBD-II scanner or a connector regardless of the type of vehicle using the general-purpose terminal of the present invention.

A more specific object of the present invention is to provide a terminal and a method capable of receiving and processing signals from OBD-II and a sensor separate from the OBD-II.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive of the invention, unless further departing from the spirit and scope of the invention as defined by the appended claims. It will be possible.

In order to achieve this object, the vehicle automatic data collection terminal utilizing the OBD-II of the present invention includes a vehicle communication unit for receiving CAN data for communication control from the control components of the vehicle, A protocol deciding unit for deciding whether the signal protocol is implemented in the OBD II interface installed in the vehicle, and a CAN communication unit 10 for collecting CAN data and generating a CAN data file, An analysis and judgment unit for calculating and analyzing based on the data of the vehicle 50, a base unit for basically storing the data provided to the vehicle, a file storage unit for generating CAN data as a file, To the external communication part for the telematics using the database part and OBD-II and CAN. An external communication unit capable of communicating with the management server by communication means such as a file transfer unit for transmitting data, a Bluetooth communication unit, and the like; and a display unit for displaying necessary information on the screen of the terminal based on the analysis result of the operation and analysis judgment unit, And a display unit capable of selecting and displaying various information.

And an application for operating the above-described components of the terminal, the application including a communication module for communicating with a scanner or a connector for collecting data from the OBD-II and communicating with an external management server, A determination module for accurately determining and analyzing the information of the vehicle in the protocol determination unit, the calculation and analysis determination unit, the file management module for generating, comparing and storing the acquired data in a file format, And a display control module for selectively outputting information according to a driver's need on the terminal screen based on the analysis result of the determination module.

A method of automatically collecting vehicle CAN data using the OBD-II includes a start-on step of transmitting signals from various components installed in the vehicle to the ECU by operating various sensors installed in the vehicle, If the voltage data obtained from the connector or the scanner is 12V, the voltage is analyzed by a commercial vehicle if the voltage is 24V. If the protocol is analyzed based on the data from the connector or the scanner, the OBD II signal protocol is implemented in the vehicle. A data acquiring step of acquiring the vehicle data from the OBD-II after the application is converted in accordance with a protocol implemented in the vehicle, an arithmetic step of computing data collected in the data acquiring step and converting it into information desired by the driver, A storage step of storing the data,

A security step of authenticating by the user's authentication technology, and an external communication connection step of connecting the file generated based on the data collected in the external management server to the network.

In the preferred embodiment of the present invention, if the voltage data obtained from the connector or the scanner is 12V, then the ISISO O14230 (K-line communication), ISO O15765-4 (CAN communication), ISO 9141 K-line communication) and SAEJ1850 (PWM / VPWM communication). If one of them is selected, the application of the terminal matching the protocol is selected and the data is acquired via the next diagnostic filter. If the voltage data is 24V, proceed to the commercial vehicle protocols J 1939 250K and J 1939 250K. If the voltage data is one of the two, the terminal application corresponding to the protocol is selected and then the data is acquired through the diagnostic filter , And if the corresponding protocol is not found, a step of selecting the most suitable protocol among the installed protocols is performed, An application is selected and then the data is acquired via a diagnostic filter.

In another embodiment of the present invention, there is a method of receiving a signal from a sensor by an operation of a driver, processing the data in the terminal, displaying it, or displaying it in combination with other data Or modules.

The present invention provides a general-purpose terminal capable of automatically collecting vehicle CAN data from an OBD-II scanner or a connector, so that data can be acquired from the OBD-II regardless of vehicle type, utilized, and converted into information desired by the driver and displayed .

In addition, by providing a general-purpose terminal including an application that can automatically collect vehicle CAN data from an OBD-II scanner or a connector, data can be acquired from OBD-II regardless of vehicle type, and converted to information desired by the driver and displayed .

The present invention provides a method for automatically collecting vehicle CAN data using a general-purpose terminal, so that anyone can easily acquire vehicle data regardless of the type of vehicle.

Also, even if there is a separate sensor from the OBD-II, it is possible to provide a terminal capable of receiving and processing a signal from these sensors, thereby providing various sensors for further convenience of the driver.

1 is a block diagram of an OBD terminal or an IoT terminal for collecting vehicle CAN data from OBD-II.
2 is a flowchart of an operation procedure of a terminal according to the present invention.
3 is a flowchart of a data acquisition method showing in more detail the method shown in Fig.

It is to be understood that the specific structural or functional description of embodiments of the present invention disclosed herein is for illustrative purposes only and is not intended to limit the scope of the inventive concept But may be embodied in many different forms and is not limited to the embodiments set forth herein.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of an OBD terminal or an IoT terminal for collecting vehicle CAN data from OBD-II.

1, a terminal for collecting CAN data includes a vehicle communication unit 10, a power determination unit 20, a protocol determination unit 30, an operation, analysis and determination unit 40, a data base unit 50, A file storage unit 60, a file transfer unit 70, an external communication unit 80, and a display unit 90. The vehicle communication section 10 receives CAN data for communication control from the control elements of the vehicle. In one embodiment, the control components of the vehicle include a motor control unit (HMCU), a battery management system (BMS), an engine control unit (ECU), an electronic throttle control device (ETC), a torque control unit . Data from EMS (electronic engine control), SAS (side collision protection), ABS (antilock brake system), TPMS (tire air pressure monitoring system) and VDC (differential attitude control) can be collected from the engine control unit (ECU) .

The power judgment unit 20 judges whether the voltage of the vehicle is 12V or 24V. If the voltage is 12V, it is classified as a commercial vehicle when the vehicle is 24V.

The protocol determination unit 30 determines which signal protocol is implemented in the OBD II interface installed in the vehicle. The protocol types are SAE J1850 pulse-width modulation (PWM), which is standard in Ford, SAE J1850 variable pulse width (VPM) standard in general motors, ISO 9141-2, ISO 14230 (KWP2000 ), And ISO 15765 CAN developed by Bosch. J1939 is a data protocol for medium commercial vehicles. They are used in large trucks, tractors, trailers, and large buses.

The operation and analysis determination unit 40 collects CAN data through the vehicle communication unit 10, generates a CAN data file, and performs calculation and analysis based on the data of the database unit 50. The file storage unit 60 updates the data stored in the database unit 50 after the data analyzed and determined by the operation and analysis determination unit 40 is updated data. The database unit 50 stores the previously constructed data and the data basically provided in the vehicle. Based on the information preliminarily stored in the database unit 50, it is possible to know the fluctuation range of the values between the main CAN data having an association with the change of the main CAN data values. Thus, it is possible to grasp the predicted value of change of the CAN data having a correlation with the change of the main CAN data value. For example, values such as RPM of the engine, battery voltage, and coolant temperature can be grasped according to the change of the running speed of the automobile.

The file transfer unit 70 transfers the updated CAN data in the file storage unit 60 to the external communication unit 80 for telematics using the database unit 50 and OBD-II and CAN.

The external communication unit 80 can communicate with the management server by communication means such as Bluetooth.

The display unit 90 displays necessary information on the screen of the terminal based on the analysis result of the calculation and analysis determination unit 40. The display unit can display various information according to the driver's command or the key input data, and can display a combination of these information.

The terminal of the present invention receives and transmits data obtained from the OBD-II connected by the CAN and the ECU by the application installed therein, analyzes and determines the data, and displays the data so that the user can easily view the data.

The terminal of the present invention includes an application to operate the aforementioned components organically. The application includes a communication module, a determination module, a file management module, a security module, and a display control module. The communication module communicates with a scanner or connector for collecting data from the OBD-II and communicates with the external management server. The determination module, the power determination unit, the protocol determination unit, the calculation and the analysis determination unit accurately determine and analyze the information of the corresponding vehicle. The file management module creates, compares, and stores the acquired data in a file format. The security module includes an authentication technique to prevent external hacking and other access of the terminal. The display control module selectively outputs information on the terminal screen according to the driver's needs based on the analysis result of the determination module.

2 is a flowchart of an operation procedure of a terminal according to the present invention.

The process proceeds from the start step to the start-on step of the next vehicle. In the start-up phase of the vehicle, when the driver drives the vehicle with the key, various sensors installed in the vehicle are operated by the engine and signals are transmitted from the various components provided in the vehicle to the ECU.

Vehicle data using OBD-II, which exchanges data with ECU and CAN communication, can be used for OBD Pico and VID 740, which are commercially available from SEKO Interface Co., Ltd., the applicant, to obtain basic data. Basic data refers to data that can be collected by all OBD-II connectors or scanners, regardless of the vehicle type. The existing data includes the voltage of the vehicle, the kind of the protocol, and the like.

In the next voltage step, if the voltage data obtained from the connector or scanner is 12V, it is resumed to commercial vehicle if it is 24V for passenger vehicle.

Voltage Signaling Phase The following protocol analysis phase analyzes what OBD II signaling protocol is implemented in the vehicle. The protocol can be inferred based on data from the connector or the scanner.

The next step is to acquire the corresponding vehicle data from the OBD-II by converting the application in accordance with the protocol implemented in the vehicle as the data acquisition step. The vehicle data includes all the data of the ECU. These data are used to calculate the remaining battery level, battery voltage information, tire pressure, used oil price, engine failure notification, oil consumption, travel speed / distance / time, coolant temperature, fuel / , A gear ratio, a diesel particulate filter (DPF), and the like.

It includes an operation step of calculating the data collected in the data acquisition step and converting it into information desired by the driver, and a storing step of storing the converted information. And a step of comparing and storing the existing stored information with the updated information at the computing and storing step. The history of this information will greatly assist in the maintenance of the vehicle.

Next, in the security module step, the driver has to access the terminal in order to view desired information in the terminal. Here, one or more authentication techniques required to authenticate a driver (user) are installed in an application so that only the corresponding driver can access the terminal and view necessary information. The terminal is then networked with the device, e.g., a management server, an insurance company server, a mechanic server, etc., in an external communication step of the next step. Sending this information directly to these servers without the driver's authorization results in the unauthorized use of personal information. Therefore, the security module step of authenticating the driver before display of the terminal and before connection with external communication is necessarily required. Authentication techniques may include passwords, fingerprinting, and biometric technologies.

3 is a flowchart of a data acquisition method showing in more detail the method shown in Fig.

(K-line communication), ISO O15765-4 (CAN communication), ISO 9141 (K-line communication), and the like, if the voltage data obtained from the connector or the scanner is 12V. ), And SAEJ1850 (PWM / VPWM communication). If one of them is selected, the application of the terminal corresponding to the protocol is selected and the data is acquired via the diagnostic filter. Next, if the voltage data obtained from the connector or the scanner is 24V, proceed to the commercial vehicle protocols J 1939 250K and J 1939 250K. If one of them is selected, the application of the terminal corresponding to the protocol is selected and then the data .

Finally, if the protocol is not found, the step of selecting the most suitable protocol among the installed protocols, the application of the terminal matching the protocol is selected, and the data is acquired through the diagnostic filter.

In the terminal of the present invention, the data obtained from all kinds of vehicles are classified and the corresponding applications are operated, so that any vehicle can be used in any vehicle Anyone can easily acquire data, display it in various forms for the convenience of the driver, store it, and transmit it to an external server.

In addition, the driver (user) receives signals from the sensors by the operation of the driver, processes the data in the terminal, and displays it or allows it to be displayed in combination with other data when there is a sensor of the device not associated with the ECU.

In this case, it is possible to install necessary sensors according to the driver's needs and to communicate with the terminal to obtain necessary information. For example, in the event of a breakdown of a brake or the like, the driver must observe the brake or the like while operating the brake, which is impossible and needs assistance from another person. In this case, it is possible to install a sensor on both brakes or the like to confirm whether there is an abnormality such as a brake through the terminal. Additional applications are installed that automatically detect when the sensor is installed. And if the sensor receives a certain signal, it indicates normal operation. If another signal comes, it indicates that it is abnormal.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. Which will be apparent to those skilled in the art to which the present invention pertains. Accordingly, the true scope of the present invention should be determined only by the appended claims.

10: vehicle communication unit 20:
30: protocol determination unit 40: calculation, analysis determination unit
50: Database part 60: File storage part
70: File transfer unit 80: External communication unit
90:

Claims (9)

As an automatic vehicle CAN data acquisition terminal using OBD-II,
The terminal includes a vehicle communication unit (10) for receiving CAN data for communication control from control components of the vehicle,
A power determination unit 20 for determining whether the voltage of the vehicle is 12 V or 24 V,
A protocol determination unit 30 for determining which signal protocol is implemented in the OBD II interface installed in the vehicle,
An analysis and determination unit 40 for collecting CAN data through the vehicle communication unit 10 to generate a CAN data file and for calculating and analyzing based on data of the database unit 50,
A base unit 50 for storing pre-built data and data basically provided in the vehicle,
A file storage unit 60 for generating CAN data into a file,
A file transfer unit 70 for transferring the updated CAN data in the file storage unit 60 to the external communication unit 80 for the telematics using the database unit 50, OBD-II and CAN,
An external communication unit 80 capable of communicating with the management server by communication means such as Bluetooth,
And a display unit 90 for displaying necessary information on the screen of the terminal based on the analysis result of the operation and analysis determining unit 40 and selecting and displaying various information according to the electronic command or key input data. Automobile CAN data collection terminal using II. The method according to claim 1,
The control components of the vehicle include a motor control unit (HMCU), a battery management system (BMS), an engine control unit (ECU), an electronic throttle control device (ETC), a torque control unit (TCU) Which can collect data from EMS (Electronic Engine Control), SAS (Side Impact Protection), ABS (Antilock Brake System), TPMS (Tire Air Pressure Monitoring System) and VDC Automatically collecting vehicle CAN data using Ⅱ. The method according to claim 1,
A communication module communicating with a scanner or a connector for collecting data from OBD-II and communicating with an external management server,
A determination module for accurately determining and analyzing information of the vehicle in the power determination unit, the protocol determination unit, the calculation and analysis determination unit,
A file management module for generating, comparing and storing the acquired data in a file format,
A security module for preventing external hacking and other persons from accessing the terminal,
And a display control module for selectively outputting information according to a driver's need on the terminal screen based on the analysis result of the determination module. As an automatic vehicle CAN data collection method using OBD-II,
A start-on step of transmitting various signals from various components installed in the vehicle to the ECU when the driver turns the vehicle on,
If the voltage data obtained from the connector or the scanner is 12V, if the voltage is 24V for the passenger vehicle,
A protocol analysis step of analyzing which OBD II signal protocol is implemented in the vehicle by inferring the protocol based on the data from the connector or the scanner,
A data acquiring step of acquiring the vehicle data from the OBD-II after the application is converted according to a protocol implemented in the vehicle,
An operation step of calculating data collected in the data acquisition step and converting the data into information desired by the driver, a storage step of storing the converted information,
A security step of authenticating by a user's authentication technology,
And an external communication connection step of connecting the generated file based on the data collected to the external management server to the network, using the OBD-II. 5. The method of claim 4,
The information obtained from the data includes information such as vehicle battery level, battery voltage information, tire air pressure, fuel consumption rate, engine failure notification, oil consumption, running speed / distance / time, coolant temperature, fuel cut / , The remaining flow rate, the gear ratio, and the diesel particulate filter (DPF). 5. The method of claim 4,
Wherein the calculating and storing step comprises comparing the stored information with the updated information and storing the same. 5. The method of claim 4,
First, if the voltage data obtained from the connector or scanner is 12V, the ISISO O14230 (K-line communication), ISO O15765-4 (CAN communication), ISO 9141 (K-line communication), SAEJ1850 / VPWM communication). If one of them is selected, the application of the terminal corresponding to the protocol is selected and the data is acquired via the next diagnostic filter,
If the voltage data obtained from the connector or the scanner is 24V, the process proceeds to commercial vehicle protocols J 1939 250K and J 1939 250K. If one of them is selected, the application of the terminal corresponding to the protocol is selected and then the data is acquired through the diagnostic filter And selecting the most suitable protocol among the installed protocols when the corresponding protocol is not found and selecting the application of the terminal matching the protocol and acquiring the data through the next diagnostic filter , Automated CAN data collection method using OBD-II. 5. The method of claim 4,
Comprising the steps of: receiving a signal from a sensor by an operation of a driver and processing the data in the terminal so that it can be displayed or displayed in combination with other data when there is a sensor of the device not associated with the ECU; Automated CAN Data Acquisition Method Using. The method of claim 3,
Wherein the application comprises a module for receiving signals from a sensor by operation of a driver and processing data in the terminal to display it or to display it in combination with other data when there is a sensor of the device not associated with the ECU, OBD-Ⅱ is used to automatically collect car CAN data.

Images