i use three Kaco blueplanet nx3 inverter and since the sunspec feature was added to the Venus OS they were recognised flawlesly incluiding the power modulation feature.
Unfortunatelly i had to add a ripple control communication adapter from Kaco with another newer firmware and since then they are no longer found by the cerbo.. i’ve tested the old communication adapter and with the newer firmware it wasn’t found either.
when i asked the Kaco support if i could use older firmware with the RCN-Kit they told me that the cerbo is not supported or approved by kaco and no further help was given.
with the homeassistant sunspec-integration the kaco is found in my network with all the sensor data, so the kaco stil sends out the data, but the venusos is looking for the wrong adress data i guess.
on the Kaco website they have a sunspec specification guide
Did you try to talk TCP Modbus directly to the stick using a Modbus Tool?
Which NX3 Model ar you using?
Which Version of the stick and which FW?
We have about 200 NX3M2 inverters in the field. For a few months now, they have had a batch of sticks that have a hardware problem, causing Modbus responses to be extremely delayed, which makes the sticks unusable for us.
sorry for the delay, i didn’t manage to go on site until today (700km away from home and KacoTool didn’t work over VPN).
With Open ModScan TCP Search i can find the Stick IP with device id 1 & 3 and it sends data. Unfortunatelly I don’t have the skills yet to use the software further .. The HomeAssistant Sunspec Addon finds the Stick and the Inverter and finds all the usual parameters.
I use the 10.0 NX3 M2 and the 20.0 NX3 M2 on seperate Installations
The Connect-RCN stick is the KNE-NX3-RCN-G1 Model with Hardwareversion M11 and Softwareversion V610-50112-01.002. I do have the old Firmware for the “normal” communication stick that worked, but since i changed to the RCN-Kit due to legal requirements of the grid-provider i dont have the old version for this. the MyKaco Download section does not work anymore and i don’t want to mix firmwares to avoid damage..
I have seen Kaco NX3 M2 devices where it works with Modbus ID 3. Some others needed to be changed.
The problem with the Kaco NX3 M2 inverters is that they aren’t directly from Kaco, but rather labeled products from an Asian company. Kaco itself can’t do anything about their behavior.
To give some feedback to the new configurable device id and port.
This helps to get my Kostal Plenticore Plus G2 partly working.
The inverter is being detected an I can enable limiting.
Limiting is not working out of the Box.
It works with the simple Node-Red Flow I reffered to earlier.
In essence it manualy writes the limit calculated by venus OS via Modbus to the inverter.
Not sure if that is being looked at.
Unfortuanetly my options of testing this will be quite limited due to winter.