Esperyd?s Raspberry PI project

Solar Batteries, Panels, Chargers, Inverters & Mounts at www.batteryhookup.com Save 5% with coupon code "Powerwalls"

I'm planning to install two PIP 5kW inverters in parallel mode, in which there will be one master and one slave inverter - the master will command the slave by it's own.
Can I still use the solar-pip commands, controlling the master unit, or I will need other type of command, does anybody know and tested?
 
You can and some people have. Think there is parts for the protocol on github to.
 
Hi
I've been following your project for a long time and I want to congratulate you for your development.
Today my raspberry pi 4 arrived =) and I started following the manual:

Raspberry PI solar system 2.0 - DIY Tech & Repairs

Solar system system running on Raspberry pi to monitor, graph and manage your home built solar system. Supports several BMS types and have all key features like MQTT, Node-Red, Influxdb and among other stuff. Its also built so you easily can add more software thanks to SensorsIOT
diytechandrepairs.nu diytechandrepairs.nu

However, I came across some doubts and at the last step of the manual I had an error.

1st: Can I use my inverter with the solar system 2.0?
I use three-phase at home so I have 3 off-grid inverters (I only have 1 connected to raspberry pi 4 to test, for now).
This is the link of my inverter:
https://pt.aliexpress.com/item/3296...u&albcp=12838283515&pvid=53d59f51-d235&nstaff. = 539263010115 & TERMINAL_ID = 451034c810174cf38ee70cee39f0563c & needSmbHouyi = false & albbt = Google_7_shopping & src = google & crea = pt32969834923 & aff_fcid = 42adbc92fe1b4d429f2c1735f974e904-1622662366688-05671-UneMJZVf & gclid = Cj0KCQjw2NyFBhDoARIsAMtHtZ48XAjvtXUKemg7vvCOFd1FOdKcXrtwo4NAXKUpL9fu_EBmHr2Tu5EaAv6gEALw_wcB & albag = 122 319 359 998 & aff_fsk = UneMJZVf & albch = shopping & albagn = 888888 & isSmbAutoCall = false & aff_trace_key = 42adbc92fe1b4d429f2c1735f974e904-1622662366688-05671-UneMJZVf & RMSG = do_not_replacement & DEVICE = C & gclsrc = aw.ds

2nd: Can I use the usb port to connect to the raspberry pi 4?

3rd: I did all the steps of the manual, I think everything is correct but at the last step when I had to choose the example “cd solar-sis/example“ I didn’t know which to choose but I chose the “PIP4084“, was it right?
When I ran “npm install“ it showed me the following error:

make: *** [crc16.target.mk:107: Release/obj.target/crc16/lib/crc16.o] Error 1
make: Leaving directory '/home/pi/solar-sis/example/PIP4084/node_modules/crc16/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:314:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
gyp ERR! System Linux 5.10.17-v7l+
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/solar-sis/example/PIP4084/node_modules/crc16
gyp ERR! node -v v12.22.1
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm WARN solar-sis_pip@1.0.1 No description
npm WARN solar-sis_pip@1.0.1 No repository field.
npm WARN solar-sis_pip@1.0.1 No license field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! crc16@1.0.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the crc16@1.0.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2021-06-02T18_23_10_516Z-debug.log
pi@raspberrypi:~/solar-sis/example/PIP4084 $
 
Thanks!
I cant check your link. Please post a proper link.

If its a PIP you have that use that protocol you use the one you mentioned. If its something else you might have to write your own protocol file.
The install should be run in the main folder if not mistaken. Not in the example since its "Examples" on how to configure it.
 
I found the problem my node version was old

