Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HELP] EASUN SMH II 4.2KW DONT WORK #162

Open
avenseElectro opened this issue Oct 19, 2024 · 37 comments
Open

[HELP] EASUN SMH II 4.2KW DONT WORK #162

avenseElectro opened this issue Oct 19, 2024 · 37 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@avenseElectro
Copy link

A clear and concise description of what the problem is.

I can't get this inverter to work at all, can anyone help me?


[WebSerial] Connecting...
[WebSerial] Connected...
[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Modbus device

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
----------------- End Autodetect -----------------
----------------- Start Autodetect -----------------

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Modbus device

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
----------------- End Autodetect -----------------

Additional context

No response

@avenseElectro avenseElectro added the help wanted Extra attention is needed label Oct 19, 2024
@softwarecrash
Copy link
Owner

the smh series works so i think, can you explain your wireing, photos and more

@avenseElectro
Copy link
Author

the smh series works so i think, can you explain your wireing, photos and more

The connection is made as you see in your diagram...
On pipsolar it works well and I don't have any problems. I switch to SMH and I can't get it to work

@softwarecrash
Copy link
Owner

the smh series works so i think, can you explain your wireing, photos and more

The connection is made as you see in your diagram... On pipsolar it works well and I don't have any problems. I switch to SMH and I can't get it to work

pipsolar have a lot of implemented protocols, i dont have all at the moment.
without know what your device speaks i cant fix it.
double check your wireing for twisted data lines and/or try to swap it

@avenseElectro
Copy link
Author

the smh series works so i think, can you explain your wireing, photos and more

The connection is made as you see in your diagram... On pipsolar it works well and I don't have any problems. I switch to SMH and I can't get it to work

pipsolar have a lot of implemented protocols, i dont have all at the moment. without know what your device speaks i cant fix it. double check your wireing for twisted data lines and/or try to swap it

I just find it strange that the pipsolar I have (pip30) works fine and when I change to the Easun smh II 4.2kw it stops working.
But ok I'll check the connections but I'm almost certain that it's clear that the pipsolar where it uses the pip30 protocol works fine.

@softwarecrash
Copy link
Owner

Pipsolar have a Lot more as the single pi30 Protocol, WE need to find Out what your device Talk in Details.
Can you get a RAW or debug Log of communication from your device?
Or use watchppwer to created a communication log

@avenseElectro
Copy link
Author

I've tried several times and re-read the connections and they're all ok.
Remembering that just connect to the pipsolar inverter (pip30 protocol works)
Tell me how to debug watchpower....

@softwarecrash
Copy link
Owner

I've tried several times and re-read the connections and they're all ok. Remembering that just connect to the pipsolar inverter (pip30 protocol works) Tell me how to debug watchpower....

start watchpower, right click on the litle icon on the task bar(next to clock) and click on debug, a folder opens. when watchpower is connected and read data the folder will fill up with files. zip it and upload it here

@avenseElectro
Copy link
Author

I've tried several times and re-read the connections and they're all ok. Remembering that just connect to the pipsolar inverter (pip30 protocol works) Tell me how to debug watchpower....

start watchpower, right click on the litle icon on the task bar(next to clock) and click on debug, a folder opens. when watchpower is connected and read data the folder will fill up with files. zip it and upload it here

What do you need from here?

Captura de ecrã 2024-10-21 182021

@avenseElectro
Copy link
Author

I've tried several times and re-read the connections and they're all ok. Remembering that just connect to the pipsolar inverter (pip30 protocol works) Tell me how to debug watchpower....

start watchpower, right click on the litle icon on the task bar(next to clock) and click on debug, a folder opens. when watchpower is connected and read data the folder will fill up with files. zip it and upload it here

Here is the watchpower debug.

debug.zip

@softwarecrash
Copy link
Owner

thank you, so the little problem is simple.
i ask the devices for QPI the most answer with 18 or 30 was the protocol version is, but yours doenst answer with anything.
short crude fix, but try it
Solar2MQTT_1.2.0-Pre5A3_OTA.bin.zip

@avenseElectro
Copy link
Author

avenseElectro commented Oct 21, 2024

thank you, so the little problem is simple. i ask the devices for QPI the most answer with 18 or 30 was the protocol version is, but yours doenst answer with anything. short crude fix, but try it Solar2MQTT_1.2.0-Pre5A3_OTA.bin.zip

Unfortunately it also doesn't work with the version you sent.

But you have it on your github stating that this inverter works.... Why isn't mine working?

@softwarecrash
Copy link
Owner

thank you, so the little problem is simple. i ask the devices for QPI the most answer with 18 or 30 was the protocol version is, but yours doenst answer with anything. short crude fix, but try it Solar2MQTT_1.2.0-Pre5A3_OTA.bin.zip

Unfortunately it also doesn't work with the version you sent.

But you have it on your github stating that this inverter works.... Why isn't mine working?

possible that your device have different firmware
what tells the web serial now?

@avenseElectro
Copy link
Author

thank you, so the little problem is simple. i ask the devices for QPI the most answer with 18 or 30 was the protocol version is, but yours doenst answer with anything. short crude fix, but try it Solar2MQTT_1.2.0-Pre5A3_OTA.bin.zip

Unfortunately it also doesn't work with the version you sent.
But you have it on your github stating that this inverter works.... Why isn't mine working?

possible that your device have different firmware what tells the web serial now?

[WebSerial] Connecting...
[WebSerial] Connected...
[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C:  QVFW][CR:    0][CC:    0][L:   3]

QVFW:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Modbus device

Invalid Slave ID

Invalid Slave ID

Time-out
Invalid Slave ID

Invalid Slave ID

Invalid Slave ID

Invalid Slave ID

Time-out

Invalid Slave ID

Invalid Slave ID

Time-out

----------------- Start Autodetect -----------------
[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)
[C:  QVFW][CR:    0][CC:    0][L:   3]

QVFW:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

[C:   QPI][CR:    0][CC:    0][L:   3]

[C:  QVFW][CR:    0][CC:    0][L:   3]

QVFW:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)
[C:  QVFW][CR:    0][CC:    0][L:   3]

