Connection device for signal transmission between a charging station and a charging gun

Abstract

A connection device for signal transmission between a charging base and a charging gun is described herein, the connection device comprising: a first connection component at the charging base side; and a second connection component at the charging gun side. The first connection component comprises an OBC controller of two charging communication ports (S+, S-) of opposite polarity; the second connection component comprises: a microcontroller configured to receive SPI bus format signals via an SPI bus connection; a CAN controller comprising a plurality of SPI interfaces in the SPI bus connection with respective pins of the microcontroller; and a CAN transceiver comprising a receiving pin and a transmitting pin in a CAN bus connection with respective interfaces of the CAN controller, and a high level terminal and a low level terminal in the CAN bus connection with the two charging communication ports, respectively.

Description

Technical Field

[0001] This disclosure relates to the field of on-board charging devices for new energy vehicles, and in particular to a connection device for signal transmission between a charging base and a charging gun, and more specifically, to a connection device for wireless signal transmission between a charging base and a charging gun. Background Technology

[0002] Currently, new energy electric vehicles have become a global trend in the transportation industry. Electric vehicles are equipped with charging sockets, which work in conjunction with charging guns to charge the vehicle's battery. Currently, the interaction between the charging socket and the vehicle involves a circuit consisting of 6-10 signal wires connected by wires. This circuit is complex, the assembly process is cumbersome, and the protective casing occupies space within the vehicle, placing high demands on the vehicle's wiring.

[0003] Therefore, in the existing technology, there is an urgent need for an improved connection device for (especially wireless) signal transmission between the charging dock and the charging gun. This can be achieved, for example, through improvements in circuit design such as SPI bus to CAN bus conversion design and the use of wireless protocols (such as Bluetooth, Wi-Fi) to replace multiple wires. This would enable information interaction with the vehicle's OBC (On-Board Charger) via wireless communication, solving the aforementioned problems of saving the required port resources between the charging dock and the charging gun and reducing design costs. Utility Model Content

[0004] The purpose of this disclosure is to solve at least one aspect of the aforementioned problems and defects in the prior art by providing a simple connection device for signal transmission between a charging dock and a charging gun, which is achieved, for example, through a conversion design based on an SPI (Serial Peripheral Interface) bus to a CAN (Controller Area Network) bus, and circuit design improvements such as using wireless protocols (such as Bluetooth, Wi-Fi) to replace multiple wires.

[0005] To achieve the above objectives, this disclosure provides the following technical solution:

[0006] In a first aspect of this disclosure, a connection device for signal transmission between a charging dock and a charging gun is provided. The connection device includes: a first connection component located on the charging dock side; and a second connection component located on the charging gun side. The first connection component includes an OBC controller with two charging communication ports of opposite polarity. The second connection component includes: a microcontroller configured to receive SPI bus format signals via an SPI bus connection; a CAN controller including a plurality of SPI interfaces respectively connected to corresponding pins of the microcontroller via the SPI bus; and a CAN transceiver including receive pins and transmit pins respectively connected to corresponding interfaces of the CAN controller via the CAN bus, and high-level and low-level terminals respectively connected to the two charging communication ports via the CAN bus.

[0007] In an exemplary embodiment, the OBC controller further includes a first wireless module with an embedded wireless protocol, and the microcontroller includes a second wireless module with an embedded wireless protocol; and in response to a handshake between the first wireless module and the second wireless module based on the wireless protocol, the microcontroller triggers the SPI bus connection between the plurality of SPI interfaces of the CAN controller.

[0008] In an exemplary embodiment, the wireless protocol includes one of the following: Bluetooth, Wi-Fi, UWB (Ultra Wideband), NFC (Near Field Communication), and Zigbee.

[0009] In an exemplary embodiment, in response to the microcontroller triggering the SPI bus connection between the plurality of SPI interfaces of the CAN controller, the CAN controller enables the CAN bus connection with the OBC controller.

[0010] In an exemplary embodiment, the plurality of SPI interfaces of the CAN controller include: SPI chip select input, SPI clock input, SPI data input, and SPI data output; and the microcontroller has a plurality of digital signal transmission pins, which are electrically connected to the SPI chip select input, the SPI clock input, the SPI data input, and the SPI data output via the SPI bus.