but I had another problem in the last step running the “node project.js” =(

“If all works out fine you can now run the software. Dont forget to configure it first in session.json where you set the port and the server to send the data to.”

In this step I don't know what to do, how do I find the port? ( is it my usb port? if yes how can i see it? )
(" i change "serial_port": "/dev/usb/hiddev0", (is my ubs ) in "pi@raspberrypi:~/solar-sis/example/PIP4084/session.json ") is right ?


that's the error when i run “node project.js”



pi@raspberrypi:~/solar-sis/example/PIP4084 $ node project.js
/home/pi/solar-sis/example/PIP4084/node_modules/bindings/bindings.js:135
throw err;
^

Error: Could not locate the bindings file. Tried:
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/Debug/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/Release/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/out/Debug/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/Debug/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/out/Release/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/Release/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/default/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/compiled/16.2.0/linux/arm/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node
→ /home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/lib/binding/node-v93-linux-arm/bindings.node
at bindings (/home/pi/solar-sis/example/PIP4084/node_modules/bindings/bindings.js:126:9)
at Object.<anonymous> (/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/lib/linux.js:1:36)
at Module._compile (node:internal/modules/cjs/loader:1109:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
at Module.load (node:internal/modules/cjs/loader:989:32)
at Function.Module._load (node:internal/modules/cjs/loader:829:14)
at Module.require (node:internal/modules/cjs/loader:1013:19)
at require (node:internal/modules/cjs/helpers:93:18)
at Object.<anonymous> (/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/lib/index.js:14:22)
at Module._compile (node:internal/modules/cjs/loader:1109:14) {
tries: [
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/Debug/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/Release/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/out/Debug/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/Debug/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/out/Release/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/Release/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/build/default/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/compiled/16.2.0/linux/arm/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node',
'/home/pi/solar-sis/example/PIP4084/node_modules/@serialport/bindings/lib/binding/node-v93-linux-arm/bindings.node'
 
Last edited:
Well after much trial on error I’ve managed to install the WatchmonUDPlistener container on WSL2. While I really appreciate the effort that was put into this software, it would have been nice if the container also had a web server and would allow you to edit the config on the web. But with WSL2 it actually made it very easy to find and edit the configuration file, if you know where to look.

Since the Watchmon toolkit is a windows application only, and I already had a PC dedicated to my battery project, it made sense to run this container on the same machine.

if there’s any interest, I can do a quick write up or video that walks you through it.
 
Nice work.

Ui would always be good but i wrote the software in 2 days and then basically havent touched it :) In the beginning with no thought of container use :p
 
Hi,

I have been trying for the last few days to get the WatchMonUdp Listener running on my HA core. Im running HA on a PI3b. So far I have :

1) Installed Portainer as a add on in HA and set up the batrium volume and container.
2) Ive tried both the latest version and the amd64 version.
3) Installed the Terminal and SSH addon so I can SSH into the Pi can and change the config file but I just cant find the config file.

So according to portainer my mount path is /mnt/data/docker/volumes/batrium/_data. If I ssh in and try and find it it appears it doesnt exist.

/ $ cd mnt
mnt $ cd /data
data $ cd /docker
-bash: cd: /docker: No such file or directory

Any idea what I need to do to access the config file. Although if I look at the logs Ive got this.

1623566052319.png

Do I need InfluxDB for this to work?

Any help would be much aprreciated.

Cheers

Gareth
 
Hey Gareth,

I’m not great with a Linux command line but once you cd to /data you may have to do sudo cd /docker. But I can tell you that you should use ”latest” tag rather than the “amd64” tag since the Pi has an ARM CPU. And, from my experience, this container needs to connect to influxdb even if it’s been disabled in the config.
 
Latest version can run without influx. but yes influx is basically the core of it :)
 
Hi,

Thanks for your reply. Still no joy.

Apparently the mount path is this.

1623782307542.png

1623783187230.png

Any other ideas. I need to amend the config file but cant even find it :/

Thanks

Gareth
 
hey Daromer,

Just wondering if it the Listener tool will run on a PiZero? i tried to get it running briefly, but had no luck. just wondering if there is some reason it would not directly work on it or not?
 
Hi @daromer and everyone else,

I might be asking a bit much of the software here but I have recently got a second PCM60x and I was wondering if it's possible to run two instances of solar-sis to grab the data from both charge controllers? Do you think it's better to add an additional raspberry pi?
 
You can run 2 or 10 on the same just change the port. :) Ie the listen port in the software
 
daromer said:
You can run 2 or 10 on the same just change the port. :) Ie the listen port in the software
Click to expand...
Thanks, can you explain a little bit more please?

Do I add another line in session.json to add a second port like this-?

"serial_port": "/dev/ttyUSB0"
"serial_port": "/dev/ttyUSB1"

Or do I create a second service in webmin somehow?
 
You need 2 services and they Will have to run each on their own Serial port. But you also need to change the TCP port that the software listens on. Dont remember what file that is in right now though.
 
You must log in or register to reply here.
Back
Top