Omnik ethernetcard support

[abc1000]

Log via wifi works perfect. But how to via ethernet? (Omnik module)

[ldeng2]

Same problem for me. Somenone???

[XtheOne]

Not much info is available of the new eternet interface logger protocol. You can try the solarman android app and see if it finds the logger in local mode. If yes my newer inverter logger scripts might work.

[abc1000]

It's very new.. I tried the apps but useless.. These apps tried all wifi...

Can i connect manual to omnik:8899? and see what's happening?

btw, for now livestats.py freezes my convertor..and must reset

[XtheOne]

You can try my ScanLoggers.py script. If it does not list the inverter then it works differently then the WiFi logger which is based on iGEN firmware which uses protocol V4. I cannot find any documentation on this ethernet interface. How does the web interface looks like?

[abc1000]

Sure, where can i find it? Firmware is not changed. webinterface has no wifi network but ethernet settings. sn 190#

[XtheOne]

https://github.com/XtheOne/Inverter-Data-Logger Screenshot of the web interface?

[abc1000]

Yes found it..

This script will look for iGEN WiFi Kit loggers from SolarMAN PV List their IPs and S/Ns and connected inverters S/N These loggers are found in Omnik, Hosola, Ginlong, Kstar, Seasun, SolaX, Samil, Sofar, Trannergy and other Solar inverters WiFi kit logger found, IP = 192.168.1.211 and S/N = 190####### Listing Inverter(s) connected to this WiFi logger closing socket, scanning done! Traceback (most recent call last): File "ScanLoggers.py", line 79, in data = logger_socket.recv(1500) socket.timeout: timed out

[XtheOne]

The good thing is that it looks like it is iGEN logger based. It does connect on port 8899 but no data is received. It could be that this logger firmware does not support V4 protocol anymore. Did you try https://play.google.com/store/apps/details?id=com.yingzhen Local mode, this app supports V5 protocol. If it does not find the inverter then omnik or igen should be asked.

Maybe https://play.google.com/store/apps/details?id=com.igentech.config.activity can find it?

[abc1000]

Tried both apps allready but they searching for AP's..

[XtheOne]

Ok, then I will ask around tomorrow

[abc1000]

ok, tnx

[XtheOne]

I have sent a request for more information to the Omnik dev team. I'm not related to Omnik myself but I use their inverters.

It does reply to the broadcast frame to port 48899 with it's IP and SN It accepts the connection on port 8899 but it does not respond to the data request frame. So, why? is another contrlCode needed? Should it be a V5 request frame?

I have no TL2 with Embedded Ethernet, so cannot experiment myself...

[abc1000]

And maybe using a second (local)remote server..?

[XtheOne]

That is an option, but then you need a listner app.

[abc1000]

I'v tried nmap (linux based) but nothing special.. I don't know what else?

[XtheOne]

I received some documentation. Mainly about how to place the interface inside the inverter. Is your inverter registered on the omnik portal and can you see production data? You can try to see the data which is sent by the inverter to the portal by using wireshark. According to the documentation local logging should work...

[abc1000]

I see nothing on port 8899, only 80 (my link to webport.) How do i filter udp, tcp.? Have now only ipaddress.

Yeah, data logging to omnikportal is allright.

[XtheOne]

if you run wireshark on windows you only see packets from/to the PC. Bridging with 2 adapters is needed.

[Pietervs2]

I had an ethernetmodule installed last week. Today I discovered, they've skipped a step after installation.

The ethernetmodule that I have, has 3 lights on it, the one on the left is red, the one on the right is green when a UTP-cable is connected. The one in the middle was off. There's a small button right underneath those three, I pressed that for 3 seconds and the light in the middle came on (also red), after which it started sending data to the Omnikportal again. (In the portal I had to enter the serialnumber of the ethernetcard (1902133xxx), it automatically asked for it after the dataconnection was restored.

But (like others) I'm looking for a working script to upload the data to PVOutput again. Any help with that might me appreciated! :) (I have attached a file with output I get when I use the command "wget http://192.168.X.XX/js/status.js -q -O - ", hoping that someone can make some sense out of it. I can't find any viable variables in this file :( ) omnik-output.txt

[XtheOne]

the status.js file is what you also get from the wifi logger. Only you request the js file, not the resulting data from running this js class. I have no Onmik with a internal ethernet card so cannot test things here... A capture of data which is sent to the portal can help to see if the frame format is newer than V4 which the WiFi logger uses.

[XtheOne]

From logging I found that the ethernet logger uses a newer protocol. Up till now V4 was used and this module uses V5. I have gotten some documentation but I have no time the comming week to try to implement V5. As I have no ethernet module testing will be slow as someone else will do the tryouts.

[Pietervs2]

Hi Michel,

Great you're trying to solve this for us!

If you need any betatesters, don't hesitate to let me know!

Best regards,

Pieter

Op 1 okt. 2017 om 18:31 heeft Michel <[email protected]mailto:[email protected]> het volgende geschreven:

From logging I found that the ethernet logger uses a newer protocol. Up till now V4 was used and this module uses V5. I have gotten some documentation but I have no time the comming week to try to implement V5. As I have no ethernet module testing will be slow as someone else will do the tryouts.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Woutrrr/Omnik-Data-Logger/issues/27#issuecomment-333388464, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATihfmhD3o_WC8Lp-Mo1Yd5Y7hhxrlRVks5sn75IgaJpZM4Plreh.

[XtheOne]

I have opened an issue under my own repo https://github.com/XtheOne/Inverter-Data-Logger/issues/3 When I get something to test I will let you know.

[Pietervs2]

Hi Michel,

I see that you have an experimental setup for your script.

I hope I'll be able to test this script this weekend!

Thanks so far!

Best regards,

Pieter

Op 1 okt. 2017 om 23:25 heeft Michel <[email protected]mailto:[email protected]> het volgende geschreven:

I have opened an issue under my own repo XtheOne/Inverter-Data-Logger#3https://github.com/XtheOne/Inverter-Data-Logger/issues/3 When I get something to test I will let you know.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Woutrrr/Omnik-Data-Logger/issues/27#issuecomment-333407929, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATihfgdDcU8EJMKFztlXU1yAr2nw4JUXks5soANCgaJpZM4Plreh.

[XtheOne]

highly experimental as the command frame format is still not known. If someone can get the firmware out of the GD32F103 MCU with a jtag interface it would greatly help!

[Pietervs2]

Wil ik wel proberen, maar ik heb geen idee hoe ik dat zou kunnen doen.

Heb je tips hoe ik dat aan kan pakken?

Op 12 okt. 2017 om 19:33 heeft Michel <[email protected]mailto:[email protected]> het volgende geschreven:

highly experimental as the command frame format is still not known. If someone can get the firmware out of the GD32F103 MCU with a jtag interface it would greatly help!

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/Woutrrr/Omnik-Data-Logger/issues/27#issuecomment-336210071, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATihfvOEWe_Y7kHuIoVXzijySi1baQbGks5srk1TgaJpZM4Plreh.

[abc1000]

I'll think it's a GD32FB07..

[abc1000]

Do we need a 10p header and a programmer?

[XtheOne]

It is a GD32F107 MCU and you can read/program it with a ST-link interface.

https://hackaday.com/2013/01/07/reverse-engineering-st-linkv2-firmware/

I have no time this weekend...

[XtheOne]

Alle tools hier: http://gd32mcu.21ic.com/en/index