An engineering vehicle commissioning method, apparatus and system

Abstract

The application discloses an engineering vehicle debugging method, device and system, a debugging signal is input into a to-be-debugged engineering vehicle to control the to-be-debugged engineering vehicle to execute a debugging action, and during execution of the debugging action by the to-be-debuged engineering vehicle, debugging data of the to-be-debugged engineering vehicle is acquired, wherein the debugging data represents data generated by the to-be-debugged engineering vehicle when executing the debugging action, and finally, a debugging result of the to-be-debugged engineering vehicle is determined according to the debugging data, that is, the debugging signal used for controlling the to-be-debugged engineering vehicle to execute the debugging action is input into the to-be-debugged engineering vehicle, and data generated during the debugging process is acquired, and the generated data is compared with normal data to determine whether the to-be-debugged engineering vehicle meets an offline standard, so that automatic debugging of the to-be-debugged engineering vehicle can be realized by using the debugging signal, the participation of personnel is reduced, the workload of a debugging personnel is reduced, and debugging consistency is improved, so that the accuracy of the debugging result is ensured.

Description

Technical Field

[0001] This application relates to the field of engineering vehicle commissioning technology, specifically to an engineering vehicle commissioning method, apparatus and system. Background Technology

[0002] With the continuous development of society, the mechanization of infrastructure construction projects such as roads, bridges, and buildings is constantly improving, and the demand for excavators is also increasing. To ensure the quality of the finished machines, excavator manufacturers generally conduct off-line tests at the end of the assembly line. Excavators that fail the test are repaired and adjusted, while qualified excavators are released to the market.

[0003] At excavator manufacturers, single-action time measurements are performed on excavators upon production to assess their performance. These measurements primarily include boom lifting time, boom lowering time, stick retraction time, stick swing time, bucket retraction time, and bucket swing time. Currently, single-action time measurements rely mainly on manual measurement, where operators determine the start and stop of the action. Timing begins when the excavator starts moving and stops when it stops moving.

[0004] Because excavators operate at high speeds, manual determination of the start and stop times is prone to errors, resulting in inaccurate test data. Furthermore, manual measurement is subject to subjectivity as different personnel may determine the start and stop times inconsistently, affecting measurement accuracy. Additionally, manual measurement requires one person to operate the excavator while another performs the measurement, leading to a waste of human resources. Summary of the Invention

[0005] To address the aforementioned technical problems, this application is proposed. Embodiments of this application provide a method, apparatus, and system for debugging engineering vehicles, thereby resolving the aforementioned technical problems.

[0006] According to one aspect of this application, a method for debugging an engineering vehicle is provided, comprising: inputting a debugging signal into the engineering vehicle to be debugged to control the engineering vehicle to be debugged to perform a debugging action; acquiring debugging data of the engineering vehicle to be debugged during the execution of the debugging action; wherein the debugging data characterizes the data generated by the engineering vehicle to be debugged when performing the debugging action; and determining the debugging result of the engineering vehicle to be debugged based on the debugging data.

[0007] In one embodiment, before inputting the debugging signal into the engineering vehicle to be debugged, the engineering vehicle debugging method further includes: acquiring the debugging signal.

[0008] In one embodiment, acquiring the debugging signal includes: collecting multiple input signals input by the operator to the vehicle during the debugging process; and selecting one or more of the multiple input signals as the debugging signal.

[0009] In one embodiment, selecting one or more input signals from the plurality of input signals as the debugging signal includes: obtaining a set of curves for the input signals based on the plurality of input signals; wherein the set of curves represents the timing curves of the plurality of input signals; and selecting one or more curves from the set of curves as the debugging signal.

[0010] In one embodiment, selecting one or more curves from the curve set as the debugging signal includes selecting two boundary curves and a curve between the two boundary curves from the curve set as the debugging signal.

[0011] In one embodiment, acquiring the debugging signal includes: collecting multiple input signals input by the operator to the vehicle during the debugging process; and fitting the debugging signal based on the multiple input signals.

[0012] In one embodiment, determining the debugging result of the engineering vehicle to be debugged based on the debugging data includes: determining the debugging result of the engineering vehicle to be debugged based on the debugging data and a pre-set normal range.

