An industrial vehicle commissioning tool

Abstract

The utility model discloses an industrial vehicle debugging tool, include: control unit, at least two communication interfaces, at least one wired communication module, at least two wireless communication modules, power management module and battery, control unit is connected with communication interface, wired communication module, wireless communication module, power management module electricity respectively, battery and power management module electricity are connected, communication interface configuration is used for with vehicle controller communication connection, wired communication module configuration is used for with host computer wired communication connection, and wireless communication module configuration is used for with host computer or mobile terminal wireless communication connection, control unit configuration is realized the data transmission between vehicle controller and host computer, mobile terminal.

Description

Technical Field

[0001] This utility model relates to the field of telecommunications technology, and in particular to an industrial vehicle debugging tool. Background Technology

[0002] During the production, commissioning, operation, and maintenance of industrial vehicles (such as forklifts and construction machinery), specialized tools are required to interact with the vehicle controller to achieve functions such as parameter configuration, status monitoring, and fault diagnosis. Traditional commissioning tools have the following drawbacks: they only have wired communication interfaces, limiting operating space and making them inconvenient to use; they can only be used via PC and cannot communicate with mobile devices such as smartphones and tablets; they are generally separate tools, either CAN to USB or RS232 to USB, which cannot be adapted to diverse vehicle systems. Utility Model Content

[0003] This utility model provides an industrial vehicle debugging tool to address at least one defect in the prior art.

[0004] This utility model provides an industrial vehicle debugging tool, including: a control unit, at least two communication interfaces, at least one wired communication module, at least two wireless communication modules, a power management module, and a battery;

[0005] The control unit is electrically connected to the communication interface, the wired communication module, the wireless communication module, and the power management module, respectively, and the battery is electrically connected to the power management module.

[0006] The communication interface is configured for communication connection with the vehicle controller, the wired communication module is configured for wired communication connection with the host computer, and the wireless communication module is configured for wireless communication connection with the host computer or mobile terminal.

[0007] The control unit is configured for data transmission between the vehicle controller and the host computer and mobile terminal.

[0008] Optionally, the wireless communication module includes a WIFI module, which is configured with a wireless access point function and is used to wirelessly connect with the host computer.

[0009] Optionally, the wireless communication module includes a Bluetooth module, which is used to wirelessly connect with the mobile terminal.

[0010] Optionally, the communication interface includes an RS232 interface and a CAN interface.

[0011] Optionally, the wired communication module includes a USB module.

[0012] Optionally, it may also include a storage unit electrically connected to the control unit, the storage unit being configured to store firmware.

[0013] Optionally, an LED indicator light is also included, which is electrically connected to the control unit and is configured to provide interactive indication for industrial vehicle debugging tools.

[0014] Optionally, it also includes buttons, which are electrically connected to the control unit and configured for human-machine interaction of industrial vehicle debugging tools.

[0015] Optionally, the battery is a rechargeable lithium battery.

[0016] Optionally, the control unit is configured to process the data received by the communication interface in parallel and to transmit the data transparently.

[0017] Compared with the prior art, the beneficial effects of this utility model are as follows: This utility model proposes a debugging tool that integrates multiple communication interfaces, wired and wireless communication modules. Based on multiple types of interfaces, it can be adapted to industrial vehicle controllers of different brands and protocols, meeting diverse debugging needs without changing tools. Wired connection ensures high stability and high-speed transmission (such as large-capacity log download), wireless connection supports mobile debugging and remote operation (such as on-site fault diagnosis and remote parameter configuration), and control unit enables flexible data transmission between the vehicle controller and host computer and mobile terminal, enabling portable use in multiple scenarios. Attached Figure Description

[0018] Figure 1 This is a structural block diagram of the industrial vehicle debugging tool in the embodiment;

[0019] Figure 2 This is a structural block diagram of another industrial vehicle debugging tool in the embodiment. Detailed Implementation

[0020] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, not the entire structure.

[0021] Figure 1 This is a structural block diagram of the industrial vehicle debugging tool in the embodiment, for reference. Figure 1The industrial vehicle debugging tool includes: a control unit 100, at least two communication interfaces (communication interface 1 and communication interface 2), at least one wired communication module 101, at least two wireless communication modules (wireless communication module 1 and wireless communication module 2), a power management module 102, and a battery 103.

