Fronius

L'Abril de 2022 me la fan la gent de Nou6tema

8.892 + 1.867 (21 % IVA) = 10.760 € -> pressupost

20220419 : porten 14 plaques Risen RSM144-7-450M de 450 Wp = 6,3 kWp / 19,29 m2 :

• P(max) = 450 W
• V(Pmax) = 41,30 V
• I(Pmax) = 10,90 A
• V(oc) = 49,70 V
• I(sc) = 11,50 A
• 144 cell Monocrystaline PERC module : 6 x 12 + 6 x 12
• cell size : 166 x 83 mm = 13.778 mm2 = 1,38 m2
• 20,6 % maximum efficiency
• pes : 24,5 Kg
• dimensions : 2108 x 1048 x 35 mm

inversor Fronius Primo 5.0-1 : specs

• number of MPP trackers = 2

• MPP voltage range (Umpp min - Umpp max) = 240 - 800 V

• usable MPP voltage range = 80 - 800 V

• number of DC connections = 2 + 2

• max. PV generator power (Pdc max) = 7,5 kW peak

• AC nominal output (Pac,r) = 5.000 W

• el inversor genera un nivel de potencia acústica máximo de < 65 dB

• inclou DataManager "101" - versio firmware 3.26.1-3 : use Solar Web -> Settings -> Components

  A través de la conexión a Internet mediante LAN o WLAN, el Fronius "Datamanager" transmite los valores de la instalación fotovoltaica directamente al portal online Fronius Solar.web para proporcionar en todo momento una vista general sobre el funcionamiento de la instalación.

• Smart Meter : Smart Meter 63A-1, Feed-in point (Primary meter), SN 21470645

  The Fronius "Smart Meter" monitors the energy flow in from and out to the grid and is linked via a data cable to your inverter's data manager card which compiles the information.

  Meter_Location_Current 0...grid interconnection point (primary meter)

• Part number : 4,210,063

• 2x sn [/]

• LAN MAC = 00:03:AC:40:DB:74

• WLAN MAC address = 6C:1D:EB:F7:FA:A5

• IP = 192.168.1.29 {fixed, 2022.08.01}
  nicolau@mars:~$ ping fronius + arp -a fronius (192.168.1.29) at 6c:1d:eb:f7:fa:a5 [ether] on wlx984827ca1628

• WLAN SSID : "a22" - Fronius Datamanager card is not compatible with 5 GHz Wi-Fi networks

• network diagnostics : ping solarweb.fronius.com (213.33.117.249)

• garantia : Ya disfrutas de una protección de garantía gratuita para tu Fronius Primo 5.0-1 (número de serie: 33193718).
  Esto te proporciona una garantía completa para tu producto Fronius hasta el 18.04.2029.

• proteccio : IP65, IP67. Amb IP65 suficient, IP67 vol dir summergir l'equip dins l'aigua

• strings : fem 2 strings - un de 8 plaques (mirant al Est), un de 6 plaques (mirant al Oest)

  A series-connected set of solar cells or modules is called a "string".

The Power Point Tracker is a high-frequency DC to DC converter. They take the DC input from the solar panels, change it to high-frequency AC, and convert it back down to a different DC voltage and current to exactly match the panels to the batteries.

theory and operation of "Maximum Power Point Tracking"

• Lu a Ju : de 9 a 17 ; Vi : de 9 a 14 h

• centralita : +34 91 649 60 40

• hotline soporte tecnico Solar Energy : +34 91 649 60 30

• email pv-support-spain@fronius.com, pv-support-australia@fronius.com -> use this platform : https://solar-sos.fronius.com/

  Número de caso: CAS-1719338-D1R4L5

• de la seva pagina trec contact@fronius.com - hi escric 2024.12.20

• tech support form

• canal uTube

• Fronius Solar SOS - ver códigos de estado de los inversores, verificar la garantía de tu equipo, descargar manuales de operación

• formulario de contacto

• photovoltaikforum.com (en alemany)

• Fronius Primo 3.0-1 - 8.2-1 operating instructions , as status codes

Dates importants :

• Abril 2022 : posem plaques solars amb Nou6tema
• Abril de 2023 : passem Torrelles a BonPreu-Esclat

Energia XX1 - u(ss), p(E-vin-19)

Energia XX1 - u(ss), p(Ev19)

Es interessant "Mi Consumo" -> "Escollir periode" + "Vista por factura" -> "Guardar com full de calcul" + format CSV

Hi ha els preus per hora (*** excepte la darrera factura ***)

See nicolau@mars:~/sebas/endesa/factures_per_anys/1_factures_tot_2019-2022.ods

See balanç energetic del dia

See 2021

