Stacker-reclaimer multitasking operation control method and device, electronic equipment and program

Abstract

The present disclosure relates to a kind of reclaimer multitasking operation control method, device, electronic equipment and program, the method comprises: when receiving the first execution instruction of first task, the execution state of multiple tasks in task list is obtained, execution state includes one of waiting, pause, running and stop, and first task is contained in task list;When the second task of execution state being running is contained in multiple tasks, the execution state of second task is changed to waiting or pause;After the execution state of second task is changed, the task data of first task is obtained according to the first execution instruction of received first task;According to the task data of first task, the operation of reclaimer is controlled, and task data includes one or more of task start position, task end position, task type.It can avoid the tedious operation of frequent operation personnel to issue operation task, while reducing the workload of operator, and reduce the security risk of reclaimer operation.

Description

Technical Field

[0001] This disclosure relates to the field of operation task control systems for circular coal yard stacker-reclaimers, specifically to a multi-task operation control method, apparatus, electronic equipment, and program for stacker-reclaimers. Background Technology

[0002] In existing technologies, coal yard material handling and relocation operations can be performed in two ways: one is manual operation by maintenance personnel on-site, moving the reclaiming boom from the current coal pile working face to a specific pile or point where material needs to be reclaimed; the other is remote issuance of reclaiming tasks via a programmable controller (PCC), which automatically moves the reclaimer from the current coal pile working face to the specific pile or point where material needs to be reclaimed. Currently, the PCC operating system only allows one task to be issued at a time. When changing piles or reclaiming locations, the current task must be terminated before a new task can be issued. Due to the tight coal supply and rising coal prices in recent years, the actual coal arriving at the coal yard differs significantly from the boiler's design coal type. Problems such as mixed coal mine locations, fluctuating coal quality and type have become common. To ensure boiler combustion safety and meet unit load requirements, multiple different types of coal need to be blended within the coal yard. The large number of coal types retrieved per shift increases the complexity of frequent task issuance by maintenance personnel, increasing their workload and operational safety risks. This is a problem that urgently needs to be solved. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides a multi-task operation control method, device, electronic equipment and program for a stacker-reclaimer.

[0004] According to a first aspect of the present disclosure, a multi-task operation control method for a stacker-reclaimer is provided, comprising: When the first execution instruction of the first task is received, the execution status of multiple tasks in the task list is obtained. The execution status includes one of waiting, paused, running and stopped. The task list includes the first task. When the plurality of tasks includes a second task whose execution status is running, the execution status of the second task is changed to waiting or paused; When the execution status of the second task changes, the task data of the first task is obtained according to the first execution instruction received from the first task; Based on the task data of the first task, the operation of the stacker-reclaimer is controlled. The task data includes one or more of the following: task start position, task end position, and task type.

[0005] Optionally, the method further includes: When the execution status of multiple tasks in the task list is not running, the task data of the first task is obtained according to the first execution instruction received from the first task. The operation of the stacker-reclaimer is controlled based on the task data of the first task.

[0006] Optionally, when the plurality of tasks includes a second task whose execution state is running, changing the execution state of the second task to waiting or paused includes: Obtain the task type of the second task, and change the execution status of the second task according to the task type of the second task. The changed execution status of the second task includes one of waiting and pausing. Update the execution status of the second task to the database after the change.

[0007] Optionally, updating the execution status of the modified second task to the database includes: The modified execution status of the second task is sent to the backend server via the transmission control protocol, so that the backend server updates the modified execution status of the second task to the database and displays the execution status of the second task in the task display bar.

[0008] Optionally, the step of obtaining the task type of the second task and changing the execution state of the second task according to the task type of the second task, wherein the changed execution state of the second task includes one of waiting and paused, including: Obtain the task type of the second task, wherein the task type includes one of stacking, retrieving, and scanning; When the task type of the second task is the same as the task type of the first task received, the execution status of the second task is changed to waiting; When the task type of the second task is different from the task type of the first task received, the execution status of the second task is changed to paused.

[0009] Optionally, obtaining the task data of the first task according to the received first execution instruction of the first task includes: Receive the first execution instruction; According to the first execution instruction, obtain the task ID of the first task; Based on the task ID of the first task, the task data of the first task is obtained from the database. The task data includes one or more of the following: task start position, task end position, and task type.

[0010] Optionally, controlling the operation of the stacker-reclaimer based on the task data of the first task includes: Based on the task data of the first task and the current operating position of the stacker-reclaimer, the moving direction and working position of the stacker-reclaimer are determined, and the moving direction and working position of the stacker-reclaimer are sent to the backend server through a transmission control protocol, so that the backend server can store the moving direction and working position of the stacker-reclaimer in the database and control the operation of the stacker-reclaimer.