[0013] In one embodiment, determining the debugging result of the engineering vehicle to be debugged based on the debugging data and a pre-set normal range includes: determining that the debugging result of the engineering vehicle to be debugged is abnormal when the debugging data is outside the normal range; and initiating an abnormality prompt.

[0014] According to another aspect of this application, an engineering vehicle debugging device is provided, comprising: a signal input module for inputting debugging signals into the engineering vehicle to be debugged to control the engineering vehicle to be debugged to perform debugging actions; a data acquisition module for acquiring debugging data of the engineering vehicle to be debugged during the execution of the debugging actions; wherein the debugging data characterizes the data generated by the engineering vehicle to be debugged when performing the debugging actions; and a result determination module for determining the debugging result of the engineering vehicle to be debugged based on the debugging data.

[0015] According to another aspect of this application, an engineering vehicle commissioning system is provided, comprising: a vehicle; and a vehicle commissioning device as described above, wherein the vehicle commissioning device is connected to the engineering vehicle.

[0016] According to another aspect of this application, an excavator is provided, which is debugged using the engineering vehicle debugging method described in any of the preceding claims.

[0017] According to another aspect of this application, a computer-readable storage medium is provided, the storage medium storing a computer program for performing the engineering vehicle commissioning method described in any of the preceding claims.

[0018] This application provides a method, apparatus, and system for debugging engineering vehicles. By inputting debugging signals into the engineering vehicle to be debugged, the system controls the vehicle to perform debugging actions. During the debugging process, debugging data is acquired, representing the data generated by the vehicle during the debugging actions. Finally, the debugging result is determined based on the debugging data. In other words, by inputting debugging signals to control the vehicle's debugging actions and acquiring the data generated during debugging, the system compares the acquired data with normal data to determine whether the vehicle meets the off-line standards. This allows for automatic debugging of the engineering vehicle using debugging signals, reducing human intervention and workload, improving debugging consistency, and ensuring the accuracy of the debugging results. Attached Figure Description

[0019] The above and other objects, features, and advantages of this application will become more apparent from the more detailed description of the embodiments of this application in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the embodiments of this application to explain this application and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.

[0020] Figure 1 This is a flowchart illustrating an exemplary embodiment of an engineering vehicle commissioning method provided in this application.

[0021] Figure 2 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application.

[0022] Figure 3 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application.

[0023] Figure 4 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application.

[0024] Figure 5This is a schematic diagram of the curve set of input signals for a single action in an engineering vehicle debugging method provided by an exemplary embodiment of this application.

[0025] Figure 6 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application.

[0026] Figure 7 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application.

[0027] Figure 8 This is a schematic diagram of the structure of an engineering vehicle debugging device provided in an exemplary embodiment of this application.

[0028] Figure 9 This is a schematic diagram of the structure of an engineering vehicle debugging device provided in another exemplary embodiment of this application.

[0029] Figure 10 This is a structural diagram of an electronic device provided in an exemplary embodiment of this application. Detailed Implementation

[0030] Hereinafter, exemplary embodiments according to this application will be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this application, and not all embodiments of this application. It should be understood that this application is not limited to the exemplary embodiments described herein.

[0031] Figure 1 This is a schematic flowchart illustrating an exemplary embodiment of an engineering vehicle commissioning method provided in this application. Figure 1 As shown, the engineering vehicle debugging method includes the following steps:

[0032] Step 100: Input the debugging signal into the engineering vehicle to be debugged to control the engineering vehicle to perform debugging actions.

[0033] Construction vehicles (such as excavators) require factory testing to ensure proper functioning and performance. Typically, testing personnel perform a series of standardized operations on each vehicle after it rolls off the production line to test its functionality and performance. For example, excavator testing mainly includes performance testing, pressure testing, test digging, and overall machine inspection. Performance testing involves manual operation of the excavator's handles and foot pedals to perform single actions such as boom raising, boom lowering, stick digging, stick unloading, bucket digging, bucket unloading, left and right slewing, and forward and backward movement. Each single action is repeated three times, with the duration manually recorded using a stopwatch. For example, during boom raising, the testing personnel pull the boom raising handle from its origin to its maximum position, manually recording the time from the start of the movement to the maximum raising position to determine if the duration meets requirements. Pressure testing involves the testing personnel pulling (pushing) the handle to its maximum position and holding it for 5-10 seconds, visually inspecting the hydraulic cylinders for leaks. Test excavation involves the commissioning personnel operating the excavator to simulate excavating and dumping materials or loading them onto trucks, manually checking whether the machine's pressure, flow rate, and speed are normal. The overall machine inspection is completed by the commissioning personnel through visual inspection, touch, and checking doors and buttons. All of these commissioning operations are manually performed by the commissioning personnel, who then record the corresponding data and compare it to normal data ranges to determine if the excavator is functioning correctly. This obviously requires a significant investment of time and effort from the commissioning personnel. Furthermore, differences in skill levels and operating habits among different commissioning personnel, and even variations in the same personnel's operations at different times, lead to inconsistencies in the actual commissioning commands input to the excavator. Additionally, the data recording is subjective and manual, introducing significant subjectivity, which also negatively impacts the accuracy of the commissioning results.

