CN117950389A - Data acquisition system - Google Patents

Abstract

The present application relates to a data acquisition system. The data acquisition system comprises: the first controller group comprises a plurality of first controllers of different types, and data are transmitted between the first controllers through a common CAN bus; the first OBD connector is provided with a plurality of groups of CAN pins, and each group of CAN pins is used for being correspondingly connected with a first controller respectively; and the data acquisition device is connected with the first OBD connector and is used for carrying out data interaction with the first controller through the first OBD connector based on a communication diagnosis protocol. The data acquisition system can perform data interaction with each controller in the development stage, so that the communication diagnosis function of each controller is debugged.

Description

Data acquisition system

Technical Field

The application relates to the technical field of diagnostic communication, in particular to a data acquisition system.

Background

The vehicle OBD connector is an interface for external equipment to access the vehicle, and maintenance detection personnel can realize data interaction between the external equipment and each controller of the vehicle through the standard OBD connector. When debugging the communication diagnostic function of a controller using a standard OBD connector, it is often necessary to use another controller as a "route" to forward the signal. However, because of different development progress of each controller of the vehicle, in the development stage, the standard OBD connector cannot be used for communication diagnosis and debugging of the specific controller.

Disclosure of Invention

Based on this, it is necessary to provide a data acquisition system that can perform communication diagnostic debugging of each controller during the development phase.

The application provides a data acquisition system, comprising:

The first controller group comprises a plurality of first controllers of different types, and data are transmitted between the first controllers through a common CAN bus;

The first OBD connector is provided with a plurality of groups of CAN pins, and each group of CAN pins is used for being correspondingly connected with a first controller respectively;

And the data acquisition device is connected with the first OBD connector and is used for carrying out data interaction with the first controller through the first OBD connector based on a communication diagnosis protocol.

In one embodiment, the first controller is one of a power domain controller, a hybrid domain controller, a comfort domain controller, a chassis domain controller, an auxiliary driving domain controller, an information domain controller, and an extranet connection domain controller.

In one embodiment, the first OBD connector is configured with seven groups of CAN pins, and the first controller group includes seven different types of first controllers, and each group of CAN pins is correspondingly connected with one type of first controller.

In one embodiment, the seven sets of CAN pins include a power CAN pin, a hybrid CAN pin, a comfort CAN pin, a chassis CAN pin, a driving assistance CAN pin, an information CAN pin, and an interconnection CAN pin.

In one embodiment, the data acquisition system further comprises:

The second controller group comprises a plurality of second controllers of different types, and data are transmitted between the second controllers through a private CAN bus;

The second OBD connector is provided with a plurality of groups of private CAN pins, and each group of private CAN pins is used for being correspondingly connected with a second controller respectively;

The data acquisition device is also connected with the second OBD connector and is also used for carrying out data interaction with the second controller through the second OBD connector based on a communication diagnosis protocol.

In one embodiment, the second controller is one of a vehicle body controller and a vehicle lamp controller.

In one embodiment, the first controller and the second controller transmit data via a private CAN bus;

And under the condition that the first OBD connector is connected with a first controller in a conducting way and the second OBD connector is connected with a second controller in a conducting way, the data acquisition device is further used for acquiring first data of the first controller and second data of the second controller, and determining whether data transmission between the first controller and the second controller is abnormal or not according to the first data and the second data.

In one embodiment, the data acquisition system further comprises a third controller;

The second OBD connector is further provided with three groups of calibration CAN pins, and the three groups of calibration CAN pins are correspondingly connected with the three third controllers respectively;

the data acquisition device is further used for acquiring calibration data of the third controller through a calibration CAN pin of the second OBD connector based on a calibration protocol.

In one embodiment, the data acquisition system further comprises a fourth controller; wherein,

The second OBD connector is also provided with two LIN pins, and the LIN pins are respectively connected with a fourth controller;

The data acquisition device is further used for carrying out data interaction with the fourth controller through the LIN pin of the second OBD connector based on the LIN communication protocol.

In one embodiment, the data acquisition system further comprises a fifth controller; wherein,

The second OBD connector is further configured with a group of Ethernet pins, and the Ethernet pins are connected with a fifth controller;

The data acquisition device is further used for performing data interaction with the fifth controller through an Ethernet pin of the second OBD connector based on an Ethernet communication protocol.

