Raspberry Pi talk to Infinisolar

SilverNodashi

Member
Joined
Apr 9, 2018
Messages
57
Hi,

Can anyone please help me with some basic code to get statistics from an Infinisolar 4Kw inverter, using a Raspberry Pi?

I know there is some code / scripts for the Axpert / PIP4048 inverter but it doesn't work on the InfinisolarSuper 4Kwinverter I have.
 
Wasnt daromer doing that with thi 10kW Infini?
 
hbpowerwall said:
Have you taken a look here - http://forums.aeva.asn.au/viewtopic.php?t=4332 ? Can't help with anything else sorry.

Yes I have. That inverter is different. Or, at least, the protocol for that inverter doesn't work on mine. Incidentally I have one of those inverters as well and already have a script to grab stats from it and post to emoncms.org but it doesn't work on the Infinisolar 4KW Super


daromer said:
With the protocol you can just add it to the config files for the Raspbery pi Solar-sis project i made and you have it going. I cant test it since I dont have above inverter but no problem as such.

Do you have the protocol?

My project: https://secondlifestorage.com/t-Esperyd´s-Raspberry-PI-project

Thanx, I'll see if I can figure your code out ;;)
I don't quite want to reinstall my Pi right now as it's doing other stuff as well. I have attached what I think the protocol is
 

Attachments

  • Infini-Solar 5KW protocol 20160309.pdf
    305 KB · Views: 1,153
Just install the solar-sis.

That looks like normal PIP4048 protocol and if so implemented. But check the git page and the code first
 
daromer said:
Just install the solar-sis.

That looks like normal PIP4048 protocol and if so implemented. But check the git page and the code first

This is not a normal PIP4048. I see in on the linkyour signature you refer to it as a MPI 10Kw inverter, same as the one on eBay. The PIP4048 software / protocol didn't work.
 
Siver please read and check the page again. No the MPI is not the same as PIP. they uses different protocol. But included in that software you have the protocol included for PIP4x series, MPI series and the PCM series.

The link you pasted look exactly like the PIP4048 protocol I have been using to my PIP inverter here at home.
 
daromer said:
Siver please read and check the page again. No the MPI is not the same as PIP. they uses different protocol. But included in that software you have the protocol included for PIP4x series, MPI series and the PCM series.

The link you pasted look exactly like the PIP4048 protocol I have been using to my PIP inverter here at home.

Hi,

I have downloaded the ISO, burned it to a USB stick and loaded it, but don't see the scripts for the MPI inverter. the inverter is installed in a remote location, about 4 hours from here and I now only have VPN access to it, so burning a new ISO is kinda out of the question.

Would you mind please telling me where the MPI script is, as I couldn't find it?

image_afbyxw.jpg
 
SiverNodashi: Did you check the Video? Do you have the MPI inverter or the PIP series? Either or you need to configure and set up the gatherer script and configure the port. When thats done and you enabled it to send to Influx you need to start the script.

Under the PIP dashboard you will find all 3 as examples. If you want to know where the data is stored check the configuration files for solar-sis and you can then find the values in Influx database.
 
daromer said:
SiverNodashi: Did you check the Video? Do you have the MPI inverter or the PIP series? Either or you need to configure and set up the gatherer script and configure the port. When thats done and you enabled it to send to Influx you need to start the script.

Under the PIP dashboard you will find all 3 as examples. If you want to know where the data is stored check the configuration files for solar-sis and you can then find the values in Influx database.

Hi,

Thanx for the help. I have to confess, I only watched the Youtube video for about 4 or 5 minutes and stopped since it just showed how to download and install Raspberry Pi ;) But I now watched it further and see where you explain the rest.