[0034] To address the aforementioned issues, this application proposes an automatic debugging method. This method involves storing debugging signals (control signals that control the engineering vehicle to be debugged to perform corresponding debugging actions) in a signal generating device (e.g., cloud, mobile device, pluggable hard drive, etc.). When debugging is required, the signal generating device is connected to the engineering vehicle to be debugged, allowing the debugging signals from the signal generating device to be input into the vehicle. This enables the vehicle to automatically perform debugging actions, thus achieving automatic debugging operation, reducing the workload of debugging personnel, and minimizing the interference of human subjective factors on the accuracy of the debugging results.

[0035] Step 200: During the debugging process of the engineering vehicle to be debugged, obtain the debugging data of the engineering vehicle to be debugged.

[0036] The debugging data represents the data generated by the engineering vehicle under debugging during the debugging process. This application improves both the automation level and the accuracy of the collected data by installing multiple data collection devices on the engineering vehicle to acquire its debugging data in real time during the debugging process. Specifically, for excavators, this application can install angle sensors on the boom, stick, and bucket to collect angle data of these components in real time during debugging. A data acquisition gateway can also be added to the CAN bus to acquire data transmitted on the CAN bus. Additionally, a camera device can be installed on the excavator (e.g., in an open area on top of the excavator) to acquire the attitude and position information of each component in real time during debugging, thereby assisting other sensors in determining the debugging data of each component during the debugging process.

[0037] Step 300: Determine the debugging results of the engineering vehicle to be debugged based on the debugging data.

[0038] In one embodiment, step 300 can be implemented by determining the debugging result of the engineering vehicle to be debugged based on the debugging data and a pre-set normal range. That is, if the test data is within the pre-set normal range, it means that the vehicle to be tested meets the off-line standard (i.e., the test is qualified or passed); if the test data is not within the pre-set normal range, it means that the vehicle to be tested does not meet the off-line standard (i.e., the test is unqualified or failed). Specifically, taking excavator testing as an example, the lower limit standard for the excavator boom lifting time (from the minimum lifting state to the maximum lifting state, which can be the average of multiple tests) is 3.5 seconds to 4.3 seconds; the lower limit standard for the excavator boom lowering time (from the minimum lowering state to the maximum lifting state, which can be the average of multiple tests) is 3.5 seconds to 4.3 seconds; the lower limit standard for the excavator stick digging time (which can be the average of multiple tests) is 2.5 seconds to 3.5 seconds; and the lower limit standard for the excavator stick unloading time (which can be the average of multiple tests) is 2.5 seconds to 3.5 seconds. By obtaining the excavator's debugging data through testing and determining whether it falls within the lower limit standard range, it is determined whether the vehicle under test meets the lower limit standard. This application utilizes a signal generator to input a debugging signal into the vehicle under test. The vehicle then performs debugging actions based on the signal, and a data collection device simultaneously activates data collection to acquire real-time debugging data generated during the debugging process. This data is then transmitted to the signal generator or another storage device connected in communication with it. In other words, this application, through a pre-set signal generator (containing the corresponding debugging signal) and data collection device, allows for automatic completion of the debugging process during testing. Simply connect the signal generator to the vehicle and simultaneously activate the data collection device. This significantly reduces the workload of debugging personnel, saving labor costs and improving the consistency and accuracy of the debugging process.

