Scenario 2: Configuration Application > Load into Field Device > Upload to ClearSCADA

If your Field Device supports configuration upload, Scenario 2 is possible:

In Scenario 2, the configuration changes are made using the Configuration Application and are loaded into the Field Device locally. The changes are then uploaded from the Field Device to ClearSCADA.

1. Make the Field Device's bulk configuration file available for editing in the Field Device's Configuration Application. If ClearSCADA has a copy of the bulk configuration file, you can export it, and then edit it using a Configuration Application (see Export Configuration).

   Some Configuration Applications are able to read the configuration directly from the Field Device, and so a bulk configuration file is not used.

2. Use the Field Device's Configuration Application to open the bulk configuration file and make the changes you require.
3. Save the configuration, and make sure you update the version of the bulk configuration. The Configuration Application creates an updated bulk configuration file.
4. Update the Field Device with the new bulk configuration file. The way you do this will vary depending on the Field Device and Configuration Application. For example, with the Schneider Electric Talus T4e, you can download the configuration update from the Configuration Application to the Talus T4e.
5. Inspect the Field Device on site to validate that the Field Device is working as expected.
6. Upload the updated configuration files from the Field Device into ClearSCADA (see Upload Configuration (WITS Outstation) ).

7. You can monitor the status of the upload by using the Outstation List and the Events List.

   For information on the Outstation List, see Display and Use Lists in the ClearSCADA Guide to Lists.

   For information on the Events List, see Display the Events for an Item or Group in the ClearSCADA Guide to Lists.