DE102024111067A1 - Electronic interface device and method for providing a communication connection - Google Patents

Abstract

In summary, the present disclosure relates to an electronic interface device and a method for providing a communication connection between at least one control module, in particular a control module of a vehicle, and at least one user terminal, for diagnostics and/or programming parameters of the control module and/or other components, in particular components connected to the control module. The electronic interface device comprises a first communication interface, designed to establish a wired and/or wireless communication connection to the user terminal, and a second communication interface, designed to establish a wired communication connection to the control module, in particular using an on-board diagnostic port, OBD2, of the vehicle, and a modular control unit coupled to the first communication interface and the second communication interface. The control unit comprises a first circuit board with a processor unit and a second circuit board with a CAN transceiver unit and an energy converter unit, and the control unit is designed to provide the communication connection for diagnostics and/or programming.

Description

FIELD OF THE INVENTION

The present disclosure relates to an electronic interface device and/or a method for providing a communication connection between at least one control module, in particular a control module of a vehicle, and at least one user terminal, for diagnosing and/or programming parameters of the control module and/or other components, in particular components connected to the control module. Additionally or alternatively, a system for diagnosing and/or programming parameters of a control module of a vehicle and/or other components, in particular components connected to the control module, is provided. Additionally or alternatively, a computer program or an app is provided which comprise commands which, when the program or app is executed by a computer or a mobile device, cause the computer or mobile device to at least partially execute the method.

TECHNICAL BACKGROUND

Tools are generally known in the field of automotive engineering by means of which diagnostics and/or programming of vehicle parameters can be carried out.

Commonly known and available solutions often suffer from deficiencies in terms of compatibility and flexibility across different operating systems, end devices and vehicles, with current implementations of programming protocols being slow or incompatible across different platforms.

SUMMARY OF THE INVENTION

Against this background, the present invention is based on the object of providing an improved electronic interface device and/or a method.

The problem is solved by the subject matter of the independent claims. The subordinate claims and the dependent claims each contain optional developments of the disclosure.

The object is then achieved by an electronic interface device for providing a communication connection according to claim 1. The disclosed electronic interface device for providing a communication connection between at least one control module, in particular a control module of a vehicle, and at least one user terminal, for diagnosing and/or programming parameters of the control module and/or other components, in particular components connected to the control module, comprises a first communication interface. The first communication interface is designed to establish a wired and/or wireless communication connection to the user terminal.

The first communication interface is configurable to support a variety of connectivity options, including, but not limited to, wired connections such as USB and/or Ethernet and/or RS-232, as well as wireless connections such as Bluetooth and/or Wi-Fi and/or NFC. This configurability allows adaptation to specific user requirements and/or environments and/or connected peripherals by enabling either single or multiple communication modes simultaneously.

USB (Universal Serial Bus) can be used to transfer data and power between peripheral devices. Ethernet can be used to connect to a local area network (LAN). RS-232 enables serial data communication between the user terminal and the electronic interface device. Bluetooth can be used to transfer data over short distances between different peripheral devices. Bluetooth Low Energy (BLE) can also be provided. Wi-Fi enables wireless internet access and network connections over longer distances than Bluetooth. NFC can be used for very close range contactless data transfer between paired peripheral devices.

This can result in corresponding universality and accessibility for the primary communication interface. The ability to support both wired and wireless connections enables broad compatibility with a variety of user devices. This can be particularly useful in environments where different devices or transmission standards are used and facilitates integration into existing systems. Furthermore, this flexibility increases usability, as users can choose the most convenient or available connection method without being limited by technology.

Furthermore, the electronic interface device has a second communication interface. The second communication interface is Establishment of a wired communication connection to the control module, in particular using an on-board diagnostic port (OBD2) of the vehicle. The second communication interface is intended for establishing a wired connection to the vehicle and corresponding control modules. This interface primarily uses the vehicle's standardized on-board diagnostic port (OBD2) to enable direct and secure communication.

The OBD2 port, short for On-Board Diagnostics 2, is a standardized interface in vehicles that provides access to status information and diagnostic data from the vehicle's control and monitoring systems. The port serves as a central communication link to the vehicle's functions. The port can be located under the dashboard on the driver's side or in the center console and allows connection to diagnostic devices to read error codes, collect real-time data, and/or program certain vehicle functions.

The electronic interface device can be designed as a dongle, which is a compact device that plugs directly into the vehicle's OBD2 port. The second communication interface provides a wired communication connection via the plug-in function.

The dongle acts as a physical link between the vehicle and a diagnostic or monitoring system. Through a direct connection to the OBD2 port, the dongle can read and send data in real time, read and/or clear vehicle error codes, and adjust and/or update specific vehicle functions. Using a dongle offers high mobility and simplicity of use, as it is easy to install and remove without requiring extensive technical intervention and/or modifications.

The electronic interface device also has a modular control unit. The modular control unit is coupled to the first communication interface and the second communication interface. The control unit comprises a first circuit board with a processor unit and a second circuit board with a CAN transceiver unit and an energy converter unit. The control unit is configured to provide the communication connection for diagnostics and/or programming.

The control unit in the disclosed electronic interface device is the central element responsible for processing data and/or controlling communication processes between the user terminal and the vehicle's control module. The modularity of the control unit allows for adapting functionality and performance by adding, removing, or replacing specific modules, particularly circuit boards, as needed or to meet desired functions. This provides a flexible and expandable architecture that allows the control unit to be optimized for different use cases or technology upgrades.

The control unit consists of two separate but interconnected circuit boards. One board houses the processor unit, which is responsible for general data processing and control. The second board contains a CAN transceiver unit for vehicle communication and an energy converter unit for power supply. This physical separation allows for specialized development and optimization of each module for its specific tasks.

The connection between the printed circuit boards can be provided by standardized interfaces and/or connectors, facilitating the replacement and/or upgrade of the printed circuit boards. For example, the processor unit and the CAN transceiver unit can communicate with each other via defined interfaces that include both electrical connections and data transmission protocols. The connection between the printed circuit boards can be established via direct connectors, cables, or other conductive connections that support both power supply and data transmission between the modules.

