Portable automobile bus troubleshooting method, device and equipment and storage medium

Abstract

The invention discloses a portable automobile bus troubleshooting method, device and equipment and a computer readable storage medium, and the method comprises the steps that power supply wires are connected with controllers of a bus to be troubleshot in sequence, the number of the power supply wires is the same as that of the controllers, and the number of the power supply wires is not 1; a test mode is selected through a preset control panel to test the controller, and the test mode comprises an automatic test mode and a manual test mode; according to the method and the device, the test result of the controller is obtained, and the test result is synchronously displayed on the preset control panel, so that the technical problems of large workload and low efficiency of gradual troubleshooting of each controller in the related technology are solved, repeated manual operation on the controller is avoided, and the test efficiency is improved. The troubleshooting efficiency of the vehicle bus is improved; and the manpower troubleshooting cost is saved.

Description

Technical Field

[0001] The present application relates to the field of automotive electronic and electrical technology, and in particular to a portable automotive bus fault troubleshooting method, device, equipment and computer-readable storage medium. Background Art

[0002] With the development of electrification, networking, and intelligence in the commercial vehicle industry, the number of controllers, sensors, and other components that need to be connected to the CAN bus network in automobiles is also increasing. During the actual production and trial production of vehicles, the interference factors in the vehicle bus increase due to the status of various components, and bus failure problems often occur. After preliminary inspections have been made to find that there are no false connections or short circuits in the wiring harness-related wiring, and that the terminal resistance is normal, it is necessary to gradually troubleshoot each controller on the bus network. The production site is different from the vehicle or component test bench, and it is impossible to directly test a single controller. On-site troubleshooting is difficult, and the controller can only be plugged in and out for testing by manual operation, which is labor-intensive and inefficient. If multiple controllers interfere with each other, it will be even more difficult to troubleshoot on site. Summary of the invention

[0003] The present application provides a portable automobile bus fault troubleshooting method, device, equipment and computer-readable storage medium, which can solve the technical problems of large workload and low efficiency in step-by-step troubleshooting of each controller in the prior art.

[0004] In a first aspect, an embodiment of the present application provides a portable vehicle bus fault troubleshooting method, the portable vehicle bus fault troubleshooting method comprising:

[0005] Connecting the power supply wiring to the controllers of the bus to be checked in sequence, wherein the number of the power supply wiring and the number of the controllers is the same and is not 1;

[0006] Selecting a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode;

[0007] The test result of the controller is obtained, and the test result is synchronously displayed on the preset control panel.

[0008] In combination with the first aspect, in one implementation, the automatic test mode includes:

[0009] Testing each of the controllers in turn through each of the power supply connections to obtain test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value;

[0010] If there is no problem with the test results of each of the controllers, then a combination test is performed on the controllers through any two of the power supply connections to obtain the test results corresponding to the two controllers;

[0011] If there is no problem with the test results of the two controllers, the controllers are subjected to a combined test through any two or more power connections to obtain test results corresponding to the two or more controllers.

[0012] In combination with the first aspect, in one implementation, the manual test mode includes:

[0013] Testing each of the controllers in turn through the power supply wiring to obtain a test result of each of the controllers;

[0014] All the controllers are tested through the power supply wiring to obtain test results of all the controllers.

[0015] In combination with the first aspect, in one implementation, before sequentially connecting the power supply wiring to the controller of the bus to be checked, the method further includes:

[0016] Connect the OBD cable to the vehicle OBD interface of the vehicle to be tested;

[0017] Unplug the original vehicle power supply / wake-up fuse of the controller involved in the bus to be checked of the vehicle to be tested, so that the power supply wiring is connected to the controller.

[0018] In combination with the first aspect, in one embodiment, after obtaining the test results of each of the controllers and synchronously displaying the test results on the preset control panel, the method further includes:

[0019] Determine that the test is finished, and replay the test results;

[0020] Or, determine that the test is finished, and copy the test result through the I / O interface.

[0021] In a second aspect, an embodiment of the present application provides a portable vehicle bus fault troubleshooting device, the portable vehicle bus fault troubleshooting device comprising:

[0022] A connection module, used to connect the power supply wiring to the controllers of the bus to be checked in sequence, wherein the number of the power supply wiring and the number of the controllers is the same and is not 1;

[0023] A test module, used to select a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode;

