Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

[Imported] DNP3 "Start MDRP Comms" alarm

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Janeway Janeway

[Imported] DNP3 "Start MDRP Comms" alarm

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: florian, originally posted: 2018-10-25 17:15:34 Id:250
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


**_Having issues with some DNP3 outstations over a satellite link. The connection drops to a site. The Comms Failed alarm raises, then 3 minutes later "Scanner command (Start MDRP Comms) Timed Out - Alarm Raised", then less than a minute later comms are re-established and the initial comms alarm clears. But there is a redirection setup to run after 59 minutes and the "Start MDRP Comms" alarm never cleared. Is there an explenation of what MDRP is or how to shut it off? I couldn't find anything in the help file._**


The 'Scanner command (Start MDRP Comms) Timed Out' I believe is normally an 'on server' error.. meaning that ClearSCADA didn't get a response back from the DNP3 driver for the Start MDRP Comms request within a suitable period of time (like 30seconds I think).

Are the TCP settings of the server modified from the standard Windows settings (like the TCP timeout is set significantly higher or such?)

My recommendations from previous experience with satellite link is to use UDP instead of TCP. The handshaking of TCP is killer with the latency of satellite links.
If you use UDP and you have previously turned off Data Link Layer acknowledgement in the DNP3, then you probably want to turn this back on however (since with UDP you don't get the 'reliable comms channel' that TCP provides).


**_Thanks for pointing me in the right direction Bevan. I'll give this a try._**