KR20130021652A - Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol - Google Patents

Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol Download PDF

Info

Publication number
KR20130021652A
KR20130021652A KR1020110084051A KR20110084051A KR20130021652A KR 20130021652 A KR20130021652 A KR 20130021652A KR 1020110084051 A KR1020110084051 A KR 1020110084051A KR 20110084051 A KR20110084051 A KR 20110084051A KR 20130021652 A KR20130021652 A KR 20130021652A
Authority
KR
South Korea
Prior art keywords
data
vehicle
frame
converting
diagnosing
Prior art date
Application number
KR1020110084051A
Other languages
Korean (ko)
Inventor
이장용
Original Assignee
현대자동차주식회사
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 현대자동차주식회사 filed Critical 현대자동차주식회사
Priority to KR1020110084051A priority Critical patent/KR20130021652A/en
Publication of KR20130021652A publication Critical patent/KR20130021652A/en

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
    • B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W30/00—Purposes of road vehicle drive control systems not related to the control of a particular sub-unit, e.g. of systems using conjoint control of vehicle sub-units, or advanced driver assistance systems for ensuring comfort, stability and safety or drive control systems for propelling or retarding the vehicle
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
    • F02D—CONTROLLING COMBUSTION ENGINES
    • F02D45/00—Electrical control not provided for in groups F02D41/00 - F02D43/00
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
    • G01M17/00—Testing of vehicles
    • G01M17/007—Wheeled or endless-tracked vehicles

Abstract

PURPOSE: An interface device converting a plurality of vehicle diagnosing protocols which are mutually different into a standard diagnosing protocol and a method thereof are provided to apply a standard format with respect to the various diagnosing protocols and improve a diagnosing program of a commercial vehicle, thereby reducing costs required for developing a vehicle diagnosing device and EOL(End Of Life) equipment. CONSTITUTION: An interface device converting a plurality of vehicle diagnosing protocols which are mutually different into a standard diagnosing protocol comprises an input unit(210), a converting unit(230), and an output unit(250). The input unit receives vehicle data from an electronic controller mounted inside a vehicle or receives diagnosing data from a vehicle diagnosing device diagnosing a vehicle condition based on the vehicle data. The converting unit converts the vehicle data into a standard format which is defined in advance or the diagnosing data into the standard format. The output unit transmits the converted vehicle data or diagnosing data to the electronic controller or the vehicle diagnosing device. [Reference numerals] (200) Interface device; (210) Input unit; (230) Converting unit; (231) Header converting module; (233) Data converting module; (235) Frame processing module; (250) Output unit; (270) Protocol information; (290) Vehicle model information

Description

Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol}

The present invention relates to an interface device and method for converting a plurality of different vehicle diagnostic protocols into a standard diagnostic protocol.

Currently, commercial vehicle diagnostic protocols include ISO 15765, ISO 14230, ISO 9141, and J1939. As such, different diagnostic protocols are used by different companies. Therefore, programs corresponding to each protocol should be developed. As a result, there is a problem that the cost increases due to an increase in development cost and development period. In addition, it is difficult to secure the initial quality due to difficulty in supplying the diagnostic program in a timely manner.

In addition, in case of overseas companies, security and productivity can be secured by using a self-diagnosis protocol, but development period and cost increase.

As such, although conventional diagnostic protocols exist, the absence of standard diagnostic protocols is a problem.

In addition, in the conventional end of line (EOL) process, the protocol is different for each ECU (Electronic Central Unit), such as ISO 15765, ISO 14230, ISO 9141, and many key on / off iterations instead of the module input BATCH method. It's serial.

Therefore, a relatively large amount of time is required for serial data input. In addition, if there is an error in the previous process, it causes a delay in the next process, there is a problem of inefficient use of the bandwidth, and it requires a company response schedule and additional development cost. As such, the work time due to individual input in the EOL process decreases production efficiency.

In addition, many new technology systems (AEBS, livestock monitoring, SMK, BSD, etc.) will be applied to new vehicle developments (ex. QZ heavy truck FMC). As a result, the inefficiency of the process time can be further highlighted.

Accordingly, an object of the present invention is to provide an interface device and method for converting a plurality of diagnostic protocols into a standard format.

