Quick Start Guide

12 SENTINEL SM1 Quick Start Guide 13
Monitoring section (MonIcon)
This allows you to view what is going on inside the device and in the system at a glance.
It shows the overall state of the monitored system, e ectively duplicating some of the indicators on the device itself:
• The System State (Normal, Check or Fault).
• The number of Devices found on the network
• What “local” alarms you will allow to be reported
You can change the view to the main panel by clicking the “>>” button.
Main control panel
This allows you to view what is going on inside the device and in the system at a glance.
It shows the overall state of the monitored system, e ectively duplicating some of the indicators on the device itself:
• The System State (Normal, Check or Fault).
• The number of Devices found on the network
• What “local” alarms you will allow to be reported
You can change the view to the main panel by clicking the “>>” button.
Hidden controls
Your vendor may have hidden some of the controls on the panel in order to maintain proper protection of the system. Such hidden controls will appear grey and cannot
be adjusted.
Saving & recalling data
Device Data may be saved to disk or opened from disk. PodWare Device Settings  les (with  le extension .dse) contain all the data necessary to restore a device to
exactly the same state as when the  le was saved.
If the current settings have been changed since the last  le save or  le open, the Save Icon on the panel toolbar will be shown in solid colour. If the settings are already
safe, the Save icon appears grey.
If a  le is opened when online to devices, the new data will be sent to the device, overwriting whatever was in the device. A warning will be given before this is done.
Data saved from one device can be reopened in another to save time inputting data. (Assuming settings are to be duplicated)
PodWare will always try to protect your data, warning you if you are attempting an action that could cause loss of data.
Tool bar
The toolbar provides the following one-click functions:
• Open - opens a  le which contains parameters for the device. A dialogue will appear, inviting you to choose a  le to open.
• Save - saves the current settings. A dialogue will appear inviting you to enter a  le name. If the settings have not changed since you last saved or opened a  le,
the Icon will appear greyed out, indicating that a save is not necessary.
• Locate -  ashes a message on the display to assist device identi cation, and as a quick check that communications are working. This only works when on-line.
• Help - launches (this) Panel Help
Keyboard shortcuts
PodWare supports the following “shortcuts” :
Tab Move to next control
In value boxes:
CTL+C Copy
CTL+V Paste
CTL+X Cut
CTL+Z Undo
On Drop-down, Spin, Push, Fader and radio controls:
PgUp Increase value (coarsely)
PgDown Reduce value (coarsely)
Up/Right arrow Increase value ( nely)
Down/Left arrow Reduce value ( nely)
On push-button controls:
Space Activate
Incident History
Each time there is a new Alarm Incident, details of the incident may be entered into a  nite-length list known as the Incident History.
The incident is entered into the list only if there is space in the list (where an expired incident can be removed), or where the new incident is more serious than the
least serious active alarm in the list (where that incident will be removed from the list).
The most recent incident is shown at the end of the list, older incidents being further back in the list. Incidents remain in the list even when the Alarm incident no
longer exists, and will remain there until the incident falls o the end of the list.
Incidents which no longer exist have their entries marked with the time which has elapsed since the incident was current (the elapsed time since the Alarm incident
ceased). Incidents which still exist (The Alarm Incident is still active) are shown as “**NOW**” instead of an elapsed time.
When the Incident history page is in view on the display, the Scroll buttons may be used to scroll among the history entries.
The list of incidents are stored so that they survive a power cycle.