CAN bus system and vehicle

Abstract

The utility model relates to a CAN bus system, which comprises a CAN bus and a controller interface connected with the CAN bus, the controller interface is used for being detachably connected with a vehicle controller, and the controller interface is internally provided with a communication pin group for establishing communication connection between external diagnosis equipment and the CAN bus. The utility model further provides a vehicle. According to the utility model, the difficulty of cancelling a vehicle OBD diagnosis port is reduced, the vehicle controller data acquisition and vehicle controller software flashing can be realized under the condition that the vehicle OBD diagnosis port is cancelled, and the vehicle controller data acquisition and vehicle controller software flashing can be realized.

Description

Technical Field

[0001] This utility model relates to the field of vehicle technology, specifically to a CAN bus system and a vehicle. Background Technology

[0002] The vehicle's OBD diagnostic port is primarily used to read message data from various vehicle controllers, including battery status, motor performance, and control system parameters, thereby accurately determining whether there are problems with the vehicle or tracing the cause of a fault. The OBD diagnostic port is also used in application scenarios where the software of various vehicle controllers needs iterative updates or bug fixes. Through the OBD diagnostic port, operators can quickly and accurately detect and read data from various vehicle controllers or perform software flashing for these controllers.

[0003] During vehicle design, there may be a need to eliminate the OBD diagnostic port. This could be due to local regulations in some overseas markets prohibiting the inclusion of an OBD diagnostic port, or it could be removed to reduce costs and increase efficiency. Removing the OBD diagnostic port prevents external diagnostic equipment from communicating with the vehicle's CAN bus, reading or collecting vehicle data messages, and rewriting the vehicle controller software. Therefore, eliminating the OBD diagnostic port is a significant challenge. Utility Model Content

[0004] The purpose of this invention is to propose a CAN bus system and vehicle to reduce the difficulty of eliminating the vehicle's OBD diagnostic port.

[0005] The present invention discloses a CAN bus system, including a CAN bus and a controller interface connected to the CAN bus. The controller interface is used for detachably connecting a vehicle controller, and the controller interface is provided with a communication pin group that enables external diagnostic equipment to establish a communication connection with the CAN bus.

[0006] Optionally, at least two of the controller interfaces may be included.

[0007] Optionally, at least two of the controller interfaces include a PDU controller interface and / or a BMS controller interface and / or an RMIPU controller interface and / or a VCU controller interface and / or an ITMS controller interface.

[0008] Optionally, the vehicle controller establishes a communication connection with the CAN bus through the communication pin group.

[0009] Optionally, the communication pin group includes CAN_H pins and CAN_L pins.

[0010] Optionally, the CAN bus is a PTCAN bus.

[0011] Optionally, the controller interface is a connector.

[0012] Optionally, an OBD diagnostic port connected to the CAN bus may also be included.

[0013] Optionally, the OBD diagnostic port includes a CAN_H pin and a CAN_L pin.

[0014] This utility model also proposes a vehicle that includes the CAN bus system described in any of the above claims.

[0015] This invention reduces the difficulty of eliminating the vehicle's OBD diagnostic port, and features a simple structure and low implementation cost. Even without the vehicle's OBD diagnostic port, it can still achieve the acquisition of vehicle controller data and the flashing of vehicle controller software. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the CAN bus system with the OBD diagnostic port removed in some embodiments;

[0017] Figure 2 This is a schematic diagram of the data acquisition and transmission path of a CAN bus system that has eliminated the OBD diagnostic port in some embodiments;

[0018] Figure 3 This is a schematic diagram of the structure of the PDU controller interface, BMS controller interface, RMIPU controller interface, VCU controller interface and ITMS controller interface described in some embodiments;

[0019] Figure 4 This is a schematic diagram of the CAN bus system with OBD diagnostic port described in some embodiments;

[0020] Figure 5 This is a schematic diagram of the structure of the OBD diagnostic port described in some embodiments;

[0021] Figure 6 This is a schematic diagram of the data acquisition and transmission path of a CAN bus system with an OBD diagnostic port as described in some embodiments.