[0022] The control unit 100 is electrically connected to the communication interface, the wired communication module 101, the wireless communication module, and the power management module 102, respectively, and the battery 103 is electrically connected to the power management module 102.

[0023] The communication interface is configured to communicate with the vehicle controller, the wired communication module 101 is configured to communicate with the host computer via wired communication, and the wireless communication module is configured to communicate with the host computer or mobile terminal via wireless communication.

[0024] The control unit 100 is configured for data transmission between the vehicle controller and the host computer and mobile terminal.

[0025] In this solution, the control unit 100 is mainly responsible for coordinating the work of all modules, parsing the data protocols of the vehicle controller, host computer, and mobile terminal, and realizing data format conversion and bidirectional transmission (for example, converting the CAN bus data of the vehicle controller into wireless signals and sending them to the mobile terminal).

[0026] In this solution, the communication interface is used to connect directly to the controller of industrial vehicles to adapt to the native interfaces of different vehicle controllers (such as CAN, RS232, RS485, EtherCAT, etc.), ensuring that it can be connected to vehicle controllers of various brands / models.

[0027] In this solution, the wired communication module 101 is used to establish a stable wired connection (such as Ethernet or USB) with the host computer (such as a debugging computer).

[0028] In this solution, the wireless communication module provides wireless connectivity to adapt to different debugging scenarios. The wireless communication module may include a Wi-Fi module, suitable for short-range wireless connection with a host computer; a Bluetooth module, suitable for connection with mobile terminals such as phones / tablets; and a 4G / 5G module, suitable for remote debugging.

[0029] In this solution, the power management module 102 is responsible for power distribution and protection, converting the battery voltage into the operating voltage required by each module (such as 3.3V, 5V, 12V). The power management module 102 can have functions such as overcharge, over-discharge, and short circuit protection.

[0030] In this solution, battery 103 is used to provide portable power, enabling the debugging tool to work independently without an external power source, thus meeting the needs of mobile debugging.

[0031] In this solution, the control unit 100 can be configured to implement protocol encapsulation and transparent transmission. For example, the vehicle status data (speed, battery voltage, fault codes) received by the CAN interface can be encapsulated and sent to the host computer via Wi-Fi. At the same time, the control commands (such as parameter modifications) from the host computer can be converted into CAN signals and sent to the vehicle controller.

[0032] In this solution, the protocol configured in the control unit 100 is converted to a commonly used industrial protocol (such as CANopen-Modbus-TCP / IP), and its specific details will not be described in detail.

[0033] In this solution, the debugging tool can be used for wired or wireless debugging scenarios. For example, for wired debugging scenarios in the workshop, communication interface 1 is connected to the corresponding interface of the vehicle controller, and wired communication module 101 is connected to the host computer. The host computer software reads the vehicle controller data through the debugging tool and performs parameter configuration or fault diagnosis.

[0034] For on-site wireless debugging scenarios, the debugging tool connects to the vehicle controller via communication interface 2 and to the mobile terminal via wireless communication module 2. Debugging personnel can view the vehicle's operating status and quickly locate on-site faults through the mobile terminal's APP.

[0035] For remote debugging scenarios, the debugging tool communicates with the cloud platform via wireless communication module 1, and remotely modifies the vehicle controller parameters through the cloud platform.

[0036] This embodiment proposes a debugging tool that integrates multiple communication interfaces and wired and wireless communication modules. Based on the multiple types of interfaces, it can be adapted to industrial vehicle controllers of different brands and protocols, meeting diverse debugging needs without changing tools. Wired connection ensures high stability and high-speed transmission (such as large-capacity log download), while wireless connection supports mobile debugging and remote operation (such as on-site fault diagnosis and remote parameter configuration). The control unit enables flexible data transmission between the vehicle controller and the host computer and mobile terminal, allowing for portable use in multiple scenarios.

[0037] Based on any of the aforementioned solutions, in one possible implementation, the wireless communication module includes a WIFI module, which is configured with a wireless access point function and is used for wireless communication connection with the host computer.

[0038] In this solution, the selected WIFI module has AP (Access Point) function. The AP function allows the debugging tool to become an independent Wi-Fi hotspot. The host computer does not need to rely on an external router and can directly connect to the hotspot, thereby establishing wireless communication and realizing wireless data transmission between the vehicle controller and the host computer.

