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.

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

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

• When using the Opc2Cli32 Driver in the zenon runtime and using first the Driver command "switch to Simulation mode" (with Opc2Cli32 Driver set to "Hardware" mode in the Editor) and then using the Driver command "switch to Hardware mode" the variables will become invalid and have the Status "switched off" instead of SPONT.

  Summary When using the Opc2Cli32 Driver in the zenon runtime and using first the Driver command "switch to Simulation mode" (with Opc2Cli32 Driver set to "Hardware" mode in the Editor) and then using the Driver command "switch to Hardware mode" the ...

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

• When using a Driver in mode "Simulation - static" and in the zenon runtime the Driver command "Switch to Hardware mode" is executed, variables of the corresponding Driver get INVALID (correct) but when then executing the Driver command "Switch to Simulation mode" the variable stays INVALID but gets also SPONT.

  Summary When performing the Driver command "Switch to Hardware mode" in the zenon runtime variables of a Driver which is running in mode "Simulation - static" get INVALID (correct). When then performing the Driver command "Switch to Simulation mode" ...