[0024] The display module is used to obtain the test result of the controller and synchronously display the test result on the preset control panel.

[0025] In a third aspect, an embodiment of the present application provides a portable vehicle bus fault troubleshooting device, the portable vehicle bus fault troubleshooting device comprising a processor, a memory, and a portable vehicle bus fault troubleshooting program stored in the memory and executable by the processor, wherein when the portable vehicle bus fault troubleshooting program is executed by the processor, the steps of the portable vehicle bus fault troubleshooting method as described in any one of claims 1 to 5 are implemented.

[0026] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, characterized in that a portable vehicle bus troubleshooting program is stored on the computer-readable storage medium, wherein when the portable vehicle bus troubleshooting program is executed by a processor, the steps of the portable vehicle bus troubleshooting method as described in any one of claims 1 to 5 are implemented.

[0027] The beneficial effects brought by the technical solution provided by the embodiments of the present application include:

[0028] The invention provides a method for testing a bus bus by sequentially connecting power supply wiring to the controller of the bus to be checked, wherein the number of the power supply wiring and the controller is the same and not 1; selecting a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode; obtaining the test result of the controller and synchronously displaying the test result on the preset control panel, thereby solving the technical problems of large workload and low efficiency in step-by-step troubleshooting of each controller in the related art, avoiding repeated manual operations on the controller, improving the efficiency of troubleshooting of vehicle bus faults and saving manpower troubleshooting costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 This is a flow chart of an embodiment of a portable vehicle bus fault troubleshooting method of the present application;

[0030] Figure 2 This is a flow chart of the second embodiment of the portable vehicle bus fault troubleshooting method of the present application;

[0031] Figure 3 This is a flow chart of the third embodiment of the portable vehicle bus fault troubleshooting method of the present application;

[0032] Figure 4 This is a functional module diagram of an embodiment of a portable vehicle bus fault troubleshooting device of the present application;

[0033] Figure 5This is a schematic diagram of the hardware structure of a portable vehicle bus fault troubleshooting device involved in the embodiment of the present application. DETAILED DESCRIPTION

[0034] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0035] First, some technical terms in the present application are explained to facilitate those skilled in the art to understand the present application.

[0036] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0037] In a first aspect, an embodiment of the present application provides a portable vehicle bus fault troubleshooting method.

[0038] In one embodiment, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the portable vehicle bus fault troubleshooting method of the present application. Figure 1 As shown, the portable vehicle bus troubleshooting method includes:

[0039] Step S10: connecting the power supply wiring to the controllers of the bus to be checked in sequence, wherein the number of the power supply wiring and the controllers is the same and the number is not 1;

[0040] Exemplarily, the power wiring of the portable vehicle bus fault troubleshooting device is connected to the controller of the bus to be checked of the vehicle in sequence, and the power wiring includes multiple power wirings, for example, including S1, S2, S3, ... Sn. The controller includes multiple controllers, for example, including E1, E2, E3, ... En. The portable vehicle bus fault troubleshooting device internally includes a central processing unit, a power control module, a bus communication module, a display control panel and a storage module; the external device includes a power control interface, a vehicle OBD interface and a data transmission I / O interface. Among them, the central processing unit is responsible for the overall operation of the device, fault diagnosis and other module control work; the power control module is responsible for the overall power supply of the device and controls the power switches S1, S2, S3, ... Sn in the external power interface to be turned on or off. The number of interfaces can be reserved and expanded according to the needs of the whole vehicle, and is compatible with 12V / 24V power supply systems; the bus communication module can detect the data communication status in the corresponding bus through the OBD interface; the display control panel can realize device function control and communication data status, detection information display, etc. The storage module can store the communication information and communication data status, detection information, etc. collected by the bus communication module, and allow mobile storage devices to copy through the data transmission I / O interface; the power control interface can be connected to the vehicle's universal insurance installation interface through a dedicated wiring harness and control the line conduction / disconnection; the vehicle OBD interface can be connected to the vehicle OBD interface through a dedicated wiring harness to realize bus communication and equipment power supply; the data transmission I / O interface is used for mutual transmission of collected data.

[0041] Step S20: selecting a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode;

