Stacker and storage location docking test method, device and system and storage medium

Abstract

The invention provides a stacking machine and storage location docking test method, device and system and a storage medium. The method comprises the steps that the current state of a target stacking machine is obtained; and when the current state is the idle state and the target stacker does not complete the docking test on all available storage locations in the target test area, generating a new test task, and issuing the new test task to the target stacker, so that the target stacker performs the docking test on the next available storage location in the target test area. Returning to the step of acquiring the current state of the target stacker and continuing to execute; and generating a test report according to task execution information uploaded when the target stacker completes the test tasks related to the target test area under the condition that the current state is an idle state and the target stacker completes the docking test on all available storage locations in the target test area. According to the method, the test efficiency is improved, the range is more comprehensive, the result is more accurate, and three-dimensional warehouse optimization is facilitated.

Description

Technical Field

[0001] The present application relates to the field of intelligent warehousing technology, and in particular to a method, device, system and storage medium for testing docking between a stacker and a storage location. Background Art

[0002] Smart warehousing is a new concept of warehousing management. It is a smart logistics realized through informatization, Internet of Things and mechatronics, which can reduce warehousing costs, improve operational efficiency and enhance warehousing management capabilities. There are many types of warehouses developed based on the concept of smart warehousing, and stereoscopic warehouses are a more important component. The stacker is the main lifting and transportation equipment in the stereoscopic warehouse. It is a special lifting machinery equipment developed with the stereoscopic warehouse. The main purpose of the stacker is to shuttle back and forth between the lanes of the stereoscopic warehouse. It docks with the storage locations in the stereoscopic warehouse, for example, storing the goods at the entrance of the lane into the storage location, or taking out the goods in the storage location and transporting them to the entrance of the lane. Before the stacker is officially put into operation, it is necessary to test the docking between the stacker and the storage location. The traditional test method is mainly for professional commissioning personnel to manually enter parameters for single storage location commissioning, and use the test results of some storage locations to judge the commissioning of the overall storage location. This method has problems such as high professional requirements for commissioning personnel, large manpower requirements, low commissioning efficiency, and low reliability of results. Summary of the invention

[0003] The purpose of this application is to solve at least one of the above-mentioned technical defects, especially the problems existing in the prior art test method for docking stacker and storage location, such as high professional requirements for debugging personnel, large manpower demand, low debugging efficiency, and low reliability of results.

[0004] In a first aspect, the present application provides a method for testing docking between a stacker and a storage location, comprising:

[0005] Get the current status of the target stacker;

[0006] When the current state is idle and the target stacker has not completed docking tests on all available storage locations in the target test area, a new test task is generated and sent to the target stacker, so that the target stacker performs docking tests on the next available storage location in the target test area, and returns to the step of obtaining the current state of the target stacker to continue execution; when the target stacker completes a test task, it will upload the task execution information;

[0007] When the current state is idle and the target stacker completes docking tests on all available storage locations in the target test area, a test report is generated according to the task execution information uploaded when the target stacker completes the test tasks related to the target test area.

[0008] In one embodiment, generating a new test task includes:

[0009] If the target stacker has not been tested in the target test area, the target starting position in the task configuration table is used as the task starting point; the target starting position is the position of the first available storage location in the target test area;

[0010] Otherwise, the first end position is used as the task starting point; the first end position is the end position of the previous test task of the target stacker;

[0011] Search for an available storage location adjacent to the task starting point in the target test area, and use the searched available storage location as the task end point;

[0012] Generate a test task based on the task start point and task end point.

[0013] In one embodiment, determining whether the target stacker has performed docking tests on all available storage locations in the target test area includes:

[0014] Determine whether the first end position matches the target end position in the task configuration table; the target end position is the position of the last available storage location in the target test area;

[0015] If so, it is determined that the target stacker has completed docking testing for all available storage locations in the target test area;

[0016] If not, it is determined that the target stacker has not completed the docking test for all available storage locations in the target test area.

[0017] In one embodiment, generating a test task according to a task start point and a task end point includes:

[0018] A test task is generated according to a task configuration table, a task start point and a task end point; the task configuration table also includes at least one parameter for indicating whether a cargo test is performed, a test task type, a test exception handling method, and an alarm manual intervention threshold.