[0022] In the diagram, 100—CAN bus, 101—PDU controller interface, 102—BMS controller interface, 103—RMIPU controller interface, 104—VCU controller interface, 105—ITMS controller interface, 106—OBD diagnostic port, 1011—first CAN_H pin, 1012—first CAN_L pin, 1021—second CAN_H pin, 1022—second CAN_L pin, 1031—third CAN_H pin, 1 032—Third CAN_L pin, 1041—Fourth CAN_H pin, 1042—Fourth CAN_L pin, 1051—Fifth CAN_H pin, 1052—Fifth CAN_L pin, 1061—Sixth CAN_H pin, 1062—Sixth CAN_L pin, 200—PDU controller, 300—BMS controller, 400—RMIPU controller, 500—VCU controller, 600—ITMS controller, 700—Wire harness. Detailed Implementation

[0023] The embodiments of this utility model will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this utility model from the content disclosed in this specification. This utility model can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this utility model. It should be understood that the preferred embodiments are only for illustrating this utility model and not for limiting the scope of protection of this utility model.

[0024] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the number, shape and size of the components in actual implementation. In actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0025] like Figure 1 The CAN bus system shown includes a CAN bus 100 and a controller interface connected to the CAN bus 100. The controller interface is used to detachably connect to a vehicle controller. The controller interface is provided with a communication pin group that enables external diagnostic equipment to establish a communication connection with the CAN bus 100.

[0026] By employing the above technical solution, a communication pin group is defined in the controller interface to enable external diagnostic devices to establish a communication connection with the CAN bus 100. Even when the vehicle's OBD diagnostic port 106 is removed, after disconnecting the controller from the controller interface, the external diagnostic device can establish a communication connection with the CAN bus 100 through the communication pin group of the controller interface. This allows for controller information acquisition or software rewriting for vehicles without an OBD diagnostic port. This reduces the difficulty of removing the vehicle's OBD diagnostic port 106, and features a simple structure and low implementation cost. It also enables controller data acquisition and controller software rewriting even when the vehicle's OBD diagnostic port is removed.

[0027] As a specific example, a CAN bus system includes at least two controller interfaces. Having at least two controller interfaces allows for data acquisition and software updates between them, preventing situations where some vehicle controllers cannot be diagnosed or updated.

[0028] In some embodiments, at least two controller interfaces include a PDU controller interface 101 for detachably connecting to a PDU controller 200, a BMS controller interface 102 for detachably connecting to a BMS controller 300, an RMIPU controller interface 103 for detachably connecting to an RMIPU controller 400, a VCU controller interface 104 for detachably connecting to a VCU controller 500, and an ITMS controller interface 105 for detachably connecting to an ITMS controller 600.

[0029] In some embodiments, the vehicle controller establishes a communication connection with the CAN bus 100 via a communication pin group. The vehicle controller and external diagnostic devices establish communication connections with the CAN bus 100 via the same defined communication pin group, facilitating communication between the vehicle controller and the external diagnostic devices. In specific implementations, the external diagnostic device can connect to the communication pin group via a wiring harness 700 or a connector, thereby establishing a communication connection with the CAN bus 100.

[0030] In some embodiments, the communication pin group includes CAN_H pins and CAN_L pins. For example... Figure 2As shown, as a specific example, the PDU controller interface 101 has a first CAN_H pin 1011 and a first CAN_L pin 1012, the BMS controller interface 102 has a second CAN_H pin 1021 and a second CAN_L pin 1022, the RMIPU controller interface 103 has a third CAN_H pin 1031 and a third CAN_L pin 1032, the VCU controller interface 104 has a fourth CAN_H pin 1041 and a fourth CAN_L pin 1042, and the ITMS controller interface 105 has a fifth CAN_H pin 1051 and a fifth CAN_L pin 1052.

[0031] With the OBD diagnostic port 106 removed, software updates to the PDU controller 200 can no longer be performed via the original method of connecting to the OBD diagnostic port 106. Using the above-described technical solution, the ITMS controller interface 105 and the PDU controller interface 101 share the same defined CAN_H and CAN_L pins. External diagnostic devices can establish communication with the CAN bus 100 through the fifth CAN_H pin 1051 and the fifth CAN_L pin 1052 of the ITMS controller interface 105, thereby establishing communication with the PDU controller 200 and enabling data acquisition or software flashing operations on the PDU controller 200.

