Some statistics variables of the DNP3_TG master driver are not updated when objects groups are received from the outstation

• Related Articles

• 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 ...

• DNP3_TG: Incorrect time stamp at variables in the Runtime under specific circumstances

  Summary When the option to use UTC time is disabled in the DNP3_TG driver configuration, variables in the Runtime may have an incorrect time stamp (year 2037) when objects are received from the outstation for those variables, with a variation that ...

• 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 ...

• New functionality implemented for the DNP3_TG driver: Subset Level 4+ master including DNP3 file transfer

  Summary The DNP3_TG driver is a Subset level 2 master and does not support DNP file transfer Description The DNP3_TG driver is a Subset level 2 master and does not support DNP file transfer Solution The DNP3_TG driver has been enhanced with ...

• 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

  Summary DNP3_TG: DNP3 master driver works with non-compliant DNP3 outstations that do not request application layer fragment confirms. Description The DNP3_TG DNP3 master driver has been enhanced to allow communication with non-compliant DNP3 ...