Balmar SG205 Manuel d'installation et d'utilisation - Page 13
Parcourez en ligne ou téléchargez le pdf Manuel d'installation et d'utilisation pour {nom_de_la_catégorie} Balmar SG205. Balmar SG205 19 pages. Battery monitor
Imprimer la page
To set an alert, ensure you have the correct SmartShunt selected (the device
name shows on the top bar) and select ALERTS from the CONFIG menu.
First, select the type of alert you wish to configure, then if you wish to configure
for a high or low value. Once selected, you can change the value one digit at a
time, using the same method used to configure the battery capacity.
NOTE: When a HIGH value is configured, the parameter must exceed the
set value for the ALERT to be triggered. When a LOW value is configured,
the parameter must fall below that value for the ALERT to be triggered.
24
Faults
Faults are triggered when specific values have been passed that may have
an impact on safety or the health of the battery. For example. draining a
battery down to less than 5% SoC will trigger a fault, as it can adversely
affect the life of a battery. Exceeding the safe current carrying ability of the
SmartShunt will also trigger a fault. Faults can help a user identify behavior
that will shorten the life of a battery. Faults can only be cleared from History
with a Factory reset.
The values used to trigger Faults are contained in the Appendix named Fault
Thresholds
Fault History is accessed from within the History Sub-menu, see History.
NOTE: The High Voltage Fault threshold for flooded batteries may be
higher than a safe voltage for operating electronics and other equipment.
This is to allow for the equalization of batteries without triggering a Fault.
For this reason, it is important to set and use a High Voltage Alert to let
the user know when potentially battery-damaging voltages are sensed.
Comparing Faults and Alerts
Here is a summary of some differences between Faults and Alerts:
1. Alerts are user-configurable; you can enable and disable alerts and
change their trigger points.
2. When an alert condition has passed, the alert does as well.
3. Faults are not user configurable.
4. Faults show a time since occurred, duration for the latest fault, and the
number of total times that fault has occurred.
5. Faults have history. When a fault is viewed, it is cleared from the screen.
The parameters for the last instance of a fault and a counter showing the
total times that fault occurred are stored.
25