There have been occasions when data gaps occurred in the CSV files collected daily.
The problems are unique to the power file. The azimuth and elevation are printed, but nothing else.
Further, that data is collected outside the schedule. Somhow, the NOAA2.py script is being run outside of schedule, and printed to the CSV files. The EpD3Dy.php script is run by a service/timer. The NOAA2.py script ius called from within the php script.
The problem may disappear if the python script is run in a different service/timer pair.
I'm examining an epevermodbus python script to read and record settings separate from the php script. This will allow me to examine the data for problematic results, such as negative values or other data anomolies.
I reset the timer to a time after the sun has risen. Unfortunately resetting the timer startup very season is not practical. I may be able to set the startup time from within the service or the script.
This problem is relatively recent. Perhaps this is a result of the differences between the Epever Tracer and Triron charge controllers.