curto

Hey @Cef Great to see you are still evolving this software for everyone who is using it. Just wanted to give you an updated on my project with the 3 x SBP 5000 inverters - which although not directly related (being AC coupled inveters only) relates in respect of using the same AA55 protocol that you are using for communicating with the inverters I use Node Red for my communication and control of the inverters and have been doing so for the last 2 years or so with no issues. I am not sure if your plan is to provide control as well as monitoring of the ES series but if so i am happy to provide you with all the info i have in terms of writing to the inverters (By IP Address in the case of multiple inverters) and being able to control what mode the units are in and the the different time settings. I have found this to be very reliable unless we have storm and we then often have failures of the GoodWe WIFI modules. I currently write in realtime to the inverters and tell them how much power to charge and discharge at any point in time (we are a 3 phase house and GoodWe do not support multiple inverters in a 3 phase scenario so have to manually control each inverter on the 3 phases) Let me know if you require any information in relation to this - it was all hard won by packet capturing everything that PVMaster was sending to the Inverters when changing modes and times of operations and then charge and discharge limits. I will be shortly biting the bullet and moving all of my control over to the modbus port (again through Node Red) but happy to share in the meantime if you want the information Craig

Excellent thanks Bulldog - very much appreciated. Will give it a try over the weekend regards Craig

@The Bulldog Just wanted to get an update on how this is going for you ? I am in Australia and have a 25Kw 3 phase Solis inverter - our electricity provider exposes us to wholesale prices so very often during the day the prices go negative and we wish to either stop or limit the amount we feed to the grid. I wonder if you ever got around to debugging the output from the Solis EPM to the Soliv Inverter - my inverter has a RS485 port for the EPM to plug into but as i already have a whole of house monitoring system that runs through Node Red i would prefer to not buy the seperate box but rather set the appropriate modbus registers I have the Solis Modbus Documentation that i have found on the internet but it does not seem to specify which registers could be used to limit output production capacity Craig

The battery uses a Can bus to communicate with the inverter - as such there are 3 cables that are of interest Can+ (H), Can -(L) and ground. In many instances you will not need to worry about the GND connection. So you can connect anything onto the bus to see what is being transmitted - but you will need to do some detective work to work out what the information is. The easiest way to connect in is to get a Dual Can hat for the Raspberry Pi - you can then (in software) tell the pi to copy everything backwards and forwards between the two ports - you would then connect one end to the battery and the other end to the inverter. Then as well as copying the packets you will need to capture them and try to decode them on the fly. Craig

Guys, Recently did a teardown of the LAN and WIFI adapters for anyone that is interested. Googling on the part numbers leads to some interesting Forums and BLogs https://photos.app.goo.gl/E16rCs262jrmZ1sE8 Craig

CEF, OK from what i can see PV Master sends out a single 48899 query on UDP Broadcast and then waits for a maximum of 10 seconds for inverters to respond. If during that time your inverter did not see the broadcast and has not responded then it is not listed in the set of Available inverters. In my case i have 3 of them - in many cases using the App i will only get two of them listed and then if i want to work on the other one i have to exit the app and start again. You missed my point re static addresses - why not the first time they find an inverter as would you like to remember this - from then on it is there rather than having to do this stupid stuff. Craig

