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'.
Intended Audience
This guide is primarily intended for engineers who are responsible for configuring SCADAPack Modbus items and features in the ClearSCADA database.
The guide also contains information for:
- Operators and engineers who use the SCADAPack Modbus driver to monitor and control plant
- Maintenance engineers.
Document Scope
This guide explains the configuration, features and database items that are specific to ClearSCADA’s SCADAPack Modbus driver. 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).

This guide contains technical information that is intended for users that are sufficiently familiar with ClearSCADA configuration and operation. Before reading this driver guide, ensure that you are familiar with:
- ClearSCADA configuration practices, procedures, and the configuration of properties that are common to many database items. For more information, see the ClearSCADA Guide to Core Configuration, and the ClearSCADA Guide to Core Point Configuration.
- Driver structure, components, and configuration properties, pick actions, and status attributes that are common to many drivers. For more information, see the ClearSCADA Guide to Drivers.
- Advanced driver configuration order, outstation types, and configuration properties and logging options that are common to many advanced drivers. For more information, see the ClearSCADA Guide to Advanced Drivers.
- The database items and configuration that are specific to this extension driver's 'parent' driver, along with any pick actions, status attributes, and logging options that are specific to that 'parent' driver. (Unless stated otherwise, this extension driver supports the features and options that are supported by its 'parent' driver, in addition to the features and options that are described in this extension driver guide.)
Some sections of this guide are intended for operator-level users. These sections are intended for users that are familiar with the navigational and operational aspects of ClearSCADA. Before reading the operational sections in this guide, ensure that you are familiar with:
- The ClearSCADA user interfaces (ViewX and WebX), the various types of display, their navigation and operation. For more information, see the ClearSCADA Guide to ViewX and WebX Clients.
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:
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.