DNP3 layer acknowledgements, retries and timeouts - Arc protection - Merging unit - Motor protection - Transformer protection - 2 winding - Feeder protection - Voltage regulation - Capacitor bank protection - Interconnection protection - Busbar differential protection (high impedance) - Generator protection - Power management/Load shedding - Back-up protection - DNP3 Communication Manual - 615 series Relion Protection and Control - 5.0 FP1 IEC - IEC - 18.03.2022

615 series DNP3 Communication Protocol Manual

It is possible to set up acknowledgements on both DNP3 link layer and application layer. The settings should be equal on both the client and the server sides of the communication. The timeouts must be set so that the other side has enough time to prepare a positive acknowledgement. If an acknowledgement is received after the configured timeout, it is discarded.

Confirmations, retries and timeouts can be configured via parameters.
  • Configuration > Communication > DNP3.0 > DNP3.0n > Data link confirm
  • Configuration > Communication > DNP3.0 > DNP3.0n > Data link confirm TO
  • Configuration > Communication > DNP3.0 > DNP3.0n > Data link retries
  • Configuration > Communication > DNP3.0 > DNP3.0n > App layer confirm
  • Configuration > Communication > DNP3.0 > DNP3.0n > App confirm TO

DNP3 link layer acknowledgements should not be used in TCP/IP link mode, since the DNP3 message transport (link) is then encapsulated and secured by the Ethernet protocol.

Link layer acknowledgements are seldom used in serial mode. The application layer acknowledgements also cover the link layer acknowledgements. This means that if the application message was successfully delivered, then the link layer must also have been successful. Furthermore, it is easier to perform a whole application layer retransmission rather than link layer retransmissions. Otherwise the application layer timeout must be prepared to cover all the timeouts and retransmissions performed by the link layer.