Data acquisition system and vehicle

Abstract

This utility model relates to a data acquisition system and a vehicle, and pertains to the field of diagnostic communication technology. The data acquisition system can acquire data from controllers across multiple network segments via the vehicle's OBD connector interface. The data acquisition system includes: an OBD connector, a gateway device, and multiple first controllers; a first port of the OBD connector connects to the data acquisition device, a second port of the OBD connector connects to a first port of the gateway device, and multiple second ports of the gateway device are respectively connected to the multiple first controllers, which belong to at least two different network segments.

Description

Technical Field

[0001] This utility model relates to the field of diagnostic communication technology, specifically to a data acquisition system and a vehicle. Background Technology

[0002] The vehicle OBD (On-Board Diagnostics) connector is the interface through which external devices access the vehicle. Maintenance and testing personnel can use the standard OBD connector to enable data exchange between external devices and various vehicle controllers. During the vehicle's development phase and during post-production vehicle testing, the OBD connector can be used to collect data for communication diagnostics and debugging of the controllers within the vehicle.

[0003] In related technologies, OBD connectors can be used to connect multiple controllers on the same network segment to acquire data from these controllers. However, current vehicles contain controllers on different network segments, necessitating the configuration of multiple OBD connectors to collect data from these controllers. Utility Model Content

[0004] The purpose of this invention is to provide a data acquisition system and vehicle to improve the convenience of data acquisition.

[0005] To achieve the above objectives, the technical solution adopted by this utility model is as follows:

[0006] This utility model provides a data acquisition system. The data acquisition system includes: an OBD connector, a gateway device, and multiple first controllers; the first port of the OBD connector is connected to the data acquisition device, the second port of the OBD connector is connected to the first port of the gateway device, and the multiple second ports of the gateway device are respectively connected to the multiple first controllers, which belong to at least two different network segments.

[0007] Based on the aforementioned technical means, since the gateway device supports connecting to data from controllers in at least two different network segments, it can acquire data from these controllers and transmit it to the data acquisition device via the OBD connector. This allows the data acquisition device to simultaneously collect data from controllers in at least two different network segments, improving the convenience of data acquisition. Alternatively, the data acquisition device can also collect data from controllers in only a single network segment according to its own data acquisition needs. Furthermore, it eliminates the need to configure a corresponding OBD connector for each controller in a network segment, simplifying the complexity of the data acquisition system.

[0008] In one possible implementation, both the first and second ports of the OBD connector are Ethernet ports.

[0009] Based on the aforementioned technical means, Ethernet ports support higher communication rates, enabling the simultaneous acquisition of more data. Furthermore, with the increasing intelligence of automotive functions, the application of Ethernet communication technology in automobiles is becoming more widespread. Given this development, the acquisition of Ethernet data is unavoidable, necessitating the use of OBD connectors and data acquisition devices.

[0010] In one possible implementation, the OBD connector also has a third port, which is connected to a data diagnostic device.

[0011] Based on the aforementioned technical means, the OBD connector can also be connected to a data diagnostic device via a third port, thereby enabling data diagnostics of the vehicle's internal controller.

[0012] In one possible implementation, the gateway device integrates at least one of the following: a TBOX, an electronic control system, and a vehicle control unit.

[0013] Based on the aforementioned technical means, the TBOX, electronic control system, and vehicle control unit may interact with various functional domains in the vehicle, and the gateway device may also interact with various functional domains in the vehicle. Therefore, integrating at least one of the TBOX, electronic control system, and vehicle control unit into the gateway device can reduce the number of wiring harnesses that need to be laid in the vehicle and simplify the circuit complexity of the vehicle.

[0014] In one possible implementation, the multiple second ports of the gateway device include at least one of the following: an Ethernet port, a USB port, a LIN port, and a CAN port.

[0015] Based on the aforementioned technical means, the gateway device supports second ports for multiple communication protocol types, enabling access for first controllers with different communication protocol types. This allows data acquisition devices to simultaneously collect data from controllers supporting different communication protocol types, improving the convenience of data acquisition. Furthermore, it eliminates the need to configure a corresponding OBD connector for each controller with a specific communication protocol type, simplifying the complexity of the data acquisition system.

[0016] In one possible implementation, the gateway device includes a protocol conversion module. The protocol conversion module is used to convert at least one of USB data, LIN data, and CAN data into Ethernet data, or to convert Ethernet data into at least one of USB data, LIN data, and CAN data.

[0017] Based on the aforementioned technical means, the protocol conversion module in the gateway device can enable communication between the data acquisition device and the controller that supports different communication protocol types.