[0011] In an exemplary embodiment, the CAN controller further includes a CAN signal transmit pin and a CAN signal receive pin; and the CAN transceiver includes a receive pin electrically connected to the CAN signal receive pin via a corresponding CAN bus connection, and a transmit pin electrically connected to the CAN signal transmit pin via a corresponding CAN bus connection.

[0012] In an exemplary embodiment, the CAN transceiver further includes a high-level terminal and a low-level terminal that are electrically connected to the two charging communication ports, respectively.

[0013] In an exemplary embodiment, the OBC controller further includes: a DC power supply positive terminal and a DC power supply negative terminal; a low-voltage auxiliary power supply positive terminal and a low-voltage auxiliary power supply positive terminal and a detection signal terminal, and a pair of charging connection confirmation signal terminals; and the connection device further includes a DC converter connected between the low-voltage auxiliary power supply positive terminal and the low-voltage auxiliary power supply positive terminal and the microcontroller.

[0014] In an exemplary embodiment, the output of the DC converter is electrically connected to the power supply pin of the microcontroller, and the DC converter is configured to step down the voltage input from both the low-voltage auxiliary power supply positive terminal (A+) and the low-voltage auxiliary power supply positive terminal (A-) to a reduced DC voltage suitable for driving the microcontroller and output it to the power supply pin of the microcontroller via its output.

[0015] In an exemplary embodiment, the connection device further includes a TDC circuit (i.e., a temperature measurement circuit or temperature sensing circuit) connected to the microcontroller, and the TDC circuit is configured to perform temperature sensing detection on the terminals (DC+, DC-) of the OBC controller so that the microcontroller can calculate the signal from the OBC controller based on a negative temperature coefficient for temperature compensation. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate certain aspects of the subject matter disclosed herein and, together with the description, help to explain some principles associated with the disclosed embodiments. In the drawings:

[0017] Figure 1 A schematic block diagram showing the connection arrangement for signal transmission between the charging dock and the charging gun in the related art is shown.

[0018] Figure 2 A schematic diagram of port connections for a connection device for signal transmission between a charging dock and a charging gun, according to an embodiment of the present disclosure, is shown.

[0019] Figures 3 to 7 Each is illustrated schematically as follows Figure 2 An exemplary circuit diagram of the various parts of the connection device is shown, schematically illustrating the port connections between the various devices. Specifically, Figures 3 to 7These are schematic circuit diagrams of the microcontroller (MCU), CAN controller for converting between CAN bus and SPI bus, CAN transceiver, DC converter, and TDC circuit in the connection device. Detailed Implementation

[0020] This disclosure will now be described in detail with reference to the accompanying drawings, which are provided as illustrative examples to enable those skilled in the art to practice this disclosure. It is important to note that the following drawings and examples are not intended to limit the scope of this disclosure to a single embodiment, but rather to enable other embodiments by means of interchange of some or all of the described or illustrated elements. Furthermore, where certain elements of this disclosure can be implemented using known components in part or entirely, only those portions of such known components necessary for understanding this disclosure will be described, and detailed descriptions of other portions of such known components will be omitted so as not to obscure this disclosure. Unless otherwise stated herein, it will be understood by those skilled in the art that embodiments described as being implemented in software are not intended to be limited to this, but may include embodiments implemented in hardware or a combination of software and hardware, and vice versa. Embodiments showing a singular number of components in this specification should not be considered limiting; rather, unless expressly stated otherwise herein, this disclosure is intended to cover other embodiments including a plurality of identical components, and vice versa. Furthermore, the applicant does not intend for any terminology in this specification or claims to be relegated to an uncommon or particular meaning unless so expressly stated. In addition, this disclosure covers current and future known equivalents of known components mentioned herein with the aid of illustrations.

[0021] Unless otherwise specified, the terms "bottom" and "top," "upper" and "lower," etc., used in this disclosure are relative concepts. Furthermore, the terms "corresponding" or "corresponding" in this disclosure refer to the correspondence between paired, collaboratively working components.

[0022] Figure 1 A schematic block diagram showing the connection arrangement for signal transmission between the charging dock and the charging gun in the related art is shown.