@Cef If you do a UDP broadcast on port 48899 this will then find all the inverters that respond. (Which i think is a stupid method by GoodWe - why wouldnt we just give the Inverters Static IP addresses and then define them in the app ? Craig

Thanks for the response. It looks like we had a bit of a breakthrough over the weekend and have now seen that for reading purposes the SBP series are treated the same as ES/EM series. So no Modbus but just the AA55 protocol over UDP I am now succesfully reading the data from the inverters with python and just converting that into Node Red now. My next step is to start writing to the inverters and this is where everyone seems to have stopped - have you got any info on the AA55 command features for writing and controlling the inverters ? I am particularly interested in being able to force discharge and charge at prescribed rates (rather than using ECO and the time block in the PV Master app). Do you have any insights there into writing/controlling ? I am just about to connect one of my inverters up with RS485/Modbus and see what they support through there. Craig

Have a look at this forum post https://secondlifestorage.com/index.php?threads/high-voltage-hybrid-inverter-gw6000-eh-with-ev-battery-chevy-volt.10300/page-6 Essentially the Inverter talks over a CANBus intrface to the batteries - these guys have worked out how to reverse engineer this to make the inverter think it is talking to a supported battery type. If you email the author directly i am sure he will help out with some code etc Craig

@PowerVan I am just working through this at the moment with the GoodWe SBP-Series of AC inverters. It is daunting at first but a couple of pointers i can give you 1) Wireshark is your friend - i havea cisco switch at home so can port mirror rather than trying to capture on a phone - but the same concept. 2)Have a read of this forum thread 3) Use Node Red which one of the users on that thread does and he posts the information to change the charge/discharge rate etc (unfortunately this does not work for my inverters so still working through that) 4) Have a read of this document which explains the AA55 protocol that GoodWe use - is appears to be quite old and not complete but it will give you a lot more info on what is happening Microsoft Word - Inverter.VS.EzFamily_PROTOCOL_V1.2.1_Customer.doc (yamasun.com.tw) 5) Essentially Goodwe have a front end protocol that uses these byte strings of aa55 and then the next two bytes are a source (you) and destination (inverter) identifier (you assign both of these) and when the inverter responds it sends back with its destination address as the sender and your source as the destnation i.e. flips the sender and receiver. 6) The initial comms with the inverter is a query to ask it for model number, serial number, version etc. (described in the linked document above) After this you get into Modbus and are essentially asking the inverter to send you a series of modbus registers. This is well described here GitHub - MiG-41/Modbus-GoodWe-DT: Protocol description for modbus Goodwe DT inwerters (Although that is Modbus RTU (RS485) ) Once you undrstand these sorts of commands then using the DOc that i linked above you want to look for 0x03 in the debug of the PV Master app - this is the command to execute/write data to the inverter I am just working through all of this at the moment Craig

No scrub that last comment - the LAN dongles appear to work OK - but there is one big issue (if you have multiple inverters). Unlike the WIFI adapters when PV Master does the initial broadcast query to discover all inverters on port 48899 - the LAN units respond with a generic HF_E20 (which is the maker High FLying Shanghai Corp) so if you have 3 inverters like i do - you can not tell them apart - just have to select one and continue on - if it is the wrong unit thn back to main screen - wait for the discovery and try another. BUT - the screen is randomly populated based on which unit responds first so with 3 inverters i can be sitting there for 10 minuts trying to jump in and out I reinstalled one of the WIFI adapters last night and the presentation in PV Master is much better with at least the serial number tacked onto the end. I have seen this drop off the network behaviour with the LAN modules also - i believe it is when you send an incorrect request/config to the unit - they go into some sort of reset state for a couple of minutes Craig

Hey @Cef- Just wanted to say what a great job you have done here. I do not have the ES series but rather the AC Coupled SB-P series. I am slowly working through (using Wireshark) what PV Master is doing and how the AA55 protocol works. Just wondering what tools/methodology you used to get into this level of control with the inverter I have already worked through the initial discovery on 48899 and then the startup query sequences etc Just trying to work out how to write data to the unit - it appears as though the SB-P supports some subset of both the ES and DT Series and responds (in a limited way) to each of the queries ANy help you could provide documentation wise etc would be great Craig

Has anyone worked out how to turn off the SSID/AP broadcast from the WIFI dongles once they are connected to your home WIFI ? I would prefer not to have AP broadcasts like that for security reasons. Craig

Yeah just tried SolarGo and it cam back with can not find any supported inverters - pretty sure it is meant for inverters with PV capability whereas mine are AC Coupled only. Craig

Thanks for this - but my version of PV Master tells me the same thing and then lists my inverters I have been backwards and forwards with GoodWe support and they have never suggested to try SolarGo - will download it now and see what it says. Interestingly enough - i have now converted one of my inverters back to WIFI and i can see difference in the main screen - it is fairly obvious whoever wrote it never contemplated someone using 3 of these with LAN adapter. When i have the LAN adapters in installed - the initial screen lists 3 devices as HF_E20 - no other identifiers - you have to select one and go to the next screen to see which is which and if you pick the wrong one - you go back to the main window and start again - however if you have the WIFI dongles it lists then as Solar-WiFi and then part of the serial number of the inverter so you can differentiate from the main screen - just poor UX design Craig