VE.Bus Error 6: Error in DDC Program

Q&A and troubleshooting
, , , ,
1

Hi All,
Does anyone have any suggestions here?
Customer has a Cerbo-S, with ESS Assistant (018C) loaded.
MPPT is a SmartSolar 150/45
Battery is a Dyness DL5
Inverter is a MultiPlus-II 48v 5kw.

The system ran fine in testing, but when installed at the customer’s place, there are 2 issues (which might be related).

  1. the MPPT (connected via VE.Direct) wont show up on VRM or the console, but its running fine.
  2. after re-uploading the ESS Assistant config with some changes, i’m getting “VE.Bus Error 6: Error in DDC Program”

The mppt issue is not the cable (checked) or firmware (all are up to date). I’m putting this aside for now, but noting it in case its related.

The advice for this “VE.Bus Error 6” error ( https://www.victronenergy.com/live/ve.bus:ve.bus_error_codes ) seems to be;

Error 6 - Error in DDC Program
This means: error in an Assistant. To solve, follow these steps:

  1. update VE.Bus firmware in all devices to the latest firmware. Instructions here.
  2. download the latest VEConfigure and make sure it has downloaded all the latest Assistants.
  3. re-configure the system
    This error can also occur in newer firmwares when a VE.Bus BMS is connected (or dis-connected) and the assistant is not configured accordingly.
    Recovery: auto-restart once the error is gone.

#1, #2 have been done
#3 has been done multiple times.
There is only one assistant loaded, so “Error in an assistant” must refer to the ESS assistant.
The Dyness is connected by a cable with a special pinout (4,5 to 7,8) as per the dyness manual, and works fine, BMS info is populated in the VRM.
The GX is a Cerbo-S, and so rather than the data cable from Cerbo to battery being in the Cerbo BMS.Can port (which the Cerbo-GX has, but the Cerbo-S GX does not have), it is in the VE.Can port, and the port has been reconfigured to use 500kb/s as per the Dyness manual.

settings > services > VE.Can port, set CAN-bus profile to CAN-bus BMS LV (500 kbit/s)

I can’t help but think that an earlier uploaded ESS Assistant profile, where the battery system was erroneously selected as “System uses LiFePO4 batteries with a VE.Bus BMS” is what has messed up the config
This hunch is based on the advice “This error can also occur in newer firmwares when a VE.Bus BMS is connected (or dis-connected) and the assistant is not configured accordingly.”
In this case, i think the Cerbo is holding onto the the fact that a VE.Bus BMS was meant to be connected, and is now not connected (even though more recent ESS profiles tell the Cerbo to be looking for a VE.Can BMS, and it has found this and is working).

Does anyone have a suggestion?

RP.

2

Reset to defaults ( a number of times in a row) with the mk3
Or flash it with and older firmware and then re update the firmware.