Welcome to Tasker⚓︎
Tasker is an application that runs on the JNIOR that uses action-based Tasks to be executed manually, triggered, scheduled, or actviated via remote connection. Actions in a 'task' can be I/O related, logging, email, or network-based.
No Code, No Programming Necessary. Just configure it and go!⚓︎
Writing JAVA code on the JNIOR is great and the perfect way to achieve the functionality you want. But, sometime you either don’t have the knowledge, expertise or time and want something out-of-the-box that you can just configure to get the job done. Tasker is the application for you!
Tasker is an application for the JNIOR that enables users to graphically build out configurations for monitor or control applications without the need to be a programmer. Tasker is not loaded on the JNIOR when it is manufactured. It is an add-on application. Please follow the Installing Tasker guide to get Tasker installed and running on your JNIOR.
The following is a quick overview of the different aspects of Tasker...
-
Workspaces – Workspaces enable Tasker logic to be separated into different files to easily manage your deployments. Multiple Workspace files can be loaded and evaluated on the JNIOR simultaneously.
-
Tasks – Tasks are groups of actions you want to perform that are executed from top to bottom. Tasks can executed manually, from a trigger event, scheduled on a specific time, or from a remote connection.
-
Devices – Some Actions used in Tasks may depend on Devices. Devices are names given to connections on and to the JNIOR. The names are then used to make configuration in Tasks easier.
-
Signals – A name given to an I/O point or sensor to make using it in an Action, Trigger or Logger easier.
-
Triggers – A set of conditions to watch for that when met execute a Task. The signals that are configured will be used.
-
Schedules – Scheduling a Task can be done for a One Time execution, Daily, Weekly or by an event.
-
Loggers – Configuration to make logging easier to use in Task Actions. Loggers ask you to provide a file path, the information to be logged to the file and the retention count. The retention count is the number of files for that specific logger that will be kept.
We are here to help. we can help you configure the new version of Tasker to work with your older configuration.