Initial Task Startup

From Control Solutions IoTServer Documentation
Revision as of 14:10, 16 May 2019 by Jimhogenson (talk | contribs)
Jump to navigation Jump to search

The Task Status page for an IoTServer with no protocols configured yet will have only the Data Engine displayed.

Managed Deconfigure 7.jpg

Go to the Task Configuration page. The task list will appear as illustrated below. Select the task you wish to configure. Keep in mind channel 0 is always the Data Engine, channel 1 will always be the SNMP Agent if you wish to include one, and channels 2 and 3 are always reserved for the serial ports 2 and 3.


Let's configure data channel 2, or serial port 2, as an example. Select that channel from the system task list. Next, select its function from the function list. Then enter the applicable parameters like baud rate, etc. The nature of additional parameters will vary according to function selected for the channel.

All tasks must be initially started up with at least a "minimal" XML file. You cannot start a task with absolutely no starting point. If you have no previously saved XML that you wish to load, you can use the minimal file already provided in the device, and simply edit the minimal configuration to make changes as desired at a later time.

After you have entered all of the necessary settings, and selected a configuration file, click Save Settings.


Your task is now ready to run. Go to the Task Status page. You will find the task listed with status "Stopped". Click the start button. Upon startup, new databases for this task are created, the databases are loaded for the first time using the content of the XML configuration file you provided, and the task will proceed on to normal operation.

You will need to refresh your page to get an updated list, but once a new protocol is added to the configuration, it will automatically appear in the Protocol Status and Protocol Configuration menus on the left. To further configure the task you just created, go to its configuration menu under Protocol Configuration.



Minimum configuration files provided:

  • global.xml
  • minObjects.xml
  • minServerPrimary.xml
  • minServerSecondary.xml
  • minRtuMaster.xml
  • minTcpClient.xml
  • minSnmpAgent.xml
  • minSnmpClient.xml
  • minSnmpTrapRecv.xml