[0011] Optionally, the step of sending the movement direction and working position of the stacker-reclaimer to the backend server via a transmission control protocol, so that the backend server stores the movement direction and working position of the stacker-reclaimer in the database, includes: The movement direction and working position of the stacker-reclaimer are sent to the backend server via a transmission control protocol. When the backend server receives the second execution instruction, it determines the current task data of the stacker-reclaimer based on the received movement direction and working position, inserts the current task data of the stacker-reclaimer into the database using an intelligent sorting method, generates the task data and task ID of the third task, and displays the task ID and execution status of the third task in the task display bar. The second execution instruction is the execution instruction for the stacker-reclaimer to run according to the movement direction and working position.

[0012] Optionally, the method further includes: When the stacker-reclaimer completes the first task and does not receive a new task execution instruction, the execution status of the second task is changed to running through the background server, and the stacker-reclaimer is controlled to continue executing the second task. The changed execution status of the second task is stored in the database, and the execution status of the second task is displayed as running in the task display bar.

[0013] According to a second aspect of the present disclosure, a multi-task operation control device for a stacker-reclaimer is provided, comprising: The first acquisition module is used to acquire the execution status of multiple tasks in the task list when a first execution instruction of the first task is received. The execution status includes one of waiting, paused, running and stopped. The task list includes the first task. The change module is used to change the execution status of the second task to waiting or paused when the plurality of tasks includes a second task whose execution status is running. The second acquisition module is used to acquire the task data of the first task according to the first execution instruction received from the first task when the execution status of the second task changes; The control module is used to control the operation of the stacker-reclaimer according to the task data of the first task, wherein the task data includes one or more of the following: task start position, task end position, and task type.

[0014] According to a third aspect of the present disclosure, a non-transitory computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the steps of the stacker-reclaimer multitasking operation control method described in the first aspect of the present disclosure.

[0015] According to a fourth aspect of the present disclosure, an electronic device is provided, comprising: A memory on which computer programs are stored; A processor is configured to execute the computer program in the memory to implement the steps of the stacker-reclaimer multitasking operation control method according to the first aspect of the present disclosure.

[0016] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the stacker-reclaimer multitasking operation control method described in the first aspect of the present disclosure.

[0017] In the above technical solution, when a first execution instruction for a first task is received, the execution status of multiple tasks in a task list is obtained. The execution status includes one of waiting, paused, running, and stopped. The task list includes the first task. When the multiple tasks include a second task whose execution status is running, the execution status of the second task is changed to waiting or paused. After the execution status of the second task changes, the task data of the first task is obtained according to the first execution instruction received from the first task. The operation of the stacker-reclaimer is controlled according to the task data of the first task. The task data includes one or more of the following: task start position, task end position, and task type. Through the above technical solution, upon receiving the first task execution instruction for the first task, the execution status of the second task is determined to be running based on the execution status of multiple tasks in the obtained task list. The execution status of the running second task is then changed, and the task data of the first task is determined based on the received first execution instruction for the first task. The operation of the stacker-reclaimer is then controlled based on the task data of the first task. This allows the stacker-reclaimer to be controlled based on the task execution instructions and the task execution status in the task list, avoiding the tedious operation of frequent task issuance by maintenance personnel during the operation of the stacker-reclaimer, reducing the workload of operators, and simultaneously reducing the safety risks of stacker-reclaimer operation.

[0018] Other features and advantages of this disclosure will be described in detail in the following detailed description section. Attached Figure Description

[0019] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the following detailed description to explain the present disclosure, but do not constitute a limitation thereof. In the drawings: Figure 1 This is a flowchart illustrating a multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment.

[0020] Figure 2 This is a flowchart illustrating another stacker-reclaimer multitasking operation control method according to an exemplary embodiment.

[0021] Figure 3 This is a flowchart illustrating another stacker-reclaimer multitasking operation control method according to an exemplary embodiment.

[0022] Figure 4 This is a flowchart illustrating yet another stacker-reclaimer multitasking operation control method according to an exemplary embodiment.

[0023] Figure 5 This is a flowchart illustrating yet another stacker-reclaimer multitasking operation control method according to an exemplary embodiment.

[0024] Figure 6 This is a flowchart illustrating a multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment.

[0025] Figure 7 This is a block diagram illustrating a multi-task operation control device for a stacker-reclaimer according to an exemplary embodiment.

[0026] Figure 8 This is a block diagram illustrating an electronic device 800 according to an exemplary embodiment.

