
Software Release Notes
975-0604-01-01 Revision A 21
2. Improvements were made to the Xantrex Xanbus library to make the device
more robust on the CAN network in the presence of network errors. The unit no
longer resets itself at midnight, which was a temporary fix to the problem of
corrupted network communications. It will now detect any network corruption
and perform a soft reset of the Xantrex Xanbus functionality only, if a
corruption occurs.
3. A new feature was added to provide float time information to the user. Two new
home/status screens are available when the unit is either in Float or not
charging. One screen shows the time that the unit last entered float at, and the
other screen shows the duration of time that the unit spent in float that day.
These new screens will scroll if scrolling is enabled. The screens are hidden if
the charger is in Bulk, Absorption, or Equalize as the information would not be
relevant.
4. A simple fix (component value change) was made for the BTS to improve the
measurement circuits' immunity to switching noise on the DSP control board.
This minor hardware change allows us to set the minimum BTS temperature
reading to -35degC (previously we limited it to -20degC). Temperatures below
this threshold are interpreted as BTS Not Connected, and the value inserted
into the Temp field of the BattSts2 PGN on Xantrex Xanbus will be "reserved".
The minimum temperature threshold is now dependent on the hardware
version of the DSP control board. Currently, the control board is being shipped
at Rev 3. The boards version will be rev'd to version 4 (by modifying a voltage
divider circuit sampled by the ADC), so the -35degC limit will apply to version
4, and the old limit of -20degC will still apply if the hardware is rev 3 or older.
5. A minor bug was found where if the LocalOffsetMinutes field in the
DateTimeSts PGN was set to an invalid value (ie. PGN_SI_NO_DATA), this
offset still got applied when converting UTC time to local time. This invalid
value scenario should not occur normally, but if it does, this new firmware
build will ignore that field and set local time equal to the reported UTC time. It
ensures that the local offset is within +/- 12 hours (or +/- 720 minutes) before
applying it to the local time value.
6. The reset to factory default feature was triggering a bug that caused some
memory locations to be corrupted as they were over written due to an array
operation that went beyond the end of the array. The result of this bug was
benign as the unit reset shortly after being triggered. This bug was fixed
though in this version of firmware.
7. The restart pending timeout was set to 5 minutes instead of 3 minutes.
Komentarze do niniejszej Instrukcji