The control unit can connect to user devices via the first communication interface and to the vehicle via the OBD2 port via the second interface. These interfaces enable the control unit to collect and process diagnostic data and send programming commands from both the user device and the vehicle control module.

The vehicle can be a passenger car, in particular a car, or a commercial vehicle, such as a truck. Other types of vehicles are not excluded by this exemplary list.

For the purposes of the present disclosure, a control module may be an electronic control unit (ECU). The electronic The control unit can be an intelligent processor-controlled unit that can communicate with other modules, for example, via a central gateway (CGW), and that can form the vehicle's on-board network via fieldbuses such as the CAN bus, LIN bus, MOST bus, FlexRay and/or via the automotive Ethernet, for example, together with telematics control units and/or environmental sensors.

It is conceivable that the control module controls functions relevant to the vehicle's driving behavior, such as the steering, engine control, transmission, anti-theft protection unit, and/or the braking system. Furthermore, driver assistance systems such as a parking assistant, adaptive cruise control (ACC), lane keeping assistant, lane change assistant, traffic sign recognition, traffic light recognition, start-off assistant, night vision assistant, and/or intersection assistant can be controlled by the control device.

Furthermore, for the purposes of this disclosure, components connected to the control module are understood to mean the devices and modules required for the proper functioning of the vehicle. These components are coupled to the control module and work together with the control module to exchange data, receive and execute commands, and monitor and control the various vehicle functions. The components may include various types of sensors installed throughout the vehicle to collect information about speed, rpm, temperature, pressure, fuel consumption, emissions, and other parameters. This data is provided to the control module for further processing to optimize driving behavior and/or inform the driver about the vehicle's condition. Furthermore, actuators may be provided as components that perform actions upon command from the control module, such as opening and closing valves, setting ignition timing, controlling fuel injection, and/or regulating air supply. Furthermore, additional control units may be provided that perform tasks for specific subsystems such as the transmission, brakes, air conditioning, infotainment system, and driver assistance systems. These communicate with the control module via the vehicle network (e.g., CAN bus). Furthermore, communication modules can be provided that enable connectivity functions such as GPS navigation, emergency call services (eCall), remote maintenance and diagnostics, as well as connection to the internet and mobile devices. Furthermore, the components include display and control elements, including the dashboard, touchscreens, switches, and other interfaces, which provide the driver with information about the vehicle's status and enable the input of control commands. Other components also include fuel system components, e.g., pumps, injectors, and filters, which are responsible for supplying and preparing fuel to the engine, and powertrain components, e.g., parts of the drive system, including the transmission, clutch, and drive shafts, which are responsible for transferring engine power to the wheels. Components of an electrically powered vehicle are not excluded. These components are an integral part of the vehicle system and interact with the control module to ensure the vehicle's performance, safety, and comfort. Furthermore, all data, parameters, and/or information from other components can be centrally retrieved for diagnostic purposes via the control module. It can also be provided to program parameters for other components.

The interface device described above offers several advantages. The electronic interface device offers high compatibility with vehicle-specific communication standards, particularly through the introduction of the ISO-TP standard, as well as versatile performance and functionality across multiple platforms using a robust control unit and a fully customized PCB design that combines all required technologies in a single device.

For the purposes of the present disclosure, a user terminal refers to an electronic device that can be used by a user to interact with the disclosed electronic interface device and thus with a vehicle. This interaction can occur via wired or wireless communication connections for the purpose of diagnosing, programming, monitoring, and/or controlling vehicle functions. User terminals serve as the interface between the user and the vehicle system by facilitating communication and providing access to vehicle data and controls.

The user terminal may comprise mobile devices, such as a smartphone or tablet, and connect to the electronic interface device via Bluetooth, Wi-Fi, and/or USB. They enable a wide range of functions, including running diagnostic procedures, displaying vehicle data in real time, programming vehicle settings, and/or updating vehicle software. Furthermore, laptops and/or desktop computers may be provided as user terminals. Connected via Bluetooth, USB and/or Wi-Fi, the user devices can run diagnostic software, perform comprehensive vehicle analyses, install software updates and perform complex programming tasks.

Furthermore, dedicated diagnostic devices can be provided as specialized handheld devices designed specifically for vehicle diagnostics. Wearables (e.g., smartwatches) can also be provided for simpler interactions, such as receiving notifications about the vehicle status or activating certain functions like vehicle locking. These user devices allow the user to access the vehicle system in an intuitive and efficient manner, expanding the possibilities for vehicle use and maintenance.

Possible further developments of the interface device described above are explained in detail below.

The first communication interface can be configured for multi-protocol communication and includes means for communication via USB, Bluetooth, Bluetooth Low Energy, and/or Wi-Fi. Multi-protocol communication allows data to be sent and/or received via various communication protocols and/or standards, both wired and wireless. This enables communication with a multitude of other devices and systems, regardless of the specific transmission protocols or interface technologies used. Suitable hardware, firmware, and drivers can be provided for this purpose. This enables interoperability and networking between devices, and seamless integration and communication across system boundaries.

Multi-protocol communication may include communication with user terminals from the IoT domain, and in particular, including user terminals with an operating system selected from the group consisting of Windows, iOS, MacOS-X, Android, and/or Unix. By supporting various communication protocols, the electronic interface device can communicate seamlessly with a wide variety of IoT devices and user terminals. This interoperability facilitates integration into existing networks without the need for specific adaptations. Explicit support for operating systems such as Windows, iOS, MacOS, Android, and Unix expands the range of devices with which the electronic interface device can interact. These operating systems cover a large proportion of computers, smartphones, tablets, and many specialized IoT devices available on the market. This ensures that virtually any device in the IoT network or any end-user device is capable of communicating with the interface device. Broad support for various operating systems and communication protocols increases the likelihood that users will be able to access diagnostic and/or programming functionality with their existing devices. This improves usability and accessibility by reducing the need for additional hardware or special adaptations.

The ability to communicate with devices running different operating systems allows developers to create applications and services that are consistent across multiple platforms. This translates to a simplified and improved experience for end users, who can expect the same features and a similar user interface on all their devices.

The multi-protocol communication may include communication with external sensors for monitoring the vehicle. Additional and/or supplementary sensors may be provided that can be coupled to the electronic interface device to acquire and provide additional sensor values from the vehicle and/or the vehicle's surroundings. These can be used for further diagnostics and/or programming.

