* thread-safety and dynamic memory for MessageOutput * use dynamic memory to allow handling of arbitrary message lenghts. * keep a message buffer for every task so no task ever mangles the message of another task. * every complete line is written to the serial console and moved to a line buffer for sending them through the websocket. * the websocket is always fed complete lines. * make sure to feed only as many lines as possible to the websocket handler, so that no lines are dropped. * lock all MessageOutput state against concurrent access. * MessageOutput: respect HardwareSerial buffer size the MessageOutput class buffers whole lines of output printed by any task in order to avoid mangling of text. that means we hand over full lines to the HardwareSerial instance, which might be too much in one call to write(buffer, size). we now check the return value of write(buffer, size) and call the function again with the part of the message that could not yet be written by HardwareSerial. |
||
|---|---|---|
| .. | ||
| Battery.h | ||
| BatteryStats.h | ||
| Configuration.h | ||
| Datastore.h | ||
| defaults.h | ||
| Display_Graphic.h | ||
| helper.h | ||
| HttpPowerMeter.h | ||
| Huawei_can.h | ||
| InverterSettings.h | ||
| JkBmsController.h | ||
| JkBmsDataPoints.h | ||
| JkBmsSerialMessage.h | ||
| Led_Single.h | ||
| MessageOutput.h | ||
| MqttHandleDtu.h | ||
| MqttHandleHass.h | ||
| MqttHandleHuawei.h | ||
| MqttHandleInverter.h | ||
| MqttHandleInverterTotal.h | ||
| MqttHandlePowerLimiter.h | ||
| MqttHandlePylontechHass.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_security.h | ||
| WebApi_sysstatus.h | ||
| WebApi_vedirect.h | ||
| WebApi_webapp.h | ||
| WebApi_ws_battery.h | ||
| WebApi_ws_console.h | ||
| WebApi_ws_Huawei.h | ||
| WebApi_ws_live.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