QVFW:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Invalid Slave ID

Invalid Slave ID

Time-out
Invalid Slave ID
Invalid Slave ID

Time-out

Invalid Slave ID

Invalid Slave ID

Time-out

Invalid Slave ID

Invalid Slave ID
[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C:  QVFW][CR:    0][CC:    0][L:   3]

QVFW:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

@softwarecrash
Copy link
Owner

thats curios. so i send the same QVFW comand as the watchpower but your device answer with NAK
lets try with another comand
Solar2MQTT_1.2.0-Pre5A4_OTA.bin.zip

@avenseElectro
Copy link
Author

avenseElectro commented Oct 21, 2024

thats curios. so i send the same QVFW comand as the watchpower but your device answer with NAK lets try with another comand Solar2MQTT_1.2.0-Pre5A4_OTA.bin.zip

That's strange...


[WebSerial] Connecting...
[WebSerial] Connected...
[C:  QMOD][CR:    0][CC:    0][L:   3]

QMOD:		 NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C:  QMOD][CR:    0][CC:    0][L:   3]

QMOD:		 NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

seems to interrupt

Captura de ecrã 2024-10-21 210225

@softwarecrash
Copy link
Owner

softwarecrash commented Oct 21, 2024

ok your device speaks a different language, it answer on all with NAK
yes that interrupt, have some exception that i dont find, its a bug for later.
so last try is to get a raw communication snipet from your com port of the pc, it exsist some software that can do that

edit: can you see the com baudrate in watchpower?
edit2: you can try this https://github.com/syssi/esphome-smg-ii/ its modbus variant, just for try, or pipsolar.

@avenseElectro
Copy link
Author

ok your device speaks a different language, it answer on all with NAK yes that interrupt, have some exception that i dont find, its a bug for later. so last try is to get a raw communication snipet from your com port of the pc, it exsist some software that can do that

edit: can you see the com baudrate in watchpower? edit2: you can try this https://github.com/syssi/esphome-smg-ii/ its modbus variant, just for try, or pipsolar.

I've tried that one and it didn't work either.
19200
Captura de ecrã 2024-10-21 212600

@softwarecrash
Copy link
Owner

ok your device speaks a different language, it answer on all with NAK yes that interrupt, have some exception that i dont find, its a bug for later. so last try is to get a raw communication snipet from your com port of the pc, it exsist some software that can do that
edit: can you see the com baudrate in watchpower? edit2: you can try this https://github.com/syssi/esphome-smg-ii/ its modbus variant, just for try, or pipsolar.

