Adapter for vehicle diagnostic port

Abstract

The present invention relates to an adapter (10) for a vehicle OBD-type diagnostic port, referred to as the OBD port. For this purpose, the adapter (10) comprises a cable (100) with a plurality of flexible conductors. A first connector (101) is arranged at one end of the cable (100), the first connector (101) having a plurality of pins and being configured to cooperate with the vehicle's OBD port (11). A second connector (102) is arranged at a second end of the cable (100), the second connector (102) having a plurality of pins and being configured to cooperate with a 35-pin connector of a data logger (12). Figure 1

Description

Title of the invention: Adapter for vehicle diagnostic socket Technical field

[0001] The invention relates to an adapter for a vehicle diagnostic port, particularly, but not exclusively, for a motor vehicle. The invention also relates to a system comprising such an adapter, a vehicle, and a data logger. Technological background

[0002] Modern vehicles are equipped with a so-called diagnostic port configured to allow a diagnostic system or tool to connect to the vehicle's network of computers, also known as the on-board computer system. Such a port is generally of the OBD type (On-Board Diagnostics), which allows data to be retrieved from the vehicle to perform a diagnostic check, for example, to detect problems in the vehicle's systems by retrieving fault codes, known as DTCs (Data Trouble Codes). An automotive technician uses an OBD-type diagnostic tool or scanner, which they connect to the OBD port, to quickly identify vehicle problems.The diagnostic tool is specifically designed to retrieve DTC codes generated by the vehicle's on-board system and obtain real-time data associated with one or more parameter identification numbers, known as PIDs (Process Identifiers).

[0003] However, not all diagnostic tools are configured to connect to an OBD port. Some data loggers required for certain types of vehicle testing are not compatible with the OBD port. For example, data obtained during DSCDA (Diagnosys of Safety Compliance Driving Assessment) tests is in a specific format that an OBD diagnostic tool does not provide. It is then necessary to convert the data obtained via the OBD diagnostic tool connecting to the vehicle's OBD port in order to record the driving data in the expected format, which can lead to errors. Summary of the present invention

[0004] One object of the present invention is to solve at least one of the problems of the technological background described above.

[0005] Another object of the present invention is, for example, to improve the recording of vehicle diagnostic data.

[0006] According to a first aspect, the present invention relates to an adapter for a vehicle OBD type diagnostic socket, referred to as the OBD socket, the adapter comprising: - a cable comprising a plurality of flexible conductors; - a first connector arranged at one end of the cable, the first connector comprising a plurality of pins and being configured to cooperate with the vehicle's OBD port; and - a second connector arranged at a second end of the cable, the second connector comprising a plurality of pins and being configured to cooperate with a 35-way socket of a data logger.

[0007] The adapter, consisting of a cable with an OBD connector at one end and a 35-pin connector at the other, retrieves data from the vehicle's OBD port and transmits it to a specific data logger. The data logger records the data in the expected format directly from the OBD port, eliminating the need for format conversion and significantly reducing the associated risk of error.

[0008] According to one embodiment, the first connector comprising 16 pins, each pin of the first connector having a unique index number between 1 and 16, the second connector comprising 35 pins, each pin of the second connector having a unique index number between 1 and 35, the plurality of flexible conductors comprises: - a first flexible conductor connecting a first pin of the first connector having index number 16 to a first pin of the second connector having index number 19; - a second flexible conductor connecting a second pin of the first connector having an index number of 4 to a second pin of the second connector having an index number of 9; - a third flexible conductor connecting a third pin of the first connector having index number 6 to a third pin of the second connector having index number 33; - a fourth flexible conductor connecting a fourth pin of the first connector having index number 14 to a fourth pin of the second connector having index number 32; - a fifth flexible conductor connecting a fifth pin of the first connector, indexed 3, to a fifth pin of the second connector, indexed 35; and - a sixth flexible conductor connecting a sixth pin of the first connector having index number 8 to a fifth pin of the second connector having index number 34.

[0009] According to another variant: - the first flexible conductor is suitable for carrying a signal representative of a positive battery of the vehicle; - the second flexible conductor is adapted to carry a signal representing a mass connected to a chassis of the vehicle; - the third flexible conductor is adapted to carry a signal from a first line of a first data bus of the vehicle of type CAN, the first line being of type CAN High; - the fourth flexible conductor is adapted to carry a signal from a second line of the vehicle's first CAN type data bus, the second line being of CAN Bas type; - the fifth flexible conductor is adapted to carry a signal from the first line of a second CAN-type vehicle data bus, the first line being of the CAN High type; and - the sixth flexible conductor is adapted to carry a signal from a second line of the vehicle's second CAN type data bus, the second line being of CAN Bas type.

