We have recently attempted to control a Wakespeed WS500 (Non Pro version- no Bluetooth) with a CerboGX with DVCC. The use case is 3 x VoltGo Lithium 12 volt 200 Ah Batteries and a 12/3000 Multiplus on a boat. The idea was the Wakespeed WS500 was to be controlled by the DVCC. The CerboGX can “see” the Wakespeed but not control it using DVCC. I am guessing someone or many people have done it as I see no posts stating the contrary but we couldnt get it to work. Long story short, after a lot of research and reading, using the most convoluted programming arrangement I had ever seen, the DVCC control didn’t work. After phone calls and emails to the Dragonfly headquarters it appears the online documentation is wrong and it was agreed to simply use the unit as a standalone external regulator. I was told by Wakespeed the Victron DVCC cannot control the Wakespeed product. It seemed odd to me but it is what it is.
Ok, so in future we want to have a solution with DVCC when we use these batteries in a Marine application. We can try to use the Wakespeed Pro version utiliising Bluetooth programming capability or the Zeus external regulator with bluetooth programming. I am reluctant to engage again with the Wakespeed product based on my recent experiences but I guess the Pro version may be totally different.
Do any forum members have experience with these products and do you have a preference?
Many thanks.
I have a Victron system in our motorhome with a Wakespeed regulator. One of the tabs in the Wakespeed config app has a toggle for “Support Victron DVCC” and, as far as I know, it works. The alternator works along with the solar to charge the battery when driving. However, I have a Lynx BMS and Victron batteries, so perhaps DVCC is only available when using a Lynx? Just FYI, while I like the Wakespeed, I haven’t found the Wakespeed Tech dept particularly helpful at times.
@bobbiemartin many thanks for that reply. Yes the tab was certainly set but I was told that unless you have a Lynx BMS to provide the base control of the regulator, DVCC will not work. I find that interesting because we use Voltgo batteries and we rely on the CerboGx to interpret the VoltGo BMS status and change the charging equipment accordingly. It seemed to me that on that basis if the Wakespeed can be “slaved” to take the DVCC instruction, the type of Battery is irrelevant. I have no doubt the Wakespeed is a good stand alone regulator but for us the implementation of DVCC was not available.
I will echo the same as @bobbiemartin I have Victron NG batteries, Lynx NG BMS, WS500 and as stated in the configuration guide for DVCzc to work a shunt on the alternator output. I reduced CCL in the DVCC menu to below the alternator output, DVCC passed on the reduced charge current command to both the WS500 and the Victron MPPT. The other thing is you need o set a max current for the alternator on the first page of the app for DVCC to work.
I have also been underwhelmed by Dragonfly support.
There is a WS500 group on Facebook that I find has some good support including someone who is very knowledgable about the firmware(s).
@pwfarnell Thanks for the comment. Our confiirguration I would have thought would allow the battery BMS to inform the CerbogGX of Battery status. We hoped that would allow DVCC to control the Wakespeed. That is apparently not the case. Yes, we did configure the alternator maximum current but to no avail. We have used DVCC previously many times when using VoltGo batteries and it has worked like a charm.
The programming was in my view at best, fairly convoluted.
Download App to iphone or android. In my case, I tried an android phone (quite modern version) but it was not compatible so we used iphone.
Iphone or Ipad cannot connect to Wakespeed as IOS will not allow access to serial port.
Use App programming to share configuration file to folder in Windows PC connected to USB port of Wakespeeed
Launch batch file and it finds configuration file. Unfortunately if the App is in Standard mode and not “Expert mode”, the file shared is a .json file, not the .txt file the windows program needs.
Put App in expert mode and share configuration file. Now two files are shared both .txt and.json.
Use the .txt file to upload to Wakespeed.
The .Json file is the one used when the Android device is used to upload to the Wakespeed.
The documentation indicates the Windows method is current. It is actually deprecated and unsupported (advise from Dragonfly two days ago).
The lack of a .txt file for windows upload is only known because of questions via email to dragonfly and follow up phone calls. In my view the production of both .json and .txt files in Expert mode only and not in standard mode is not provided in ANY documention.
The programming is apparently much easier if using an Android device. It would be good if Dragonfly documention actually said that as it could have saved us a couple of days in the engine bay of a boat. We do have an android device but apparently the wrong version.
I am outlining this as it may help somebody else who is trying to do the same thing. I am not trying the bag any product but I am trying to establish a way forward so we can provide a good product and program it effectively for clients.
We were using Orion XS1400s but they keep blowing up.