[0042] Exemplarily, through the device control panel, select the corresponding test mode and bus interface to be tested, such as 6-14, 3-11, 7-15, etc., and replace the names of S1, S2, S3, etc. with the corresponding vehicle controller names, so that the device can automatically name and save relevant data and results. The test mode includes an automatic test mode and a manual test mode. The automatic test mode includes: testing each of the controllers through each of the power connections in turn to obtain the test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value; if there is no problem with the test results of each of the controllers, then the controllers are combined tested through any two of the power connections to obtain the test results corresponding to the two controllers; if there is no problem with the test results of the two controllers, then the controllers are combined tested through any two or more of the power connections to obtain the test results corresponding to the two or more controllers.

[0043] The manual test mode includes testing each of the controllers in turn through the power wiring to obtain the test results of each controller; or testing all of the controllers through the power wiring to obtain the test results of all of the controllers.

[0044] Step S30: Acquire the test result of the controller, and synchronously display the test result on the preset control panel.

[0045] Exemplarily, the test results include bus baud rate and bus network status information, wherein the bus network status information includes bus load value, error frame and voltage value. The bus baud rate and bus network status information of each controller, wherein the bus network status information includes bus load value, error frame and voltage value, are synchronously displayed on a preset control panel.

[0046] In this embodiment, the power wiring is connected to the controllers of the bus to be checked in sequence, wherein the number of the power wiring and the controllers is the same and the number is not 1; a test mode is selected through a preset control panel to test each controller, wherein the test mode includes an automatic test mode and a manual test mode; the test results of each controller are obtained, and the test results are synchronously displayed on the preset control panel, thereby solving the technical problems of large workload and low efficiency in step-by-step troubleshooting of each controller in the related art, avoiding repeated manual operations on the controller, improving the efficiency of vehicle bus fault troubleshooting and saving manpower troubleshooting costs.

[0047] In one embodiment, referring to Figure 2 , Figure 2 This is a flow chart of the second embodiment of the portable vehicle bus fault troubleshooting method of the present application. Figure 2 As shown, the portable vehicle bus troubleshooting method includes:

[0048] Step S21: testing each of the controllers in turn through each of the power supply connections to obtain test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value;

[0049] Exemplarily, S1, S2, S3, ...Sn are controlled to be closed separately in sequence, and the bus baud rate and bus network status corresponding to the corresponding controllers E1, E2, E3, ...En are recorded respectively, and the message data and test results are automatically stored. The corresponding information is synchronously displayed on the control panel, and you can choose whether to continue the test.

[0050] Step S22: If there is no problem with the test results of each of the controllers, then a combination test is performed on the controllers through any two of the power supply connections to obtain test results corresponding to the two controllers;

[0051] For example, if no obvious abnormality is found during the test, you can choose to continue the test. The device automatically controls the power supply wiring to close all, and disconnects S1, S2, S3, ... Sn in sequence to record the corresponding bus network status when the controller E1, E2, E3, ... En is closed, and automatically stores the message data and test results. The corresponding information is synchronously displayed on the control panel, and you can choose whether to continue the test.

[0052] Step S23: If there is no problem with the test results of the two controllers, then a combination test is performed on the controllers through any two or more power connections to obtain test results corresponding to the two or more controllers.

[0053] For example, if no obvious abnormality is found during the test, you can choose to continue the test. The device automatically controls S1, S2, S3, ... Sn to conduct a combination of connection control from more to less (such as: close S1, S2, test S3 ... Sn bus status, close S1, S3, test S2, S4 ... Sn bus status, etc.), and records the corresponding bus network status of controllers E1, E2, E3, ... En in different combinations, and automatically stores message data and test results, and the corresponding information is synchronously displayed on the control panel. During the test, you can choose to pause / stop / continue the test according to the actual test situation.

[0054] In this embodiment, the bus network status under the operation of different controllers can be tested individually or in combination through the automatic test mode.

[0055] In one embodiment, referring to Figure 3 , Figure 3 This is a flow chart of the third embodiment of the portable vehicle bus fault troubleshooting method of the present application. Figure 3 As shown, the portable vehicle bus troubleshooting method includes:

[0056] Step S24: testing each of the controllers in turn through the power supply wiring to obtain a test result of each of the controllers;

[0057] For example, manually control S1, S2, S3, ...Sn to be closed separately, respectively record the bus baud rate and bus network status of the corresponding controllers E1, E2, E3, ...En in different states, and automatically store the message data and test results, and the corresponding information is synchronously displayed on the control panel. The corresponding test conditions and test results are displayed on the device panel to lock the vehicle bus fault point.

