DNP3_TG: assemble and process complete message when non-compliant DNP3 outstation does not request confirms to be sent for non-final fragments of a multi-fragment message

• Related Articles

• Sporadic communication interruption to a DNP3 outstation when using the DNP3_TG driver

  Summary Under specific circumstances the communication with a DNP3 outstation using the DNP3_TG driver would get interrupted when the DNP3_TG driver receives a specific multi-fragment response. Variables would become INVALID for a short moment before ...

• Checklist: Process closes unexpectedly (***Non-reproducible***)

  Time estimate: 45 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• The DNP3_TG driver closes unexpectedly without an error message after receiving a specific response to a file transfer request.

  Summary The DNP3_TG driver closes without an error message when a specific outstation reports a file size 0xFFFFFFFF in a response to a file open request. In this particular case, the outstation reports 0xFFFFFFFF to indicate not a file size of 4GB ...

• When using DNP3_TG driver with UDP as channel mode and unsolicited responses in the outstation are not allowed, the sending of a SBO command after a restart of the outstation leads to the case that no more commands can be sent afterwards.

  Summary No more commands can be sent from the DNP3_TG driver to the outstation after a restart of the outstation is followed by a SBO command of the DNP3_TG driver if UDP is configured as channel mode and unsolicited responses are not allowed in the ...

• DNP3_TG driver as DNP3 master with dual endpoint does not correctly accept unsolicited responses from an outstation initiated connection.

  Summary With a DNP3_TG driver configured for use with a dual endpoint, after the master initially established a connection and closed the connection again due to inactivity after the idle timeout, an outstation can successfully connect to the ...