[0019] In one embodiment, searching for an available storage location adjacent to the first end position in the target test area includes:

[0020] Starting from the task starting point, traverse to the last storage location of the target test area in the order of layer, column, row, and lane, and the first available storage location traversed is the available storage location adjacent to the first end position.

[0021] In one embodiment, when the current state is an idle state and the target stacker completes the docking test for all available storage locations in the target test area, a test report is generated according to the task execution information uploaded when the target stacker completes the test task related to the target test area, including:

[0022] When the current state is an idle state and the target stacker completes the docking test for all available storage locations in the target test area, obtaining a parameter value of a parameter in the task configuration table for reflecting whether to restart the test;

[0023] If the parameter value reflects yes, then return to obtain the current state of the target stacker and restart the docking test on the target test area;

[0024] If the parameter value reflects no, a test report is generated based on the task execution information uploaded when the target stacker completes the test task related to the target test area.

[0025] In one embodiment, after obtaining the current state of the target stacker, the method further includes:

[0026] When the current state is the executing state, the current position of the target stacker is recorded.

[0027] In a second aspect, the present application provides a stacker and storage location docking test device, comprising:

[0028] A data acquisition module is used to obtain the current status of the target stacker;

[0029] The task generation module is used to generate a new test task when the current state is idle and the target stacker has not completed the docking test for all available storage locations in the target test area, and send it to the target stacker so that the target stacker can perform the docking test on the next available storage location in the target test area, and return to the step of obtaining the current state of the target stacker to continue execution; when the target stacker completes a test task, it will upload the task execution information;

[0030] The report generation module is used to generate a test report according to the task execution information uploaded when the target stacker completes the test task related to the target test area when the current state is idle and the target stacker completes the docking test on all available storage locations in the target test area.

[0031] In a third aspect, the present application provides a stacker and storage location docking test system, including a host computer and multiple stackers, the host computer being communicatively connected to each stacker, the host computer including one or more processors, and a memory, the memory storing computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the steps of the stacker and storage location docking test method described in any of the above embodiments are executed.

[0032] In a fourth aspect, the present application provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the stacker and storage location docking test method as described in any of the above embodiments.

[0033] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages:

[0034] Based on any of the above embodiments, the host computer first obtains the current state of the target stacker related to the target test area to determine whether it can undertake a new test task. When the stacker is in an idle state and has not completed the test of all target test areas, the host computer will intelligently generate a new test task, instruct the stacker to go to the next storage location to be tested in the area for docking test, and then continue to return to the step of monitoring the status of the stacker for monitoring. If the test of all target test areas has been completed, the host computer will summarize all task execution information reported by the stacker when testing in the target test area and generate a test report. This method realizes full coverage automated testing of the target test area of ​​the vertical library without manual intervention. At the same time, the test report reflects the docking performance of all available storage locations in the target test area, which can evaluate the use efficiency of the vertical library equipment and find problem storage locations. Compared with the traditional manual testing method, the test efficiency is greatly improved, the scope is more comprehensive, the results are more accurate, and data support is provided for the optimization of the vertical library. In addition, through the setting of the host computer software level, the object at the equipment level of the stacker is fully controlled, and the control logic that the PLC on the stacker needs to execute is minimized. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0036] Figure 1 A schematic diagram of a process for testing a stacker and a storage location docking provided in one embodiment of the present application;

[0037] Figure 2 A schematic diagram of a flow chart of a method for testing docking between a stacker and a storage location provided in another embodiment of the present application;

[0038] Figure 3 An internal structure diagram of a host computer provided for one embodiment of the present application. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions 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.

[0040] The present application provides a method for testing the docking between a stacker and a storage location, which can be applied to a stacker and a storage location docking test system with a host computer as the core. The staff can configure each stacker on the host computer to create a model instance corresponding to each stacker. The parameters that need to be configured may include the equipment parameters of each stacker, such as the type of stacker. In order to facilitate the host computer to establish a communication connection with each stacker, the connection parameters of each stacker, such as the stacker number, name, IP address, warehouse number, etc., can also be entered in the host computer.