The second communication interface can be configured as an OBD2 interface for connecting to the vehicle's on-board diagnostic port. The OBD2 interface serves as a hardware interface that enables the connection between the user terminal and the vehicle's on-board diagnostic port (OBD2). This standardized interface enables access to a wide range of vehicle data, including error codes, real-time performance information, and/or specific vehicle status indicators. The OBD2 interface can standardize the diagnostic process across different vehicle makes and models, facilitate fault detection and troubleshooting, and monitor and optimize vehicle performance. It also enables developers and third-party providers to create innovative applications and services based on vehicle data. By providing a direct access point to vehicle systems, the OBD2 interface increases maintenance efficiency and vehicle safety.

Furthermore, means for communication via the vehicle communication protocols and/or standards CAN ( ISO 11898-2), TP2.0, ISO-TP, ISO15765-2, J2534 and UDS. This supports interoperability with other device and software manufacturers.

The processor unit can be designed as a system-on-a-chip (SoC) unit and is configured to provide a microcontroller and/or flash memory. The system-on-a-chip (SoC) allows all the necessary electronic circuits and components of a system to be combined on a single, integrated chip. This allows space- and energy-efficient functions to be provided by integrating the components of an entire system into a single chip, whereby an SoC reduces the physical space required and energy consumption compared to systems that use separate components distributed across multiple chips. Furthermore, the SoC can be optimized for specific applications, which can lead to improved performance. The short connection paths on the chip reduce latency and increase data transfer speeds between components. Specific microcontrollers and memories, in particular flash memories, can be designed to enable efficient execution of functions and software.

The energy converter unit can be configured to provide a primary 5-volt supply voltage. The energy converter unit, which provides a 5-volt supply voltage, enables a standardized and efficient power supply for electronic components and systems operating at this voltage. Providing a specific voltage optimizes energy consumption, improving the energy efficiency of the electronic interface device. A stable and regulated supply voltage increases the safety and reliability of the electronic interface device by minimizing voltage fluctuations. Furthermore, the 5-volt design facilitates the integration and expansion of the electronic interface device with standard peripherals and external modules that have the same voltage requirements.

It can be provided that the control unit is configured to execute firmware comprising flashing and/or logging functionality. This allows for a seamless and comprehensive user experience. For this purpose, a software solution is provided that is specifically designed to program vehicle control units (flashing) and to acquire and record vehicle data (logging). This application aims to offer a consistent and intuitive user experience, regardless of the operating system or device on which it is executed. The firmware is flexible and widely applicable at both the hardware and software levels and represents a comprehensive solution for programming vehicle control units and acquiring vehicle data. Cross-platform compatibility is achieved, allowing users to use the software on various user devices such as smartphones, tablets, and computers running operating systems including Windows, MacOS-X, Linux, iOS, and Android. The application can have a user-friendly interface output via an output unit of the user device, which enables easy execution of flashing and logging functions. Real-time data visualization and analysis can be provided.

It may be provided that the firmware can be updated via an update service. The firmware update service can be implemented via the provision of OTA updates. A new firmware version can be delivered wirelessly to the electronic interface device via the internet and/or a local network. The electronic interface device receives and installs the update automatically or upon user confirmation, without requiring physical access. Furthermore, an update client can be integrated into the firmware of the electronic interface device, which communicates regularly or at predefined intervals with a central server (application server) to check for new firmware versions. When an update is available, the update client can download it and initiate the update process. Furthermore, it may be provided that users can manually search for updates and download and install them via an interface (e.g., a web interface or a mobile app). This requires a certain degree of user interaction but allows greater control over the update process.

The ability to update firmware via an update service improves both the security and functionality of the electronic interface device. Regular updates can close security gaps and strengthen protection against cyberattacks, which is crucial for the security of connected devices. At the same time, these updates enable the introduction of new features and improvements, thereby increasing the usability and value of the electronic interface. The reliability of the device can be increased over its lifetime. Errors and problems discovered after delivery can be effectively resolved, leading to increased customer satisfaction. Furthermore, firmware updates allow for rapid adaptation to technological changes and user feedback without the need for physical service visits, saving time and money and thus providing a cost-effective solution for both manufacturers and users.

It can be provided that the control unit is designed to read out and provide vehicle information comprising a configuration and/or a type of vehicle. Furthermore, the control unit is designed to provide corresponding diagnostic and/or programming functionalities based on the vehicle information. By reading out specific vehicle information, the control unit can optimize diagnostic processes and maintenance work. By reading out and recognizing the exact configuration and type of the vehicle, corresponding diagnostic tests and maintenance routines can be carried out that are specifically tailored to the respective vehicle model and its equipment. Furthermore, knowledge of the exact vehicle configuration and type enables the control unit to perform compatibility checks for accessories and spare parts. This can ensure that only compatible components are used, which can increase the safety and reliability of the vehicle. Reading out the vehicle type and/or configuration facilitates the provision of software updates that have been specifically developed for the vehicle model and its specific equipment. This ensures that the software is always optimally tailored to the vehicle.

The electronic interface device can be provided with a display unit for providing a status message from the electronic interface device. This can improve interaction with the electronic interface device. Using LED lights (e.g., RGB), different colors or flashing patterns can be provided to indicate different operating states, such as readiness, activation, error states, or successful completion of operations. This allows immediate feedback to be given to the user, who receives direct feedback on the operating status of the electronic interface device, making operation more intuitive and efficient. Displaying error codes or warning messages facilitates the identification and resolution of problems without the need for additional diagnostic tools. Coded instructions for the correct use of the electronic interface device can be provided via the display unit, which can facilitate operation. The display unit significantly improves the user experience with the electronic interface device by providing clear, understandable, and timely information about the status and functionality of the electronic interface device.

The electronic interface device may be provided with a data integrity mechanism. The data integrity mechanism includes CRC, encryption, and/or compression. The data integrity mechanism can be used to ensure that data is not altered, corrupted, or tampered with in an unauthorized manner during transmission, storage, and/or processing. Data correctness and completeness can be ensured by verifying that the data remains unchanged from its origin to its destination. Data integrity mechanisms can contribute to increased security and efficiency through the use of techniques such as the cyclic redundancy check (CRC) for error detection, encryption to protect against unauthorized access, and compression to increase efficiency.

