Difference between revisions of "Initial Task Startup"

From Control Solutions IoTServer Documentation
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
The Task Status page for an IoTServer with no protocols configured yet will have only the Data Engine displayed.
 +
<hr>
 
[[File:Managed Deconfigure 7.jpg]]
 
[[File:Managed Deconfigure 7.jpg]]
 +
<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.
 
<hr>
 
<hr>
 
[[File:MinStartup-1.jpg]]
 
[[File:MinStartup-1.jpg]]
 
<hr>
 
<hr>
All tasks must be initially started up with at least a "minimal" XML file.
+
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.
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.
 
  
 +
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.
 +
<hr>
 
[[File:MinStartup-2.jpg]]
 
[[File:MinStartup-2.jpg]]
 +
<hr>
 +
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.
 
<hr>
 
<hr>
 
[[File:MinStartup-3.jpg]]
 
[[File:MinStartup-3.jpg]]
 +
<hr>
 +
After a pause while the task starts, the Task Status page will show "Running" and the buttons will change accordingly.
 +
 +
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.
 
<hr>
 
<hr>
 
[[File:MinStartup-4.jpg]]
 
[[File:MinStartup-4.jpg]]
 
<hr>
 
<hr>
Minimum configuration files provided:  
+
Minimum configuration files that are provided already preloaded are as follows:  
 
 
* global.xml
 
* minObjects.xml
 
 
 
* minServerPrimary.xml
 
* minServerSecondary.xml
 
  
* minRtuMaster.xml
+
{| class="wikitable"
* minTcpClient.xml
+
|-
 +
! File Name !! Function or purpose
  
* minSnmpAgent.xml
+
|-
* minSnmpClient.xml
+
| global.xml || Minimal task manager configuration with only a Data Engine enabled.
* minSnmpTrapRecv.xml
+
|-
 +
| minObjects.xml || Minimal set of 3 data objects.
 +
|-
 +
| minServerPrimary.xml || Minimal configuration for primary Modbus RTU slave or Modbus TCP server. Should be used only once.
 +
|-
 +
| minServerSecondary.xml || Minimal configuration for secondary Modbus RTU slave or Modbus TCP server. Use this for additional instances of slave/server after primary has been defined once.
 +
|-
 +
| minRtuMaster.xml || Minimal configuration for Modbus RTU Master.
 +
|-
 +
| minTcpClient.xml || Minimal configuration for Modbus TCP Client (master).
 +
|-
 +
| minSnmpAgent.xml || Minimal configuration for an SNMP Agent based on the minimal set of data objects in minObjects.xml.
 +
|-
 +
| minSnmpClient.xml || Minimal configuration for an SNMP Client.
 +
|-
 +
| minSnmpTrapRecv.xml || Minimal configuration for an SNMP Trap Receiver.
 +
|-
 +
|}

Latest revision as of 14:19, 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


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.


MinStartup-2.jpg


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.


MinStartup-3.jpg


After a pause while the task starts, the Task Status page will show "Running" and the buttons will change accordingly.

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.


MinStartup-4.jpg


Minimum configuration files that are provided already preloaded are as follows:

File Name Function or purpose
global.xml Minimal task manager configuration with only a Data Engine enabled.
minObjects.xml Minimal set of 3 data objects.
minServerPrimary.xml Minimal configuration for primary Modbus RTU slave or Modbus TCP server. Should be used only once.
minServerSecondary.xml Minimal configuration for secondary Modbus RTU slave or Modbus TCP server. Use this for additional instances of slave/server after primary has been defined once.
minRtuMaster.xml Minimal configuration for Modbus RTU Master.
minTcpClient.xml Minimal configuration for Modbus TCP Client (master).
minSnmpAgent.xml Minimal configuration for an SNMP Agent based on the minimal set of data objects in minObjects.xml.
minSnmpClient.xml Minimal configuration for an SNMP Client.
minSnmpTrapRecv.xml Minimal configuration for an SNMP Trap Receiver.