[0018] In one possible implementation, the plurality of first controllers includes at least one of the following functional domain controllers: power domain controller, chassis domain controller, entertainment domain controller, body domain controller, and intelligent driving domain controller.

[0019] Based on the above technical means, it is possible to support data acquisition devices to simultaneously acquire data from different functional domain controllers.

[0020] In one possible implementation, the plurality of first controllers further includes at least one of the following: a controller that communicates via a USB port, a controller that communicates via a LIN port, and a controller that communicates via an Ethernet port.

[0021] Based on the above technical means, it is possible to support data acquisition devices in acquiring data from controllers of other types besides functional domain controllers.

[0022] In one possible implementation, the data acquisition system further includes at least one second controller connected to the first controller.

[0023] Based on the aforementioned technical means, the gateway device can acquire data not only from the first controller directly connected to the gateway device, but also from the second controller indirectly connected to the gateway device, thereby supporting the data acquisition device in collecting data from various controllers inside the vehicle. Furthermore, this avoids being limited by the number of interfaces on the gateway device, expanding the number of controllers that the data acquisition device can simultaneously collect data from.

[0024] This utility model also provides a vehicle, which includes a data acquisition system as provided in any of the above embodiments. Attached Figure Description

[0025] Figure 1 This is a structural diagram of a data acquisition system according to some embodiments;

[0026] Figure 2 This is an interface structure diagram of an OBD connector according to some embodiments;

[0027] Figure 3 This is a structural diagram of a gateway device according to some embodiments. Detailed Implementation

[0028] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0029] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0030] This application provides a data acquisition system that can collect data from various controllers in a vehicle during the vehicle's research and development phase and during after-sales maintenance, in order to enable functional debugging of each controller.

[0031] like Figure 1 As shown, the data acquisition system 1 includes: an OBD connector 10, a gateway device 20, and multiple first controllers 30. The first port of the OBD connector 10 is connected to the data acquisition device 40, the second port of the OBD connector 10 is connected to the first port of the gateway device 20, and the multiple second ports of the gateway device 20 are respectively connected to the multiple first controllers 30, which belong to at least two different network segments.

[0032] In some embodiments, a network segment may include one or more first controllers 30.

[0033] In some embodiments, controllers in the same functional domain may use the same network segment, while controllers in different functional domains may use different network segments.

[0034] In this way, gateway device 20 can acquire data from controllers in at least two different network segments and transmit this data to data acquisition device 40 via OBD connector 10. This enables data acquisition device 40 to simultaneously acquire data from controllers in at least two different network segments, improving the convenience of data acquisition. Alternatively, data acquisition device 40 can also acquire data from controllers in only a single network segment according to its own data acquisition needs. Furthermore, it eliminates the need to configure a corresponding OBD connector 10 for each controller in a network segment, simplifying the complexity of the data acquisition system.

[0035] In some embodiments, both the first and second ports of the OBD connector 10 can be Ethernet ports. It should be understood that Ethernet ports support higher communication rates, enabling the simultaneous acquisition of more data. Furthermore, with the increasing intelligence of automotive functions, Ethernet communication technology is being used more and more widely in vehicles. Given this development, the acquisition of Ethernet data is unavoidable. By using Ethernet ports to connect the OBD connector 10 to the data acquisition device 40 and the gateway device 20, the additional costs associated with Ethernet data acquisition and parsing can be avoided.

[0036] In some embodiments, the second port of the OBD connector 10 may also include a CAN port. That is, the OBD connector 10 can be connected to the gateway device 20 simultaneously via both the Ethernet port and the CAN port.

[0037] In some embodiments, the OBD connector 10 also has a third port, which is connected to a data diagnostic device. In this way, the data diagnostic device can perform fault diagnosis on the vehicle's controller via the OBD connector 10.

[0038] In some embodiments, the third port of the OBD connector 10 can be a CAN port.

[0039] For example, such as Figure 2 As shown, the OBD connector 10 includes 16 pins, and the pin definitions can be found in Table 1:

[0040] Pins 1 and 9 (Ethernet positive (RX+) and Ethernet negative (RX-)) are the positive and negative input pins for the Ethernet interface. The Ethernet positive (RX+) and Ethernet negative (RX-) are the Ethernet input interfaces of the vehicle OBD connector 10.

[0041] Pins 12 and 13 (Ethernet positive (TX+) and Ethernet negative (TX-)) are the positive and negative output pins of the Ethernet interface. Ethernet positive (TX+) and Ethernet negative (TX-) are the Ethernet output interfaces of the vehicle OBD connector 10.

[0042] Pin 8 is the Ethernet wake-up pin.