[0027] Figure 9 This is a block diagram illustrating an electronic device 900 according to an exemplary embodiment. Detailed Implementation

[0028] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure.

[0029] It is understood that the terms "first," "second," etc., used in this disclosure are used to describe various types of information, but such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another and do not indicate a particular order or degree of importance.

[0030] It is further understood that although operations are described in a specific order in the accompanying drawings in the embodiments of this disclosure, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the shown operations to be performed to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0031] The actual coal supplied to the coal yard differs significantly from the coal type designed for the boiler. Issues such as mixed coal mine locations, fluctuating coal quality and type have become common. To ensure boiler combustion safety and meet unit load requirements, it is necessary to blend multiple different types of coal within the coal yard. Each shift involves a large variety of coal types being retrieved. However, current technology only allows one task to be issued at a time by the programmable logic controller (PLC). If a change of stacker or reclaiming location is required, the currently executing task must be terminated, and a new task must be issued. Because of the large variety of coal types retrieved per shift, maintenance personnel need to frequently issue tasks, increasing their workload and labor costs, while also posing operational safety risks. To address these issues, a multi-task operation control method for stacker-reclaimers is proposed, which is described below.

[0032] Figure 1 This is a flowchart illustrating a multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 1 As shown, the method includes: In step S11, when the first execution instruction of the first task is received, the execution status of multiple tasks in the task list is obtained. The execution status includes one of waiting, paused, running and stopped. The task list contains the first task.

[0033] In step S12, when the plurality of tasks includes a second task whose execution status is running, the execution status of the second task is changed to waiting or paused.

[0034] In step S13, after the execution status of the second task changes, the task data of the first task is obtained according to the first execution instruction received from the first task.

[0035] In step S14, the operation of the stacker-reclaimer is controlled according to the task data of the first task. The task data includes one or more of the following: task start position, task end position, and task type.

[0036] For example, a multi-task operation control function is added to the stacker-reclaimer operation task control system. Tasks in different areas can be viewed in the task list. The operator selects the first task from the task list to execute. The backend server assembles the task data of the first task into a data packet in JSON (JavaScript Object Notation) format. Then, according to a transmission control protocol such as TCP (Transmission Control Protocol), the task data packet of the first task is sent to the backend server. When the backend server receives the first execution instruction for the first task, it obtains the execution status of multiple tasks in the task list. This execution status includes one of waiting, paused, running, and stopped. If a second task with a running execution status is included among these multiple tasks, its execution status is changed to waiting or paused according to its task type. After the execution status of the second task changes, the task data of the first task is obtained according to the received first execution instruction. Based on the task data of the first task, the operation of the stacker-reclaimer is controlled. This task data includes one or more of the following: task start position, task end position, and task type. For example, if the task list contains Task 1 and Task 2, when the maintenance personnel select Task 1 to execute, the backend server will receive information that the stacker-reclaimer is currently running Task 2. Based on the task type of Task 2, the server will change the execution status of Task 2 to "waiting" or "paused," and control the operation of the stacker-reclaimer based on the task data of Task 1. This allows the server to control the operation of the stacker-reclaimer according to the task execution instructions and the task execution status in the task list, avoiding the tedious operation of frequently issuing work tasks during the operation of the stacker-reclaimer and reducing the workload of the operators.

[0037] Among these execution states, "Waiting" indicates that the task is in a non-execution state and requires manual execution by the operator; "Pause" indicates that the operating mechanism of the equipment, such as pitch and rotation, has been stopped, and the task program will maintain the current steps of the task execution. When "Continue" is clicked, the task will continue from the steps at the time of the pause; "Run" indicates that the equipment is executing the task and will execute it step by step according to the task steps; and "Stop" indicates that the operating mechanism of the equipment, such as pitch and rotation, has been stopped, and the current task has ended.

[0038] Through the above technical solution, upon receiving the first task execution instruction for the first task, the execution status of the second task is determined to be running based on the execution status of multiple tasks in the obtained task list. The execution status of the running second task is then changed, and the task data of the first task is determined based on the received first execution instruction for the first task. The operation of the stacker-reclaimer is then controlled based on the task data of the first task. This allows the stacker-reclaimer to be controlled based on the task execution instructions and the task execution status in the task list, avoiding the tedious operation of frequent task issuance by maintenance personnel during the operation of the stacker-reclaimer, reducing the workload of operators, and simultaneously reducing the safety risks of stacker-reclaimer operation.