I've tried that one and it didn't work either. 19200 Captura de ecrã 2024-10-21 212600

wait ... the default speed for PI protocols is 2400, so thats fucking fast. let me build short a version that changes to 19200

@softwarecrash
Copy link
Owner

softwarecrash commented Oct 21, 2024

changes on QVFW querry to 19200
Solar2MQTT_1.2.0-Pre5A5_OTA.bin.zip

dont know its a typo error or right, at the top of it stand modbus settings, so its possible that you have a version that speaks modbus

@softwarecrash
Copy link
Owner

@all-solutions need your assitance here for watchpower and com monitoring

@avenseElectro
Copy link
Author

avenseElectro commented Oct 21, 2024

changes on QVFW querry to 19200 Solar2MQTT_1.2.0-Pre5A5_OTA.bin.zip

dont know its a typo error or right, at the top of it stand modbus settings, so its possible that you have a version that speaks modbus

Unfortunately it didn't work either....

I would suggest removing this inverter model from your "inverters that work"

my inverter is that https://pt.aliexpress.com/item/1005006361049535.html?spm=a2g0o.order_list.order_list_main.5.4dbdcaa4ncfHFi&gatewayAdapt=glo2bra

@softwarecrash
Copy link
Owner

softwarecrash commented Oct 21, 2024

changes on QVFW querry to 19200 Solar2MQTT_1.2.0-Pre5A5_OTA.bin.zip
dont know its a typo error or right, at the top of it stand modbus settings, so its possible that you have a version that speaks modbus

Unfortunately it didn't work either....

I would suggest removing this inverter model from your "inverters that work"

try to aks your seller for the comunication protocol, thtas was helpfull too

not so fast ;)
so here someone wrote that a device with this name works, so your device is different from other with same name, wait for all-sollutions, he can explain you how to get raw data from the com port comunication, with this data we can clearly see whats going on with your device

@avenseElectro
Copy link
Author

avenseElectro commented Oct 21, 2024

changes on QVFW querry to 19200 Solar2MQTT_1.2.0-Pre5A5_OTA.bin.zip
dont know its a typo error or right, at the top of it stand modbus settings, so its possible that you have a version that speaks modbus

Unfortunately it didn't work either....
I would suggest removing this inverter model from your "inverters that work"

try to aks your seller for the comunication protocol, thtas was helpfull too

not so fast ;) so here someone wrote that a device with this name works, so your device is different from other with same name, wait for all-sollutions, he can explain you how to get raw data from the com port comunication, with this data we can clearly see whats going on with your device

Ok, I've already asked but I doubt I'll get an answer...
In this article he mentions that it didn't work... It's not the same inverter

@softwarecrash
Copy link
Owner

softwarecrash commented Oct 21, 2024

changes on QVFW querry to 19200 Solar2MQTT_1.2.0-Pre5A5_OTA.bin.zip
dont know its a typo error or right, at the top of it stand modbus settings, so its possible that you have a version that speaks modbus

Unfortunately it didn't work either....
I would suggest removing this inverter model from your "inverters that work"

try to aks your seller for the comunication protocol, thtas was helpfull too
not so fast ;) so here someone wrote that a device with this name works, so your device is different from other with same name, wait for all-sollutions, he can explain you how to get raw data from the com port comunication, with this data we can clearly see whats going on with your device

Ok, I've already asked but I doubt I'll get an answer... In this article he mentions that it didn't work...

try ask easun direct, looks like direct brand from him
at the bottom its a hint that it work, its the only thing i found on search your device name with qpigs or qpiri (protocol comands)

@avenseElectro
Copy link
Author

@softwarecrash the cable that came with inverter has 4 connections....
IMG_2024-10-23-13-33-35-019
IMG_2024-10-23-13-34-00-309
IMG_2024-10-23-13-34-28-389

@softwarecrash
Copy link
Owner

@softwarecrash the cable that came with inverter has 4 connections....
IMG_2024-10-23-13-33-35-019
IMG_2024-10-23-13-34-00-309
IMG_2024-10-23-13-34-28-389

2 for Data
2 for Power, Take a Look at the Wiki and Protocol folder

@avenseElectro
Copy link
Author