[0039] This application provides a method for debugging engineering vehicles. The method involves inputting debugging signals into the engineering vehicle to control it to perform debugging actions. During the debugging process, debugging data is acquired, representing the data generated by the vehicle during the debugging actions. Finally, the debugging result is determined based on the debugging data. Specifically, by inputting debugging signals to control the vehicle's debugging actions and acquiring the data generated during debugging, the method compares the acquired data with normal data to determine whether the vehicle meets the production line standards. This method utilizes debugging signals to achieve automatic debugging of the engineering vehicle, reducing human intervention and workload, improving debugging consistency, and ensuring the accuracy of the debugging results.

[0040] Figure 2 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application. Figure 2 As shown, prior to step 100, the above-mentioned engineering vehicle commissioning method may further include:

[0041] Step 400: Obtain debug signals.

[0042] Because different engineering vehicles require different debugging methods or contents, and even the same type of engineering vehicle may require different debugging methods or contents for different purposes, different debugging signals need to be input. Therefore, before inputting debugging signals, it is necessary to determine the type of engineering vehicle to be debugged and the type of operation to be performed, in order to obtain the corresponding debugging signals. Specifically, all debugging signals of the engineering vehicle can be stored in a signal generator. During actual debugging, only one or more debugging signals need to be selected as the current debugging signal. For example, when the engineering vehicle is an excavator, multiple debugging signals corresponding to the above-mentioned debugging items can be selected.

[0043] Figure 3 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application. Figure 3 As shown, step 400 above may include:

[0044] Step 410: Collect multiple input signals from the vehicle during the debugging process.

[0045] In order to better reflect the performance and function of the engineering vehicle to be tested during actual operation, the testing signals input to the engineering vehicle to be tested in this application need to be similar or close to the control signals input by the staff during actual operation. Therefore, this application collects multiple input signals of the vehicle input by the operator (testing personnel) during the testing process in advance to obtain the input signals when the testing personnel manually test, so as to obtain input signals that are more in line with manual testing, so as to conform to human operating habits and more accurately reflect the actual performance and function of the engineering vehicle to be tested.

[0046] Step 420: Select one or more input signals from the multiple input signals as debugging signals.

[0047] After collecting multiple input signals (i.e., the debugging signals input by the debugging personnel to the engineering vehicle to be debugged during manual debugging), this application can select one or more superior input signals from the multiple input signals as debugging signals, such as selecting the input signal that appears more frequently among the multiple input signals, or selecting the average value of multiple input signals, thereby further improving the consistency and accuracy of the debugging process.

[0048] Figure 4 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application. Figure 4 As shown, step 420 above may include:

[0049] Step 421: Obtain the curve set of the input signals based on multiple input signals.

[0050] The curve set represents the time-series curves of multiple input signals, such as... Figure 5 The figure shows a set of curves composed of multiple timing signal curves for the same single action (only two curves are shown in the figure: Boom up and Boom up2, but this does not limit the number of timing curves in the set). By acquiring multiple input signals, a set of curves for a single action or compound action is obtained (usually, a set of curves consists of multiple similar curves), that is, the trend of the timing curve of the input signal for that single action or compound action.

[0051] Step 422: Select one or more curves from the curve set as debugging signals.

[0052] After obtaining a set of curves for a single action or a compound action, one or more curves in the set can be selected as debugging signals, or the debugging signals for the single action or compound action can be obtained based on the set of curves.

[0053] In one embodiment, step 422 can be implemented by selecting two boundary curves and one curve in the middle of the curve set as debugging signals. To ensure the high performance of the engineering vehicle under testing, this application can select two boundary curves (i.e., the upper and lower limits of the input signal) from the curve set as debugging signals to obtain the performance of the engineering vehicle under extreme input signals, thereby expanding the applicability range of the engineering vehicle under testing and reducing the probability of vehicle failure under extreme operating conditions. Furthermore, this application can also select one of the two boundary curves as the debugging signal to ensure the performance of the engineering vehicle under testing under normal operating conditions, thus enabling a more comprehensive detection of the performance of the engineering vehicle under testing.

[0054] Figure 6 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application. Figure 6 As shown, step 400 above may include:

[0055] Step 430: Collect multiple input signals that the operator inputs into the vehicle during the debugging process.