According to one aspect of the invention there is provided an interface device. The apparatus may include an input unit configured to receive vehicle data from an electronic controller mounted in a vehicle or to receive diagnostic data from a vehicle diagnostic apparatus for diagnosing a vehicle state based on the vehicle data; A converting unit converting the vehicle data into a predefined standard format or converting the diagnostic data into the standard format; And an output unit for transmitting the vehicle data or the diagnostic data converted into the standard format to the electronic controller or the vehicle diagnostic device.

According to another feature of the invention there is provided a conversion method. This method is a method for converting data received by an electronic controller mounted in a vehicle or an interface device connected to a vehicle diagnostic device for diagnosing a vehicle state. Receiving an input; Converting the data into a predefined standard format; And outputting the data converted into the standard format to the electronic controller or the vehicle diagnostic device.

According to an embodiment of the present invention, by applying a standard format for a variety of diagnostic protocols used by each company to improve the efficiency of the diagnostic program of the commercial vehicle to facilitate the cost and development response in the development of vehicle diagnostics and EOL equipment.

In addition, the EOL process time can be shortened.

1 is a conversion diagram of a vehicle diagnostic protocol according to an embodiment of the present invention.
2 is a conceptual diagram illustrating an implementation structure of a conversion function of an interface device according to an embodiment of the present invention.
3 is a conceptual diagram illustrating a flow of a conversion function of an interface device according to an embodiment of the present invention.
4 is a block diagram showing a detailed configuration of an interface device according to an embodiment of the present invention.
5A and 5B are flowcharts illustrating a series of processes of a diagnostic protocol conversion method according to an embodiment of the present invention.
6 shows a frame structure according to an embodiment of the present invention.
7 shows a standard structure through J2534-1 API analysis to which an embodiment of the present invention is applied.
8 shows a standard structure according to an embodiment of the invention.
9 shows a structure of a data field according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and like reference numerals designate like parts throughout the specification.

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise.

Hereinafter, an interface device and a method for converting a plurality of different vehicle diagnostic protocols into a standard diagnostic protocol according to an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

1 is a conversion diagram of a vehicle diagnostic protocol according to an embodiment of the present invention.

Referring to FIG. 1, a vehicle electronic controller 100 using different vehicle diagnostic protocols is connected to an interface device 200, and the interface device 200 uses a vehicle diagnostic device 300 using another vehicle diagnostic protocol. ).

Here, the vehicle electronic controller 100 controls the engine and various devices of the vehicle, extracts the data of the vehicle from the vehicle, and transmits the vehicle data to the interface device 200 using a predefined vehicle diagnostic protocol.

In this case, the vehicle electronic controller 100 may use one of three types of communication protocols as a protocol of a physical layer. Here, the communication protocol may include a controller area network (CAN), a K-line on keyword (KWP), and a K-line.

In addition, the vehicle electronic controller 100 may use a plurality of different diagnostic protocols, respectively, as an application layer protocol, and the plurality of diagnostic protocols include ISO 15765, ISO 14230, ISO 9141, J1939, and the like.

Meanwhile, the vehicle diagnostic apparatus 300 is installed at a location remote from the electronic controller to analyze vehicle data received from the electronic controller.

 Like the vehicle electronic controller 100, the vehicle diagnostic apparatus 300 may use one of a communication protocol of a controller area network (CAN), a K-line on keyword (KWP), and a K-line as a protocol of a physical layer. In addition, one of the diagnostic protocols, such as ISO 15765, ISO 14230, ISO 9141, J1939, may be used as the protocol of the application layer.

On the other hand, the interface device 200 converts the vehicle diagnostic protocol of the vehicle electronic controller 100 and the vehicle diagnostic apparatus 300 into a predefined standard format. That is, the input data according to the vehicle diagnostic protocol of the vehicle electronic controller 100 or the input data according to the vehicle diagnostic protocol of the vehicle diagnostic apparatus 300 are converted into a standard format and output.

In this case, the interface device 200 uses the conversion of ISO 15765 ↔ ISO 14230 with the highest frequency of use.

Here, the functions of the interface device 200 will be described with reference to FIGS. 2 and 3 as follows.

First, FIG. 2 is a conceptual diagram illustrating an implementation structure of a conversion function of an interface device according to an embodiment of the present invention.

Referring to FIG. 2, a driver class may be composed of a K-line driver class, a CAN driver class, and a TCP driver class according to the type of communication protocol. Each driver class is associated with a Protocol Transform program, which is associated with a BufferedQueue Class. The buffer queue class consists of a receive queue and a transmit queue.

