The dbus-fronius log shows the init messages. And the readout seems to be ok. My feeling is the limit is just not set. Maybe caused from another setting. Is the source code where the setlimit is called availlable? I found the dbus-fronius repository and set the registers with an c program, this is working. So i think only the limit call is missing…
1 Like
It sounds a bit like what I described here:
It almost works but not quite.
As a quick and admittedly dirty workaround, I set up a very simple Node-RED flow. I’d never used Node-RED before, so there are probably better approaches—but this one works:
This flow reads the limit that Venus OS calculated for me and passes it to the inverter via Modbus. It works like a charm. For my Kostal Inverter, it’s register 832.
So yeah—almost working.
Feature request for Victron: for Kostal inverters, Venus OS should allow specifying a Modbus port other than the default (502). That would make integration a lot easier.
And of course investigate why the limit never arrives at the inverter as in your case.
If anyone’s interested, I’m happy to share the full setup I used to get my Kostal Plenticore 10 G2 to limit AC feed-in.
I’m looking to add a hybrid solar inverter to our system (actually installed in our 14yr old Kangoo ZE connected to its secondary HV battery but that’s a different story/project altoghether). I"m following this topic with interest and wonder whether there are any (community based) recommandations, comparisons between brands, types and their compatibility with the Victron platform available. The idea is to be able to charge by solar at work (DC, solar), and plug in at home (AC to MP-II )
Hi,
void SunspecUpdater::onPowerLimitRequested(double value)
{
const DeviceInfo &deviceInfo = mInverter->deviceInfo();
double powerLimitScale = deviceInfo.powerLimitScale;
qInfo() << "POWER LIMIT SCALE" << deviceInfo.powerLimitScale;
if (powerLimitScale < PowerLimitScale)
return;
The powerLimitScale for an SE17K is never set. It is 0 here, so the modbus command is never set because its ends on this if …
If i set it to 100 everything is working like expected.
I’m seeing my three newly installed Solax X1-Smart-G2 inverters showing up in the Cerbo GX inverter menu. However, there is no data coming in. That is probably due to the fact that they are not Sunspec compliant but rather Modbus TCP only. I have a document with the communication protocol and all registers. How could I go about adding support for these inverters? My priority is just viewing data, but extended support for limiting would be useful as well.
Solax Power X1-SMART-G2 single phase inverter Modbus-RTU comms protocolV1.2.pdf (1.4 MB)
Everything worked fine untill enphase updated to Version 8.3.5052 the integration stopped working.
after update to Software Version 8.3.5167 the integration is ok again.
Did you recieve an answer from Enphase Support? Or is the gateway running on an older software version, as @Paulh suggested?
It’s not a problem, the Victron manuals do have a good quality and there are a lot of Victron manuals of all sorts of installation, hardware, software, etc. As a newby I like to have a manual how to connect my AC PV to the MultiPlus II. The information is somewhere out there on the internet, it makes it easier just to have 2 A4 sheets with instructions.
My problems started after unlocking modus funtionality by enphase support in firmware version 5167. Because it didn’t work I switched modbus off en ET112 on again which resulted in a steady situation. Enphase support did some reseach and changed stuff I suppose, I noticed some ‘solved errors’ on CT measuring after which Enphase asked me to switch on the modbus which I did and it is working steady for almost a week now, no lost af signal anymore ! I asked Enphase what they had done but got no reaction.
I tested ‘zero feed in’ which works nice. After I switched it on PV is switched off and grid goes to zero after a while PV is comming in and slowly starts to fill the battery.
I did not have time to test what happens if battery is full.
Can report that Dynamic power limiting works really well in SolarEdge SE16K (fw 0004.0023.0036).
VenusOS: 3.70~23
There is only one potential issue. It typically occurs on semi-cloudy days when clouds briefly pass over the solar panels. During these moments, the grid export power drops, the dynamic power limit resets to the inverter’s maximum power, and when sunlight returns, the power spikes over the limit. However, the power limit reacts too slowly and often overcompensates, sometimes dropping to 0W before eventually stabilising.
One possible solution would be to set the power limit to grid feed-in limit + consumption instead of maximum PV inverter power.
1 Like
You should phone Enphase and they will activate Modbus ports on the Envoy or IQ Gateway, after that your GX system will find Enphase Gateway
Tested on:
Solaredge SE7K Firmware 0004.0020.0036
Venus OS V3.63
‘Dynamic power limiting’ can (sometimes) be enabled on the Cerbo, but the connection between the Cerbo and the Solaredge is completely unstable.
Sometimes the connection is disconnected for several hours and then spontaneously reconnects, but making it unreliable to use.
When the connection is lost, the ‘dynamic power limiting’ option is no longer visible in the Cerbo.
Here you have the Enphase documentation:
https://enphase.com/en-gb/download/ac-coupling-enphase-iq-microinverters-victron-battery-inverters-tech-brief
I control my 3 Growatt Inverters via nodered, mqtt and Tasmota modbus bridge.
I read out al 3 of them and Nodered puts this data in the victron pv nodes which works flawless.
Is there a node for nodered that outputs the current wanted solar percentage which I can write to my Growatt Inverters?
It works perfectly for Kaco blueplanet NX3M2 Inverters.
Answering myself to post a follow up question 
Is there still work going on to include Kostal in Modbus/Sunspec support?
First of all, should this topic stay here, or may I use this info to create a feature request?
I know there are a few hurdles but if I can do it, it should be a piece of cake for Victron, right?
I guess the biggest blocker for most people to do further testing at the moment is to get a connection to the inverter.
To make this easier for people I would suggest making the port configurable instead of having it fixed to the default port 502.
That alone should be enough to make most moder Kostal devices visible to VenusOS.
At the moment this can only be achieved by some sort of port forwarding dirty tricks that might be to complicated for most to even give it a try.
For the non-yet-working limiting on the Kostal device.
Kostal published their specs on their website.
KOSTAL Interface description MODBUS (TCP) & SunSpec with control information
It has just recently been updated (June).
This plus more can be found on their Service Portal .
Section 3.1. describes active power and reactive power control.
It seems as simple as writing the desired power as a value to address 832 and for very large systems to include the scale factor on 833.
Like I described here.
Sorry if I am too pushy here.
It is the pure excitement that it is (almost) working and should be made available to more people.
3 Likes
Me too. Just like I tried to explain here
Also: it looks like the “AC export current limit” set in “peak shaving” is not adhered to.
1 Like
I did put in a feature request quiet a while ago for two features regarding Modbus. You can find it here. I did add yours there. Perhaps we can upvote it together.
Thanks and best regrads
Christian
2 Likes
Enphase specifics
Though confirmed by Enphase, in reality it is quite complex to make this working. Out of the box it doesn’t work, and help from Enphase Support desk is needed in order to enable the Modbus-TCP feature remotely. And getting that enabled has been reported by users to be quite difficult.
It was indeed difficult to find the right Enphase representative who knew what to do. Once I finally managed to activate Modbus TCP, it worked fine. According to Enphase, it’s read-only, but I can now confirm that the Cerbo can limit the production of the Enphase system. My entire system is connected to the AC OUT of my 3-phase setup. So, the Sunspec protocol now appears to be implemented on the Enphase side as well.
@mpvader Are there any specific things I can test?
Tested with Sunny Boy 4.0 (Firmware version 4.03.07.R) and works fine.
1 Like