[0010] According to yet another variant, the pins of the plurality of pins of the first connector correspond to male pins.

[0011] According to a further variant, the pins of the plurality of pins of the second connector correspond to female pins.

[0012] According to another variant, the second connector includes a keying feature.

[0013] According to a second aspect, the present invention relates to a system comprising a vehicle, a data logger and an adapter as described above according to the first aspect of the present invention, the adapter being connected to an OBD port of the vehicle via the first connector of the adapter and the adapter being connected to a 35-way port of the data logger via the second connector of the adapter. Brief description of the figures

[0014] Other features and advantages of the present invention will become apparent from the description of the specific and non-limiting embodiments of the present invention below, with reference to the attached Figures 1 to 2, in which:

[0015] [Fig-1] schematically illustrates a system comprising a vehicle, a recorder data and an adapter for the vehicle's OBD type diagnostic port, according to a particular and non-limiting embodiment of the present invention;

[0016] [Fig.2] schematically illustrates the adapter of [Fig.1], according to a particular and non-limiting embodiment of the present invention. Description of examples of achievements

[0017] A vehicle OBD type diagnostic socket adapter and a system comprising such an adapter will now be described in what follows with joint reference to Figures 1 to 2. The same elements are identified with the same reference signs throughout the following description.

[0018] The terms "first," "second" (or "firsts," "seconds"), etc., are used in this document by arbitrary convention to allow for the identification and distinction of different elements (such as operations, means, etc.) implemented in the embodiments described below. Such elements may be distinct or correspond to a single element, depending on the embodiment.

[0019] Fig. 1 schematically illustrates a system 1 comprising a vehicle 11, a data recorder 12 and an adapter 10 for the vehicle's OBD-type diagnostic port, according to a particular and non-limiting embodiment of the present invention.

[0020] Vehicle 11 corresponds, for example, to a vehicle with an internal combustion engine, with electric motor(s), or a hybrid vehicle with an internal combustion engine and one or more electric motors. Vehicle 11 thus corresponds, for example, to a land vehicle, such as a car, a truck, a bus, or a motorcycle.

[0021] The vehicle 11 carries a set of computers forming an embedded computer network, also called the vehicle 11 embedded system.

[0022] These computers form, for example, a multiplexed architecture for the implementation of various services useful for the proper functioning of the vehicle 11 and for assisting the driver and / or passengers of the vehicle 11 in controlling the vehicle 11 via the control of a set of systems embedded in the vehicle 11. The computers communicate and exchange data with each other via one or more computer buses, for example a communication bus of the type CAN data bus (from the English "Controller Area Network" or in French "Réseau de contrôlers"), CAN FD (from the English "Controller Area Network Flexible Data-Rate" or in French "Réseau de contrôlers à débit de données flexible"), FlexRay (according to the ISO 17458 standard), LIN (from the English "Local Interconnect Network" or in French "Réseau interconnecté local") or Ethernet (according to the ISO / IEC 802-3 standard).

[0023] The vehicle 11 further includes an OBD port or socket enabling a diagnostic tool or system to connect to the vehicle 11's on-board network to obtain a set of diagnostic data, which includes, for example, a set of DTC codes and / or PIDs generated by one or more control units in the vehicle 11's on-board control unit network. The OBD socket (or second-generation OBD 2 socket (or port)) corresponds to a connector or wired communication interface, for example, a 16-pin socket. The socket OBD corresponds to an OBD 2 connector of type A or type B, depending on the vehicle size 11.

[0024] Diagnostic data is transmitted, for example, according to a communication protocol such as the UDS protocol (Unified Diagnostic Services). Each control unit of the vehicle's embedded system 11 (or each control unit of a subset of the control units forming the embedded system) implements, for example, a UDS-type service for the communication of diagnostic data (DTC codes, for example).

[0025] The communication of diagnostic data based on CAN type communication systems between the vehicle's on-board network 11 and the OBD socket is standardized according to ISO 15765-4:2021 and SAE J1939-71 standards.