[0041] After the host computer establishes a connection with the stacker using the connection parameters, in order to facilitate the host computer to control the stacker and monitor its status, the staff can define which variables can be used for interaction between the host computer and the stacker through the interactive variable table, the data type, address, length, value range of the variables, and the corresponding meaning of each value. The host computer can send control commands to the stacker by assigning values ​​to specific fields and then transmitting them between the stacker, and the stacker can also report its own status to the host computer. Since the host computer needs to send test tasks to the stacker, the interactive variable table can include relevant parameters for helping the host computer write test tasks to the stacker, such as the task number of the test task, the starting position, the end position, whether to pick up goods, whether to put goods, and the task type. The stacker also needs to report its own status to the host computer. The interactive variable table can also include relevant parameters for the host computer to read its status from the stacker, such as the current status of whether the task is being executed, the communication status, the heartbeat value, whether to carry goods, whether the equipment is abnormal, the current position, the test task execution stage, etc. The parameters in the interactive variable table can be configured by the staff.

[0042] In addition, the host computer also needs to know the relevant information of the storage locations in the warehouse it controls. The staff can enter the relevant information of the storage locations in each shelf in the shelf information table, such as the location of the storage location, the type of storage location, the type of pallet used by the storage location, etc. The host computer can create model instances of each shelf in the warehouse it manages based on the shelf information table.

[0043] Furthermore, after the above configuration work is completed, the host computer can create corresponding visualization objects for each model instance, and by clicking on the visualization object, the query and modification of the data table related to the model instance can be triggered. By dragging the visualization object, an association relationship can be established between model instances. For example, if a stacker is responsible for operating certain shelves, the visualization object of the stacker can be dragged together with the visualization object of the shelf to establish an association relationship between them.

[0044] Based on the above configuration, the host computer controls the stacker to perform full coverage automatic docking test between the stacker and the storage location. Figure 1 The stacker and storage location docking test method includes steps S102 to S106.

[0045] S102, obtaining the current state of the target stacker.

[0046] It can be understood that the present embodiment tests the storage locations within a certain range in the opposing warehouse, i.e., the target test area. The target stacker refers to the stacker associated with the target test area. Since each stacker only travels on a fixed lane, if the target test area to be tested only involves a single lane, the number of target stackers is one. If the target test area to be tested is an area covering multiple lanes, the number of target stackers can be at least two. When the user instructs the host computer to start the test, the host computer will collect the current state of the target stacker through the interactive variable table to determine whether the target stacker is performing the test task. The interactive variable table may also include the current position of the target stacker. When the host computer obtains the current state, it may also obtain the current position of the target stacker at the same time, and display the position of the target stacker in the warehouse in a visual manner to achieve comprehensive monitoring of the test process.

[0047] Regarding the target test area, it can be limited by the task configuration table in the host computer. Specifically, the task configuration table may include the target starting position and the target ending position. The target starting position is the position of the first available storage location in the target test area, and the target ending position is the position of the last available storage location in the target test area. For example, the layer number, row number, column number and lane number of the storage location are used as coordinates to represent the location of the storage location. Then the first available storage location can be the available storage location with the smallest layer number, row number, column number and lane number in the target test area, and the last available storage location can be the available storage location with the largest layer number, row number, column number and lane number in the target test area. Further, the available storage location here refers to the availability of the storage location during the test phase, that is, the available storage location refers to the storage location that needs to participate in the test, and the unavailable storage location refers to the storage location that does not need to participate in the test. The staff can set whether each storage location is available through the shelf information table.

[0048] S104, when the current state is idle and the target stacker has not completed the docking test on all available storage locations in the target test area, a new test task is generated and sent to the target stacker, so that the target stacker performs a docking test on the next available storage location in the target test area, and returns to the step of obtaining the current state of the target stacker to continue execution.

[0049] It can be understood that the state of the stacker may include an idle state, an executing state, and a completed state. Among them, the idle state refers to the state in which the stacker is in when there is no test task being executed. The executing state refers to the state in which the stacker is in when it is executing a test task. The completed state is a transition state between the idle state and the executing state. When the stacker completes a test task, it will enter the completed state from the executing state. When the upper computer determines that the stacker is in the executing state, it will instruct the stacker to upload the task execution information, that is, report the test results of the test task just completed. When the upper computer receives the task execution information, it will feedback confirmation information to the stacker, and the stacker will enter the idle state.

