Introduction to the SCADAPack Modbus Driver
This driver is an extension driver. It provides additional application-specific functionality to the 'parent' driver with which it is associated. To interact successfully with devices using an extension driver, you need to:
- Install and run both the extension driver and its 'parent' driver (and, if applicable, its 'grandparent' driver)
- Ensure that the extension driver and its 'parent' driver (and, if applicable, its 'grandparent' driver) are licensed
(some extension drivers are licensed separately to their 'parent' driver) - Configure the required database items and settings on the 'parent 'driver (and, if applicable, the 'grandparent' driver)
- Configure the required database items and settings on this extension driver.
- Ensure that the database items (and any database items on which they depend) have valid, saved, configuration and are 'In Service'.
The SCADAPack Modbus driver is an Advanced ModbusExtension Driver. It provides additional functionality to enable ClearSCADA to communicate with SCADAPack® controllers, using the Modbus® protocol suite (see Which Driver?). In order to communicate with SCADAPack controllers, ClearSCADA needs to run both the Advanced Modbus driver and the SCADAPack Modbus extension driver (see Confirm that the SCADAPack Modbus Server Component is Installed).
The Modbus communication types that the driver supports include:
- Modbus RTU serial, Modbus ASCII serial
- Modbus RTU over TCP, Modbus ASCII over TCP
- Modbus RTU over UDP, Modbus ASCII over UDP
- Open Modbus/TCP.
ClearSCADA can communicate with SCADAPack controllers directly, using direct or PSTN communications. Function codes supported by the SCADAPack Modbus driver determine how it reads or writes to data on the controllers (see Modbus Function Codes Supported by the ClearSCADA SCADAPack Modbus Driver).
ClearSCADA can also provide a communications ‘gateway’ to allow applications such as TelePACE®, and ISaGRAF®, to communicate with SCADAPack controllers remotely, via the same communications link (for example, in situations where a SCADAPack controller has only one radio link). With the latter set-up, a Remote Connection database item provides a TCP/IP socket connection between ClearSCADA and the remote application.
The SCADAPack Modbus driver also enables ClearSCADA to retrieve DLOG (stored SCADAPack) data records from SCADAPack controllers and, if required, store those records historically in the ClearSCADA database.
The SCADAPack Modbus driver documentation:
- Summarizes the Terminology of which you need to be aware
- Explains how to:
- Confirm that the SCADAPack Modbus Server Component is Installed
- Configure SCADAPack specific features and items within the ClearSCADA database (see Configuring SCADAPack Modbus Devices in ClearSCADA, and see Scanning Direct Controllers on the SCADAPack Modbus Driver).
The documentation also explains:
- Features that are of interest to operators (see Using SCADAPack Modbus Specific Actions)
- Driver-specific aspects that are of interest to system administrators and engineers when investigating unexpected behavior relating to the SCADAPack Modbus driver. For information, see:
NOTE: If your ClearSCADA system is running the SCADAPack Modbus RealFLO Extension Driver to communicate with SCADAPack controllers that have RealFLO enabled, it will support additional features that only apply to the RealFLO-enabled devices. Use the ClearSCADA Guide to the SCADAPack Modbus RealFLO Driver in conjunction with this guide for information on these additional features.