The CRC can be used to verify the integrity of transmitted data by calculating a special CRC value from the data and comparing it with a received or previously stored CRC value. This can be implemented either in hardware using dedicated CRC modules or in software using appropriate algorithms. Furthermore, the data can be encrypted before transmission or storage to protect the confidentiality and integrity of the information. Symmetric encryption methods up to more complex asymmetric cryptosystems can be implemented. Data compression can be used to reduce the size of the data to be transmitted or stored. This can be achieved using a variety of algorithms that aim either for losslessness or for an optimal balance between compression rate and quality. Compression mechanisms can be implemented in software or supported by specialized hardware.

So far, the disclosure has been described with respect to the claimed electronic interface device. Features, advantages, or alternative embodiments may be assigned to the other claimed objects (e.g., the system, the method, or a computer program product) and vice versa. In other words, the subject matter claimed or described with respect to the electronic interface device can be improved by features described or claimed in the method or system, and vice versa.

According to a further aspect, the disclosure provides a system for diagnosing and/or programming parameters of a control module of a vehicle and/or other components, in particular components connected to the control module.

The system comprises at least one user terminal for providing diagnostic and/or programming functionalities for diagnosing and/or programming parameters of the vehicle's control module and/or other components. This allows a user to interact with the vehicle.

Furthermore, the system comprises the disclosed electronic interface device for providing a communication connection between the user terminal and the control module of the vehicle for diagnostics and/or programming.

According to a further aspect, the disclosure provides a method for providing a communication connection with the disclosed electronic interface device between at least one control module, in particular a control module of a vehicle, and at least one user terminal, for programming and/or monitoring parameters of the control module and/or other components, in particular components connected to the control module. The method comprises several method steps. In a first method step, a wired and/or wireless communication connection is established to the user terminal via the first communication interface of the electronic interface device. In a further method step, a wired communication connection is established to the control module, in particular using an on-board diagnostic port, OBD2, of the vehicle via the second communication interface of the electronic interface device. In a further method step, the communication connection for diagnostics and/or programming is provided.

The disclosure further provides a computer program with program code for carrying out the disclosed method when the computer program is executed on an electronic device. The computer program can be provided as a signal via download or stored in a memory unit of a portable device with computer-readable program code contained therein to cause a system to execute instructions according to the above-mentioned method.

The above embodiments and further developments can be combined with one another as desired, where appropriate. Further possible embodiments, further developments, and implementations of the disclosure also include combinations of features of the disclosure described above or below with respect to the exemplary embodiments that are not explicitly mentioned. In particular, those skilled in the art will also add individual aspects as improvements or additions to the respective basic form of the present disclosure.

The above description can be summarized in other words and in a possible more concrete embodiment of the disclosure as described below, whereby the following description is not to be interpreted as limiting the disclosure.

The electronic interface device (Gt-Flasher OBDII interface) is designed for compatibility with the ISO-TP (ISO15765-2) standard. Equipped with USB, BLE (Bluetooth Low Energy), and Wi-Fi capabilities, this interface offers outstanding performance on Windows, Android, and iOS platforms. The firmware version offers robust USB and BLE flashing functionality, tailored for 12-volt vehicles, and features a low-power ESP32 microcontroller for efficiency and sustainability.

The electronic interface device is designed to allow easy connection to the widely used OBDII diagnostic port in all vehicles, thus providing a crucial communication link for diagnostic and programming functions. A flashing and logging application called Gt-Flasher and Data Logger is provided as part of the electronic interface device to ensure a seamless and comprehensive user experience across multiple platforms. Additionally, a state-of-the-art application is provided that enables global dealers to quickly deliver products via Android and iOS phones and tablets, as well as Microsoft Windows computers.

The electronic interface device introduces compatibility with the ISO-TP standard and offers versatile performance on multiple platforms using a robust ESP32 SoC microcontroller and a fully custom PCB design that incorporates all the required technology logies in a single device. The interface device also features a unique design that allows for easy connection to the ubiquitous OBDII diagnostic port, thus providing a crucial communication link for diagnostic and programming tasks via USB, Wi-Fi, or BLE.

By merging the wired and wireless communication capabilities of the electronic interface device with current automotive communication standards such as UDS, J2534, ISO15765-2, and CAN (ISO 11898-2), the need for separate interfaces for tasks such as programming or monitoring a vehicle is eliminated. In addition to the hardware innovation, a dedicated GT-Flasher application is provided to provide a seamless and comprehensive user experience.

Accessing, downloading, and installing the interface device application and automatically obtaining a unique application license are critical steps to effectively utilize the integrated system on Microsoft Windows platforms.

To further increase the reach and convenience of product delivery, Android and iOS applications have been introduced. These enable dealers to deliver corresponding software products to end users worldwide using phones and tablets. This is done using a cloud system and a portal that is automatically configured to provide solutions based on the end user's needs by identifying the vehicle type and engine management system.

The interface device (Gt-Flasher OBD2 (SAE J1962) interface) is capable of monitoring and programming any CAN-BUS (ISO 11898-2)-based control module in a CAN (Controller Area Network)-equipped vehicle. Furthermore, the device can forward CAN messages from external sensors via BLE, Wi-Fi, or directly wired sensors to the input connector assigned to the OBD2 connector. The interface device can be connected to any Windows, Android, or iOS device via USB, Wi-Fi, Bluetooth, or Bluetooth Low Energy (BLE). The Gt-Flasher firmware supports online updates for expanding or further improving features. The interface device also offers compatibility with other software vendors that use CAN, ISO-TP (ISO 15765-2) variants, and layers over this protocol.

The electronic interface device offers a compact, lightweight OBD2 interface (45 mm x 23 mm x 81 mm), features low power consumption with industry-standard electronic components, and includes multiple communication protocols (USB, BLE, WIFI) and several vehicle-specific communication protocols (CAN, TP2.0, ISO-TP, 15015765, UDS). CAN relay functions can be provided using external input. Wireless firmware updates (over-the-air, OTA) are provided. The electronic interface device features an RGB LED for status indication. The electronic interface device features fast programming capabilities for various vehicle control units via CAN. CRC, encryption, and compression can be provided for CAN communication. The electronic interface device is IoT-capable based on WIFI communication.

