RTU32E Upgrade made easy

Retrofit your legacy RTUs

Footprint from the past, functionality of the future…RTU32E

The RTU32E is powerful and versatile.  It provides current and future-proof functionality – with a footprint and connectors to fit the past. It allows rapid upgrade of legacy equipment and avoids the significant costs of replacing or rewiring cabinets.

The RTU32E supports IP and serial connections using PSTN, leased lines, GSM, GPRS, 3G/4G, ADSL and radio. A wide selection of communications drivers enables interfacing with various SCADA hosts, RTUs, PLCs and field devices. SCADA protocols include IEC61850, IEC60870, MODBUS, DNP3 and DNP3 WITS.

With 60 on board I/O (12x AI, 32x DI, 16x DO and 4x AO), built in 3G modem support, 2x high-speed LAN, 4 serial ports + 2x USB ports, Brodersen makes it easy to upgrade and meet the demands for the future.


Share it with your freinds

Overview - RTU protocols and driver setup
Your RTU application may simply be an 'end point' and only need to interface with a SCADA host or other master device - or it may need to 'sing and dance'...
1- Select what you need
The RTU Configuration Tool allows selection of protocols and hardware.
2 - Create a project in WorkSuite
Then define IO points, create some logic and additional variables eg. this waste water pump station controller accumulates pump statistics and computes derived flow totals from change in wet well volume.
3 - Setup DNP3 slave for this example
Use the Fieldbus Configurator to add the DNP3 slave protocol, create a channel (how to communicate), create a 'session' (who to communicate with), then set application layer parameters (messaging rules).
4 - 'Variables of interest'
Variables (data points in the RTU database) can be 'exposed' to one or more protocols, by referencing them in either the fieldbus editor (simple protocols like Modbus), or including them in a 'profile' (advanced protocols like IEC61850 and DNP3). For DNP3 slave, the variables of interest are dragged in to the DNP3S profile, where they can be associated to object types, given a point address, event class, reporting limits etc.
5 - Prove it works
Connect the RTU to the SCADA host and prove the data values are transferred correctly. If you need to troubleshoot the message contents - use the RTU web interface utility to capture network data packets for viewing in Wireshark to quickly resolve issues.
6 - Make it smarter!
The WorkSuite logic tools allow you to interact with the RTU communications tasks, to enhance the monitoring and control of your data transfer processes. This example DNP3 slave RTU is monitoring the unread events buffers and is able to manipulate point object properties (event class, reporting thresholds etc) and network interface properties (IP address of the host and peer slaves that it may be communicating with).
Conclusion - enjoy having a 'future proof' RTU...
Your RTU requirements will evolve over time, so when you need more I/O, comm ports, protocols or RTU functionality - know it can be easily implemented in a Brodersen RTU.
Previous slide
Next slide