i want to over size my solar array for cloudy/winter days i have a SmartSolar 150/100 with 3kwp array with a Venus GX and a MultiPlus 3000/48 and i want to add another array on a BlueSolar 150/35 but i need to limit the total battery charge current, will the GX communicate with both MPPT's?
Hello. I installed a new Mulitplus 2 48/5000. DVCC limit charge current does not work. With the old Quattro, DVCC worked without any problems. Did I make a mistake somewhere? System setup: ESS with Cerbo MPPT chargers show "external control". greeting Paul
I have a Cerbo GX connected via VE.Can to a SmartSolar MPPT 150/70 VE.Can and a Lynx Shunt 1000 VE.Can. I have DVCC enabled as well as SCS, SVS, and STS. I have found that the MPPT changes charging states correctly according to the readings from the shunt. However, it is not compensating voltage according to the temperature reading from the shunt. The MPPT seems to be compensating from the initial ambient temperature as the standalone strategy. The MPPT has v3.05 firmware and the shunt has v1.08. Any help would be appreciated.
Good morning Victron Community,
I've noticed the addition in DVCC the ability to limit the managed battery charge voltage to a value of your liking. The way I understand it is the ability to override the BMS CAN CVL (charge voltage limit) value from the battery and to charge at the selected voltage specified in DVCC.
For this particular site we are using 2x Revov R100 batteries which are set up with CAN comms between the battery pack and Multiplus-II 5kVA. The battery's parameters are set up to charge at a CVL value of 55.5V as seen below
[image]however as a test I've lowered it to 54V in DVCC (and KEEP BATTERIES CHARGED) BUT I see that although it is trying to be close to 54V charging it still goes above that at 54.51V and triggers a High Voltage alarm on VRM (see below):
VEConfig file is also set up to charge at 54V for both absorption and float for this test (just noting as extra information).
Question for this post: Any ideas why this 54V limit is not holding?
Although the end result doesn't affect the batteries (safe voltages) the alarms in VRM are the problems.
I am struggling with the correct settings of the Venus GX, Quattro and MPPT to maximise the use of the solar panels. System setup:-Quattro 24/8000-720 Ah tubular plate battery (12 x 2 V cells)
-Venus GX, DVCC enabled (charge current limit at 70A, STS, SCS and SVS enabled)
-2 x LG Neon R 370 Wp solar panel (total 740 Wp)
I have been experimenting with the DVCC setting of the Venus GX and the configuration of the Quattro in order to maximise the output of the solar panels. So far I have concluded that when I use an assistant in the Quattro configuration that switches of the AC in, then I get a lot more out the solar panels (see screenshot 1 below). When I do not use the assistant and AC in is connected to shore, (see screenshot 2), solar output sometimes even goes to 0, but mostly around 50 W.
I have read and studied all manuals (Quattro, GX, MPPT) in english and dutch, read approx. 100 postings on the community site on similar subjects, but I still cannot find the best configuration for the Quattro and the DVCC setting.
The following is stated in the GX manual:
-" Enabling DVCC changes a GX device from a passive monitor into an active controller"
-" DVCC offers features such as a configurable system wide charge current limit, where the GX device actively limits the inverter/charger in case the solar chargers are already charging at full power."
-"Limit charge current. This is a user-configurable maximum charge current setting. It works across the whole system. MPPT Solar Chargers are automatically prioritized over the mains/generator."
My expectation was that by enabling DVCC with the charge current limit and STS,SCS and SVS enabled, that the GX would make sure maximum output comes from the solar panels and the output from the Quattro is reduced. But as shown by the screenshots this is not happening.
The only way that I was able to maximise the output from the solar panels was by using an assistant that switches off AC in of the Quattro, when the batteries are above SoC of 70 %. Once below 70 % it then reconnects AC in and batteries get charged to 90 %. After that AC in switches off again and solar panels take over the charging. This will work on sunny days, but a longer time without a lot of sun results in a lot of shore power being used to bring the batteries every time back from 70 to 90 %. Over a longer period of time this seems to use more electricity then letting the Quattro keep the batteries at 100 % continuously.
After having read more or less similar posts, I have the impression that if I lower the absorption and float voltage of the Quattro with say 0.2 V that the charging should behave as expected: solar charging takes priority and charge with high watts and Quattro charging is reduced. So I changed the absorption and float voltage of the Quattro with 0.2 V, but I still do not actually see the charging behave as expected, see screenshots (screenshot 1 with assistant, 2 without).
Any suggestion/help is appreciated, because I want to lower the shore power electricity bill and use as much solar power as available.
Hi i just installed 7 US3000 and followed this
all running latest alpha Firmware
According to the above install manual:
When the battery is correctly connected this will also set the following values automatically:
Venus Settings → System Setup Parameter Value
Shared Voltage Sense OFF
Shared Temperature Sense OFF
I did not get DVCC set to ON in the CCGX and no auto config took place on any devices... any ideas why?
the batteries are visible in the CCGX devices tab and no apparent errors.
I ended up configuring everything manually but curious why DVCC did not work and potentially if there is an issue i need to address.
thanks in advance.
I have just purchased LifePo4 victron smart batteries and a smart bms. Am I right in thinking that I use a non inverting remote cable to connect the bms to my cerbo gx and use dvcc mode to control the mppt.
also where does an Orion tr smart 12/12-30 go in this situation???
My thought was the Orion output goes to the ve+ post of the battery and the remote (h) connected to the bms, likewise the mppt output connects here also and is controlled via dvcc parameters.
I have a smart battery protect that I am putting between the ve+ post and my loads (bus bar) but see that it is one way hence the questions ref the chargers.
Hope this makes sense and thanks in advance for any constructive advice given.
Ich möchte gerne das DVCC in meinem cerbo Gx nutzen. Mit 2 Mppt victron Laderegler über ve. Direct, einem multi 12 v 2000 und 200 Ah Victron Ve. Bus bms lifepo4.
Nun steht in der Anleitung leider nicht ob er sich die temperatur automatisch aus der Batterie holt oder ob ich was machen muss. Ich möchte am liebsten den smart shunt installieren, da ich kein Display brauche wie beim 712. Einen Shunt brauche ich definitiv aber was macht da am meisten Sinn wenn man kein Display braucht? Oder mach ich mir da zu viele Gedanken? Geht mir nur um den Temperatur Fühler, den müsste ich ja extra bestellen, da der vom multi ja nicht an dem Shunt passt. Aber wenn die Batterie eh über das bus zum cerbo die temperatur weitergibt kann ich mir das ja sparen?
Gibt es sonst noch Dinge zu beachten bei dem DVCC?
Hello everybody, just registered for my first question.
im super new to Victron Components but i i have read a lot the last couple of month.
I would like to know if it is possible to update my Multi Plus with SN 19xx125, to a higher Version which work with the Cerbo Gx an allows me to limit the charge current via Victron Connect iOS or Mac.
The Cerbo Manuel tells me its possible with Firmware 422 to have access ti DVCC, but maybe wit Firmware 2xx it might be possible to show the Multi at least in the Connect App or VRM Network?
So far with my Firmware 125 of Multi, i have no access at all.
Before i try updating, i just wanna make sure, not to do stupid and unnecessary things.
Thanks for your help.
Multiplus 12/1600/70 (old microprocessor, sn starts with 19)
Cerbo Gx with Toch Display
Lynx Power In (Modified with Fuses like Lynx Distributor)
Smart MPPT 100/20
Smart Battery Protect
Should DVCC allow the MPPT to charge when sun is available, even when the Multiplus starts a charge due to low SOC early on a sunny day?
I've found the Multi will still be in absorption and the MPPT will go to float, but decides not to bother with any output, even though it could.
If i turn the MPPT charge off and on (in Victron Connect) it will try to charge for a few seconds but quickly cycle through Bulk-Absorption to float and give no output.. Only when the Multi goes to float does the MPPT start charging.
I'm using DVCC, + Ignore AC, both MPPT absorption and float voltages are higher than the Multi's
Could it be overheating? Today was hot and the batteries showed a peak of 37 Deg C, or maybe an incorrect setting, I.e. reduce the Ignore AC charge to end after bulk, but that's not ideal until we have more solar?
Or a symptom of the MPPT adaptive charge, either way i thought DVCC should tell them both what to do, as the Multi decided to use the AC In mains to charge when there was enough sun to cover the end of the absorption phase :( ..?
in december 2019 a great feature was added to the firmware 1.47 of the VE.direct MPPT chargers:
tail current mechanism improved: it can now use the real battery current. The current can be received via VE.Smart Networking (Bluetooth) as well as from a GX Device
This is a useful feature I'm using in most installations since it has been released. A week ago I tried to do the same with a VE.Can SmartSolar and unfortunately it doesn't seem to work at all.
The system consists of a CCGX, BMV700, Multiplus 5000 and VE.Can 250/100 SmartSolar. Other devices have been removed to keep things more simple.
There is no ESS/HUB assistant installed and therefore no active external control of the charger. Also no bluetooth smart network has been created and the firmware is up to date on all products. In the system the BMV is set as the default battery monitor to use and SOC syncs well with the multiplus. DVCC and SCS are enabled and SCS status is active. In the carger the absorption time is set to a fixed time with a tail current of 10A. If the current value falls below that value for more than one minute the charger should end absorption stage earlier and pass over to float. But it doesn't. Nevertheless DVCC is working with voltage, temperature and even current (tried a limit on the system). It seems the charger just has no use for the value "battery current" sent from the BMV and uses it's own current value instead to end absorption.
I have asked dealers, distributors and victron support, but all of them told me the charger would be able to do this without testing it. So I'd really appreciate if someone with a new CAN system (the old chargers can't) could test this. Of course a load must be switched on to have different current values between charger and BMV. I just want to know if this feature is working or has not been implemented yet and victron doesn't know about itself. If it works probably someone finds a mistake in my settings? I would prefer I made a mistake.
Thank you very much!
Recently got a system consisting of:
1x Quattro 48/3000/35
2x Pylontech US3000c
2x BlueSolar Charger MPPT 150/35
All firmware updates available via the VRM portal have been applied. I don't have a USB adapter, so I guess the inverter is on the firmware it came with.
The Pylontech - Victron setup manual says that the DVCC settings will be automatically populated. This was not the case for me.
What settings should I use for my setup?
DVCC -> On
SVS Shared Voltage Sense -> ?
STS Shared Temperature Sense -> ?
SCS Shared Current Sense ->
SCS Status shows "Disabled, external control"
When I enable limit Charge Current, it defaults to 50A. But I can change it.
It does look like the system sees the batteries correctly. Looking at the max charge current on the battery view, it matches the two batteries I have in my system.
While bulk charging batteries alone, PV output stays at about 1400 watts. When a 700 watt load is turned on on the multiplus, PV output mysteriously falls to about 900 watts.This occurs while still in bulk charging mode. One of my mppt's is throttled down to very low output even though it's in constant sun.
I'm running 3 Smart Solar MPPTs,BMV-712, a CCGX (DVCC on, SVS, STS, SCS on, Max charge off) and a Mulitplus compact connected via an MK3.
Any suggestions to fix this and keep the 1400 watt output from being throttled down?
Is the DVCC charge current limit dynamic?
Currently running a system with a Quattro whose charge current seems to be limited to 50A which was the DVCC limit. I changed the limit on the CCGX from 50 to 70A. But charge continues at the same rate. The unit is not limited by the AC input current. It is below 50% of the AC in limit.
The BMS has a 600A charge limit
So what is limiting the rate of charge?
Therefore I am wondering if the Limit is a dynamic limit or a set-point sent once at the beginning of the bulk sequence or other trigger. If so which trigger.
This error keeps showing up and then clearing, it has done so at least 10 times in the last couple weeks. All firmware is up to date according to VRM online checking.
3 BlueSolar Charger MPPT 150/85
2 Skylla-IP44 24V/30A (currently turned off)
It's getting pretty annoying to get an email every time this happens and then clears, I have looked through every post concerning this and see no solutions, anybody have an answer to this?
I stumbled upon the Buck-Boost DC-DC Converter and thought it would be great for my hybrid RV setup (12V OE alternator and battery, 24V auxiliary alternator and house LFP bank). But then I was very surprised to learn that it is not integrated into the beautiful Victron CAN ecosystem and thus cannot participate in DVCC.
In my dreams, I would have this device work bidirectionally: use up to 40A of current from the OE system to charge the 24V LFP bank and keep the OE 12V system topped up from the 24V bank when the engine is not running. Both being controlled by the REC Q BMS.
Is there any way to achieve even a portion of this?
In an installation with a CCGX and multiple SmartSolar MPPTs each MPPT with the same spec array and exposed to the same incoming solar what will determine the power produced by each MPPT?
Is it just down to small differences in physical installation? e.g. cabling or variation in actual panel output. Or is there something happening within the DVCC algorithm to control power output in each MPPT?
Dear Victron Fellows,
I have the following use case for two almost identical installations:
On the already existing 3-Phase ESS installation using MultiPlus II Devices, the battery should be charged in case of a grid failure and in time of insufficient PV power.
The installation already has the following devices:
A single phase 5kVA 230V Diesel inverter is available. It should be used to provide the power for the charger.
Is it possible to charge the battery using an additional MultiPlus II connected to the CCGX?
Can the Multi be connected to the CCGX and does it receive the relevant battery information BYD BMS information (DVCC)?
According to the following question it should be possible. And that is what I would expect and I think is the reason of DVCC.
Asking my dealer to verify the answer he told me that it is not be possible to connect the additional Multi to the existing CCGX, because the additional multi would need its own controller and needs to operate independent from the ESS system.
He suggested to connect the Multi by the relays (LINK). This would not be an preferred option for me because I would expect the charging process to be more optimal if it is controlled by the batteries BMS.
If the additional Multi can not be connected to the CCGX, would it be possible to add another Venus device and connect the CAN Bus to this device for retrieving the BMS information?
I have some curly questions on using a Cerbo GX and Distributed Voltage and Current Control (DVCC) to manage the system described below.
The yacht installation I’m preparing will have four Victron 12.8V 300Ah Smart LiFePO4 batteries, arranged in parallel. Their overall voltage will be sensed by a SmartShunt, connected to the Cerbo by VE.Direct. The batteries’ 3 Pole Balance Temperature & Voltage (BTV) cables will be daisy-chained to a Smart BMS CL 12-100. This BMS will control a Smart Battery-Protect 220 via its Load Disconnect terminal. The BMS will also control a Cyrix-Li-Charge 120 via its Charge Disconnect terminal. Three Smart MPPT 100/50 solar charge controllers will send current from 1200W of solar panels to the batteries through the Cyrix. The MPPTs will connect to the Cerbo by VE.Direct-to-USB adapters, into a USB hub and then to one of the Cerbo’s USB ports. Another job the BMS will do is regulate battery charging from a 115A alternator.
The system will include a MultiPlus 12/3000/120-50 inverter/charger, connected to the Cerbo by VE.Bus. Current from the MultiPlus will not be routed through either the Smart Battery Protect 220 or the Cyrix-Li-Charge 120, to avoid damaging those with flow in both directions.
I’ve read Victron’s explanations of DVCC, along with relevant discussions here in the Community. I’m satisfied it will work. What I think will happen (and not happen) is:
- the Cerbo will take the battery voltage sensed by the shunt and assess this in terms of what it was told the batteries are, during setup;
- it will look up its program library of how these batteries like to be treated and will instruct the MPPTs and the MultiPlus how they should serve up amps for charging, or draw on them for inverting;
- when the Cerbo assesses that the battery voltage reported by the shunt is getting low, it will tell the MultiPlus to stop inverting;
- the Cerbo will not be able to stop the DC loads from drawing upon the batteries, as it has no data connection to the BMS or the battery-protect. These two will use their load-disconnect linkage to cut the loads when one of the batteries says ‘Stop!’;
- if something goes wrong and the Cerbo doesn’t succeed in stopping the MPPTs from charging, the BMS will step in when the batteries ask it to and stop the charging via its charge-disconnect link to the Cyrix;
- however, if something goes wrong and the Cerbo doesn’t succeed in stopping the MultiPlus from charging, there’s nothing in the system or the setup to cut it off. I assume that the MultiPlus will not stop itself from charging, given it’s been told to be dumb and work under DVCC rules. Perhaps I could add a Cerbo controlled relay as a back-up, to switch off the MultiPlus if it goes feral?
Please set me straight if any of the above is off-beam.
Some aspects I’m less clear on are:
- will the shunt report the overall charging current from the MPPTs, the MultiPlus and the alternator, such that the Cerbo might instruct the MultiPlus and the MPPTs to ease-off or stop?
- if the batteries are full, does the BMS have the ability to throttle the current from the alternator? Checking … . Yes, it does.
- and last but not least …
… the Cerbo GX has a second pair of CAN-bus ports, called BMS.Can. Little is written about these, other than how they can be used to hook up other-brand CAN-bus BMS equipped batteries or BMSs. So how good would it be to have Victron lithium batteries that can talk directly to a Cerbo over CAN-bus? :-D Has Victron said these are on the way, or ruled them out for some reason?
The Pylontech documentation is silent on the SCS parameter:
Default is on. Must it be on? I will update it based on this answer.
Hi, I have a question around the behaviour of the Multiplus-ii when connected to Cerbo GX with DVCC on under the control of Pylontech US3000.
The US3000 manual has the following current limits:
Recommend Charge/Discharge Current (A) 37
Max. Charge/Discharge Current (A) 74
Peak Charge/Discharge Current (A) 100A@15sec
The Cerbo DVCC Discharge Current Limit is set to 37A since plugging in the Pylontech cable to the Cerbo. What will happen when the load on the Multiplus causes DC current to exceed 37A? Will it just shut down or alarm, or something else?
I really need it to allow the Multiplus to operate within the specification of the battery, to allow for short-term high load scenarios as this is an entirely off-grid install with solar and backup generator.
I have a parallel multiplus system, with a BMV712, and CERBO GX connected to a FLA battery bank on my boat.
I am interested in limiting charge current when the engine alternator is producing as well as the generator as to not exceed the charge current acceptance rate of my batteries.
A method that we have discussed is using a AUX input on the master multiplus to trigger a reduction in the output capability of the multiplus units. This aux contact would be tied to a “main engine running” signal.
I am certain that this method would work, but there might be a better way.
Could I turn on DVCC on the CERBO GX and have it limit the charge current by using the value supplied by the BMV712?
That would be the best method in that it would be dynamic.
Please let me know.
I have a Multiplus (Easyplus) 12/1600 along with a Cerbo GX and other stuff.
Because I want to use the BMS Assistant on the MP, I had to use the Temperature Sensor input for the control signal (the MP 12/1600 has no other Aux input). This works well and I can control the Charging feature exactly as I want with this assistant.
I was fine with doing that as I could use a Temp Sensor that was connected to the Cerbo GX instead and enable DVCC and the STS feature. That seems to work fine for the SmartSolar MPPT and that picks up the temperature from the sensor correctly, but the MP shows the temp reading as either "NaN C" or "20 C".
I have two temp sensors on the GX and I have tried setting the Sensor in the STS selection to either one of them and it makes no difference to the MP - although the MPPT sees the change (and neither are 20 C either).
Any ideas why the MP is not picking up the Temp Sensor data from the Cerbo GX?
Hi guys, wondering if anybody can point me in the right direction on a little MPPT VE.Direct problem.
I have a small Multiplus 24/5000 grid-tied system running great with BMV-700, Venus GX and off-brand DC coupled PV charger with 200Ah of Li-Ion. I've recently added another PV string on an MPPT 100/50 Rev2. Everything has latest firmware as of this post.
The MPPT is working great, except that every day its output is down by a few hundred watts. Heres the wierd part - It comes good when I disable DVCC then imediately re-enable it again. It remains at full output until the next day. Here's a video showing this:
In this video you can observe the output is down from what it should be. After disabling DVCC, the MPPT settles on a much higher output, with most going to the battery (huh? already 100% soc) and a little extra going to the grid. When DVCC is then re-enabled, the MPPT continues to produce full power, and the excess goes correctly to the grid. That is, until the next day.
The utility connection is a 10A circuit, so export is limited by the Multiplus to 2400W. When there is excess solar and the grid circuit hits 10A export, DVCC correctly backs off the MPPT as intended, so the battery is not overcharged past 100% SOC and the 10A grid circuit limit is observed - great.
My suspicion is that there is a bug somewhere in this code which is somehow causing the MPPT to stay backed off even when it should be instructed to return to full power output. When this condition is in effect, the charge voltage target in the MPPT is observed at 27.3V (while battery remains at 27.1V, as observed in the MPPT's menu on the venus GX). The mppt *should* be going flat out, but somehow remains backed off.
No battery current limits are ever being hit, the battery temp is mid 20C at all times, wire gauges are all correctly sized and nothing is getting hot.
Could I please have your advice on configuring and switching on a newly installed DVCC system in a yacht? Questions at the bottom. First, a system description. The devices involved are:
- three 12.8V Smart lithium batteries, in parallel as the house battery bank
- Smart BMS CL 12-100, to keep the diesel engine’s alternator safe from overheating
- Smart Battery Protect 220 for load disconnect
- Smart Battery Protect 100 for charge disconnect of MPPT output (might change to a 220)
- Smart Shunt
- Cerbo GX and GX Touch 50 display
- MultiPlus 12/3000/120 - 50
- three 100/50 MPPTs with three x 400W solar panels
There are also two battery chargers connected to the positive bus-bar, being:
- an Orion-Tr 12/12-30 battery to battery charger, for charging the engine start battery, if needed
- a Sterling 12-24 charger for charging the 24V battery bank for the bowthruster
Data connections between the devices are:
- VE.Direct cable between the Smart Shunt and the Cerbo GX
- VE.Bus between the MultiPlus and the Cerbo GX
- VE.Direct-to-USB between the MPPTs and the Cerbo GX
And of course there are:
- load disconnect cable from the Smart BMS CL 12-100 to the Smart Battery Protect 220
- charge disconnect cable from the Smart BMS CL 12-100 to the Smart Battery Protect 100
I’ve read the DVCC information in the Color Control GX Manual. I’d happily read more information if it was available. :-)
How do the following configuration steps look to you?
- I need to activate DVCC in the Cerbo GX. Easy.
- I’m thinking I will activate ‘Limit charge current’ at first, to keep charging calm, at 50 amps max
- Shared Voltage Sense (SVS) comes on by default when DVCC is enabled. From Section 4.4.2 of the Manual, I gather the Smart Shunt will be the source of the voltage measurement, rather than the MultiPlus. This makes sense, so I think I’ll leave SVS on.
- Shared Temperature Sense is a problem. The system doesn’t have a temperature input at present. The batteries in the bilge are likely to be colder than the distant MultiPlus, a possible temperature source. I think I will turn STS off, until I can connect a sensor directly to the Cerbo. Which sensor?
- Shared Current Sense (SCS). Section 4.4.4 of the Manual is difficult to understand, but I get the impression I should turn SCS on, so the MPPTs can be configured to use the Smart Shunt’s current measurements.
Could I please have your thoughts on this approach? I will of course be working with the installer, however, he is not a Victron expert.
In this configuration (RV) with a main battery and a truck battery both connected and charged by one Multi Plus. BMV-712 monitors the main battery voltage and the truck battery voltage. DVCC enabled on the CCGX.. With all connected, it works as advertised. However if for some reason the main battery is disconnected from the camper DC system (BMS action), the Multi Plus gets confused seeing the main battery (now disconnected) voltage and trying to power/charge the rest of the system along with the truck battery. This of course causes the Multi to create significant voltage swings.
Is there a way of telling the BMV-712 to switch from sharing the main voltage to sharing the truck voltage instead as it is the one getting charged?
Any other suggestions?
The BMS could in effect via a relay swap the voltages sensed by the BMV-712. That appears to me the only alternative. I would rather not do that.
I couldn't find anywhere the re-bulk voltage offset threshold that the algorithm of a Multi (MP-II, or Multigrid, whatever) in an ESS system with DVCC enabled with unmanaged batteries (nickel-iron batteries in our example) is applied ? For example, we have a bank of 24V NIFE with 31.5VCC for absorption, with the following parameters :
The bulk-abs-float cycle starts all over again once the voltage of the batteries drop below the float voltage, or below a pre-determined voltage threshold, or minus a certain % of the float voltage, andfor example for how long ? 1 min ?
Couldn't find the info on the Victron documentation (it is clear for MPPT charging algorithms though, but not for internal Multi's DVCC algorithms). We've set up those settings depicted above in order to be able to restart a full charging cycle with a 2h absorption cycle, if the voltage of the array drops below a certain limit (2x times a day max = 0.5 days absorption interval). It would be helpful to manually override the threshold, just like you can do when you have non controlled MPPTs charger (in which you can specify the re-bulk voltage). In any case, knowing the default value would help us in having more prediction over the conditions that trigger a new charging cycle.
Based on our experience and .csv log, it seems like the Multi restart a full charging cycle once the battery voltage drops at the nominal voltage (~ < 25VCC). Can anyone confirm this ?
Thanks in advance for your help !
Hi and thanks for reading this.
I have a REC-BMS (Victron version) connected to a Raspberry PI3 with CAN-HAT running 2.60 which has worked very fine for some weeks. Tonight I connected a Multiplus 12/1600/70 via MK3-USB cable to the PI. I also have a BMV-712 connected via a VE.DIRECT cable using the same shunt as the REC-BMS.
All devices appear on VRM Remote Console and look fine. The battery charged to 14.2V just fine and current quickly tailed away to zero-Amps. After a short period of use, an Automatic Monitoring 'DVCC Firmware insufficient alarm: Warning' appeared.
My Multiplus is an 1906 model running firmware 209; could this too old for REC-BMS control? I see a Victron helpful stating 19xx model is supported. Also have two-signal lithium assistant running if that makes any difference.
Some VRM screenshots attached somewhere below.
I have been working on a couple of project involving MG batteries with BMS, Quattro and CCGX controller. I have read the DVCC section of the CCGX manual and if it greatly help understand the basis of DVCC some details are left out and I need to reassure our customers.
Some system also includes Blue Solar Ve.Can controller(150/85), Skylla and /or Skylla-i
System are set per recommended settings in the DVCC section of the manual.
The Manual mentions that when DVCC is ON the Ve.Bus device and MPPT system are "controlled by the BMS". and they follow the CVL, CCL and DCL sent by the BMS.
Q1) The BMS does not send the data to the device directly since they are not on the same network. The CCGX appear to be redirecting the references. Are each device directly controlling the charge voltage based on the CVL or is the CCGX adjusting the Current limit to each device to meet the CVL?
Q2) In a case of the BMS controlled system, is there a need to set Absorbtion/Float voltage or are those numbers ignored by the Device?
The Solar charger strictly indicate external control and if the BMS communication is lost they seem to Stop charging. So it seems that the setting are ignored. Are they?
The Case of the VeBus device is not that obvious. External control state does not exist. It seems that the LED are either Bulk when some charging is happening and Absorbtion when the charging stops or oscillates. Never seems to get to float which is disconcerting for some of our client.
Is this the intended behavior?
Is the absorption voltages set in the charger profile totally ignored or used as "Limits"?
Should the BMS communication stop how will the system react? Will the Quattro stop charging or inverting?
I have three different Victron DC systems and had plans to add the Orion TR Smart to two of them. I purchased a 12v 30a non-isolated Orion TR for my RV and to bluntly put it.. I'm not impressed.
This device has no ve.direct connector, what is the logic behind this decision? If I've invested the money to control every aspect of my Victron system through Venus, why would this device be headless? There also seems no way to add it into the bluetooth VE networking protocol.
I have come to rely heavily on DVCC for my dynamic charging needs, so the fact that this device can only be controlled through bluetooth with an extremely limited set of configuration options is frustrating.
The bluetooth radio in this device is abysmal. I can control every other Victron Smart product meters away from them, whereas this Orion TR doesn't even broadcast outside of the vehicle it's in. I have also seen similar complains in the ratings sections of a retailer and on this forum.
Has anyone used the external relay control features of their multiplus or possibly bmv-7xx to provide at least some type of logic-based control to their dc-dc charger?
I feel like this device was rushed to market. I am struggling to see the value in the Orion TR, I am considering returning this item. Does anyone have any insight if there are firmware improvements scheduled for this product or if I'm missing something here?