0.19 FW

-Official HW 1.0 hardware support, since it uses slightly different hardware components, which affect analog readings, there is an internal check to see what string is recorded in the flash OTP section and based on that use specific internal multipliers for analog conversion results. If no recorded data found in the OTP, the BMS defaults to <1.0 HW setup, so it should function properly with earlier board revisions.
-Added a restart charging timer "restartChargTime"($43), which allows the charging to automatically restart after the configured time has passed since a successful charging ending. Will very likely add a restart times counter in 0.20 FW to limit the maximum amount of charging restarts allowed.
-Started working on parallel mode operation, where it's possible to charge multiple packs from the same charger in a controlled fashion, even if the packs are of different capacity, but it's not quite official released yet.
-Heartbeat function for parallel mode operation. Unit broadcasts it's pack data and charging status.
-Some fixes and improvements for charging algorithm
-Bigger TX-buffer for faster USB serial printout
-Updated some parameter descriptions for serial terminal

0.18

-NTC temperature limit fixed to use the NTC min and max limits, instead of pack voltage min and max
-Initial license information added to the source files
-Serial terminal printout improved. Battery voltage, charger voltage and charging current values now show lowest-latest-highest measured values by the internal fast sampling.
-Charging ending flag now indicated
-Fault logging has been updated along side with fault handling.
-New feature, wake-up by CAN-traffic

Known bugs:
-When BMS is woken up from low-power mode by charger, initial charging attempt will result in a fault state, but will recover after the fault wait time, so not a critical bug.

0.17c

-Made cell voltage calculation interrupt resistant, which caused sometimes weird cell voltages to be read on connected CAN devices

0.17b

-Changed the CAN TX retry implementation slightly to a more robust one

0.17a

-Fixed the problem causing the majority of TX CAN frames being dropped from the Lite

0.17

-Fixed CAN RX activity cyan LED tick/flash to be much more visible and therefore usable
-Parameter saving/loading to/from overhauled
-Bootloader preparation
-Parameters from this version onward that don't need to be returned back to default values after FW upgrade should be retained if they don't need defaulting
-CAN ID should now stay the same even between FW upgrades

0.16

Pre-release, not necessary stable
-Save sender CAN ID and pass it to packet handler
-USB VCP test fix for Win10
-Parameter default value auto-loading if saved non-volatile parameters were saved with a different FW version then currently running with
-Improved current monitoring at the start of charging

0.15

-small fixes
-added CanRxRefreshActive "$39" parameter to be configurable through CAN

0.14

YOU NEED TO LOAD DEFAULT PARAMETER VALUES AFTER FLASHING AND POWER CYCLE OR SOFT BOOT AFTER WRITING YOUR OWN PARAMETERS

-Added a new parameter canRxRefreshActive, which allows to extend the activeTimer up to a point by received CAN-frames
-Fixed a bug that would terminate the start of charging prematurely and cause the state machine to bounce between starting charging and ending charging
-Internal change to how runtimePars.activeTick and runtimePars.storageTick were incremented and monitored

0.13 - CAN traffic switched to be ISR-based

If running FW 0.12, no need to load default parameter values after flashing.
-Fixed CAN TX misbehavior that caused multiple same frames to be sent instead of a single one