20230414 : passem a *** Bonpreu Esclat ***

Quadre al principi de la factura, sense impostos

Veure els meus canvis de potencia amb Energia XXI

Ho podem fer en batch, on demand, mitjançant

• les dades de potencia gravades cada minut
  # PKW - guardar en CSV la energia del darrer minut, produida, consumida i la entrada/sortida de la xarxa */1 * * * * /home/pi/python/pkw/eines/veure_potencia_instant/4_veure_potencia_instant_i_esciure_a_fitxer.py

  out : /home/pi/python/pkw/dades/potencies/csv/, as pot_CSV_2022_09_04.csv, contenint :

  szTemps, p_pv, p_load, p_grid {timestamp, produccio, consum, compra/venda} 18:44,1086,-285,-800 18:45,1046,-280,-765 18:46,1029,-297,-731

• el preu de la energia que compro cada hora es grava cada nit
  # PKW - llegir preus de REE a les 22 h i 0 minuts : PVPC = jo compro 00 22 * * * /home/pi/python/pkw/eines/ree/1_get_preu_pvpc.sh out : /home/pi/python/pkw/dades/ree/pvpc/preu_PVPC_Y2022-M07-D29.json

• el preu de la energia que venc cada hora es grava cada nit
  # PKW - llegir preus de REE a les 22 h i 5 minuts : PCEX = jo venc 05 22 * * * /home/pi/python/pkw/eines/ree/2_get_preu_excedente.sh out : /home/pi/python/pkw/dades/ree/pcex/preu_PCEX_Y2022-M07-D29.json

Podem llegir un preu "vell" (fent servir un "token") mitjançant : PVPC = jo compro, PCEX = jo venc

Tenim una eina per comprovar que el token funciona, que no ha caducat
Es el que sembla dir la seva pagina - que caduquen

30 de juny a 31 de Juliol - see detalls factura Agost 2022 o pdf

A la factura hi trobem (ells fan una lectura cada 15 minuts, cuartorario) :

Faig jo el calcul

Per un altra banda, cada dia a les 22:55 {compte amb l'horari d'hivern} guardem la energia que hem poduit i hem consumit en tot el dia:
{R4 crontab /home/pi/python/fronius/1_llegir_energia.py -> pi@R4:~/python/fronius/energies_per_dies.log}

Fa servir la crida

Els valors dels darrers periodes son :

• {/home/nicolau/sebas/energia_solar/fronius/dades/produccio_maig_2022_endavant.ods}
• {/home/nicolau/sebas/energia_solar/fronius/dades/sag_2023.ods}

Aquest valor coincideix perfectament amb la lectura que dona la APP i que guardem aqui

Si ens falta algun dia, podem llegir des Archive

Per fer grafiques, llegim les dades del R4 al Minie amb

Per importar, fem

1. copiar de la pagina web
2. aquí picar boto dret en una casella
3. Paste especial -> Paste especial -> Use text import dialog
4. delimiter := "*"

See Fronius APIs

Events :

• 20220624 - MPP2 deix de produir - del 25.06.2022 fins 06.07.2022
• 20241025 - se'n va la llum fins 20241026 12h

Finalment, comptem la energia produida en 1 dia

• a partir de les mostres q agafem cada 5 segons.
  { cron /pkw/eines/analitzar_un_dia/energia_1_dia.py -> /pkw/logs/energia_pkw.log }

• de la API : GetPowerFlowRealtimeData.fcgi -> ["Body"]["Data"]["Inverters"]["1"]["E_Day"]
  { cron /pkw/eines/llegir_energia_generada_avui/8_llegir_energia_generada_avui.py -> /pkw/logs/energia_api.log }

• from "archive", see above

Ho fem 2 cops xq hi ha una petita discrepancia i vull saber-ne la rao

eMail Fronius !

Solar web ens diu per cada dia

• energia produida
• energia consumida
• energia autoconsum

Aquestes dades les treu del "archive" i ens en limita el accés a 3 dies ...

Naltros tenim /home/pi/python/pkw/dades/potencies/csv/, as pot_CSV_2022_09_04.csv - energia produida, consumida i diferencia (no es autoconsum)

Llavors (pi@R4:~/python/pkw/eines/analitzar_un_dia $ ./3_energies_1_dia_own_data.py 2022_10_13)

• sumem els 3 valors per tot el dia
• comprovem que hi hagi 1.440 linies :
  1 mesura per minut, 60 mesures per hora, 1440 mesures per dia

Tenim instalades 14 plaques de 450 Wp = 6.300 Wp
A ple rendiment, podrien produir 151.200 Wh en un dia

