wana understand

[patmtp35]

hi , not realy an issue but to understand why that's not working.

Perhaps somethings change with the last esmart Rev:4.2.
Mygreensolar don't work any more , ony work solarmate pc or android.
i made a y cable one side on cloud-box-m2 other on pc computer using the same serial2usb as you specify and solarmate works greate on both side at same time or separte (on disconected or the other)
if i try my green solar pc it recive data only if i launch solarmate on android.
if i launch the emsart_test.py nothing happend , but if i launch solarmate on android data comes.
So perhaps the request message change ?
some have the same issue as me ?

ps: i try with two RPI clean debian 10

[CaptainTactful]

Hi, sorry for the delay in answering, yeah I see there's a new esmart4 mainly to cater for lithium batteries I assume.
I wouldn't be surprised that things have changed in the comms. It's far easier, from my pov to write fresh code, than it is pick through and reverse engineer someone elses. Especially when you can see flaws in the overall implimentation.
For example. the esmart3 tries to be a JBUS or MODbus RTU protocol, but doesn't stick to the spec.

I'm pretty sure, from the looks of it, that the ecoworthy 60A is a rebadged esmart4.
https://www.ebay.co.uk/itm/326031658158
Manufacturers website
https://www.ipandee.com/products/60a-mppt-solar-charge-controller/

If you look at the feedback for someone who purchased one they talk about needing a cable to change settings.

I may purchase one in the future as it's 150v VOC and they had an offer in Febuary with another 20% off, so £80 free postage.
But the Victron BlueSolar 150/35 simply sends serial data out it's JST PH 2.0 5v ttl port and they give free firmware updates.
The victron is a far more active mppt when I look at the influx data and definitely gives a greater return if watts is important.

[CaptainTactful]

I've downloaded the software .rar from the ipandee website and tried it with the esmart3 and it works. Meaning the esmart4 should be a direct replacement, comms-wise for a failed esmart3.

Couple of caveats. On Win 10 I had to run the 'MpptSolarMonitor_N_V1.3.exe' as administrator before the com ports showed up, then open the com port and start monitoring.
Though that's not a guarantee as it's possible, that on initial comms to the controller the software reads the device model and communicates appropriately.
I'll get an eco worthy and confirm.

Persoanlly I'd like to be able to change the rs485 address of 2 of my 3 esmart3 controllers so I can have them run on a single bus, but that doesn't appear obvious.

[CaptainTactful]

~~Unforutnately, the esmart4 isn't a direct replacement for a failed esmart3. The rebadged ecoworthy 60A mppt I have here works with the pc-software but not mysolargreenmonitor.

I'll have a go at capturing the comms at some point , probbanly this autumn/winter. The pc-software (not available on the ecoworthy website strangley) logs the data out and in count, if it's accurate it looks to be far more chatty than the esmart3.
I will see.
Unless someone else gets there first wink wink..nudge nudge,,~~

I was just about to pack the controller away and gave it one extra go with the esmart3 software, mysolargreenmonitor.
It DOES work. But, it looks like the timing is off, as the software drops the connection to the controller and connects again sevaral seconds later.
Should mean it's fine with skagmos test script which i'm using.
I'll try that and post back.

[CaptainTactful]

yep works fine.