At this time, the diagnostic transform algorithm (TransformWork) class converts data input to the interface in the standby state, that is, data stored in the reception queue, and outputs one of the corresponding output interfaces, that is, each driver class, through the transmission queue.

3 is a conceptual diagram illustrating a flow of a conversion function of an interface device according to an embodiment of the present invention.

Referring to FIG. 3, the conversion program of the interface device 200 receives data from a device using respective communication protocols through K-line, CAN, and TCP sockets.

When such data is stored in the input queue, it is converted into a standard format predefined by a conversion algorithm and transferred to the output queue, and the data stored in the output queue is output through K-line or CAN communication.

The interface device 200 may have a detailed configuration as shown in FIG. 4.

4 is a block diagram showing a detailed configuration of an interface device according to an embodiment of the present invention.

Referring to FIG. 4, the interface device 200 includes an input unit 210, a converter 230, an output unit 250, a protocol information DB 270, and a vehicle model information DB 290.

The input unit 210 receives vehicle data from the electronic controller 100 mounted in the vehicle, or receives diagnostic data from the vehicle diagnostic apparatus 300 for diagnosing a vehicle state based on the vehicle data.

The conversion unit 230 converts the vehicle data into a predefined standard format or the diagnostic data into a standard format.

The output unit 250 outputs the vehicle data or the diagnostic data converted into the standard format to the electronic controller 100 or the vehicle diagnostic apparatus 300.

The protocol information DB 270 stores each protocol information used by the in-vehicle electronic controller 100.

The vehicle model information DB 290 stores the type of vehicle.

In this case, the conversion unit 230 includes a header conversion module 231, a data conversion module 233, and a frame processing module 235.

Here, the header conversion module 231 converts the frame header based on the protocol in cooperation with the protocol information DB 270.

In addition, the data conversion module 233 works with the vehicle model information DB 290 to convert the frame data based on the ECU information.

In addition, the frame processing module 235 processes the timing and response frame in cooperation with the protocol information DB 270.

Meanwhile, although not shown in the drawing, the interface device 200 may further include a gateway unit. When the gateway unit receives all the items of the end of line (EOL) from the engine automatic diagnosis system (HADS) equipment, the gateway unit inputs them in parallel to each electronic controller (ECU). Alternatively, when the EOL information is input in parallel for each protocol of the electronic controller (ECU) in the HADS device, the filter is input to each electronic controller (ECU).

Next, a conversion operation of the interface device 200 will be described with reference to FIGS. 5 to 9.

5A and 5B are flowcharts illustrating a series of procedures of a method for converting a diagnostic protocol according to an embodiment of the present invention, FIG. 6 is a frame structure according to an embodiment of the present invention, and FIG. 7 is an embodiment of the present invention. FIG. 8 illustrates a standard structure through J2534-1 API analysis, FIG. 8 illustrates a standard structure according to an embodiment of the present invention, and FIG. 9 illustrates a structure of a data field according to an embodiment of the present invention.

First, referring to FIG. 5A, when data is input from the vehicle electronic controller 100 or the vehicle diagnostic apparatus 300 (S101), the header conversion module 231 analyzes the FMT field (S103).

Here, the data frame includes a header field, a data field, and a checksum field as shown in FIG. 6.

In this case, the header field may consist of a maximum of 4 bytes, and may include an FMT field, a target (Tgt) address field, a source (Src) address field, and a length (Len) field.

Here, the target (Tgt) address field and the source (Src) address field are optional fields for multinode connection.

The FMT header field defines the content to be output and the character format, and specifies the sorting method of the string and whether to use the image. The 'Format Byte' includes A1, A0, L5, L4, L3, L2, L1, L0. do.

At this time, A1 and A0 define the form of the header to be used in the message. In addition, L5, L4, L3, L2, L1, L0 define the length of the message from SID to checksum byte.

The Data field is a field in which data is stored. The data field is composed of SID and data and has a maximum of 255 bytes.

In addition, the checksum field is one byte.

5, when A1 = 1 and A0 = 0 of the FMT field, the header conversion module 231 operates in the physical addressing mode and the header conversion module 231 performs the FMT field and the target address field. And check the data in the source address field (S107).

Further, when A1 = 0 and A0 = 0 of the FMT field, the header conversion module 231 checks the data in the FMT field in the header field (S109).

In addition, the header conversion module 231 confirms the checksum (S111), and if all errors are detected, ends all steps, but generates an predefined standard structure if no error is detected (S115).

