...
Command Queue operation was officially released in Automation1 version 2.3.0.
Why would you use Command Queue? When executing AeroScript code via the .NET interface and the C library, 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.
Command Queue operation is supported in the .NET interface only and is not necessary for operation via the library and C library; this feature can't be accessed from Automation1 Studio. This Command Queue obsoletes the previous Queue Mode operation and PROGRAM BUFFEREDRUN command from A3200 . This is a change from A3200's use cases; see and has significant differences from the A3200 implementation. See Introduction to Queue Mode and Command Queue in A3200 for more details . The Command Queue reserves one task for operation which cannot be used for other purposes.on the previous implementation.
For complete documentation, please refer to the Automation1 Help documentation on our website for the .NET API and the C API.
...
Command Queue has its own control methods to govern the task in which it runs. (The Command Queue reserves one task for operation which cannot be used for other purposes.) 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:
...