I have an MPI 4Kwh and MPI 10Kwh inverter (though I have a PIP4048 as well) and configured the port as hidraw0 (that's what the script picked up). The inverter isn't hooked up to the PV or batteries yet, but I now get a feed from it:

Code:
Apr 26 04:04:20 grafpi solar_mpi[4808]: [2018-04-26 04:04:20] info serial:/dev/hidraw0:SEND query/power_status
Apr 26 04:04:20 grafpi solar_mpi[4808]: [2018-04-26 04:04:20] info serial:/dev/hidraw0:SEND_RAW [{"type":"Buffer","data":[94,80,48,48,51,80,83,13]}]
Apr 26 04:04:20 grafpi solar_mpi[4808]: [2018-04-26 04:04:20] info serial:/dev/hidraw0:RECIVED_RAW Data:
Apr 26 04:04:20 grafpi solar_mpi[4808]: [2018-04-26 04:04:20] info serial:/dev/hidraw0:RECIVED query/power_status
Apr 26 04:04:20 grafpi solar_mpi[4808]: [2018-04-26 04:04:20] info influx:SEND mpi_query_power_status solar_input_power_1=0,solar_input_power_2=0,battery_power=0,ac_input_active_power_r=0,ac_input_active_power_s=0,ac_input_active_power_t=0,ac_input_total_active_power=0,ac_output_active_power_r=0,ac_output_active_power_s=0,ac_output_active_power_t=0,ac_output_total_active_power=0,ac_output_apperent_power_r=10.8,ac_output_apperent_power_s=0,ac_output_apperent_power_t=0,ac_output_total_apperent_power=10.8,ac_output_power_percentage=2,ac_output_connect_status=1,solar_input_1_work_status=0,solar_input_2_work_status=0,battery_power_direction=0,dc_ac_power_direction=0,line_power_direction=1


Since I don't know NodeJS, but rather a bit of PHP and Python, I just need to figure out how to add more data to the Grafana dashboard, like the input Volt, Ampere and Hertz, as well as the input and output volt of the 3 phases on the MPI 10Kwh.

And I need to figure out how to post to emoncms.org and pvoutput.org

P.S. Nice addition of Webmin. I haven't used it in many years and never thought of using it on a Pi, as I'm used to SSH


daromer said:
SiverNodashi: Did you check the Video? Do you have the MPI inverter or the PIP series? Either or you need to configure and set up the gatherer script and configure the port. When thats done and you enabled it to send to Influx you need to start the script.

Under the PIP dashboard you will find all 3 as examples. If you want to know where the data is stored check the configuration files for solar-sis and you can then find the values in Influx database.

Daromer: Just by the way, some of the scripts in your video are not in the ISO (anymore?) at
you have some scripts which I don't see right now:

Code:
pi@grafpi /energy-logger $ ll
total 32K
drwxr-xr-x 7 root root 4.0K Dec 12 21:09 .
drwxr-xr-x 24 root root 4.0K Dec 12 09:17 ..
-rw-r--r-- 1 root root 885 Jun 15 2017 .gitignore
drwxr-xr-x 2 root root 4.0K Dec 12 18:27 meter
drwxr-xr-x 3 root root 4.0K Dec 12 09:54 mpp
drwxr-xr-x 2 root root 4.0K Dec 12 21:15 scripts
drwxr-xr-x 4 root root 4.0K Dec 12 20:44 solar-sis
drwxr-xr-x 8 root root 4.0K Dec 12 09:11 WatchMonUdpListener

For example, you reference going into the batrium folder, which is not in the same place as on the video. I also couldn't find the batrium_reader.exe so I am not sure how to get the field values into Grafana now?

Code:
pi@grafpi /energy-logger $ cd mpp/
pi@grafpi /energy-logger/mpp $ ls
calls.json node_modules package.json project.js session.json test.js

pi@grafpi /energy-logger/WatchMonUdpListener $ sudo find / -name batrium_reader.exe
pi@grafpi /energy-logger/WatchMonUdpListener $ sudo find / -name *batrium_reader.exe
pi@grafpi /energy-logger/WatchMonUdpListener $ sudo find / -name batrium*.exe
pi@grafpi /energy-logger/WatchMonUdpListener $

The batruim service is running, though not logging:

Code:
pi@grafpi /energy-logger/WatchMonUdpListener $ sudo tail -f /var/log/solar_batrium.log
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_5431_SessionMetrics.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_5432_DailySession.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_5457_DailySession.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_5632_LifetimeMetrics.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_5732_SystemDiscovery.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_5831_DailySessionHist.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_6131_StatusComms.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_6831_QuickSessionHist.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: #033[32mLoaded file: Msg_7857_HwShuntMetrics.js#033[0m
Apr 26 04:29:36 grafpi solar_batrium[7179]: Batrium logger Server is listening at port18542

and even thought I can see in /var/log/solar_mpi.log that something is logged, it doesn't show on the dashboard either:

Code:
pi@grafpi /energy-logger/WatchMonUdpListener $ sudo tail -f /var/log/solar_mpi.log
Apr 26 04:33:38 grafpi solar_mpi[7845]: [2018-04-26 04:33:38] info serial:/dev/hidraw0:SEND query/power_status
Apr 26 04:33:38 grafpi solar_mpi[7845]: [2018-04-26 04:33:38] info serial:/dev/hidraw0:SEND_RAW [{"type":"Buffer","data":[94,80,48,48,51,80,83,13]}]
Apr 26 04:33:38 grafpi solar_mpi[7845]: [2018-04-26 04:33:38] info serial:/dev/hidraw0:RECIVED_RAW Data:
Apr 26 04:33:38 grafpi solar_mpi[7845]: [2018-04-26 04:33:38] info serial:/dev/hidraw0:RECIVED query/power_status
Apr 26 04:33:38 grafpi solar_mpi[7845]: [2018-04-26 04:33:38] info influx:SEND mpi_query_power_status solar_input_power_1=0,solar_input_power_2=0,battery_power=0,ac_input_active_power_r=0,ac_input_active_power_s=0,ac_input_active_power_t=0,ac_input_total_active_power=0,ac_output_active_power_r=0,ac_output_active_power_s=0,ac_output_active_power_t=0,ac_output_total_active_power=0,ac_output_apperent_power_r=0,ac_output_apperent_power_s=0,ac_output_apperent_power_t=0,ac_output_total_apperent_power=0,ac_output_power_percentage=0,ac_output_connect_status=0,solar_input_1_work_status=0,solar_input_2_work_status=0,battery_power_direction=0,dc_ac_power_direction=0,line_power_direction=0


the inverter is in the lab right now, so there's no PV or batteries connected yet, but it will be done in the next 6 or so hours.

image_jfzfks.jpg


image_ussqik.jpg


image_txelvb.jpg
 
Your watching a video for the old system. The new one does not have that old Batrium code done in c#. The new one is in NodeJS only.

Batrium will only log if the raspbery is on same wireless network as the Batrium is. Is it ?

And once again it does not show automatically on the dashboard because the service fetches data
1. You need to configure so the data is sent to Influx. -> You do that in the config
2. You need to add the values in the dashboard.
 
daromer said:
Your watching a video for the old system. The new one does not have that old Batrium code done in c#. The new one is in NodeJS only.

Batrium will only log if the raspbery is on same wireless network as the Batrium is. Is it ?

And once again it does not show automatically on the dashboard because the service fetches data
1. You need to configure so the data is sent to Influx. -> You do that in the config
2. You need to add the values in the dashboard.

Would you mind sharing the URL or the Video I need to watch then?
I downloaded and installed the ISO from here http://romer.se/raspv8.rar as-is, so Batrium is running on Raspberry Pi (http://192.168.10.30:3000/), thought inFlux isn't running (http://192.168.10.30:8083/#) - Still need to figure Influx out.

1. Which config files do I need to edit?
2. Which values do I need to add, where and how?

I don't know NodeJS programming at all, but have some experience in PHP5, a lot of BASH scripting and some PERL / Python coding
 
Influx is running its just the web interface that isnt enabled.

1. Check the folder with the solar-sis examples. You have one config file for commands and one for normal use.
session.json is where you set the parameter for influx:


image_cithgf.jpg


Make sure its true. Then you can see what port you can check above if influx is running. Also the pre_header.

2. see above
 
[ATTACH said:
1540[/ATTACH]
daromer pid='29431' dateline='1524835760']
Influx is running its just the web interface that isnt enabled.

1. Check the folder with the solar-sis examples. You have one config file for commands and one for normal use.
session.json is where you set the parameter for influx:


image_cithgf.jpg


Make sure its true. Then you can see what port you can check above if influx is running. Also the pre_header.

2. see above

Ok, so that's the same file I have been editing all along. See the results below:
Code:
 "serial_port": "/dev/hidraw0",
 "serial_baudrate": 2400,
 "serial_queue_delay": 200,
 "serial_parsers_readline": "\r",
 "serial_restart_threshold": 10000,
 "serial_clear_command_queue_on_restart": true,
 "http_port": 3001,
 "influx_pre_header": "pip_",
 "influxUrl": "http://localhost:8086/write?db=powerwall&precision=s",
 "IntervalCommands": [
  {
   "name": "general_status",
   "config": "query_config",
   "command": "query/general_status",
   "interval": 3000,
   "max": 0,
   "influx": true
  },


Yet I cannot connect to http://192.168.10.30:8083/#


image_abkzgv.jpg


image_sanlrw.jpg


Code:
pi@grafpi /energy-logger/mpp $ tail -f /var/log/solar_mpi.log
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx { Error: connect ECONNREFUSED 127.0.0.1:8086
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx  at Object.exports._errnoException (util.js:1020:11)
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx  at exports._exceptionWithHostPort (util.js:1043:20)
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx  at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx stack: 'Error: connect ECONNREFUSED 127.0.0.1:8086\n  at Object.exports._errnoException (util.js:1020:11)\n  at exports._exceptionWithHostPort (util.js:1043:20)\n  at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)',
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx code: 'ECONNREFUSED',
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx errno: 'ECONNREFUSED',
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx syscall: 'connect',
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx address: '127.0.0.1',
Apr 28 08:45:00 grafpi solar_mpi[5932]: [2018-04-28 08:45:00] ERR! influx port: 8086 }
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] info serial:/dev/hidraw0:SEND query/general_status
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] info serial:/dev/hidraw0:SEND_RAW [{"type":"Buffer","data":[94,80,48,48,51,71,83,13]}]
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] info serial:/dev/hidraw0:RECIVED_RAW Data:
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] info serial:/dev/hidraw0:RECIVED query/general_status
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] info influx:SEND mpi_query_general_status solar_input_voltage_1=NaN,solar_input_voltage_2=NaN,solar_input_current_1=NaN,solar_input_current_2=NaN,battery_voltage=NaN,battery_capacity=NaN,battery_current=NaN,ac_input_voltage_r=NaN,ac_input_voltage_s=NaN,ac_input_voltage_t=NaN,ac_input_frequency=NaN,ac_input_current_r=NaN,ac_input_current_s=NaN,ac_input_current_t=NaN,ac_output_voltage_r=NaN,ac_output_voltage_s=NaN,ac_output_voltage_t=NaN,ac_output_frequency=NaN,ac_output_current_r=NaN,ac_output_current_s=NaN,ac_output_current_t=NaN,inner_temperature=NaN,component_max_temperature=NaN,external_battery_temperature=NaN
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx Error: connect ECONNREFUSED 127.0.0.1:8086
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx  at Object.exports._errnoException (util.js:1020:11)
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx  at exports._exceptionWithHostPort (util.js:1043:20)
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx  at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx { Error: connect ECONNREFUSED 127.0.0.1:8086
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx  at Object.exports._errnoException (util.js:1020:11)
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx  at exports._exceptionWithHostPort (util.js:1043:20)
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx  at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx stack: 'Error: connect ECONNREFUSED 127.0.0.1:8086\n  at Object.exports._errnoException (util.js:1020:11)\n  at exports._exceptionWithHostPort (util.js:1043:20)\n  at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)',
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx code: 'ECONNREFUSED',
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx errno: 'ECONNREFUSED',
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx syscall: 'connect',
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx address: '127.0.0.1',
Apr 28 08:45:02 grafpi solar_mpi[5932]: [2018-04-28 08:45:02] ERR! influx port: 8086 }