[0026] An OBD connector comprises 16 pins, each with a unique index number from 1 to 16. Some of the pins use communication protocols according to standards such as ISO 15765-4:2021 and SAE J1939-71. The pinout of an OBD connector is, for example, as follows: - Index number pin 1: reserved for the vehicle manufacturer, such a pin is not standard and its use depends on the vehicle manufacturer; - pin with index number 2: positive pin of the SAE J1850 PWM protocol bus (from the English "Push Width Modulation" or in French "pulse width modulation"); - Index number pin 3: reserved for the vehicle manufacturer, such a pin is not standard and its use depends on the vehicle manufacturer; - Index number pin 4: chassis ground pin used for system grounding (connected to the vehicle chassis); - Index number pin 5: signal ground pin used for system ground (connected to vehicle chassis); - Pin with index number 6: CAN high pin (from the English "CAN HIGH") according to ISO 15765-4:2021 and SAE J2284 standards for the implementation of a 2-line (or 2-wire) communication protocol at a rate of 1 Mb / s; - pin with index number 7: K line pin according to ISO 9141-2 and ISO 14230-4 standards using an asynchronous serial communication protocol; - Pin with index number 8: reserved for the vehicle manufacturer; this pin is not standard and its use depends on the manufacturer; - Pin with index number 9: reserved for the vehicle manufacturer; this pin is not standard and its use depends on the manufacturer; - Pin with index number 10: negative pin of the SAE J1850 PWM protocol bus - Pin with index number 11: reserved for the vehicle manufacturer; this pin is not standard and its use depends on the manufacturer; - Pin with index number 12: reserved for the vehicle manufacturer; this pin is not standard and its use depends on the manufacturer; - Pin with index number 13: reserved for the vehicle manufacturer; this pin is not standard and its use depends on the manufacturer; - Pin with index number 14: CAN Low pin (from the English "CAN LOW") according to ISO 15765-4:2021 and SAE J2284 standards for implementing a 2-line (or 2-wire) communication protocol at a data rate of 1 Mb / s - Pin with index number 15: L-line pin according to ISO 9141-2 and ISO 14230-4 standards using an asynchronous serial communication protocol; and - Index number pin 16: Battery positive pin (“+ battery”) connected to the vehicle battery to power scan-type tools, with a 12V / 4A supply for Type A OBD sockets and a 24V / 2A supply for Type B OBD sockets.

[0027] The pins of the vehicle's OBD connector 11 correspond to female pins. According to an alternative embodiment, the pins of the vehicle's OBD connector 11 correspond to male pins.

[0028] The data logger 12 is configured to record data provided by the vehicle's onboard network. The data logger includes a 35-way, and therefore 35-pin, connector; the data logger 12 is thus not natively configured or adapted to connect to the OBD connector of the vehicle 11. The data logger 12 is configured for the acquisition and storage of data obtained from the onboard network of a vehicle such as the vehicle 11. The data logger 12 is, for example, configured for the acquisition and recording of data obtained from one or more CAN or CAN FD buses of the vehicle 11. Alternatively, the data logger 12 is further configured for the acquisition and recording of data obtained from one or more LIN buses of the vehicle 11.

[0029] The 35-way connector of the data logger 12 comprises 35 male pins. According to one embodiment, the 35 pins of the 35-way connector of the data logger 12 correspond to female pins.

[0030] The adapter 10 of system 1 is configured and adapted to link or connect the vehicle 11 to the data recorder 12, and more specifically the OBD socket of the vehicle 11 to the 35-way socket of the data recorder 12, so as to carry the data and signals arriving on at least some of the pins of the OBD socket of the vehicle 11 to corresponding pins of the 35-way socket of the data recorder 12.

[0031] Adapter 10 comprises for this purpose: - a 100 cable comprising a plurality of flexible conductors; - a first connector 101 arranged at one end of cable 100, the first connector 101 comprising a plurality of pins and being configured to cooperate with the vehicle's OBD socket 11; and - a second connector 102 arranged at a second end of cable 100 (which is opposite to the first end of cable 100), the second connector 102 comprising a plurality of pins and being configured to cooperate with the 35-way socket of data logger 12.

[0032] Each flexible conductor comprises, for example, a plurality of strands arranged parallel to each other, the strands being made of an electrically conductive material such as copper.

[0033] Each flexible conductor is fixed, for example crimped, at one end to a pin of the first connector 101 and fixed, for example crimped, at a second end (opposite to the first end) to a pin of the second connector 101. Such a flexible conductor thus conducts or carries a signal from the pin of the first connector 101 to the pin (called corresponding pin) of the second connector 102, the 2 pins being linked and connected together via this flexible conductor.