[0039] In this solution, the control unit receives data from the vehicle controller (via the communication interface) and sends it unchanged to the WIFI module via serial port. The WIFI module packages the data using TCP / UDP protocol and sends it to the connected host computer. Conversely, data sent by the host computer is received by the WIFI module, forwarded to the control unit via serial port, and then sent to the vehicle controller by the control unit. The entire process does not change the data format (transparent transmission), ensuring the integrity of the debugging data.

[0040] In this solution, the WIFI module has AP function. In environments without external networks (such as workshops or outdoor sites) or in scenarios where it is inconvenient to set up routers, a wireless connection between the host computer and the vehicle controller can be quickly established simply by using the AP hotspot built into the debugging tool, thereby improving debugging flexibility and efficiency.

[0041] Based on any of the aforementioned solutions, in one possible implementation, the wireless communication module includes a Bluetooth module, which is used for wireless communication connection with the mobile terminal.

[0042] In this solution, the debugging tool is equipped with a Bluetooth module. Through the Bluetooth module, the debugging tool can wirelessly connect with mobile terminals (such as mobile phones and tablets), thereby enabling the APP or mini-program on the mobile terminal to directly interact with the debugging tool and realize the debugging of industrial vehicle controllers (such as status monitoring, simple parameter configuration, fault code reading, etc.).

[0043] Compared to Wi-Fi-based PC debugging, Bluetooth modules are better suited for mobile scenarios. They do not require complex network configuration and can communicate simply by pairing, greatly improving the flexibility of on-site debugging.

[0044] Based on any of the aforementioned solutions, in one possible implementation, the communication interface includes an RS232 interface and a CAN interface.

[0045] In this solution, the communication interfaces of the debugging tool include RS232 and CAN interfaces. Both serve as direct physical connection channels between the debugging tool and the industrial vehicle controller, and are adapted to vehicle controllers with different communication protocols and application scenarios.

[0046] The RS232 interface is based on an asynchronous serial communication protocol and is used for scenarios with low transmission rates, short distances, and point-to-point communication. The CAN interface is based on a controller area network protocol and is suitable for industrial scenarios with multiple nodes, high reliability, and strong anti-interference capabilities.

[0047] In this solution, the debugging tool is equipped with two communication interfaces, which can cover the communication needs of most industrial vehicle controllers, ensuring that the debugging tool is compatible with different vehicle controllers and realizes bidirectional data transmission (such as reading vehicle status and sending debugging commands).

[0048] Based on any of the aforementioned solutions, in one possible implementation, the wired communication module includes a USB module.

[0049] In this solution, the wired communication module of the industrial vehicle debugging tool includes a USB module, which serves as a high-speed, stable wired connection channel between the debugging tool and the host computer, enabling bidirectional data transmission between the two.

[0050] In this solution, the host computer and the debugging tool communicate via a serial port protocol. The control unit does not need to handle the complex USB protocol stack; it only needs to interact with the USB chip in the USB module via the serial port.

[0051] Based on any of the aforementioned solutions, in one possible implementation, the debugging tool further includes a storage unit electrically connected to the control unit, the storage unit being configured to store firmware.

[0052] In this solution, the industrial vehicle debugging tool includes a storage unit configured to store the debugging tool's own firmware program. The storage unit supports firmware updates (new firmware is sent via a host computer or mobile terminal and written to the storage unit via the control unit), enabling the debugging tool to extend its lifespan by upgrading firmware to expand its functionality (such as supporting new protocols) and fixing vulnerabilities.

[0053] In this solution, the storage unit can be an SPI Flash, which is connected to the control unit 100 via the SPI bus. The control unit reads / writes firmware data via SPI commands. Alternatively, the storage unit can be an eMMC, which is connected to the control unit via the SDIO interface.

[0054] In this solution, the update mode can be triggered by the host computer. In the update mode, the host computer sends the new firmware file via wired / wireless means. The control unit receives the firmware data and writes it to the backup area of ​​the storage unit. If the firmware data passes the integrity verification, the new firmware is copied from the backup area to the main firmware area of ​​the storage unit; otherwise, the update fails.

[0055] Based on any of the aforementioned solutions, in one possible implementation, the debugging tool further includes an LED indicator light, which is electrically connected to the control unit and configured for interactive indication of the industrial vehicle debugging tool.

