Modbus Scanner Configuration Overview Page 1 of 1

Modbus Scanner Configuration Overview

Your SCADAPack E rPAC or RTU supports a large number of Modbus RTU Slaves and Servers and a large number
of point scanners on each Slave or Server. In addition, SCADAPack E Configurator allows you to easily enable and
disable communications with each Modbus RTU Slave or Modbus/TCP Server. These capabilities are ideal in
environments where you need the flexibility to:
 Support both Modbus/TCP and Modbus RTU connections to a single Modbus RTU Slave or Modbus/TCP Server.
 Support multiple point scanners on a single Modbus RTU Slave or Modbus/TCP Server.
 Quickly take Modbus RTU Slaves or Modbus/TCP Servers in and out of service to support different configuration or
application requirements.
The table below summarizes the maximum number of devices, point scanners and points that can be configured.
Note: For SCADAPack 300E RTUs, it takes 2 digital points associated with the Modbus scanner to count as one point
toward the maximum limit, compared with 1 analog point counting as one point toward the maximum limit.

Modbus RTU Master or Maximum Number of Maximum Number of Maximum Number of

Modbus/TCP Client Modbus Devices Point Scanners per Mapped Points per
Modbus Device Modbus RTU Master or
Modbus/TCP Client
SCADAPack 300E 20 50 500
SCADAPack ES, SCADAPack ER, 128 100 3000
SCADAPack 530E, SCADAPack
535E

While the flexibility offered by SCADAPack E products has advantages, polling large numbers of Modbus registers on
large numbers of devices can reduce performance. Factors such as scan rate, point quantities, and overall network
conditions also affect performance. If you need to simultaneously poll large numbers of Modbus RTU Slaves or
Modbus/TCP Servers at high speed, you may want to use a Schneider Electric Programmable Logic Controller (PLC)
as the Modbus RTU Master or Modbus/TCP Client. Schneider Electric PLCs are designed for high-speed polling
applications.

Configuring Modbus RTU Master and Modbus/TCP Client Operation

The procedure below lists the high-level steps required to configure an rPAC or RTU to operate as a Modbus RTU
Master or Modbus/TCP Client. Follow the links for details.
1. Enable Modbus RTU Master or Modbus/TCP Client operation.
2. Add the devices that you want to function as Modbus RTU Slaves or Modbus/TCP Servers.
3. Add the point scanners that define which Modbus registers are scanned and mapped to DNP points.

Managing Modbus RTU Slaves and Modbus/TCP Servers

Once a Modbus RTU Slave or Modbus/TCP Server is configured and communicating with the Modbus RTU Master or
Modbus/TCP Client, you can:
 Enable and disable communications with Modbus devices
 Force read and write operations
 View status information
 Update status and control information every second

mk:@MSITStore:C:\Program%20Files%20(x86)\Schneider%20Electric\SCADAPack%20E\Reference%20Man... 9/8/2021