Two (related) issues after updating to 2.9.6 firmware


  • Hi All,

    I've been happily running my ABMS for several years now, in an all up Victron+REC+Wakespeed configuration. During that time, I've only updated the firmware on my CerboGX, leaving the REC alone and only updating the Wakespeed once for the initial Victron integration.

    Anyhow, we're in the process of doing a repower, and bumping up to a 120A alternator, so I figured that it was time to do a "great firmware update" but I've run into an issue with the REC.

    Previously, as my SOC approached 100% and the cell voltages approached CHAR, the REC would modify the DVCC parameters and taper off the charge current way down, then eventually it would modify the Voltage Limit down to 13.9V.

    The behaviour I'm seeing now is that it keeps running at full current (set for 150A on my system) until a cell hits the charge voltage, then it disconnects the main relay and sets the target current to 0A, and never drops the target voltage. 

    I have set MODE 2, so it should be in Victron mode (with separate OV and UV contactors). It's communicating as I can see the status on my Victron setup.

    My settings are as follows:

    CMAX 3.9v (Way too high, but put it there so it wouldn’t be a factor while I tested the system)
    MAXH 1.5e-1
    CMIN 2.5
    MINH 1.0e-1
    BVOL 3.58
    BMIN 3.45
    CHAR 3.65
    CHIS 2.5e-1
    UBDI 1.0e-2
    CFVC 5.0e-1
    RAZL 2.5e-1
     
    For the moment, I've put in a manual DVCC limit of 13.9V, and that keeps the system stable. But I would like to get the automation working correctly, especially before I throw my shiny new 120A alternator at system.
     
    Any thoughts or things to try would be greatly appreciated. 
     
    Edit: I've since modified the values to try the values suggested by @Ben in another thread, setting the BVOL to 3.55 and CHAR to 3.52, and it's still cutting off the main relay when a cell hits CHAR, and never ramping the charging down.
     
     Second edit: Apparently I can't type. CHAR is 3.52 not 3.62


  • So after an email from Tine, I went and checked my system. Turns out for the past 3 years I've had my contactor leads flip-flopped. RE1 was controlling the contactor on the charging side of the world, and the Main Relay was controlling my DC loads. 

    How ever, that doesn't explain why RE1 is now acting like a "Charge enable" relay rather than a low voltage disconnect. That's the next mystery to figure out. However, my DC load contorl is through a Victron Smart BatteryProtect, so I'm running that autonomously for the moment, and just have the one Contactor going. 


  • Hey Hans, glad you're making progress.  In the latest f/w version there is no longer a separate 2 relay version.  Using the "Tasks" page in the Wifi module you can set it to drop out on low voltage.  That being said, with the enhanced CANBus integration the convention is to let the BMS systematically enable/disable/modulate the other Victron devices using DVCC and retain only a single relay as a critical shutdown for bothi hi/lo trips


  • @Rick Yeah, looks like I'll have to pick up the wifi module. 

    In this case, it's for the rest of the DC system on my boat (lighting, VHF radio, AIS transponder, instrumentation, etc...). Right now I have the BatteryProtect set to cut out the DC system on its own when it hits the low voltage threshold, it was just nice to have it all integrated.


  • @Hans to have a battery protect, as low voltage discontactor, you need to know, IF only one cell comes low, the Battery Protect will not "see" this.

    If your cells are perfectly balance also at the low voltage range, the Battery protect will work fine. But often you see one cell is earlier low as other, and the Battery protect will NOT switch off the load, OR too late!!


Please login to reply this topic!