CN111427335B - Vehicle remote diagnosis method, equipment connector and vehicle connector - Google Patents

Vehicle remote diagnosis method, equipment connector and vehicle connector Download PDF

Info

Publication number
CN111427335B
CN111427335B CN202010321672.8A CN202010321672A CN111427335B CN 111427335 B CN111427335 B CN 111427335B CN 202010321672 A CN202010321672 A CN 202010321672A CN 111427335 B CN111427335 B CN 111427335B
Authority
CN
China
Prior art keywords
vehicle
diagnosis
connector
diagnosed
message
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.)
Active
Application number
CN202010321672.8A
Other languages
Chinese (zh)
Other versions
CN111427335A (en
Inventor
刘均
陈质健
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Launch Technology Co Ltd
Original Assignee
Shenzhen Launch Technology Co Ltd
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 Shenzhen Launch Technology Co Ltd filed Critical Shenzhen Launch Technology Co Ltd
Priority to CN202010321672.8A priority Critical patent/CN111427335B/en
Publication of CN111427335A publication Critical patent/CN111427335A/en
Application granted granted Critical
Publication of CN111427335B publication Critical patent/CN111427335B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
    • G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0267—Fault communication, e.g. human machine interface [HMI]
    • G05B23/0272—Presentation of monitored results, e.g. selection of status reports to be displayed; Filtering information to the user
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0275—Fault isolation and identification, e.g. classify fault; estimate cause or root of failure
    • G05B23/0278—Qualitative, e.g. if-then rules; Fuzzy logic; Lookup tables; Symptomatic search; FMEA
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Fuzzy Systems (AREA)
  • Mathematical Physics (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Small-Scale Networks (AREA)

Abstract

The application discloses a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium. In the scheme of the application, the vehicle to be diagnosed and the diagnostic equipment are not directly connected with each other through CAN FD, the vehicle to be diagnosed and the vehicle connector are connected with each other through CAN FD, the diagnostic equipment and the device connector are connected with each other through CAN FD, and the vehicle connector and the device connector are connected with each other through remote communication. That is, the vehicle connector and the device connector are used as a data transfer station to realize data interaction between the vehicle to be diagnosed and the diagnostic device. According to the technical scheme, the vehicle to be diagnosed and the diagnosis equipment are decoupled, so that the diagnosis equipment CAN remotely diagnose the vehicle to be diagnosed, and the application range of the diagnosis equipment based on CAN FD is improved.

Description

Vehicle remote diagnosis method, equipment connector and vehicle connector
Technical Field
The application belongs to the technical field of automobile communication, and particularly relates to a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium.
Background
With the rapid development of automotive electronics and industrial automation, the number of devices and the data volume on a controller area network (Controller Area Network, CAN) bus are greatly increased, which brings a great challenge to the CAN bus. To meet higher bandwidth and data throughput, CAN FD (CAN with Flexible Data-Rate) was developed.
Currently, some vehicles communicate with diagnostic devices using CAN FD bus. At present, the CAN FD bus CAN only be used for diagnosis in a short distance in a mode of locally shielding twisted pair wire connection between the diagnosis equipment and the vehicle, which brings more inconvenience to vehicle diagnosis.
Disclosure of Invention
The application provides a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium, so that diagnosis equipment CAN remotely diagnose a vehicle to be diagnosed, and the application range of the diagnosis equipment based on a CAN FD bus is improved.
In a first aspect, the present application provides a vehicle remote diagnosis method applied to a vehicle remote diagnosis system, where the vehicle remote diagnosis system includes a diagnosis device, a device connector, a vehicle connector, and a vehicle to be diagnosed, the vehicle remote diagnosis method includes:
the diagnostic equipment acquires vehicle information of the vehicle to be diagnosed, generates a diagnostic message and sends the diagnostic message to the equipment connector, and the diagnostic message is generated based on a CAN FD protocol;
the equipment connector packages the diagnosis message into a first data packet and sends the first data packet to the vehicle connector in a remote communication mode;
The vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle to be diagnosed, receives diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message, encapsulates the diagnosis response data into a second data packet, and sends the second data packet to the equipment connector in a remote communication mode;
the device connector analyzes the second data packet to obtain the diagnosis response data and sends the diagnosis response data to the diagnosis device;
the diagnosis device analyzes and processes the diagnosis response data to obtain a diagnosis result.
In a second aspect, the present application provides a vehicle remote diagnosis method applied to a device connector, including:
receiving a diagnosis message sent by a diagnosis device based on a vehicle to be diagnosed, and packaging the diagnosis message into a first data packet, wherein the diagnosis message is generated based on a CAN FD protocol;
transmitting the first data packet to a vehicle connector in a remote communication mode, so that the vehicle connector analyzes the first data packet to obtain the diagnosis message;
receiving a second data packet sent by the vehicle connector through the remote communication mode, wherein the second data packet is obtained by packaging diagnosis response data by the vehicle connector, and the diagnosis response data is obtained by responding the vehicle to be diagnosed based on a diagnosis message;
Analyzing the second data packet to obtain the diagnosis response data;
and sending the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result.
Optionally, before the receiving the diagnosis message sent by the diagnosis device based on the vehicle to be diagnosed, the vehicle remote diagnosis method further includes:
acquiring the vehicle type information of the vehicle to be diagnosed;
the CAN FD terminal resistor is configured according to the vehicle type information;
and performing CAN FD connection with the diagnostic equipment based on the CAN FD terminal resistor.
Optionally, the performing CAN FD connection with the diagnostic device based on the CAN FD terminal resistor includes:
determining a target CAN FD node according to the CAN FD terminal resistance;
determining a data transmission rate;
and constructing a CAN FD network by the target CNAFD node and a CAN FD node of the diagnostic equipment, and performing CAN FD connection with the diagnostic equipment based on the data transmission rate.
In a third aspect, the present application provides a vehicle remote diagnosis method applied to a vehicle connector, including:
receiving a first data packet sent by a device connector through remote communication, wherein the first data packet is obtained by packaging a diagnostic message by the device connector; the diagnostic message is generated by the diagnostic equipment based on the vehicle to be diagnosed according to the CAN FD protocol and is sent to the equipment connector;
Analyzing the first data packet to obtain the diagnosis message;
sending the diagnosis message to the vehicle to be diagnosed;
receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message;
encapsulating the diagnostic response data into a second data packet;
and sending the second data packet to the device connector in a remote communication mode so that the device connector analyzes and obtains the diagnosis response data, and sending the diagnosis response data to the diagnosis device so that the diagnosis device can further analyze the diagnosis response data to obtain a diagnosis result.
Optionally, before the receiving the first data packet sent by the device connector through remote communication, the vehicle remote diagnosis method further includes:
acquiring the vehicle type information of the vehicle to be diagnosed;
configuring a data transmission rate and a CAN FD filter according to the vehicle type information;
and carrying out CAN FD connection with the vehicle to be diagnosed based on the CAN FD filter and the data transmission rate.
Optionally, the receiving the diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message specifically includes:
and filtering response data of the vehicle to be diagnosed responding to the diagnosis message according to the CAN FD filter to obtain the diagnosis response data.
In a fourth aspect, the present application provides a vehicle remote diagnosis system, where the vehicle remote diagnosis system includes a diagnosis device, a device connector, a vehicle connector, and a vehicle to be diagnosed, where the diagnosis device is configured to obtain vehicle information of the vehicle to be diagnosed, generate a diagnosis message, and send the diagnosis message to the device connector, where the diagnosis message is generated based on a CAN FD protocol;
the device connector is used for packaging the diagnosis message into a first data packet and sending the first data packet to the vehicle connector in a remote communication mode;
the vehicle connector is used for analyzing the first data packet to obtain the diagnosis message, sending the diagnosis message to the vehicle to be diagnosed, receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message, packaging the diagnosis response data into a second data packet, and sending the second data packet to the equipment connector in a remote communication mode;
the device connector is further configured to parse the second data packet to obtain the diagnosis response data, and send the diagnosis response data to the diagnosis device;
the diagnosis device is also used for analyzing and processing the diagnosis response data to obtain a diagnosis result.
In a fifth aspect, the present application provides a device connector comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method of the second aspect when the computer program is executed.
In a sixth aspect, the present application provides a vehicle connector comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to the third aspect when the computer program is executed.
In a seventh aspect, the present application provides a computer readable storage medium storing a computer program which when executed by a processor performs the steps of the method of the second aspect as described above; alternatively, the computer program as described above implements the steps of the method as described in the third aspect when executed by a processor.
In an eighth aspect, the present application provides a computer program product comprising a computer program which, when executed by one or more processors, performs the steps of the method of the second aspect as described above; alternatively, the computer program as described above may implement the steps of the method of the third aspect as described above when executed by one or more processors.
From the above, according to the scheme of the application, the diagnosis device does not directly establish CAN FD connection with the vehicle to be diagnosed, but establishes CAN FD connection with the device connector, and sends a diagnosis message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized. It will be appreciated that the advantages of the second to eighth aspects may be found in the relevant description of the first aspect, and are not repeated here.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, and it is possible for a person skilled in the art to obtain other drawings from these drawings without inventive effort.
FIG. 1 is a network architecture diagram of a vehicle remote diagnostic system provided in an embodiment of the present application;
FIG. 2 is a schematic flow chart of an implementation of a vehicle remote diagnosis method according to an embodiment of the present application;
FIG. 3 is a schematic flow chart of another implementation of a vehicle remote diagnosis method according to an embodiment of the present application;
FIG. 4 is a schematic flow chart of another implementation of a vehicle remote diagnosis method according to an embodiment of the present application;
FIG. 5 is a block diagram of a vehicle remote diagnostic device provided in an embodiment of the present application;
FIG. 6 is a block diagram of another vehicle remote diagnostic device provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of a device connector according to an embodiment of the present application;
fig. 8 is a schematic structural view of a vehicle connector provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
Currently, when a diagnostic device establishes a CAN FD connection with a vehicle to be diagnosed for CAN FD diagnosis, considering that the CAN FD connection often depends on a local shielded twisted pair, the transmission distance of the local shielded twisted pair is usually limited, which requires that the diagnostic device CAN only perform diagnostic operations on the vehicle to be diagnosed over the local shielded twisted pair within a limited distance. Once the diagnostic equipment is far away from the vehicle to be diagnosed, CAN FD diagnosis cannot be performed in the above manner, which greatly limits the application scenarios of CAN FD diagnosis. Based on this, the embodiment of the application provides a vehicle remote diagnosis method, a device connector, a vehicle connector and a computer readable storage medium, which CAN decouple a vehicle to be diagnosed from a diagnosis device through the device connector and the network connector, so as to realize remote diagnosis of the vehicle to be diagnosed by the diagnosis device based on CAN FD. In order to illustrate the technical solutions proposed in the embodiments of the present application, the following description is made by specific embodiments.
A vehicle remote diagnosis method provided in the embodiment of the present application is described below. Referring to fig. 1, the vehicle remote diagnosis method is applied to a vehicle remote diagnosis system, and the vehicle remote diagnosis system comprises a vehicle to be diagnosed, a vehicle connector, an equipment connector and diagnosis equipment; the vehicle to be diagnosed and the vehicle connector perform data interaction in a CAN FD communication mode; the vehicle connector and the equipment connector interact data in a remote communication mode; and the device connector and the diagnostic device also carry out data interaction in a CAN FD communication mode.
Specifically, in the vehicle remote diagnosis system described above:
the diagnosis equipment is used for acquiring vehicle information of the vehicle to be diagnosed, generating a diagnosis message and sending the diagnosis message to the equipment connector, wherein the diagnosis message is generated based on a CAN FD protocol;
the device connector is used for packaging the diagnosis message into a first data packet and sending the first data packet to the vehicle connector in a remote communication mode;
the vehicle connector is used for analyzing the first data packet to obtain the diagnosis message, sending the diagnosis message to the vehicle to be diagnosed, receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message, packaging the diagnosis response data into a second data packet, and sending the second data packet to the equipment connector in a remote communication mode;
the device connector is further configured to parse the second data packet to obtain the diagnosis response data, and send the diagnosis response data to the diagnosis device;
the diagnosis device is also used for analyzing and processing the diagnosis response data to obtain a diagnosis result.
In the embodiment of the application, the vehicle to be diagnosed is a vehicle with a diagnosis requirement at present, that is, any vehicle with a diagnosis requirement can be used as the vehicle to be diagnosed to be connected to the vehicle remote diagnosis system; the vehicle connector can serve as a data transfer station and transfer data to the vehicle or equipment connector to be diagnosed; the device connector can also be used as a data transfer station to transfer data to the vehicle connector or the diagnostic device; the diagnostic device includes, but is not limited to, various vehicle scanning tools such as a handheld diagnostic instrument or a PC, and a diagnostic database is stored on the diagnostic device, through which diagnostic response data sent by a vehicle to be diagnosed can be diagnosed and a diagnostic result of the vehicle to be diagnosed can be fed back.
Referring to fig. 2, fig. 2 shows a schematic diagram of an interaction flow among a vehicle to be diagnosed, a vehicle connector, a device connector and a diagnostic device, and the vehicle remote diagnosis method includes:
step 201, the diagnostic device obtains the vehicle information of the vehicle to be diagnosed, and generates a diagnostic message based on a CAN FD protocol;
in this embodiment of the present application, the diagnostic device may actively start the data interaction of the present wheel, or may perform corresponding feedback by the diagnostic device after the vehicle to be diagnosed starts the data interaction of the present wheel, which is not limited herein. In consideration of the fact that the vehicle remote diagnosis system can be connected with a plurality of vehicles to be diagnosed, in order to facilitate distinguishing and avoid confusion in the data interaction process, vehicle information of the vehicles to be diagnosed can be timely obtained after the vehicles to be diagnosed which are required to be subjected to data interaction currently are selected; the vehicle information may be used to identify a vehicle to be diagnosed, and may include, for example, vehicle type information. After that, the diagnostic device CAN generate a corresponding diagnostic message for the vehicle to be diagnosed based on the CAN FD protocol. Because the diagnosis message is generated based on the vehicle to be diagnosed which is currently subjected to data interaction, the diagnosis message can be correctly sent to the vehicle to be diagnosed,
For example only, when the present-round data interaction is actively initiated by the diagnostic device, the diagnostic message may carry a diagnostic request for obtaining any ECU fault information on the vehicle to be diagnosed.
Step 202, the diagnostic device sends the diagnostic message to the device connector;
in the embodiment of the application, after the diagnostic device generates the diagnostic message, the diagnostic message CAN be sent to the device connector through the CAN FD connection with the device connector.
Step 203, the device connector encapsulates the diagnostic packet into a first data packet;
in this embodiment of the present application, after receiving the diagnostic packet, the device connector may further perform data encapsulation on the diagnostic packet to encapsulate the diagnostic packet into the first data packet. Specifically, the encapsulation mode used in encapsulating the first data packet is related to the transmission protocol used in subsequent remote communications. For example, if the transmission is performed by the hypertext transfer protocol (HyperText Transfer Protocol, HTTP) later, the diagnostic packet is encapsulated based on the HTTP protocol in this step, that is, the first packet is embodied in the form of an HTTP packet, which is not limited herein.
Step 204, the device connector sends the first data packet to the vehicle connector through a remote communication mode;
in this embodiment of the present application, after the diagnostic packet is encapsulated into the first data packet, the first data packet may be sent to a vehicle connector connected to the vehicle to be diagnosed through remote communication. It should be noted that, between the vehicle connector and the device connector, remote communication may be implemented by using a preset server as a data transfer station; alternatively, the remote communication may be implemented by a peer-to-peer (P2P) technology; alternatively, the remote communication may be realized by a wired network; alternatively, the remote communication may be implemented through a cellular mobile network such as 2G, 3G, 4G, or 5G, and the specific manner in which the remote communication is implemented is not limited herein.
Step 205, the vehicle connector receives the first data packet, and analyzes the first data packet to obtain the diagnostic message;
in this embodiment of the present application, when the vehicle connector receives, through remote communication, a first data packet sent by the device connector, the first data packet may be parsed based on a transmission protocol adopted by the remote communication, so as to obtain a diagnostic packet carried by the first data packet.
Step 206, the vehicle connector sends the diagnosis message to the vehicle to be diagnosed;
in the embodiment of the present application, the vehicle connector may send the diagnostic message to the vehicle to be diagnosed through a CAN FD connection with the vehicle to be diagnosed.
Step 207, the vehicle to be diagnosed generates diagnosis response data according to the diagnosis message;
in an embodiment of the present application, the vehicle to be diagnosed may generate corresponding diagnostic response data under the indication of the diagnostic message, where the diagnostic response data includes, but is not limited to, parameters related to vehicle diagnosis, such as a current running speed of the vehicle, an engine displacement, and/or a transmission parameter.
Step 208, the vehicle to be diagnosed feeds back the diagnosis response data to the vehicle connector;
in the embodiment of the present application, the vehicle to be diagnosed may send the diagnosis response data to the vehicle connector through a CAN FD connection with the vehicle connector.
Step 209, the vehicle connector receives the diagnostic response data and encapsulates the diagnostic response data into a second data packet
In this embodiment, after receiving the diagnosis response data, the vehicle connector further encapsulates the diagnosis response data to encapsulate the diagnosis message into a second data packet. Specifically, the encapsulation mode used in encapsulating the second data packet is related to the transmission protocol used in the subsequent remote communication. For example, if the transmission is performed by the HTTP protocol, the diagnostic response data will be encapsulated based on the HTTP protocol in this step, that is, the second packet will be embodied in the form of an HTTP packet, which is not limited herein. It should be noted that, since the transmission protocol adopted when the vehicle connector and the device connector interact data is always kept unchanged, the data format of the second data packet is always the same as the data format of the first data packet.
Step 210, the vehicle connector sends the second data packet to the device connector through remote communication;
in this embodiment, the implementation of step 210 is similar to that of step 204, except that the transmitting end is changed by the device connector to the vehicle connector, the receiving end is changed by the vehicle connector to the device connector, and the transmitted data is changed by the first data packet to the second data packet, so the relevant explanation and description of this step refer to step 204.
Step 211, the device connector receives the second data packet and parses the second data packet to obtain the diagnosis response data;
in this embodiment of the present application, when the device connector receives, through remote communication, a second data packet sent by the vehicle connector, the second data packet may be parsed based on a transmission protocol adopted by the remote communication, so as to obtain diagnostic response data carried by the second data packet.
Step 212, the device connector transmits the diagnosis response data to the diagnosis device;
in the embodiment of the application, the device connector may send the diagnosis response data to the diagnosis device through a CAN FD connection with the diagnosis device.
And 213, the diagnostic equipment analyzes and processes the diagnostic response data to obtain a diagnostic result.
In the embodiment of the application, the diagnosis data is analyzed and processed through a locally stored diagnosis database, so as to obtain a diagnosis result obtained by diagnosing the vehicle to be diagnosed. The diagnosis result can be output through a display screen, and a diagnosis person can be informed of possible problems of the vehicle to be diagnosed at present in time and intuitively; alternatively, the above diagnosis result may be output to a mobile client associated with the vehicle to be diagnosed, and the manner of outputting the above diagnosis result is not limited herein. The diagnostic equipment completes one round of data interaction with the vehicle to be diagnosed. It should be noted that in the embodiments of the present application, each round of data interaction needs to be initiated by the diagnostic device side.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
Another vehicle remote diagnosis method provided in the embodiment of the present application, which is applied to a device connector, is described below. Referring to fig. 3, fig. 3 shows a specific implementation flow of the vehicle remote diagnosis method, which is described in detail as follows:
step 301, receiving a diagnosis message sent by a diagnosis device based on a vehicle to be diagnosed, and packaging the diagnosis message into a first data packet, wherein the diagnosis message is generated based on a CAN FD protocol;
step 302, transmitting the first data packet to a vehicle connector through a remote communication manner, so that the vehicle connector analyzes the first data packet to obtain the diagnostic message;
step 303, receiving a second data packet sent by the vehicle connector through the remote communication mode, wherein the second data packet is obtained by packaging diagnosis response data by the vehicle connector, and the diagnosis response data is obtained by responding to the vehicle to be diagnosed based on a diagnosis message;
step 304, analyzing the second data packet to obtain the diagnosis response data;
and 305, transmitting the diagnosis response data to the diagnosis device so that the diagnosis device analyzes and processes the diagnosis response data to obtain a diagnosis result.
Step 301 is the same as or similar to step 203, step 302 is the same as or similar to step 202, step 303 is the same as or similar to step 203, steps 304 and 305 are the same as or similar to step 210, and step 306 is the same as or similar to step 211, which will not be described herein.
Optionally, before the step 301, the vehicle remote diagnosis method further includes:
acquiring the vehicle type information of the vehicle to be diagnosed;
the CAN FD terminal resistor is configured according to the vehicle type information;
and performing CAN FD connection with the diagnostic equipment based on the CAN FD terminal resistor.
In this embodiment of the present application, because the number of current automobile manufacturers is greater, in order to better connect the device connector with the diagnostic device by using CAN FD, vehicle type information of the vehicle to be diagnosed may be obtained from vehicle information of the vehicle to be diagnosed, and a CAN FD terminal resistor may be configured according to the vehicle type information, where a resistance value of the CAN FD terminal resistor is in a preset resistance value range, for example, the resistance value range may be 100 ohms to 140 ohms, and the resistance value of the terminal resistor is not limited herein.
In some embodiments, the vehicle type information of the vehicle to be diagnosed may be obtained by analyzing a vehicle identification code (Vehicle Identification Number, VIN) of the vehicle to be diagnosed after the vehicle identification code is read by the vehicle connector; alternatively, the vehicle type information of the vehicle to be diagnosed may be directly input into the vehicle connector by the vehicle owner of the vehicle to be diagnosed, which is not limited herein. After the vehicle connector obtains the vehicle type information of the vehicle to be diagnosed, the vehicle connector CAN be packaged in the vehicle information of the vehicle to be diagnosed, and the vehicle information containing the vehicle type information of the vehicle to be diagnosed is synchronized into the device connector in a remote communication mode, so that the device connector CAN configure a CAN FD terminal resistor according to the vehicle type information, and CAN FD connection is established with the diagnostic device according to the CAN FD terminal resistor.
It should be noted that the CAN FD connection is established by a local shielded twisted pair, i.e. a wired connection between the device connector and the diagnostic device. Wherein, the above-mentioned CAN FD connection meets the ISO 11898 standard, and is not described herein.
Optionally, the step of establishing a CAN FD connection with the diagnostic device based on the CAN FD terminal resistor specifically includes:
determining a target CAN FD node according to the CAN FD terminal resistance;
determining a data transmission rate;
and constructing a CAN FD network by the target CNAFD node and a CAN FD node of the diagnostic equipment, and performing CAN FD connection with the diagnostic equipment based on the data transmission rate.
In the embodiment of the application, the device connector will agree with the diagnostic device with a data transmission rate, wherein the data transmission rate may be set in advance by the diagnostic person according to the vehicle type information of the vehicle to be diagnosed, that is, the diagnostic device may determine the data transmission rate according to the vehicle type information of the vehicle to be diagnosed. Of course, the data transmission rate may be determined by other means, which are not limited herein. In addition, the device connector determines a target CAN FD node adopted in the device connector according to the CAN FD terminal resistance, and constructs the target CAN FD node in the device connector and the CAN FD node of the diagnostic device together into one or more groups of CAN FD bus networks, and performs CAN FD connection with the diagnostic device based on the constructed CAN FD bus network and the data transmission rate.
In some embodiments, the diagnostician may further preset a configuration table, where CAN FD protocol configuration information related to each vehicle model is configured, where the CAN FD protocol configuration information is used to indicate the number of groups of the CAN FD bus network that needs to be built. For example, if it is determined, based on the model of the vehicle to be diagnosed, that the CAN FD protocol configuration information indicates that a set of CAN FD bus networks needs to be established, then the target CAN FD node in the device connector will together establish a set of CAN FD bus networks with the CAN FD node of the diagnostic device under the indication of the CAN FD protocol configuration information; for another example, if it is determined, based on the model of the vehicle to be diagnosed, that the CAN FD protocol configuration information indicates that two sets of CAN FD bus networks need to be established, the target CAN FD node in the device connector will together establish two sets of CAN FD bus networks with the CAN FD node of the diagnostic device under the indication of the CAN FD protocol configuration information.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
A further vehicle remote diagnosis method provided in an embodiment of the present application, which is applied to a vehicle connector, is described below. Referring to fig. 4, fig. 4 shows a specific implementation flow of the vehicle remote diagnosis method, which is described in detail as follows:
step 401, receiving a first data packet sent by a device connector through remote communication, wherein the first data packet is obtained by encapsulating a diagnostic message by the device connector; the diagnostic message is generated by the diagnostic equipment based on the vehicle to be diagnosed according to the CAN FD protocol and is sent to the equipment connector;
step 402, analyzing the first data packet to obtain the diagnostic message;
step 403, sending the above diagnosis message to the vehicle to be diagnosed;
step 404, receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message;
step 405, encapsulating the diagnosis response data into a second data packet;
step 406, sending the second data packet to the device connector through a remote communication manner, so that the device connector analyzes and obtains the diagnosis response data, and then sending the diagnosis response data to the diagnosis device, so that the diagnosis device further analyzes the diagnosis response data to obtain a diagnosis result.
Wherein steps 401 and 402 are the same as or similar to step 205, step 403 is the same as or similar to step 206, steps 404 and 405 are the same as or similar to step 209, and step 406 is the same as or similar to step 210, which will not be described herein.
Optionally, before the step 401, the vehicle remote diagnosis method further includes:
acquiring the vehicle type information of the vehicle to be diagnosed;
configuring a data transmission rate and a CAN FD filter according to the vehicle type information;
and carrying out CAN FD connection with the vehicle to be diagnosed based on the CAN FD filter and the data transmission rate.
In this embodiment of the present application, because the number of current automobile manufacturers is greater, in order to better connect the vehicle connector with the vehicle to be diagnosed in a CAN FD manner, vehicle type information of the vehicle to be diagnosed may also be obtained from vehicle information of the vehicle to be diagnosed, and the data transmission rate and the CAN FD filter may be configured according to the vehicle type information, so that the vehicle connector and the vehicle to be diagnosed may be subsequently connected with the vehicle to be diagnosed in a CAN FD manner based on the configured CAN FD filter and the configured data transmission rate. The diagnostic personnel CAN preset a configuration table, wherein the configuration table is configured with association relations among parameters of the vehicle type, the data transmission rate and the CAN FD filter; the vehicle connector may implement a configuration of the data transfer rate and CAN FD filter based on the configuration table.
In some embodiments, the vehicle type of the vehicle to be diagnosed may be obtained by analyzing a vehicle identification code of the vehicle to be diagnosed after the vehicle connector reads the vehicle identification code; alternatively, the vehicle type of the vehicle to be diagnosed may be directly input into the vehicle connector by the owner of the vehicle to be diagnosed, which is not limited herein. It should be noted that, after the vehicle connector obtains the vehicle type of the vehicle to be diagnosed, the vehicle type of the vehicle to be diagnosed may be synchronized with the device connector by a remote communication manner, so as to instruct the device connector to complete the relevant configuration, which is not described herein.
It should be noted that the CAN FD connection is established by a local shielded twisted pair, i.e. a wired connection between the vehicle connector and the vehicle to be diagnosed. Wherein, the above-mentioned CAN FD connection meets the ISO 11898 standard, and is not described herein.
Optionally, in consideration of that the vehicle to be diagnosed may send response data irrelevant to the diagnosis operation to the vehicle connector after the vehicle to be diagnosed establishes the CAN FD connection with the vehicle connector, in order to improve the diagnosis efficiency, the step 404 may be specifically:
and filtering response data of the vehicle to be diagnosed responding to the diagnosis message according to the CAN FD filter to obtain the diagnosis response data.
In the embodiment of the present application, the response data of the vehicle to be diagnosed in response to the above-mentioned diagnostic message may include response data unrelated to the diagnostic operation. Obviously, these response data, which are not relevant for the diagnostic operation, should not be forwarded to the diagnostic device. Based on this, it is necessary to filter the response data in response to the above-described diagnostic message, filter out the response data irrelevant to the diagnostic operation, and retain only the response data relevant to the diagnostic operation, that is, the diagnostic response data. The above filtering operation is achieved in particular by means of the previously configured filters. In an actual application scene, response data which does not accord with the CAN FD data format CAN be filtered through a configured filter, and response data which does not match the data transmission rate CAN be filtered through the configured filter; that is, only response data satisfying the CAN FD data format and the data transfer rate is retained.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
Corresponding to the vehicle remote diagnosis method applied to the device connector set forth above, the embodiment of the application provides a vehicle remote diagnosis apparatus applied to the device connector. As shown in fig. 5, a vehicle remote diagnosis device 500 in the embodiment of the present application includes:
a diagnostic message receiving unit 501, configured to receive a diagnostic message sent by a diagnostic device based on a vehicle to be diagnosed, where the diagnostic message is generated based on a CAN FD protocol;
a first data packet encapsulation unit 502, configured to encapsulate the diagnostic packet into a first data packet;
a first data packet sending unit 503, configured to send the first data packet to a vehicle connector through a remote communication manner, so that the vehicle connector parses the first data packet to obtain the diagnostic packet;
a second data packet receiving unit 504, configured to receive a second data packet sent by the vehicle connector through the remote communication manner, where the second data packet is obtained by encapsulating diagnostic response data by the vehicle connector, and the diagnostic response data is obtained by responding to the vehicle to be diagnosed based on a diagnostic message;
a second data packet parsing unit 505, configured to parse the second data packet to obtain the diagnosis response data;
And a diagnostic response data transmitting unit 506 configured to transmit the diagnostic response data to the diagnostic device, so that the diagnostic device analyzes and processes the diagnostic response data to obtain a diagnostic result.
Optionally, the vehicle remote diagnosis device 500 further includes:
a vehicle type information acquisition unit for acquiring the vehicle type information of the vehicle to be diagnosed;
the terminal resistor configuration unit is used for configuring CAN FD terminal resistors according to the vehicle type information;
and the CAN FD connection unit is used for carrying out CAN FD connection with the diagnostic equipment based on the CAN FD terminal resistor.
Optionally, the CAN FD connection unit includes:
a target CAN FD node determination subunit for determining a target CAN FD node according to the CAN FD terminal resistance;
a data transmission rate determination subunit configured to determine a data transmission rate;
and the CAN FD network construction subunit is used for constructing a CAN FD network from the target CNAFD node and the CAN FD node of the diagnostic equipment and carrying out CAN FD connection with the diagnostic equipment based on the data transmission rate.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
Corresponding to the vehicle remote diagnosis method applied to the vehicle connector, the embodiment of the application also provides a vehicle remote diagnosis device, which is applied to the vehicle connector. As shown in fig. 6, a vehicle remote diagnosis device 600 in the embodiment of the present application includes:
a first data packet receiving unit 601, configured to receive a first data packet sent by a device connector through remote communication, where the first data packet is obtained by encapsulating a diagnostic packet by the device connector; the diagnostic message is generated by the diagnostic equipment based on the vehicle to be diagnosed according to the CAN FD protocol and is sent to the equipment connector;
a first packet parsing unit 602, configured to parse the first packet to obtain the diagnostic packet;
a diagnostic message sending unit 603, configured to send the diagnostic message to the vehicle to be diagnosed;
a diagnostic response data receiving unit 604, configured to receive diagnostic response data sent by the vehicle to be diagnosed based on the diagnostic message;
a second packet encapsulation unit 605 for encapsulating the diagnosis response data into a second packet;
and a second data packet sending unit 606, configured to send the second data packet to the device connector through a remote communication manner, so that the device connector parses and obtains the diagnostic response data, and further send the diagnostic response data to the diagnostic device, so that the diagnostic device further analyzes the diagnostic response data to obtain a diagnostic result.
Optionally, the vehicle remote diagnosis device 600 further includes:
a vehicle type information acquisition unit for acquiring the vehicle type information of the vehicle to be diagnosed;
the configuration unit is used for configuring the data transmission rate and the CAN FD filter according to the vehicle type information;
and the CAN FD connection unit is used for carrying out CAN FD connection with the vehicle to be diagnosed based on the CAN FD filter and the data transmission rate.
Optionally, the diagnostic response data receiving unit is specifically configured to filter, according to the CAN FD filter, response data of the vehicle to be diagnosed in response to the diagnostic message, so as to obtain the diagnostic response data.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
The embodiment of the application also provides a device connector. Referring to fig. 7, fig. 7 is a schematic structural diagram of a device connector according to an embodiment of the present application. As shown in fig. 7, the device connector 7 of this embodiment includes: at least one processor 70 (only one processor is shown in fig. 7), a memory 71 and a computer program 72 stored in the memory 71 and executable on the at least one processor 70, the processor 70 implementing the steps in the method embodiments applied to the device connector when executing the computer program 72, for example, may be implemented:
receiving a diagnosis message sent by a diagnosis device based on a vehicle to be diagnosed, and packaging the diagnosis message into a first data packet, wherein the diagnosis message is generated based on a CAN FD protocol;
transmitting the first data packet to a vehicle connector in a remote communication mode, so that the vehicle connector analyzes the first data packet to obtain the diagnosis message;
receiving a second data packet sent by the vehicle connector through the remote communication mode, wherein the second data packet is obtained by packaging diagnosis response data by the vehicle connector, and the diagnosis response data is obtained by responding the vehicle to be diagnosed based on a diagnosis message;
Analyzing the second data packet to obtain the diagnosis response data;
and sending the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result.
The connector may include, but is not limited to, a processor 70, a memory 71. It will be appreciated by those skilled in the art that fig. 7 is merely an example of the connector 7 and is not meant to be limiting of the connector 7, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The processor 70 may be a central processing unit (Central Processing Unit, CPU) and the processor 70 may be any other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field-programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 71 may in some embodiments be an internal storage unit of the connector 7, such as a hard disk or a memory of the connector 7. The memory 71 may also be an external storage device of the connector 7 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the connector 7. Further, the memory 71 may include both the internal storage unit and the external storage device of the connector 7. The memory 71 is used for storing an operating system, an application program, a boot loader (BootLoader), data, other programs, and the like, such as program codes of the computer programs. The above-described memory 71 may also be used to temporarily store data that has been output or is to be output.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
The embodiment of the application also provides a vehicle connector. Referring to fig. 8, fig. 8 is a schematic structural diagram of a vehicle connector according to an embodiment of the present application. As shown in fig. 8, the vehicle connector 8 of this embodiment includes: at least one processor 80 (only one processor is shown in fig. 8), a memory 81, and a computer program 82 stored in the memory 81 and executable on the at least one processor 80, the processor 80 implementing steps in an embodiment of a method applied to a vehicle connector when executing the computer program 82, for example, may be implemented:
receiving a first data packet sent by a device connector through remote communication, wherein the first data packet is obtained by packaging a diagnostic message by the device connector; the diagnostic message is generated by the diagnostic equipment based on the vehicle to be diagnosed according to the CAN FD protocol and is sent to the equipment connector;
analyzing the first data packet to obtain the diagnosis message;
sending the diagnosis message to the vehicle to be diagnosed;
receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message;
encapsulating the diagnostic response data into a second data packet;
and sending the second data packet to the device connector in a remote communication mode so that the device connector analyzes and obtains the diagnosis response data, and sending the diagnosis response data to the diagnosis device so that the diagnosis device can further analyze the diagnosis response data to obtain a diagnosis result.
The vehicle connector may include, but is not limited to, a processor 80, a memory 81. It will be appreciated by those skilled in the art that fig. 8 is merely an example of the vehicle connector 8 and is not intended to be limiting of the vehicle connector 8, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The processor 80 may be a central processing unit (Central Processing Unit, CPU), the processor 80 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field-programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 81 may in some embodiments be an internal storage unit of the vehicle connector 8, such as a hard disk or a memory of the vehicle connector 8. The memory 81 may also be an external storage device of the vehicle connector 8, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the vehicle connector 8 in other embodiments. Further, the memory 81 may include both the internal storage unit and the external storage device of the vehicle connector 8. The memory 81 is used for storing an operating system, an application program, a boot loader (BootLoader), data, other programs, and the like, such as program codes of the computer programs. The above-described memory 81 may also be used to temporarily store data that has been output or is to be output.
From the above, in the embodiment of the present application, the diagnostic device no longer directly establishes a CAN FD connection with the vehicle to be diagnosed, but establishes a CAN FD connection with the device connector, and sends a diagnostic message to the device connector; the device connector packages the received diagnosis message into a first data packet, then sends the first data packet to the vehicle connector, and after the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle, so that the diagnosis device can finally receive diagnosis response data fed back by the vehicle to be diagnosed based on the diagnosis message. The diagnosis device is decoupled from the vehicle to be diagnosed through the device connector and the vehicle connector, so that remote data interaction of the diagnosis device and the vehicle to be diagnosed based on CAN FD is realized.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program when executed by a processor implements steps of the method embodiments described above.
Embodiments of the present application provide a computer program product which, when run on a connector, causes the connector to perform steps that enable the implementation of the method embodiments described above.
The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the above computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. The computer program comprises computer program code, and the computer program code can be in a source code form, an object code form, an executable file or some intermediate form and the like. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a vehicle remote diagnostic device/connector, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in this application, it should be understood that the disclosed apparatus/connectors and methods may be implemented in other ways. For example, the above-described apparatus/connector embodiments are merely illustrative, e.g., the division of the modules or units described above is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims (9)

1. A vehicle remote diagnosis method, characterized by being applied to a vehicle remote diagnosis system including a diagnosis device, a device connector, a vehicle connector, and a vehicle to be diagnosed, the vehicle remote diagnosis method comprising:
The equipment connector acquires the vehicle type information of the vehicle to be diagnosed, configures a CAN FD terminal resistor according to the vehicle type information, and performs CAN FD connection with the diagnosis equipment based on the CAN FD terminal resistor;
the diagnosis equipment acquires vehicle information of the vehicle to be diagnosed, generates a diagnosis message and sends the diagnosis message to the equipment connector, and the diagnosis message is generated based on a CAN FD protocol;
the equipment connector packages the diagnosis message into a first data packet and sends the first data packet to the vehicle connector in a remote communication mode;
the vehicle connector analyzes the first data packet to obtain the diagnosis message, sends the diagnosis message to the vehicle to be diagnosed, receives diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message, packages the diagnosis response data into a second data packet, and sends the second data packet to the equipment connector in a remote communication mode;
the equipment connector analyzes the second data packet to obtain the diagnosis response data and sends the diagnosis response data to the diagnosis equipment;
the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result;
the vehicle to be diagnosed and the vehicle connector perform data interaction in a CAN FD communication mode; and the device connector and the diagnostic device perform data interaction in a CAN FD communication mode.
2. A vehicle remote diagnosis method, applied to a device connector, comprising: receiving a diagnosis message sent by a diagnosis device based on a vehicle to be diagnosed, and packaging the diagnosis message into a first data packet, wherein the diagnosis message is generated based on a CAN FD protocol;
the first data packet is sent to a vehicle connector in a remote communication mode, so that the vehicle connector analyzes the first data packet to obtain the diagnosis message;
receiving a second data packet sent by the vehicle connector in the remote communication mode, wherein the second data packet is obtained by packaging diagnosis response data by the vehicle connector, and the diagnosis response data is obtained by responding the vehicle to be diagnosed based on a diagnosis message;
analyzing the second data packet to obtain the diagnosis response data;
sending the diagnosis response data to the diagnosis equipment so that the diagnosis equipment analyzes and processes the diagnosis response data to obtain a diagnosis result;
before the receiving diagnosis device sends the diagnosis message based on the vehicle to be diagnosed, the vehicle remote diagnosis method further comprises the following steps:
acquiring the vehicle type information of the vehicle to be diagnosed;
The CAN FD terminal resistor is configured according to the vehicle type information;
CAN FD connection is carried out with the diagnosis equipment based on the CAN FD terminal resistor;
the vehicle to be diagnosed and the vehicle connector perform data interaction in a CAN FD communication mode; and the device connector and the diagnostic device perform data interaction in a CAN FD communication mode.
3. The vehicle remote diagnosis method according to claim 2, characterized in that the CAN FD connection with the diagnosis device based on the CAN FD terminal resistance includes:
determining a target CAN FD node according to the CAN FD terminal resistance;
determining a data transmission rate;
and constructing a CAN FD network by the target CAN FD node and the CAN FD node of the diagnostic equipment, and performing CAN FD connection with the diagnostic equipment based on the data transmission rate.
4. A vehicle remote diagnosis method, characterized by being applied to a vehicle connector, comprising:
receiving a first data packet sent by a device connector through remote communication, wherein the first data packet is obtained by packaging a diagnostic message by the device connector; the diagnosis message is generated by the diagnosis equipment based on the vehicle to be diagnosed according to the CAN FD protocol and is sent to the equipment connector; the equipment connector acquires the vehicle type information of the vehicle to be diagnosed, configures a CAN FD terminal resistor according to the vehicle type information, and performs CAN FD connection with the diagnosis equipment based on the CAN FD terminal resistor;
Analyzing the first data packet to obtain the diagnosis message;
sending the diagnosis message to the vehicle to be diagnosed;
receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message;
encapsulating the diagnostic response data into a second data packet;
the second data packet is sent to the equipment connector in a remote communication mode, so that the equipment connector analyzes and obtains the diagnosis response data, and then the diagnosis response data are sent to the diagnosis equipment, so that the diagnosis equipment further analyzes the diagnosis response data to obtain a diagnosis result;
the vehicle to be diagnosed and the vehicle connector perform data interaction in a CAN FD communication mode; and the device connector and the diagnostic device perform data interaction in a CAN FD communication mode.
5. The vehicle remote diagnosis method according to claim 4, further comprising, before the first data packet transmitted by the receiving device connector by remote communication:
acquiring the vehicle type information of the vehicle to be diagnosed;
configuring a data transmission rate and a CAN FD filter according to the vehicle type information;
and performing CAN FD connection with the vehicle to be diagnosed based on the CAN FD filter and the data transmission rate.
6. The method of claim 5, wherein receiving diagnostic response data sent by the vehicle to be diagnosed based on the diagnostic message comprises:
and filtering response data of the vehicle to be diagnosed responding to the diagnosis message according to the CAN FD filter to obtain the diagnosis response data.
7. A vehicle remote diagnosis system is characterized in that the vehicle remote diagnosis system comprises diagnosis equipment, equipment connectors, vehicle connectors and a vehicle to be diagnosed, wherein,
the equipment connector is used for acquiring the vehicle type information of the vehicle to be diagnosed, configuring a CAN FD terminal resistor according to the vehicle type information, and performing CAN FD connection with the diagnosis equipment based on the CAN FD terminal resistor; the diagnosis equipment is used for acquiring vehicle information of the vehicle to be diagnosed, generating a diagnosis message and sending the diagnosis message to the equipment connector, wherein the diagnosis message is generated based on a CAN FD protocol;
the device connector is used for packaging the diagnosis message into a first data packet and sending the first data packet to the vehicle connector in a remote communication mode;
the vehicle connector is used for analyzing the first data packet to obtain the diagnosis message, sending the diagnosis message to the vehicle to be diagnosed, receiving diagnosis response data sent by the vehicle to be diagnosed based on the diagnosis message, packaging the diagnosis response data into a second data packet, and sending the second data packet to the equipment connector in a remote communication mode;
The device connector is further used for analyzing the second data packet to obtain the diagnosis response data and sending the diagnosis response data to the diagnosis device;
the diagnosis equipment is also used for analyzing and processing the diagnosis response data to obtain a diagnosis result;
the vehicle to be diagnosed and the vehicle connector perform data interaction in a CAN FD communication mode; and the device connector and the diagnostic device also conduct data interaction in a CAN FD communication mode.
8. A device connector, the device connector comprising:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform the vehicle remote diagnostic method of claim 2 or 3.
9. A vehicle connector, the vehicle connector comprising:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform the vehicle remote diagnostic method of any of claims 4-6.
CN202010321672.8A 2020-04-22 2020-04-22 Vehicle remote diagnosis method, equipment connector and vehicle connector Active CN111427335B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010321672.8A CN111427335B (en) 2020-04-22 2020-04-22 Vehicle remote diagnosis method, equipment connector and vehicle connector

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010321672.8A CN111427335B (en) 2020-04-22 2020-04-22 Vehicle remote diagnosis method, equipment connector and vehicle connector

Publications (2)

Publication Number Publication Date
CN111427335A CN111427335A (en) 2020-07-17
CN111427335B true CN111427335B (en) 2023-06-02

Family

ID=71554280

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010321672.8A Active CN111427335B (en) 2020-04-22 2020-04-22 Vehicle remote diagnosis method, equipment connector and vehicle connector

Country Status (1)

Country Link
CN (1) CN111427335B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112180905A (en) * 2020-10-22 2021-01-05 上海星融汽车科技有限公司 Vehicle remote diagnosis system and method thereof
CN112927392A (en) * 2021-01-19 2021-06-08 深圳市元征科技股份有限公司 Communication method, vehicle communication interface device and readable storage medium
CN112859818A (en) * 2021-01-22 2021-05-28 深圳市轩宇车鼎科技有限公司 Automobile diagnosis method and device
CN115705044A (en) * 2021-08-11 2023-02-17 华为技术有限公司 Vehicle remote diagnosis method, device and system
CN114326673A (en) * 2021-12-29 2022-04-12 深圳市元征科技股份有限公司 Vehicle remote diagnosis method and device, connector and storage medium
CN114650194B (en) * 2022-03-29 2024-05-10 深圳市元征科技股份有限公司 Data communication method, device, electronic equipment and storage medium
CN114866585B (en) * 2022-04-24 2024-09-10 深圳市元征科技股份有限公司 Remote upgrading method, device, system and equipment end connector
CN115390545A (en) * 2022-08-16 2022-11-25 北京经纬恒润科技股份有限公司 Vehicle diagnosis method, apparatus, device, readable storage medium, and program product

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106990772A (en) * 2017-03-30 2017-07-28 深圳市元征科技股份有限公司 OBD diagnostic devices and Vehicular diagnostic method
CN107272649A (en) * 2017-07-05 2017-10-20 东南（福建）汽车工业有限公司 Malfunction remote diagnosis system and method
CN110892681A (en) * 2017-07-21 2020-03-17 罗伯特·博世有限公司 Transmitting/receiving device for a CAN bus system and method for detecting a short circuit using a CAN transmitting/receiving device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11024102B2 (en) * 2018-05-10 2021-06-01 Mahle International Gmbh Apparatuses, systems, and methods for remotely capturing automotive vehicle diagnostic information, monitoring, and controlling

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106990772A (en) * 2017-03-30 2017-07-28 深圳市元征科技股份有限公司 OBD diagnostic devices and Vehicular diagnostic method
CN107272649A (en) * 2017-07-05 2017-10-20 东南（福建）汽车工业有限公司 Malfunction remote diagnosis system and method
CN110892681A (en) * 2017-07-21 2020-03-17 罗伯特·博世有限公司 Transmitting/receiving device for a CAN bus system and method for detecting a short circuit using a CAN transmitting/receiving device

Also Published As

Publication number Publication date
CN111427335A (en) 2020-07-17

Similar Documents

Publication Publication Date Title
CN111427335B (en) Vehicle remote diagnosis method, equipment connector and vehicle connector
CN111538312B (en) Vehicle remote diagnosis method, system, equipment connector and vehicle connector
CN111552268B (en) Vehicle remote diagnosis method, equipment connector and vehicle connector
EP3809223B1 (en) Vehicle remote diagnosis method and related apparatus
CN109669442A (en) A kind of method for converting protocol and conversion equipment
CN111552266B (en) Vehicle remote diagnosis method, system, equipment connector and vehicle connector
CN104734911A (en) CAN bus network management test system and method
CN114253251A (en) Vehicle remote diagnosis method and device, equipment connector and storage medium
CN110908363A (en) Data acquisition method and device for vehicle-mounted terminal
CN111506047B (en) Vehicle diagnosis method, device and storage medium
CN112740627A (en) Vehicle remote diagnosis method and system
CN110333713A (en) Car fault diagnosis method and system
KR20130021652A (en) Interface apparatus and method for converting a plurality of different vehicles diagnosis protocol to standard diagnosis protocol
CN112927392A (en) Communication method, vehicle communication interface device and readable storage medium
CN113645097A (en) Vehicle signal monitoring method, terminal equipment and electronic control unit
CN113038421A (en) Automobile diagnosis method, automobile diagnosis device and automobile gateway
CN113110391A (en) Vehicle data transmission method, diagnosis terminal and server
KR20240017005A (en) Remote vehicle communication filtering
CN114326673A (en) Vehicle remote diagnosis method and device, connector and storage medium
CN114637275A (en) Vehicle remote diagnosis method and device, electronic equipment and storage medium
Spencer et al. New can bus communication modules for digitizing forest machines functionalities in the context of forestry 4.0
CN112492546A (en) Automobile control method and system and readable storage medium
CN111740888B (en) Ignition signal synchronization method and related equipment
CN111683347B (en) Ignition signal synchronization method and related equipment
CN113542333A (en) Method for monitoring vehicle signals

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
GR01 Patent grant
GR01 Patent grant