[0023] In such Figure 1As an example in the related technologies shown, in existing charging sockets for new energy vehicles, the current charging socket design typically matches the charging gun interface and is also consistent with the vehicle's connection points. According to the national industry standard for charging sockets for new energy vehicles, in addition to the high-voltage power line interfaces DC+ and DC-, there are also six low-voltage signal line interfaces: S+ / S- / CC1 / CC2 / A+ / A- (in the new national standard DC charging interface, CC1 and CC2 are used for power connection confirmation; S+ and S- are communication lines between the off-board charger and the electric vehicle; DC+ and DC- are used for charging the battery pack and are high-current lines; A+ and A- connect to the off-board charger, providing low-voltage auxiliary power to the electric vehicle, and the center is ground). Such cumbersome port connections and complex signal loops are not conducive to assembly, require significant space in the vehicle, and are not user-friendly for vehicle wiring.

[0024] Figure 2 A schematic diagram of port connections for a connection device for signal transmission between a charging dock and a charging gun, according to an embodiment of the present disclosure, is shown.

[0025] In one aspect of this disclosure, based on the overall technical concept of this disclosure, such as Figure 2 As shown, a connection device for signal transmission between a charging dock and a charging gun is provided. The connection device includes: a first connection component located on the charging dock side; and a second connection component located on the charging gun side. The first connection component includes an OBC controller with two charging communication ports (S+, S-) of opposite polarity. The second connection component includes: a microcontroller (MCU) configured to receive SPI bus format signals via an SPI bus connection; a CAN controller including a plurality of SPI interfaces respectively connected to corresponding pins of the microcontroller via the SPI bus; and a CAN transceiver including receive pins and transmit pins respectively connected to corresponding interfaces of the CAN controller via the CAN bus, and high-level and low-level terminals respectively connected to the two charging communication ports via the CAN bus (e.g., specifically, high-level and low-level terminals of a differential signal).

[0026] As an example, a microcontroller (MCU) typically only has an SPI bus port and not a CAN bus port. Therefore, in order to achieve CAN-based communication with the charging gun, the SPI bus port needs to be extended to a CAN bus port.

[0027] In exemplary embodiments of this disclosure, for example, the OBC controller further includes a first wireless module with an embedded wireless protocol (e.g., including but not limited to Bluetooth, Wifi, NFC, etc.), and the microcontroller MCU includes a second wireless module with an embedded wireless protocol; and in response to a handshake between the first wireless module and the second wireless module based on the wireless protocol, the microcontroller triggers the SPI bus connection between the plurality of SPI interfaces of the CAN controller.

[0028] In a further embodiment, as an example, the wireless protocol includes one of the following: Bluetooth, Wi-Fi, UWB, NFC, Zigbee.

[0029] As a specific example, in response to the microcontroller triggering the SPI bus connection between the plurality of SPI interfaces of the CAN controller, the CAN controller enables the CAN bus connection with the OBC controller. Such triggering is typically achieved, for example, through hardware-wired signal communication, thus, in the triggered state, subsequent signal interaction between the charging dock and the charging gun is essentially switched to wireless communication. This setup establishes a wireless link based on a wireless communication protocol for information exchange with the vehicle's OBC, thereby eliminating the need for low-voltage wiring harnesses and saving on in-vehicle wiring.

[0030] In a further exemplary embodiment, for example, the two charging communication ports S+ and S- of the OBC controller are essentially CAN bus ports, serving as key interfaces for communication between the charging pile and the electric vehicle (primarily for transmitting control signals and exchanging data). Specifically, for example, the function of S- and S+ is to realize real-time interaction of charging parameters (such as voltage and current requirements and charging status monitoring) through the CAN bus protocol, specifically, for example, to be responsible for transmitting charging control signals and battery management data, thereby ensuring a safe and efficient charging process. Correspondingly, considering that the microcontroller MCU, for example, only has an SPI bus port and not a CAN bus port, the SPI bus port of the microcontroller MCU is extended to a CAN bus port based on the CAN controller and the CAN transceiver in the second connection component, thereby realizing interaction with the OBC controller via the CAN bus.

[0031] This setup enables improvements in circuit design, such as SPI bus to CAN bus conversion and the use of wireless protocols (such as Bluetooth, Wifi, Zigbee) to replace multiple low-voltage wires, thereby solving the aforementioned problems in the prior art of saving the required port resources between the charging dock and the charging gun and reducing design costs.