[0039] Figure 2 This is a flowchart illustrating another multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 2 As shown, the method also includes: In step S15, when the execution status of multiple tasks in the task list is not running, the task data of the first task is obtained according to the first execution instruction of the first task received.

[0040] In step S16, the operation of the stacker-reclaimer is controlled according to the task data of the first task.

[0041] For example, when an operations and maintenance (O&M) personnel select to execute the first task in the task list, and the backend server receives the first execution instruction for the first task, it obtains the execution status of multiple tasks in the task list. If the execution status of multiple tasks in the task list is all non-running (this non-running execution status includes one of waiting, paused, and stopped), the server obtains the task data of the first task based on the received first execution instruction. Based on the task data of the first task, the operation of the stacker-reclaimer is controlled. For example, if the task list contains task 1 and task 2, and the O&M personnel select task 1 for execution, but the backend server does not find any currently running tasks on the stacker-reclaimer, then the operation of the stacker-reclaimer is controlled based on the task data of task 1. This allows the stacker-reclaimer to be controlled based on the task execution instructions and the task execution status in the task list, avoiding the tedious operation of frequently issuing work tasks during the operation of the stacker-reclaimer and reducing the workload of the operators.

[0042] Optionally, the method further includes: When the stacker-reclaimer completes the first task and does not receive a new task execution instruction, the execution status of the second task is changed to running through the backend server, and the stacker-reclaimer is controlled to continue executing the second task. The changed execution status of the second task is stored in the database, and the execution status of the second task is displayed as running in the task display bar.

[0043] For example, if the maintenance personnel select to execute the first task in the task list, and the stacker-reclaimer completes the first task but the maintenance personnel do not issue a new task execution instruction, the backend server changes the execution status of the second task to "running," stores the changed execution status of the second task in the database, and displays the execution status of the second task as "running" in the task display bar. That is, the execution status of the second task in the task list is changed to "running." It can be understood that if the maintenance personnel still do not issue a new task execution instruction after the second task is completed, the backend server will execute the tasks in the task list in the order set by the maintenance personnel, avoiding the tedious operation of the maintenance personnel having to frequently issue work tasks and reducing the workload of the operators.

[0044] Figure 3 This is a flowchart illustrating another multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 3 As shown, step S12 includes: In step S121, the task type of the second task is obtained, and the execution status of the second task is changed according to the task type. The changed execution status of the second task includes one of waiting and pausing.

[0045] In step S122, the execution status of the modified second task is updated to the database.

[0046] For example, when the execution status of the second task is running, the task type of the second task is obtained, which includes one of stacking, picking and scanning. The execution status of the second task is changed according to the task type. The changed execution status of the second task includes one of waiting and pausing. The changed execution status of the second task is updated to the database to facilitate random and flexible calls by on-site maintenance personnel.

[0047] Optionally, step S122 includes: The modified execution status of the second task is sent to the backend server via the transmission control protocol, so that the backend server updates the database with the modified execution status of the second task and displays the execution status of the second task in the task display bar.

[0048] For example, when the execution status of the second task changes to either waiting or paused, the changed execution status of the second task is sent to the backend server via TCP communication. The backend server updates the changed execution status of the second task to the database and displays the execution status of the second task in the task display bar. That is, the execution status of the second task in the task list changes to paused or waiting, which is convenient for on-site maintenance personnel to call it randomly and flexibly.

[0049] Figure 4 This is a flowchart illustrating yet another multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 4 As shown, step S121 includes: In step S1211, the task type of the second task is obtained, which includes one of stacking, picking, and scanning.

[0050] In step S1212, when the task type of the second task is the same as the task type of the received first task, the execution status of the second task is changed to waiting.

[0051] In step S1213, when the task type of the second task is different from the task type of the received first task, the execution status of the second task is changed to paused.

[0052] For example, when an operations and maintenance personnel selects to execute the first task in the task list, and a second task in the task list is found to be running, the task type of the second task is obtained. This task type includes one of stacking, picking, and scanning. When the task type of the second task is the same as the task type of the first task received, the execution status of the second task is changed to waiting. When the task type of the second task is different from the task type of the first task received, the execution status of the second task is changed to paused. For example, if an operations and maintenance personnel selects to execute task 1, and task 2 in the task list is currently running, the task type of task 2 is obtained. If the task type of task 2 is stacking, and the task type of task 1 is also stacking, the execution status of task 2 is changed to waiting. If the task type of task 1 is not waiting, the execution status of task 2 is changed to paused.

[0053] Figure 5 This is a flowchart illustrating yet another multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 5 As shown, step S13 or step S15 includes: In step S131, the first execution instruction is received.

