When changes are made to the variable administration in the editor and changed runtime files are compiled and the runtime is reloaded, a variable that is advised more than once in the runtime may use the variable ID instead of the DNP point index.
In most cases the variable ID will be high and the variable value will become INVALID. In certain cases where the variable ID is low, the variable may receive a value from a different DNP point index.
When changes are made to the variable administration in the editor and changed runtime files are compiled and the runtime is reloaded, a variable that is advised more than once in the runtime may use the variable ID instead of the DNP point index.
In most cases the variable ID will be high and the variable value will become INVALID. In certain cases where the variable ID is low, the variable may receive a value from a different DNP point index.
An issue has been addressed in the DNP3_NG driver where after a reload of the runtime with changes made to the variable administration, variables may have received an incorrect DNP point index.
Now the reload correctly considers the DNP point index and variable communication remains correct.
As a workaround, the runtime can be stopped and restarted, if any changes to the variable administration are made.