The data acquisition device comprises a first controller group, a first OBD connector and a data acquisition device. The first controller group comprises a plurality of first controllers of different types, the first OBD connector comprises a plurality of groups of CAN pins, and each group of CAN pins is connected with a first controller. The data acquisition device can be directly connected with the first controller through the first OBD connector to perform data interaction with the first controller in a diagnosis communication mode, so that the diagnosis communication function of the first controller can be debugged in a research and development stage.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments or the conventional techniques of the present application, the drawings required for the descriptions of the embodiments or the conventional techniques will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.

FIG. 1 is a diagram of a data acquisition system according to an embodiment;

FIG. 2 is a pin diagram of a first OBD connector according to an embodiment;

Fig. 3 is a data acquisition system of another embodiment.

Reference numerals illustrate:

100-first controller group, 200-first OBD connector, 300-data acquisition device, 400-second controller group, 500-second OBD connector.

Detailed Description

In order that the application may be readily understood, a more complete description of the application will be rendered by reference to the appended drawings. Embodiments of the application are illustrated in the accompanying drawings. This application may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein in the description of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

It will be understood that the terms first, second, etc. as used herein may be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish one element from another element. For example, a first resistance may be referred to as a second resistance, and similarly, a second resistance may be referred to as a first resistance, without departing from the scope of the application. Both the first resistor and the second resistor are resistors, but they are not the same resistor.

It is to be understood that in the following embodiments, "connected" is understood to mean "electrically connected", "communicatively connected", etc., if the connected circuits, modules, units, etc., have electrical or data transfer between them.

It is understood that "at least one" means one or more and "a plurality" means two or more. "at least part of an element" means part or all of the element.

As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," and/or the like, specify the presence of stated features, integers, steps, operations, elements, components, or groups thereof, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or groups thereof. Also, the term "and/or" as used in this specification includes any and all combinations of the associated listed items.

The standard OBD connector includes 16 pins, each defined as follows: pin 4 is defined as chassis ground, pin 5 is defined as signal ground, pin 16 is defined as power pin, pin 6 and pin 14 bit CAN bus pins, pin 3, pin 8, pin 11, pin 12 and pin 13 are defined as Ethernet signal pins, pin 1, pin 2, pin 7, pin 9, pin 10 and pin 15 bit custom pins. The external device can interact data with the vehicle in a diagnosis communication mode through the standard OBD connector, and the calibration and the function debugging of the controller are realized. The standard OBD connector is only connected with one CAN bus, so that diagnosis communication of each controller on the vehicle CAN be realized. When controller a is subjected to diagnostic communication function debugging, controller B may be required to act as a route, forwarding data of controller a. In the research and development stage, the functions of the controller A cannot be debugged through the standard OBD connector due to different development progress of the controller A and the controller B. Based on the problems, the application provides a data acquisition system which can interact with each controller in the research and development stage so as to realize the function debugging of each controller. It should be noted that the first controller, the second controller, the third controller, the fourth controller, and the fifth controller according to the present application are all in-vehicle controllers, and may be understood as in-vehicle electronic control units (Electronic Control Unit, ECU).

In one embodiment, as shown in FIG. 1, the present application provides a data acquisition system comprising a first controller group 100, a first OBD connector 200, and a data acquisition device 300.

The first controller group 100 includes a plurality of different types of first controllers, and data is transmitted between the first controllers through a common CAN bus. The first OBD connector 200 is configured with a plurality of groups of CAN pins, each group of CAN pins being configured to be respectively and correspondingly connected to a first controller.

The first controller mainly refers to an on-vehicle ECU which performs data transmission through a public CAN bus. The CAN bus is a bi-directional serial bus, and therefore, each set of CAN pins of the first OBD connector includes a can_h pin and a can_l pin to enable direct connection with the leads of the first controller.

The data acquisition device 300 is connected to the first OBD connector 200 for data interaction with the first controller via the first OBD connector 200 based on a communication diagnostic protocol.

It will be appreciated that the data acquisition device 300 may be in diagnostic communication with the first controller via the first OBD connector 200. I.e. the data acquisition device outputs a diagnostic request which is sent via the first OBD connector 200 to the first controller, which performs a data interaction with the data acquisition device 300 in response to the diagnostic request. The data transmitted by the data acquisition device 300 and the first controller through the first OBD connector 200 includes fault information of the first controller and the corresponding actuator, data acquired by a sensor (the sensor is in communication connection with the first controller), and the like. The data acquisition device may be a diagnostic instrument, for example.

In an embodiment of the application, the data acquisition device comprises a first controller group, a first OBD connector and the data acquisition device. The first controller group comprises a plurality of first controllers of different types, the first OBD connector comprises a plurality of groups of CAN pins, and each group of CAN pins is connected with a first controller. The data acquisition device can be directly connected with the first controller through the first OBD connector to perform data interaction with the first controller in a diagnosis communication mode, so that the diagnosis communication function of the first controller can be debugged in a research and development stage.

