DNP3_TG: INVALID timestamp is updated when there is no connection to the outstation

• Related Articles

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

  Summary The statistics variables "unsolicited response objects received" (offset 907) and "solicited response objects received" (offset 906) of the DNP3_TG DNP3 master driver are not updated when the master receives object groups from the outstation. ...

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

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

• DNP3_TG: Driver does not / cannot switch to redundant connection under specific circumstances

  Summary DNP3_TG driver does not switch to redundant connection under certain circumstances. This has been fixed. Description DNP3_TG driver does not switch to the redundant connection if the TCP connection to a Terminal Server is established but the ...

• FAQ: How can I monitor and react on the communication status of my devices with zenon?

  Data quality is very important to the integrity of a HMI or SCADA system. As such, zenon has numerous ways to monitor the communication status of different devices within your automation environment. Here are some options that you can use in your ...