A powerful monitoring and logging application is built into London Architect that can receive pertinent information from across a network of devices. These 'events' are logged at user decided timing and particular events can be selected to be monitored from only certain devices.
The event log is an important online monitoring system for the network. Almost a standalone application in itself the Event Log tracks state changes relating to the operation of the network of devices. These events are time stamped and stored in a database for retrieval in the pursuit of bug fixing or a better understanding of unusual operations relating to the hardware, e.g. CobraNet and general device network handling parameters.
The Event Log is either shown as a tab at the bottom of the design window or as a hide-able window on the side or top of the design area. The Event Log window can be brought into view by using the View menu.
See the Event Descriptions for more information on the types of information that can be collected.
Configuring the Event Log application
In the Application Preferences for the Event Log preferences (Tools>Application Preferences>Event Log) there is an option to auto archive the Event Log periodically based on a certain number of entries being reached, the default is 10000. If the Event Log experiences problems then try reducing this number or try collecting a reduced number of days worth of events. There is a maximum number of archived Event Logs that will be saved with the design file. You can change this number in the 'General' tab of the File Preferences.
In the Application Preferences you can also enable or disable the Event Log collection and the frequency of the collection. As well as automatically collecting the events, you can manually read the event from the devices by using the 'Get events from devices now' button on the Event Log Toolbar (furthest right).
Event Log data In the Devices
If the data is not collected by the PC, it is stored on the device until collected. If the allocated memory fills up, the data is overwritten oldest first.