Custom Component: ABB/Power-One/FIMER PV Inverters - SunSpec Modbus TCP

alexdelprete · August 5, 2021, 1:37pm

Ok, that’s the correct base address, I was looking for the 1 and the 66 values. Compare your last screenshot with mine.

alexdelprete · August 5, 2021, 1:41pm

Could you show me QmodMaster screenshot with starting address 40070 please?

Also, check that QmodMaster is configured like this:

monkeypr00f · August 5, 2021, 1:50pm

711a0123-fe9a-47be-9f45-2d79785c438a1168×1081 167 KB

alexdelprete · August 5, 2021, 1:58pm

Ok, it’s working.

Two issues:

The base address is 40000 for you, I use the VSN300 datalogger, and its base address is 0. I could make it configurable, but there’s also the problem at point 2 to consider.
The inverter is monophase (check the value at 40070, it’s 101, means monophase. 103 is 3-phase). My component has been specifically made for 3-phase models, since I use that one. The registers are different between 1-phase and 3-phase models.

I advice to use this component, made by @CJNE, it works great for any SunSpec device, also monophase or 3-phase inverters. It’s a generic SunSpec client, should work with anything SunSpec compliant…

Let me know if it works for you.

monkeypr00f · August 5, 2021, 2:00pm

I’ll try right now, thanks for the time to explain

alexdelprete · August 5, 2021, 2:00pm

I forgot the address: Custom Component: Generic SunSpec modbus TCP monitoring (inverter, meter etc)

Let me know if it works

xunil79 · August 5, 2021, 2:05pm

Hi Alesx
I’ve the same model Federico has. 1-phase

I’ll also try the component you suggested.
Thanks in advance

alexdelprete · August 5, 2021, 2:08pm

No problem, sorry for this, if it was only the base address we could solve it, but I didn’t include support for monophase inverters.

Actually, right now I’m developing a direct local integration with VSN300 via http, so no more modbus or sunspec. Some information of the VSN300 (I think VSN700 too) is not available through ModBus/SunSpec, and I wanted to pull it out.

I have a python script working, I just need to make it a custom component now.

Ciao,

Alessandro

xunil79 · August 5, 2021, 2:18pm

Unfortunately Fimer and ABB don’t provide any public technical info of modbus registries.
Do you know why I can get output using as unit 2,11,13 and so on to 247?

Thanks in advance
Ciao

alexdelprete · August 5, 2021, 2:20pm

I found a lot of documents regarding ModBus for FIMER/ABB/Aurora register map.

But I also contacted tech support of FIMER and talked with the software support people, they’re very nice, and sent me a couple of documents for VSN300 and ModBus map. On my github repository for this component I uploaded the document used to develop this.

I don’t understand the question, you are saying that you can read data with any slave ID?

xunil79 · August 5, 2021, 2:23pm

yes exactly. not any but most of them

alexdelprete · August 5, 2021, 2:25pm

really strange, I use the VSN300, and it only answers for unit ID 2, which is my PVI-10.0-OUTD inverter.

I think it’s something related to the VS700 included with the React2 bundle.

xunil79 · August 5, 2021, 2:27pm

when I perform a scan with CAS modbus scanner I can see many device IDs with “good” status.
All those IDs are able to show me the data

alexdelprete · August 5, 2021, 2:29pm

That’s not a proper test.

Use QmodMaster, set unit id, and read from registers address 40000 or 40070. Like you did before.

If you read the same info independently of the unit ID, probably with the VS700 there’s some configuration or feature enabled.

xunil79 · August 5, 2021, 2:33pm

same in QmodMaster.

alexdelprete · August 5, 2021, 2:36pm

data is not the same if you look at it. try with base addr. 40000.

it’s the VSN700, look at the manual and configuration.

xunil79 · August 9, 2021, 2:09pm

Hi Federico,
does the custom component work with your React 2?

monkeypr00f · September 2, 2021, 12:45pm

Ciao Claudio,

the custom SunSpec integration from HACS works with REACT2, it provides you information on realtime power consumption/production…but all the batteries part is missing. There are problems too using that integration with the new Energy panel, all the sensors are NOT compatible with the statistics required by the dashboard. You need to template every single sensor to gain the long term statistics needed.

alexdelprete · September 4, 2021, 6:30pm

@monkeypr00f @xunil79

Federico, Claudio: I decided to update my component, to make it compatible with the new requirements for the Energy integration.

I was also looking at the differences between the monophase and 3-phase inverters: basically the register addresses are the same, but the monophase has less data, because it’s only the data for 1 phase, while the values for the 3-phase has data (current, voltage, etc.) for each phase. So, to make it simple, I think I don’t have to adapt the read function to the monophase. But I need to test it on a monophase inverter…

I also introduced in the initial configuration process of the component the base_address, which in your case we discovered is 40000, it is the start address of the register map. For my VSN300 datalogger it’s 0. Making it configurable will allow anybody to configure it for their specific datalogger/inverter.

Tomorrow I should have a beta version to test, can I ask your help in testing it? If it works also for you, I will release v2.0 of the component.

Thanks,

Alessandro

monkeypr00f · September 4, 2021, 7:30pm

Alessandro that sounds awesome! I’ll give you all the support may be useful to land this project!