[0056] In this solution, the industrial vehicle debugging tool is equipped with LED indicator lights. The LED indicator lights are electrically connected to the control unit. The LED indicator lights can emit light signals of different colors and flashing frequencies, thereby providing feedback on the working status of the debugging tool (such as power supply, communication connection, fault, etc.).

[0057] Based on any of the aforementioned solutions, in one possible implementation, the debugging tool further includes buttons, which are electrically connected to the control unit, and the buttons are configured for human-machine interaction of the industrial vehicle debugging tool.

[0058] In this solution, the industrial vehicle debugging tool is equipped with buttons. These buttons serve as a physical human-machine interface, allowing users to directly control specified functions of the debugging tool (such as mode switching, parameter configuration, and command triggering) through pressing operations.

[0059] In this solution, buttons serve as the physical interaction interface, providing a fast, reliable, and external-device-independent operation method for industrial vehicle debugging tools. During on-site debugging, users can perform core operations such as mode switching, parameter adjustment, and emergency command triggering simply by pressing buttons without opening a host computer or app, significantly improving the tool's ease of use and scenario adaptability.

[0060] Based on any of the aforementioned solutions, in one possible implementation, the battery is a rechargeable lithium battery.

[0061] In this solution, a rechargeable lithium battery is used as the portable power supply for the debugging tool. This can meet the long-term stable power supply requirements of the debugging tool in scenarios where it is not connected to an external power source (such as mobile debugging in the workshop or outdoor operation). It also supports repeated charging, reducing the cost of use.

[0062] In this solution, the charging function of the lithium battery is realized through the power management module 102; the lithium battery supplies power to various modules of the debugging tool (control unit, communication module, etc.) through the power management module 102, and the power management module 102 can be configured to output multiple voltage levels.

[0063] Based on any of the aforementioned schemes, in one possible implementation, the control unit is configured to process data received by the communication interface in parallel and to transmit the data transparently.

[0064] In this solution, the control unit is configured to simultaneously receive and parse data from multiple communication interfaces (such as CAN interface and RS232 interface), enabling concurrent processing of multiple types of data.

[0065] In this solution, the control unit is configured not to perform in-depth parsing on the received data (only necessary format conversion or protocol adaptation), but to forward it to the target end (such as host computer or mobile terminal) as is, or conversely, to forward the instructions from the host computer / mobile terminal to the vehicle controller as is, thereby realizing data pass-through.

[0066] For example, in this solution, the transparent transmission mapping relationship can be defined through firmware. For instance, when the CAN interface receives data and the WIFI module sends data, it is encapsulated as a TCP data packet (without parsing the CAN frame content); when the RS232 interface receives data and the Bluetooth module sends data, the serial port data is directly forwarded (preserving the original string / binary format); when the USB module receives data and the CAN interface sends data, the host computer command is converted into a CAN signal as is (only level conversion is performed).

[0067] Figure 2 This is a structural block diagram of another industrial vehicle debugging tool in the embodiment, for reference. Figure 2 Based on any of the aforementioned solutions, in one possible implementation, the debugging tool includes:

[0068] Control unit 100, RS232 interface 201, CAN interface 202, USB module 301, WIFI module 302, Bluetooth module 303, power management module 102, battery 103, storage unit 104, LED indicator 105, button 106.

[0069] The control unit 100 is electrically connected to the RS232 interface 201, CAN interface 202, USB module 301, WIFI module 302, Bluetooth module 303, power management module 102, storage unit 104, LED indicator 105, and button 106, respectively. The battery 103 is electrically connected to the power management module 102. The WIFI module 302 is configured with AP function.

[0070] RS232 interface 201 and CAN interface 202 are configured for communication connection with vehicle controller 11; USB module 301 and WIFI module 302 are configured for wired communication connection with host computer 12; Bluetooth module 303 is configured for wireless communication connection with mobile terminal 13. Host computer 12 and mobile terminal 13 are configured for communication connection with cloud server 14.

[0071] In this scheme, the control unit 100 is configured to process the data received by the RS232 interface 201 and the CAN interface 202 in parallel, and to transmit the data transparently.

[0072] In this scheme, the main control unit 100 mainly realizes the parallel reception and processing of RS232 serial data and CAN bus message data, and performs protocol encapsulation and transparent transmission.