[0058] Step S25: Alternatively, all the controllers are tested through the power supply wiring to obtain test results of all the controllers.

[0059] For example, manually control S1, S2, S3, ... Sn to be all closed, respectively record the bus baud rate and bus network status of the corresponding controllers E1, E2, E3, ... En in different states, and automatically store the message data and test results, and the corresponding information is synchronously displayed on the control panel. The corresponding test conditions and test results are displayed on the device panel to lock the vehicle bus fault point.

[0060] In this embodiment, the manual test mode can be used to control any one or several power supply interfaces to be connected or disconnected according to specific needs of personnel, so as to test the bus network in the corresponding state.

[0061] Furthermore, in one embodiment, before the power wiring is connected to the controller of the bus to be checked in sequence, it also includes: connecting the OBD wiring to the vehicle OBD interface of the vehicle to be checked; unplugging the original vehicle power supply / wake-up fuse of the controller involved in the bus to be checked of the vehicle to be checked, so as to connect the power wiring to the controller.

[0062] Demonstratively, connect the portable automobile bus fault troubleshooting device to the OBD interface of the vehicle through a dedicated OBD connection, and start the device. At this time, the device automatically puts S1, S2, S3, ... Sn, etc. into the disconnected state; connect the detection equipment to the dedicated power connection, and unplug the original vehicle power supply / wake-up fuse of the controllers E1, E2, E3, ... En involved in the bus to be checked, and replace them with S1, S2, S3, ... Sn corresponding to the dedicated power connection.

[0063] The power wiring of the portable vehicle bus fault troubleshooting device is sequentially connected to the controller of the bus to be checked of the vehicle, and the power wiring includes multiple power wirings, for example, including S1, S2, S3, ... Sn. The controller includes multiple controllers, for example, including E1, E2, E3, ... En. The portable vehicle bus fault troubleshooting device internally includes a central processing unit, a power control module, a bus communication module, a display control panel and a storage module; the external device includes a power control interface, a vehicle OBD interface and a data transmission I / O interface. Among them, the central processing unit is responsible for the overall operation of the device, fault diagnosis and other module control work; the power control module is responsible for the overall power supply of the device and controls the power switches S1, S2, S3, ... Sn in the external power interface to be turned on or off. The number of interfaces can be reserved and expanded according to the needs of the whole vehicle, and is compatible with 12V / 24V power supply systems; the bus communication module can detect the data communication status in the corresponding bus through the OBD interface; the display control panel can realize device function control and communication data status, detection information display, etc. The storage module can store the communication information and communication data status, detection information, etc. collected by the bus communication module, and allow mobile storage devices to copy through the data transmission I / O interface; the power control interface can be connected to the vehicle's universal insurance installation interface through a dedicated wiring harness and control the line conduction / disconnection; the vehicle OBD interface can be connected to the vehicle OBD interface through a dedicated wiring harness to realize bus communication and equipment power supply; the data transmission I / O interface is used for mutual transmission of collected data.

[0064] Through the device control panel, select the corresponding test mode and bus interface to be tested, such as 6-14, 3-11, 7-15, etc., and replace the names of S1, S2, S3, etc. with the corresponding vehicle controller names, so that the device can automatically name and save relevant data and results. The test mode includes automatic test mode and manual test mode. The automatic test mode includes: testing each of the controllers through each of the power connections in turn to obtain the test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value; if there is no problem with the test results of each of the controllers, then the controllers are combined tested through any two of the power connections to obtain the test results corresponding to the two controllers; if there is no problem with the test results of the two controllers, then the controllers are combined tested through any two or more of the power connections to obtain the test results corresponding to the two or more controllers.

[0065] The test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value. The bus baud rate and bus network status information of each controller, and the bus network status information includes bus load value, error frame and voltage value are synchronously displayed on the preset control panel.

[0066] In this embodiment, by integrating the functions of bus detection, data acquisition, display, storage and vehicle controller power control, the original computer plus bus detection equipment and other related functions are integrated, the device is more portable and the power supply can be provided by the whole vehicle, and the use conditions are more convenient. The equipment power control module is responsible for the overall power supply of the device and controls the power switches S1, S2, S3, ... Sn in the external power interface to be turned on / off. The number of interfaces can be reserved and expanded according to the needs of the whole vehicle, and is compatible with 12V / 24V power supply systems.