It should be noted that, the communication diagnostic protocol and the calibration protocol referred to below are all application layer protocols, and the CAN bus protocol and the LIN bus protocol referred to below are all transport layer protocols. In the embodiment of the application, the data acquisition device can support a communication diagnosis protocol and a calibration protocol. The first OBD connector may support the CAN bus protocol and the second OBD connector referred to hereinafter may support the CAN bus protocol, the LIN bus protocol and the ethernet communication protocol.

In one embodiment, the first controller is one of a power domain controller, a hybrid domain controller, a comfort domain controller, a chassis domain controller, an auxiliary driving domain controller, an information domain controller, and an extranet connection domain controller.

The domain controller may be understood as an integration of a plurality of onboard ECUs. The power domain controller may include a transmission controller, a generator controller, an airbag controller, a vehicle controller, and the like. The hybrid domain controller may include an engine controller, a battery management system controller, an on-board DC-DC converter, and the like. The comfort zone controller may include a body controller, a door controller, a seat controller, and the like. The chassis domain controller may comprise a chassis controller. The auxiliary driving area controller can comprise a controller of a radar, a camera, a panoramic image system and the like. The information domain controller may include a controller of an entertainment host, a vehicle recorder, or the like. The foreign network connection domain controller may include a controller of a smart antenna, an in-vehicle remote communication terminal, an electronic toll collection system, and the like. It is understood that the first controller may be any vehicle-mounted ECU that CAN communicate via a common CAN bus.

In one embodiment, the first OBD connector is configured with seven sets of CAN pins, a first controller set comprising seven different types of first controllers, each set of CAN pins being correspondingly connected to one type of first controller.

In one embodiment, the seven sets of CAN pins include a power CAN pin, a hybrid CAN pin, a comfort CAN pin, a chassis CAN pin, a driving assistance CAN pin, an information CAN pin, and an interconnect CAN pin.

The pin profile of the first OBD connector is shown in fig. 2, comprising seven sets of CAN pins and a set of power pins. For example, a set of power CAN pins may be defined, pin 1 and pin 9, which may establish a communication connection with any one of the first controllers included in the power domain controller. Pin 2 and pin 10 may be defined as a set of hybrid CAN pins that may establish a communication connection with any first controller included in the hybrid domain controller. Pin 3 and pin 11 may be defined as a set of comfort CAN pins that may establish a communication connection with any one of the first controllers included in the comfort domain controller. Pin 4 and pin 12 may be defined as a set of chassis CAN pins that may establish a communication connection with any first controller included in the chassis domain controller. Pin 5 and pin 13 may be defined as a set of driving assistance CAN pins that may establish a communication connection with any of the first controllers included in the driving assistance domain controller. Pin 6 and pin 14 may be defined as a set of information CAN pins that may be used to establish a communication connection with any first controller included in the information domain controller. Pin 7 and pin 15 may be defined as a set of interconnected CAN pins that may establish a communication connection with any first controller included in the foreign network connection domain controller. Pins 8 and 16 may be defined as a set of power pins that may be used to power a data acquisition device.

In the research and development stage, when a certain first controller needs to be subjected to communication diagnosis function debugging, pins corresponding to the first controller and the first OBD connector can be connected, and the data acquisition device can perform data interaction through the first OBD connector and the first controller so as to realize the debugging of the communication diagnosis function.

In one embodiment, as shown in fig. 3, the data acquisition system further comprises a second controller group 400 and a second OBD connector 500.

The second controller group 400 includes a plurality of different types of second controllers, and data CAN be transmitted between the second controllers through a private CAN bus. The vehicle-mounted ECU CAN transmit data through the public CAN bus, but in terms of signal transmission capacity and safety of signal transmission, some vehicle-mounted ECU, namely the second controller, needs to transmit data through the private CAN bus. The second controller is one of a vehicle body controller and a lamp controller, for example.

The second OBD connection 500 is configured with a plurality of sets of private CAN pins, each set of private CAN pins being configured to be respectively and correspondingly connected to a second controller. The formats of the data messages transmitted through the private CAN bus and the public CAN bus are different, and therefore, the private CAN pins are separately set for the second controller by setting the second OBD connector 500. Each set of proprietary CAN pins includes a proprietary can_h pin and a proprietary can_l pin.

The data acquisition device 300 may be coupled to the second OBD connector 500 and may be in data communication with the second controller via the second OBD connector 500 based on a communication diagnostic protocol.