[0056] In order to better reflect the performance and function of the engineering vehicle to be tested during actual operation, the testing signals input to the engineering vehicle to be tested in this application need to be similar or close to the control signals input by the staff during actual operation. Therefore, this application collects multiple input signals of the vehicle input by the operator (testing personnel) during the testing process in advance to obtain the input signals when the testing personnel manually test, so as to obtain input signals that are more in line with manual testing, so as to conform to human operating habits and more accurately reflect the actual performance and function of the engineering vehicle to be tested.

[0057] Step 440: Fit the debugging signal based on multiple input signals.

[0058] After collecting multiple input signals (i.e., the debugging signals input by the debugging personnel to the engineering vehicle to be debugged during manual debugging), this application can fit a fitted signal based on the multiple input signals. This fitted signal may be one of the multiple input signals, or it may not belong to any of the multiple signals. The fitted signal obtained by fitting multiple input signals can combine the advantages of multiple input signals and avoid the disadvantages of each input signal (such as jitter), thereby obtaining a better debugging signal. It should be understood that the debugging signal fitted in this application can also be combined with the two boundary curves in the above-mentioned curve set for joint debugging, so as to expand the applicability of the engineering vehicle to be debugged.

[0059] Figure 7 This is a flowchart illustrating a method for debugging an engineering vehicle, provided in another exemplary embodiment of this application. Figure 7 As shown, step 300 above may include:

[0060] Step 310: When the debugging data is outside the normal range, the debugging result of the engineering vehicle to be debugged is determined to be abnormal.

[0061] Step 320: Prompt an exception message.

[0062] If the debugging data collected during the debugging process is outside the normal range, meaning the debugging output data does not meet the vehicle's off-line standards, it indicates that the debugging data is abnormal. This confirms that the debugging result of the engineering vehicle to be debugged is abnormal, and an abnormality alert can be issued, such as an alarm (audio-visual alarm) or voice prompt. To further improve the automation level of automatic debugging, this application can also analyze the abnormal components and corresponding causes based on the type and content of the abnormal data after detection, and display the corresponding results to the debugging personnel via voice (audio) or images / video (display screen).

[0063] The following uses an excavator as an example to illustrate the process of adjusting the speed of an excavator using the adjustment method provided in this application:

[0064] At the start of debugging, connect the signal generator to the excavator controller or CAN bus, and turn on the preset switch button to input the debugging signal stored in the signal generator to the excavator controller or CAN bus, so as to control the excavator to perform the corresponding debugging actions, thereby completing a series of debugging actions and recording debugging data for subsequent analysis and to give the corresponding debugging results.

[0065] (1) Performance testing. The signal generator inputs a debugging signal (i.e., replaces the hand handle to input operation commands). When the excavator performs the corresponding operation, it automatically records the duration of the operation and the extension and retraction time of the hydraulic cylinder of the working device, automatically generates a performance test table, and stores it in the cloud.

[0066] (2) Pressure test. After the performance test is completed, this step is automatically entered. At the same time, the system operation information is recorded. The pressure fluctuation during the extension and retraction of the working device cylinder is used to determine whether there is oil leakage and a prompt is given.

[0067] (3) Trial Excavation Test. After the pressure test is completed, this step is automatically initiated. Simultaneously, characteristic parameters describing the machine's operating performance, such as pressure, flow rate, rotation speed, gear position, temperature, and attitude, as well as fault information, are automatically recorded during the trial excavation process. These are indicated by sound, light, and interface colors, and finally, a table is automatically generated and uploaded to the cloud. The historical execution records for the machine's lifecycle can be retrieved later by opening the mobile phone.

[0068] During the commissioning process, the operating status parameters (pressure, flow rate, speed, gear, temperature, etc.) and fault information can be displayed simultaneously on a large monitoring screen.

[0069] Figure 8 This is a schematic diagram of the structure of an engineering vehicle debugging device provided in an exemplary embodiment of this application. Figure 8 As shown, the engineering vehicle debugging device 80 includes: a signal input module 81, used to input debugging signals into the engineering vehicle to be debugged, so as to control the engineering vehicle to be debugged to perform debugging actions; a data acquisition module 82, used to acquire debugging data of the engineering vehicle to be debugged during the debugging action; wherein, the debugging data represents the data generated by the engineering vehicle to be debugged when performing the debugging action; and a result determination module 83, used to determine the debugging result of the engineering vehicle to be debugged based on the debugging data.

