1,771
edits
Extra Sensors: Difference between revisions
From Cumulus Wiki
Jump to navigationJump to search
m
no edit summary
m (→Introduction) |
mNo edit summary |
||
|
== Inner working ==
When run it is first checked if anything has to be done through the parameters ''ExtraSensors'' (in cumulusutils.ini) and ''LogExtraSensors'' (in Cumulus.ini).
When both parameters are true then the names of the extra sensors in ''strings.ini'' are checked if they deviate from the default. If they deviate it means the user has changed the name which is taken as a proof of presence of an ''Extra Sensor''. A sensor present means the realtime data and a corresponding chart will be created for presentation. The only sensor where the name in ''strings.ini'' is not determinant for its presence is the Ecowitt CO2 sensor. Those names may be changed by the user, but only a value in the logfile for the CO2 value is taken as proof of presence.
A structure is created for each sensor present. Each AirQuality sensor is automatically coupled with an AirQualityAvg sensor (which is not a physical sensor by itself) for presentation. For each CO2 sensor all seven successive sensors (see strings.ini) are also created.
With the list of sensors the extrasensorsrealtime.txt is generated, followed by extrasensors.txt (the code) and the charts are added to CutilsCharts.def. The actual charts code is generated by the compiler. The compiler runs implicitly when generating the website. Otherwise it has to be run separately when ExtraSensors is run on its own and regeneration of the charts code would be required (e.g. when adding a sensor). The command then would be:
utils/cumulusutils.exe ExtraSensors CompileOnly
Data generation is separate from the code generation and should run on the FTP frequency like all other data generators of CumulusUtils and CumulusMX.
Run:
utils/cumulusutils.exe UserAskedData
in the scheduler. The compiler and/or the AirLink module require that command as well.
| |||
