Sierra 5391-01, 5391-02 user manual Interpreting Sentry Events, Event Report Types

Page 21

T12017-Sentry_LANServer_Users_Manual

Page 21 of 59

5.8.Interpreting Sentry Events

Sentry events are captured and stored on the LANServer’s flash disk in a file called events.dat. (Additional information on this file is provided in section 5.10 Not every LANServer project reports Sentry Events. If it isn’t present then this is a decision the web project designer made. In the template project supplied with the LANServer, sentry event logging is enabled. An events page must be part of the project and event logging must be enabled.

The event table is a human readable presentation of the event information. The most recent event is the topmost one.

5.8.1.Event Report Types

The two types of event report – K and P reports. P reports are trigged by time and K reports are triggered by a state change for a Sentry-Sensor or by a change of gas concentration.

P Reports

Periodically, the LANServer, records the gas concentration and state of each Sentry- Sensor. The period was configured by the developer who constructed the web project and can be changed. Having the P report allows the user to verify that the Sentry was being monitored during a period. If no K reports were generated because the gas levels remain normal for a long period of time then having the P reports raises the confidence that the system was working and online during that interval.

One P report will be generated each time the LANServer is restarted.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com Tel: (408) 262-2299 Fax: (408) 262-2269 Toll_Free: 888-509-1970 email: support@fieldserver.com

Image 21
Contents Applicability & Effectivity Sentry LANServerTable of Contents LED1 Features Product Description GeneralOperation Connections Sentry Firmware VersionModel 5391-01 LANServer with 2-4 Sentry Controllers Page Quick Start Quick Start LANServer TerminologyBrowser Security Settings Setting Browser Security Settings for ActiveX controlsActiveX Controls and Security T12017-SentryLANServerUsersManual Customize the settings Cookies and Browser Security Setting the Browser Privacy Settings for CookiesSpecify the WebServer IP address and then click Allow T12017-SentryLANServerUsersManual Interpreting Zone Buttons T12017-SentryLANServerUsersManual Interpreting Sentry-Sensor Controls Interpreting Sentry -Combo Controls Interpreting Sentry Alarms Acknowledging Alarms Understanding the Alarm Table ColorsClick Retry to clear the dialog Event Report Types Interpreting Sentry EventsPage What happens if Event Logging is disabled? Understanding the EventsEvents Page and the Date / Time Space Problems Potential Problems with Event Logging File ProblemsEvent File Maintenance Limited number of event recordsManaging Sentry Events Uploading How Event Time Stamps are reported Manual upload Potential Problems with an UploadInterpreting the Sentry Face Plate LED Current sensor number Gas Concentration for current sensor Sensor ActiveX Not Installed One User at a TimeLANServer Driver Ver .05f Required How the Control Operates DescriptionProblems with Calibration Backup Control Backup File ContentsInterpreting Analog, Text and LED controls Text Controls Analog ControlsLED Controls Using the LANServer to allow customers to upload files Appendix 1.2. Objects report ‘Not Found’ Appendix 1.3. Page login.htm not foundAppendix 1.7. Cookie Length Appendix 1.6. Buttons Display in White40159,8 40977,8 40985,8 Appendix 1.9. LANServer Configuration LEDFYI Appendix 2. LANServer Error MessagesWEB#13 Err Not enough Space for alarm WEB#15 FYI ASO Max Limited to %d Web#68 FYI. Http Appendix 3. WinSock Error Messages Wsaenetreset WsaeconnresetWsaeafnosupport WsaealreadyWsaedestaddrreq WsaefaultWsaehostdown WsaehostunreachWsaemfile WsaeisconnWsaemsgsize WsaenetdownWsaenotsock WsaenotconnWsaeopnotsupp WsaepfnosupportWsaesocktnosupport WsaeshutdownSockraw WsaetimedoutWsainvalidproctable WsainvalidparameterWsainvalidprovider WsaioincompleteWsanodata WsanotinitialisedHosts WsanorecoveryWsaproviderfailedinit WsasyscallfailureWsavernotsupported WINSOCK.DLLWsaediscon WsaoperationabortedAppendix 4. FieldServer ActiveX Controls Appendix 4.1. Ana1 Appendix 4.2. LED1Appendix 4.3. Char1 Appendix 4.4. Limitations and Supported Environments Appendix 5. General Appendix 5.1 .1 Browser Caching This page Intentionally Left Blank