[0050] The test tasks performed by the stacker can be fixed types, or parameters related to the task type can be added to the above task configuration table. Through the value of the parameter, different types of test tasks are issued to the target stacker, such as the task of transferring goods within the warehouse or the task of entering and leaving the warehouse. The test results of the stacker will be generated based on the feedback of the sensors set on the stacker itself and the warehouse location to form task execution information.

[0051] When the target stacker is in an idle state, it is necessary to determine whether the target stacker has completed the docking test for all available storage locations in the target test area. If not, a new test task should be generated and the stacker should be instructed to continue to execute the new test task. At this time, the target stacker will re-enter the execution state, and the host computer will also return to step S102 to continue monitoring the working state of the target stacker. The above-mentioned new test task is used to instruct the target stacker to start from the available storage location where the last test was completed, and go to the next available storage location of the available storage location for docking test.

[0052] The next available storage location here can be searched in the target test area according to the preset search rules. From the perspective of test efficiency, the available storage location adjacent to the available storage location can be directly searched. That is, the target stacker starts from the target starting position in a certain order in the target test area, and each time it conducts docking tests with the available storage location adjacent to the available storage location of the previous test until the target end position is tested, thereby achieving full coverage of the target test area. Of course, the management personnel can also design other test rules according to the test needs, such as the end point of each test task needs to be separated from the previous time by multiple storage locations.

[0053] S106, when the current state is an idle state and the target stacker completes docking tests on all available storage locations in the target test area, a test report is generated according to each task execution information uploaded when the target stacker completes the test tasks related to the target test area.

[0054] It can be understood that when the target stacker is in an idle state, if it is determined that the target stacker has completed the docking test for all available storage locations in the target test area, all task execution information uploaded by the target stacker when executing the test task related to the target test area can be summarized and processed to generate a test report. Specifically, each test task will be assigned a corresponding task number when it is issued, and the current status of the task and the number of the issued stacker will be recorded in the test task. When a target test area needs to be tested, a blank task table corresponding to it will be created, and these test tasks will be summarized in the task table corresponding to this test. When the target stacker is collected in the execution state, the corresponding test task will be found in the task table according to its number, and the current state of the test task will be updated to execution. When the target stacker is collected in the completion state, the corresponding test task will be found in the task table according to its number, and the current state of the test task will be updated to completion. When the target stacker uploads the task execution information, the task number will be added to the task execution information. When a test report needs to be generated, the task table records all test tasks related to the target test area. All their task numbers are extracted, and then the corresponding task execution information is extracted to generate a test report based on this part of the task execution information. The test report generation method can be set by the staff, for example, filtering out the fields of interest from the task execution information, and then displaying them in a combination of charts and data.

[0055] Based on the stacker and storage location docking test method in this embodiment, the host computer first obtains the current state of the target stacker related to the target test area to determine whether it can undertake a new test task. When the stacker is in an idle state and has not completed the test of all target test areas, the host computer will intelligently generate a new test task, instruct the stacker to go to the next storage location to be tested in the area for docking test, and then continue to return to the step of monitoring the stacker status for monitoring. If the test of all target test areas has been completed, the host computer will summarize all task execution information reported by the stacker when testing in the target test area and generate a test report. This method realizes full coverage automated testing of the target test area of ​​the vertical warehouse without manual intervention. At the same time, the test report reflects the docking performance of all available storage locations in the target test area, which can evaluate the use efficiency of the vertical warehouse equipment and find problem storage locations. Compared with the traditional manual testing method, the test efficiency is greatly improved, the scope is more comprehensive, and the results are more accurate, providing data support for the optimization of the vertical warehouse. In addition, through the settings at the upper computer software level, complete control of the stacker as an object at the device level can be achieved, minimizing the control logic that needs to be executed by the PLC on the stacker.

[0056] In one embodiment, generating a new test task includes:

[0057] (1) If the target stacker has not been tested in the target test area, the target starting position in the task configuration table is used as the task starting point. The target starting position is the position of the first available storage location in the target test area.