[0073] USB module 301 primarily enables wired communication between the PC and the wireless debugging tool. WIFI module 302 primarily enables the establishment of an access point (AP) and wireless communication; after the host computer 12's wireless network card connects to the debugging tool's hotspot, wireless pass-through functionality is achieved. Bluetooth module 303 primarily enables wireless communication between the mobile terminal 13's app or mini-program and the debugging tool.

[0074] Button 106 and LED indicator 105 primarily enable human-computer interaction. Power management module 102 primarily manages the charging and discharging of battery 103 and estimates battery capacity. Storage unit 104 primarily stores firmware to be upgraded downloaded from cloud server 14.

[0075] In this solution, the debugging tool can transmit CAN and RS232 data to the PC (host computer 12) via wired transmission through USB module 301; transmit CAN and RS232 data to the PC via WIFI module 302; transmit CAN and RS232 data to the mobile terminal 13 via Bluetooth module 303; and perform functions such as vehicle calibration, firmware upgrade, and fault diagnosis using the APP or applet on the mobile terminal 13.

[0076] In this solution, the debugging tool's WIFI module 302 has a built-in AP hotspot. Since the debugging tool supports AP functionality, it has a built-in WIFI hotspot, eliminating the need for an additional router for WIFI communication. The control unit 100 can perform parallel processing of data from different physical layers and multiple protocols. It can process RS232 serial data and CAN bus message data in parallel and simultaneously transmit them to USB, WIFI, and Bluetooth devices, enabling multiple devices to access terminal information simultaneously. The control unit 100 can be configured to uniformly encapsulate heterogeneous data into a specified format, ensuring compatibility with both PC and mobile data parsing.

[0077] In this solution, the debugging tool can achieve parallel processing and transparent transmission of data at different physical layers, and can simultaneously process RS232 serial data and CAN bus message data. The debugging tool has built-in AP functionality, enabling WIFI data transparent transmission without the need for an additional router. The debugging tool also has a built-in rechargeable lithium battery, eliminating the need for external power. Combined with the built-in Bluetooth communication module, it allows for vehicle calibration, firmware upgrades, and fault diagnosis via a mobile app or mini-program. Wiring is simple and it is easy to use.

[0078] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention. The scope of the present invention is determined by the scope of the appended claims.

Claims

1. An industrial vehicle debugging tool, characterized in that, include: The control unit, at least two communication interfaces, at least one wired communication module, at least two wireless communication modules, a power management module, and a battery; The control unit is electrically connected to the communication interface, the wired communication module, the wireless communication module, and the power management module, respectively, and the battery is electrically connected to the power management module. The communication interface is configured to communicate with the vehicle controller, the wired communication module is configured to communicate with the host computer via wired communication, and the wireless communication module is configured to communicate wirelessly with the host computer or mobile terminal. The control unit is configured to enable data transmission between the vehicle controller and the host computer and mobile terminal.

2. The industrial vehicle debugging tool as described in claim 1, characterized in that, The wireless communication module includes a WIFI module, which is configured with a wireless access point function and is used to wirelessly connect with the host computer.

3. The industrial vehicle debugging tool as described in claim 1, characterized in that, The wireless communication module includes a Bluetooth module, which is used for wireless communication connection with the mobile terminal.

4. The industrial vehicle debugging tool as described in claim 1, characterized in that, The communication interfaces include an RS232 interface and a CAN interface.

5. The industrial vehicle debugging tool as described in claim 1, characterized in that, The wired communication module includes a USB module.

6. The industrial vehicle debugging tool as described in claim 1, characterized in that, It also includes a storage unit electrically connected to the control unit, the storage unit being configured to store firmware.

7. The industrial vehicle debugging tool as described in claim 1, characterized in that, It also includes LED indicator lights, which are electrically connected to the control unit and are configured for interactive indication of industrial vehicle debugging tools.

8. The industrial vehicle debugging tool as described in claim 1, characterized in that, It also includes buttons that are electrically connected to the control unit and are configured for human-machine interaction for industrial vehicle debugging tools.

9. The industrial vehicle debugging tool as described in claim 1, characterized in that, The battery is a rechargeable lithium battery.

10. The industrial vehicle debugging tool as described in claim 1, characterized in that, The control unit is configured to process the data received by the communication interface in parallel and to transmit the data transparently.

Images