[0034] The length of cable 100 is arbitrary, for example equal to 1, 2, 3 or 5 m or within a length range between 0.5 and 10 m.

[0035] Flexible conductors are, for example, inserted all together in a sheath protecting them from the external environment. The sheath is made of a flexible material such as polyethylene (PE), a polyester-based thermoplastic elastomer (TPE-E), polyvinyl chloride (PVC), etc.

[0036] The first connector 101 comprises 16 pins, each configured to cooperate with a pin of the vehicle's OBD port 11. The 16 pins of the first connector 101 correspond to male pins when the pins of the OBD port correspond to female pins. Alternatively, the 16 pins of the first connector 101 correspond to female pins when the pins of the OBD port correspond to male pins.

[0037] The pins of the first connector 101 are indexed in such a way that each pin of the first connector has a unique index number between 1 and 16.

[0038] The second connector 102 comprises 35 pins, each configured to cooperate with one pin of the 35-way socket of the data logger 12. The 35 pins of the second connector 102 correspond to female pins, while the pins of the 35-way socket correspond to male pins. Alternatively, the The 35 pins of the second 102 connector correspond to male pins when the pins of the 35-way socket correspond to female pins.

[0039] The pins of the first connector 101 are indexed in such a way that each pin of the first connector has a unique index number between 1 and 16.

[0040] The cooperation of a pin of a connector (i.e. the first connector 101 or the second connector 102) with a pin of the socket (i.e. respectively the OBD socket or the 35-way socket) into which the connector is fitted means that the pins come into contact (e.g. the pins fit into each other) to establish an electrical contact and allow the transmission of the signal and the data carried by the signal.

[0041] According to a particular embodiment, the second connector 102 includes a keying feature configured to cooperate with a corresponding element of the 35-way pinout to correctly insert the second connector 102 into the 35-way socket. Similarly, a keying feature is, for example, provided in the first connector 101, which is configured to cooperate with a corresponding element of the OBD socket.

[0042] According to another embodiment, the first connector 101 and / or the second connector 102 include fastening elements for maintaining the first connector 101 and / or the second connector 102 fixed(s) to the OBD socket and / or the 35-way socket respectively when the adapter is connected to the vehicle 11 and the data recorder.

[0043] Figure [Fig.2] schematically illustrates the adapter 10, according to a particular and non-limiting embodiment of the present invention.

[0044] According to the example in [Fig.2], the cable 100 of the adapter 10 comprises 6 flexible conductors, namely: - a first flexible conductor 21 connecting a first pin of the first connector 101 having index number 16 to a first pin of the second connector 102 having index number 19; - a second flexible conductor 22 connecting a second pin of the first connector 101 having index number 4 to a second pin 102 of the second connector having index number 9; - a third flexible conductor 23 connecting a third pin of the first connector 101 having index number 6 to a third pin of the second connector 102 having index number 33; - a fourth flexible conductor 24 connecting a fourth pin of the first connector 101 having index number 14 to a fourth pin of the second connector 102 having index number 32; - a fifth flexible conductor 25 connecting a fifth pin of the first connector 101, having index number 3, to a fifth pin of the second connector 102, having index number 35; and - a sixth flexible conductor 26 connecting a sixth pin of the first connector 101 having index number 8 to a fifth pin of the second connector 102 having index number 34.

[0045] Such a configuration allows the data recorder to retrieve the data obtained from the OBD socket on the indexed pins 16, 4, 6, 14, 3 and 8 directly into the input of the 35-way socket of the data recorder on the expected channels for this data, i.e. on the channels associated with the indexed pins 19, 9, 33, 32, 35 and 34 respectively, when the adapter 10 is connected on the one hand to the OBD socket of the vehicle 11 via its first connector 101 and on the other hand to the 35-way socket of the data recorder 12 via its second connector 102.

[0046] This avoids having to convert the data as acquired by an OBD type diagnostic tool connected directly to the OBD port of the vehicle 11 in order to be able to use or save them in a specific format required for, for example, certain types of driving such as DSCDA for example.

[0047] The 6 flexible conductors 21 to 26 thus allow the signals or data received by pins 16, 4, 6, 14, 3 and 8 of the OBD socket of the vehicle 11 to be carried.