[0058] It can be understood that when the target stacker is in an idle state, it is possible that it has never been tested in the target test area and is waiting to receive the first test task. It may also be that a test task has just ended and it is waiting to receive the next test task. The idea of ​​the target stacker to test in this embodiment is to test the adjacent available storage locations from the first available storage location in the target test area in sequence until the last available storage location in the target test area is tested. On this basis, for these two situations, the way of selecting the starting point of the test task is different. Specifically, when the target stacker has not been tested in the target test area, the target stacker will perform the first test task on the target test area, and the starting point of the test task should be the first available storage location in the entire target test area, that is, the target starting position. If the layer number, row number, column number and lane number of the storage location are used as coordinates to represent the location of the storage location. Then the first available storage location can be the available storage location with the smallest layer number, row number, column number and lane number in the target test area.

[0059] Regarding determining whether the target stacker has been tested in the target test area, if the task table corresponding to the target test area in the above description is used to record the relevant task status, it can be determined by detecting whether the task table corresponding to the target test area does not have a test task in the completed state. If so, it is determined that the target stacker has not been tested in the target test area. If not, it is determined that the target stacker has been tested in the target test area.

[0060] (2) Otherwise, the first end position is taken as the task starting point.

[0061] To ensure that no available storage locations are missed in the target test area, if the target stacker has been tested in the target test area, it should start from the position where the previous test task ended, that is, the first end position, and move to the adjacent available storage location to perform a docking test with the adjacent available storage location.

[0062] (3) Search for an available storage location adjacent to the task starting point in the target test area, and use the searched available storage location as the task end point.

[0063] After determining the task starting point, based on it, search for an available storage location adjacent to the target end position, and the searched storage location can be used as the task end point of the newly generated test task. In this way, it can be guaranteed that starting from the target starting position, a docking test is performed on a storage location each time, and the test is traversed in sequence to the target end position, achieving full coverage of the target test area.

[0064] Searching for adjacent available storage locations can be implemented based on the search rules set by the staff. Specifically, starting from the task starting point, traversing to the last storage location of the target test area, that is, the target end position, in the order of layer, column, row, and lane, the first available storage location traversed is the available storage location adjacent to the first end position. That is, the location of the storage location is represented by the coordinates composed of the layer number, row number, column number, and lane number, and the first storage location is the storage location with the smallest coordinate value, and the last storage location is the storage location with the largest coordinate value. Add one to the coordinate value corresponding to the storage location at the starting point of the task, and determine whether the storage location corresponding to the accumulated coordinate value is available. If it is available, the storage location is determined to be the end point of the task. Otherwise, continue to accumulate the coordinate value. In the process of accumulation, that is, layer, column, row, and lane are equivalent to digits from low to high. Taking the layer as an example, when the layer reaches the maximum value, it continues to add one, then the value of the layer returns to the minimum value, and the value of the column will increase by one. Taking specific values ​​as an example, if the maximum number of layers is 20, and the current task starting point is layer 20, column 5, row 8, lane 2, then when the accumulation is performed, the result is layer 1, column 6, row 8, lane 2.

[0065] (4) Generate a test task based on the task start point and task end point.

[0066] That is, the target stacker will start from the task starting point and go to the task end point for docking test. In order to set the test task more flexibly, other parameters can also be read from the task configuration table when generating the test task. Specifically, the task configuration table can also include at least one parameter for indicating whether the test is loaded, the test task type, the test exception handling method, and the alarm manual intervention threshold. Among them, whether the test is loaded is used to set whether the target stacker carries goods during the test. The test task type is used to set the specific actions of the target stacker during the docking test. The test exception handling method is used to set the control method of the target stacker when an abnormality occurs during the docking test, such as leaving the pallet in the warehouse, sending the pallet to the inbound terminal or the outbound terminal, and continuing to execute the test task. The alarm manual intervention threshold is used to set the upper limit of the alarm when the target stacker has an equipment failure. When the upper limit is exceeded, the target stacker will stop moving and manual intervention is required to solve it.

[0067] In one embodiment, determining whether the target stacker has performed docking tests on all available storage locations in the target test area includes:

[0068] (1) Determine whether the first end position matches the target end position in the task configuration table. The target end position is the position of the last available storage location in the target test area.

