Replies: 9 comments 22 replies
-
Hey @SNAPE15 Your initial logics was sound. I had the same thought on the subject. Issue I have found is that using modicon convention notation where address is 0 and register is +1... as you described (which is the correct logics and same approach I have tried) the register does not show any signs of life, no voltage, no current, no power... I do not expect they will have any but its better than nothing... cos either the document is wrong... or part of the document is wrong or there is another document they have not released.... yet? Keep in touch. Keen to hear abt your journey |
Beta Was this translation helpful? Give feedback.
-
Hey I will say – thank you for being patient – I am not that great with things I do not understand… esp. configs… It said in Winet docs that it needed mqtt, so I installed it. |
Beta Was this translation helpful? Give feedback.
-
Probably solved at this point, but I wanted to point out that there is not MPPT4 on the SHxT line. Even the largest model (SH25T) has a total of 3 MPPTs. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, I have also received an SH15 and would like to have the configuration for the MPPT3. Would be great if someone could help. |
Beta Was this translation helpful? Give feedback.
-
Absolutely easiest way to get this done is to install winet extractor add on via mqtt
Sungrow does have currently mppt3 registers allowance only but they are not working correctly and are not listed in their protocol.
These registes are listed below (if these were to be added to modbus protocol), but like I said – they will not work until Sungrow fixes their code
- name: MPPT3 voltage
unique_id: sg_mppt3_voltage
device_address: !secret sungrow_modbus_slave
address: 5014 # reg 5015
input_type: input
data_type: uint16
precision: 1
unit_of_measurement: V
device_class: Voltage
state_class: measurement
scale: 0.1
scan_interval: 10
- name: MPPT3 current
unique_id: sg_mppt3_current
device_address: !secret sungrow_modbus_slave
address: 5015 # reg 5016
input_type: input
data_type: uint16
precision: 2
unit_of_measurement: A
device_class: Current
state_class: measurement
scale: 0.1
scan_interval: 10
Winet extractor does however expose mppt3 in a different way and you can use these sensors instead.
Hope that helps. 😊
|
Beta Was this translation helpful? Give feedback.
-
Winet extractor exposes mppt3 separately corrects quite a few of faulty registers values. It just reads them differently and somehow these do not get corrupted.
Thats currently the only way to do stand alone mppt3 read.
Sungrow r&d are working in fix but no eta yet
On 22 Sep 2024, at 8:16 pm, Christian Wissel ***@***.***> wrote:
They are documented just like the other registers: https://github.com/Gnarfoz/Sungrow-Inverter/blob/main/Modbus%20Information/TI_20231019_Communication.Protocol.of.Residential.Hybrid.Inverter_V1.1.2_EN.pdf
It is indeed not possible to read just MPPT3 alone. However, you can read it together with MPPT1 and MPPT2 if you do it in a single operation. You'll have to use the virtual_count option to do that and then use a bunch of template sensors to convert the raw values into usable sensors, because the registers alternate between voltage and amperage.
See also: #298 (reply in thread)<#298 (reply in thread)>
—
Reply to this email directly, view it on GitHub<#254 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIGQNNDFNNTV4GCAAQREHPTZX27JHAVCNFSM6AAAAABDLDD372VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZRG44TKNA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Sadly this kills communication for multiple inverters which sit behind logger1000a. And I do have that config. So not an option for me.
On 22 Sep 2024, at 8:31 pm, Christian Wissel ***@***.***> wrote:
There's also the option of using a RS485 to Ethernet converter on the "logger" port on COM2. Avoids all other issues with the WiNet-S stick as well.
—
Reply to this email directly, view it on GitHub<#254 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIGQNNFO6JRRTRC7LRIBE7LZX3BEHAVCNFSM6AAAAABDLDD372VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZRHAYDGMY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Yes it it only gets complex from there.
Full modbus for logger.
Modbus for chint meter.
Modbus for each inverter.
Trust me. Keep it one inverter if u can.
Complex config. But works.
On 22 Sep 2024, at 9:00 pm, Christian Wissel ***@***.***> wrote:
Interesting, you're the first person I've encountered who actually has a logger 1000. 😅
—
Reply to this email directly, view it on GitHub<#254 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIGQNNFJRLQO4SUOUU5ZPM3ZX3ENXAVCNFSM6AAAAABDLDD372VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZRHAZDAOA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I understand how to add the code, but what address should i be assigning, or does it not matter. MPPT2 V & C are 5012 and 5013, does that mean MPPT3 would be 5014 and 5015?
and if so, MPPT4 would be 5016 and 5017 which takes over Total DC Power, just move it further up the count? Or do I add extra MPPT's at end of that range (5035 from memory)?
update, so i found the communication protocol document and seems they didn't allow for 3rd and 4th string at that stage. So does that mean I need to wait til the newer document is released to know the address?
also, I've noticed that my dashboard is showing a figure for sensor.load_power as 1 figure (245w for example), yet if i have that sensor in a power flow card it shows a higher figure (500w for example). anyone know why? the lower figure seems tomatch what is shown as load power on the inverters webpage, but wondering why it's a higher figure when in the power flow card.
Beta Was this translation helpful? Give feedback.
All reactions