Right now I have the Pi connected to my PIP inverter at home, since the MPI inverter is installed about 5 hours' drive from here right now.
In theory they should work the same, right?

How does it distinquish between the PIP and MPI inverters?
 

Attachments

  • image_abkzgv.jpg
    image_abkzgv.jpg
    165.3 KB · Views: 289
Once again 8083 is the web interface and its not enabled in last version. In the config I pasted It says 8086 that is the api itself for the database.

It does not distringuish between them. You start the one with the right config configured on the right port. There is different protocol for them each. I have not made it to consider what to use as of now.
 
daromer said:
Once again 8083 is the web interface and its not enabled in last version. In the config I pasted It says 8086 that is the api itself for the database.

It does not distringuish between them. You start the one with the right config configured on the right port. There is different protocol for them each. I have not made it to consider what to use as of now.

ok, let's forget about the influx port. I cannot get it to collect data from the inverter. If you look at the errors I posted, how do I get the scripts on your ISO to collect the data and post to a DB?
 
The following instructions below is only for the PIP (not the Batrium etc.) as that's all I have but for the PIP you need to make sure you have the right device/serial port selected. If you use the USB cable, then you need to find the right HID device. It could be hidraw0 or hidraw1 or hidraw2 etc. Run this command 'dmesg | grep hidraw'

