Incorrect negative values in the runtime under specific circumstances for variables of the the DNP3_TG driver

• Related Articles

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

• BeckhNG driver sometimes receives incorrect values under specific conditions when requesting many variables e.g. RGM recipe shadow variables

  Summary When the BeckhoffNG driver advises (enable in the driver) many variables and during this advise another set of variables is advised, the first advise is returned from the buffer in the driver before it was correctly updated. This resulted in ...

• In specific circumstances the system driver variables may not be updated in the Runtime.

  Summary System driver variables may show wrong or outdated values in the Runtime when they are added by executing the "Reload project online" function. DescriptionSystem driver variables may show wrong or outdated values in the Runtime when they are ...

• The OPCUA client driver may cause the runtime to stop responding under specific circumstances

  Summary The OPCUA client driver uses the due time for publish responses (keepalive) to check if the OPCUA server is still responding. Normally if the connection to the OPCUA server is lost, the connection is closed at the TCP level. If however no ...

• Under specific circumstances the runtime may close unexpectedly when writting values to the hardware via the variable diagnosis screen.

  Summary When executing the diagnosis screen specific function all variables: write set values from the standby server with both servers running, the runtime may close suddenly if this function is executed repeatedly with different variable's ...