CN111740888B - Ignition signal synchronization method and related equipment - Google Patents
Ignition signal synchronization method and related equipment Download PDFInfo
- Publication number
- CN111740888B CN111740888B CN202010406514.2A CN202010406514A CN111740888B CN 111740888 B CN111740888 B CN 111740888B CN 202010406514 A CN202010406514 A CN 202010406514A CN 111740888 B CN111740888 B CN 111740888B
- Authority
- CN
- China
- Prior art keywords
- ignition signal
- vehicle
- canbus
- connector
- supply voltage
- 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
Links
Images
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
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- 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/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- 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)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Small-Scale Networks (AREA)
Abstract
The application belongs to the field of vehicle diagnosis and provides a synchronization method of ignition signals and related equipment, wherein the synchronization method of the ignition signals comprises the following steps: the method comprises the following steps that a vehicle connector acquires an ignition signal of a vehicle, encapsulates the ignition signal into a network data packet and sends the network data packet to an equipment connector through remote communication; the equipment connector analyzes the network data packet to obtain an ignition signal and sends the ignition signal to the diagnostic equipment; the diagnosis equipment judges whether the ignition signal meets a preset condition or not, and if so, the ignition signal synchronization is finished, so that the ignition signal synchronization is realized during remote diagnosis. The embodiment of the application also discloses a vehicle connector, a device connector and a diagnosis device.
Description
Technical Field
The present application relates to the field of vehicle diagnostics, and more particularly, to a method and related apparatus for synchronizing an ignition signal.
Background
In the automobile diagnosis process, the diagnosis device needs to acquire an ignition signal of the vehicle to judge whether the vehicle is in an ignition state. Most of the existing diagnostic devices can only synchronize the ignition signal of the vehicle when the diagnostic devices are used at the near end, and cannot synchronize the ignition signal when the vehicle is diagnosed remotely.
Disclosure of Invention
In view of the above, embodiments of the present application provide a synchronization method for an ignition signal and a related device, so as to solve the problem that the ignition signal cannot be synchronized when a vehicle is remotely diagnosed.
A first aspect of an embodiment of the present application provides a synchronization method for an ignition signal, which is applied to a vehicle remote diagnosis system, where the vehicle remote diagnosis system includes a vehicle, a vehicle connector, a device connector, and a diagnosis device, and the method includes:
the vehicle connector acquires an ignition signal of the vehicle, encapsulates the ignition signal into a network data packet, and sends the network data packet to the equipment connector through remote communication;
the equipment connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to the diagnostic equipment;
and the diagnostic equipment judges whether the ignition signal meets a preset condition or not, and completes the ignition signal synchronization if the ignition signal meets the preset condition.
A second aspect of an embodiment of the present application provides a method for synchronizing an ignition signal, applied to a vehicle connector, the method including:
establishing an OBD connection with the vehicle;
acquiring an ignition signal of a vehicle;
packaging the ignition signal into a network data packet;
and sending the network data packet to an equipment connector through remote communication so that the equipment connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to diagnostic equipment, and then the diagnostic equipment judges whether the ignition signal meets a preset condition or not and completes ignition signal synchronization under the condition of meeting the preset condition.
In a possible implementation manner of the second aspect, the ignition signal comprises a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
the acquiring of the ignition signal of the vehicle specifically comprises:
establishing CANBus connection with the vehicle, configuring CANBus filtering parameters, and acquiring a CANBus ignition signal message of the vehicle;
and/or; acquiring an ignition signal level of a target pin of a vehicle OBD;
and/or; the supply voltage of the vehicle OBD is collected.
A third aspect of the embodiments of the present application provides a method for synchronizing an ignition signal, which is applied to a device connector, and includes:
receiving a network data packet sent by a vehicle connector through remote communication, wherein the network data packet is obtained by encapsulating an ignition signal by the vehicle connector, and the ignition signal is obtained from a vehicle by the vehicle connector;
analyzing the network data packet to obtain the ignition signal;
and sending the ignition signal to a diagnostic device so that the diagnostic device judges whether the ignition signal meets a preset condition or not, and completing ignition signal synchronization when the preset condition is met.
In a possible implementation manner of the third aspect, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
the sending the ignition signal to a diagnostic device specifically includes:
sending the CANBus ignition signal message to the diagnostic equipment through a CANBus network;
and/or; sending the ignition signal level on a target pin to the diagnostic device;
and/or; outputting a supply voltage associated with the supply voltage to the diagnostic device.
In a possible implementation manner of the third aspect, the sending the CANBus ignition signal message to the diagnostic device through the CANBus network specifically includes:
configuring CANBus terminal resistance parameters to establish a CANBus network;
and sending the CANBus ignition signal message to the diagnostic equipment through the CANBus network.
In a possible implementation manner of the third aspect, the outputting, to the diagnostic device, a power supply voltage associated with the power supply voltage specifically includes:
establishing communication connection with the diagnostic equipment and providing power supply for the diagnostic equipment;
outputting a supply voltage associated with the supply voltage to the diagnostic device.
A fourth aspect of an embodiment of the present application provides a method for synchronizing ignition signals, which is applied to a diagnostic device, and includes:
receiving an ignition signal sent by an equipment connector, wherein the ignition signal is obtained by analyzing a network data packet by the equipment connector; the network data packet is obtained by a vehicle connector package from an ignition signal acquired by a vehicle, and is sent to the equipment connector by the vehicle connector through remote communication;
and judging whether the ignition signal meets a preset condition, and if so, completing the ignition signal synchronization.
In a possible implementation manner of the fourth aspect, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
judging whether the ignition signal meets a preset condition or not, and finishing the ignition signal synchronization if the ignition signal meets the preset condition, wherein the method specifically comprises the following steps:
judging whether the CANBus ignition signal message contains ignition information, if so, judging that a preset condition is met, and completing ignition signal synchronization;
and/or; judging whether the level of the ignition signal is high level or low level, if so, meeting a preset condition, and completing the synchronization of the ignition signal;
and/or; and judging whether the power supply voltage is in a preset voltage range, if so, meeting a preset condition, and completing ignition signal synchronization.
A fifth aspect of an embodiment of the present application provides a vehicle connector including:
a memory for storing an executable computer program; a processor for invoking the executable computer program to perform and implement the method steps as described in the second aspect above.
A sixth aspect of embodiments of the present application provides a device connector, including:
a memory for storing an executable computer program; a processor for invoking the executable computer program to perform and implement the method steps as described in the third aspect above.
A seventh aspect of an embodiment of the present application provides a diagnostic apparatus, including:
a memory for storing an executable computer program; a processor for invoking the executable computer program to execute and implement the method steps as described in the fourth aspect above.
Compared with the prior art, the embodiment of the application has the beneficial effects that: the ignition signal of the vehicle is sent to the vehicle connector, the vehicle connector encapsulates the ignition signal into a network data packet, the network data packet is sent to the equipment connector through remote communication, the equipment connector analyzes the network data packet to obtain the ignition signal, the ignition signal is sent to the diagnosis equipment, the diagnosis equipment judges whether the ignition signal meets a preset condition, if yes, the ignition signal synchronization is completed, and therefore the ignition signal synchronization is achieved in the remote diagnosis process.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.
FIG. 1 is a schematic diagram of a vehicle remote diagnosis system provided by an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating an implementation of a synchronization method for an ignition signal provided by an embodiment of the present application;
FIG. 3 is a schematic flow chart of another implementation of a synchronization method for an ignition signal provided by an embodiment of the present application;
FIG. 4 is a schematic flow chart of another implementation of a synchronization method for an ignition signal provided by an embodiment of the present application;
FIG. 5 is a schematic flow chart illustrating a specific implementation of a synchronization method for an ignition signal according to an embodiment of the present application;
FIG. 6 is a schematic diagram of a synchronization device based on an ignition signal of a vehicle connector according to an embodiment of the present application;
FIG. 7 is a schematic diagram of a synchronization apparatus for an ignition signal based on a device connector according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a synchronization apparatus for ignition signals based on a diagnostic device according to an embodiment of the present application;
FIG. 9 is a schematic view of a vehicle connector provided by an embodiment of the present application;
FIG. 10 is a schematic view of a device connector provided by an embodiment of the present application;
fig. 11 is a schematic diagram of a diagnostic apparatus 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 structures, 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.
In order to explain the technical means described in the present application, the following description will be given by way of specific examples.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to a determination" or "in response to a detection". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
In addition, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not intended to indicate or imply relative importance.
The synchronization method of the ignition signal provided by the embodiment of the present application is applied to a vehicle remote diagnosis system, as shown in fig. 1, the vehicle remote diagnosis system provided by the embodiment of the present application includes a vehicle 100, a vehicle connector 200, a device connector 300 and a diagnosis device 400, the vehicle connector 200 and the device connector 300 are remotely connected in communication, for example, the communication can be performed by using a mobile communication network such as 3G/4G/5G, a wide area network or an ethernet network through a communication manner of peer-to-peer P2P or server data forwarding. The vehicle connector 100 is communicatively connected to the vehicle 300, for example, the vehicle 100 may supply power to the vehicle connector 200 through a ControLLer Area Network (CAN) protocol, a K-wire protocol, a J1708 protocol, or a J1850 protocol. The device connector 300 is communicatively coupled to the diagnostic device 400, for example, via a CAN protocol, a K-wire protocol, a J1708 protocol, or a J1850 protocol, and the diagnostic device 400 may be powered by the device connector 300. The vehicle connector 200 acquires an ignition signal sent by the vehicle 100, encapsulates the ignition signal into a network data packet, sends the network data packet to the equipment connector 300 through remote communication, the equipment connector 300 analyzes the network data packet to obtain the ignition signal, sends the ignition signal to the diagnostic equipment 400, and the diagnostic equipment 400 judges whether the ignition signal meets a preset condition or not, completes ignition signal synchronization if the ignition signal meets the preset condition, so that the ignition signal is synchronized to the diagnostic equipment when the vehicle conducts remote diagnosis.
The method for synchronizing the ignition signals provided by the embodiment of the present application is described below with reference to the vehicle remote diagnosis system shown in fig. 1.
Referring to fig. 2, fig. 2 shows a flow for implementing the synchronization method of the ignition signal provided by the embodiment of the present application, and the main execution body of the flow of the present application is the vehicle connector in the system shown in fig. 1. As shown in fig. 2, the method includes:
s201: an OBD connection is established with the vehicle.
Specifically, the vehicle connector establishes communication connection with an On Board Diagnostics (OBD) On the vehicle in a wired or wireless manner, and when the vehicle performs remote diagnosis, the vehicle connector initializes and establishes communication connection with the OBD On the vehicle through a preset protocol.
S202: an ignition signal of the vehicle is acquired.
Specifically, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage. For a particular vehicle to be diagnosed, the ignition signal may be one, two, or even three of the three types described above. In the specific ignition signal synchronization process, the ignition signal synchronization can be realized only if one is effective. The ignition signal of the vehicle is output through the OBD pin, and different ignition signals correspond to different output pins.
For example, the CANBus ignition signal message is typically output by the 6PIN and 14PIN PINs of the vehicle, the ignition signal level is typically output by the 1PIN or 8PIN PINs, and the supply voltage is typically output by the 16PIN PINs. In a possible implementation manner, after a vehicle is started, the vehicle connector acquires vehicle state information sent by the vehicle OBD through PINs 1PIN, 6PIN, 8PIN, 14PIN and 16PIN under the condition that vehicle information is unknown, wherein valid vehicle state information is an ignition signal. The valid vehicle state information may be any one of a CANBus ignition signal message, an ignition signal level, a supply voltage, or a combination of any two or three of them.
Specifically, the obtaining of the CANBus ignition signal message specifically includes: the vehicle connector establishes CANBus connection with a vehicle through a CAN protocol, configures CANBus filtering parameters and obtains a CANBus ignition signal message of the vehicle. In a specific implementation manner, after the CANBus connector establishes CANBus connection with the vehicle, the CANBus filter filters the acquired vehicle message, that is, filters out the message which is not encoded according to the CANBus data format, so as to obtain a filtered CANBus message, and determines the CANBus message containing the ignition signal as a CANBus ignition signal message.
Specifically, the acquiring of the ignition signal level specifically includes: the vehicle connector collects the ignition signal level of the vehicle OBD target pin. The vehicle connector can acquire the level of the ignition signal in a logic level acquiring mode, or acquire the level through the analog-digital converter, namely, the analog signal corresponding to the level is converted into the digital signal.
Specifically, acquiring the supply voltage specifically includes: the vehicle connector collects the supply voltage of the vehicle OBD. The power supply voltage of the vehicle OBD is generally output by a 16PIN of the vehicle OBD, that is, by a power supply PIN of the vehicle OBD. The supply voltage may be obtained by collecting a voltage of a power pin of the vehicle OBD.
Since the ignition signal of the vehicle to be diagnosed may be any one of, or a combination of any two of, or a combination of three of the CANBus ignition signal message, the ignition signal level, and the power supply voltage, the corresponding ignition signal acquisition manner may also be any one of, or a combination of any two of, or a combination of three of the above-mentioned acquisition manners. And is not particularly limited herein.
S203: and packaging the ignition signal into a network data packet.
After acquiring the ignition signal of the vehicle, the vehicle connector performs data encapsulation on the ignition signal so as to encapsulate the ignition signal into a network data packet. Specifically, the encapsulation method used for encapsulating the network data packet is related to the transmission protocol used in the subsequent remote communication. For example, if the subsequent transmission is performed by HyperText Transfer Protocol (HTTP), the step encapsulates the ignition signal based on HTTP Protocol. That is, the network packet is embodied in the form of an HTTP packet. The encapsulation process is not specifically limited herein.
In a preferred embodiment, the vehicle connector encapsulates the vehicle status information and the verification data into a network data packet. The check data can be obtained according to the MD5 message digest algorithm or the CRC algorithm, so that the device connector or the diagnostic device can check the check data, thereby improving the security of data transmission.
S204: and sending the network data packet to an equipment connector through remote communication so that the equipment connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to diagnostic equipment, and then the diagnostic equipment judges whether the ignition signal meets a preset condition or not and completes ignition signal synchronization under the condition of meeting the preset condition.
Specifically, the vehicle connector transmits the network data packet to the equipment connector through remote communication, so that the equipment connector analyzes the network data packet to obtain an ignition signal and transmits the ignition signal to the diagnosis equipment. The diagnosis equipment further judges whether a preset condition is met or not according to the received ignition signal, and completes ignition signal synchronization under the condition that the preset condition is met. The remote communication can be point-to-point P2P communication or server forwarding. The network for remote communication may be a mobile communication network such as 3G, 4G, 5G, etc., and may also be a wide area network, ethernet, etc.
In the above embodiment, the vehicle connector acquires an ignition signal of a vehicle, encapsulates the ignition signal into a network data packet, and sends the network data packet to the device connector through remote communication, and the device connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to the diagnostic device, and the diagnostic device determines whether the ignition signal meets a preset condition, and if the ignition signal meets the preset condition, completes the ignition signal synchronization, thereby realizing the ignition signal synchronization in the remote diagnosis process.
Referring to fig. 3, fig. 3 shows a flow for implementing the synchronization method of the ignition signal provided in the embodiment of the present application, and a main body of the flow in the embodiment is the device connector in the system shown in fig. 1. As shown in fig. 3, the method includes:
s301: receiving a network data packet sent by a vehicle connector through remote communication, wherein the network data packet is obtained by encapsulating an ignition signal by the vehicle connector, and the ignition signal is obtained from a vehicle by the vehicle connector.
Specifically, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage. The vehicle connector acquires the ignition signal of the vehicle through a specific PIN of the vehicle OBD, such as acquiring a CANBus ignition signal message through 6PIN and 14PIN, and/or acquiring the level of the ignition signal through 1PIN or 8PIN, and/or acquiring the power supply voltage through 16 PIN. After acquiring the vehicle ignition signal, the vehicle connector encapsulates the vehicle ignition signal into a network data packet suitable for remote communication transmission, and then sends the network data packet to the equipment connector through remote communication. With regard to the specific manner in which the vehicle connector acquires the vehicle ignition signal, as well as the packaging manner and the remote communication manner, reference may be made to the above specific contents of the method embodiment of the vehicle connector. And will not be described in detail herein.
S302: and analyzing the network data packet to obtain the ignition signal.
And after receiving the network data packet, the equipment connector analyzes the network data packet to obtain an ignition signal in the network data packet. Based on the network data packet encapsulated by the vehicle connector, the ignition signal parsed by the device connector at this time includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage.
In a preferred implementation manner, the network data packet received by the device connector includes the verification data, the device connector parses the network data packet to obtain the vehicle ignition information and the verification data, verifies the verification data, and if the verification passes, S303 is executed. The specific check rule may perform the check based on the MD5 message digest algorithm, or perform the check according to the CRC algorithm, which is not specifically limited herein.
S303: and sending the ignition signal to a diagnosis device so that the diagnosis device judges whether the ignition signal meets a preset condition or not and completes ignition signal synchronization when the preset condition is met.
After the device connector obtains the vehicle ignition signal through analysis, firstly, whether the ignition signal is one or two or three combinations of a CANBus ignition signal message, an ignition signal level and a power supply voltage is determined, after the type of the ignition signal is determined, a corresponding sending mode of the vehicle ignition signal is further determined according to the type of the ignition signal, and then the vehicle ignition signal is sent to the diagnostic device based on the corresponding sending mode, so that the diagnostic device judges whether the ignition signal meets a preset condition or not, and completes ignition signal synchronization when the preset condition is met.
Specifically, when the ignition signal comprises a CANBus ignition signal message, the device connector sends the CANBus ignition signal message to the diagnostic device via the CANBus network. Further, the device connector configures CANBus terminal resistance parameters to establish a CANBus network, and then sends the CANBus ignition signal message to the diagnostic device through the CANBus network. In a specific implementation manner, the configured CANBus terminal resistance is 60-120 Ω, and specific parameters can be determined according to a specific vehicle type of a vehicle to be diagnosed. After the CANBus terminal resistor is configured, according to CANBus configuration of different vehicle types, a CAN node inside the equipment connector and a CAN node of the diagnostic equipment jointly establish one or more groups of CANBus bus networks, so that CANBus connection with the diagnostic equipment is established, and the CANBus ignition signal message is sent to the diagnostic equipment through the CANBus network.
Specifically, when the ignition signal includes an ignition signal level, the device connector sends the ignition signal level to the diagnostic device by sending the ignition signal level on the target pin. In one particular implementation, the device connector is configured with an analog OBD interface for simulating a vehicle OBD interface, through which an analog OBD connection is established with the diagnostic device, and then the ignition signal level is output through a specific PIN of the interface, such as 1PIN or 8 PIN.
Specifically, when the ignition signal includes a supply voltage, the device connector outputs a supply voltage associated with the supply voltage to the diagnostic device. In one particular implementation, the device connector establishes a communication connection with the diagnostic device and provides power to the diagnostic device. The device connector outputs a supply voltage associated with the supply voltage to the diagnostic device after parsing the network data packet to obtain an ignition signal including the supply voltage. Wherein the power supply voltage associated with the power supply voltage is a power supply voltage that is the same or similar in voltage value to the power supply voltage. For example, if the supply voltage in the ignition signal is 14V, then the supply voltage may be 13.5V-14.5V; if the supply voltage in the ignition signal is 27V, the supply voltage may be 26.5V-27.5V.
Since the ignition signal in the network data packet may be any one of, or any two of, a CANBus ignition signal message, an ignition signal level, and a power supply voltage, or any three of them, the transmission manner in which the device connector transmits the ignition signal to the diagnostic device is any one of, or any two of, or three of the above-mentioned transmission manners, and the specific transmission manner corresponds to the type of the ignition signal analyzed from the network data packet.
In the above embodiment, the device connector obtains the network data packet sent by the vehicle connector through the remote communication, analyzes the network data packet to obtain the ignition signal, and then sends the ignition signal to the diagnostic device, and the diagnostic device determines whether the ignition signal meets a preset condition, and if so, completes the synchronization of the ignition signal, thereby implementing the synchronization of the ignition signal in the remote diagnosis process.
Referring to fig. 4, fig. 4 shows a flow for implementing the synchronization method of the ignition signal provided by the embodiment of the present application, and a main body of the flow of the present application is a diagnostic device in the system shown in fig. 1. As shown in fig. 4, the method includes:
s401: receiving an ignition signal sent by an equipment connector, wherein the ignition signal is obtained by analyzing a network data packet by the equipment connector; the network data packet is derived by a vehicle connector package from an ignition signal acquired from a vehicle and transmitted by the vehicle connector to the device connector by remote communication.
Specifically, the diagnostic device receives an ignition signal sent by the device connector, the ignition signal including a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage. The ignition signal is obtained by the device connector parsing a network packet obtained by the vehicle connector package from the ignition signal obtained from the vehicle and sent by the vehicle connector to the device connector by remote communication. For the specific implementation manner of the vehicle connector acquiring the vehicle ignition signal, the encapsulation manner and the remote communication manner, and the specific implementation manner of the device connector analyzing the network data packet and sending the ignition signal, reference may be made to the above embodiment of the ignition signal synchronization method based on the vehicle connector and the embodiment of the ignition signal synchronization method based on the device connector, and details are not repeated here.
S402: and judging whether the ignition signal meets a preset condition, and if so, completing the ignition signal synchronization.
Specifically, when the ignition signal includes a CANBus ignition signal message, the diagnostic device determines whether the CANBus ignition signal message includes ignition information, and if so, determines that a preset condition is met, that is, the vehicle is ignited, and the ignition signal synchronization is completed.
Specifically, when the ignition signal includes an ignition signal level, the diagnostic device judges whether the ignition signal is a high level or a low level, and if the ignition signal is the high level, the vehicle is considered to be ignited, and the ignition signal synchronization is completed; if the level is low, the vehicle is turned off, and signal synchronization is not required at this time.
Specifically, when the ignition signal includes the supply voltage, the diagnostic device determines whether the supply voltage is within a preset voltage range, and if so, the preset condition is met, and the ignition signal synchronization is completed. In one specific implementation, when the supply voltage is higher than 12V or higher than 24V, it is considered that the vehicle is ignited, and the preset condition is satisfied, and the diagnostic device completes the ignition signal synchronization. Specifically, for a passenger vehicle, the flameout voltage is 12V, and when the supply voltage is higher than 12V, for example, 13V or even 14V is reached, the diagnostic device determines that the passenger vehicle is started at ignition, so that the ignition signal synchronization can be completed; for a commercial vehicle, 24V at the cut-off voltage, when the supply voltage is higher than 24V, for example, 25V or even 27V, the diagnostic device determines that the commercial vehicle is in ignition start, so that the ignition signal synchronization can be completed.
In the above embodiment, the diagnostic device receives the ignition signal sent by the device connector, and determines whether the ignition signal meets a preset condition according to specific characteristic parameters of the ignition signal, and if so, completes the synchronization of the ignition signal, thereby implementing the remote synchronization of the ignition signal.
Referring to fig. 5, fig. 5 shows a specific implementation flow of the synchronization method for the ignition signal provided by the embodiment of the present application. As shown in fig. 5, the method includes:
s501: the vehicle connector acquires an ignition signal of a vehicle to be diagnosed, encapsulates the ignition signal into a network data packet, and sends the network data packet to the equipment connector through remote communication.
S502: the equipment connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to the diagnostic equipment.
S503: and the diagnosis equipment judges whether the ignition signal meets a preset condition or not, and completes the synchronization of the ignition signal if the ignition signal meets the preset condition.
The specific implementation of steps S501-S503 can refer to the above embodiments of the vehicle connector-based ignition signal synchronization method, the device connector-based ignition signal synchronization method, and the diagnostic device-based ignition signal synchronization method. And will not be described in detail herein.
In the above embodiment, the vehicle connector acquires an ignition signal of a vehicle, encapsulates the ignition signal into a network data packet, and sends the network data packet to the device connector through remote communication, and the device connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to the diagnostic device, and the diagnostic device determines whether the ignition signal meets a preset condition, and if the ignition signal meets the preset condition, completes the ignition signal synchronization, thereby realizing the ignition signal synchronization in the remote diagnosis process.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
The method for synchronizing the ignition signals is described above, and the structure for implementing the method for synchronizing the ignition signals is described in detail below. The relevant contents may be referred to above.
As shown in fig. 6, the synchronization apparatus for an ignition signal of a vehicle connector according to the embodiment of the present application includes,
a connection module 610 for establishing an OBD connection with a vehicle;
a first obtaining module 620, configured to obtain an ignition signal of a vehicle;
an encapsulating module 630, configured to encapsulate the ignition signal as a network data packet;
the first sending module 640 is configured to send the network data packet to an equipment connector through remote communication, so that the equipment connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to a diagnostic device, and then the diagnostic device determines whether the ignition signal meets a preset condition, and completes ignition signal synchronization when the preset condition is met.
In one possible implementation, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
the first obtaining module 620 is specifically configured to:
establishing CANBus connection with the vehicle, configuring CANBus filtering parameters, and acquiring a CANBus ignition signal message of the vehicle;
and/or; acquiring an ignition signal level of a target pin of an OBD (on-board diagnostics) of a vehicle;
and/or; the supply voltage of the vehicle OBD is collected.
As shown in fig. 7, the synchronization apparatus for an ignition signal based on a device connector according to the embodiment of the present application includes:
a receiving module 710, configured to receive a network data packet sent by a vehicle connector through remote communication, where the network data packet is obtained by encapsulating, by the vehicle connector, an ignition signal, and the ignition signal is obtained from a vehicle by the vehicle connector;
an analyzing module 720, configured to analyze the network data packet to obtain the ignition signal;
the second sending module 730 is configured to send the ignition signal to a diagnostic device, so that the diagnostic device determines whether the ignition signal meets a preset condition, and completes ignition signal synchronization when the preset condition is met.
In one possible implementation, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
the second sending module 730 is specifically configured to:
sending the CANBus ignition signal message to the diagnostic equipment through a CANBus network;
and/or; sending the ignition signal level on a target pin to the diagnostic device;
and/or; outputting a supply voltage associated with the supply voltage to the diagnostic device.
In a possible implementation manner, the second sending module 230 is further specifically configured to:
configuring CANBus terminal resistance parameters to establish a CANBus network;
and sending the CANBus ignition signal message to the diagnostic equipment through the CANBus network.
In a possible implementation manner, the second sending module 730 is further specifically configured to:
establishing communication connection with the diagnostic equipment and providing power supply for the diagnostic equipment;
outputting a supply voltage associated with the supply voltage to the diagnostic device.
As shown in fig. 8, an embodiment of the present application provides a synchronization apparatus for an ignition signal based on a diagnostic device, including:
a second obtaining module 810, configured to receive an ignition signal sent by an equipment connector, where the ignition signal is obtained by analyzing a network data packet by the equipment connector; the network data packet is obtained by encapsulating an ignition signal acquired from a vehicle by a vehicle connector and is sent to the equipment connector by the vehicle connector through remote communication;
the determining module 820 is configured to determine whether the ignition signal meets a preset condition, and if so, complete the ignition signal synchronization.
In one possible implementation, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
the determining module 820 is specifically configured to:
judging whether the CANBus ignition signal message contains ignition information, if so, judging that a preset condition is met, and completing ignition signal synchronization;
and/or; judging whether the level of the ignition signal is high level or low level, if so, meeting a preset condition, and completing the synchronization of the ignition signal;
and/or; and judging whether the power supply voltage is in a preset voltage range, if so, meeting a preset condition, and completing ignition signal synchronization.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
Fig. 9 is a schematic view of a vehicle connector provided in an embodiment of the present application. As shown in fig. 9, the vehicle connector of this embodiment includes: a processor 11, a memory 12 and a computer program 13 stored in said memory 12 and executable on said processor 11. The processor 11, when invoking the computer program 13, implements:
establishing an OBD connection with the vehicle;
acquiring an ignition signal of a vehicle;
packaging the ignition signal into a network data packet;
and sending the network data packet to an equipment connector through remote communication so that the equipment connector analyzes the network data packet to obtain the ignition signal and sends the ignition signal to diagnostic equipment, and then the diagnostic equipment judges whether the ignition signal meets a preset condition or not and completes ignition signal synchronization under the condition of meeting the preset condition.
In one possible implementation, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage; the processor 11, when invoking the computer program 13, further implements:
establishing CANBus connection with the vehicle, configuring CANBus filtering parameters, and acquiring a CANBus ignition signal message of the vehicle;
and/or;
acquiring an ignition signal level of a target pin of an OBD (on-board diagnostics) of a vehicle;
and/or;
the supply voltage of the vehicle OBD is collected.
Illustratively, the computer program 13 may be partitioned into one or more modules/units, which are stored in the memory 12 and executed by the processor 11 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 13 in the vehicle connector.
The vehicle connector may be a computing device such as a desktop computer, a notebook, a palmtop computer, or the like. Those skilled in the art will appreciate that fig. 9 is merely an example of a vehicle connector, and does not constitute a limitation of a vehicle connector, and may include more or fewer components than shown, or some components in combination, or different components, for example, the vehicle connector may also include input-output devices, network access devices, buses, etc.
The Processor 11 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 12 may be an internal storage unit of the vehicle connector, such as a hard disk or a memory of the vehicle connector. The memory 12 may also be an external storage device of the vehicle connector, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the vehicle connector. Further, the memory 12 may also include both an internal storage unit of the vehicle connector and an external storage device. The memory 12 is used for storing the computer program and other programs and data required for the vehicle connector. The memory 12 may also be used to temporarily store data that has been output or is to be output.
Fig. 10 is a schematic diagram of a device connector provided by an embodiment of the present application. As shown in fig. 10, the device connector of this embodiment includes: a processor 21, a memory 22 and a computer program 23 stored in said memory 22 and executable on said processor 21. The processor 21, when invoking the computer program 23, implements:
receiving a network data packet sent by a vehicle connector through remote communication, wherein the network data packet is obtained by encapsulating an ignition signal by the vehicle connector, and the ignition signal is obtained from a vehicle by the vehicle connector;
analyzing the network data packet to obtain the ignition signal;
and sending the ignition signal to a diagnosis device so that the diagnosis device judges whether the ignition signal meets a preset condition or not and completes ignition signal synchronization when the preset condition is met.
In one possible implementation, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage; the processor 21, when invoking the computer program 23, further implements:
sending the CANBus ignition signal message to the diagnostic equipment through a CANBus network;
and/or;
sending the ignition signal level on a target pin to the diagnostic device;
and/or;
outputting a supply voltage associated with the supply voltage to the diagnostic device.
In a possible implementation manner, the processor 21, when invoking the computer program 23, further implements:
configuring CANBus terminal resistance parameters to establish a CANBus network;
and sending the CANBus ignition signal message to the diagnostic equipment through the CANBus network.
In a possible implementation manner, when the processor 21 calls the computer program 23, the following is further implemented:
establishing communication connection with the diagnostic equipment and providing power supply for the diagnostic equipment;
outputting a supply voltage associated with the supply voltage to the diagnostic device.
Illustratively, the computer program 23 may be partitioned into one or more modules/units, which are stored in the memory 22 and executed by the processor 21 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 23 in the device connector.
The device connector can be a desktop computer, a notebook computer, a palm computer and other computing devices. Those skilled in the art will appreciate that fig. 10 is merely an example of a device connector and does not constitute a limitation of a device connector and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the device connector may also include input output devices, network access devices, buses, etc.
The Processor 21 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 22 may be an internal storage unit of the device connector, such as a hard disk or a memory of the device connector. The memory 22 may also be an external storage device of the device connector, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the device connector. Further, the memory 22 may also include both an internal storage unit of the device connector and an external storage device. The memory 22 is used for storing the computer program and other programs and data required by the device connector. The memory 22 may also be used to temporarily store data that has been output or is to be output.
Fig. 11 is a schematic diagram of a diagnostic apparatus provided in an embodiment of the present application. As shown in fig. 11, the diagnostic apparatus of this embodiment includes: a processor 31, a memory 32 and a computer program 33 stored in said memory 32 and executable on said processor 31. The processor 31, when invoking the computer program 33, implements:
receiving an ignition signal sent by an equipment connector, wherein the ignition signal is obtained by analyzing a network data packet by the equipment connector; the network data packet is obtained by encapsulating an ignition signal acquired from a vehicle by a vehicle connector and is sent to the equipment connector by the vehicle connector through remote communication;
and judging whether the ignition signal meets a preset condition, and if so, completing the ignition signal synchronization.
In one possible implementation, the ignition signal includes a CANBus ignition signal message, and/or an ignition signal level, and/or a supply voltage;
the processor 31, when invoking the computer program 33, further implements:
judging whether the CANBus ignition signal message contains ignition information, if so, judging that a preset condition is met, and completing ignition signal synchronization;
and/or;
judging whether the level of the ignition signal is high level or low level, if the level is high level, meeting the preset condition, and completing the synchronization of the ignition signal;
and/or;
and judging whether the power supply voltage is in a preset voltage range, if so, meeting a preset condition, and completing ignition signal synchronization.
Illustratively, the computer program 33 may be partitioned into one or more modules/units that are stored in the memory 32 and executed by the processor 31 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 33 in the device connector.
The diagnosis device can be a desktop computer, a notebook computer, a palm computer and other computing devices. It will be understood by those skilled in the art that fig. 11 is merely an example of a diagnostic device and is not intended to be limiting and may include more or fewer components than shown, or some components in combination, or different components, for example, the diagnostic device may also include input output devices, network access devices, buses, etc.
The Processor 31 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 32 may be an internal storage unit of the diagnostic device, such as a hard disk or a memory of a device connector. The memory 32 may also be an external storage device of the diagnostic device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), etc. provided on the diagnostic device. Further, the memory 32 may also include both an internal storage unit of the device connector and an external storage device. The memory 32 is used for storing the computer program and other programs and data required by the diagnostic device. The memory 32 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of 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 processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like.
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 implementation. 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.
The above-mentioned embodiments are only used to illustrate the technical solutions of the present application, and not to limit 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 solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A synchronization method of ignition signals is characterized by being applied to a vehicle remote diagnosis system, wherein the vehicle remote diagnosis system comprises a vehicle, a vehicle connector, a device connector and a diagnosis device, and the method comprises the following steps:
the vehicle connector acquires an ignition signal of the vehicle under the condition that vehicle information is unknown, encapsulates the ignition signal into a network data packet, and sends the network data packet to the equipment connector through remote communication; the ignition signal is effective vehicle state information obtained from a designated pin of the OBD of the vehicle, the designated pin is a pin corresponding to a CANBus ignition signal message, a pin corresponding to an ignition signal level and a pin corresponding to a power supply voltage, and the effective vehicle state information is one or more of the CANBus ignition signal message, the ignition signal level and the power supply voltage;
the equipment connector analyzes the network data packet to obtain the ignition signal; determining the type of the ignition signal, and when the ignition signal comprises a CANBus ignition signal message, sending the CANBus ignition signal message to the diagnostic equipment through a CANBus network; the device connector is configured with an analog OBD interface for simulating the OBD interface of the vehicle, when the ignition signal comprises an ignition signal level, establishing analog OBD connection with the diagnostic device through the analog OBD interface, and sending the ignition signal level to the diagnostic device through a target pin of the analog OBD interface; outputting a supply voltage associated with the supply voltage to the diagnostic device when the ignition signal includes the supply voltage;
the diagnosis equipment judges whether the ignition signal meets a preset condition or not, and if yes, ignition signal synchronization is finished; when the ignition signal comprises a CANBus ignition signal message, the diagnosis equipment judges whether the CANBus ignition signal message contains ignition information, if so, the diagnosis equipment judges that a preset condition is met, and ignition signal synchronization is completed; when the ignition signal comprises an ignition signal level, the diagnosis equipment judges whether the ignition signal is a high level or a low level, and if the ignition signal is the high level, the ignition signal synchronization is finished; if the level is low, signal synchronization is not needed; when the ignition signal comprises a power supply voltage, the diagnosis equipment judges whether the power supply voltage is in a preset voltage range, if so, a preset condition is met, and the ignition signal synchronization is completed.
2. A method of synchronizing an ignition signal, applied to a vehicle connector, the method comprising:
establishing an OBD connection with the vehicle;
acquiring an ignition signal of the vehicle under the condition that the vehicle information is unknown; the ignition signal is effective vehicle state information obtained from a designated pin of the OBD of the vehicle, the designated pin is a pin corresponding to a CANBus ignition signal message, a pin corresponding to an ignition signal level and a pin corresponding to a power supply voltage, and the effective vehicle state information is one or more of the CANBus ignition signal message, the ignition signal level and the power supply voltage;
packaging the ignition signal into a network data packet;
sending the network data packet to an equipment connector through remote communication so that the equipment connector analyzes the network data packet to obtain the ignition signal, determining the type of the ignition signal, and sending a CANBus ignition signal message to diagnostic equipment through a CANBus network when the ignition signal comprises a CANBus ignition signal message; the device connector is configured with an analog OBD interface for simulating the OBD interface of the vehicle, when the ignition signal comprises an ignition signal level, establishing analog OBD connection with the diagnostic device through the analog OBD interface, and sending the ignition signal level to the diagnostic device through a target pin of the analog OBD interface; outputting a supply voltage associated with the supply voltage to the diagnostic device when the ignition signal includes the supply voltage; the diagnosis equipment judges whether the ignition signal meets a preset condition or not, and completes ignition signal synchronization under the condition that the preset condition is met; when the ignition signal comprises a CANBus ignition signal message, the diagnosis equipment judges whether the CANBus ignition signal message contains ignition information, if so, the diagnosis equipment judges that a preset condition is met, and ignition signal synchronization is completed; when the ignition signal comprises an ignition signal level, the diagnosis equipment judges whether the ignition signal is a high level or a low level, and if the ignition signal is the high level, the ignition signal synchronization is finished; if the level is low, signal synchronization is not needed; when the ignition signal comprises a power supply voltage, the diagnosis equipment judges whether the power supply voltage is in a preset voltage range, if so, a preset condition is met, and the ignition signal synchronization is completed.
3. The method for synchronizing ignition signals according to claim 2,
the acquiring of the ignition signal of the vehicle specifically comprises one or more of the following steps:
establishing CANBus connection with the vehicle, configuring CANBus filtering parameters, and acquiring a CANBus ignition signal message of the vehicle;
acquiring an ignition signal level of a target pin of an OBD (on-board diagnostics) of a vehicle;
the supply voltage of the vehicle OBD is collected.
4. A method of synchronizing firing signals, applied to a device connector, the method comprising:
receiving a network data packet sent by a vehicle connector through remote communication, wherein the network data packet is obtained by encapsulating an ignition signal by the vehicle connector, and the ignition signal is obtained by the vehicle connector from a vehicle under the condition that vehicle information is unknown; the ignition signal is effective vehicle state information acquired by the vehicle connector from a designated pin of an OBD of the vehicle, the designated pin is a pin corresponding to a CANBus ignition signal message, a pin corresponding to an ignition signal level and a pin corresponding to a power supply voltage, and the effective vehicle state information is one or more of the CANBus ignition signal message, the ignition signal level and the power supply voltage;
analyzing the network data packet to obtain the ignition signal;
determining the type of the ignition signal, and when the ignition signal comprises a CANBus ignition signal message, sending the CANBus ignition signal message to diagnostic equipment through a CANBus network; the device connector is configured with an analog OBD interface for simulating the OBD interface of the vehicle, when the ignition signal comprises an ignition signal level, establishing analog OBD connection with the diagnostic device through the analog OBD interface, and sending the ignition signal level to the diagnostic device through a target pin of the analog OBD interface; outputting a supply voltage associated with the supply voltage to the diagnostic device when the ignition signal includes the supply voltage; so that the diagnosis equipment judges whether the ignition signal meets a preset condition or not and completes the ignition signal synchronization when the preset condition is met; when the ignition signal comprises a CANBus ignition signal message, the diagnosis equipment judges whether the CANBus ignition signal message contains ignition information, if so, the diagnosis equipment judges that a preset condition is met, and ignition signal synchronization is completed; when the ignition signal comprises an ignition signal level, the diagnosis equipment judges whether the ignition signal is a high level or a low level, and if the ignition signal is the high level, the ignition signal synchronization is finished; if the level is low, signal synchronization is not needed; when the ignition signal comprises a power supply voltage, the diagnosis equipment judges whether the power supply voltage is in a preset voltage range, if so, a preset condition is met, and the ignition signal synchronization is completed.
5. The method for synchronizing ignition signals according to claim 4, wherein the sending the CANBus ignition signal message to the diagnostic device via a CANBus network comprises:
configuring CANBus terminal resistance parameters to establish a CANBus network;
and sending the CANBus ignition signal message to the diagnostic equipment through the CANBus network.
6. The method for synchronizing an ignition signal according to claim 4, wherein the outputting a supply voltage associated with the supply voltage to the diagnostic device specifically comprises:
establishing communication connection with the diagnostic equipment and providing power supply for the diagnostic equipment;
outputting a supply voltage associated with the supply voltage to the diagnostic device.
7. A method of synchronizing an ignition signal, for use in a diagnostic device, the method comprising:
receiving an ignition signal sent by an equipment connector, wherein the ignition signal is obtained by analyzing a network data packet by the equipment connector; the ignition signal is effective vehicle state information acquired by a vehicle connector from a designated pin of an OBD of the vehicle, the designated pin is a pin corresponding to a CANBus ignition signal message, a pin corresponding to an ignition signal level and a pin corresponding to a power supply voltage, and the effective vehicle state information is one or more of the CANBus ignition signal message, the ignition signal level and the power supply voltage; the network data packet is obtained by encapsulating an ignition signal acquired from a vehicle by a vehicle connector under the condition that vehicle information is unknown, and is sent to the equipment connector by the vehicle connector through remote communication; the equipment connector is used for determining the type of the ignition signal, and when the ignition signal comprises a CANBus ignition signal message, the CANBus ignition signal message is sent to the diagnostic equipment through a CANBus network; the device connector is configured with an analog OBD interface for simulating the OBD interface of the vehicle, when the ignition signal comprises an ignition signal level, establishing analog OBD connection with the diagnostic device through the analog OBD interface, and sending the ignition signal level to the diagnostic device through a target pin of the analog OBD interface; when the ignition signal comprises a supply voltage, outputting a supply voltage associated with the supply voltage to the diagnostic device;
judging whether the ignition signal meets a preset condition or not, and finishing the synchronization of the ignition signal if the ignition signal meets the preset condition; when the ignition signal comprises a CANBus ignition signal message, judging whether the CANBus ignition signal message contains ignition information, if so, judging that a preset condition is met, and completing ignition signal synchronization; when the ignition signal comprises an ignition signal level, judging whether the ignition signal is a high level or a low level, and if the ignition signal is the high level, completing ignition signal synchronization; if the level is low, signal synchronization is not needed; and when the ignition signal comprises a power supply voltage, judging whether the power supply voltage is in a preset voltage range, if so, meeting a preset condition, and completing the synchronization of the ignition signal.
8. A vehicle connector, characterized in that the vehicle connector comprises:
a memory for storing an executable computer program;
a processor for invoking said executable computer program to perform and implement the method steps of claim 2 or 3.
9. A device connector, characterized in that the device connector comprises:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform and implement the method steps of any of claims 4 to 6.
10. A diagnostic apparatus, characterized in that the diagnostic apparatus comprises:
a memory for storing an executable computer program;
a processor for invoking the executable computer program to perform and implement the method steps of claim 7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010406514.2A CN111740888B (en) | 2020-05-14 | 2020-05-14 | Ignition signal synchronization method and related equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010406514.2A CN111740888B (en) | 2020-05-14 | 2020-05-14 | Ignition signal synchronization method and related equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN111740888A CN111740888A (en) | 2020-10-02 |
CN111740888B true CN111740888B (en) | 2022-09-20 |
Family
ID=72647224
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010406514.2A Active CN111740888B (en) | 2020-05-14 | 2020-05-14 | Ignition signal synchronization method and related equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111740888B (en) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN2914192Y (en) * | 2006-05-29 | 2007-06-20 | 杨少军 | Car trouble network diagnostic system |
CN104850113A (en) * | 2014-11-14 | 2015-08-19 | 北汽福田汽车股份有限公司 | Automobile remote diagnostic system and method |
CN107000686A (en) * | 2014-09-29 | 2017-08-01 | 莱尔德无线技术(上海)有限公司 | Remote information process device and the method detected for vehicle ignition |
CN109194730A (en) * | 2018-08-24 | 2019-01-11 | 驾图信科技有限公司 | Vehicle information acquisition system and method based on block chain |
CN109218001A (en) * | 2017-07-05 | 2019-01-15 | 福特全球技术公司 | Method and apparatus for fired state monitoring |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170039784A1 (en) * | 2012-06-21 | 2017-02-09 | Autobrain Llc | Automobile diagnostic device using dynamic telematic data parsing |
CN105675304A (en) * | 2016-01-04 | 2016-06-15 | 杭州科技职业技术学院 | Automobile engine on-line monitoring system |
CN109861388B (en) * | 2018-12-20 | 2022-06-24 | 江苏迪纳数字科技股份有限公司 | Remote monitoring method of vehicle-mounted intelligent terminal |
-
2020
- 2020-05-14 CN CN202010406514.2A patent/CN111740888B/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN2914192Y (en) * | 2006-05-29 | 2007-06-20 | 杨少军 | Car trouble network diagnostic system |
CN107000686A (en) * | 2014-09-29 | 2017-08-01 | 莱尔德无线技术(上海)有限公司 | Remote information process device and the method detected for vehicle ignition |
CN104850113A (en) * | 2014-11-14 | 2015-08-19 | 北汽福田汽车股份有限公司 | Automobile remote diagnostic system and method |
CN109218001A (en) * | 2017-07-05 | 2019-01-15 | 福特全球技术公司 | Method and apparatus for fired state monitoring |
CN109194730A (en) * | 2018-08-24 | 2019-01-11 | 驾图信科技有限公司 | Vehicle information acquisition system and method based on block chain |
Also Published As
Publication number | Publication date |
---|---|
CN111740888A (en) | 2020-10-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111208800B (en) | Automobile diagnosis method and device and vehicle communication interface | |
CN108227675B (en) | Vehicle diagnosis method, device, terminal and computer-readable storage medium | |
US11665018B2 (en) | OBD interface bus type detection method and apparatus | |
CN108803580B (en) | Method for matching vehicle CAN protocol and related equipment | |
EP3809223B1 (en) | Vehicle remote diagnosis method and related apparatus | |
US8983714B2 (en) | Failsafe communication system and method | |
CN111538312B (en) | Vehicle remote diagnosis method, system, equipment connector and vehicle connector | |
US9208624B2 (en) | Time window authentication for vehicle telematics device | |
US8798843B2 (en) | Vehicle diagnosing apparatus | |
US9451028B2 (en) | Communication profile selection for vehicle telematics device | |
CN104734911A (en) | CAN bus network management test system and method | |
US11514731B2 (en) | Method and system for remote vehicle diagnostics | |
CN111427335A (en) | Vehicle remote diagnosis method, equipment connector and vehicle connector | |
CN111506047B (en) | Vehicle diagnosis method, device and storage medium | |
CN114253251A (en) | Vehicle remote diagnosis method and device, equipment connector and storage medium | |
CN113608518B (en) | Data generation method, device, terminal equipment and medium | |
CN109857085B (en) | Method and system for generating driving data in simulation mode, simulation terminal and test system | |
CN112927392A (en) | Communication method, vehicle communication interface device and readable storage medium | |
CN111552266B (en) | Vehicle remote diagnosis method, system, equipment connector and vehicle connector | |
CN113110391A (en) | Vehicle data transmission method, diagnosis terminal and server | |
CN113406944A (en) | Vehicle diagnosis method, apparatus, device and computer readable storage medium | |
CN111552268A (en) | Vehicle remote diagnosis method, equipment connector and vehicle connector | |
CN112817888B (en) | OBD device state setting method and device, OBD device and storage medium | |
CN111740888B (en) | Ignition signal synchronization method and related equipment | |
CN111683347B (en) | Ignition signal synchronization method and related equipment |
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 |