See below my raspberry pi output. It'll show I have two devices hidraw1 and hidraw2 for my Logitech keyboard. But there's hidraw0 that I highlighted in red that is a generic hid. That'll be your PIP. So in your serial_port parameter, in my case, I would put in /dev/hidraw0

root@grafpi:~# dmesg | grep hidraw
[ 0.769032] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.256707] hid-generic 0003:0665:5161.0001: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.2/input0
[ 3.336938] logitech-djreceiver 0003:046D:C52B.0004: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.3/input2
[ 3.509073] logitech-hidpp-device 0003:046D:404B.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K400] on usb-3f980000.usb-1.3:1
 
not2bme said:
The following instructions below is only for the PIP (not the Batrium etc.) as that's all I have but for the PIP you need to make sure you have the right device/serial port selected. If you use the USB cable, then you need to find the right HID device. It could be hidraw0 or hidraw1 or hidraw2 etc. Run this command 'dmesg | grep hidraw'

See below my raspberry pi output. It'll show I have two devices hidraw1 and hidraw2 for my Logitech keyboard. But there's hidraw0 that I highlighted in red that is a generic hid. That'll be your PIP. So in your serial_port parameter, in my case, I would put in /dev/hidraw0

root@grafpi:~# dmesg | grep hidraw
[ 0.769032] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.256707] hid-generic 0003:0665:5161.0001: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.2/input0
[ 3.336938] logitech-djreceiver 0003:046D:C52B.0004: hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.3/input2
[ 3.509073] logitech-hidpp-device 0003:046D:404B.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K400] on usb-3f980000.usb-1.3:1