In this case, the structure is one of the ways in which the user can define a data type in the C language. The structure is a compound data type that groups variables by a single name.

The header conversion module 231 forms the structure in a standardized format. Referring to FIG. 7, the header conversion module 231 represents a standard structure through J2534-1 API analysis, and the standard structure is defined as shown in FIG.

Here, according to FIG. 7, the standard structure includes a protocol ID, RxStatus, TxFlags, TimeStamp, DataSize, ExtraDataIndex, and Data.

8, the standard structure may be defined to include an input / output physical protocol ID, a protocol ID of an input / output application layer, a DLC, a header, and a data field.

In this case, the header conversion module 231 may generate the protocol ID of the standard structure of FIG. 8 by referring to the information stored in the protocol information DB 270.

The header conversion module 231 transmits the standard structure to the input queue (S117).

Then, the header conversion module 231 determines whether the data length code (DLC) is less than eight (S119). The DLC field represents the number of bytes of the data field, and the data field is composed of 0 to 8 bytes.

At this time, the header conversion module 231 generates a single frame when the DLC is less than 8 (S121), and generates a multiframe when the DLC is not less than 8 (S123).

Here, referring to FIG. 9, the data field of the CAN frame is 8 bytes, the CAN identifier is N_Al, and the network protocol data unit (N_PDU) type (Type) of the network layer is a single frame ( Single Frame (SF), First Frame (FF), Continuous Frame (ConsecutiveFrame (CF)), and Flow Control (FlowControl, FC).

At this time, the single frame SF is composed of 1 byte of N_PCI (Network Protocol Control Information) and 7 bytes of data.

In addition, the multi-frame is composed of a first frame (FF) and a continuous frame (CF), the first frame (FF) is composed of two bytes of N_PCI and 6 bytes of data. The continuous frame CF is composed of one byte of N_PCI and seven bytes of data.

Meanwhile, referring to FIG. 5B, the header conversion module 231 inputs header information and address information (S125 and S127), respectively, and determines whether ARR_Num = 1 (S129). That is, it is determined whether the frame is a single frame or a multi frame.

In this case, when ARR_Num = 1, PCI = DLC is generated as 1 byte (S131). When ARR_Num = 1, when PCI is 2 bytes DLC in FF, PCI is generated as 1 byte in SFF (S133). .

The SID (Symbolic IDentifier) is converted (S135).

Then, the data conversion data conversion module 233 inputs the data field (S137) and transmits the converted data to the output queue (S139).

In this case, the frame processing module 235 determines whether the output interface is K-Line or CAN (S141), and if it is K-Line, transmits the converted data to the K-Line queue (S143). In addition, in the case of CAN, the converted data is transmitted to the CAN queue (S145).

The output unit 250 transmits the data transmitted to the K-Line queue or the CAN queue to the corresponding device, that is, the electronic controller 100 or the vehicle diagnostic apparatus 300 (S147).

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, It belongs to the scope of right.

Claims (13)

An input unit configured to receive vehicle data from an on-vehicle electronic controller or to receive diagnostic data from a vehicle diagnostic apparatus for diagnosing a vehicle state based on the vehicle data;
A converting unit converting the vehicle data into a predefined standard format or converting the diagnostic data into the standard format; And
Output unit for transmitting the vehicle data or the diagnostic data converted to the standard format to the electronic controller or the vehicle diagnostic device
Lt; / RTI > The method of claim 1,
Wherein,
A header conversion module for converting a frame header based on a protocol used by the electronic controller or a protocol used by the vehicle diagnostic apparatus;
A data conversion module for converting frame data based on the vehicle model information of the vehicle; And
A frame processing module that performs frame processing based on the protocol
Interface device comprising a. The method of claim 2,
The header conversion module,
Analyzes the FMT field among the header fields of the input data to determine whether to apply the physical address mode or the non-address mode to the header field.If no error is detected, a predefined standard structure is generated to generate the header information and the address information. Interface device for converting into SID (Silence InDicator frame) frame after inputting. The method of claim 3,
The header conversion module,
And generating a single frame when the DLC (Data Length Code) is smaller than 8 bytes, and generating the multi frame when not smaller than 8, and inputting the header information and the address information to each frame. 5. The method according to any one of claims 1 to 4,
Wherein the input unit comprises:
Interface device that receives data through K-Line communication, CAN communication, and Socket communication. 5. The method according to any one of claims 1 to 4,
The output unit includes:
Interface device for transmitting data via K-Line communication or CAN communication. A method for converting data received by an interface device connected to an on-vehicle electronic controller or a vehicle diagnostic device for diagnosing a vehicle state,
Receiving data from an on-vehicle electronic controller or a vehicle diagnostic device for diagnosing a vehicle state;
Converting the data into a predefined standard format; And
Outputting the data converted into the standard format to the electronic controller or the vehicle diagnostic device.
Conversion method comprising a. The method of claim 7, wherein
Wherein the converting comprises:
Converting a frame header of the data based on a protocol used by the electronic controller or a protocol used by the vehicle diagnostic device;
Converting frame data of the data based on vehicle model information of the vehicle; And
Performing frame processing based on the protocol
Conversion method comprising a. 9. The method of claim 8,
Converting the header,
Analyzing the FMT field of the input data;
Determining whether bit information defining a header form in the FMT field indicates a physical address mode or a non-address mode, and checking a checksum to generate a predefined standard structure if an error is not detected; And
Enter header and address information
Conversion method comprising a. 10. The method of claim 9,
Between the generating and the inputting
Determining whether a data length code (DLC) is less than eight;
If small, generating a single frame; And
Generating a multi-frame if large;
The input step,
And converting the header information and the address information into the single frame or the multi-frame. The method of claim 10,
After the input step,
In case of the single frame, PCI (Protocol Control Information) to match the size of the DLC;
Setting the PCI of the first frame and the PCI of the continuous frame to a predefined size in the multi-frame;
Converting the single frame or the multi-frame to a Silence InDicator frame
Conversion method comprising more. The method of claim 11,
After converting to the SID frame,
Inputting data input from the electronic controller or the vehicle diagnostic apparatus into a data field;
Conversion method comprising more. 13. The method according to any one of claims 7 to 12,
The outputting step,
Conversion method that outputs the converted data through K-Line communication or CAN communication.
KR1020110084051A 2011-08-23 2011-08-23 Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol KR20130021652A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020110084051A KR20130021652A (en) 2011-08-23 2011-08-23 Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020110084051A KR20130021652A (en) 2011-08-23 2011-08-23 Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol

Publications (1)

Publication Number Publication Date
KR20130021652A true KR20130021652A (en) 2013-03-06

Family

ID=48174471

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020110084051A KR20130021652A (en) 2011-08-23 2011-08-23 Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol

Country Status (1)

Country Link
KR (1) KR20130021652A (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101491622B1 (en) * 2014-02-17 2015-02-11 연세대학교 산학협력단 Apparatus and method for driving control of self-driving vehicle
CN104865950A (en) * 2014-02-21 2015-08-26 现代自动车株式会社 Method and apparatus for checking vehicle specificatio
WO2016130446A1 (en) * 2015-02-09 2016-08-18 General Electric Company Protocol conversion system and method for a vehicle system
CN106043160A (en) * 2015-04-08 2016-10-26 罗伯特·博世有限公司 Method for operating electrified motor vehicle
CN106406271A (en) * 2016-05-13 2017-02-15 深圳市元征科技股份有限公司 Automobile offline detection system and method
CN108255160A (en) * 2018-03-12 2018-07-06 深圳市博诺技术有限公司 The automobile bus communication wire selection system and method for a kind of 38PIN interfaces
CN111552274A (en) * 2018-01-08 2020-08-18 深圳市道通科技股份有限公司 Automobile diagnosis method, device, equipment, system and diagnosis connecting equipment
CN112068536A (en) * 2020-09-29 2020-12-11 爱动超越人工智能科技（北京）有限责任公司 Universal self-adaptive vehicle remote diagnosis method, device and system
CN112254983A (en) * 2020-10-16 2021-01-22 中国第一汽车股份有限公司 Vehicle detection method, device, equipment and storage medium
CN115022414A (en) * 2022-04-20 2022-09-06 华东师范大学 CAN ID reverse direction and determination method for vehicle electronic control unit
US20230350406A1 (en) * 2015-08-05 2023-11-02 EZ Lynk SEZC System and method for remote emissions control unit monitoring and reprogramming

Cited By (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9360867B2 (en) 2014-02-17 2016-06-07 Industry-Academic Cooperation Foundation, Yonsei University Apparatus and method for controlling driving device of self-driving vehicle
KR101491622B1 (en) * 2014-02-17 2015-02-11 연세대학교 산학협력단 Apparatus and method for driving control of self-driving vehicle
US9514579B2 (en) 2014-02-21 2016-12-06 Hyundai Motor Company Method and apparatus for checking vehicle specification
CN104865950A (en) * 2014-02-21 2015-08-26 现代自动车株式会社 Method and apparatus for checking vehicle specificatio
WO2016130446A1 (en) * 2015-02-09 2016-08-18 General Electric Company Protocol conversion system and method for a vehicle system
US9426224B1 (en) 2015-02-09 2016-08-23 General Electric Company Protocol conversion system and method for a vehicle system
CN106043160B (en) * 2015-04-08 2021-02-19 罗伯特·博世有限公司 Method for operating an electrified motor vehicle
CN106043160A (en) * 2015-04-08 2016-10-26 罗伯特·博世有限公司 Method for operating electrified motor vehicle
US20230350406A1 (en) * 2015-08-05 2023-11-02 EZ Lynk SEZC System and method for remote emissions control unit monitoring and reprogramming
CN106406271A (en) * 2016-05-13 2017-02-15 深圳市元征科技股份有限公司 Automobile offline detection system and method
CN111552274A (en) * 2018-01-08 2020-08-18 深圳市道通科技股份有限公司 Automobile diagnosis method, device, equipment, system and diagnosis connecting equipment
CN108255160A (en) * 2018-03-12 2018-07-06 深圳市博诺技术有限公司 The automobile bus communication wire selection system and method for a kind of 38PIN interfaces
CN108255160B (en) * 2018-03-12 2023-09-08 深圳市博诺技术有限公司 38PIN interface automobile bus communication line selection system and method
CN112068536A (en) * 2020-09-29 2020-12-11 爱动超越人工智能科技（北京）有限责任公司 Universal self-adaptive vehicle remote diagnosis method, device and system
CN112254983A (en) * 2020-10-16 2021-01-22 中国第一汽车股份有限公司 Vehicle detection method, device, equipment and storage medium
CN115022414A (en) * 2022-04-20 2022-09-06 华东师范大学 CAN ID reverse direction and determination method for vehicle electronic control unit
CN115022414B (en) * 2022-04-20 2023-08-22 华东师范大学 CAN ID reverse and determining method for vehicle electronic control unit

Similar Documents

Publication Publication Date Title
KR20130021652A (en) Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol
EP3402128B1 (en) Abnormality detection method, abnormality detection device, and abnormality detection system
US9305408B2 (en) Multiple electronic control unit diagnosing system and method for vehicle
US6360145B1 (en) Vehicle platform-portable controller
US9160620B2 (en) Integrated fault diagnosis and prognosis for in-vehicle communications
US8983714B2 (en) Failsafe communication system and method
EP3230960A1 (en) Remote vehicle data collection system
CN109491357A (en) Equipment that diagnostic operation is executed on multiple controllers and associated method and vehicle
CN111447128A (en) Vehicle data acquisition and uploading method capable of being remotely and dynamically configured and storage medium
KR101855753B1 (en) Gateway apparatus for vehicles diagnosis and system having the same
WO2013184117A1 (en) Message tunneling in industrial networks
CN111506047B (en) Vehicle diagnosis method, device and storage medium
CN113014464A (en) Abnormality detection method, abnormality detection device, and abnormality detection system
CN110908363A (en) Data acquisition method and device for vehicle-mounted terminal
WO2018196655A1 (en) Public network communication method for on-board electronic processing unit system
CN111427321B (en) Multi-protocol compatible MES data acquisition system and method thereof
CN106850419A (en) Car borne gateway and the method for car borne gateway
CN111443691A (en) Intelligent online diagnosis method and device for automobile
CN112764410B (en) Vehicle-mounted controller testing device, system and method
CN115391422B (en) Vehicle perception information generation method, device, equipment, medium and program product
CN111552268B (en) Vehicle remote diagnosis method, equipment connector and vehicle connector
CN113672478A (en) Log obtaining method, device, terminal, server and storage medium
Dekanic et al. Integration of CAN bus drivers and UDS on Aurix platform
KR101704300B1 (en) Method for transmitting/receiving can message and system performing the same
CN103532686A (en) Serial data transceiver circuit with line sequence self-adaptive function, and control method thereof

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E601 Decision to refuse application