@p_i Who are you checking for stock? 

 

Just now, Sc00bs said:

@p_i Who are you checking for stock? 

MicroRobotics, as per the link in my previous post: https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/W17286

I have used both of these in the past 

https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/RS485-MINI

https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/RS485-3P

 

I've seen comments on this forum that the cheap one doesn't work reliably? Or is this another version of the cheap one?

Mileage may vary, I never had any problems but other people have said that they did. 

It is always better to minimise the possible causes of issues, but if you have no other option then you have to make use of what you have available. 

Cost on them is negligible so if you have no other option then it worth trying it out in my opinion. I have never heard of anyone breaking anything using one of them.  

I got two of these https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/RS485-3P and ran my jacauc-based node-red flow via serial but I kept getting random timeouts on my HA RPI4. None of my attempts at staggering my modbus requests had any effect, not random delays, increased queuing times, nothing. I suspect the RPI4 with HA simply isn't fast enough to keep up with the load, maybe due to other HA stuff running on there. So I tried option B: installed mbusd on a RPI3b to expose the serial ports via TCP/IP and now there's no timeouts, even with me polling every 10s for ALL the data (was 15s before). I think I should even be able to even pull data at 5s intervals, if I decrease the default mbusd inter-request delay a bit more (was 100ms default, already dropped to 50ms). My proof of concept via grafana is coming along nicely too but I still have lots to learn...

7 minutes ago, p_i said:

I got two of these https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/RS485-3P and ran my jacauc-based node-red flow via serial but I kept getting random timeouts on my HA RPI4. None of my attempts at staggering my modbus requests had any effect, not random delays, increased queuing times, nothing. I suspect the RPI4 with HA simply isn't fast enough to keep up with the load, maybe due to other HA stuff running on there. So I tried option B: installed mbusd on a RPI3b to expose the serial ports via TCP/IP and now there's no timeouts, even with me polling every 10s for ALL the data (was 15s before). I think I should even be able to even pull data at 5s intervals, if I decrease the default mbusd inter-request delay a bit more (was 100ms default, already dropped to 50ms). My proof of concept via grafana is coming along nicely too but I still have lots to learn...

 

The adaptor you have is perfectly fine,- it has a GND and some protection.

Agree that, the native mbusd timing is far superior to what Python and Node V8 offers. I have mbusd running on a 10+ year old Pi Model 1b. The mbusd addon on HASS OS also works flawlessly.

My production Pi-4(HA+SSD) + Pi-1b(mbusb) pulls data every 2 seconds, ~15m of RS485 bus and maybe 2 timeouts per day.

1 hour ago, kellerza said:

My production Pi-4(HA+SSD) + Pi-1b(mbusb) pulls data every 2 seconds, ~15m of RS485 bus and maybe 2 timeouts per day.

Thanks for the inspiration. Turned up the heat here and I'm managing about 30 modbus (x2 inverters) requests every 2 seconds, without timeouts! It's almost a constant stream of modbus requests. The load on the mbusd RPI3b has increased slightly to 0.17 but that's not really busy. Not sure if the RPI4 sdcard is going to be happy with all the influx writes but this is proof of concept for now.

On 2023/11/17 at 12:35 PM, p_i said:

Thanks for the inspiration. Turned up the heat here and I'm managing about 30 modbus (x2 inverters) requests every 2 seconds, without timeouts! It's almost a constant stream of modbus requests. The load on the mbusd RPI3b has increased slightly to 0.17 but that's not really busy. Not sure if the RPI4 sdcard is going to be happy with all the influx writes but this is proof of concept for now.

The SD card won't last long.

In my setup I use an SSD and my write interval is only 60 seconds. The 2 second read interval is to ensure I can react quickly to significant changes in power.

I backed off and now I'm only reading every 5 seconds. But this morning my battery bank (that I used to power my RPI3b with mbusd) ran out so I took the time to run a power lead to the RPI3b but now mbusd refuses to talk to the inverter. I put mbusd in debugging mode and it appears the commands to the inverters are timing out. And yes, I've rebooted the RPI3b multiple times and plugged and replugged all my cables. I even put it back on the battery bank as a test but no go. Any idea other than to reboot the inverters?

Edited November 26, 20232 yr by p_i

2 hours ago, p_i said:

I backed off and now I'm only reading every 5 seconds. But this morning my battery bank (that I used to power my RPI3b with mbusd) ran out so I took the time to run a power lead to the RPI3b but now mbusd refuses to talk to the inverter. I put mbusd in debugging mode and it appears the commands to the inverters are timing out. And yes, I've rebooted the RPI3b multiple times and plugged and replugged all my cables. I even put it back on the battery bank as a test but no go. Any idea other than to reboot the inverters?

cable, probably, stranded cat5 cable seems near unobtainium locally these days, so most people seems to use fixed install solid copper cable to make up the rs485 cable and once this gets bent once or twice it could well break and then give an iffy/intermittant connection, check the rs485 cable, likely to be your problem...

1 hour ago, Kalahari Meerkat said:

cable, probably, stranded cat5 cable seems near unobtainium locally these days, so most people seems to use fixed install solid copper cable to make up the rs485 cable and once this gets bent once or twice it could well break and then give an iffy/intermittant connection, check the rs485 cable, likely to be your problem...

I was using the same cabling that was working perfectly until 2am when the power bank died. As a test I now swapped out one of my https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/RS485-3P devices with my old https://www.robotics.org.za/communication-wireless-Industrial/RS485-devices/RS485-USB/W17286 and immediately it worked. Swapped the RS485-3P unit back in and it refuses to work. Back to the W17286 unit and it works. So I think I need to source a second W17286 unit somewhere and it seems I might have to import it since I don't see them available anywhere in South Africa at present.

PS: I also tested the continuity on the CAT5 cable and the cable is fine so it's not that. So somehow 2x RS485-3P units simply stopped working?

PPS: Seems it's available locally as https://www.takealot.com/waveshare-industrial-usb-to-rs485-converter/PLID93157151 which is a bit of a rip-off in terms of pricing. Hmm...

Edited November 26, 20232 yr by p_i
added takealot link

3 hours ago, p_i said:

PS: I also tested the continuity on the CAT5 cable and the cable is fine so it's not that. So somehow 2x RS485-3P units simply stopped working?

Redid the one cable and even doubled up the wires but still no go. Will have to source me another W17286...

1 hour ago, p_i said:

Redid the one cable and even doubled up the wires but still no go. Will have to source me another W17286...

Bear in mind a twisted pair is twisted. Using 2 wires from a pair you loose the twisted effect. Twisted reject more interference. 

Here's another interesting observation: According to https://www.waveshare.com/usb-to-rs485.htm the "Transmission mode" of the W17286 is "Point-to-multipoints (up to 32 nodes, it is recommended to use repeaters for 16 nodes or more)". Does this mean you could use one W17286 to talk to two inverters, each with their own unique modbus ID, which is the default scenario in a parallel installation?

The same applies to the RS485-3P device as per the manual https://handsontec.com/dataspecs/module/USB-RS485.pdf: "Supports Multi-point Communication".

Edited November 26, 20232 yr by p_i
added other device too

2 hours ago, p_i said:

Here's another interesting observation: According to https://www.waveshare.com/usb-to-rs485.htm the "Transmission mode" of the W17286 is "Point-to-multipoints (up to 32 nodes, it is recommended to use repeaters for 16 nodes or more)". Does this mean you could use one W17286 to talk to two inverters, each with their own unique modbus ID, which is the default scenario in a parallel installation?

The same applies to the RS485-3P device as per the manual https://handsontec.com/dataspecs/module/USB-RS485.pdf: "Supports Multi-point Communication".

I think I got my answer from @kellerza here: https://github.com/kellerza/sunsynk/issues/39#issuecomment-1229449999

20 hours ago, p_i said:

Here's another interesting observation: According to https://www.waveshare.com/usb-to-rs485.htm the "Transmission mode" of the W17286 is "Point-to-multipoints (up to 32 nodes, it is recommended to use repeaters for 16 nodes or more)". Does this mean you could use one W17286 to talk to two inverters, each with their own unique modbus ID, which is the default scenario in a parallel installation?

And I managed to get it to work with my single W17286 RS485-USB device. I simply had to add a 2 second delay between querying the first and second inverter. 1.5s would have worked but I opted to give it a little bit more time to complete the first hit before hitting it again. Without this delay it appeared like the modbus became clogged and nothing got through. I'll experiment some more with the various modbus-getter parameters to see if the queuing to mbusd can be handled more graciously.

PS: this is a temporary fix so I have some figures whilst I wait for my second W17286 device to arrive. 2s delayed/offset figures are better than no figures.

Edited November 27, 20232 yr by p_i

I am sure this has been discussed before, but for the life of me I cannot find it.

