* VE.Direct: remove polling interval the polling interval was meant to limit the amount of MQTT updates. however, that is already controlled by the global MQTT publish interval. the removed interval was instead used to limit polling of the VE.Direct UART for incoming data. the Victron device sends data unsolicited. the VeDirectFrameHandler does not implement any polling mechanism. no data is ever sent to the Victron device. what the removed polling interval did was cause a buffer overrun of the HardwareSerial class, since the incoming data was not processed in time. so every five seconds, we read a whole valid VE.Direct frame, plus some old data, which was not a whole frame, leading to VE.Direct error messages to pop up. with the polling interval removed, no framing errors are reported, and instead we gain new data from the charge controller approximately ever two seconds -- for free. * VE.Direct: change texts to correct VE.Direct capital letters * VE.Direct: improve "UpdatesOnly" switch labels especially since the publish interval setting is gone, the label makes it hard to comprehend what the switch does. update the texts to better explain what the switch is used for. use the same text on the VE.Direct info view. * VE.Direct: use StatusBadge on info view there were custom badges to indicate the VE.Direct settings. replace those by the common StatusBadge to make then look the same as the other badged on the info views. |
||
|---|---|---|
| .. | ||
| Battery.h | ||
| Configuration.h | ||
| Datastore.h | ||
| defaults.h | ||
| Display_Graphic.h | ||
| helper.h | ||
| HttpPowerMeter.h | ||
| Huawei_can.h | ||
| InverterSettings.h | ||
| Led_Single.h | ||
| MessageOutput.h | ||
| MqttHandleDtu.h | ||
| MqttHandleHass.h | ||
| MqttHandleHuawei.h | ||
| MqttHandleInverter.h | ||
| MqttHandleInverterTotal.h | ||
| MqttHandlePowerLimiter.h | ||
| MqttHandleVedirect.h | ||
| MqttHandleVedirectHass.h | ||
| MqttSettings.h | ||
| NetworkSettings.h | ||
| NtpSettings.h | ||
| PinMapping.h | ||
| PowerLimiter.h | ||
| PowerMeter.h | ||
| PylontechCanReceiver.h | ||
| README | ||
| SunPosition.h | ||
| Utils.h | ||
| WebApi_battery.h | ||
| WebApi_config.h | ||
| WebApi_device.h | ||
| WebApi_devinfo.h | ||
| WebApi_dtu.h | ||
| WebApi_errors.h | ||
| WebApi_eventlog.h | ||
| WebApi_firmware.h | ||
| WebApi_Huawei.h | ||
| WebApi_inverter.h | ||
| WebApi_limit.h | ||
| WebApi_maintenance.h | ||
| WebApi_mqtt.h | ||
| WebApi_network.h | ||
| WebApi_ntp.h | ||
| WebApi_power.h | ||
| WebApi_powerlimiter.h | ||
| WebApi_powermeter.h | ||
| WebApi_prometheus.h | ||
| WebApi_Pylontech.h | ||
| WebApi_security.h | ||
| WebApi_sysstatus.h | ||
| WebApi_vedirect.h | ||
| WebApi_webapp.h | ||
| WebApi_ws_console.h | ||
| WebApi_ws_Huawei.h | ||
| WebApi_ws_live.h | ||
| WebApi_ws_Pylontech.h | ||
| WebApi_ws_vedirect_live.h | ||
| WebApi.h | ||
This directory is intended for project header files.
A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.
```src/main.c
#include "header.h"
int main (void)
{
...
}
```
Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.
In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.
Read more about using header files in official GCC documentation:
* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html