[0054] In step S132, the task ID of the first task is obtained according to the first execution instruction.

[0055] In step S133, the task data of the first task is obtained from the database according to the task ID of the first task. The task data includes one or more of the following: task start position, task end position, and task type.

[0056] For example, when an operations and maintenance personnel selects to execute the first task in the task list, the backend server receives the first execution instruction for the first task. Based on the first execution instruction, it obtains the task type of the first task and iterates through the task list according to the task type. After the iteration, it records the tasks of the same type that are currently being executed and stores them in memory. The tasks recorded in memory are assembled into task data packets one by one and sent to the backend server one by one. The backend server adopts a write-through caching strategy. After receiving the task data packets, it parses them one by one. After parsing, it obtains the task ID of each task, iterates through the task threads according to the task ID, terminates the task thread and releases the corresponding memory resources, and then updates the task status to waiting according to the task ID. Based on the task ID of the first task, it parses the task data packet of the first task from the database and obtains the task data of the first task. The task data includes one or more of the following: task start position, task end position, and task type.

[0057] Optionally, step S14 or step S16 includes: Based on the task data of the first task and the current operating position of the stacker-reclaimer, the moving direction and working position of the stacker-reclaimer are determined, and the moving direction and working position of the stacker-reclaimer are sent to the back-end server through the transmission control protocol, so that the back-end server can store the moving direction and working position of the stacker-reclaimer in the database and control the operation of the stacker-reclaimer.

[0058] For example, the task data of the first task includes the task start position and the task end position of the first task. Based on the task start position and the task end position of the first task and the current running position of the stacker-reclaimer, the movement direction and working position of the stacker-reclaimer are determined. The working position is the current start position and end position of the stacker-reclaimer. The movement direction and working position of the stacker-reclaimer are sent to the backend server via TCP communication. The backend server stores the movement direction and working position of the stacker-reclaimer in the database. The backend server controls the operation of the stacker-reclaimer based on the movement direction and working position.

[0059] Optionally, step S14 or step S16 includes: The movement direction and working position of the stacker-reclaimer are sent to the backend server via a transmission control protocol. When the backend server receives the second execution instruction, it determines the current task data of the stacker-reclaimer based on the received movement direction and working position, and inserts the current task data of the stacker-reclaimer into the database using an intelligent sorting method. This generates the task data and task ID of the third task, and displays the task ID and execution status of the third task in the task display bar. The second execution instruction is the execution instruction for the stacker-reclaimer to run according to the movement direction and working position.

[0060] For example, the working position is the current start and end position of the stacker-reclaimer. The movement direction and working position of the stacker-reclaimer are sent to the backend server via TCP communication. Based on the movement direction and working position of the stacker-reclaimer, the current task data of the stacker-reclaimer is determined. When the backend server receives the second execution instruction, it inserts the current task data of the stacker-reclaimer into the database using an intelligent sorting method, generates the task data and task ID of the third task, and displays the task ID and execution status of the third task in the task display bar. The second execution instruction is the execution instruction for the stacker-reclaimer to run according to the movement direction and working position.

[0061] Through the above technical solution, upon receiving the first task execution instruction for the first task, the execution status of the second task is determined to be running based on the execution status of multiple tasks in the obtained task list. The execution status of the running second task is then changed, and the task data of the first task is determined based on the received first execution instruction for the first task. The operation of the stacker-reclaimer is then controlled based on the task data of the first task. This allows the stacker-reclaimer to be controlled based on the task execution instructions and the task execution status in the task list, avoiding the tedious operation of frequent task issuance by maintenance personnel during the operation of the stacker-reclaimer, reducing the workload of operators, and simultaneously reducing the safety risks of stacker-reclaimer operation.

[0062] Figure 6 This is a flowchart illustrating a multi-task operation control method for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 6 As shown, when the stacker-reclaimer performs multi-task switching: Step S1: Check if any tasks are running in the task list; When the task list contains Task 1 that is currently running: Step S2: Switch the task status of Task 1 to waiting and send it to the background server via TCP communication; Step S3: Update the modified task status of Task 1 to the database; Step S4: The updated task status is displayed in the task status bar; Step S5: Obtain the task ID of task 2; Step S6: Retrieve the task data corresponding to the task ID from the database; Step S7: Calculate the moving direction and working position of the stacker-reclaimer based on the task data of Task 2 in the database; Step S8: Receive the second instruction issued by the operations and maintenance personnel; Step S9: Send the second instruction to the backend server via TCP communication to control the execution of the instruction; Step S10: Save the task data to the database; Step S11: Control the stacker-reclaimer to execute the task according to the task data.

