CN109088807A - Based on CAN network vehicle protocol API development system - Google Patents
Based on CAN network vehicle protocol API development system Download PDFInfo
- Publication number
- CN109088807A CN109088807A CN201810999090.8A CN201810999090A CN109088807A CN 109088807 A CN109088807 A CN 109088807A CN 201810999090 A CN201810999090 A CN 201810999090A CN 109088807 A CN109088807 A CN 109088807A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- development system
- detection
- data
- obd
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40208—Bus networks characterized by the use of a particular bus standard
- H04L2012/40215—Controller Area Network CAN
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40267—Bus for use in transportation systems
- H04L2012/40273—Bus for use in transportation systems the transportation system being a vehicle
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
Based on CAN network vehicle protocol API development system.The detection of this system first step starts, and second step initializes CAN, and third step instruction is sent, and the 4th step data parsing, the 5th step detection is completed.The present invention is used for vehicle protocol API development system.
Description
Technical field:
The present invention relates to one kind to be based on CAN network vehicle protocol API development system.
Background technique:
From the 1980s, major automobile manufacturing enterprise such as beauty, day, Europe starts to be equipped on the electro jet car of its production
The OBD of OBD, initial stage do not have self-checking function.OBD- II more more advanced than OBD is generated in mid-term the 1990s, american car
Association of Engineers (SAE) has formulated a set of standard criterion, it is desirable that each automobile manufacturing enterprise provides unified according to the standard of OBD- II
Diagnostic mode, in latter stage 90 year 20th century, OBD is arranged all in accordance with new standard in the automobile into North America market.
Vehicle diagnostic device is a special instrument specifically for automotive check, it can be achieved that detecting the performance of vehicle, and right
The failure of vehicle is detected, and is a kind of tool of vehicle detection indispensability, and Auto analyzer currently on the market is divided into two classes, and one
Kind for controlling in car door, overhaul by the matching and test for mainly applying to automobile remote controllers；Another kind is directed to automobile engine
Or circuit fault diagnosis.This time invention is most of on current market just for automobile engine or circuit fault diagnosis
Diagnostic equipment only radiodiagnosis x under Automobile Service Factory or main engine plants' vehicle is used, need user very clear during use
Understanding vehicle details to be checked, such as engine manufacturer, engine model, the information such as brand styles of vehicle, certain vehicle
Relevant information for the people of Automobile Service personnel and main engine plants very it will be apparent that but vehicle is ignorant of for big department people come
It says, vehicle OBD diagnostic equipment is difficult have actual purposes.
The use of current diagnostic instrments most on the market is all under the vehicle shop specialized maintenance 4S or vehicle production
Line detection, which is equipped with, to be used, and needs when use to be manually entered or select vehicle manufacturers, vehicle motor manufacturer, vehicle
ECU manufacturer, some information that must select some laymans such as vehicle communication agreement that can not know.Such as detection people
Member be clearly understood that the communication protocol of vehicle to be checked is ISO 15765(250k), ISO 15765(500k), SAE J1939
Etc. information can just make to detect it is normal complete detection work, often can all be repeated when developing diagnostic equipment for a new model
The communication protocol of vehicle is dissolved into wherein be unfavorable for diagnostic equipment exploitation efficiency.
The prior art determines that main development efficiency is low, and the big collection of repeated workload, for protocol development, different people has not
Same view, so big to diagnostic equipment later period extension difficulty.
Summary of the invention:
The object of the present invention is to provide one kind only need to call api interface during diagnostic equipment is developed, and programmer need not
Consider vehicle protocol concrete principle based on CAN network vehicle protocol API development system.
Above-mentioned purpose is realized by following technical scheme:
One kind being based on CAN network vehicle protocol API development system, and first step detection starts, and second step initializes CAN, third step
Instruction is sent, and the 4th step data parsing, the 5th step detection is completed.
It is described based on CAN network vehicle protocol API development system, the first step detection be initially by collector with
The connection of vehicle OBD interface, and detection device is made to establish communication linkage by bluetooth or wifi.
It is described based on CAN network vehicle protocol API development system, the second step initialization CAN is detection device
By calling API initialization interface to initialize vehicle-mounted CAN network in order；What is called first is the first of ISO 15765
Beginningization interface, responds to ECU, if ECU does not provide response and illustrates the failure of this initializtion protocol, following program meeting
The automatic initialization interface for calling ISO 15765, and so on the initialization directive ECU that issues of guidance respond.
It is described based on CAN network vehicle protocol API development system, it is complete to second step that the third step instruction, which is sent,
At later, by sending instruction corresponding with second process, vehicle trouble code information, ready state information, IUPR letter are obtained
Breath, vehicle essential information and real-time acquisition automotive power information.
It is described based on CAN network vehicle protocol API development system, if the protocol information that second step matches is ISO
It when 15765, when receiving the data frame of ECU return, needs to judge the data frame format currently returned, judges whether to need
Splicing is wrapped, packet splicing api interface is called to carry out the splicing of data frame if necessary.
It is described based on CAN network vehicle protocol API development system, the 4th step data parsing is to complete third step
Later, the parsing of OBD data is done, the process of parsing is also the interface difference that point different agreement is called, and interface routine returns basis
Data packet is unpacked, data type judges, data conversion, formula calculate a series of logical process and finally obtain true OBD
Data.
It is described based on CAN network vehicle protocol API development system, the 5th step detection is completed to be detection completion
Afterwards, OBD is pulled out, an OBD detection is completed in pass hull closure connection.
The utility model has the advantages that
1. in order to allow it is most of be ignorant of vehicle or only understand vehicle sections information personnel and can also make vehicle to discharge relevant detection,
The present invention is integrated with big department's vehicle communication agreement on the market, and detector can be helped to use automatically when being connected to OBD interface
Person identifies information of vehicles, and detection work is completed and reminds whether testing staff's vehicle has the relevant failure of discharge；It is truly realized
At any time vehicle is detected over the ground, finds the problem solve the problems, such as in time；Also one clean atmosphere of the earth.
The present invention provides the exploitations of conveniently vehicle OBD checkout and diagnosis instrument to service, and is integrated with the logical of most of vehicle
Believe that agreement includes ISO 15765, SAE J1939,14230 ISO etc.；Api interface need to be only called during diagnostic equipment exploitation
, programmer need not consider the concrete principle of vehicle protocol.
3. the present invention discharges relevant diagnostic equipment about OBD to vehicle and greatly improves development efficiency, developer is simultaneously not required to
It is to be understood that how for a moment vehicle diagnostics agreement is thing, program development work directly can be carried out according to interface document, greatly shortened
Development cycle.
Api interface of the invention can become the development agreement frame of complete set, and it is flat can be transplanted to different exploitations
It is more convenient to use quick for different platform developer in platform.
Detailed description of the invention:
Attached drawing 1 is OBD diagnostic equipment work flow diagram of the invention.
Attached drawing 2 is program API service Interface Flowchart figure of the invention.
Specific embodiment:
Below in conjunction with attached drawing of the invention, technical scheme in the embodiment of the invention is clearly and completely described.
Embodiment 1:
One kind being based on CAN network vehicle protocol API development system, and first step detection starts, and second step initializes CAN, third step
Instruction is sent, and the 4th step data parsing, the 5th step detection is completed.
Embodiment 2:
Described in embodiment 1 to be based on CAN network vehicle protocol API development system, the first step detection is initially that will acquire
Device is connect with vehicle OBD interface, and detection device is made to establish communication linkage by bluetooth or wifi.
Embodiment 3:
Described in embodiment 1 to be based on CAN network vehicle protocol API development system, the second step initialization CAN is that detection is set
It is standby that vehicle-mounted CAN network is initialized by calling API initialization interface in order；That call first is ISO 15765
The initialization interface of (250K), responds to ECU, if ECU does not provide response and illustrates the failure of this initializtion protocol, connects
Program of getting off can call ISO 15765(500K automatically) initialization interface, and so on guidance issue initialization directive ECU
It responds.Due to the detection of laws and regulations requirement when OBD discharges relevant detection, thus must have a kind of initialization procedure meet to
Examine vehicle protocol.
Embodiment 4:
Described in embodiment 1 to be based on CAN network vehicle protocol API development system, it is to second that the third step instruction, which is sent,
After step is completed, by sending corresponding with second process instruction, acquisition vehicle trouble code information, ready state information,
IUPR information, vehicle essential information and real-time acquisition automotive power information.
Embodiment 5:
It is as described in example 4 to be based on CAN network vehicle protocol API development system, if the protocol information that second step matches is
When ISO 15765, when receiving the data frame of ECU return, need to judge the data frame format currently returned, judgement is
No needs packet splicing calls packet splicing api interface to carry out the splicing of data frame if necessary.
Embodiment 6:
Described in embodiment 1 to be based on CAN network vehicle protocol API development system, the described 4th step data parsing is completion the
After three steps, the parsing of OBD data is done, the process of parsing is also the interface difference that point different agreement is called, and interface routine returns
It is unpacked according to data packet, data type judgement, data conversion, formula calculate a series of logical process and finally obtain really
OBD data.
Embodiment 7:
Described in embodiment 1 to be based on CAN network vehicle protocol API development system, the 5th step detection is completed to be to have detected
At OBD later, is pulled out, an OBD detection is completed in pass hull closure connection.
Embodiment 8:
Based on CAN network vehicle protocol API development system described in above-described embodiment, vehicle OBD detection is first by customized
Communication protocol send API instruction interface arrive OBD collector, collector analyze the instruction and be packaged into standard agreement instruct pass through
Vehicle OBD interface is sent to specified automotive control system (this refers to vehicle electrically controlling unit ECU), and vehicle control system receives
According to instructing specific request content to be responded layer by layer according to original route to data after instruction, mobile device receives response data
It is called after parsing for other modules.
The present invention be directed in the above process api interface service realization, main operational principle is: mobile device or its
He replaces the detection device of mobile device, and more or directly api interface is embedded into OBD collector, passes through calling interface reality
The acquisition of existing data.
Claims (7)
1. one kind is based on CAN network vehicle protocol API development system, it is characterized in that: first step detection starts, second step is initial
Change CAN, third step instruction is sent, and the 4th step data parsing, the 5th step detection is completed.
2. according to claim 1 be based on CAN network vehicle protocol API development system, it is characterized in that: described first
Step detection is initially to connect collector with vehicle OBD interface, and detection device is made to establish communication chain by bluetooth or wifi
It connects.
3. according to claim 1 be based on CAN network vehicle protocol API development system, it is characterized in that: described second
Step initialization CAN is detection device by calling API initialization interface to initialize vehicle-mounted CAN network in order；First
What is called is the initialization interface of ISO 15765, is responded to ECU, if ECU does not provide response, explanation is this time initialized
Failure Of Protocol, following program can call the initialization interface of ISO 15765 automatically, and so on guidance issue initialization refer to
ECU is enabled to respond.
4. according to claim 1 be based on CAN network vehicle protocol API development system, it is characterized in that: the third
It is, by sending instruction corresponding with second process, to obtain vehicle trouble code letter after completing to second step that step instruction, which is sent,
Breath, ready state information, IUPR information, vehicle essential information and real-time acquisition automotive power information.
5. according to claim 4 be based on CAN network vehicle protocol API development system, it is characterized in that: if second step
When the protocol information mixed is ISO 15765, when receiving the data frame of ECU return, need to judge currently to return
Data frame format judges whether to need to wrap splicing, the splicing if necessary for calling packet splicing api interface to carry out data frame.
6. according to claim 1 be based on CAN network vehicle protocol API development system, it is characterized in that: the described the 4th
Step data parsing is to do the parsing of OBD data after completing third step, and the process of parsing is also connecing for point different agreements calling
It is mouthful different, interface routine return unpacked according to data packet, data type judgement, data conversion, a series of logics of formula calculating
Processing finally obtains true OBD data.
7. according to claim 1 be based on CAN network vehicle protocol API development system, it is characterized in that: the described the 5th
Step detection is completed to be to pull out OBD after detection is completed, and an OBD detection is completed in pass hull closure connection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810999090.8A CN109088807A (en) | 2018-08-30 | 2018-08-30 | Based on CAN network vehicle protocol API development system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810999090.8A CN109088807A (en) | 2018-08-30 | 2018-08-30 | Based on CAN network vehicle protocol API development system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109088807A true CN109088807A (en) | 2018-12-25 |
Family
ID=64795217
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810999090.8A Pending CN109088807A (en) | 2018-08-30 | 2018-08-30 | Based on CAN network vehicle protocol API development system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109088807A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377085A (en) * | 2021-06-29 | 2021-09-10 | 上海星融汽车科技有限公司 | Vehicle decoder communication parameter analysis system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202257264U (en) * | 2011-09-23 | 2012-05-30 | 深圳市迈纬汽车电子有限公司 | Vehicle bus network communication concentrator |
| CN104866947A (en) * | 2015-04-03 | 2015-08-26 | 深圳迪恩杰科技有限公司 | Vehicle-mounted intelligent online management system orienting 4S store vehicle owner services and method thereof |
| CN105242532A (en) * | 2015-08-20 | 2016-01-13 | 魏宇 | Adaptive protocol analysis method of car remote start control system |
| CN106371430A (en) * | 2016-11-17 | 2017-02-01 | 北京汽车股份有限公司 | Vehicle electronic control module configuration device and control method |
-
2018
- 2018-08-30 CN CN201810999090.8A patent/CN109088807A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN202257264U (en) * | 2011-09-23 | 2012-05-30 | 深圳市迈纬汽车电子有限公司 | Vehicle bus network communication concentrator |
| CN104866947A (en) * | 2015-04-03 | 2015-08-26 | 深圳迪恩杰科技有限公司 | Vehicle-mounted intelligent online management system orienting 4S store vehicle owner services and method thereof |
| CN105242532A (en) * | 2015-08-20 | 2016-01-13 | 魏宇 | Adaptive protocol analysis method of car remote start control system |
| CN106371430A (en) * | 2016-11-17 | 2017-02-01 | 北京汽车股份有限公司 | Vehicle electronic control module configuration device and control method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113377085A (en) * | 2021-06-29 | 2021-09-10 | 上海星融汽车科技有限公司 | Vehicle decoder communication parameter analysis system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Malekian et al. | Design and implementation of a wireless OBD II fleet management system | |
| CN106990773A (en) | vehicle remote diagnosis method, cloud server and system | |
| EP3422128A1 (en) | Method and apparatus for use in remote diagnosis of vehicle | |
| CN104932489B (en) | Wireless vehicle mounted chip flash diagnostic system and method | |
| CN109030994B (en) | Test method and system | |
| US7257472B2 (en) | Method and apparatus for fault diagnosis | |
| CN105573296A (en) | Hardware-in-loop-based automation test system for automobile diagnosis, and method thereof | |
| CN106227122B (en) | A kind of detection of vehicle mounted failure and early warning system | |
| CN110855558B (en) | Internet of vehicles gateway and CANoverTCP/IP protocol connection realization method, ECU and upgrading method | |
| CN102023922A (en) | System and method for testing automotive electronic diagnostic software | |
| CN104038262A (en) | Mobile terminal commercial vehicle monitoring system for realizing diagnosis technology and Bluetooth communication under Android platform | |
| CN113190454A (en) | Real-vehicle test method and system for vehicle-mounted terminal software | |
| CN111443691A (en) | Intelligent online diagnosis method and device for automobile | |
| CN102393733A (en) | Failure diagnosis method, fault diagnosis instrument and system thereof | |
| CN111506047B (en) | Vehicle diagnosis method, device and storage medium | |
| CN110968070B (en) | Intelligent ECU fault diagnosis system | |
| CN109872568A (en) | Vehicle trouble alarming method for power, device, computer equipment and storage medium | |
| CN107145138A (en) | A kind of diagnostic system suitable for different vehicle | |
| CN110717998A (en) | PEMS detection device for non-road vehicle and detection method thereof | |
| CN110647139B (en) | Evaluation test tool and evaluation test method for OBD (on-Board diagnostics) mass production vehicle | |
| CN113433923A (en) | Vehicle remote diagnosis method, system, readable storage medium and device | |
| CN109088807A (en) | Based on CAN network vehicle protocol API development system | |
| CN114257470A (en) | Vehicle Bluetooth function test system and test method | |
| CN211294143U (en) | Vehicle-mounted wireless terminal detection system for automobile | |
| CN205785829U (en) | A kind of vehicle diagnosing system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181225 |
|
| RJ01 | Rejection of invention patent application after publication |