Page History

Purpose

Queue operation is used to buffer lines of AeroScript code. This operation mode is useful for applications that require many short duration moves in a row. This often includes CNC machining or laser manufacture applications. Programs that require velocity blending, velocity profiling, or lookahead synchronization are also common use cases for queue operation. Some AeroScript commands are also only compatible with queue mode operation.

Command Queue History

Command Queue operation was officially released in Automation1 version 2.3.0. When executing AeroScript code via the .NET interface, a fixed overhead of processing time and sometimes network latency occurs between commands. Command Queue operation allows the controller to buffer single lines of AeroScript code in a FIFO (First In First Out) queue to execute commands with no latency. 

...

For complete documentation, please refer to the Automation1 Help documentation on our website for the .NET API and the C API.

Governing the Command Queue

Command Queue has its own control methods to govern the task in which it runs. This differs from ProgramStop() and other AeroScript commands, which aren't available in Command Queue. The following basic control and scheduling functions are available for the Command Queue, in both the .NET API and the C API:

...

• Paused status (boolean)
• Empty queue status (boolean)
• Number of executed commands over the queue's lifespan
• Number of unexecuted commands remaining in the queue
• Number of times the queue became empty during its lifespan

Additional Considerations

When using Command Queue, several considerations are the responsibility of the customer and end user. This includes queue starvation management, and thread safety.

Please refer to the documentation (.NET API, C API) for full information on queue starvation management and thread safety for the Queue Mode commands and class, which differ between .NET and C.

Related articles

...