[0063] When the task list does not contain a running task 1: Step S5: Obtain the task ID of task 2; Step S6: Retrieve the task data corresponding to the task ID from the database; Step S7: Calculate the moving direction and working position of the stacker-reclaimer based on the task data of Task 2 in the database; Step S8: Receive the second instruction issued by the operations and maintenance personnel; Step S9: Send the second instruction to the backend server via TCP communication to control the execution of the instruction; Step S10: Save the task data to the database; Step S11: Control the stacker-reclaimer to execute the task according to the task data.

[0064] Figure 7 This is a block diagram illustrating a multi-task operation control device for a stacker-reclaimer according to an exemplary embodiment, such as... Figure 7 As shown, the stacker-reclaimer multi-task operation control device 700 includes: a first acquisition module 701, a change module 702, a second acquisition module 703, and a control module 704.

[0065] The first acquisition module 701 is used to acquire the execution status of multiple tasks in the task list when a first execution instruction of the first task is received. The execution status includes one of waiting, paused, running and stopped. The task list contains the first task. The change module 702 is used to change the execution status of the second task to waiting or paused when the multiple tasks include a second task whose execution status is running. The second acquisition module 703 is used to acquire the task data of the first task according to the first execution instruction of the first task received after the execution status of the second task changes; The control module 704 is used to control the operation of the stacker-reclaimer according to the task data of the first task, the task data including one or more of the following: task start position, task end position, and task type.

[0066] Optionally, the device further includes a third acquisition module and a first control module.

[0067] The third acquisition module is used to acquire the task data of the first task based on the first execution instruction received from the first task when the execution status of multiple tasks in the task list is not running. The first control module is used to control the operation of the stacker-reclaimer based on the task data of the first task.

[0068] Optionally, the change module 702 includes: a first change submodule and a first update submodule.

[0069] The first modification submodule is used to obtain the task type of the second task and change the execution status of the second task according to the task type. The changed execution status of the second task includes one of waiting and pausing. The first update submodule is used to update the execution status of the second task after the change to the database.

[0070] Optionally, this first update submodule is used for: The modified execution status of the second task is sent to the backend server via the transmission control protocol, so that the backend server updates the database with the modified execution status of the second task and displays the execution status of the second task in the task display bar.

[0071] Optionally, the first change submodule includes: a first acquisition submodule, a first state change submodule, and a second state change submodule.

[0072] The first acquisition submodule is used to acquire the task type of the second task, which includes one of stacking, picking and scanning. The first state change submodule is used to change the execution state of the second task to waiting when the task type of the second task is the same as the task type of the first task received. The second state change submodule is used to change the execution state of the second task to pause when the task type of the second task is different from the task type of the first task received.

[0073] Optionally, the second acquisition module 703 or the third acquisition module includes: a first receiving submodule, a second acquisition submodule and a third acquisition submodule.

[0074] The first receiving submodule is used to receive the first execution instruction; The second acquisition submodule is used to acquire the task ID of the first task according to the first execution instruction; The third acquisition submodule is used to retrieve the task data of the first task from the database based on the task ID of the first task. The task data includes one or more of the following: task start position, task end position, and task type.

[0075] Optionally, the control module 704 or the first control module is further configured to: Based on the task data of the first task and the current operating position of the stacker-reclaimer, the moving direction and working position of the stacker-reclaimer are determined, and the moving direction and working position of the stacker-reclaimer are sent to the back-end server through the transmission control protocol, so that the back-end server can store the moving direction and working position of the stacker-reclaimer in the database and control the operation of the stacker-reclaimer.

[0076] Optionally, the control module 704 or the first control module is further configured to: The movement direction and working position of the stacker-reclaimer are sent to the backend server via a transmission control protocol. When the backend server receives the second execution instruction, it determines the current task data of the stacker-reclaimer based on the received movement direction and working position, and inserts the current task data of the stacker-reclaimer into the database using an intelligent sorting method. This generates the task data and task ID of the third task, and displays the task ID and execution status of the third task in the task display bar. The second execution instruction is the execution instruction for the stacker-reclaimer to run according to the movement direction and working position.

[0077] Optionally, the device further includes a second modification module.

[0078] When the stacker-reclaimer completes the first task and does not receive a new task execution instruction, the execution status of the second task is changed to running through the backend server, and the stacker-reclaimer is controlled to continue executing the second task. The changed execution status of the second task is stored in the database, and the execution status of the second task is displayed as running in the task display bar.

