SCADAPack 474 to another SCADAPack 474 communication

[Tyrone19]

Hi Community

Looking for some assistance on how to set communication between 2 SCADAPacks 474 on different sites (DNP3). eg. If sensor 1 is high on Site 1 activate a relay on Site 2. Also how would we go about configuring DTMs on Remote connect eg. For ATV6xx communication.

Any guides, notes, videos or past programs will be highly appreciated.

Thank you

[AlastairF · Accepted solution]

Station to Station communications using DNP3:

There's a few steps along the way.

1. Set up DNP3 routing table so each device has a route to the other.

Help Navigation: SCADAPack SCADA Protocols Technical Reference > DNP3 Protocol Reference Information > DNP3 Routing

2. Use the DNP3 Peer Communication blocks to set up the logic. Your call as to using Read requests or Write requests (commands). You need to set up the list of points first then execute the operation.

Help Navigation: SCADAPack Function Blocks Technical Reference > DNP3 Peer Communication Function Blocks

Comment: It can  be way easier to use ModBus communications but DNP3 can be more robust.

ATV drive communication:

No problem setting this up.

Use of DTM allows you to configure the drive and set the communications parameters and tables.

Still waiting on the new RemoteConnect 2.7.3 release available mid April to see what has changed with communications but in previous releases the use of the IO Scanning tables in the drive was prevented by address limitations in RemoteConnect.

I got around that by using the separate read and write configuration tables (NCA and NMA tables). These are limited to 8 parameters each and have the default parameters loaded for the first two fields. Your configured communications then reads/ writes to NC (IEC %MW12761) and NM (IEC %MW12741) tables for the actual values. The standard drive setup is to use the DriveCom profile and I have a DFB that uses this for drive control and monitoring.

[Tyrone19]

Thanks so much for the info!

[Tyrone19]

Hi, Is it possible for one SCADAPack to communicate with 2 or more scadapacks using peer to peer. I am trying to do this, it works with one, however as soon as I add a second one my points get mixed up. I have 2 different read list and different read execution blocks.

[BevanWeiss · Accepted solution]

Yes, it's possible to have dozens of RTUs communicating in this manner.

Although the most I've ever setup is 10.. since in practical applications there's very few larger scale systems (needing to talk between so many nodes).

If you are 'writing' to a particular RTU, then each of the writing RTUs needs to have a separate DNP3 address at the destination to write into (unless you want overwriting to occur).

If reading from a particular RTU then no issue, but for each RTU you read from you'd need to have a unique local address to put the read data into.

You're going to have to provide more information on what your actual code is for us to provide much help on this however (and I'd suggest you do this as a separate topic).

[Tyrone19]

Thanks Bevan for your assistance. It was a small error on my code as I initialized to two queues with the same string therefore caused a clash.  

[Tyrone19]

Hi All, Is there any best practices on how often the execute read list should execute? I would assume that this should only occur when there is a change in value?

[Tyrone19]

Hi All, Is there any best practices on how often the execute read list should execute? I have a client who is polling even second which is creating way too much traffic on the network.