[0032] like Figure 3 As shown, with the OBD diagnostic port 106 disabled, data is acquired from the PDU controller 200 via the fifth CAN_H pin 1051 and the fifth CAN_L pin 1052 of the ITMS controller interface 105. The message data from the PDU controller 200 is transmitted to the CAN bus 100 via the first CAN_H pin 1011 and the first CAN_L pin 1012 of the PDU controller interface 101, and then transmitted to the external diagnostic device via the fifth CAN_H pin 1051 and the fifth CAN_L pin 1052 of the ITMS controller interface 105.

[0033] As a specific example, CAN bus 100 is a PTCAN bus.

[0034] In some embodiments, such as Figure 4 As shown, the CAN bus system also includes an OBD diagnostic port 106 connected to the CAN bus 100. When there is a need for the OBD diagnostic port 106, it can be connected to the CAN bus 100.

[0035] In some embodiments, such as Figure 5As shown, the OBD diagnostic port 106 includes a sixth CAN_H pin 1061 and a sixth CAN_L pin 1062. The VCU controller 500, PDU controller 200, RMIPU controller 400, ITMS controller 600, BMS controller 300, and other controllers establish communication with the CAN bus 100 by each controller having CAN_H and CAN_L pins for inputting or outputting communication signals. Similarly, the OBD diagnostic port 106 also has CAN_H and CAN_L pins connected to the CAN bus 100 to establish communication connections with each controller. All controllers and the OBD diagnostic port 106 share the same CAN bus 100 communication loop, and interactive communication between the controllers and the OBD diagnostic port 106 is achieved through the CAN_H and CAN_L pins, providing universal applicability.

[0036] like Figure 6 As shown, in a scenario where the OBD diagnostic port 106 is retained, when data is acquired from the PDU controller 200, the message data from the PDU controller 200 is transmitted to the CAN bus 100 via the first CAN_H pin 1011 and the first CAN_L pin 1012 of the PDU controller interface 101. Then, the message data is transmitted to the OBD diagnostic port 106 via a branch harness connected to the OBD diagnostic port 106. Finally, the message data is transmitted to an external diagnostic device via the sixth CAN_H pin 1061 and the sixth CAN_L pin 1062 of the OBD diagnostic port 106. Similarly, when the sixth CAN_H pin 1061 and the sixth CAN_L pin 1062 of the OBD diagnostic port 106 are connected to an external diagnostic device for software flashing, the software program data can be transmitted in reverse along the above data acquisition and transmission path, thereby achieving software flashing.

[0037] This utility model also proposes a vehicle that includes the CAN bus system described in any of the above claims.

[0038] The above embodiments are merely preferred embodiments provided to fully illustrate the present utility model, and the protection scope of the present utility model is not limited thereto. Equivalent substitutions or modifications made by those skilled in the art based on the present utility model are all within the protection scope of the present utility model. In the description of this specification, the reference to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., means that a specific feature, structure, material, or characteristic associated with that embodiment or example is included in at least one embodiment or example of the present utility model. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described in this specification.

Claims

1. A CAN bus system, characterized in that The CAN bus (100) and a controller interface connected with the CAN bus (100), the controller interface being used for detachably connecting a vehicle controller, and a communication pin group being arranged in the controller interface and capable of establishing a communication connection between an external diagnosis device and the CAN bus (100).

2. CAN bus system according to claim 1, characterized in that The controller interface comprises at least two controller interfaces.

3. CAN bus system according to claim 1, characterized in that The controller interface comprises a PDU controller interface (101) and / or a BMS controller interface (102) and / or an RMIPU controller interface (103) and / or a VCU controller interface (104) and / or an ITMS controller interface (105).

4. The CAN bus system according to claim 1, characterized in that The vehicle controller establishes a communication connection with the CAN bus (100) through the communication pin group.

5. The CAN bus system according to claim 1, characterized in that The communication pin group comprises a CAN_H pin and a CAN_L pin.

6. The CAN bus system according to claim 1, characterized in that The CAN bus (100) is a PTCAN bus.

7. The CAN bus system according to claim 1, characterized in that The controller interface is a connector.

8. The CAN bus system according to claim 1, characterized in that An OBD diagnosis port (106) connected with the CAN bus (100) is further included.

9. CAN bus system according to claim 8, characterized in that The OBD diagnosis port (106) comprises a CAN_H pin and a CAN_L pin.

10. A vehicle characterized by comprising: The CAN bus system according to any one of claims 1-9 is included.

Images