Differences

This shows you the differences between two versions of the page.

--- battery_compatibility:freedomwon [2020-08-05 12:08] – [CAN Bus Wiring] added CAN 2 terminals detail. warwickchapman
+++ battery_compatibility:freedomwon [2020-11-28 15:12] – [CAN Bus Wiring] - added info for Cerbo boekel
@@ Line 113: / Line 113: @@
 **Note:** In the case of the Venus GX or Octo GX, if the VE.CAN ports (RJ45) are being used by MPPTs, the secondary CAN bus needs to be connected using the green terminal blocks.  If you require any information on how to do this, contact Freedom Won support at support@freedomwon.co.za
+**Note:** When using a Cerbo GX use the 'BMS-CAN' port for the battery and configure that port to 500kpbs, the Cerbo GX has RJ45 ports for both CANbus channels.
 If multiple batteries are installed in parallel the second RJ45 socket is used to link the next battery in the line onto the CAN Bus network. The termination resistor is installed in the last battery in the CAN Bus line. Refer to Lite installation manual for further information.
@@ Line 138: / Line 140: @@
 The MultiPlus or Quattro devices must be correctly configured for operation with the Freedom Lite as follows (note that settings not directly related to the Lite are not mentioned here and must be referenced in the [[https://docs.victronenergy.com/veconfigure.html|VEConfigure manual]]).
-The GX-device must be configured to use the battery monitor provided by the Freedom Won battery and disabling the MultiPlus or Quattro battery monitor ensures that the correct battery monitor is used:
+The GX-device will use the battery monitor provided by the Freedom Won battery by default:
-☛ Disable Battery Monitor (the VE.Bus battery monitor is not required with a CAN Bus Lithium battery)
+☛ Since Venus OS 2.60, it is no longer necessary to disable the Battery Monitor. Whether it is on, or off, you can ignore it.
-**NOTE:** It appears that the final step in this process, enabling ESS, turns the battery monitor back on.  Please check the General tab on more time once you've complete the process before you save the configuration or upload it.
-{{:battery_compatibility:freedom_won_ve_config_1.png?direct&600|}}
 ☛ Set the Low Shut-Down, Low Restart, and Low Pre-alarm voltages.  The Low Pre-alarm only activates the low battery LED on the inverter and serves no other purpose in this setup. The Low Shut Down and Low Restart voltage settings are usually overridden by the commands from the Lite but offer redundancy in instances of loss of communication and therefore should still be set correctly.
@@ Line 195: / Line 193: @@
 ===== GX-Device Venus OS Configuration =====
+NOTE:  Venus OS 2.60 has important updates to the support for FreedomWon Batteries and it is strongly recommended that you make use of 2.60 or newer.
 It is very important that the following settings are entered correctly for proper functioning of the Lite communication interface:
-☛ Settings → Services → CAN-bus Profile → CAN-bus BMS (500kbit/s)
+☛ Settings → Services → VE.CAN port → CAN-bus Profile → CAN-bus BMS (500kbit/s)
-//**Note**: For systems with VE Can MPPT’s, select 250kbit/s and ensure Lite profile is also set for 250kbit/s (check with Freedom Won or your Freedom Won distributor).//
+//**Note**: For systems with VE Can MPPT's and only one CAN-port (CCGX), select 250kbit/s and ensure Lite profile is also set for 250kbit/s (check with Freedom Won or your Freedom Won distributor).
+All other GX devices have dual CAN-ports or a CAN-port that only supports 500kbit/s (GX version of inverters) so on those systems BMS-CAN should be set at 500kbps//
-{{:battery_compatibility:freedom_won_venus_1.png?direct&600|}}
+{{ :battery_compatibility:venus-1.png?direct&600 |}}
-☛ Confirm that the Freedom Lite is showing in the device list as per below
+☛ Confirm that the Freedom Lite is showing in the device list (top of the menu structure) as per below
-☛ Settings → System Setup → Switch on DVCC and SVS, check that BMS Control is “On”
+{{ :battery_compatibility:venus-2.png?direct&600 |}}
-{{:battery_compatibility:freedom_won_venus_2.png?direct&600|}}
+☛ Freedom Lite → Parameters → Confirm that the Charge Current Limit and Discharge Current Limit are as per the Lite specifications (Note: if the battery is fully charged the CCL may be reduced. Check that the voltage target is within the range 54.8V to 55.8V (Note: below about 95% SoC the value reflected should be 55.7 or 55.8V. For a fully charged battery this value should range from 55.0V to 55.8V depending on the state of balancing of the cells in the Lite.
-{{:battery_compatibility:freedom_won_venus_3.png?direct&600|}}
+☛ Confirm that DVCC is forced on at: Settings → DVCC
-☛ Freedom Lite (device list) → Parameters → Confirm that the Charge Current Limit and Discharge Current Limit are as per the Lite specifications (Note: if the battery is fully charged the CCL may be reduced. Check that the voltage target is within the range 54.8V to 55.8V (Note: below about 95% SoC the value reflected should be 55.7 or 55.8V. For a fully charged battery this value should range from 55.0V to 55.8V depending on the state of balancing of the cells in the Lite.
+{{ :battery_compatibility:venus-3.png?direct&600 |}}
 ===== MPPT Configuration =====
-The voltage setpoints on the MPPT’s must be set to 55,8V for bulk and float with equalization disabled. In order to do this on the Ve CAN MPPT’s select the User Defined option 8 battery type as this allows adjustment of the charge voltage setpoints.
+The voltage setpoints on the MPPT's must be set to 55.8V for bulk and float with equalisation *disabled*. In order to do this on the VE.CAN MPPT's select the User Defined option 8 battery type as this allows adjustment of the charge voltage setpoints.
-Adjust the maximum current on the MPPT’s to ensure that the combined total charge power cannot exceed the maximum rated charge current for the Lite or Lite’s in the system.
+Adjust the maximum current on the MPPT's to ensure that the combined total charge power cannot exceed the maximum rated charge current for the Lite or Lite’s in the system.
 ===== Troubleshooting =====