The electronic interface device is an OBD2 (also known as OBDII/SAE J1962) interface device that communicates with various engine and transmission control modules or other subsystems via CAN BUS (ISO 11898-2), J2534, and ISO 15765 protocols. These communication protocols enable this device to reprogram the control modules or monitor sensor values and variables. The user can connect to this device via wired or wireless protocols such as USB, BLE, or Wi-Fi with a Windows computer, Android, or iOS device.

The electronic hardware of the electronic interface device consists of two circuit boards that merge seamlessly into a single unit. The ESP32 Wroom32D PCB (2 layers) is a versatile system-on-chip (SoC) developed by Espressif Systems. This SoC is widely used in embedded systems, IoT (Internet of Things), and various electronic projects. It features a dual-core Xtensa LX6 microcontroller, which offers high computing power and typically has 4 MB of flash memory for program storage. The chip offers a variety of GPIO pins, analog-to-digital converter (ADC) pins, and interfaces such as SPI, I2C, I2S, and UART for connecting a wide range of peripherals. The native ESP IDF 4.4 can be used as the development environment for the firmware used, and can later be migrated to ESP IDF 5.1.2. The second circuit board (2 layers) can accommodate the CAN transceiver and DC-DC converter as well as various supporting components.

PCB2 can be provided as a breakout board, connecting to PCB1 at the bottom to complete the circuit board that integrates the electronic interface device into a functional unit. It contains the MCP2551 CAN transceiver, which enables communication with a CAN-based network. To provide the required voltage for the system, a DC-DC converter is used for the primary 5-volt supply. The circuit board also contains an RGB LED that indicates the connection status of the electronic interface device to inform the user of various operating conditions. The male SAE J1962 OBD2 adapter is directly connected to the circuit board to enable connection to the vehicle's female OBD2 port. By attaching an OBD2 connector to the side of the unified circuit board, the internal structure of the device is completed. The surface of the circuit board is lead-free and complies with HASL guidelines.

The housing is made of PLA and splits into two parts to securely house the unified circuit board without the use of any screws, and features a cutout for the USB port. The micro-USB port is used for direct computer connection or firmware updates. All functions are available via USB, BLE, and Wi-Fi. The housing has a cutout on the front for the power LED to indicate the status of the electronic interface device and the connection.

Using the electronic interface device, the user can access, control, or monitor any module connected to the vehicle via CAN. The user can diagnose faults through sensor monitoring or request and clear actual trouble codes. The user can program the firmware of any implemented control module. The user can connect wirelessly or via USB using Windows, Android, or iOS. The user can also perform firmware updates via Windows. The user can capture sensor readings and save them to a cloud-based system. The user can retrieve information such as VIN, flash counters, and software versions from the connected control modules.

The electronic interface device's workflow is simple and user-friendly. Users can create an account in a web-based application or a portable application and use it to log in to the application on their user devices (smartphones). For Windows platforms, users can download the application and USB drivers after creating an account and then log in using their previously specified data (e.g., credentials). After the program installation is complete and the user has successfully logged in to their account, the next step is to connect the electronic interface device (the Gt-Flasher OBD2 dongle) to the corresponding OBD port in the vehicle. This connection can be established using three different protocols (USB, BLE, WIFI) via a computer or mobile device.

After a successful connection, the application controlling the electronic interface (firmware) starts an automatic scan to identify the vehicle type and the type of control units present in the vehicle, particularly the engine and transmission management systems. This is necessary for identifying and configuring the correct communication protocol. Once the protocol is recognized, the user is prompted to identify the vehicle to access the available options.

Now, the available functions become accessible to the user, including reading and clearing trouble codes, monitoring vehicle sensors, resetting flash counters, switching to various calibrations, and programming and resetting control modules. The majority of functions are conveniently accessible with just 3-4 touches, and all available options are automatically configured for the user by the server. This ensures that they are immediately available upon request and optimizes the user experience.

1. 1. Elektronische Schnittstellen scannen und verbinden
2. 2. Signalstärke von Elektronische Schnittstellen anzeigen
3. 3. Verbindungseinstellungen anpassen
4. 4. Manuelle oder automatische Auswahl des Protokolls für Modulkommunikation
5. 5. Elektronische Schnittstellen abfragen und konfigurieren
6. 6. Fahrzeugsteuermodule identifizieren
7. 7. Fahrzeugsteuermodule neu programmieren
8. 8. Fehlercodes anzeigen und löschen
9. 9. Sensordaten überwachen und aufzeichnen
10. 10. Motor-Kalibrierungen wechseln/austauschen
11. 11. Motorbetriebsfunktionen aktivieren und deaktivieren
12. 12. Flash-Zähler zurücksetzen
13. 13. Firmware von Elektronische Schnittstellen aktualisieren
14. 14. Benutzerkonto konfigurieren und löschen
15. 15. Monitoring des Datenverkehrs vom CAN-Netzwerk

The following options are available to users after successful setup:

1. 1. Scan and connect electronic interfaces
2. 2. Display signal strength of electronic interfaces
3. 3. Adjust connection settings
4. 4. Manual or automatic selection of the protocol for module communication
5. 5. Query and configure electronic interfaces
6. 6. Identify vehicle control modules
7. 7. Reprogram vehicle control modules
8. 8. Display and delete error codes
9. 9. Monitor and record sensor data
10. 10. Change/replace motor calibrations
11. 11. Activate and deactivate engine operating functions
12. 12. Reset flash counter
13. 13. Update firmware of electronic interfaces
14. 14. Configure and delete user account
15. 15. Monitoring data traffic from the CAN network

The programming function (Function 7) is the most sophisticated, yet user-friendly function. This function seamlessly integrates various technologies to enable a comprehensive control module reprogramming process and represents the central delivery method of the electronic interface.

Throughout the entire reprogramming process, the electronic interface serves as a bridge that unites and consolidates various technologies and communication protocols. The encryption and compression algorithms work hand in hand, ensuring a secure and efficient transition from a CAN-BUS-based system to a cloud-based server.