[0032] Figures 3 to 7 Each is illustrated schematically as follows Figure 2 An exemplary circuit diagram of the various parts of the connection device is shown, schematically illustrating the port connections between the various devices. Specifically, Figures 3 to 7 These are schematic circuit diagrams of the microcontroller (MCU), CAN controller for converting between CAN bus and SPI bus, CAN transceiver, DC converter, and TDC circuit in the connection device.

[0033] In an exemplary embodiment of this disclosure, as shown in the figure as a specific example, the microcontroller is, for example, an MCU with an embedded wireless protocol, typically as illustrated, configured to interact with the OBC controller using a wireless signal transmission link, and it only has an SPI bus port. Thus, information is exchanged with the in-vehicle OBC via wireless communication, thereby eliminating the need for low-voltage wiring harnesses and achieving the goal of saving on in-vehicle wiring.

[0034] Furthermore, the CAN transceiver, such as the one illustrated typically, is configured to receive data from the CAN bus and transmit it to the CAN controller.

[0035] Accordingly, as shown in the figure as a specific example, the CAN controller, which is located between the microcontroller MCU and the CAN transceiver and is communicatively connected to them respectively (specifically, connected to the microcontroller MCU via an SPI bus and to the CAN transceiver via a CAN bus), is typically configured to convert CAN bus format data into SPI bus format data and transmit it to the MCU module.

[0036] In an exemplary embodiment of this disclosure, further as a specific example, for the CAN controller, for example at least as follows: Figure 4 As shown, the CAN controller further includes a CAN signal transmitting pin TXCAN as its transmitting port and a CAN signal receiving pin RXCAN as its receiving port; and correspondingly, the CAN transceiver has a receiving pin RXD (e.g., CAN_RXD1) that is communicatively connected to the CAN signal receiving pin RXCAN via a corresponding CAN bus. Figure 5 (as shown), and the transmit pin TXD (as shown) connected to the CAN signal transmit pin TXCAN via the corresponding CAN bus connection CAN_TXD1. Figure 5 (As shown). This enables the CAN controller to communicate with the CAN transceiver via the CAN bus.

[0037] Furthermore, in an exemplary embodiment of this disclosure, as shown in the figure, the plurality of SPI interfaces of the CAN controller include: SPI chip select input SPI_CS, SPI clock input SPI_CLK, SPI data output SPI_SO, and SPI data input SPI_SI; and the microcontroller has a plurality of digital signal transmission pins DIO8, DIO9, DIO10, and DIO11, which are electrically connected to the SPI chip select input SPI_CS, the SPI clock input SPI_CLK, the SPI data output SPI_SO, and the SPI data input SPI_SI respectively via the SPI bus. Thus, the CAN controller is communicatively connected to the microcontroller MCU via the SPI bus.

[0038] With the above settings, the CAN bus can be extended to the SPI bus by means of the CAN controller, thereby enabling the establishment of a signal interaction path between the microcontroller (MCU) which does not have a CAN bus port and the CAN transceiver.

[0039] In an exemplary embodiment of this disclosure, as shown in the figure as an example, the CAN transceiver further includes a high-level terminal CAN_H and a low-level terminal CAN_L, respectively electrically connected to the two charging communication ports S+ and S- of the OBC controller. In automotive electronic systems, CAN-H is used for high-level data transmission, and CAN-L is used for low-level data transmission, representing high-level and low-level signal transmission, respectively. The CAN bus typically transmits data differentially. Differential data transmission can effectively reduce interference from external electromagnetic noise, especially common-mode noise. Furthermore, the wires connected to CAN_H and CAN_L are two twisted pairs in the Controller Area Network (CAN) communication protocol. When the bus is interfered with, both buses will be affected simultaneously, but their differential voltage will not be affected. Moreover, the specific form in which the two wires of the twisted pair structure are intertwined can effectively suppress electromagnetic interference and improve communication stability.

[0040] Regarding their respective voltage levels, the high-level terminal CAN_H has a higher voltage in the dominant state, while the low-level terminal CAN_L has a lower voltage in the dominant state. As an example, regarding the determination of their respective voltage levels, when the voltage of the high-level terminal CAN_H is higher than that of CAN_L, it indicates a dominant level (low level); when the voltages of the high-level terminal CAN_H and the low-level terminal CAN_L are equal, it indicates a recessive level (high level). In other words, therefore, a dominant level on the CAN bus is represented by logic "0", and a recessive level is represented by logic "1".