[0067] In a second aspect, an embodiment of the present application also provides a portable vehicle bus fault troubleshooting device.

[0068] In one embodiment, referring to Figure 4 , Figure 4 This is a functional module diagram of an embodiment of a portable vehicle bus fault troubleshooting device of the present application. Figure 4 As shown, the portable vehicle bus fault troubleshooting device includes:

[0069] A connection module 10, used to sequentially connect the power supply wiring to the controllers of the bus to be checked, wherein the number of the power supply wiring and the number of the controllers is the same and is not 1;

[0070] A test module 20, used to select a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode;

[0071] The display module 30 is used to obtain the test result of the controller and synchronously display the test result on the preset control panel.

[0072] Furthermore, in one embodiment, the automatic test mode includes:

[0073] Testing each of the controllers in turn through each of the power supply connections to obtain test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value;

[0074] If there is no problem with the test results of each of the controllers, then a combination test is performed on the controllers through any two of the power supply connections to obtain the test results corresponding to the two controllers;

[0075] If there is no problem with the test results of the two controllers, the controllers are subjected to a combined test through any two or more power connections to obtain test results corresponding to the two or more controllers.

[0076] Furthermore, in one embodiment, the manual test mode includes:

[0077] Testing each of the controllers in turn through the power supply wiring to obtain a test result of each of the controllers;

[0078] All the controllers are tested through the power supply wiring to obtain test results of all the controllers.

[0079] Among them, the functional implementation of each module in the above-mentioned portable vehicle bus fault troubleshooting device corresponds to each step in the above-mentioned portable vehicle bus fault troubleshooting method embodiment, and its functions and implementation processes are no longer repeated here.

[0080] In a third aspect, an embodiment of the present application provides a portable vehicle bus fault troubleshooting device, which may be a personal computer (PC), a laptop computer, a server, or other device with data processing capabilities.

[0081] Reference Figure 5 , Figure 5 The hardware structure diagram of the portable vehicle bus fault troubleshooting device involved in the embodiment of the present application is shown in FIG. In the embodiment of the present application, the portable vehicle bus fault troubleshooting device may include a processor, a memory, a communication interface, and a communication bus.

[0082] The communication bus may be of any type and is used to interconnect the processor, the memory, and the communication interface.

[0083] The communication interface includes input / output (I / O) interface, physical interface and logical interface, etc., which are used to realize the interconnection of devices inside the portable vehicle bus troubleshooting device, and the interface used to realize the interconnection of the portable vehicle bus troubleshooting device with other devices (such as other computing devices or user devices). The physical interface can be an Ethernet interface, a fiber optic interface, an ATM interface, etc.; the user device can be a display, a keyboard, etc.

[0084] The memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.

[0085] The processor may be a general-purpose processor, and the general-purpose processor may call the portable vehicle bus troubleshooting program stored in the memory and execute the portable vehicle bus troubleshooting method provided by the embodiment of the present application. For example, the general-purpose processor may be a central processing unit (CPU). The method executed when the portable vehicle bus troubleshooting program is called may refer to the various embodiments of the portable vehicle bus troubleshooting method of the present application, and will not be repeated here.

[0086] Those skilled in the art will understand that Figure 5 The hardware structure shown in the figure does not constitute a limitation on the present application, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0087] In a fourth aspect, an embodiment of the present application also provides a computer-readable storage medium.

[0088] The computer-readable storage medium of the present application stores a portable vehicle bus fault troubleshooting program, wherein when the portable vehicle bus fault troubleshooting program is executed by a processor, the steps of the portable vehicle bus fault troubleshooting method as described above are implemented.

[0089] Among them, the method implemented when the portable vehicle bus fault troubleshooting program is executed can refer to the various embodiments of the portable vehicle bus fault troubleshooting method of the present application, and will not be repeated here.

[0090] It should be noted that the serial numbers of the above-mentioned embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0091] The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices. The terms "first", "second" and "third" are used to distinguish different objects, etc., and do not represent a sequence, nor do they limit "first", "second" and "third" to different types.

[0092] In the description of the embodiments of the present application, "exemplary", "for example" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary", "for example" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary", "for example" or "for example" is intended to present related concepts in a specific way.

[0093] In the description of the embodiments of the present application, unless otherwise specified, “ / ” means or, for example, A / B can mean A or B; the “and / or” in the text is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “multiple” refers to two or more than two.