I noticed awhile back that the daily total load consumption (mbus #084) is +-3.5kwh lower than actual total consumption. I presume that this has to do with losses and self-consumption.

The energy dashboard in home assistant uses the correct formula for total house consumption. 

Viz. (Solar power + battery discharge + grid import - battery charge) This will give your total household consumption with everything factored in.

 

 

On 2022/03/19 at 7:21 PM, Joerg said:

Hi,

I installed a Waveshare RS485 to ETH and use a PI with ioBroker and the modbus software adapter to read my values via RTU via TCP from my SunSynk 8kW. I used the manual to find the registers but I can't find the register to enable/disable the use of the timer frames to charge the batteries. I want to turn into Loadshedding mode automatically according Eskom Schedules. Can anyone tell me please which register it is?

Thank you!

Hi Joerg,

I am trying to import SunSynk monitoring data into iobroker as well. However, I use the WIFI dongle. All data is available from the Sunsynk cloud via the app or the web site.

Do you know if there is a way to access the data via a web service, provided by Sunsynk?

I also tried the Solarman adapter which should work for Deye, but it doesn't seem to work for Sunsynk 

Anyone any idea?

Mike

On 2024/02/07 at 5:13 PM, MikeCPT said:

Hi Joerg,

I am trying to import SunSynk monitoring data into iobroker as well. However, I use the WIFI dongle. All data is available from the Sunsynk cloud via the app or the web site.

Do you know if there is a way to access the data via a web service, provided by Sunsynk?

I also tried the Solarman adapter which should work for Deye, but it doesn't seem to work for Sunsynk 

Anyone any idea?

Mike

Hi Mike,

actually I have a Sunsynk 8k and a Deye 15k (3 phases) and they both work via Solarman App but(!) the App does not provide all the data by far, unlike modbus and it is much too slow to actually "control" anything with it.

I would think if you can see the data on your app, the iobroker adapter will read them. Just wait long enough, sometimes you initially need to wait until the next day until they show.

Joerg

13 hours ago, Joerg said:

Hi Mike,

actually I have a Sunsynk 8k and a Deye 15k (3 phases) and they both work via Solarman App but(!) the App does not provide all the data by far, unlike modbus and it is much too slow to actually "control" anything with it.

I would think if you can see the data on your app, the iobroker adapter will read them. Just wait long enough, sometimes you initially need to wait until the next day until they show.

Joerg

Thanks Joerg.
Right now I am using the Sunsync app. Yes, I agree, the data is limited but quite actual. 
Do you know, if I would be able to configure the dongle/logger to work with both apps (Sunsynk and Solarman) simultaneously?
ioBroker only offers an adapter for Solarman, but not for Sunsynk (maybe because Sunsynk doesn't offer a web service).

Hi all

I'm trying to get my Node-Red to talk to the inverter, but it just says "initialise".  DMESG confirmed my device got allocated ttyUSB0.

What should the baud rate be ?  I have set 9600

I have seen comments elsewhere about the Deye RS485 RJ45 connector using pins 4 & 5 ???

Alternatively, if I went the TCP route, over port 8899, do I not need to authenticate in some way using the logger serial number and the inverter serial number ?

Thanks in advance

Edited February 10, 20242 yr by championc

On 2024/02/09 at 7:22 AM, MikeCPT said:

Thanks Joerg.
Right now I am using the Sunsync app. Yes, I agree, the data is limited but quite actual. 
Do you know, if I would be able to configure the dongle/logger to work with both apps (Sunsynk and Solarman) simultaneously?
ioBroker only offers an adapter for Solarman, but not for Sunsynk (maybe because Sunsynk doesn't offer a web service).

Hi MIke,

just found your reply...I even didn't know that there is a Sunsynk app now 🙂

iobroker uses cloudaccess for solarman (updates every 5 minutes!), have no idea if there is a sunsynk api...

Cloud solutions are good for checking things away from home but as soon as you want to control anything at home direct access most of the times is more reliable and faster. You probably could access data parallel to your dongle. At least it works with my Deye 15K SG01HP3-EU-AM2

13 hours ago, Joerg said:

Hi MIke,

just found your reply...I even didn't know that there is a Sunsynk app now 🙂

iobroker uses cloudaccess for solarman (updates every 5 minutes!), have no idea if there is a sunsynk api...

Cloud solutions are good for checking things away from home but as soon as you want to control anything at home direct access most of the times is more reliable and faster. You probably could access data parallel to your dongle. At least it works with my Deye 15K SG01HP3-EU-AM2

Hi Joerg,

yes, there is a SunSynk app available. It gives you all the basic stuff for monitoring and looks very similar to the Solarman app.

However, AFAIK Sunsynk didn't publish a web service API (yet) and therefore no adapter is available for ioBroker or HASS.

Since both apps are very similar, my hope was to use the Solarman adapter, but change the web service endpoint to Sunsynk...But I don't know the endpoint (yet)....maybe a network expert can use a WIFI sniffer to find out what endpoint the Sunsynk app is using 😀

The service provider who does the maintenance for our inverter use the Sunsynk app. That's the reason why I ask if it's possible to configure the dongle/logger to talk to two separate cloud services. 

I also reached out to Sunsnyk wrt the API...but they are very slow with their response.

Monitoring is all I am looking for. Config I would do on the device.

Mike.

On 2022/11/25 at 8:22 AM, AFTP said:

Thanks very much for the link. I managed to get comms to my 12 kW 3-phase inverter working. I had to use the "Meter-485" RJ45 port. There is another RJ45 that is labelled "ModeBUS", but according to the latest Sunsynk manual its use is reserved. 

The register addresses are definitely different to the inverters that you guys have done most of the development work on (except for the first few, so it is possible to get the serial number for example using the same registers). 

I did eventually stumble on the attached document on another forum that does seem to describe the 12 kW 3-phase inverter's Modbus register locations. I am still working through it to confirm everything. (I think this is the same document a poster mentioned on your github forum, but I'm attaching it here for anyone looking for it in the future.)

Modbus amit posun.docx 226.9 kB · 33 downloads

Posting this to help others find the answer. The Meter-485 port definitely seems to be read only. None of the write commands have any effect. Using the BMS port with a splitter (if you're using it for the battery already) works for reads and writes on the 3-Phase 12KW Sunsynk inverter.