En un any hem produit (sols produccio) ... 7.684.243 Wh
Aixo son 21.053 Wh/dia de mitjana per dia
Aixi el rendiment es de 21.053/151.200 = 14 %

Prova minima i que funciona {2025.05.20} :

solarweb-query-api : PDF

Open interfaces - en, es

• Fronius Solar API (JSON)
• Fronius "push" service
• Modbus TCP (se ejecuta en una capa física de Ethernet)
• Modbus RTU (protocolo de nivel serial)

Fronius Solar Online Support - Solve your technical issues now.

Solar.SOS can be used on your PC or, away from your desktop, on a tablet or smartphone. The app is free and can be downloaded directly from the Play Store for Android.

We provide an OpenAPI interface specification file for GEN24 inverters to support client generation in multiple languages.
Download the file here https://www.fronius.com/QR-link/0025 -> solarApiv1.zip -> solarApiv1.json
To display the spec you can use https://editor.swagger.io
For proper client generation please use https://openapi-generator.tech

Requests - currently, the only request protocol supported is HTTP : use HTTP-GET requests to query data from Solar API

There are 2 types of requests : realtime and archive

• Up to 2 realtime requests are allowed to be performed in parallel with keeping a timeout of 4 seconds between two consecutive calls.
• Archive requests are not allowed to be performed in parallel and need to keep a timeout of 120 seconds between two consecutive calls.

# 2.6 Timeout, 42,0410,2012_Fronius Solar API V1.pdf

List of most interesting requests :

• {global} /solar_api/GetAPIVersion.cgi
• {realtime} /solar_api/v1/GetActiveDeviceInfo.cgi?DeviceClass=System
• {realtime} /solar_api/v1/GetInverterRealtimeData.cgi?Scope=System
• {realtime} /solar_api/v1/GetSensorRealtimeData.cgi
• {realtime} /solar_api/v1/GetMeterRealtimeData.cgi?Scope=System
• {realtime} /solar_api/v1/GetStringRealtimeData.cgi
• {realtime} /solar_api/v1/GetPowerFlowRealtimeData.fcgi
• {archive} /solar_api/v1/GetArchiveData.cgi?Scope=System

Requests take many seconds to complete with the exception of /solar_api/v1/GetPowerFlowRealtimeData.fcgi, which only takes tens of milliseconds.
It seems this fast cgi was some afterthought second process?

All JSON structures are described using Orderly JSON, a textual format for describing JSON data. Please refer to the online documentation on https://github.com/lloyd/orderly/ for details.

Acces a les parts de un JSON des python : documentacio

The response is like this ;

A specific device is identified by the string parameter DeviceId.

To know what we have, we use /solar_api/v1/GetActiveDeviceInfo.cgi?DeviceClass=System :

{realtime} /solar_api/v1/GetInverterRealtimeData.cgi

Aqui veiem la potencia que estem produint ara matex (identica a P_PV) i la energia que hem produit al llarg del dia

Here we can see the energy flow at my home entry point : (+ from grid , - to grid )

The values EnergyReal_WAC_Sum_Produced and EnergyReal_WAC_Sum_Consumed represent the values for the Smart Meter itself.
The values EnergyReal_WAC_Minus_Absolute and EnergyReal_WAC_Plus_Absolute represent the values for Solar.web.

Now it depends where the Smart Meter is installed (Feed-In-Point or Consumption-Path), so that either EnergyReal_WAC_Minus_Absolute is the same as EnergyReal_WAC_Sum_Produced or EnergyReal_WAC_Sum_Consumed.

See email

Please note, for performance reasons the URL extension is different to other Solar API requests.

It is better to use the fcgi call rather than the cgi call because it returns less data and is much faster because all the values are read from memory rather than flash storage

Aqui veiem el balanç entre energia produida i consumida

Ho tenim :

• MARS : /home/nicolau/sebas/python/fronius/7_power_flow_realtime_data.py
• R4 : /home/pi/python/fronius/1_llegir_energia.py {crontab 23:55}

De fet, es la duracio de la operacio "urllib2.urlopen(my_url).read()"

RRG 20220704 :
no me'n surto d'aconseguir per JSON l'amperatge (o la potència, m'és igual) de cada string per separat.

if we provide DeviceId, we shall use "Scope=Device"
Now we get

Lectura senzilla i acumulada :

I think it's this one :

Minimal code :

We have a nodeJS server providing these values :

I save 1-year of power sampled every 5 seconds in a RRD database, so I can produce nice graphs.

But I also store the power sampled every minute in a 1-day file. Later, in background, we shall know the energy we produced this day, and compare it to values provided by API.

Cada minut s'escriu a ~/python/pkw/logs/potencies/csv/ :

El format es

... i ocupa 28 K al dia

