Delay in Milliseconds

The delay task block consists of an input and a done output. The only setting for the delay block in the integer value for the number of milliseconds. This task block is only useful for Tier 2 and Tier 3 because Tier 1 task blocks have a throttle limitation.

See Plans and Limits for more information on Tier 1 limitations.

If the input to the delay block is triggered the delay block will wait for the number of milliseconds that you have configured until it triggers the done output. The accumulated time will reset to zero when the done output is triggered and will restart the delay if the input trigger is activated again.

Examples

Here is a simple example of a mission that uses a delay before a message is sent to the mission log.

Use Cases

The delay is generally used to give some time seperation between tasks. Sometimes in a mission there is a process that requires multiple iterations and each iteration requires some "resting" time. Use the delay task block for these situations.

Copy / Settings / Docs

Each task block has three buttons named Copy, Settings, and Help.

• Copy: This will duplicate the task block with all the current settings.
• Settings: Settings will show a dialog that allows some added configuration for the block
  • Note: This allows you to add a text note for the current block. This note will appear in the log file if the Block Loggin option is enabled.
  • Transition Out Time: Each block can specify a delay in milliseconds that it will wait after an output trigger is activated. This feature is generally not used but is avilable for more granular flow control of the mission if needed.
  • Block Logging: If this is enabled then the internal logging of the block is turned on and will be sent to the mission log. Each block has different amounts of internal logging which can make mission logs become large in some cases. Users generally do not enable this feature because of the limits to data storage.

Other