It will be appreciated that after the second controller is connected to the corresponding pins of the second OBD connector 500, the data acquisition device 300 may send a communication diagnosis request to the second controller through the second OBD connector 500, and the second controller may respond to the communication diagnosis request and perform data interaction through the second OBD connector and the data acquisition device.

In the embodiment of the application, the data acquisition system further comprises a second controller group and a second OBD connector, wherein the second controller group comprises a plurality of second controllers of different types, the second OBD connector is provided with a plurality of groups of private CAN pins, each group of private CAN pins CAN be correspondingly and directly connected with one second controller, and further, the data acquisition device CAN carry out data interaction with the second controller through the second OBD connector, so that the debugging of the communication diagnosis function of the second controller in the development stage CAN be realized.

In one embodiment, the data acquisition device is further configured to acquire first data of the first controller and second data of the second controller, and determine whether an abnormality occurs in data transmission between the first controller and the second controller according to the first data and the second data, when the first OBD connector is in conductive connection with the first controller and the second OBD connector is in conductive connection with the second controller. The first controller and the second controller transmit data through the private CAN bus.

In practical applications, a situation that one controller is used as a routing node to forward a message of another controller often occurs, so that accuracy of signal transmission between the two controllers needs to be ensured. In the research and development stage, the first OBD connector and the first controller can be connected, the second OBD connector and the second controller can be connected, and the data acquisition device can acquire first data of the first controller and second data of the second controller. The first data can be used as original data, and the second data is data forwarded by the second controller; optionally, the second data is taken as original data, and the first data is data forwarded by the first controller. After the data acquisition device acquires the first data and the second data, the first data and the second data are compared, so that a developer can determine whether to optimize a signal transmission channel between the first controller and the second controller according to the comparison result.

In one embodiment, the data acquisition system further comprises a third controller. The third controller is an onboard ECU with calibration requirements. The third controller may be any one of a battery management system, an engine management system, and an ECU of a radar system, for example. The third controller performs data transmission based on the CAN bus protocol. The second OBD connector is also provided with three groups of calibration CAN pins which are correspondingly connected with the three third controllers respectively. Likewise, each set of calibration CAN pins includes a calibration CAN_H pin and a calibration CAN_L pin.

The data acquisition device CAN acquire calibration data of the third controller through a calibration CAN pin of the second OBD connector based on a calibration protocol.

It CAN be appreciated that for a third controller with calibration requirements, the third controller may be connected to a corresponding calibration CAN pin, and the data acquisition device may acquire calibration data of the third controller through the second OBD connector, so that a developer may optimize the third controller and related actuators according to the calibration data.

In one embodiment, the data acquisition system further comprises a fourth controller. The fourth controller is any vehicle-mounted ECU which performs data transmission through the LIN bus. The fourth controller may be a battery sensor or an entertainment host controller, for example. The second OBD connector is further configured with two LIN pins, each of which is connected to a fourth controller. The data acquisition device may interact with the fourth controller via a LIN pin of the second OBD connector based on a LIN bus protocol.

It can be understood that the LIN pin of the second OBD connector is connected to the fourth controller, and the second OBD connector and the fourth controller both support the LIN bus protocol, so that the data acquisition device can perform data interaction through the second OBD connector and the fourth controller, and the debugging of the communication diagnosis function of the fourth controller in the development stage can be realized.

In one embodiment, the data acquisition system further comprises a fifth controller. The fifth controller is any vehicle-mounted ECU which performs data transmission based on an Ethernet communication protocol and has calibration requirements. For example, the fifth controller may be an onboard ECU of the advanced autopilot system. The second OBD connector is further configured with a set of ethernet pins, the ethernet pins being connected to the fifth controller. The set of ethernet pins may include a calibration t1+ pin and a calibration T1-pin. The data acquisition device may interact with the fifth controller via the second OBD connector based on an ethernet communication protocol.

It will be appreciated that when the fifth controller supporting the ethernet communication protocol and the calibration protocol is functionally commissioned, corresponding pins of the fifth controller and the second OBD connector may be connected. The data acquisition device can perform data interaction with the fifth controller through the second OBD connector, and the function debugging of the fifth controller in the research and development stage can be realized.

