Write to Mission Log

The write to mission task block consists of an input and a done output. The only setting for this task block is the message that you want to write to the mission log. This task block is helpful for testing missions, but they are also useful for mission where you just need to make some logs along the way that can be reviewed at a later date.

If the task block is triggered the specified message will be written to the log then the done output is triggered.

Examples

Here is a simple example of a mission that uses a write to mission log. In this example the variable "var1" contents are written to the mission log.

The mission logs can be access from the Agent Control screen. Press on the "Agent History" button and select the mission to view the mission log.

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