[0069] It can be understood that in the above-mentioned test idea of ​​traversing the entire target test area, the sign of the end of the test is that the target end position has been traversed when the test task is completed. Therefore, the end point when the previous test task is completed, that is, the first end position, can be compared with the target end position to determine whether the traversal of the target test area has been completed.

[0070] (2) If so, it is determined that the target stacker has completed docking testing for all available storage locations in the target test area.

[0071] (3) If not, it is determined that the target stacker has not completed the docking test for all available storage locations in the target test area.

[0072] In one embodiment, see Figure 2 The stacker and storage location docking test method includes steps S202 to S210.

[0073] S202, obtaining the current state of the target stacker.

[0074] S204, when the current state is idle and the target stacker has not completed the docking test on all available storage locations in the target test area, a new test task is generated and sent to the target stacker, so that the target stacker performs a docking test on the next available storage location in the target test area, and returns to the step of obtaining the current state of the target stacker to continue execution.

[0075] The description of step S202 and step S204 may refer to the description of step S102 and step S104 above.

[0076] S206, when the current state is an idle state and the target stacker completes the docking test on all available storage locations in the target test area, obtain a parameter value of a parameter in the task configuration table that is used to reflect whether to restart the test.

[0077] It is understandable that in some cases, it is manually determined that there are abnormalities in the test process of the target test area and retesting is required. At this time, the task configuration table may also include a parameter for indicating whether the test needs to be restarted. If the parameter value reflects yes, the task table will be recreated or the original task table will be initialized, and the next test task will be used as the first test task of the target test area, starting from the original target starting position, and docking tests will be performed on one storage location each time, traversing in sequence to the target end position, and re-testing the full coverage of the target test area. If the parameter value reflects no, all task execution information uploaded by the target stacker when executing the test tasks related to the target test area can be summarized and processed to generate a test report.

[0078] S208: If the parameter value reflects yes, return to obtain the current state of the target stacker and restart the docking test on the target test area.

[0079] S210, if the parameter value reflects no, then generating a test report according to the task execution information uploaded when the target stacker completes the test task related to the target test area.

[0080] The present application provides a stacker and storage location docking test device, including a data acquisition module, a task generation module and a report generation module. The data acquisition module is used to obtain the current state of the target stacker. The task generation module is used to generate a new test task and send it to the target stacker when the current state is an idle state and the target stacker has not completed the docking test on all available storage locations in the target test area, so that the target stacker performs a docking test on the next available storage location in the target test area, and returns to the step of obtaining the current state of the target stacker to continue execution. When the target stacker completes a test task, it will upload the task execution information. The report generation module is used to generate a test report based on the task execution information uploaded when the target stacker completes the test tasks related to the target test area when the current state is an idle state and the target stacker completes the docking test on all available storage locations in the target test area.

[0081] For the specific definition of the stacker and storage location docking test device, please refer to the definition of the stacker and storage location docking test method mentioned above, which will not be repeated here. Each module in the above-mentioned stacker and storage location docking test device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0082] The present application provides a stacker and storage location docking test system, including a host computer and multiple stackers, the host computer is communicatively connected with each stacker, the host computer includes one or more processors, and a memory, the memory stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the steps of the stacker and storage location docking test method described in any of the above embodiments are executed.

[0083] Indicatively, if Figure 3 As shown, Figure 3 This is a schematic diagram of the internal structure of the host computer provided in the embodiment of the present application. Figure 3 The host computer 300 includes a processing component 302, which further includes one or more processors, and a memory resource represented by a memory 301, which is used to store instructions that can be executed by the processing component 302, such as an application. The computer device can be used as a processing core in an access control device, or as an operating carrier of a system platform. The application stored in the memory 301 can include one or more modules, each corresponding to a set of instructions. In addition, the processing component 302 is configured to execute instructions to execute the steps of the stacker and storage location docking test method of any of the above embodiments.

[0084] The host computer 300 may further include a power supply component 303 configured to perform power management of the host computer 300 , a wired or wireless network interface 304 configured to connect the computer device 300 to a network, and an input / output (I / O) interface 305 .

[0085] The present application provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the stacker and storage location docking test method as described in any of the above embodiments.

[0086] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0087] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can refer to each other.