In a particular embodiment, the second OBD connector may include 16 pins. Wherein, pin 1, pin 2, pin 9 and pin 10 CAN be defined as private CAN pins, CAN be connected with the second controller, and illustratively, pin 1 and pin 9 are BCM private CAN pins, CAN establish communication connection with the vehicle body controller; pin 2 and pin 10 are DLP private CAN pins, and CAN establish communication connection with the car light controller. Pin 3, pin 5, pin 6, pin 11, pin 13, and Pin 14 may be defined as calibration CAN pins. Illustratively, pin 2 and pin 10 are BMS calibrated CAN pins, which CAN establish a communication connection with the ECU of the battery management system; the pin 5 and the pin 13 are EMS_CAN pins, and CAN be in communication connection with an ECU of an engine management system; pin 6 and pin 14 are RadarF _CAN pins that CAN establish a communication connection with the ECU of the radar system. Pin 4 and pin 12 may be defined as Ethernet pins, and illustratively pin 4 and pin 12 are HAD calibration T1 pins, which may establish a communication connection with the ECU of the advanced autopilot system. Pin 7 and pin 15 are defined as two LIN pins, illustratively EBS_LIN, and may be in communication with the battery sensor, and CSC_LIN_CLOCK, and may be based on the LIN bus and the entertainment host controller, and may be configured to obtain a CLOCK signal. Pins 8 and 16 may be defined as power pins that may power the data acquisition device.

The data acquisition device can be directly connected with each controller still in the development stage through the second OBD connector, so that the debugging of the communication diagnosis function of each controller is realized.

In the description of the present specification, reference to the term "some embodiments," "other embodiments," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, schematic descriptions of the above terms do not necessarily refer to the same embodiment or example.

The technical features of the above-described embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above-described embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples merely represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims (10)

1. A data acquisition system, comprising:

The first controller group comprises a plurality of first controllers of different types, and data are transmitted between the first controllers through a common CAN bus;

The first OBD connector is provided with a plurality of groups of CAN pins, and each group of CAN pins is used for being correspondingly connected with a first controller respectively;

And the data acquisition device is connected with the first OBD connector and is used for carrying out data interaction with the first controller through the first OBD connector based on a communication diagnosis protocol.

2. The data acquisition system of claim 1, wherein the first controller is one of a power domain controller, a hybrid domain controller, a comfort domain controller, a chassis domain controller, a driver assistance domain controller, an information domain controller, and an extranet connection domain controller.

3. The data acquisition system of claim 2 wherein the first OBD connector is configured with seven sets of CAN pins, the first controller set comprising seven different types of first controllers, each set of CAN pins being correspondingly connected to one type of first controller.

4. The data acquisition system of claim 3 wherein the seven sets of CAN pins include a power CAN pin, a hybrid CAN pin, a comfort CAN pin, a chassis CAN pin, a driving assistance CAN pin, an information CAN pin, and an interconnect CAN pin.

5. The data acquisition system of claim 1, wherein the data acquisition system further comprises:

The second controller group comprises a plurality of second controllers of different types, and data are transmitted between the second controllers through a private CAN bus;

The second OBD connector is provided with a plurality of groups of private CAN pins, and each group of private CAN pins is used for being correspondingly connected with a second controller respectively;

The data acquisition device is also connected with the second OBD connector and is also used for carrying out data interaction with the second controller through the second OBD connector based on a communication diagnosis protocol.

6. The data acquisition system of claim 5 wherein the second controller is one of a body controller and a lamp controller.

7. The data acquisition system of claim 5 wherein the first controller and the second controller transmit data over a private CAN bus;

And under the condition that the first OBD connector is connected with a first controller in a conducting way and the second OBD connector is connected with a second controller in a conducting way, the data acquisition device is further used for acquiring first data of the first controller and second data of the second controller, and determining whether data transmission between the first controller and the second controller is abnormal or not according to the first data and the second data.

8. The data acquisition system of claim 5, wherein the data acquisition system further comprises a third controller;

The second OBD connector is further provided with three groups of calibration CAN pins, and the three groups of calibration CAN pins are correspondingly connected with the three third controllers respectively;

the data acquisition device is further used for acquiring calibration data of the third controller through a calibration CAN pin of the second OBD connector based on a calibration protocol.

9. The data acquisition system of claim 5, wherein the data acquisition system further comprises a fourth controller; wherein,

The second OBD connector is also provided with two LIN pins, and the LIN pins are respectively connected with a fourth controller;

The data acquisition device is further used for carrying out data interaction with the fourth controller through the LIN pin of the second OBD connector based on the LIN communication protocol.

10. The data acquisition system of claim 5 further comprising a fifth controller; wherein,

The second OBD connector is further configured with a group of Ethernet pins, and the Ethernet pins are connected with a fifth controller;

The data acquisition device is further used for performing data interaction with the fifth controller through an Ethernet pin of the second OBD connector based on an Ethernet communication protocol.