Sierra 5391-01, 5391-02 user manual Understanding the Events, Events Page and the Date / Time

Page 23

T12017-Sentry_LANServer_Users_Manual

Page 23 of 59

5.9.Understanding the Events Page

One report for the Sentry, even if only one sensor on the Sentry generated the event.

Type of report.

The date and time the event was recorded.

There are important data and time considerations. See Section 5.9.1

Event Trigger.

In this example, Sensor 1 is reporting a Threshold and Delta Event as well as indicating that an alarm event is still active (lower case). If the alarm event was new it would have been reported with an uppercase

A

Notes on the previous page provide explanation of the event ‘letters’

Sensor gas

concentration

levels.Sensor Numbers 1..8

5.9.1.Events Page and the Date / Time

When events are recorded, the LANServer records the event time as the number of seconds that have elapsed since Jan 1, 1970 UTC. This data is stored in the events.dat file. This provides an absolute, but inconvenient time.

When reported on the events web page, this time, is converted to a human readable form and reported in PST (Pacific Standard Time). The LANServer does not auto adjust for Daylight Savings time and hence is permanently fixed in PST.

It is important that the LANServer’s data and time has been set to avoid invalid data and times in the events report. When LANServer’s are shipped from the factory the date and time has not been set.

5.9.2.What happens if Event Logging is disabled?

If event logging is disabled then the events page will not update with new events and new events will not be recorded. Not every web project has event logging enabled. Furthermore the LANServer may disable event logging under certain circumstances.

If event logging is disabled then the LANServer prints a message to the Error Screen. “WEB:#42 FYI. Event storage disabled.”

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 23
Contents Applicability & Effectivity Sentry LANServerTable of Contents LED1 Operation FeaturesProduct Description General Connections Sentry Firmware VersionModel 5391-01 LANServer with 2-4 Sentry Controllers Page Quick Start Quick Start LANServer TerminologyActiveX Controls and Security Browser Security SettingsSetting Browser Security Settings for ActiveX controls 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 Events Page and the Date / Time What happens if Event Logging is disabled?Understanding the Events Limited number of event records Potential Problems with Event Logging File ProblemsSpace Problems Event File MaintenanceManaging 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 LANServer Driver Ver .05f Required ActiveX Not InstalledOne User at a Time 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 Wsaealready WsaeconnresetWsaenetreset WsaeafnosupportWsaehostunreach WsaefaultWsaedestaddrreq WsaehostdownWsaenetdown WsaeisconnWsaemfile WsaemsgsizeWsaepfnosupport WsaenotconnWsaenotsock WsaeopnotsuppWsaetimedout WsaeshutdownWsaesocktnosupport SockrawWsaioincomplete WsainvalidparameterWsainvalidproctable WsainvalidproviderWsanodata WsanotinitialisedWsasyscallfailure WsanorecoveryHosts WsaproviderfailedinitWsaoperationaborted WINSOCK.DLLWsavernotsupported WsaedisconAppendix 4.3. Char1 Appendix 4. FieldServer ActiveX Controls Appendix 4.1. Ana1Appendix 4.2. LED1 Appendix 4.4. Limitations and Supported Environments Appendix 5. General Appendix 5.1 .1 Browser Caching This page Intentionally Left Blank