• Connectivity: Micro USB / BLE / WIFI
• Operation CPU Speed: 160-240MHz
• Wireless operating frequency: 2.4 GHZ (-12 ~ 9 dBm)
• Max. Frequency: 2.484 GHz
• Max. data rate: 150 Mbps
• Bandwith: 72 Mhz
• Operating voltage: 12V (OBD) / 5V (Micro-USB connector) 600mA
• Enclosure Material: PLA
• Min-Max operating temperature: -40 °C bis 85 °C

The electronic interface device may have the following characteristics:

• Connectivity: Micro USB / BLE / WIFI
• Operation CPU Speed: 160-240MHz
• Wireless operating frequency: 2.4GHZ (-12~9dBm)
• Max. Frequency: 2.484 GHz
• Max. data rate: 150 Mbps
• Bandwidth: 72 MHz
• Operating voltage: 12V (OBD) / 5V (Micro USB connector) 600mA
• Enclosure material: PLA
• Min-Max operating temperature: -40°C to 85°C

• RF certification: FCC/CE-RED/IC/TELEC/KCC/SRRC/NCC
• Wi-Fi certification: Wi-Fi Alliance
• Bluetooth certification: BQB
• Green certification: RoHS/REACH
• Reliability: HTOL/HTSL/uHAST/TCT/ESD

The ESP32 Module Certification can include:

• RF certification: FCC/CE-RED/IC/TELEC/KCC/SRRC/NCC
• Wi-Fi certification: Wi-Fi Alliance
• Bluetooth certification: BQB
• Green certification: RoHS/REACH
• Reliability: HTOL/HTSL/uHAST/TCT/ESD

The above embodiments and further developments can be combined with one another as desired, where appropriate. Further possible embodiments, further developments, and implementations of the invention also include combinations of features of the invention not explicitly mentioned above or described below with regard to the exemplary embodiments. In particular, those skilled in the art will also add individual aspects as improvements or additions to the respective basic form of the present invention.

TABLE OF CONTENTS OF THE DRAWING

• 1 ein Blockdiagramm zur Darstellung einer Ausführungsform einer elektronischen Schnittstellenvorrichtung;
• 2 ein Ablaufdiagramm zur Darstellung eines Ausführungsbeispiels eines offenbarungsgemäßen Verfahrens;
• 3 ein Blockdiagramm zur Darstellung einer Ausführungsform des offenbarungsgemäßen Systems, und
• 4 ein Blockdiagramm zur Darstellung eines Ausführungsbeispiels zur Verwendung der offenbarungsgemäßen elektronischen Schnittstellenvorrichtung.

The present invention will be explained in more detail below with reference to the exemplary embodiments shown in the schematic figures of the drawings. In the drawings:

• 1 a block diagram illustrating an embodiment of an electronic interface device;
• 2 a flowchart illustrating an embodiment of a method according to the disclosure;
• 3 a block diagram illustrating an embodiment of the system according to the disclosure, and
• 4 a block diagram illustrating an embodiment for using the electronic interface device according to the disclosure.

The accompanying drawings are intended to provide a further understanding of embodiments of the invention. They illustrate embodiments and, in conjunction with the description, serve to explain principles and concepts of the invention. Other embodiments and many of the noted advantages will be apparent upon review of the drawings. Elements of the drawings are not necessarily shown to scale relative to one another.

In the figures of the drawing, identical, functionally identical and acting elements, features and components are provided with the same reference symbols, unless otherwise stated.

DESCRIPTION OF EMBODIMENTS

1 shows a block diagram illustrating an embodiment of an electronic interface device. 1 The schematically illustrated interface device 1 is for Providing a communication connection 2', 2" between at least one control module 3, in particular a control module 3 of a vehicle 4 and at least one user terminal 5, for diagnostics and/or programming of parameters of the control module 3 and/or further components 15, in particular components 15 connected to the control module 3.

The electronic interface device 1 has a first communication interface 6. The first communication interface 6 is designed to establish a wired and/or wireless communication connection 2' to the user terminal 5. The first communication interface 6 is designed for multi-protocol communication and includes means for communication via USB, Bluetooth, Bluetooth Low Energy, and/or Wi-Fi.

In addition, the electronic interface device 1 has a second communication interface 7. The second communication interface 7 is designed to establish a wired communication connection 2'' to the control module 3, in particular using an on-board diagnostic port, OBD2, of the vehicle 4. The second communication interface 7 is designed as an ODB2 interface for connecting to the on-board diagnostic port of the vehicle 4. The second communication interface 7 provides means for communication via the vehicle communication protocols and/or standards CAN (ISO 11898-2), TP2.0, ISO-TP, ISO15765-2, J2534, and UDS.

Furthermore, the electronic interface device 1 has a modular control unit 8. The modular control unit 8 is coupled to the first communication interface 6 and the second communication interface 7. The control unit 8 comprises a first circuit board 9 with a processor unit 11 and a second circuit board 10 with a CAN transceiver unit 12 and an energy converter unit 13. The control unit 8 is designed to provide the communication connection 2', 2" for diagnostics and/or programming. The processor unit 11 is designed as a system-on-a-chip (SoC) unit. The processor unit 11 is designed to provide a microcontroller and/or a flash memory. The energy converter unit 13 is designed to provide a primary 5-volt supply voltage. Firmware comprising flashing and/or logging functionality can be executed by means of the control unit 8. The firmware can be updated via an update service.

The control unit 8 is further configured to read and provide vehicle information, in particular vehicle information of the vehicle 4 comprising a configuration and/or a type of the vehicle 4. Furthermore, the control unit 8 is configured to provide corresponding diagnostic and/or programming functionalities based on the vehicle information.

The vehicle 4 can be configured as a motor vehicle. The motor vehicle can include the control module 3 or a plurality of control modules 3. The control module 3 of the motor vehicle can be configured as a control unit and can communicate with a plurality of other components 15 of the motor vehicle. Information can be provided by the components 15 of the motor vehicle via a communication medium, e.g., a CAN network, via the control unit.