[0088] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for testing the docking of a stacker and a storage location, characterized in that: include: Get the current status of the target stacker; When the current state is an idle state and the target stacker has not completed docking tests on all available storage locations in the target test area, a new test task is generated and sent to the target stacker, so that the target stacker performs a docking test on the next available storage location in the target test area, and returns to the step of obtaining the current state of the target stacker to continue execution; when the target stacker completes one of the test tasks, it uploads task execution information; When the current state is an idle state and the target stacker completes the docking test on all the available storage locations in the target test area, a test report is generated according to the task execution information uploaded when the target stacker completes the test task related to the target test area.

2. The method for testing the docking between a stacker and a storage location according to claim 1, characterized in that: The generating of a new test task includes: If the target stacker has not been tested in the target test area, the target starting position in the task configuration table is used as the task starting point; the target starting position is the position of the first available storage location in the target test area; Otherwise, the first end position is used as the starting point of the task; the first end position is the end position of the previous test task of the target stacker; Searching for the available storage location adjacent to the task starting point in the target test area, and using the searched available storage location as the task end point; The test task is generated according to the task starting point and the task end point.

3. The method for testing the docking between a stacker and a storage location according to claim 2, characterized in that: Determining whether the target stacker has performed docking tests on all available storage locations in the target test area includes: Determine whether the first end position matches the target end position in the task configuration table; the target end position is the position of the last available storage location in the target test area; If yes, it is determined that the target stacker has completed docking testing for all the available storage locations in the target test area; If not, it is determined that the target stacker has not completed the docking test on all the available storage locations in the target test area.

4. The method for testing the docking between a stacker and a storage location according to claim 2, characterized in that: Generating the test task according to the task starting point and the task end point includes: The test task is generated according to the task configuration table, the task starting point and the task end point; the task configuration table also includes at least one parameter for indicating whether to carry cargo for the test, the test task type, the test exception handling method, and the alarm manual intervention threshold.

5. The method for testing the docking between a stacker and a storage location according to claim 2, characterized in that: The searching the available storage location adjacent to the first end position in the target testing area includes: Starting from the task starting point, traverse to the last storage location of the target test area in the order of layer, column, row, and lane, so that the first available storage location traversed is the available storage location adjacent to the first end position.

6. The method for testing the docking between a stacker and a storage location according to claim 1, characterized in that: When the current state is an idle state and the target stacker completes the docking test for all the available storage locations in the target test area, a test report is generated according to each task execution information uploaded when the target stacker completes the test task related to the target test area, including: When the current state is an idle state and the target stacker completes the docking test on all the available storage locations in the target test area, obtaining a parameter value of a parameter in the task configuration table for reflecting whether to restart the test; If the parameter value reflects yes, returning to the step of obtaining the current state of the target stacker and restarting the docking test on the target test area; If the parameter value reflects a negative value, a test report is generated according to the task execution information uploaded when the target stacker completes the test task related to the target test area.

7. The method for testing the docking between a stacker and a storage location according to claim 1, characterized in that: After obtaining the current state of the target stacker, the method further includes: When the current state is the executing state, the current position of the target stacker is recorded.

8. A stacker and storage location docking test device, characterized in that: include: A data acquisition module is used to obtain the current status of the target stacker; The task generation module is used to generate a new test task when the current state is an idle state and the target stacker has not completed the docking test for all available storage locations in the target test area, and send it to the target stacker, so that the target stacker performs the docking test on the next available storage location in the target test area, and returns to the step of obtaining the current state of the target stacker to continue execution; when the target stacker completes one of the test tasks, it will upload the task execution information; A report generation module is used to generate a test report based on the task execution information uploaded when the target stacker completes the test task related to the target test area, when the current state is an idle state and the target stacker completes the docking test on all the available storage locations in the target test area.

9. A stacker and storage location docking test system, characterized in that: The system comprises a host computer and a plurality of stackers, wherein the host computer is communicatively connected with each of the stackers, the host computer comprises one or more processors, and a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the one or more processors, the steps of the stacker and storage location docking test method as described in any one of claims 1 to 7 are executed.

10. A storage medium, characterized in that: The storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of the stacker and storage location docking test method as described in any one of claims 1 to 7.

Images