[0041] With the above settings, based on the CAN bus connection, signal interaction is achieved between the CAN transceiver and the OBC controller equipped with a CAN bus port.

[0042] In an exemplary embodiment of this disclosure, as shown in the figure, the OBC controller further includes: a DC power supply positive terminal DC+ and a DC power supply negative terminal DC-; a ​​low-voltage auxiliary power supply positive terminal A+ and a low-voltage auxiliary power supply positive terminal A-, a detection signal terminal, and a pair of charging connection confirmation signal terminals CC1 and CC2; and the connection device further includes a DC converter connected between the low-voltage auxiliary power supply positive terminals A+ and A- and the microcontroller MCU. As a specific example, as shown in the figure, the low-voltage auxiliary power supply positive terminals A+ and A- of the charging gun are stepped down to 3.3V via the DC converter to power the wireless MCU chip.

[0043] It should be noted that, for the sake of brevity, Figures 3 to 7 The OBC controller in the first connection component of the connection device is not shown. Only the corresponding ports to which the various circuit parts lead are shown, such as the two charging communication ports S+ and S-, the DC power positive terminal DC+ and the DC power negative terminal DC-; the low-voltage auxiliary power positive terminal A+ and the low-voltage auxiliary power positive terminal A- and the detection signal terminal, and a pair of charging connection confirmation signal terminals CC1 and CC2.

[0044] In a further exemplary embodiment, as shown, for example, the output of the DC converter is electrically connected to the power supply pin of the microcontroller, and the DC converter is configured to step down the voltage input from the positive terminal A+ of the low-voltage auxiliary power supply to a reduced DC voltage suitable for driving the microcontroller, and output it to the power supply pin of the microcontroller via its output. Thus, the DC converter facilitates the use of both the auxiliary power supplies A+ and A- of the charging gun for powering the microcontroller (MCU).

[0045] In an exemplary embodiment of this disclosure, as shown in the figure as an example, the connection device further includes a temperature sensing circuit TDC electrically connected to the microcontroller. The temperature sensing circuit TDC is configured to detect temperature at terminals (DC+, DC) of the OBC controller so that the microcontroller can calculate temperature compensation based on the signal from the OBC controller using a negative temperature coefficient. Specifically, as an example, a negative temperature coefficient is used as the basis for temperature compensation, thereby introducing analog quantities (e.g., temperature changes cause resistance changes, and consequently voltage changes, from which the temperature value is determined based on the detected quantity value according to circuit parameters; subsequently, the ambient temperature is displayed based on the read voltage). Typically, higher temperatures generally correspond to higher resistance.

[0046] With this configuration, the temperature sensing circuit (TDC) performs temperature compensation for the measured values ​​of circuit parameters based on a negative temperature coefficient, thereby ensuring the robustness of the circuit parameter measurements and the accuracy of the signals under temperature changes.

[0047] Based on the above-described connection device for signal transmission between the charging base and the charging gun, the following superior technical effects compared to existing technical solutions in the field can be achieved:

[0048] For example, by using a conversion design based on the SPI bus to the CAN bus, a microcontroller MCU with an embedded wireless protocol that only has an SPI bus port instead of a CAN bus port can be used, thereby expanding the application field; and by using wireless protocols (such as Bluetooth, Wi-Fi) to replace multiple low-voltage wires in circuit design improvements, the aforementioned problems of saving port resources required between the charging dock and the charging gun, saving low-voltage wire wiring, and reducing design costs can be solved.

[0049] The above description of the cascaded circuits in the foregoing embodiments of this disclosure is intended to be illustrative and not restrictive. Although this disclosure has been described in conjunction with the accompanying drawings, the embodiments disclosed in the drawings are intended to exemplify preferred embodiments of this disclosure and should not be construed as limiting this disclosure.

[0050] Therefore, those skilled in the art will understand that the embodiments described above are exemplary and can be improved by those skilled in the art. The structures described in the various embodiments can be modified and freely combined without conflict in structure or principle, and these changes should fall within the protection scope of this disclosure.

