Where a third-party server uses the DNP3 protocol to obtain data from ClearSCADA, and ClearSCADA uses the DNP3 protocol to obtain its data from an outstation, ClearSCADA becomes dual-purpose, with regard to DNP3. When communicating with the third-party server, ClearSCADA acts as a DNP3 Slave, and when communicating with the outstation, ClearSCADA acts as a DNP3 Master.
In this scenario, you need to configure ClearSCADA as both a DNP3 master (see ClearSCADA as a DNP3 Master Communicating with DNP3 Outstations), and a DNP3 Slave, (see Third-Party Master Communicating with a ClearSCADA DNP3 Slave)
The diagram below shows a third party server acting as a DNP3 master to ClearSCADA, and ClearSCADA acting as a master to a DNP3 outstation. This scenario might be required, for example, should a system have a hierarchical structure, whereby ClearSCADA and/or a third-party server provide control and monitoring features for different subsets of data.
