MXCHIP -> Openlog - Githubissues

Palamedes1 commented 9 months ago

Hello,

First of all I would like to thank Damian for sharing all of his work, it has been a great help to me.

I have 3 WVC-inverters (wifi), 2x WVC-350 and 1x WVC-1200. I would like to integrate these into my home-assistant, if possible, using esphome. So I looked at all documentation and opened one of my WVC-350 inverters.

Unfortunately, my inverter has a different communications-chip (the MXCHIP EMW3080-E). However, the layout looks (more or less) the same and I traced the VDD, GND and UART TX to the same J4-pins Damian did.

WVC-350

I removed the MXCHIP and connected jumper wires to the J4-pins and then connected those to an Openlog. Unfortunately, my inverter does not output the same kind of “messages/telgrams” as I found in this repository. In fact, the OpenLog only outputs one or two (seemingly random) characters once in a while.

So, time to troubleshoot. I have a few questions about the setup you used:

Did you remove the communication chip (HF-LPT270) and connect the OpenLog directly to J4, or did you solder wires to the HF-LPT270 and connect those to the OpenLog?
If you kept the HF-LPT270 in place, was it connected to the wifi -> Chinese cloud server??
What config-file did you use for the OpenLog? I used: 115200,26,3,0,1,1,0 baud,escape,esc#,mode,verb,echo,ignoreRX

damianburrin commented 9 months ago

You need the serial port to deal with all the handshaking. I tapped the wires

You can either solder to top or i took the chip out and then put the jumper wire in the socket and push the serial chip back in

I don't think i changed any thing on open log. If i did it was just speed.

But sureci left it stock

Palamedes1 commented 8 months ago

Hi Damian,

Thanks for your reply. I was finally able to do some testing, but I'm still having some problems:

I soldered a jumper cable on top of the TX connector and connected it to my openlog. Then I powered up the inverter and waited a few hours. When I later checked the logs, there were two files created. The contents of the first file (1,292 kb) are unreadable to me:

