JSON Change Object

This block uses JSON data format. If you don't know what JSON is take a look at What is JSON?

The JSON Change Object task block consists of an input and a done output.

If the input to the JSON Change Object is triggered the block will read the JSON value in the first entry. The block will search the JSON from the first entry for the key in the second entry. The block will then replace the value for the key with the value in the third entry. The modified JSON will then be placed into the variable of the fourth entry.

Examples

Here is a simple example of a mission that uses a JSON Change Object. This example changes a JSON object for the key "last" to a value of "Cat" and places the modified JSON is then placed in the variable var1. Then the value of var1 is written to 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.