[0094] In some processes described in the embodiments of the present application, multiple operations or steps that appear in a specific order are included, but it should be understood that these operations or steps may not be executed in the order in which they appear in the embodiments of the present application or in parallel, and the sequence number of the operation is only used to distinguish the different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed in sequence or in parallel, and these operations or steps may be combined.

[0095] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, disk, CD) as described above, and includes a number of instructions for a terminal device to execute the methods described in each embodiment of the present application.

[0096] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A portable vehicle bus fault troubleshooting method, characterized in that: The portable vehicle bus fault troubleshooting method comprises: Connecting the power supply wiring to the controllers of the bus to be checked in sequence, wherein the number of the power supply wiring and the number of the controllers is the same and is not 1; Selecting a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode; The test result of the controller is obtained, and the test result is synchronously displayed on the preset control panel.

2. The portable vehicle bus fault troubleshooting method according to claim 1, characterized in that: The automatic test mode includes: Testing each of the controllers in turn through each of the power supply connections to obtain test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value; If there is no problem with the test results of each of the controllers, then a combination test is performed on the controllers through any two of the power supply connections to obtain the test results corresponding to the two controllers; If there is no problem with the test results of the two controllers, the controllers are subjected to a combined test through any two or more power connections to obtain test results corresponding to the two or more controllers.

3. The portable vehicle bus fault troubleshooting method according to claim 1, characterized in that: The manual test mode includes: Testing each of the controllers in turn through the power supply wiring to obtain a test result of each of the controllers; Alternatively, all the controllers are tested through the power supply wiring to obtain test results of all the controllers.

4. The portable vehicle bus fault troubleshooting method according to claim 1, characterized in that: Before sequentially connecting the power supply wiring to the controller of the bus to be checked, the method further includes: Connect the OBD cable to the vehicle OBD interface of the vehicle to be tested; Unplug the original vehicle power supply / wake-up fuse of the controller involved in the bus to be checked of the vehicle to be tested, so that the power supply wiring is connected to the controller.

5. The portable vehicle bus fault troubleshooting method according to claim 1, characterized in that: After obtaining the test result of the controller and synchronously displaying the test result on the preset control panel, the method further includes: Determine that the test is finished, and replay the test results; Or, determine that the test is finished, and copy the test result through the I / O interface.

6. A portable vehicle bus fault troubleshooting device, characterized in that: The portable vehicle bus fault troubleshooting device comprises: A connection module, used to connect the power supply wiring to the controllers of the bus to be checked in sequence, wherein the number of the power supply wiring and the number of the controllers is the same and is not 1; A test module, used to select a test mode through a preset control panel to test the controller, wherein the test mode includes an automatic test mode and a manual test mode; The display module is used to obtain the test result of the controller and synchronously display the test result on the preset control panel.

7. The portable vehicle bus fault troubleshooting device as claimed in claim 6, characterized in that: The automatic test mode includes: Testing each of the controllers in turn through each of the power supply connections to obtain test results of each of the controllers, wherein the test results include bus baud rate and bus network status information, and the bus network status information includes bus load value, error frame and voltage value; If there is no problem with the test results of each of the controllers, then a combination test is performed on the controllers through any two of the power supply connections to obtain the test results corresponding to the two controllers; If there is no problem with the test results of the two controllers, the controllers are subjected to a combined test through any two or more power connections to obtain test results corresponding to the two or more controllers.

8. The portable vehicle bus fault troubleshooting device as claimed in claim 6, characterized in that: The manual test mode includes: Testing each of the controllers in turn through the power supply wiring to obtain a test result of each of the controllers; All the controllers are tested through the power supply wiring to obtain test results of all the controllers.

9. A portable vehicle bus fault troubleshooting device, characterized in that: The portable vehicle bus fault troubleshooting device comprises a processor, a memory, and a portable vehicle bus fault troubleshooting program stored in the memory and executable by the processor, wherein when the portable vehicle bus fault troubleshooting program is executed by the processor, the steps of the portable vehicle bus fault troubleshooting method as described in any one of claims 1 to 5 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a portable vehicle bus fault troubleshooting program, wherein when the portable vehicle bus fault troubleshooting program is executed by a processor, the steps of the portable vehicle bus fault troubleshooting method according to any one of claims 1 to 5 are implemented.

Images