[0070] This application provides an engineering vehicle debugging device. A signal input module 81 inputs a debugging signal into the engineering vehicle to be debugged, controlling the vehicle to perform debugging actions. During the debugging process, a data acquisition module 82 acquires debugging data from the vehicle, whereby the debugging data represents the data generated by the vehicle during the debugging actions. Finally, a result determination module 83 determines the debugging result of the vehicle based on the debugging data. In other words, by inputting the debugging signal used to control the vehicle to perform debugging actions into the vehicle and acquiring the data generated during the debugging process, the device compares the generated data with normal data to determine whether the vehicle meets the off-line standards. This allows for automatic debugging of the vehicle using the debugging signal, reducing human intervention and workload, improving debugging consistency, and ensuring the accuracy of the debugging results.

[0071] Figure 9 This is a schematic diagram of the structure of an engineering vehicle debugging device provided in another exemplary embodiment of this application. (See diagram below.) Figure 9 As shown, the engineering vehicle debugging device 80 may further include a signal acquisition module 84 for acquiring debugging signals.

[0072] In one embodiment, such as Figure 9 As shown, the signal acquisition module 84 may further include: a signal collection unit 841, used to collect multiple input signals input by the operator into the vehicle during the debugging process; and a signal selection unit 842, used to select one or more input signals from the multiple input signals as debugging signals.

[0073] In one embodiment, the signal selection unit 842 may be further configured to: obtain a set of curves of input signals based on multiple input signals, wherein the set of curves represents the timing curves of multiple input signals; and select one or more curves from the set of curves as debugging signals.

[0074] In one embodiment, the signal selection unit 842 may be further configured to select two boundary curves and one curve in the middle of the curve set as debugging signals.

[0075] In one embodiment, such as Figure 9 As shown, the signal acquisition module 84 may further include a signal fitting unit 843, used to fit a debugging signal based on multiple input signals.

[0076] In one embodiment, such as Figure 9As shown, the result determination module 83 may include: an anomaly determination unit 831, used to determine that the debugging result of the engineering vehicle to be debugged is abnormal when the debugging data is outside the normal range; and an anomaly prompting unit 832, used to initiate an anomaly prompt.

[0077] This application also provides an engineering vehicle commissioning system, comprising: a vehicle; and a vehicle commissioning device as described above, wherein the vehicle commissioning device is connected to the engineering vehicle.

[0078] This application provides an engineering vehicle debugging system that controls the engineering vehicle to perform debugging actions by inputting debugging signals into the vehicle to be debugged. During the debugging process, debugging data is acquired, representing the data generated by the vehicle during the debugging actions. Finally, the debugging result is determined based on the debugging data. In other words, by inputting debugging signals to control the vehicle to perform debugging actions and acquiring the data generated during the debugging process, the system compares the generated data with normal data to determine whether the vehicle meets the off-line standards. This system utilizes debugging signals to achieve automatic debugging of the engineering vehicle, reducing human intervention and workload, improving debugging consistency, and ensuring the accuracy of the debugging results.

[0079] This application also provides an excavator that is debugged using any of the above-described engineering vehicle debugging methods, or the excavator includes the above-described engineering vehicle debugging device.

[0080] This application provides an excavator that controls the excavator to perform debugging actions by inputting debugging signals. During the debugging process, debugging data is acquired, representing the data generated by the excavator during the debugging actions. Finally, the debugging result is determined based on the debugging data. Specifically, by inputting debugging signals to control the excavator's debugging actions and acquiring the data generated during the debugging process, the generated data is compared with normal data to determine whether the excavator meets the discharge standard. This allows for automatic debugging of the excavator using debugging signals, reducing human intervention and workload, improving debugging consistency, and ensuring the accuracy of the debugging results.

[0081] Below, for reference Figure 10 This application describes an electronic device according to embodiments thereof. The electronic device may be either or both of a first device and a second device, or a standalone device independent of them, which may communicate with the first device and the second device to receive acquired input signals from them.

[0082] Figure 10 A block diagram of an electronic device according to an embodiment of this application is illustrated.

[0083] like Figure 10 As shown, the electronic device 10 includes one or more processors 11 and memory 12.

[0084] The processor 11 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 10 to perform desired functions.