[0051] The breadth and scope of this disclosure should not be limited to any of the embodiments described above, but should be defined only by the following claims and their equivalents.

[0052] It should be noted that the word "comprising" does not exclude other elements or steps, and the words "a" or "an" do not exclude multiple. Furthermore, any element reference numerals in the claims should not be construed as limiting the scope of this disclosure.

Claims

1. A connection device for signal transmission between a charging base and a charging gun, characterized in that, The connecting device includes: A first connection component, located on the charging dock side, includes: The OBC controller includes two charging communication ports of opposite polarity (S+, S-). The second connection component, located on the charging gun side, includes: The microcontroller is configured to receive SPI bus format signals via an SPI bus connection; The CAN controller includes multiple SPI interfaces that are respectively connected to corresponding pins of the microcontroller via the SPI bus; The CAN transceiver includes a receive pin (RXD) and a transmit pin (TXD) that are respectively connected to the corresponding interfaces of the CAN controller via a CAN bus, and a high-level terminal and a low-level terminal that are respectively connected to the two charging communication ports via the CAN bus.

2. The connecting device according to claim 1, characterized in that, The OBC controller further includes a first wireless module with an embedded wireless protocol, and the microcontroller includes a second wireless module with an embedded wireless protocol. In response to a handshake between the first wireless module and the second wireless module based on the wireless protocol, the microcontroller triggers the SPI bus connection between the plurality of SPI interfaces of the CAN controller.

3. The connecting device according to claim 2, characterized in that, The wireless protocol includes one of the following: Bluetooth, Wi-Fi, UWB, NFC, and Zigbee.

4. The connecting device according to claim 2, characterized in that, In response to the microcontroller triggering the SPI bus connection between the plurality of SPI interfaces of the CAN controller, the CAN controller enables the CAN bus connection with the OBC controller.

5. The connecting device according to claim 2, characterized in that, The CAN controller's plurality of SPI interfaces include: SPI chip select input (SPI_CS), SPI clock input (SPI_CLK), SPI data output (SPI_SO), and SPI data input (SPI_SI); and The microcontroller has multiple digital signal transmission pins (DIO8, DIO9, DIO10, DIO11), which are electrically connected to the SPI chip select input (SPI_CS), the SPI clock input (SPI_CLK), the SPI data output (SPI_SO), and the SPI data input (SPI_SI) via the SPI bus.

6. The connecting device according to claim 2, characterized in that, The CAN controller also includes a CAN signal transmit pin (TXCAN) and a CAN signal receive pin (RXCAN); and The CAN transceiver includes a receive pin (RXD) electrically connected to the CAN signal receive pin (RXCAN) via a corresponding CAN bus connection (CAN_RXD1), and a transmit pin (TXD) electrically connected to the CAN signal transmit pin (TXCAN) via a corresponding CAN bus connection (CAN_TXD1).

7. The connecting device according to claim 6, characterized in that, The CAN transceiver also has a high-level terminal (CAN_H) and a low-level terminal (CAN_L) that are electrically connected to the two charging communication ports (S+, S-), respectively.

8. The connecting device according to claim 1, characterized in that, The OBC controller also includes: a DC power positive terminal (DC+) and a DC power negative terminal (DC-); a low-voltage auxiliary power positive terminal (A+) and a low-voltage auxiliary power positive terminal (A-); a detection signal terminal; and a pair of charging connection confirmation signal terminals (CC1, CC2). The connection device further includes a DC converter, which is connected between the low-voltage auxiliary power supply positive terminal (A+) and the low-voltage auxiliary power supply positive terminal (A-) and the microcontroller.

9. The connecting device according to claim 8, characterized in that, The DC converter is electrically connected at its input terminal to the positive terminal (A+) of the low-voltage auxiliary power supply and at its output terminal to the power supply pin of the microcontroller, so as to supply the microcontroller with the DC voltage obtained by stepping down the voltage input from the positive terminal (A+) of the low-voltage auxiliary power supply.

10. The connecting device according to claim 8, characterized in that, The connection device further includes a TDC circuit connected to the microcontroller, and the TDC circuit is configured to perform temperature sensing on the terminals (DC+, DC-) of the OBC controller so that the microcontroller can calculate the signal from the OBC controller based on a negative temperature coefficient for temperature compensation.

Images