The user device 5 can be configured as an IoT device. The user device can be configured as a smartphone, tablet, computer, or as a device for diagnosing and/or programming parameters of a control module 3 of a vehicle 4 and/or other components 5.

The electronic interface device 1 has a data integrity mechanism. The data integrity mechanism may include CRC, encryption, and/or compression.

The electronic interface device 1 is also for carrying out the process related to 2 schematically illustrated method 200. 2 shows the flowchart of the disclosed method 200 for providing a communication connection 2', 2" with an electronic interface device 1 between at least the control module 3, in particular the control module 3 of the vehicle 4, and at least the user terminal 5, for programming and/or monitoring parameters of the control module 3 and/or further components 15, in particular components 15 connected to the control module 3.

In the illustrated embodiment, the method 200 comprises several steps. In a first step 210, the wired and/or wireless communication connection 2' to the user terminal 5 is established via the first communication interface 6 of the electronic interface device 1. In a further step 220 of the method 200, the wired communication connection 2" to the control module 3 is established, in particular using an on-board diagnostic port, OBD2, of the vehicle 4 via the second communication interface 7 of the electronic interface device 1. In a further step 230, the communication connection 2', 2" is provided for diagnostics and/or programming. After the communication connection 2', 2" has been provided, the firmware can be executed, comprising a flashing and/or logging functionality. Vehicle information, comprising a configuration and/or a type of the vehicle 4, can be read out and provided. Based on the vehicle information, corresponding diagnostic and/or programming functionalities are provided. These are provided on the user terminal 5 to the user of the user terminal 5.

3 shows a block diagram illustrating a possible embodiment of a system 100 with the disclosed electronic interface device 1. The system 100 can be used to carry out the method 200, which is also described in detail with reference to FIG. 2. The system 100 is designed for diagnosing and/or programming parameters of a control module 3 of the vehicle 4 and/or other components 5, in particular components (5) connected to the control module.

The system 100 comprises the user terminal 5 for providing diagnostic and/or programming functionalities for diagnosing and/or programming parameters of the control module of the vehicle 4 and/or other components 15 of the vehicle 4. The electronic interface device 1 is provided for providing the communication connection between the user terminal 5 and the control module of the vehicle 4 for diagnostic and/or programming.

In the illustrated embodiment of the system 100, the electronic interface device 1 has a display unit 14. A status message of the electronic interface device 1 can be provided via the display unit 14. The display unit 14 can be embodied as an RGB LED display. Various status information can be provided to the user via the RGB LED display using different colors and/or flashing signals.

The electronic interface device 1 can communicate with external sensors for monitoring the vehicle 4 using multi-protocol communication. The sensor values can be used for further analysis and/or adjustment of the vehicle 1.

4 shows a block diagram illustrating an embodiment for using the disclosed electronic interface device 1. A user can connect the electronic interface device 1 to the vehicle 4 via the ODB port of the vehicle 4. This establishes the wired communication connection 2 to the vehicle 4 and the control module 3 of the vehicle 4 and/or other components 15 of the vehicle 4. Communication takes place via the vehicle communication protocols and/or standards CAN (ISO 11898-2), TP2.0, ISO-TP, ISO15765-2, J2534, and UDS.

Furthermore, the communication connection 2' to the user terminal 5 is established via the first communication interface 6 of the electronic interface device 1. The communication connection 2' can be established using various protocols, including USB, BLE, and/or Wi-Fi. The user terminal 5 is a device from the IoT field, comprising user terminals 5 with an operating system selected from the group consisting of Windows, iOS, MacOS-X, Android, and/or Unix. Smartphones, tablets, laptops, smartwatches, and/or special diagnostic devices can be provided.

A variety of applications can be installed on the user terminal 5. The application (app) can contain functions 16 that can be selected and/or executed by a user. Using the functions 16, the communication connection 2', 2" can be established and diagnostics and/or programming can be performed.

To do so, the user can connect to a corresponding application server 17 via an internet connection 18 using the user terminal 5. From the application server, the user can load the corresponding application using the function 16. To do so, the user can create and log in to a user account in the application or in a service running on the application server. This user account can be used to provide the application, provide new versions, offer services, and/or perform updates.

After connecting the electronic interface device 1 to the ODPB2 port of the vehicle 4 and the user terminal 5, the application can be executed on the user device 5. The functions 16, which control the electronic interface controller 1, can be selected via the application installed on the user terminal 5. After connecting the electronic interface controller 1, an automatic scan can be performed. The automatic scan can be used to determine the type of control modules 3 installed in the vehicle 4 and to identify them. For example, the engine and transmission management system can be read and identified. This allows the correct communication protocol to be selected and configured. After setting the correct protocol, the user can be automatically prompted to identify the vehicle 4 in order to then access the options available for the vehicle 4.

The available functions 16 are provided to the user via an output unit of the user terminal 5. These functions may include reading and clearing error codes, monitoring components 15, e.g., sensors, on the vehicle 1, resetting flash counters, switching to various calibrations, and programming and resetting control modules 3.

The 16 functions can be selected and executed with just a few gestures, for example, via a smartphone or tablet display. The functions and their options are configured and provided by the application server via the user account.

• - die elektronische Schnittstellenvorrichtung 1 scannen und verbinden,
• - Signalstärke der elektronischen Schnittstellenvorrichtung 1 anzeigen
• - Verbindungseinstellungen der elektronischen Schnittstellenvorrichtung 1 anpassen,
• - manuelle Auswahl des Protokolls für die Modulkommunikation,
• - elektronische Schnittstellenvorrichtung 1 abfragen und konfigurieren,
• - Steuermodule 3 des Fahrzeugs 4 identifizieren,
• - Steuermodule 3 des Fahrzeugs 4 neu programmieren,
• - Fehlercodes anzeigen und löschen,
• - Sensordaten überwachen und aufzeichnen,
• - Motor-Kalibrierungen wechseln/austauschen,
• - Motorbetriebsfunktionen aktivieren und deaktivieren,
• - Flash-Zähler zurücksetzen,
• - Firmware der elektronischen Schnittstellenvorrichtung 1 aktualisieren, und/oder
• - Benutzerkonto konfigurieren und löschen

The functions 16 for operating and using the electronic interface device 1 may include:

• - scan and connect the electronic interface device 1,
• - Display signal strength of electronic interface device 1
• - Adjust the connection settings of the electronic interface device 1,
• - manual selection of the protocol for module communication,
• - query and configure electronic interface device 1,
• - Identify control modules 3 of vehicle 4,
• - Reprogram control modules 3 of vehicle 4,
• - Display and delete error codes,
• - Monitor and record sensor data,
• - Change/replace engine calibrations,
• - Activate and deactivate engine operating functions,
• - Reset flash counter,
• - Update the firmware of the electronic interface device 1, and/or
• - Configure and delete user account

While executing functions 16, the electronic interface device 1 serves as an interface that combines and consolidates various technologies and communication protocols. The encryption and compression algorithms work together to ensure a secure and efficient transition from a CAN bus-based system to a cloud-based server.

The electronic interface device 1 allows the user to access, control, or monitor each control module 3 connected to the vehicle 4 via CAN. Furthermore, access to the other components 15 connected to the control module 3 is also possible. The user can diagnose faults by monitoring sensors or request and clear actual error codes. The user can program the firmware of each implemented control module 3. The user can connect wirelessly or via USB to Windows, Android, or iOS. The user can perform an update service via Windows. The user can record sensor values and save them in a cloud-based system. The user can retrieve information such as VIN, flash counter, and software versions from the connected control modules 3.

Although the present invention has been fully described above using preferred embodiments, it is not limited thereto but can be modified in many ways.

List of reference symbols

1

Interface device

2'

Communication connection

2"

Communication connection

3

Control module

4

vehicle

5

User terminal

6

first communication interface

7

second communication interface

8

Control unit

9

first circuit board

10

second circuit board

11

Processor unit

12

CAN transceiver unit

13

Energy converter unit

14

Display unit

15

Components

16

Functions

17

Application server

18

Internet connection

100

system

200

Proceedings

210-230

Procedural steps

QUOTES CONTAINED IN THE DESCRIPTION

This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• ISO 11898-2), TP2.0, ISO-TP, ISO15765-2, J2534 [0033]

Claims (15)

Electronic interface device (1) for providing a communication connection (2', 2") between at least one control module (3), in particular a control module (3) of a vehicle (4), and at least one user terminal (5), for diagnosing and/or programming parameters of the control module (3) and/or further components (15), in particular components (15) connected to the control module (3), comprising: a first communication interface (6) configured to establish a wired and/or wireless communication connection (2') to the user terminal (5); a second communication interface (7) configured to establish a wired communication connection (2") to the control module (3), in particular using an on-board diagnostic port, OBD2, of the vehicle (4); and a modular control unit (8) coupled to the first communication interface (6) and the second communication interface (7), wherein the control unit (8) comprises a first circuit board (9) with a processor unit (11) and a second circuit board (10) with a CAN transceiver unit (12) and an energy converter unit (13), and wherein the control unit (8) is designed to provide the communication connection (2', 2") for diagnostics and/or programming. Interface device according to Claim 1 , wherein the first communication interface (6) is designed for multi-protocol communication and comprises means for communication via USB, Bluetooth, Bluetooth Low Energy and/or WiFi. Interface device according to Claim 2 , wherein the multi-protocol communication includes communication with user terminals (5) from the IoT field, and in particular comprising user terminals (5) with an operating system selected from the group comprising Windows, iOS, macOS-X, Android and/or Unix. Interface device according to at least one of the Claims 2 and 3 , wherein the multi-protocol communication includes communication with external sensors for monitoring the vehicle (4). Interface device according to at least one of the preceding claims, wherein the second communication interface (7) is designed as an ODB2 interface for connecting to the on-board diagnostic port of the vehicle (4) and provides means for communication via the vehicle communication protocols and/or standards CAN (ISO 11898-2), TP2.0, ISO-TP, ISO15765-2, J2534 and UDS. Interface device according to at least one of the preceding claims, wherein the processor unit (11) is designed as a system-on-a-chip, SoC, unit and is designed to provide a microcontroller and/or a flash memory. Interface device according to at least one of the preceding claims, wherein the energy converter unit (13) is designed to provide a primary 5-volt supply voltage. Interface device according to at least one of the preceding claims, wherein the control unit (8) is designed to execute a firmware comprising a flashing and/or logging functionality. Interface device according to at least one of the preceding claims, wherein the firmware is updatable via an update service. Interface device according to at least one of the preceding claims, wherein the control unit (8) is designed to read out and provide vehicle information comprising a configuration and/or a type of the vehicle (4), and is further designed to provide corresponding diagnostic and/or programming functionalities based on the vehicle information. Interface device according to at least one of the preceding claims, wherein the electronic interface device (1) has a display unit (14) for providing a status message of the electronic interface device (1). Interface device according to at least one of the preceding claims, wherein the electronic interface device (1) has a data integrity mechanism comprising CRC, encryption and/or compression. System (100) for diagnosing and/or programming parameters of a control module (3) of a vehicle (4) and/or other components (5), in particular components (5) connected to the control module (3), comprising: at least one user terminal (5) for providing diagnostic and/or programming functionalities for diagnosing and/or programming parameters of the control module of the vehicle (4) and/or other components, and an electronic interface device (1) according to at least one of the preceding claims, for providing a communication connection between the user terminal (5) and the control module of the vehicle (4) for diagnostics and/or programming. Method (200) for providing a communication connection (2', 2") with an electronic interface device (1) according to at least one of the preceding device claims between at least one control module (3), in particular a control module (3) of a vehicle (4), and at least one user terminal (5), for programming and/or monitoring parameters of the control module (3) and/or further components (15), in particular components (15) connected to the control module (3), comprising: establishing (210) a wired and/or wireless communication connection (2') to the user terminal (5) via the first communication interface (6) of the electronic interface device (1); establishing (220) a wired communication connection (2") to the control module (3), in particular using an on-board diagnostic port, OBD2, of the vehicle (4) via the second communication interface (7) of the electronic interface device (1), and providing (230) the communication connection (2', 2") for diagnostics and/or programming. Computer program, wherein the computer program comprises instructions which, when executed by a computer, cause the computer to carry out the method according to the disclosure.