RobotAgentz Docs

Appearance

At Minute ​

The At Minute task block consists of an input and a True and False outputs.


If the input to this block is triggered the first entry for the minute number (0-59) will be compared to the actual minute number (0-59) and if they match the True output will be triggered else the False output will be triggered.

TIP

One thing to keep in mind when using this block is that an minute will be true for a minute, so if you run some other task blocks when this block is true and then go back to it to check for the minute it will run again. This could cause a situation where you could be running some logic many times during a minute instead of just running it once for that minute. The way to combat this is to add another At Minute after your logic to determine if the next minute has come before going back to the original minute to be checked. The example below will show this configuration.

Examples ​

Here is an example of a mission that checks if the current minute number is 17. If it is then it will trigger a log message block to write "17th minute of the hour!" in the mission log. Then after the logging of the message another At Minute block will be used to check if the previous minute has passed. If so, then the process moves back to the original At Minute block. This setup only allows the writing to the log to occur once each hour.


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.