avenseElectro commented Oct 23, 2024

@softwarecrash
tx
rx
12v
gnd
???????
show-me wlki link please

@all-solutions
Copy link
Collaborator

all-solutions commented Oct 23, 2024

Your cable is for the wifi dongle. That's why you have also the 12v pin in that.

BTW: Can you please show us the complete wiring from your inverter to the Wemos? Perhaps there is a problem. We can not solve it, when we don't know your wiring.

show-me wlki link please

Really???
image

@avenseElectro
Copy link
Author

Your cable is for the wifi dongle. That's why you have also the 12v pin in that.

BTW: Can you please show us the complete wiring from your inverter to the Wemos? Perhaps there is a problem. We can not solve it, when we don't know your wiring.

show-me wlki link please

Really??? image

If my connection was wrong, the inverter I have that uses the pip30 wouldn't work either...

But here's my wiring:
IMG_20241022_135353
IMG_20241022_135330
IMG_20241022_120745
IMG_20241022_120926
IMG_20241022_135436
IMG_20241022_135415
IMG_20241022_120756

@avenseElectro
Copy link
Author

In the photo it shows pins D1 and D2 but it was to test the esphome at the moment it is on D6 and D7

@all-solutions
Copy link
Collaborator

OK, I have to look at the big screen tomorrow. On the phone right now, I can't see that exactly. BTW: You definitely have an SMH, not an SMG?

@avenseElectro
Copy link
Author

You definitely have an SMH, not an SMG?

Imagem WhatsApp 2024-10-24 às 15 07 00_b77e6201

@madmaximus
Copy link

Almost the same problem with my 2.2kW EASun
Screenshot_2024-11-01-06-12-41-432_com android chrome

Looks that my esp-01 could not recognize protocol

@softwarecrash
Copy link
Owner

Almost the same problem with my 2.2kW EASun Screenshot_2024-11-01-06-12-41-432_com android chrome

Looks that my esp-01 could not recognize protocol

What for easun Model?

@madmaximus
Copy link

IMG_20241101_202402
This marking on the side

@madmaximus
Copy link

A clear and concise description of what the problem is.

I can't get this inverter to work at all, can anyone help me?


[WebSerial] Connecting...
[WebSerial] Connected...
[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Modbus device

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
----------------- End Autodetect -----------------
----------------- Start Autodetect -----------------

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Protocol

[C:   QPI][CR:    0][CC:    0][L:   3]

QPI:		NAK (Length: 3)

[C: ^P005PI][CR:    0][CC:    0][L:   3]

^P005PI:		NAK (Length: 3)

Try Autodetect Modbus device

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!

Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
Invalid Slave ID

Invalid Slave ID

Time-out

Request failed!
----------------- End Autodetect -----------------

Additional context

No response

I found the solution it seems rx and tx wire wrong marking, so i just replace one to another and its works !!!
Try itz because my errors was similar
Now i have connection 😄

@miggi
Copy link

miggi commented Dec 2, 2024

The same situation for me, with EASUN SMG-II 6.2Kw, cannot make it to work. Also tried your latest recommendation to switch tx/rx, but without result.

Maybe it's connectivity issue ? No idea how to read that trobuleshooting log :)


Response Timed Out
Time-out
Request failed!
----------------- End Autodetect -----------------
ProzessData P:0 C:0
MQTT Client State: 0
Data sent to MQTT
----------------- Start Autodetect -----------------
Try Autodetect Protocol
[C: QPI][CR: 0][CC: 0][L: 3]
QPI: NOA (Length: 3)
[C: ^P005PI][CR: 0][CC: 0][L: 3]
^P005PI: NOA (Length: 3)
Try Autodetect Protocol
[C: QPI][CR: 0][CC: 0][L: 3]
QPI: NOA (Length: 3)
[C: ^P005PI][CR: 0][CC: 0][L: 3]
^P005PI: NOA (Length: 3)
Try Autodetect Protocol
[C: QPI][CR: 0][CC: 0][L: 3]
QPI: NOA (Length: 3)
[C: ^P005PI][CR: 0][CC: 0][L: 3]
^P005PI: NOA (Length: 3)
Try Autodetect Modbus device
Init MUST PV/PH 18 protocol, baud 19200, modbusAddr 4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

5 participants