oyvindskaaden/glados.no
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add files

Browse Source
This commit is contained in:
Øyvind Skaaden
2020-08-16 15:32:44 +02:00
parent 0bd406c224
commit f8dccc95bc
1411 changed files with 79926 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
_files/sound/bss/london/manual/MAIN/MAINEvent_Log.htm Normal file
View File

@@ -0,0 +1,64 @@
<!doctype HTML public "-//W3C//DTD HTML 4.0 Frameset//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="generator" content="Adobe RoboHelp 9">
<title>Event Log</title>
<link rel="StyleSheet" href="HtmlHelp.css" type="text/css">
<style title="hcp" type="text/css">
<!--
p.hcp1 { font-size:10pt; }
span.hcp2 { font-weight:bold; }
-->
</style>
</head>
<body>
<h1 class="firstHeading" style="color: #008080; font-size: 18pt;">Event
Log</h1>
<p><img src="Event_log_2.jpg" alt="" width="593" height="142" border="0"></p>
<p class="hcp1">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.</p>
<p class="hcp1">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.</p>
<p class="hcp1">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.</p>
<p class="hcp1">See the <a href="Event&#32;Descriptions.html">Event
Descriptions</a> for more information on the types of information that
can be collected.</p>
<p class="hcp1"><span class="hcp2">Configuring
the Event Log application</span></p>
<p class="hcp1">In the Application Preferences for the Event
Log preferences (<span class="hcp2">Tools&gt;Application
Preferences&gt;Event Log</span>) 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.
&#160;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.</p>
<p>In the <a href="MAINApplication_Preferences.htm">Application Preferences</a>
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).</p>
<p class="hcp1"><span class="hcp2">Event Log
data In the Devices</span></p>
<p style="margin-bottom: 0;"><font style="font-size: 10pt;" size="2">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.</font></p>
</body>
</html>