Archive requests shall be provided whenever access to historic device-data is possible.
Of course, the Datalogger Web can only provide what is stored in its internal memory and has not been overwritten by newer data yet. It can loose data, due to capacity reason. The number of days stored is dependent on the number of connected units to log.

There is only one CGI to access all historic data. This CGI contains detailed, summed, error and events queries.

Call is

The number of parallel queries is system wide restricted to 4 clients.

{archive} /solar_api/v1/GetArchiveData.cgi?Scope=System

Strings which include information on both date and time are always in RFC3339 format with time zone offset or Zulu marker. See Section 5.6 of RFC 3339, "Date and Time on the Internet: Timestamps"

Each channel is handled and requested by name.
Most of the channels are recorded in constant cyclic intervals which can be set between 5 and 30 minutes.
Only Digital_PowerManagementRelay_Out_∗, InverterErrors, InverterEvents and Hybrid_Operating_State are event triggered and may occure every time.

Values we can read, this is, available channels :

See page 68 of "42,0410,2012_Fronius Solar API V1_(85 pg).pdf" at "sebas@minie:~/dades/energia_solar/fronius" :

Escric a pv-customer-spain@fronius.com (Jose Frances) i obren el cas "CAS-1758271-Q1S6B8" - cant read WAC_Sum_Consumed using python on API - 20241214 - incidencia a la central.

Conecto el Android amb la APP per cable al router i poso el ThrowingStar al mig per veure que envia el Redmi 10.

Que veiem ?

• no agafa dades del Fronius, 192.168.1.229
• agafa dades encriptades de 85.31.3.249

Aixi, no podem veure el format del Request de energia consumida des la APP de Andorid

2025.02.07 - Mario Weiermaier

En relación con su consulta, el canal "EnergyReal_WAC_Sum_Consumed" solo funciona para el Ohmpilot en las solicitudes de datos archivados. Si revisa el manual de la API Solar (sección 5.2.2, página 72), verá que este canal no devuelve información, solo lo hace "EnergyReal_WAC_Sum_Produced".
El consumo de electricidad del sistema no es un dato que se obtenga directamente del inversor o del medidor inteligente, sino que se calcula en "solar.web". Para obtener el consumo diario, deberá solicitar los siguientes tres canales:

Comparem amb les lectures que agafem a mitjanit - ambdos concorden.

Aixi, si alguna lectura a mitja nit falla, podem recuperar el valor.

Si la data es massa vella i no hi ha dades, rebem

A dia 2025.05.13 puc llegir 2024.06.06, pero no em dona dates de 2024.06.05 - hi tenim poc menys de un any

No hi ha dades a la resposta del Fronius.
SmartMeter maybe ? No memory there !

Funciona be amb "canal1" pero les dades de volta son buides amb "canal2"

Solucio : email -> minie@/home/sebas/dades/python/fronius/0_from_ARCHIVE/2_get_archive_3_channels.py

Si demanem el resum, surt un sol valor, promig del dia :

Si volem el detall, surt una llista de temperatures, cada 5 minuts :

Les marques temporals son curioses, amb increments de 300 segons, es a dir 5 minuts, comptant des "Start" :

Al R0 salvem la temperatura de tot el dia a les 23:05

Dibuixem : aquest tutorial ho explica bé rrdtool as timeseries datastore

Un cop al dia guardem les dades al R0 (temp, volt, amp)

De tant en tant, llegim eixes dades (escollint el dia), filtrem els valor no desitjats, omplim un estructura adient pel "pyplot" i fem un dibuix que guardem a fitxer

Instalacio : doc, vfy

Check install :

Step by step : install/remove

We can use requests :

Or urllib.request

Millor sense el "with" : urllib.urlopen

using JSON

Details on opening URLs

20220725 :

• Akleber at github [*****] JSON tools, fetch examples

forum logicmachine

PHP code

Lets do it from MARS :

sudo apt install hhvm -> HHVM is an open-source virtual machine designed for executing programs written in Hack and PHP -> install HHVM {no cal}

Forum ben interessant ...

push log data

github : go to settings, enable API and get API Key ("9999") and SystemID ("88888")

Service URL : https://pvoutput.org/service/r2/addoutput.jsp

... pero no arriba l'altre cantó ...

Es recomana un "cron" :

• com es que NO puc llegir el voltatge o el corrent produits ara mateix (realtime), o la temperatura actual, i si que puc llegir-los des fitxer (archive requests) ?
  Current_DC_String_1 Current_DC_String_2 Voltage_DC_String_1 Voltage_DC_String_2 Temperature_Powerstage

