Version 1.56 BETA Release Notes: Version 1.56 Beta fixes various issues with the virtual battery driver and also adds new features to the driver as a whole. Note: we will only be supporting venus OS 3.41 and newer going forward so you must be on this version or higher.
- IMPORTANT: Version 1.56 Beta fixes a major problem that can happen if you select the Test Heating Pads (SFK-275EX & SFK-300HP and 200-V3 BMS) in the SFK app while also connected to a Venus OS device, this would result in the heating pads keep running beyond the 15 seconds and could only be stopped if you disconnected the battery from the venus OS device and clicked on test heating pads again. While rare, it could result in a run-a-way heating problem. It is advised you upgrade to this version IMMEDIATELY or make sure you do NOT click on the run heating pad test while connected to a Venus OS device.
- Users can now set the Float Charge Voltage by setting the max value in the driver, this will allow you to setup a custom float value if you do not want to use the default 14v
- Users can now set the Max Charge and Max Discharge value in amps, this will set how each connected battery will work with the driver. (The virtual battery will still combine these to show the total value)
- Note if any of these items is changed you will need to PERFORM A REBOOT on the venus OS device for these to take effect.
- Fixed device battery setup issues in the virtual battery, if you change the battery setup from parallel to series, you will need to PERFORM A REBOOT on the venus OS device for these to take effect. We also fixed a bug that would default back to parallel connection if a device was disconnected in a series configuration.
- Fixed a bug where the driver would necessarily look for the BMS device’s serial number repeatedly, this should improve BMS and driver stability and performance. Another correction was done to the default device name where the batteries would show up with a strange character in front of the device’s name (a little rectangle)
- Known Issues: a compatibility issue has been discovered with the BMV-712 device and other VE direct devices when it comes to temperature, their appears to be a conflict where they are both writing to the 0 ID of the temperature sensor, this affectively makes the Virtual Battery Temperature appear the same as the BMV-712 shunt temperature, we will be resolving this issue in the next 1 or 2 driver updates.