Hi,

Thanx, mine uses hidraw0 and I already have that in the sessions.js file.


I have now re-downloaded the http://romer.se/raspv8.rar Image file, re-imaged it to my SD card and started from scratch. Watching the video again to see what I missed, I did pickup some errors, which I previously ignored since I know knew how to get around the problems. But this leads me to believe that perhaps the ISO is missing something?

At 1:17 in the videowhere he searches the port, it gives s clear response, yet on my Pi, the output has some errors:



image_dvtova.jpg


And I also noticed that theserialport-list.js symlink refers to a file that doesn't exist anymore:
Code:
root@grafpi:/energy-logger/scripts# ll
total 36
lrwxrwxrwx 1 root root 46 Oct 17 2017 batrium.service -> ../WatchMonUdpListener/startup/batrium.service
-rwxr-xr-x 1 root root 181 Dec 11 13:16 deploy.sh
-rwxr-xr-x 1 root root 78 Oct 22 2017 enable.sh
-rwxr-xr-x 1 root root 384 Jun 15 2017 list_serial.sh
-rw-r--r-- 1 root root 489 Dec 12 20:27 meter.service
lrwxrwxrwx 1 root root 65 Apr 29 20:59 serialport-list.js -> /energy-logger/MPP/node_modules/serialport/bin/serialport-list.js
-rw-r--r-- 1 root root 282 Oct 21 2017 solar.conf
-rw-r--r-- 1 root root 539 Dec 12 23:06 solar_mpi.service
-rw-r--r-- 1 root root 534 Dec 12 23:07 solar_pcm.service
-rw-r--r-- 1 root root 519 Dec 12 23:08 solar_pip.service
root@grafpi:/energy-logger/scripts# ll serialport-list.js
lrwxrwxrwx 1 root root 65 Apr 29 20:59 serialport-list.js -> /energy-logger/MPP/node_modules/serialport/bin/serialport-list.js
root@grafpi:/energy-logger/scripts# ll /energy-logger/
.gitignore      meter/        mpp/         scripts/       solar-sis/      WatchMonUdpListener/
root@grafpi:/energy-logger/scripts# ll /energy-logger/mpp/
calls.json  node_modules/ package.json project.js  session.json test.js
root@grafpi:/energy-logger/scripts# ll /energy-logger/mpp/node_modules/
ansi-regex/       core-util-is/      ini/           number-is-nan/      safe-buffer/       tar-fs/
aproba/         debug/          isarray/         object-assign/      semver/         tar-stream/
are-we-there-yet/    deep-extend/       is-fullwidth-code-point/ once/          serialport/       tunnel-agent/
.bin/          delegates/        minimist/        os-homedir/       set-blocking/      unzip-response/
bindings/        end-of-stream/      mkdirp/         prebuild-install/    signal-exit/       util-deprecate/
bl/           expand-template/     ms/           process-nextick-args/  simple-get/       wide-align/
chownr/         gauge/          nan/           promirepl/        string_decoder/     wrappy/
code-point-at/      github-from-package/   node-abi/        pump/          string-width/      xtend/
commander/        has-unicode/       noop-logger/       rc/           strip-ansi/
console-control-strings/ inherits/        npmlog/         readable-stream/     strip-json-comments/
root@grafpi:/energy-logger/scripts# ll /energy-logger/mpp/node_modules/se
semver/    serialport/  set-blocking/
root@grafpi:/energy-logger/scripts# ll /energy-logger/mpp/node_modules/serialport/bin
bin/     binding.gyp
root@grafpi:/energy-logger/scripts# ll /energy-logger/mpp/node_modules/serialport/bin/
echo.js     find-arduino.js list.js     repl.js     terminal.js   write-a-lot.js
root@grafpi:/energy-logger/scripts# ll /energy-logger/mpp/node_modules/serialport/bin/
 
