To configure a Flow Run in ClearSCADA when the majority of a Flow Run’s configuration is carried out using the RealFLO application and then being read into the ClearSCADA database:
- You need to ensure that each Flow Run has been fully configured in the Flow Computer, using a PC that is running the RealFLO application. (After the corresponding Flow Run items have been created and enabled in the ClearSCADA database, the ClearSCADA server reads the Flow Run’s configuration from the Flow Computer.)
- In the ClearSCADA database, you need to have configured the RealFLO controller with which the Flow Run is associated (see Configuring SCADAPack Modbus RealFLO Controllers).
- You also need to ascertain:
- The types of flow run (gas, liquid or water)
- How many flow runs ClearSCADA is to monitor on a controller
- The numbers of those flow run(s).
- If the Flow Run is in an Instance of a Group Template, ensure that the appropriate Property Overrides are enabled to allow the configuration to be read successfully (for more information, see Read Configuration).
As a minimum, for a Flow Run to be functional (online), you need to configure the Flow Run’s number and specify the name of the outstation (controller) with which the Flow Run is associated.
You then need to put the Flow Run In Service and save the configuration.
Use the Read Configuration pick action to read the rest of the Flow Run’s configuration from the controller into the ClearSCADA database.
UNEXPECTED BEHAVIOR OF APPLICATION
Should a read occur while a Flow Run’s configuration Form is open and an attempt be made to save any user-instigated configuration changes to that Flow Run after the read is complete, a diagnostic message will be displayed. The message will indicate that the Flow Run’s configuration has changed on the server since the Form was opened. Options are provided to discard the user-instigated changes or overwrite the server’s Flow Run configuration with those changes.