Maretron DSM150, User Manual

Page: 242 / 274

DSM150
User’s Manual
Page 226 Revision 1.4.18
8.3.7.2.2 Trigger Configuration
Figure 261
– Trigger Configuration – Low Alert
Re-trigger Period
– When you accept an alert, it will change to the “Accepted” state, and
annunciators that are sounding for that alert will stop sounding. If the condition which caused
the alert remains true after the amount of time in this field, the alert will return to the “Active”
state, and annunciators will begin sounding again for that alert. If a value of 0:00 is entered,
then the alert will never re-trigger.
Alert Set Point
– If the value of the parameter being monitored falls below the value in this field,
the alert will become active.
Alert Set Delay
– The parameter being monitored must fall below the Low Alert Set Point value
for longer than the time in this field in order for an alert to become active. This can be used to
prevent false alerts caused by parameter values that briefly have a value that would cause an
alert but quickly return to the normal value range. The value is entered as minutes:seconds. If
only one number is entered, it will be interpreted as seconds.
Alert Clear Point
– If the alert is active and the parameter value rises above the value in this field,
the alert will become inactive.
Alert Clear Delay
– The parameter being monitored must rise above the Low Alert Clear Point
value for longer than the time in this field in order for the alert to become inactive. The value is
entered as minutes:seconds. If only one number is entered, it will be interpreted as seconds.
In this example, the set point may be described in more than one unit, so additional fields have been
supplied so that the user can select the units of depth. Changing the units of the set point will also
change the units of the clear point. The initial units displayed in these fields will correspond to those
set in the Units Dialog (see section 5.2.7).
8.3.7.3 Trigger Type is Data Unavailable Alert
The Data Unavailable Alert can be used in conjunction with other alert types when you need to know
if a particular parameter is no longer being received
on the network or is flagged as “not available” by
the transmitting device. For instance, you probably would want to use a Data Unavailable Alert for the
Depth->Current Depth parameter, since it would be advisable to know if the depth sounder were to
stop transmitting a depth reading or became unable to determine the depth due to fouling or some
other reason. On the other hand, if you were to set a Data Unavailable Alert on Engine->Engine