Difference between revisions of "Task Configuration"
Jump to navigation
Jump to search
Jimhogenson (talk | contribs) |
Jimhogenson (talk | contribs) |
||
Line 1: | Line 1: | ||
== Task Manager Interface == | == Task Manager Interface == | ||
[[File:Task manager config page common 1.jpg]] | [[File:Task manager config page common 1.jpg]] | ||
+ | |||
+ | The task manager is your first stop for telling the IoTServer what you want it to do. There are 32 slots that may be occupied by some function, typically a protocol engine or other application. This means you could hypothetically have up to 30 different protocols all talking to each other via the IoTServer, if we actually had that many protocols to pick from. | ||
+ | |||
+ | Select the task you want to configure from the drop-down list, or select an empty slot to assign to a new function. An empty slot is simply denoted "Data Channel N". When assigned to a function, that slot will take on the name of the function. | ||
[[File:Task manager config page common 2.jpg]] | [[File:Task manager config page common 2.jpg]] |
Revision as of 14:15, 23 April 2019
Contents
Task Manager Interface
The task manager is your first stop for telling the IoTServer what you want it to do. There are 32 slots that may be occupied by some function, typically a protocol engine or other application. This means you could hypothetically have up to 30 different protocols all talking to each other via the IoTServer, if we actually had that many protocols to pick from.
Select the task you want to configure from the drop-down list, or select an empty slot to assign to a new function. An empty slot is simply denoted "Data Channel N". When assigned to a function, that slot will take on the name of the function.