[0079] Through the above technical solution, upon receiving the first task execution instruction for the first task, the execution status of the second task is determined to be running based on the execution status of multiple tasks in the obtained task list. The execution status of the running second task is then changed, and the task data of the first task is determined based on the received first execution instruction for the first task. The operation of the stacker-reclaimer is then controlled based on the task data of the first task. This allows the stacker-reclaimer to be controlled based on the task execution instructions and the task execution status in the task list, avoiding the tedious operation of frequent task issuance by maintenance personnel during the operation of the stacker-reclaimer, reducing the workload of operators, and simultaneously reducing the safety risks of stacker-reclaimer operation.

[0080] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0081] Figure 8 This is a block diagram illustrating an electronic device 800 according to an exemplary embodiment. For example... Figure 8 As shown, the electronic device 800 may include a processor 801 and a memory 802. The electronic device 800 may also include one or more of a multimedia component 803, an input / output (I / O) interface 804, and a communication component 805.

[0082] The processor 801 controls the overall operation of the electronic device 800 to complete all or part of the steps in the aforementioned stacker-reclaimer multi-task operation control method. The memory 802 stores various types of data to support the operation of the electronic device 800. This data may include, for example, instructions for any application or method operating on the electronic device 800, and application-related data such as contact data, sent and received messages, images, audio, video, etc. The memory 802 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. Multimedia component 803 may include a screen and an audio component. The screen may be, for example, a touchscreen, and the audio component is used to output and / or input audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signals may be further stored in memory 802 or transmitted via communication component 805. The audio component also includes at least one speaker for outputting audio signals. I / O interface 804 provides an interface between processor 801 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual or physical buttons. Communication component 805 is used for wired or wireless communication between the electronic device 800 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, NB-IoT, eMTC, or other 5G technologies, or combinations thereof, is not limited here. Therefore, the corresponding communication component 805 may include: a Wi-Fi module, a Bluetooth module, an NFC module, etc.

[0083] In an exemplary embodiment, the electronic device 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to execute the aforementioned stacker-reclaimer multi-task operation control method.

[0084] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the stacker-reclaimer multitasking operation control method described above. For example, the computer-readable storage medium may be the memory 802 including program instructions, which may be executed by the processor 801 of the electronic device 800 to complete the stacker-reclaimer multitasking operation control method described above.

[0085] Figure 9 This is a block diagram illustrating an electronic device 900 according to an exemplary embodiment. For example, the electronic device 900 may be provided as a server. (Refer to...) Figure 9 The electronic device 900 includes a processor 922, which may be one or more, and a memory 932 for storing computer programs executable by the processor 922. The computer program stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processor 922 may be configured to execute the computer program to perform the aforementioned stacker-reclaimer multitasking operation control method.

[0086] Additionally, the electronic device 900 may also include a power supply component 926 and a communication component 950. The power supply component 926 can be configured to perform power management of the electronic device 900, and the communication component 950 can be configured to enable communication of the electronic device 900, such as wired or wireless communication. Furthermore, the electronic device 900 may also include an input / output (I / O) interface 959. The electronic device 900 can operate on an operating system stored in a memory 932.

[0087] In another exemplary embodiment, a computer-readable storage medium including program instructions is also provided, which, when executed by a processor, implement the steps of the stacker-reclaimer multitasking operation control method described above. For example, the non-transitory computer-readable storage medium may be the memory 932 including program instructions described above, which may be executed by the processor 922 of the electronic device 900 to complete the stacker-reclaimer multitasking operation control method described above.

[0088] In another exemplary embodiment, a computer program product is also provided, which includes a computer program executable by a programmable device, the computer program having a code portion for performing the above-described stacker-reclaimer multitasking operation control method when executed by the programmable device.

[0089] The preferred embodiments of this disclosure have been described in detail above with reference to the accompanying drawings. However, this disclosure is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this disclosure, various simple modifications can be made to the technical solutions of this disclosure, and these simple modifications all fall within the protection scope of this disclosure.

[0090] It should also be noted that the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, this disclosure will not describe the various possible combinations separately.

[0091] Furthermore, various different embodiments of this disclosure can be combined in any way, as long as they do not violate the spirit of this disclosure, they should also be regarded as the content disclosed in this disclosure.

Claims