• si hi ha un "reset" del Fronius (que n'hi ha), on queda guardada la causa ?

• si llegeixo un valor durant 1 dia (as "Temperature_Powerstage"), que son les marques temporals que van de 300 en 300 ?

  Son els segons des l'origen : "__OFFSET_IN_SECONDS__"

  nicolau@mars:~/sebas/python/fronius/0_from_ARCHIVE/out$ cat temperature.json { "Body": { "Data": { "inverter/1": { "Data": { "Temperature_Powerstage": { "Unit": "ºC", "Values": { "0": 0, "10200": 0, ... "52500": 57, "52800": 57, --- 14 h 40 min !!! "5400": 0, "5700": 0, "600": 0, "6000": 0,

Using the Fronius Push Service, system data can be sent directly from any Fronius SnapINverter or Fronius Datamanager (1.0 / 2.0) to any server to be used as you desire.

Various data formats are available (for example, XML and JSON).

Supported protocols: HTTP POST and FTP upload.

formats

42,0410,2152_Operating Instruction Fronius Push Service_DE_i_EN.pdf :
At present the only way to communicate with the Fronius push service is to make an HTTP request to a specific URL.

The current state can be requested be performing an HTTP get request:

PVOutput is a free online service for sharing and comparing photovoltaic solar panel output data.
It provides both manual and automatic data uploading facilities.

Homepage, API specificacion, list user 104774, sys id "canSebas"

Using a push service requires a PVOutput API key and System Id.
Refer to Service API on how to obtain the SystemId and API Key

[/] Replace your_sid with the System Id and your_key with the PVOutput API Key.

• Fronius push() service configuration {*****}

• sourceforge PV Control+

• {own} python requests

wiki : Modbus is a data communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs).

Fronius docu

Que es ? Modbus SunSpec is an open, Modbus-based communication protocol that conforms to the SunSpec Alliance standard.

Modbus TCP (Ethernet) is available for the following products: Fronius Datamanager Card 1.0, Card 2.0 or Box 2.0

TG by "R.C."

MBAP = MODBUS application protocol header

Supported function codes :

If an error occurs on the slave during the processing of a request, an error message is sent as the response (exception response). The most significant bit of the function code is set to 1 (corresponds to adding 0x80 to the function code) and an exception code is added, which indicates the reason for the error.

Modbus "Read Holding Registers", function code 03, reads between 1 and 125 holding registers from the PLC.

The request PDU consists of 5 bytes:

The normal response varies in length from 4 bytes up to 252 bytes depending on the number of holding registers requested:

Note: The total number of bytes returned is 2 + ( 2 * RegisterCount ), where RegisterCount is the number of holding registers requested.

fernhillsoftware

Mapes at "/home/nicolau/sebas/energia_solar/fronius/modbus/SE_EI_Modbus_Sunspec_Maps_State_Codes_Events"

http://www.fronius.com/QR-link/0006 -> SE_EI_Modbus_Sunspec_Maps_State_Codes_Events_EN.zip

• Integer Meter Model (201, 202, 203) - Meter_Register_Map_Int&SF_v1.0_201a203.xlsx
• Floating Point Meter Model (211, 212, 213) - Meter_Register_Map_Float_v1.0_211a213.xlsx
• Fronius Datamanager Register Map: Integer Inverter Model (101, 102, 103) - mapa_registros_Fronius_101a103.xlsx

pyModbusTCP project, documentation, PDF, github (install)

See client docs :

Using this code

... we get :

Pg 99 de "42,0410,2049_operating Instructions fronius datamanager - modbus TCP and RTU.pdf" The data of an energy meter connected with the Fronius Datamanager via Modbus RTU can be read by the relevant SunSpec models via Modbus TCP.

Fem servir "mapa_registros_Fronius_101a103.xlsx", doncs tenim un model "101", single phase

• Fronius webinar Third-party monitoring and control via Sunspec Modbus RS485 TCP/IP interface, minut 28 +
• stackoverflow tagged
• video domotica.solar
• get mapas_registros.xlsx
• node red {***}
• pysunspec - provides objects and applications that support interaction with SunSpec compliant devices and documents.
  documentation

We need a TSDB = time series database

• round robin database, rrdb - wiki RRDtool

• influxdata : how to visualize - There are many types of dashboards to choose from, such as those that come with InfluxDB, other open source projects like Grafana, ...

• Graphite supports reading data from rrd files

Gràcies, Pere !

Dashboards are a great way to visualize and present time series data

7 powerful Time-Series Database for monitoring solution

plotly libraries

• silo.tips {PDF}

hietala, cada 300 segons

En Albert te un projecte ben xulu : PiHeat

Despres de la instalacio i les inicialitzacions, funciona amb el crontab :

Els punts claus son :

3 dubtes : {solucio : paket Debian}

• quan es posa el crontab dins el sistema, quan s'engega "piheat -> cron -> piheat"
• des on es crida "piheat-cli.initialize", per a "crear" el fitxer i demes : piheat.postinst
• quan es posa al sistema el servei "piheat.service" : piheat.postinst

Diferencies :

• jo no tindré un servidor web local, sino que faré un FTP a byet.host, free hosting

Un altre projecte similar : Smart Meter amb RRDtool al Raspberry

Un "create" + "update" + "graph" sample

Volem q el R4 llegeixi JSON del Fronius i faci 4 grafiques. Projecte al github {gitlab}

Be, essiguem una mica mes ambiciosos - volem un programa que :

• in : periode, as (from 2022-02-14 to 2022-03-11)
• out : kWh que he (comprat/vengut) + diners que he de (pagar/cobrar)

Fem codi al R4 :

O tambe :

Documentacio create command

Si fem una mostra cada 5 segons i volem guardar 1 any, quantes entrades ("rows") ens calen ?
1 mostra / 5 seg ; 12 mostres / 1 minut ; 720 mostres / 1 hora ; 17.280 mostres / 1 dia ; 6.307.200 mostres / 365 dies o 1 any.

Fem :

Mind the "RRA steps" :
steps defines how many of these primary data points are used to build a consolidated data point which then goes into the archive

Si fem servir la eina "info", veiem

The "heartbeat" defines the maximum acceptable interval between samples/updates. If the interval between samples is less than "heartbeat", then an average rate is calculated and applied for that interval. If the interval between samples is longer than "heartbeat", then that entire interval is considered "unknown".

oss.oetiker

The step size is the smallest time interval in the RRD file. By default, this is 300 sec (5 min) though you can specify it smaller or larger if necessary at creation time. Generally, you would set this to be the expected amount of time between data samples; so if your samples come approximately every 5 min, you set this to 5 min.

The heartbeat is the maximum amount of time between samples before they are deemed unknown. This is an indicator of the irregularity of samples. In general, this would be twice the expected sample interval; so if your samples come every 5 min, set this to 600 s (10 min). If there is a gap larger than this, the sample range is marked 'unknown'.

The XFF is the proportion of DS data points making up an RRA consolidated data point which can be unknown before the consolidated data point becomes unknown. Generally, this is set to 0.5, but can be higher if you want (e.g. 0.9).

stackoverflow

When creating an RRD database we'll need to specify a couple things, namely one or more Data Sources and one or more Round Robin Archives.

• the data source (DS) defines what type of data is accepted and some boundaries on what constitutes good data.

  Format : DS:ds-name:{GAUGE|COUNTER|DERIVE|DCOUNTER|DDERIVE|ABSOLUTE}:heartbeat:min:max

  The min and max specify a range for "good" values; if a value is outside of this range it is said to be unknown.

  Min - the minimum acceptable value. Values less than this number are considered unknown. This is optional. Specify "U" (unknown) to not set a min

  Max - the maximum acceptable value. Values exceeding this number are considered unknown. This is optional. Specify "U" (unknown) to not set a max

• the round robin archives (RRA) can almost be thought of as views, it defines the different ways we can store and retrieve data.

• good quick intro to rrdtool

cuddletech

What is CDEF ?
Consolidation Functions take values from DEFs and perform calculations on them
As to change line colour by value

Documentacio update command

El codi python per escriure dades es :

updatev :

This alternate version of update takes the same arguments and performs the same function. The v stands for verbose, which describes the output returned. updatev returns a list of any and all consolidated data points (CDPs) written to disk as a result of the invocation of update.

Compte que si fem :

Ens podem trobar amb :

Documentacio resize command

RRD of 10080 rows was to contain 7 days of data at 1 sample per minute (60 samples per hour X 24 hours X 7 days)

To have 1 year of data at 1 sample every 5 secs, our size must be ... 12 samples per minute X 60 minutes per hour X 24 hour per day X 365 days per year =

So I did :

... and got a 6317280 rows file (6307200 + 10080)

The syntax is rrdtool resize filename rra-num GROW|SHRINK rows
... where rows is the number of rows you want to add or remove.

The new .rrd file, with the modified RRAs, is written to the file resize.rrd in the current directory. The original .rrd file is not modified.

Documentacio graph command

This command creates an image from the data in an RRD file.

rrdtool graph needs data to work with, so you must use one or more data definition statements to collect this data :

oss.oetiker

Values of different variables can be presented in 5 different shapes in a graph - AREA, LINE1, LINE2, LINE3, and STACK.

AREA is represented by a solid colored area with values as the boundary of this area.

LINE1/2/3 (increasing width) are just plain lines representing the values.

STACK parameter for AREA and LINEx indicates to "stack" this element on top of previous AREA or LINE1/2/3.

Another important thing to note is that variables are plotted in the order they are defined in the graph command. Therefore care must be taken to define STACK only after defining AREA/LINE. It is also possible to put formatted comments within the graph.

oss.oetiker

sis solucoes graph, RPN for DEF, DEF, CDEF, VDEF, rrdgraph overview

lists.oetiker.ch

Some URLs :

• Creating pretty graphs with RRDTOOL
• Getting Started with RRDtool
• Alex van den Bogaerdt - transparency !

Documentacio xport command

The xport function's main purpose is to write an XML or JSON formatted representation of the data stored in one or several RRDs.

Funciona de maravella, quan poso eixos parametres de temps de inici i final :

Malauradament, quan poso jo els "epoch" de començament i final, canvia el step i perdem dades :

Aixo passa quan hi ha "NaV" :

Aixi, descartem el fer servir "xport"

export command , pythonhosted

... malauradament, no funciona, ... no treu res ... issue 1179 {20220517}

Documentacio fetch command

The fetch function will analyze the RRD and try to retrieve the data in the resolution requested. The data fetched is printed to stdout.

filename = the name of the RRD you want to fetch the data from.

CF = the consolidation function that is applied to the data you want to fetch (AVERAGE,MIN,MAX,LAST)

El codi es ben planer :

Funciona perfectament :

No acaba de rutllar :

No treu res, i no en se pas la rao.

Documentacio dump command

The dump function writes the contents of an RRD in human readable XML format to a file or to stdout. This format can be read by rrdrestore.

rrdtool uses "unix" time : epoch - every day is treated as if it contains exactly 86400 seconds

Here is a online epochconverter.com converter

Compte : 12am refers to midnight at the start of the specified day (00:00) and 12pm to midnight at the end of that day (24:00)

Assuming you're using GNU coreutils (as both --date and the %s format string are GNU extensions), use

stackOverflow

Convert seconds since the epoch (1970-01-01 UTC) to a date :

Sometimes rrdtool sets "NaN" values in the DB, as when a data is missing. Any numerical operation will fail with this operand, so we have to replace it.

Comencem amb :

Objectiu : fer grafiques maques.

Cron job cannot be used to schedule a job in seconds interval, so you cannot schedule a cron job to run every 5 seconds.

The alternative is to write a shell script that uses ‘sleep 5’ command in it :

We want to run this shell script forever since R4 start ...

.. i que acaba cridant a "/home/pi/python/pkw/bin/pkw_cli.py read_and_store" per escriure a la RRDB.

Acabarà aqui : gitlab.com/sebastia-net/pkw

Llegeixo

Afegeixo id_ed25519.pub a https://gitlab.com/-/profile/keys/9621914

Tambe llegeixo

Verify :

El fitxer es fa força gran :

1. guardem el vell
   pi@R4:~/python/pkw/dades/old_rrds $ mv ../pkw.rrd ./pkw_2025.rrd
2. en fem un de nou, buid
   pi@R4:~/python/pkw/bin $ ./pkw_cli.py initialize

Com fem per re-generar-lo ?

Les dades es graven aixi :

Que en detall ve a ser :

Objectius :

• verificar (i corregir si cal) la consistencis dels fitxers de dades - han de tenir 1440 mesures cada dia (1 mesura cada minut, 60 per hora)
• comparar amb Fronius APP
• fer alguna grafica
• calcular la factura, vist que sabem el preu del KW per cada hora

Entrada : /home/sebas/dades/python/pkw/dades/potencies/csv/

Podem calcular la energia produida i la consumida mitjançant els nostres "CSV"

Entrada : potencies llegides cada minut (produccio, consum, diferencia)

Sortida : energia produida en un dia (Wh), consum en un dia (Wh)

El cert es que l'energia auto-consumida que calculo no em coincideix amb la mostrada a la APP del Android, tot i tenir les 1440 linies (24 hores x 60 mostres per hora) al CSV.

També, a partir de les dades q agafem cada minut, - /home/sebas/dades/python/pkw/dades/potencies/csv/pot_CSV_2023_12_27.csv from R4@/home/pi/python/pkw/dades/potencies/csv - podem calcular la energia produida i consumida en un dia :

... mentre que Fronius diu ...

Els factors que intervenen son :

• sigui "P" la produccio de les plaques solars (sempre positiva)
• sigui "C" el consum de la casa (sempre negativa)
• sigui "D" la energia excedent que surt cap a la xarxa (positiva) o deficit que entra de la xarxa (negativa)
• sigui "A" el autoconsum,
• i "EV" la energia que venem i "EC" la energia que comprem

Els calculs interessants son :

• si "C<P", consumim menys que produim, es a dir, tenim excedent i estem venent energia a la xarxa (diff<0)

  A = C

  EV = P-C

• si "C>P", consumim mes del que produim, es a dir, estem comprant energia de la xarxa (diff>0)

  A = P

  EC = C-P

Ara ja tenim els valors a facturar :

• EV es lo que hem de cobrar, energia venuda
• EC es lo que hem de pagar, energia comprada

SAG - calculo una factura {up}

El R4 va escrivint fitxers de texte amb dates de energia i potencia.

Al MARS podem fer alguna grafica en background, visualitzant valors diaris, setmanals o mensuals.

D'entrada, fem servir matplotlib

Gestor d'excedents: si no es vol liar molt (molt) amb programació i Raspberrys i tal, hi ha alguns gestors ja fets. Un de obert és el freeds.es.

Fa servir esp32 (SoC, System on Chip, incluye wifi y bluetooth) i esp01 (monta la versión más sencilla del ESP8266, con un procesador de 32bits a 80 Mhz, con 1MB de memoria, y dispone de 2 pines GPIO, SPI, I2C y UART)

Software : https://github.com/pablozg/freeds/releases

Te un canal a Telegram

To display, do :

1. log into solarweb homepage using email

2. click "Analisis" (2nd from left)

3. click "Historial"

4. under "equipos" select "Primo 5.0-1"

5. under "canales" select "Corriente CC MPP1" and "Corriente CC MPP2", or "Potencia MPP1" and "Potencia MPP2", or "Tensión CC MPP1" and "Tensión CC MPP2" ...

6. click "OK" and you'll get a nice graph

Seria interessant fer servir wireShark per veure les comandes que envia solarweb per obtenir dades (tensio o corrent) de MPP1 o MPP2 ---> impossible snifejar de PC-A eltrafic entre PC-B i PC-C en una wifi

Use it to open a wifi access point or display solar voltage and current

On local console, do :

1. select CONFIG
2. select "Punto acceso a wifi"
3. select "Activar ?" - mind it stops after 10 min
4. on your device (PC or Android), disconnect "Mobile Data"
5. now we must connect the PC (or Android) to wifi "Fronius_240.1234567" - the password is "12345678"
6. open a browser on default IP address of the Datamanager Card (192.168.250.181)
7. on right side, select "Ajustes"
8. select "Modbus" and configure :
   • TCP connection
   • port 502
   • string control address offset = 101
   • Sunspec Model Type INT + SF
9. also, activate "logging en horas nocturnas" to know your energy use by night
   Note: make sure to turn on the Night Mode in the Display Settings on the Fronius inverter to keep it from going offline at night.

datamanager troubleshooting guide

El horario valle abarca desde las 00h a 08 h entre semana, y durante todo el día los fines de semana y festivos.
Horario llano : de lunes a viernes, por la mañana de 08h a 10h, por la tarde de 14h a 18h y por la noche de 22h a 00h.
Horario punta : de lunes a viernes no festivos, de 10 a 14h y de 18 a 22h.

Els aparells electrics que tenim son :

El consum energetic de 2021 va ser :

factures ENDESA

factura Agost 2022

energia produida cada dia

• 8 septiembre: definir la correcta posición del Fronius Smart Meter
• 6 octubre: la comunicación entre Fronius GEN24 Plus y BYD Battery-Box Premium HVS/M
• 10 noviembre, 16 h: activar/desactivar límite de alimentación a red con inversores Fronius (“inyección 0”) - unirse, ver video, pdf
• 30 noviembre, 16 h: conexión de 2 inversores Fronius en paralelo - unirse, ver video, pdf

eventos 20220913

¿Tiene preguntas o comentarios sobre el seminario web? Póngase en contacto con webinar2@fronius.com

Se pueden ver en diferido ?

• Fronius solar.web : solarweb.com

  Premium upgrade : 9,08 EUR - 3 meses ; 24,20 EUR - 12 meses ; 65,34 EUR - 36 meses

• 42,0410,2149 operating instructions + Status diagnostics and troubleshooting

• JSON viewer and validator

• PVOutput.org is a free service for sharing, comparing and monitoring live solar photovoltaic (PV) and energy consumption data
  upload solar data from a GoodWe power inverter to the PVOutput.org website : markruys, zonoskar

• github/gitlab (search for "fronius") :
  • ioBroker.fronius
    help
  • fronius-json-tools [*****]
  • Growatt proxy - foro

• email support@fronius.com, pv-support-spain@fronius.com +34 91 649 60 30