� � � @�p � ��0 @�~x �@@ � @�0 � @ � ��,�� @ � � p � �p � � 8�� @ @ �B�h � �p��> C � p�� ( � � 3�� �@� � X �� @ � &�� 0��p \��~< �� lxd8 @ �p�� O�� 00 p� @@� �� @ �@ � �� @� x � ��x��x�� @�� A etc etc etc

I assume that's the handshaking you were referring to. The second file contained only:

12<

I have seen these characters before when I was logging with the MXCHIP removed.

I put the micro-sd card back in the openlog and pressed the reset button on the inverter. No idea if that would help, I think I read somewhere that the button was connected to network functionality, so I wanted to try it anyway. The log came back (after a few hours) with:

12<�� etc

Unreadable…...

So I can think of a few possibilities as to why this didn't work:

My chip uses a different communication protocol to communicate with the main board.
Something is wrong in my openlog (setting) (baud rate probably (was set to 115200)).
A connection to the cloud server is required with this chip.
Something is broken.

I think the cloud connection could be the problem. However, for security reasons, a connection to a (foreign) cloud server is not an option.

Do you have any insights, maybe I missed something?

Thanks a lot !!

damianburrin commented 8 months ago

Hi Damian,

Thanks for your reply. I was finally able to do some testing, but I'm still having some problems:

I soldered a jumper cable on top of the TX connector and connected it to my openlog. Then I powered up the inverter and waited a few hours. When I later checked the logs, there were two files created. The contents of the first file (1,292 kb) are unreadable to me:

� � � @�p � � ��0 @��~x� �@@ �� @�0 � @ �� ,�� @ � �� p� � �p �� 8�� @ @� ��B��h �� p��> C �� p��� ( �� 3�� � �@�� X �� @ �� &�� 0��p \��~< � � �� lxd8 @ �p�� O�� 0�0 p�� @@� �� @ �@� � �� @� �x � ��x��x�� @�� A � etc etc etc

I assume that's the handshaking you were referring to. The second file contained only:

12<

I have seen these characters before when I was logging with the MXCHIP removed.

I put the micro-sd card back in the openlog and pressed the reset button on the inverter. No idea if that would help, I think I read somewhere that the button was connected to network functionality, so I wanted to try it anyway. The log came back (after a few hours) with:

12<�� etc

Unreadable…...

So I can think of a few possibilities as to why this didn't work:

My chip uses a different communication protocol to communicate with the main board.

Something is wrong in my openlog (setting) (baud rate probably (was set to 115200)).

A connection to the cloud server is required with this chip.

Something is broken.

I think the cloud connection could be the problem. However, for security reasons, a connection to a (foreign) cloud server is not an option.

Do you have any insights, maybe I missed something?

Thanks a lot !!

First thing double check your open log and change the text file to ensure it is configured correctly. The data you are getting is what it would look like if you were at the wrong baud rate.

The type of chip shouldn't matter the communication protocol will be the same it's just serial. The data comes off the chip so you are collecting it before it's even transmitted to the cloud so that shouldn't be the issue.

Only connect the RX pin leave the TX and make sure its connected to the TX pin of the serial chip. Power up. Look at that serial logger - you should get a green light first and then if its recieving data you should get a flashing blue light. If you are getting that it must just be getting the right speed. Mine was 115000 but your chip might be configured slow or faster so try different settings

Hope that helps

damianburrin commented 8 months ago

One other thing I just thought of.

You will only get data if you have solar panels connected and it’s outside

Damian

From: Palamedes1 @.> Sent: Monday, November 6, 2023 4:17 PM To: damianburrin/WVC-Life-Edition-Data-Collector @.> Cc: Damian @.>; Comment @.> Subject: Re: [damianburrin/WVC-Life-Edition-Data-Collector] MXCHIP -> Openlog (Issue #4)

Hi Damian,

Thanks for your reply. I was finally able to do some testing, but I'm still having some problems:

I soldered a jumper cable on top of the TX connector and connected it to my openlog. Then I powered up the inverter and waited a few hours. When I later checked the logs, there were two files created. The contents of the first file (1,292 kb) are unreadable to me:

� � � @�p � � ��0 @��~x� �@@ �� @ �0 � @ �� ,�� @ � �� p� � �p �� 8��

�@ @� ��B��h �� p ��> C �� p�� ( �� 3�� @�� X �� @ �� &�� 0��p \��~< � � �� lxd 8 @ �p�� O�� 0� 0 p�� @@� �� @ �@� � �� @� �x � ��x��x�� @�� A � etc etc etc

I assume that's the handshaking you were referring to. The second file contained only:

12<

I have seen these characters before when I was logging with the MXCHIP removed.

I put the micro-sd card back in the openlog and pressed the reset button on the inverter. No idea if that would help, I think I read somewhere that the button was connected to network functionality, so I wanted to try it anyway. The log came back (after a few hours) with:

12<�� etc

Unreadable…...

So I can think of a few possibilities as to why this didn't work:

My chip uses a different communication protocol to communicate with the main board.
Something is wrong in my openlog (setting) (baud rate probably (was set to 115200)).
A connection to the cloud server is required with this chip.
Something is broken.

I think the cloud connection could be the problem. However, for security reasons, a connection to a (foreign) cloud server is not an option.

Do you have any insights, maybe I missed something?

Thanks a lot !!

— Reply to this email directly, view it on GitHub https://github.com/damianburrin/WVC-Life-Edition-Data-Collector/issues/4#issuecomment-1795328085 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKBERI5Y66NMXPJ6ZWJV3TYDEEQTAVCNFSM6AAAAAA6CBGLJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJVGMZDQMBYGU . You are receiving this because you commented. https://github.com/notifications/beacon/AEKBERMFZSAJJT425TACCD3YDEEQTA5CNFSM6AAAAAA6CBGLJWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTLAKEFK.gif Message ID: @. @.> >

damianburrin commented 8 months ago

I've just thought - though i'm sure you twigged this. The unit needs to be connected to a solar panel and outside or it won't power up the board.

damianburrin / WVC-Life-Edition-Data-Collector

MXCHIP -> Openlog #4