Repository navigation
Help please with modbus (RJ45 connection) on Solis S6-EH1P5K-L inverter #45
|
Hello, I'm really struggling. I'm trying to help a friend to wire up his Solis S6-EH1P5K-L for modbus. I wired up my own Fox inverter modbus connection a few weeks ago and that was fairly painless but this just doesn't seem to want to play nicely. The inverter has a USB datalogger but also an RJ45 port, marked RS485. (as discussed at #44 & #43) We have a Waveshare PoE modbus to TCP device and have tried connecting the blue wire to RS485B and white/blue to RS485A as per the manual for this inverter. But I've just seen the photo at Pho3niX90/solis_modbus#75 (comment) where user Dominic-070 has the blue wires the opposite way around to what is specified in the manual. We've also tried the Orange wires as suggested at #28 (comment). In fact, I've tried all the pairs and they all turn the Activity light to a solid blue, except the blue & white/blue wires which cause it to pulse. This suggests to me that the blue wires are the correct ones. So, I've read lots of the discussions here and am not even sure if I should be using solax-modbus or solis_modbus but I've tried both and am getting nowhere. solis_modbus creates lots of entities but then does not populate any of them and solax_modbus does not create any at all. I've tried using Qmodbus to test but I'm really not sure what I'm doing here. The output remains blank for several minutes and then splurts out some stuff that I don't understand and then sleeps again. It frequently outputs "Exception 56" in red and then occasionally other exceptions, namely 1, 3, 26, 27, 86, 104, 120. I'm really out of my depth here and despite searching for these errors I have no idea how to proceed. Could I have got the settings for the Waveshare wrong? There doesn't seem to be a definitive guide here on which settings to use if you are connecting to the RS485 (RJ45 connector) port rather than to a datalogger where there are client and server Waveshare devices. In the advanced settings should I use Auto query storage Multi host or Simple Modbus TCP to RTU? Anyway thanks for reading and any suggestions would be most welcome. |
Replies: 4 comments 3 replies
|
Try Simple Modbus TCP to RTU and the following cable config.
Testing with Modbus involves querying the correct registers and retrieving the proper values. E.g., 33139 is to read the Battery SOC. Use the same values for your reference. |
|
Thanks for your advice. I've checked my settings and used Qmodbus to query the correct register (33139) as you advise and the Registers area on the left remains blank. All I see is the request on the right hand side under Bus Monitor. Here are my settings: Unless I've done something glaringly wrong or you have any other suggestions then the next thing I'm going to try is to check the wiring and then try my working Waveshare on my friend's setup in case there is a hardware issue. Can't do that for a week as he is away. I have remote retwork access for testing but not physical access to the house. Many thanks. |
|
I've now tried my friend's Waveshare at my house with my Fox system and it works fine so it's looking like it must be the wiring, the Waveshare config or his inverter unless you have any more thoughts. Does my config posted above look good to you? Thanks |
|
@tarmacalastair The config looks ok. Try different Baud Rates and double-check wiring. |
|
Thanks for all your help. We now finally have a connection. My friend double-checked the cabling and also changed the Slave ID from 1 to 2. I'm sure we'd already tried that but it is now working. Thanks again... |
|
Thanks so much. One inverter now working and my friend has followed up with a further query at #46 |
How did you change the slave ID, my SolisCloud app does not have the parallel settings option. Is that only available when logged in as installer. |
Thanks for all your help. We now finally have a connection. My friend double-checked the cabling and also changed the Slave ID from 1 to 2. I'm sure we'd already tried that but it is now working.
Thanks again...