1. A multi-task operation control method for a stacker-reclaimer, characterized in that, include: When the first execution instruction of the first task is received, the execution status of multiple tasks in the task list is obtained. The execution status includes one of waiting, paused, running and stopped. The task list includes the first task. When the plurality of tasks includes a second task whose execution status is running, the execution status of the second task is changed to waiting or paused; When the execution status of the second task changes, the task data of the first task is obtained according to the first execution instruction received from the first task; Based on the task data of the first task, the operation of the stacker-reclaimer is controlled, wherein the task data includes one or more of the following: task start position, task end position, and task type. When the plurality of tasks includes a second task whose execution state is running, changing the execution state of the second task to waiting or paused includes: Obtain the task type of the second task, and change the execution status of the second task according to the task type of the second task. The changed execution status of the second task includes one of waiting and pausing. Update the execution status of the second task to the database after the change; The step of obtaining the task type of the second task and changing the execution state of the second task according to the task type of the second task, wherein the changed execution state of the second task includes one of waiting and paused, including: Obtain the task type of the second task, wherein the task type includes one of stacking, retrieving, and scanning; When the task type of the second task is the same as the task type of the first task received, the execution status of the second task is changed to waiting; When the task type of the second task is different from the task type of the first task received, the execution status of the second task is changed to paused.

2. The method according to claim 1, characterized in that, The method further includes: When the execution status of multiple tasks in the task list is not running, the task data of the first task is obtained according to the first execution instruction received from the first task. The operation of the stacker-reclaimer is controlled based on the task data of the first task.

3. The method according to claim 1, characterized in that, The step of updating the execution status of the modified second task to the database includes: The modified execution status of the second task is sent to the backend server via the transmission control protocol, so that the backend server updates the modified execution status of the second task to the database and displays the execution status of the second task in the task display bar.

4. The method according to claim 1 or 2, characterized in that, The step of obtaining task data for the first task based on the received first execution instruction of the first task includes: Receive the first execution instruction; According to the first execution instruction, obtain the task ID of the first task; Based on the task ID of the first task, retrieve the task data of the first task from the database.

5. The method according to claim 1 or 2, characterized in that, The step of controlling the operation of the stacker-reclaimer based on the task data of the first task includes: Based on the task data of the first task and the current operating position of the stacker-reclaimer, the moving direction and working position of the stacker-reclaimer are determined, and the moving direction and working position of the stacker-reclaimer are sent to the backend server through a transmission control protocol, so that the backend server can store the moving direction and working position of the stacker-reclaimer in the database and control the operation of the stacker-reclaimer.

6. The method according to claim 5, characterized in that, The step of sending the movement direction and working position of the stacker-reclaimer to the backend server via a transmission control protocol, so that the backend server stores the movement direction and working position of the stacker-reclaimer in the database, includes: The movement direction and working position of the stacker-reclaimer are sent to the backend server via a transmission control protocol. When the backend server receives the second execution instruction, it determines the current task data of the stacker-reclaimer based on the received movement direction and working position, inserts the current task data of the stacker-reclaimer into the database using an intelligent sorting method, generates the task data and task ID of the third task, and displays the task ID and execution status of the third task in the task display bar. The second execution instruction is the execution instruction for the stacker-reclaimer to run according to the movement direction and working position.

7. The method according to claim 3, characterized in that, The method further includes: When the stacker-reclaimer completes the first task and does not receive a new task execution instruction, the execution status of the second task is changed to running through the background server, and the stacker-reclaimer is controlled to continue executing the second task. The changed execution status of the second task is stored in the database, and the execution status of the second task is displayed as running in the task display bar.

8. A multi-task operation control device for a stacker-reclaimer, characterized in that, include: The first acquisition module is used to acquire the execution status of multiple tasks in the task list when a first execution instruction of the first task is received. The execution status includes one of waiting, paused, running and stopped. The task list includes the first task. The change module is used to change the execution status of the second task to waiting or paused when the plurality of tasks includes a second task whose execution status is running. The second acquisition module is used to acquire the task data of the first task according to the first execution instruction received from the first task when the execution status of the second task changes; The control module is used to control the operation of the stacker-reclaimer according to the task data of the first task, wherein the task data includes one or more of the following: task start position, task end position, and task type. The change module includes: The first modification submodule is used to obtain the task type of the second task and change the execution status of the second task according to the task type of the second task. The modified execution status of the second task includes one of waiting and pausing. The first update submodule is used to update the execution status of the modified second task to the database; The first change submodule includes: The first acquisition submodule is used to acquire the task type of the second task, wherein the task type includes one of stacking, picking, and scanning. The first state change submodule is used to change the execution state of the second task to waiting when the task type of the second task is the same as the task type of the first task received. The second state change submodule is used to change the execution state of the second task to pause when the task type of the second task is different from the task type of the first task received.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method described in any one of claims 1-7.

10. An electronic device, characterized in that, include: A memory on which computer programs are stored; A processor for executing the computer program in the memory to implement the steps of the method according to any one of claims 1-7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-7.

Images