L-VIS User Manual
270
LOYTEC
Version 6.2
LOYTEC electronics GmbH
To determine if a project is suitable or not, it is not necessary to execute the whole
replacement procedure just to find out that the result still does not match the definition of
the device in the database. Instead, check the following things upfront, before starting the
download:
Run the configuration software standalone, without connection to any L-VIS
device and load the project which is considered to match the current device in the
network.
Check the program ID of the device definition in the network.
If the ID starts with
9000a9…
then the interface matches a standard device,
without any static NVs. In this case, only consider projects which do not contain
any static NV data points. The loaded project must have a Program-ID model
number of 0.
If the program ID starts with
9000d7…
then the device has static NVs created
and therefore uses a non-standard interface. In this case, check the last byte of the
program ID. It is the program ID model number and it must match the model
number of the project which you consider for download.
Once a project with matching model number was identified, this will most likely
be compatible as far as the static interface is concerned. To double check, you
may go through the list of static NVs defined in the project and compare it with
the NVs that should be available on the device according to the devices definition
in the network. If the static interface seems to match, the replace procedure may
be started.
During the replace procedure, if the selected project causes data points to be
reported during project load, which cannot be assigned to any of the existing
dynamic NVs, then this project assumes a different set of dynamic NVs and is
most likely not the right version of the project. Repeat the process with other
projects. The only time when such reports are to be expected is during the first
download in a two-stage replace procedure, as required for mixed projects (static
and dynamic NVs).
12.4.2 Change Network Configuration
There are a few cases where the network definition of the device is changed to match the
current configuration of the device. Such changes are normally handled by the network
management program, but may be supported by functions of the configuration software as
well.
While changing the device configuration requires one of the device replacement procedures
to be executed, changing the network configuration usually means to restore a database
backup which matches the configuration of the current device.
If the device uses static NVs only and the bindings which were originally used together
with this project were saved and are available in a file, the network configuration may be
adjusted by completely removing the old device definition (if any), executing the
integration procedure for a pre-programmed new device, followed by a binding import to
restore the original bindings.
12.4.3 Recover from a failed Update
When a project update including a change of the static interface fails, there may be some
extra steps necessary to restore the last working setup or to resolve the original problem and
finish the upgrade. Which one to use, depends on how far the upgrade procedure ran.