Yeah that video is old. Daromer updated the code with his new solar-sis package and that is probably the old code you're looking at.

This is what you should be getting. I didn't go too far with his version because it didn't fit my needs but here's what it looks like on my pi:

root@grafpi:/energy-logger/solar-sis/example/PIP4084# ls -las
total 28
4 drwxr-xr-x 3 root root 4096 Dec 12 16:01 .
4 drwxr-xr-x 5 root root 4096 Dec 12 02:52 ..
4 -rwxr-xr-x 1 root root 3075 Apr 18 22:12 calls.json
4 drwxr-xr-x 189 root root 4096 Dec 12 16:03 node_modules
4 -rw-r--r-- 1 root root 103 Dec 12 02:52 package.json
4 -rwxr-xr-x 1 root root 1622 Dec 12 02:52 project.js
4 -rwxr-xr-x 1 root root 864 Apr 23 19:31 session.json
root@grafpi:/energy-logger/solar-sis/example/PIP4084# node project.js
[2018-04-29 16:09:58] http localhost Listening on port: 3001
[2018-04-29 16:09:58] info serial:/dev/hidraw0 Open serial port
[2018-04-29 16:09:58] info queue:ADD_INTERVAL query/general_status:QPIGS
[2018-04-29 16:09:58] info queue:ADD_INTERVAL query/device_rated_information:QPIRIT
[2018-04-29 16:10:00] info serial:/dev/hidraw0:RECIVED_RAW Data: (B?? Length: 4
[2018-04-29 16:10:00] info serial:/dev/hidraw0:RECIVED_RAW Data: (123.3 59.9 120.1 60.0 0240 0211 008 225 28.50 004 053 0035 0012 089.3 28.50 00000 00010110 00 00 00342 110?P Length: 112
[2018-04-29 16:10:01] info serial:/dev/hidraw0:RECIVED_RAW Data: (120.0 25.0 120.0 60.0 13.0 3000 2400 24.0 25.5 23.0 28.7 28.6 2 10 050 0 2 3 6 10 0 0 26.0 0 0?? Length: 99
[2018-04-29 16:10:08] info serial:/dev/hidraw0:SEND query/general_status
[2018-04-29 16:10:08] info serial:/dev/hidraw0:SEND_RAW [{"type":"Buffer","data":[81,80,73,71,83,183,169,13]}]
[2018-04-29 16:10:09] info serial:/dev/hidraw0:RECIVED_RAW Data: (123.4 59.9 120.2 60.0 0240 0215 008 226 28.50 003 053 0035 0012 089.3 28.50 00000 00010110 00 00 00342 110?? Length: 115
[2018-04-29 16:10:09] info serial:/dev/hidraw0:RECIVED query/general_status
[2018-04-29 16:10:09] info influx:SEND pip_query_general_status grid_voltage=123.4,grid_frecuency=59.9,ac_output_voltage=120.2,ac_output_frecuency=60,ac_output_power_va=240,ac_output_active_power=215,output_load_percent=8,bus_voltage=226,battery_voltage=28.5,battery_charging_current=3,battery_capacity=53,inverter_heat_sink_temperature=35,pv_input_current_for_battery=12,pv_input_voltage_1=89.3,battery_voltage_from_scc=28.5,battery_discharge_current=0,device_status=00010110,charging_scc=1,charging_ac=1,charging_scc_acc=0
^C
root@grafpi:/energy-logger/solar-sis/example/PIP4084#
 
Back
Top