CN112927392A - Communication method, vehicle communication interface device and readable storage medium - Google Patents
Communication method, vehicle communication interface device and readable storage medium Download PDFInfo
- Publication number
- CN112927392A CN112927392A CN202110068342.7A CN202110068342A CN112927392A CN 112927392 A CN112927392 A CN 112927392A CN 202110068342 A CN202110068342 A CN 202110068342A CN 112927392 A CN112927392 A CN 112927392A
- Authority
- CN
- China
- Prior art keywords
- target
- filter
- vehicle data
- diagnostic software
- logical link
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 title claims abstract description 94
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000001914 filtration Methods 0.000 claims abstract description 13
- 238000004590 computer program Methods 0.000 claims description 20
- 238000003745 diagnosis Methods 0.000 claims description 9
- 230000006870 function Effects 0.000 description 21
- 230000005540 biological transmission Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- 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
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- B60R16/00—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for
- B60R16/02—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements
- B60R16/023—Electric or fluid circuits specially adapted for vehicles and not otherwise provided for; Arrangement of elements of electric or fluid circuits specially adapted for vehicles and not otherwise provided for electric constitutive elements for transmission of signals between vehicle parts or subsystems
- B60R16/0231—Circuits relating to the driving or the functioning of the vehicle
-
- 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/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- 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
Abstract
The application is applicable to the technical field of vehicles and provides a communication method, a vehicle communication interface device and a readable storage medium. The method comprises the following steps: when the starting of the diagnostic software is detected, N logical links corresponding to the diagnostic software are established; respectively configuring corresponding filters for each logical link, wherein different filters are used for filtering vehicle data of different ECUs in the vehicle; matching a corresponding target logic link when a data acquisition instruction is received; and acquiring the target vehicle data filtered by the target filter, and forwarding the target vehicle data to the diagnostic software through the target logical link. According to the method and the device, the N logical links corresponding to the diagnostic software are established, each logical link acquires the vehicle data required by the logical link through the corresponding filter and forwards the vehicle data to the diagnostic software, so that each logical link can independently and simultaneously complete communication with the vehicle ECU, the communication speed can be improved, the communication time can be reduced, and the communication efficiency can be improved.
Description
Technical Field
The present application relates to a vehicle, and more particularly, to a communication method, a vehicle communication interface device, and a readable storage medium.
Background
As Electronic Control Units (ECUs) become more and more important for automobiles, when an automobile needs a diagnostic device (such as a diagnostic apparatus) to perform diagnosis, the diagnostic device needs to communicate with the ECU in the automobile to obtain data information (such as fault codes, types of vehicle accessories, etc.) of the automobile.
Because the requirements for functions and performance of vehicles are more and more, the number of ECUs in vehicles is also increasing, and at present, Communication between the diagnostic device and the Vehicle ECUs can be realized through a Vehicle Communication Interface (VCI) device based on a ControLLer Area network Bus (continuous Area network-work Bus), the ControLLer Area network Bus is called a CANBUS for short, for example, one end of the VCI device is in Communication connection with the diagnostic device, and the other end of the VCI device is connected with the vehicles through the CANBUS, so that Communication between the diagnostic device and the Vehicle ECUs is realized.
Disclosure of Invention
The embodiment of the application provides a communication method, a vehicle communication interface device and a readable storage medium, and aims to solve the problem that the communication efficiency between diagnosis equipment and a vehicle is low when an existing VCI device is used.
In a first aspect, an embodiment of the present application provides a communication method applied to a vehicle communication interface device, where the vehicle communication interface device is respectively in communication connection with a diagnosis device configured with diagnosis software and a target vehicle, and the communication method includes:
when the diagnostic software is detected to be started, N logical links corresponding to the diagnostic software are established;
configuring a corresponding filter for each logic link; wherein, different filters are used for filtering out vehicle data of different ECUs in the vehicle;
when a data acquisition instruction sent by diagnostic software is received, matching a target logical link corresponding to the data acquisition instruction from the N logical links;
acquiring target vehicle data filtered by a target filter, and forwarding the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
In one embodiment, the configuring a corresponding filter for each logical link respectively includes:
configuring corresponding filters for each logical link, and respectively acquiring handles of the filters corresponding to each logical link; wherein the handle is used to identify a corresponding filter.
In one embodiment, before obtaining the target vehicle data filtered by the target filter and forwarding the target vehicle data to the diagnostic software through the target logical link, the method includes:
determining a target handle corresponding to the target logical link;
and determining the target filter according to the target handle.
The acquiring of the target vehicle data filtered by the target filter includes:
the target vehicle data filtered by the target filter is obtained from the cached vehicle data and/or from a CANBUS physical bus.
In one embodiment, when vehicle data transmitted from the CANBUS physical bus is received, the vehicle data transmitted by the CANBUS is filtered and cached to a preset area according to N filters corresponding to the N logical links, and cached vehicle data is obtained.
In one embodiment, the obtaining target vehicle data filtered by a target filter and forwarding the target vehicle data to the diagnostic software through the target logical link includes:
and when a plurality of target logical links corresponding to the data acquisition instruction are matched from the N logical links, respectively acquiring the target vehicle data filtered by the target filter corresponding to each target logical link, and respectively forwarding the target vehicle data filtered by the target filter corresponding to each target logical link to the diagnosis software through the plurality of target logical links.
In one embodiment, the establishing N logical links corresponding to the diagnostic software when the diagnostic software is detected to be started includes:
when the starting of the diagnostic software is detected, initializing a driving program;
and after initializing a driver, establishing N logical links corresponding to the diagnostic software.
In a second aspect, an embodiment of the present application provides a vehicle communication interface apparatus that is in communication connection with a diagnosis device configured with diagnosis software and a target vehicle, respectively, the vehicle communication interface apparatus including:
the establishing module is used for establishing N logical links corresponding to the diagnostic software when the diagnostic software is detected to be started;
the configuration module is used for configuring a corresponding filter for each logic link; wherein, different filters are used for filtering out vehicle data of different ECUs in the vehicle;
the matching module is used for matching a target logical link corresponding to the data acquisition instruction from the N logical links when the data acquisition instruction sent by the diagnostic software is received;
the acquisition module is used for acquiring the target vehicle data filtered by the target filter and forwarding the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
In one embodiment, the configuration module is specifically configured to configure a corresponding filter for each logical link, and obtain a handle of the filter corresponding to each logical link; wherein the handle is used to identify a corresponding filter.
In one embodiment, the obtaining module is further configured to determine a target handle corresponding to the target logical link before obtaining the target vehicle data filtered by the target filter and forwarding the target vehicle data to the diagnostic software through the target logical link; and determining the target filter according to the target handle.
In one embodiment, the obtaining module is specifically configured to: obtaining target vehicle data filtered by the target filter from the cached vehicle data and/or from a CANBUS physical bus, and forwarding the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
In one embodiment, the vehicle communication interface device further comprises a caching module for: when vehicle data transmitted from the CANBUS physical bus is received, the vehicle data transmitted by the CANBUS physical bus is filtered and cached to a preset area according to N filters corresponding to the N logical links, and cached vehicle data are obtained.
In one embodiment, the obtaining module is specifically configured to: and when a plurality of target logical links corresponding to the data acquisition instruction are matched from the N logical links, respectively acquiring the target vehicle data filtered by the target filter corresponding to each target logical link, and respectively forwarding the target vehicle data filtered by the target filter corresponding to each target logical link to the diagnosis software through the plurality of target logical links.
In one embodiment, the establishing module is specifically configured to: when the starting of the diagnostic software is detected, initializing a driving program; and after initializing a driver, establishing N logical links corresponding to the diagnostic software.
In a third aspect, an embodiment of the present application provides a vehicle communication interface device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the above communication method when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and the computer program realizes the steps of the communication method when executed by a processor.
In a fifth aspect, the present application provides a computer program product, which when run on an electronic device, causes the electronic device to perform the steps of the above communication method.
Compared with the prior art, the embodiment of the application has the advantages that: when detecting that the diagnostic software is started, the embodiment of the application establishes N logical links corresponding to the diagnostic software; configuring a corresponding filter for each established logical link, configuring different filters for different logical links, wherein the different filters are used for filtering vehicle data of different ECUs in the vehicle, when the diagnosis software needs the vehicle data, sending a data acquisition instruction, determining a target logical link for receiving the data from the N established logical links according to the data acquisition instruction, acquiring the target vehicle data filtered by the target filter, and forwarding the target vehicle data to the diagnosis software through the target logical link; wherein the target filter is a filter corresponding to the target logical link. By establishing N logical links corresponding to the diagnostic software, each logical link acquires the vehicle data required by the logical link through a corresponding filter and forwards the vehicle data to the diagnostic software, so that each logical link can independently and simultaneously complete communication with the vehicle ECU, the logical links do not interfere with other logical links, the communication speed can be improved, the communication time can be reduced, and the communication efficiency can be improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
FIG. 1 is an architecture diagram of a communication system connection provided by an embodiment of the present application;
fig. 2 is a flowchart illustrating a communication method according to an embodiment of the present application;
FIG. 3 is an architecture diagram of a communication system connection provided by another embodiment of the present application;
fig. 4 is a flowchart illustrating a communication method according to another embodiment of the present application;
FIG. 5 is a schematic structural diagram of a vehicle communication interface device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a vehicle communication interface device according to another 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.
The Communication method provided by the embodiment of the application can be applied to a Vehicle Communication Interface (VCI) device. As shown in fig. 1, the architecture diagram of a communication system connection is shown, the communication system includes a VCI apparatus 10, a diagnostic device 20 and a target vehicle 30, the VCI apparatus 10 is respectively connected with the diagnostic device 20 and the target vehicle 30 configured with diagnostic software in a communication manner, for example, one end of the VCI apparatus is connected with the diagnostic device in a wired or wireless communication manner, and the other end of the VCI apparatus can be connected with the vehicle in a communication manner based on a CANBUS bus, so as to realize communication between the diagnostic device and the vehicle ECU.
In order to explain the technical solution described in the present application, the following description is given by way of specific examples.
Referring to fig. 2, a schematic flow chart of a communication method provided in an embodiment of the present application is shown, where the method includes:
step S101, when the starting of the diagnostic software is detected, N logical links corresponding to the diagnostic software are established.
Specifically, when the diagnostic software in the diagnostic device is started, the diagnostic software can actively send a start instruction with the diagnostic software identifier to the VCI apparatus, and when the VCI apparatus receives the start instruction with the corresponding diagnostic software identifier, it is determined that the diagnostic software is detected to be started. Or the VCI device actively inquires whether the diagnostic equipment has the diagnostic software to start or not at regular time, and judges to detect the start of the corresponding diagnostic software when the start reply information with the diagnostic software identifier is obtained. When detecting that the corresponding diagnostic software is started, establishing a logic link type according to the pre-stored need of the diagnostic software, and establishing N corresponding logic links. Each logical link is preset to receive and transmit a preset amount of vehicle ECU data, and the limit quantity value of the logical diagnosis link is preset.
For example, in an application scenario, each logical link can receive and transmit one type of vehicle ECU data, when the start of the diagnostic software is detected, N logical links are established according to the type and the number of ECUs corresponding to the vehicle data pre-stored and required by the diagnostic software according to the identification of the diagnostic software, for example, three types of vehicle ECU data including a vehicle transmission control ECU, an engine ECU and an ignition ECU need to be acquired by the diagnostic software 1 in the vehicle diagnosis process, and three logical links can be established according to the diagnostic software 1, wherein each logical link corresponds to one type of ECU. Each logical link can also be preset to receive and transmit K types of vehicle ECU data, wherein K is greater than or equal to 2 and is an integer, for example, each logical link can receive and transmit two types of vehicle ECU data, when the start of the diagnostic software is detected, the types and the number of the ECUs corresponding to the vehicle data required by the diagnostic software are pre-stored according to the identification of the diagnostic software, for example, four types of vehicle ECU data including a vehicle transmission control ECU, an engine ECU, an ignition ECU and a battery management ECU are required to be obtained by the diagnostic software 2 in the vehicle diagnosis process, two logical links can be established according to the diagnostic software 2, each logical link is used for transmitting data to the diagnostic software for the two types of vehicle ECUs, when one logical link transmits data for one of the plurality of vehicle ECUs, the data transmission of the other ECUs can be shielded when the logical link transmits data for one.
In one embodiment, the establishing N logical links corresponding to the diagnostic software when the diagnostic software is detected to be started includes: when the starting of the diagnostic software is detected, initializing a driving program; and after initializing a driver, establishing N logical links corresponding to the diagnostic software.
Specifically, when the start of the diagnostic software is detected, a CanBus driver in the VCI apparatus is initialized, the CanBus driver including filter functions set for the plurality of ECUs and a reception function for receiving data, and the filter functions and the reception function are initialized. The filtering function may be a filtering rule set according to data characteristics (such as data format, data identification, etc.) of the corresponding ECU, and multiple filtering functions may be configured, each corresponding to a different vehicle ECU.
Step S102, configuring corresponding filters for each logic link; wherein different filters are used to filter out vehicle data of different ECUs in the vehicle.
Specifically, configuring a corresponding filter for each logical link may be associating a corresponding filter function for each logical link, so that the logical link only receives data for diagnosing the ECU corresponding to the logical link according to the receiving function and the corresponding filter function.
In one application scenario, as shown in fig. 3, three logical links are established, and each logical link configures an architecture diagram of a communication system connection corresponding to a filter.
In one embodiment, the configuring a corresponding filter for each logical link respectively includes: configuring corresponding filters for each logical link, and respectively acquiring handles of the filters corresponding to each logical link; wherein the handle is used to identify a corresponding filter.
Specifically, a corresponding filter is configured for each logical link; the different filters are used for filtering vehicle data of different ECUs in the vehicle, respectively acquiring handles of the filters corresponding to the logical links, and associating the logical links with the filter handles, wherein the filters are filter functions set for the ECUs, and each filter handle can correspond to different ECUs.
Step S103, when a data acquisition instruction sent by the diagnostic software is received, matching a target logical link corresponding to the data acquisition instruction from the N logical links.
Specifically, when the diagnosis software needs to acquire the vehicle ECU data, a data acquisition instruction is sent, the ECU type corresponding to the data to be acquired is determined according to the data acquisition instruction, the corresponding logical link can be determined according to the ECU type, and the determined logical link is called a target logical link. The corresponding logical link can be determined according to the type of the ECU, for example, the logical link is determined to be associated with the filtering function corresponding to the type of the ECU.
In an application scenario, if the data acquisition instruction is a data instruction for acquiring a transmission control ECU, a logical link associated with the transmission control ECU corresponding to the filter function is determined, and the logical link is determined as a target logical link. Or when the data acquisition command needs to acquire data of the transmission control ECU and the engine ECU, determining the logical link corresponding to the transmission control ECU and the logical link corresponding to the engine ECU as target logical links.
Step S104, obtaining target vehicle data filtered by a target filter, and forwarding the target vehicle data to the diagnosis software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
Specifically, the obtaining of the target vehicle data filtered by the target filter may obtain the vehicle data filtered by the corresponding filter through a receiving function (e.g., an accept function).
In one embodiment, the receiving function may be specifically configured to search and return vehicle data meeting a target filter corresponding to a target handle from cached vehicle data and vehicle data currently received and transmitted by a CanBus physical bus, where the vehicle data is vehicle ECU data transmitted through the CanBus. The target handle may be understood as identifying information for the associated filter on the target logical link. The forwarding of the target vehicle data to the diagnostic software through the target logical link may be after the target vehicle data meeting the CanBus communication protocol format is converted into the target vehicle data meeting the diagnostic software communication format, and the target vehicle data is forwarded to the diagnostic software.
In one embodiment, as shown in fig. 4, step S1041 to step S1042 are included before step S104:
step S1041, determining a target handle corresponding to the target logical link.
Specifically, after the target logical link is determined, a target handle associated with the target logical link is determined.
Step S1042, determining the target filter according to the target handle.
Specifically, the handle may be understood as an identifier of the corresponding filter, and the corresponding target filter may be determined according to the target handle.
In one embodiment, when a plurality of target logical links corresponding to the data acquisition instruction are matched from the N logical links, the target vehicle data filtered by the target filter corresponding to each target logical link is acquired respectively, and the target vehicle data filtered by the target filter corresponding to each target logical link is forwarded to the diagnostic software through the plurality of target logical links respectively.
Specifically, when a plurality of target logical links corresponding to the data acquisition instruction are matched from the N logical links according to the data acquisition instruction, forwarding data of the corresponding ECU to the diagnostic software through each of the plurality of target logical links, where forwarding the data of the corresponding ECU by each logical link may be: ECU data filtered from data received on the CANBUS by a corresponding filter.
In one embodiment, when vehicle data transmitted from the CANBUS physical bus is received, the vehicle data transmitted by the CANBUS is filtered and cached to a preset area according to N filters corresponding to the N logical links, and cached vehicle data is obtained.
Specifically, when vehicle data transmitted from the CANBUS physical bus is received, the corresponding logical link cannot process the vehicle data temporarily or a data acquisition instruction sent by the diagnostic software is not received, and the vehicle data transmitted from the CANBUS physical bus is filtered according to N filters corresponding to the N logical links and then cached to a preset area, so as to obtain cached vehicle data.
In one embodiment, the obtaining target vehicle data filtered by the target filter includes: the target vehicle data filtered by the target filter is obtained from the cached vehicle data and/or from a CANBUS physical bus.
Specifically, if target vehicle data which is not transferred exists in the cached vehicle data, the target vehicle data filtered by the target filter is obtained from the cached vehicle data. And if the CANBUS physical bus is currently transmitting the vehicle data, receiving the currently transmitted vehicle data from the CANBUS physical bus, and acquiring the target vehicle data obtained by filtering the currently transmitted vehicle data through the target filter.
In one embodiment, at the end of the running of the diagnostic software, the plurality of logical links established for the diagnostic software are released, the association relation of the filters configured on the logical links is cleared, and the handles of the logical link association filters are cleared at the same time. And if an instruction of finishing data transmission of the ECU corresponding to the logical link is received, releasing the logical link corresponding to the data transmission finishing, clearing the incidence relation of the filter configured by the logical link, and clearing the handle of the filter associated with the logical link.
According to the method and the device, N logical links corresponding to the diagnostic software are established, each logical link acquires vehicle data needed by the logical link through a corresponding filter and forwards the vehicle data to the diagnostic software, so that each logical link can independently and simultaneously complete communication with the vehicle ECU, the logical links are not interfered with other logical links, the communication speed can be improved, the communication time can be shortened, and the communication efficiency can be improved.
Fig. 5 shows a block diagram of a vehicle communication interface device provided in the embodiment of the present application, corresponding to the communication method described in the above embodiment, and only the relevant portions of the embodiment of the present application are shown for convenience of description. The vehicle communication interface device is respectively in communication connection with a diagnosis device provided with diagnosis software and a target vehicle:
referring to fig. 5, the vehicle communication interface device 500 includes:
an establishing module 501, configured to establish, when it is detected that the diagnostic software is started, N logical links corresponding to the diagnostic software;
a configuration module 502, configured to configure a corresponding filter for each logical link; wherein, different filters are used for filtering out vehicle data of different ECUs in the vehicle;
a matching module 503, configured to match a target logical link corresponding to a data acquisition instruction from the N logical links when the data acquisition instruction sent by the diagnostic software is received;
an obtaining module 504, configured to obtain target vehicle data filtered by a target filter, and forward the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
In one embodiment, the configuration module is specifically configured to configure a corresponding filter for each logical link, and obtain a handle of the filter corresponding to each logical link; wherein the handle is used to identify a corresponding filter.
In one embodiment, the obtaining module is further configured to determine a target handle corresponding to the target logical link before obtaining the target vehicle data filtered by the target filter and forwarding the target vehicle data to the diagnostic software through the target logical link; and determining the target filter according to the target handle.
In one embodiment, the obtaining module is specifically configured to: obtaining target vehicle data filtered by the target filter from the cached vehicle data and/or from a CANBUS physical bus, and forwarding the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
In one embodiment, the vehicle communication interface device further comprises a caching module for: when vehicle data transmitted from the CANBUS physical bus is received, the vehicle data transmitted by the CANBUS physical bus is filtered and cached to a preset area according to N filters corresponding to the N logical links, and cached vehicle data are obtained.
In one embodiment, the obtaining module is specifically configured to: and when a plurality of target logical links corresponding to the data acquisition instruction are matched from the N logical links, respectively acquiring the target vehicle data filtered by the target filter corresponding to each target logical link, and respectively forwarding the target vehicle data filtered by the target filter corresponding to each target logical link to the diagnosis software through the plurality of target logical links.
In one embodiment, the establishing module is specifically configured to: when the starting of the diagnostic software is detected, initializing a driving program; and after initializing a driver, establishing N logical links corresponding to the diagnostic software.
According to the method and the device, N logical links corresponding to the diagnostic software are established, each logical link acquires vehicle data needed by the logical link through a corresponding filter and forwards the vehicle data to the diagnostic software, so that each logical link can independently and simultaneously complete communication with the vehicle ECU, the logical links are not interfered with other logical links, the communication speed can be improved, the communication time can be shortened, and the communication efficiency can be improved.
Fig. 6 is a schematic structural diagram of a vehicle communication interface device according to an embodiment of the present application. The vehicle communication interface apparatus 600 includes: a processor 601, a memory 602, and a computer program 603 stored in the memory 602 and operable on the processor 601. The steps in the above-described embodiment of the communication method are implemented when the above-described processor 601 executes the above-described computer program 603.
Illustratively, the computer program 603 may be partitioned into one or more units/modules, which are stored in the memory 602 and executed by the processor 601 to complete the present application. The one or more units/modules 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 603 in the vehicle communication interface device 600. For example, the computer program 603 may be divided into an establishing module, a configuring module, a matching module, an obtaining module, and the like, and specific functions of the modules are described in the foregoing embodiments, which are not described herein again.
The vehicle communication interface device 600 may include, but is not limited to, a processor 601 and a memory 602. Those skilled in the art will appreciate that fig. 6 is merely an example of a vehicle communication interface apparatus 600 and does not constitute a limitation of the vehicle communication interface apparatus 600, and may include more or less components than those shown, or combine certain components, or different components, for example, the vehicle communication interface apparatus 600 may further include input and output devices, network access devices, buses, etc.
The Processor 601 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 602 may be an internal storage unit of the vehicle communication interface device 600, such as a hard disk or a memory of the vehicle communication interface device 600. The memory 602 may include both an internal storage unit and an external storage device of the vehicle communication interface apparatus 600. The memory 602 is used to store the computer programs and other programs and data required by the vehicle communication interface device 600. The memory 602 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 functions may be distributed as different functional units and modules according to needs, that is, the internal structure of the apparatus may be divided into different functional units or modules to implement 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 vehicle diagnostic device may refer to 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.
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.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the above-described modules or units is only one type of division of logical functions, 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 embodiments of the present application.
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 unit may be stored in a computer-readable storage medium if it is implemented in the form of a software functional unit and sold or used as a separate product. Based on such understanding, all or part of the flow in the method of the embodiments described above may be implemented by a computer program, which may be stored in a computer readable storage medium and used by a processor to implement the steps of the embodiments of the methods described above. The computer program includes computer program code, and the computer program code may be in a source code form, an object code form, an executable file or some intermediate form. The computer readable medium may include: any entity or device capable of carrying the above-mentioned 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 signal, telecommunication signal, software distribution medium, etc. It should be noted that the computer readable medium described above may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media excludes electrical carrier signals and telecommunications signals in accordance with legislation and patent practice. The above-mentioned embodiments are only used for illustrating the technical solutions 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 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 communication method applied to a vehicle communication interface apparatus that is communicatively connected to a diagnosis device provided with diagnosis software and a target vehicle, respectively, the communication method comprising:
when the diagnostic software is detected to be started, N logical links corresponding to the diagnostic software are established;
configuring a corresponding filter for each logic link; wherein, different filters are used for filtering out vehicle data of different ECUs in the vehicle;
when a data acquisition instruction sent by diagnostic software is received, matching a target logical link corresponding to the data acquisition instruction from the N logical links;
acquiring target vehicle data filtered by a target filter, and forwarding the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
2. The communication method according to claim 1, wherein the configuring a corresponding filter for each logical link respectively comprises:
configuring corresponding filters for each logical link, and respectively acquiring handles of the filters corresponding to each logical link; wherein the handle is used to identify a corresponding filter.
3. The communication method according to claim 2, wherein before obtaining the target vehicle data filtered by the target filter and forwarding the target vehicle data to the diagnostic software through the target logical link, the method comprises:
determining a target handle corresponding to the target logical link;
and determining the target filter according to the target handle.
4. The communication method according to claim 1, wherein the obtaining target vehicle data filtered by a target filter comprises:
the target vehicle data filtered by the target filter is obtained from the cached vehicle data and/or from a CANBUS physical bus.
5. The communication method according to claim 4, wherein the communication method comprises:
when vehicle data transmitted from the CANBUS physical bus is received, the vehicle data transmitted by the CANBUS physical bus is filtered and cached to a preset area according to N filters corresponding to the N logical links, and cached vehicle data are obtained.
6. The communication method according to claim 1, wherein the obtaining target vehicle data filtered by a target filter and forwarding the target vehicle data to the diagnostic software via the target logical link comprises:
and when a plurality of target logical links corresponding to the data acquisition instruction are matched from the N logical links, respectively acquiring the target vehicle data filtered by the target filter corresponding to each target logical link, and respectively forwarding the target vehicle data filtered by the target filter corresponding to each target logical link to the diagnosis software through the plurality of target logical links.
7. The communication method according to claim 1, wherein the establishing of the N logical links corresponding to the diagnostic software when the startup of the diagnostic software is detected comprises:
when the starting of the diagnostic software is detected, initializing a driving program;
and after initializing a driver, establishing N logical links corresponding to the diagnostic software.
8. A vehicle communication interface apparatus that is communicatively connected to a diagnostic device provided with diagnostic software and a target vehicle, respectively, the vehicle communication interface apparatus comprising:
the establishing module is used for establishing N logical links corresponding to the diagnostic software when the diagnostic software is detected to be started;
the configuration module is used for configuring a corresponding filter for each logic link; wherein, different filters are used for filtering out vehicle data of different ECUs in the vehicle;
the matching module is used for matching a target logical link corresponding to the data acquisition instruction from the N logical links when the data acquisition instruction sent by the diagnostic software is received;
the acquisition module is used for acquiring the target vehicle data filtered by the target filter and forwarding the target vehicle data to the diagnostic software through the target logical link; wherein the target filter is a filter corresponding to the target logical link.
9. A vehicle communication interface device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110068342.7A CN112927392A (en) | 2021-01-19 | 2021-01-19 | Communication method, vehicle communication interface device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110068342.7A CN112927392A (en) | 2021-01-19 | 2021-01-19 | Communication method, vehicle communication interface device and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112927392A true CN112927392A (en) | 2021-06-08 |
Family
ID=76163431
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110068342.7A Pending CN112927392A (en) | 2021-01-19 | 2021-01-19 | Communication method, vehicle communication interface device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112927392A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791605A (en) * | 2021-09-13 | 2021-12-14 | 一汽解放汽车有限公司 | Test method, device, equipment and storage medium |
| CN113978394A (en) * | 2021-10-26 | 2022-01-28 | 深圳市元征科技股份有限公司 | Vehicle fault detection method and device, electronic equipment and storage medium |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020154603A1 (en) * | 2001-04-19 | 2002-10-24 | Andreas Deuter | Diagnostic device for a field bus with control-independent transfer of information |
| EP1378826A1 (en) * | 2002-07-01 | 2004-01-07 | Sun Microsystems, Inc. | Filter network for data representation |
| US20100121951A1 (en) * | 2008-11-06 | 2010-05-13 | Stefan Trebing | Method and arrangement for diagnosing networks including field bus systems |
| CN103605354A (en) * | 2013-12-02 | 2014-02-26 | 北京中瑞蓝科电动汽车技术有限公司 | Multifunctional vehicle terminal device |
| CN108320351A (en) * | 2018-02-07 | 2018-07-24 | 安徽星网软件技术有限公司 | A kind of vehicle trouble on-line monitoring system and method |
| CN108536121A (en) * | 2018-03-16 | 2018-09-14 | 深圳市道通科技股份有限公司 | Method for building up, device and the vehicle communication interface VCI of logical channel |
| CN109873725A (en) * | 2019-03-06 | 2019-06-11 | 中国铁道科学研究院集团有限公司通信信号研究所 | A kind of railway signal TDCS/CTC system prevents the means of defence of data network storm |
| CN110850841A (en) * | 2019-10-30 | 2020-02-28 | 深圳市元征科技股份有限公司 | Fault diagnosis method and related device |
| CN111063054A (en) * | 2019-12-23 | 2020-04-24 | 智车优行科技（上海）有限公司 | Fault information sending method and device and vehicle fault processing method and device |
| CN111179466A (en) * | 2019-12-18 | 2020-05-19 | 国汽(北京)智能网联汽车研究院有限公司 | Vehicle state data storage method, vehicle state data storage device, vehicle-mounted instrument system and vehicle |
| CN111427335A (en) * | 2020-04-22 | 2020-07-17 | 深圳市元征科技股份有限公司 | Vehicle remote diagnosis method, equipment connector and vehicle connector |
| CN111541579A (en) * | 2020-06-19 | 2020-08-14 | 深圳市乙辰科技股份有限公司 | Industrial gateway control method and device, computer equipment and storage medium |
-
2021
- 2021-01-19 CN CN202110068342.7A patent/CN112927392A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020154603A1 (en) * | 2001-04-19 | 2002-10-24 | Andreas Deuter | Diagnostic device for a field bus with control-independent transfer of information |
| EP1378826A1 (en) * | 2002-07-01 | 2004-01-07 | Sun Microsystems, Inc. | Filter network for data representation |
| US20100121951A1 (en) * | 2008-11-06 | 2010-05-13 | Stefan Trebing | Method and arrangement for diagnosing networks including field bus systems |
| CN103605354A (en) * | 2013-12-02 | 2014-02-26 | 北京中瑞蓝科电动汽车技术有限公司 | Multifunctional vehicle terminal device |
| CN108320351A (en) * | 2018-02-07 | 2018-07-24 | 安徽星网软件技术有限公司 | A kind of vehicle trouble on-line monitoring system and method |
| CN108536121A (en) * | 2018-03-16 | 2018-09-14 | 深圳市道通科技股份有限公司 | Method for building up, device and the vehicle communication interface VCI of logical channel |
| CN109873725A (en) * | 2019-03-06 | 2019-06-11 | 中国铁道科学研究院集团有限公司通信信号研究所 | A kind of railway signal TDCS/CTC system prevents the means of defence of data network storm |
| CN110850841A (en) * | 2019-10-30 | 2020-02-28 | 深圳市元征科技股份有限公司 | Fault diagnosis method and related device |
| CN111179466A (en) * | 2019-12-18 | 2020-05-19 | 国汽(北京)智能网联汽车研究院有限公司 | Vehicle state data storage method, vehicle state data storage device, vehicle-mounted instrument system and vehicle |
| CN111063054A (en) * | 2019-12-23 | 2020-04-24 | 智车优行科技（上海）有限公司 | Fault information sending method and device and vehicle fault processing method and device |
| CN111427335A (en) * | 2020-04-22 | 2020-07-17 | 深圳市元征科技股份有限公司 | Vehicle remote diagnosis method, equipment connector and vehicle connector |
| CN111541579A (en) * | 2020-06-19 | 2020-08-14 | 深圳市乙辰科技股份有限公司 | Industrial gateway control method and device, computer equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113791605A (en) * | 2021-09-13 | 2021-12-14 | 一汽解放汽车有限公司 | Test method, device, equipment and storage medium |
| CN113791605B (en) * | 2021-09-13 | 2023-10-27 | 一汽解放汽车有限公司 | Test method, device, equipment and storage medium |
| CN113978394A (en) * | 2021-10-26 | 2022-01-28 | 深圳市元征科技股份有限公司 | Vehicle fault detection method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11665018B2 (en) | OBD interface bus type detection method and apparatus | |
| CN111208800B (en) | Automobile diagnosis method and device and vehicle communication interface | |
| CN110032173B (en) | Automatic matching method for automobile diagnosis system and related equipment | |
| CN111427335B (en) | Vehicle remote diagnosis method, equipment connector and vehicle connector | |
| CN112927392A (en) | Communication method, vehicle communication interface device and readable storage medium | |
| CN106970609A (en) | The diagnostic method and vehicle diagnostics box of vehicle diagnostics box | |
| CN111538312A (en) | Vehicle remote diagnosis method, system, equipment connector and vehicle connector | |
| CN108445860B (en) | Diagnostic apparatus, diagnostic request processing method, and computer-readable storage medium | |
| CN111552268B (en) | Vehicle remote diagnosis method, equipment connector and vehicle connector | |
| CN109565458A (en) | Method and apparatus for the data communication in access controller local area network | |
| CN113645097A (en) | Vehicle signal monitoring method, terminal equipment and electronic control unit | |
| CN113406944A (en) | Vehicle diagnosis method, apparatus, device and computer readable storage medium | |
| CN111061237B (en) | Vehicle identification code flashing method and vehicle identification code flashing system | |
| CN111966391A (en) | System configuration method and device of vehicle, terminal equipment and storage medium | |
| CN111913472A (en) | Operation mode control method of vehicle diagnostic device and related device | |
| CN116319499A (en) | Diagnostic method and device for vehicle, electronic equipment and storage medium | |
| CN114756585A (en) | Vehicle data acquisition method and device, electronic equipment and storage medium | |
| CN114035552A (en) | Vehicle diagnosis method, diagnosis device and readable storage medium | |
| CN115016438A (en) | Diagnostic method, diagnostic apparatus, and target vehicle | |
| US20210112147A1 (en) | Transformation device, transformation method and storage medium | |
| CN112817888A (en) | OBD device state setting method and device, OBD device and storage medium | |
| CN113395264A (en) | Communication connection method, apparatus, server and medium | |
| KR102028653B1 (en) | Device and method for analysing can message using obd-ⅱ query | |
| 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210608 |