[0085] The memory 12 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 11 may execute the program instructions to implement the methods of the various embodiments of this application described above and / or other desired functions. Various contents such as input signals, signal components, and noise components may also be stored in the computer-readable storage medium.

[0086] In one example, the electronic device 10 may also include an input device 13 and an output device 14, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0087] When the electronic device is a standalone device, the input device 13 can be a communication network connector for receiving the collected input signals from the first device and the second device.

[0088] In addition, the input device 13 may also include, for example, a keyboard, a mouse, etc.

[0089] The output device 14 can output various information to the outside, including determined distance information, direction information, etc. The output device 14 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0090] Of course, for the sake of simplicity, Figure 10 Only some of the components of the electronic device 10 relevant to this application are shown in this illustration; components such as buses, input / output interfaces, etc., are omitted. In addition, the electronic device 10 may include any other suitable components depending on the specific application.

[0091] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this application. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0092] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may, for example, include, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0093] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this application to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations thereof.

Claims

1. A method for debugging engineering vehicles, characterized in that, include: Acquiring debugging signals includes: collecting multiple input signals input to the vehicle by the operator during the debugging process; and obtaining a set of curves for the input signals based on the multiple input signals; wherein the set of curves represents the time-series curves of the multiple input signals; and selecting one or more curves from the set of curves as the debugging signal, wherein the debugging signal is obtained based on the type of engineering vehicle to be debugged and the type of operation to be performed. Input the debugging signal into the engineering vehicle to be debugged, so as to control the engineering vehicle to be debugged to perform the debugging action; During the debugging process of the engineering vehicle to be debugged, debugging data of the engineering vehicle to be debugged is acquired; wherein, the debugging data represents the data generated by the engineering vehicle to be debugged when performing the debugging process; and Based on the debugging data, the debugging results of the engineering vehicle to be debugged are determined.

2. The engineering vehicle debugging method according to claim 1, characterized in that, Selecting one or more curves from the curve set as the debugging signal includes: Two boundary curves and one curve in the middle of the two boundary curves are selected from the curve set as the debugging signal.

3. The engineering vehicle debugging method according to claim 1, characterized in that, The acquisition of debugging signals includes: Collect multiple input signals from the operator during the vehicle commissioning process; and The debugging signal is obtained by fitting the multiple input signals.

4. The engineering vehicle debugging method according to claim 1, characterized in that, The step of determining the debugging result of the engineering vehicle to be debugged based on the debugging data includes: Based on the debugging data and the pre-set normal range, the debugging result of the engineering vehicle to be debugged is determined.

5. The engineering vehicle commissioning method according to claim 4, characterized in that, The step of determining the debugging result of the engineering vehicle to be debugged based on the debugging data and the preset normal range includes: When the debugging data is outside the normal range, the debugging result of the engineering vehicle to be debugged is determined to be abnormal; and Initiate an error message.

6. A debugging device for engineering vehicles, characterized in that, include: The signal acquisition module is used to acquire debugging signals; The signal acquisition module includes a signal collection unit and a signal selection unit. The signal collection unit is used to collect multiple input signals input by the operator to the vehicle during the debugging process. The signal selection unit is used to obtain a curve set of the input signals based on the multiple input signals, wherein the curve set represents the time sequence curve of the multiple input signals, and to select one or more curves in the curve set as the debugging signal. The debugging signal is obtained according to the type of engineering vehicle to be debugged and the type of operation to be performed. The signal input module is used to input debugging signals into the engineering vehicle to be debugged, so as to control the engineering vehicle to be debugged to perform debugging actions; The data acquisition module is used to acquire debugging data of the engineering vehicle to be debugged during the debugging process; wherein the debugging data represents the data generated by the engineering vehicle to be debugged when performing the debugging action; and The result determination module is used to determine the debugging result of the engineering vehicle to be debugged based on the debugging data.

7. A commissioning system for engineering vehicles, characterized in that, include: Engineering vehicles; as well as The engineering vehicle debugging device as described in claim 6, wherein the vehicle debugging device is connected to the engineering vehicle.

8. An excavator, characterized in that, The excavator is debugged using the engineering vehicle debugging method described in any one of claims 1-5, or includes the engineering vehicle debugging device described in claim 6.

9. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for executing the engineering vehicle debugging method according to any one of claims 1-5.

Images