[0043] One of pins, 4 and 5, is defined as ground, and the other is defined as redundant.

[0044] Pins 6 and 14 (CANH, CANL) are CAN pins. CANH and CANL are the CAN interfaces of the vehicle OBD connector 10.

[0045] Pin 16 is defined as the power supply pin. The power supply pin is used to connect to the positive terminal of the battery.

[0046] Pins 2, 7, 10, 11, and 15 are reserved pins. Reserved pins are custom pins and can be defined as needed.

[0047] Table 1

[0048]

[0049]

[0050] Of course, the definitions of the pins included in the vehicle OBD connector 10 are not limited to those shown in Table 1, and other definitions may also be used. The specific design can be adapted according to actual needs. This is merely an exemplary description of a specific implementation of the application and is not intended to limit the scope of this application.

[0051] In some embodiments, the CAN port or reserved port in Table 1 above can be used as the third port of the OBD connector 10.

[0052] In some embodiments, the gateway device 20 integrates at least one of a telematics box (TBOX), an electronic control system (VCU), and a vehicle control unit.

[0053] For example, the TBOX is used to communicate with the backend system and mobile app to remotely display and control vehicle information. The TBOX connects to the host computer via the vehicle's internal CAN bus, enabling it to acquire real-time information such as vehicle status and button status, and transmit this information to the backend system or mobile app. Simultaneously, it can also receive control commands from the mobile app or backend system to achieve remote vehicle control.

[0054] For example, the VCU, as the vehicle controller of an electric vehicle, is used to coordinate the operation of various components of the vehicle (such as the battery, transmission, motor, engine, etc.). It can collect and process signals from different control modules in real time, such as the accelerator pedal, brake pedal, gear position, battery, motor, etc., thereby realizing comprehensive control and management of the vehicle.

[0055] It should be understood that the TBOX, electronic control system and vehicle control unit may interact with various functional domains in the vehicle, and the gateway device 20 may also interact with various functional domains in the vehicle. Therefore, integrating at least one of the TBOX, electronic control system and vehicle control unit into the gateway device 20 can reduce the number of wiring harnesses that need to be laid in the vehicle and simplify the circuit complexity of the vehicle.

[0056] In some embodiments, the gateway device 20 has multiple second ports, including at least one of the following: an Ethernet port, a USB port, a Local Interconnect Network (LIN) port, and a Controller Area Network (CAN) port. This allows the gateway device 20 to support second ports with multiple communication protocol types, enabling the access of first controllers 30 with different communication protocol types. This facilitates the data acquisition device 40 in simultaneously acquiring data from controllers supporting different communication protocol types, improving the convenience of data acquisition. Furthermore, it eliminates the need to configure a corresponding OBD connector 10 for each controller with a different communication protocol type, simplifying the complexity of the data acquisition system.

[0057] In some embodiments, the gateway device 20 includes a protocol conversion module, which is used to convert at least one of USB data, LIN data, and CAN data into Ethernet data, or to convert Ethernet data into at least one of USB data, LIN data, and CAN data. Thus, the protocol conversion module in the gateway device 20 enables the data acquisition device 40 to communicate with a controller that supports different communication protocol types.

[0058] In some embodiments, the plurality of first controllers 30 include at least one of the following functional domain controllers: power domain controller, chassis domain controller, entertainment domain controller, body domain controller, and intelligent driving domain controller.

[0059] The power domain controller can include the transmission controller, generator controller, airbag controller, and vehicle controller, etc.

[0060] Hybrid domain controllers can include engine controllers, battery management system controllers, and on-board DC-DC converters, among others.

[0061] Comfort domain controllers can include body controllers, door controllers, and seat controllers, among others.

[0062] The chassis domain controller may include the chassis controller.

[0063] The driver assistance domain controller can be a controller that includes devices such as radar, cameras, and surround-view imaging systems.

[0064] Information domain controllers can be controllers for devices such as infotainment systems and dashcams.

[0065] External network connection domain controllers can include controllers such as smart antennas, vehicle-mounted remote communication terminals, and electronic non-stop toll collection systems.

[0066] In some embodiments, the functional domain controller described above may be a controller that communicates via a CAN port.

[0067] In some embodiments, the plurality of first controllers 30 may further include at least one of the following: a controller that communicates via a USB port, a controller that communicates via a LIN port, and a controller that communicates via an Ethernet port. In this way, controllers supporting different communication protocol types can simultaneously access the gateway device 20 and send data to the data acquisition device 40 through the gateway device 20.