[0048] The first flexible conductor 21 is thus adapted to carry a signal representing the positive (+) terminal of the vehicle's battery (+) terminal. The second flexible conductor 22 is adapted to carry a signal representing the ground connected to the chassis of the vehicle's chassis. The third flexible conductor 23 is adapted to carry a signal from the first line of a first CAN-type data bus of the vehicle's chassis, the first line being CAN High. The fourth flexible conductor 24 is adapted to carry a signal from the second line of the vehicle's first CAN-type data bus, the second line being CAN Low. The fifth flexible conductor 25 is adapted to carry a signal from the first line of a second CAN-type data bus of the vehicle, the first line being CAN High, the second CAN data bus being different from the first CAN data bus.The sixth flexible conductor 26 is adapted to carry a signal from a second line of the vehicle's second CAN-type data bus, the second line being of the CAN Bas type.

[0049] As described in ISO 11519, data transmission is carried out on a differential wire pair on a CAN bus, namely on: - a first line identified as CAN L (CAN LOW); and - a second line identified as CAN H (CAN HIGH).

[0050] The voltage is different on each line for the dominant level and the recessive level of the signal carried.

[0051] According to alternative embodiments, the pin index numbers of the first connector 101 are not limited to index numbers 16, 4, 6, 14, 3, and 8, and the pin index numbers of the second connector 102 are not limited to index numbers 19, 9, 33, 32, 35, and 34, depending on the data to be recorded and the expected recording format. Similarly, the number of flexible conductors is not limited to 6, depending on the data to be recorded and / or the expected recording format.

Claims

Demands

1. Adapter (10) for vehicle OBD type diagnostic port (11), referred to as OBD port, said adapter comprising: - a cable (100) comprising a plurality of flexible conductors (21 to 26); - a first connector (101) arranged at a first end of said cable (100), said first connector (101) comprising a plurality of pins and being configured to cooperate with the vehicle's OBD port (11); and - a second connector (102) arranged at a second end of said cable (100), said second connector (102) comprising a plurality of pins and being configured to cooperate with a 35-way socket of a data logger (12).

2. Adapter (10) according to claim 1, wherein said first connector (101) comprises 16 pins, each pin of the first connector (101) having a unique index number from 1 to 16, said second connector (102) comprises 35 pins, each pin of the second connector (102) having a unique index number from 1 to 35, said plurality of flexible conductors (21 to 26) comprises: - a first flexible conductor (21) connecting a first pin of the first connector (101) having index number 16 to a first pin of the second connector (102) having index number 19; - a second flexible conductor (22) connecting a second pin of the first connector (101) having index number 4 to a second pin of the second connector (102) having index number 9; - a third flexible conductor (23) connecting a third pin of the first connector (101) having index number 6 to a third pin of the second connector (102) having index number 33; - a fourth flexible conductor (24) connecting a fourth pin of the first connector (101) having index number 14 to a fourth pin of the second connector (102) having index number 32; - a fifth flexible conductor (25) connecting a fifth pin of the first connector (101) having index number 3 to a fifth pin of the second connector (102) having index number 35; and - a sixth flexible conductor (26) connecting a sixth pin of the first connector (101) having index number 8 to a fifth pin of the second connector (102) having index number 34.

3. Adapter (10) according to claim 2, wherein: - the first flexible conductor (21) is adapted to carry a signal representing a positive battery terminal of the vehicle (11); - the second flexible conductor (22) is adapted to carry a signal representing a ground terminal connected to a chassis of the vehicle (11); - the third flexible conductor (23) is adapted to carry a signal from a first line of a first CAN-type vehicle data bus, said first line being of the CAN High type; - the fourth flexible conductor (24) is adapted to carry a signal from a second line of said first CAN-type vehicle data bus, said second line being of the CAN Low type; - the fifth flexible conductor (25) is adapted to carry a signal from a first line of a second CAN-type vehicle data bus, said first line being of the CAN High type;and - the sixth flexible conductor (26) is adapted to carry a signal from a second line of said second CAN-type vehicle data bus, said second line being of CAN Bas type.;

4. Adapter (10) according to any one of claims 1 to 3, wherein the pins of the plurality of pins of the first connector (101) correspond to male pins.

5. Adapter (10) according to any one of claims 1 to 4, wherein the pins of the plurality of pins of the second connector (102) correspond to female pins.

6. Adapter (10) according to any one of claims 1 to 5, wherein said second connector (102) includes a keying feature.

7. A system comprising a vehicle (11), a data logger (12), and an adapter (10) according to any one of claims 1 to 6, said adapter being connected to an OBD port of the vehicle via the first connector (101) of said adapter (10) and said adapter (10) being connected to a 35-way socket of said data recorder (12) via the second connector (102) of said adapter (10).

Images