L-VIS User Manual
271
LOYTEC
Version 6.2
LOYTEC electronics GmbH
12.4.3.1 Failure before Database Update
If the procedure failed before the database update, that is, the device template in the
database is still the old version, the device must be rolled back to the last project as well, so
that the database and the device match again. The recommended procedure is detailed
below:
Follow the standard procedure for device replacement as appropriate for your
project, but
do not run the configuration software in plug-in mode at any
time.
Only use the software standalone, including any other configuration tasks
you may be doing to other devices at the same time. If the project used static and
dynamic NVs and the upgrade required a change of the static interface, your
dynamic NVs may be lost and the replace procedure may report data points
which cannot be assigned. Remove them from the project and continue.
Once the device is replaced and commissioned, run the configuration software in
plug-in mode.
If the device lost its dynamic NVs, use the function
Recover DynNVs…
from
the
Tools
menu now, to recover the set of dynamic NVs which were removed
during the last upgrade.
Most likely, the bindings will be lost as well. Use the function
Recover
Bindings…
from the
Tools
menu to recreate the bindings as they were recorded
before the upgrade procedure started.
If the replace procedure reported missing dynamic NVs before, the project has to
be loaded again. Clear the current project data from the editor and re-open it from
the project file.
Program the device to restore the system to the last working state.
12.4.3.2 Failure after Database Update
If the procedure failed after the database update, that is, the device successfully loaded the
new project and the database was updated to match the new static interface, the only things
which could still be missing are dynamic NVs and bindings which would need to be
restored after the database update.
There are two possible options from here:
Try to find the reason why the NVs or the bindings could not be restored,
possibly checking the
Binding Report…
which is available from the
View
menu
for errors, then try to use the
Recover DynNVs…
and
Recover Bindings…
functions from the
Tools
menu to first restore the dynamic NVs (if any) and then
restore the bindings.
Revert back to the last working setup by removing the device from the network
database and roll back the device configuration by following one of the
procedures for integration of a new device, but using the last working project.
While doing this,
do not run the configuration software in plug-in mode at
any time.
Also, skip the step of manually creating dynamic NVs, if instructed to
do so by the standard procedure. If the old project actually used dynamic NV data
points, these will be reported as unusable. Delete them from the project and
continue. Once the device is re-integrated, recover the dynamic NVs (if any) and
the bindings as described above. If dynamic NVs were recovered, the project
needs to be loaded again so that the NVs can be used.