Echelon LonMaker - Manual (Page 253)

LonMaker User’s Guide 237
• AppInst. The instance of the LonMaker application that generated the event.
• EventType ID. The type of event that occurred (for example, created, deleted, renamed, shape
moved, connection added).
• Object Type ID. The type of object modified by the event (for example, AppDevice, Channel,
Router, Subnet, NSI, Subsystem, Device template, LonMark Object).
• SubsystemName. The name of the subsystem in which the object is defined. This field can be
empty if the object spans multiple subsystems (for example, channels), or if the subsystem no
longer exists.
• SubsystemHandle. The handle of the subsystem in which the object is defined. Can be 0 for
objects that span multiple subsystems.
• ObjectName. The name of the object that was modified. If the object no longer exists, the name
will be “Object ID:<n>” where <n> is the handle of the object. For events related to network
variables and message tags, the name will be that of their functional block.
• ObjectId. The handle of the object that was modified. For events related to network variables and
message tags, the object ID will be the index of their functional block.
• DeviceHandle. The handle of the device in which the object is defined. This field only applies to
events related to network variables, message tags, and functional blocks.
• NvHandle. The index of the network variable in the device. This field only applies to events
related to network variables.
• Mthandle. The index of the message tag in the device. This field only applies to events related to
message tags.
Manual Network Resynchronization
You may need to manually resynchronize the LNS network database, the network, or the LonMaker
drawing if automatic resynchronization fails or if one the following scenarios occur:
• An LNS application other than the LonMaker tool makes changes to the LNS network database
that are not tracked by LNS events.
• A LonMaker drawing is saved improperly.
• Log entries are deleted from the LonMaker event log before they are applied to a LonMaker
drawing
• Changes are made to a LonMaker drawing in between creating and restoring a hot backup of the
network database.
• A LonMaker backup file containing an LNS network database and LonMaker drawing files is
restored and devices need to be recommissioned.
• A LonMaker network design is created using network recovery.
To manually resynchronize a LonMaker network, follow these steps:
1. Back up the LonMaker network following the steps in Backing up a LonMaker Network Design in
this chapter. This enables you to restore the LonMaker network design in the event a serious
resynchronization error occurs.
2. In the LonMaker drawing, open the LonMaker menu, point to Synchronize, and then click
Resynchronize. The Synchronize LonMaker Drawing dialog appears.
If you did not back up the network and changes have been made since the last backup, a message
appears recommending that you back up the network before proceeding. If this occurs, you should
click No, close the drawing, and back up the network.