This page contains detailed instructions on building a module and flashing it with the latest firmware. Following these instructions will allow you to communicate with compatible inverters.
This page contains detailed instructions on building a module and flashing it with the latest firmware. Following these instructions will allow you to communicate with compatible inverters.
@ -195,8 +195,9 @@ The `<VALUE>` should be set to `1` = `ON` and `0` = `OFF`
}
}
```
```
**beginning from verson `0.8.39` the wattage and percentage has one decimal place!**
### Power Limit relative persistent [%]
### Power Limit (active power control) relative persistent [%]
```json
```json
{
{
@ -205,10 +206,10 @@ The `<VALUE>` should be set to `1` = `ON` and `0` = `OFF`
"val": <VALUE>
"val": <VALUE>
}
}
```
```
The `VALUE` represents a percent number in a range of `[2 .. 100]`
The `VALUE` represents a percent number in a range of `[2.0 .. 100.0]`
### Power Limit absolute persistent [Watts]
### Power Limit (active power control) absolute persistent [Watts]
```json
```json
{
{
@ -217,10 +218,10 @@ The `VALUE` represents a percent number in a range of `[2 .. 100]`
"val": <VALUE>
"val": <VALUE>
}
}
```
```
The `VALUE` represents watts in a range of `[0 .. 65535]`
The `VALUE` represents watts in a range of `[1.0 .. 6553.5]`
### Power Limit relative non persistent [%]
### Power Limit (active power control) relative non persistent [%]
```json
```json
{
{
@ -229,10 +230,10 @@ The `VALUE` represents watts in a range of `[0 .. 65535]`
"val": <VALUE>
"val": <VALUE>
}
}
```
```
The `VALUE` represents a percent number in a range of `[2 .. 100]`
The `VALUE` represents a percent number in a range of `[2.0 .. 100.0]`
### Power Limit absolute non persistent [Watts]
### Power Limit (active power control) absolute non persistent [Watts]
```json
```json
{
{
@ -241,7 +242,7 @@ The `VALUE` represents a percent number in a range of `[2 .. 100]`
"val": <VALUE>
"val": <VALUE>
}
}
```
```
The `VALUE` represents watts in a range of `[0 .. 65535]`
The `VALUE` represents watts in a range of `[1.0 .. 6553.5]`
@ -328,7 +329,7 @@ Send Power Limit:
- If the DC voltage is missing for a few seconds, the microcontroller in the inverter goes off and forgets everything that was temporary/non-persistent in the RAM: YieldDay, error memory, non-persistent limit.
- If the DC voltage is missing for a few seconds, the microcontroller in the inverter goes off and forgets everything that was temporary/non-persistent in the RAM: YieldDay, error memory, non-persistent limit.
### Update your AHOY-DTU Firmware
### Update your AHOY-DTU Firmware
To update your AHOY-DTU, you have to download the latest firmware package.
To update your AHOY-DTU, you have to download the latest firmware package.
Here are the [latest stable releases](https://github.com/lumapu/ahoy/releases/) and [latest development builds](https://nightly.link/lumapu/ahoy/workflows/compile_development/development03/ahoydtu_dev.zip) available for download.
Here are the [latest stable releases](https://github.com/lumapu/ahoy/releases/) and [latest development builds](https://fw.ahoydtu.de/dev) available for download.
As soon as you have downloaded the firmware package, unzip it. On the WebUI, navigate to Update and press on select firmware file.
As soon as you have downloaded the firmware package, unzip it. On the WebUI, navigate to Update and press on select firmware file.
From the unzipped files, select the right .bin file for your hardware and needs.
From the unzipped files, select the right .bin file for your hardware and needs.
- If you use an ESP8266, select the file ending with esp8266.bin
- If you use an ESP8266, select the file ending with esp8266.bin
You have build your own hardware (or purchased one). The firmware is already loaded on the ESP and the WebUI is accessible from your browser.
## Ahoy configuration
## Start
So far we have built our own DTU, written a program on it and put it into operation.
But how do I get my data from the inverter?
But how do I get my data from the inverter?
To do this, we need to configure the DTU.
The following steps are required:
The following steps are required:
1. Set the pinning to communicate with the radio module.
1. Set the pinning to communicate with the radio module.
2. Check if Ahoy has a current time
2. Check if Ahoy has a current time
3. Set inverter data
3. Configure the inverter data (e.g. serialnumber)
### 1.) Set the pinning
### 1.) Set the pinning
Once you are in the web interface, you will find the "System Config" sub-item in the Setup area (left).
Once you are in the web interface, you will find the "System Config" sub-item in the Setup area.
This is where you tell the ESP how you connected the radio module.
This is where you tell the ESP how you connected the radio module.
Note the schematics you saw earlier. - If you haven't noticed them yet, here's another table of connections.
Note the schematics you saw earlier. - If you haven't noticed them yet, here's another table of connections.
@ -38,7 +37,7 @@ Note the schematics you saw earlier. - If you haven't noticed them yet, here's a
| FCSB| GPIO21
| FCSB| GPIO21
| GPIO3| GPIO8
| GPIO3| GPIO8
### 2.) Set current time (normal skip this step)
### 2.) Set current time (standard: skip this step)
Ahoy needs a current date and time to talk to the inverter.
Ahoy needs a current date and time to talk to the inverter.
It works without, but it is recommended to include a time. This allows you to analyze information from the inverter in more detail.
It works without, but it is recommended to include a time. This allows you to analyze information from the inverter in more detail.
Normally, a date/time should be automatically retrieved from the NTP server. However, it may happen that the firewall of some routers does not allow this.
Normally, a date/time should be automatically retrieved from the NTP server. However, it may happen that the firewall of some routers does not allow this.
@ -51,20 +50,22 @@ Now it's time to place the inverter. This is necessary because it is not the inv
Each inverter has its own S.Nr. This also serves as an identity for communication between the DTU and the inverter.
Each inverter has its own S.Nr. This also serves as an identity for communication between the DTU and the inverter.
The S.Nr is a 12-digit number. You can look it up [here (german)](https://github.com/lumapu/ahoy/wiki/Hardware#wie-ist-die-serien-nummer-der-inverter-aufgebaut) for more information.
The S.Nr is a 12-digit number. Check [here (german)](https://github.com/lumapu/ahoy/wiki/Hardware#wie-ist-die-serien-nummer-der-inverter-aufgebaut) for more information.
#### set pv-modules (not necessary)
#### set pv-modules (not necessary)
Click on "Add Inverter" and enter the S.No. and a name. Please keep the name short!
Click on "Add Inverter" and enter the S.No. and a name. Please keep the name short!
In the upper tab "Inputs" you can enter the data of the solar modules. These are only used directly in Ahoy for calculation and have no influence on the inverter.
In the upper tab "Inputs" you can enter the data of the solar modules. These are only used directly in Ahoy for calculation and have no influence on the inverter.
#### set radio parameter (not necessary, only for EU)
#### set radio parameter (not necessary, only for EU)
In the next tab "Radio" you can adjust the power and other parameters if necessary. However, these should be left as default (EU only).
In the next tab "Radio" you can adjust the power and other parameters if necessary. However, these should be left as default (EU only).
#### advanced options (not necessary)
#### advanced options (not necessary to be changed)
In the "Advanced" section, you can customize more settings.
In the "Advanced" section, you can customize more settings.
uint32_tnxtTrig=mSunset+mConfig->sun.offsetSec+60;// set next trigger to communication stop, +60 for safety that it is certain past communication stop
uint32_tnxtTrig=mSunset+mConfig->sun.offsetSecEvening+60;// set next trigger to communication stop, +60 for safety that it is certain past communication stop
iv->commEnabled=!iv->config->disNightCom;// if sun.disNightCom is false, communication is always on
iv->commEnabled=!iv->config->disNightCom;// if sun.disNightCom is false, communication is always on
if(!iv->commEnabled){// inverter communication only during the day
if(!iv->commEnabled){// inverter communication only during the day
if(mTimestamp<(mSunrise-mConfig->sun.offsetSec)){// current time is before communication start, set next trigger to communication start
if(mTimestamp<(mSunrise-mConfig->sun.offsetSecMorning)){// current time is before communication start, set next trigger to communication start
nxtTrig=mSunrise-mConfig->sun.offsetSec;
nxtTrig=mSunrise-mConfig->sun.offsetSecMorning;
}else{
}else{
if(mTimestamp>=(mSunset+mConfig->sun.offsetSec)){// current time is past communication stop, nothing to do. Next update will be done at midnight by tickCalcSunrise
if(mTimestamp>=(mSunset+mConfig->sun.offsetSecEvening)){// current time is past communication stop, nothing to do. Next update will be done at midnight by tickCalcSunrise
nxtTrig=0;
nxtTrig=0;
}else{// current time lies within communication start/stop time, set next trigger to communication stop
}else{// current time lies within communication start/stop time, set next trigger to communication stop
DanielR92
2 years ago
