Echelon LonMaker - Manual (Page 235)

LonMaker User’s Guide 219
18. This window displays the status of the resynchronization. Resynchronization events will be listed
in the order they occur. Click OK when the resynchronization is complete. The
resynchronization events, including any errors, are shown in the status pane and recorded in a log
file (Resync.log). The resync log is stored in the drawing directory of the current LonMaker
network.
Notes:
• Recommissioning a device may temporarily interrupt its operation. Recommission devices
when the network can tolerate brief service interruptions.
• When recommissioning the network, the LonMaker tool is placed OnNet and it remains
OnNet after the recommissioning process has been completed.
• If you defined and commissioned new devices in between backing up and restoring the
network, recommissioning the network does not modify the new devices. You can redefine
and commission those devices so that they communicate properly with existing devices after
you have restored and recommissioned your network.
Recovering a LonMaker Network
You can recover a LonMaker network design from a physical network. The network recovery creates
a new LonMaker drawing and LNS network database based on the devices recovered. This is useful
for networks that were installed with legacy network tools not based on LNS; self-installed networks,
including ISI networks; and LonMaker networks or networks installed with LNS in which the original
network database has been lost.
To recover a network, follow these steps:
1. If you are recovering a network that was originally installed with a tool based on the LonManager
API, you can use the LonManager CSV utility to create a comma-separated value (CSV) file from
the LonManager database. This file will provide names from the LonManager database to
enhance the recovery.