I have an alarm rule on my BMV, in VRM, set to trigger when the Time To Go value is less than 5 hours. The rule works well enough and allows me to trap high-load scenarios before they deplete the batteries too much.
However, when the system is charging, the time to go value is set to "infinite", but on VRM, it sees that value as 0, which is less than 5, and it erroneously triggers the alert. Even worse, it sort of reverses the logic when I'm discharging, thus clearing the alarm.
Is there a way to get around that behavior?
Also, some of the trigger points for several alarms on VRM don't even make sense. There are several examples where alarm trigger value make no sense at all. Like why necessitate a "high" value for time to go -it's a "required" value so I fudge the value at 1000.
If I've got 1000 hours to go on my batteries, I don't want an alarm on that, except perhaps one hooked up to streamers and ticker-tape :)