[0068] In some embodiments, such as Figure 3 As shown, the data acquisition system also includes at least one second controller 50, which is connected to the first controller 30. That is, some or all of the first controllers 30 may be connected to the second controller 50. Data from the second controller 50 is transmitted to the gateway device 20 via the first controller 30, and then to the data acquisition device 40 via the gateway device 20 and the OBD connector 10. In this way, the gateway device can acquire data not only from the first controllers directly connected to it, but also from the second controllers indirectly connected to it, thus supporting the data acquisition device in acquiring data from various controllers inside the vehicle. Furthermore, this avoids being limited by the number of interfaces on the gateway device, expanding the number of controllers that the data acquisition device can simultaneously acquire data from.

[0069] For example, the first controller 30 and the second controller 50 may be an on-board electronic control unit (ECU).

[0070] By way of example, the data acquisition process of the data acquisition system provided by this utility model is described below. After the data acquisition device 40 is connected to the OBD connector 10, the data acquisition device 40 can send a data acquisition command to the OBD connector 10 in response to the user's operation. The data acquisition command may include information about the target controller to be acquired, such as the controller identifier, the controller IP address, and the network segment to which the controller belongs.

[0071] After receiving the data acquisition command forwarded by the OBD connector 10, the gateway device 20 can forward the data acquisition command to the target controller based on the target controller information carried in the data acquisition command. The target controller then sends the data to be acquired as instructed by the data acquisition command to the gateway device 20.

[0072] Network device 20 can identify the type of data. For example, if it is Ethernet data, it will send it directly to OBD connector 10; if it is CAN data, it will first convert the CAN data into Ethernet data and then send the Ethernet data to OBD connector 10. After receiving the data, OBD connector 10 will forward it to data acquisition device 40.

[0073] This utility model provides a vehicle that includes the aforementioned data acquisition system. A vehicle can also be referred to as a vehicle, mobile carrier, electric vehicle (EV), hybrid electric vehicle (HEV), plug-in hybrid electric vehicle (PHEV), fuel cell vehicle (FCV), autonomous vehicle, intelligent and connected vehicle (ICV), driverless vehicle, etc.

[0074] In this embodiment, the vehicle can be a sedan, a sport utility vehicle (SUV), a truck, an electric vehicle, a motorcycle, a tricycle, a special vehicle (such as an ambulance, fire truck, police car, etc.), a driverless taxi, a smart connected bus, an autonomous logistics vehicle, an electric truck, etc. Furthermore, this data acquisition system is also applicable to various special-purpose vehicles, such as agricultural vehicles, mining vehicles, forestry vehicles, airport vehicles, and port vehicles. This utility model does not impose specific limitations in this regard.

[0075] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data acquisition system, characterized by, The data acquisition system includes: an on-board automatic diagnostic system OBD connector (10), a gateway device (20), and multiple first controllers (30); The first port of the OBD connector (10) is connected to the data acquisition device (40), the second port of the OBD connector (10) is connected to the first port of the gateway device, and the multiple second ports of the gateway device (20) are respectively connected to the multiple first controllers (30), which belong to at least two different network segments.

2. The data acquisition system of claim 1, wherein, The first and second ports of the OBD connector (10) are both Ethernet ports.

3. The data acquisition system of claim 1, wherein, The OBD connector (10) also has a third port, which is connected to a data diagnostic device.

4. The data acquisition system of claim 1, wherein, The gateway device (20) integrates at least one of the following: a remote communication terminal TBOX, an electronic control system, and a vehicle control unit.

5. The data acquisition system of claim 1, wherein, The gateway device (20) has multiple second ports including at least one of the following: an Ethernet port, a Universal Serial Bus (USB) port, a Local Interconnect Network (LIN) port, and a Controller Area Network (CAN) port.

6. The data acquisition system of claim 5, wherein, The gateway device (20) includes a protocol conversion module; the protocol conversion module is used to convert at least one of USB data, LIN data and CAN data into Ethernet data, or to convert Ethernet data into at least one of USB data, LIN data and CAN data.

7. The data acquisition system of claim 1, wherein, The plurality of first controllers (30) include at least one of the following functional domain controllers: power domain controller, hybrid domain controller, comfort domain controller, chassis domain controller, driver assistance domain controller, information domain controller, and external network connection domain controller.

8. The data acquisition system of claim 7, wherein, The plurality of first controllers (30) further include at least one of the following: a controller that communicates via a USB port, a controller that communicates via a LIN port, and a controller that communicates via an Ethernet port.

9. The data acquisition system of claim 1, wherein, The data acquisition system further includes at least one second controller (50), which is connected to the first controller (30).

10. A vehicle characterized by comprising: Includes the data acquisition system according to any one of claims 1 to 9.

Images