Configuration Order
For each simple driver, you need to configure:
- If applicable to the drivers that you are using, either:
- Channels to define the communications connections between the scanner and a PLC or other remote device (see Configuring Channels on Simple Drivers).
Or:
- Servers to define the device on which the points are located.
- Scanners to define the rate at which data is scanned and, if applicable, when the data is scanned, and the type of communications connection used (see Configuring Scanners on Simple Drivers).
- Points to represent the calculated values, measuring instruments, or control devices that are associated with each scanner. The type of point that you can configure varies, depending on the driver (see Points on Simple Drivers).
- Pulse actions to carry out controls on plant for only brief periods of time. Pulse actions are supported by several simple drivers (see Defining Pulse Action Details in the ClearSCADA Guide to Core Point Configuration).
To minimize the time taken to configure the required simple driver items, configure them in the order given above.
By default, an item is not ‘In Service’ when you first create a database entry for it. In order for the ClearSCADA server to communicate with an item, you have to put the item In Service (online), and ensure that it has saved, valid configuration (see Placing an Item In Service in the ClearSCADA Guide to Core Configuration). ClearSCADA will generally prompt you for any mandatory settings that an item requires, as you configure it.
If you later take a scanner out of service, its dependants (points, pulse actions, and so on) become out of service.
Similarly, if you later take a channel out of service, its scanners and their dependants (points, pulse action, and so on) also become out of service.
In each case, this does not affect the configuration of these items.
Be aware that users need to be assigned the Configure Database feature to enable them to configure items in the database (see Database Security in the ClearSCADA Guide to Core Configuration).