Difference between revisions of "Initial Task Startup"

From Control Solutions IoTServer Documentation
Jump to navigation Jump to search
Line 3: Line 3:
 
[[File:Managed Deconfigure 7.jpg]]
 
[[File:Managed Deconfigure 7.jpg]]
 
<hr>
 
<hr>
 +
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.
 +
 
[[File:MinStartup-1.jpg]]
 
[[File:MinStartup-1.jpg]]
 
<hr>
 
<hr>

Revision as of 13:57, 16 May 2019

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.

MinStartup-1.jpg


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 and simply edit the minimal configuration to make changes as desired.

MinStartup-2.jpg


MinStartup-3.jpg


MinStartup-4.jpg


Minimum configuration files provided:

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