RobotAgentz Docs

Appearance

Launch another Agent to execute a mission ​

This task block is used to launch another agent to run a mission.


If the input to this block is triggered this task block will request a new agent to run the specified mission. This block allows the option to initialize the variables in the new mission. This initialization is a JSON object in the following format:
    [{opname:"",opvalue:""},...]

Here is an example initialization JSON. This will create a variable var1 and var2 in the new mission and will set the values to 1234 and 5678 respectively. 
    [
        {
            "opname": "var1",
            "opvalue": "1234"
        },
        {
            "opname": "var2",
            "opvalue": "5678"
        }
    ]

There is also another optional setting of an Agent name. This is helpful if you have many launched agents and want to see them by name in the Agent Control screen. If this setting is not configured the name will default to "anon".

Note: ​

Keep in mind that this feature is limited by what concurrency plan you are paying for. When this feature is used it will count as a concurrecy of 2, while the parent agent is still running.

Examples ​

Here is an example of a mission that launches another mission named "initvartest" located in a folder named "test". This example is also initializing the variables for the launched mission. The "initvartest" mission will run and will be able to use the variables "var1" and "var2". The new mission that runs will be named "test35526".

Use Cases ​

This task block enables your missions to be modular. You can separate features and functions of missions into smaller modules and then launch them based on conditions in the parent mission. There is no restriction on how many missions are launch, but there is a restriction on how many missions can be runnning at one time, which is the concurrency number in the plan you have purchased as noted above.

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 ​