1,954
edits
Extra Sensors: Difference between revisions
m
→Inner working
m (→Introduction) |
m (→Inner working) |
||
| (5 intermediate revisions by the same user not shown) | |||
|
''Extra Sensors'' is a feature already present in Cumulus 1. Ignored for long time by CumulusUtils, with the rise of the [https://www.ecowitt.com/shop/homePage Ecowitt ecology] and the support of CumulusMX for the GW1000 (and higher) devices, it has been decided to make ''Extra Sensors'' a standard module of CumulusUtils.
For the obvious reason of the absence of a log, the lightning sensor will be ignored by CumulusUtils as are additional sensors which can not be logged. You are advised to use the [[Custom Logs|CustomLogs]] to chart Lightning.
Please read the paragraph operation carefully and report any difficulty in operating the module both in this Wiki, from within the website or otherwise. I think all cases are covered but you never know.
For External Extra Sensors i.e. sensors the user has available outside the CMX system such as e.g. a Geiger Counter see: [[External Extra Sensors]].
In CMX version 3.22.0 - b3211 the Custom Logs were introduced, providing the possibility for the user to create their own logfiles for any value - also strings - which CMX produces in a [[Webtags|webtag]]. This called for a procedure in CumulusUtils to handle those logs. In version 6.21.0 this was realised. the [[Custom Logs]] procedure us based on the External Sensors module and has its own wiki page.
=== Dependency ===
#CumulusUtils must be run once with the command ''ExtraSensors'' (fastest) or ''Website'' to create the required parameters in the section ''[ExtraSensors]'' in the inifile.
#The module requires that the user has ''Extra Sensor'' logging enabled in CumulusMX(''CMX menu=>Station Settings=>Common Options=>Log Extra sensors'' must be enabled) AND the user must set the parameter ''ExtraSensors'' in the cumulusutils.ini file to ''true''. This last parameter makes it possible to have ''Extra Sensors'' operational in CMX but not display them on the web (if you are generating the website). Once both parameters are set to true the module is active.
#After the first run the following inifile parameters exist (see below): ''ExtraTemp, ExtraHum, ExtraDP, SoilTemp, SoilMoisture, AirQuality, UserTemp, LeafTemp, LeafWetness, LaserDist, LaserDepth''. Filling these with e.g. '''1,2,3''' activates those sensors and a subsequent run will show these under the menu choice ''Extra''.
#For the CO2 sensor the parameter ''CO2='', a value 0 (or empty ) or 1 (de-)activates that sensor which subsequently is handled as an extra sensor and will be shown under the menu choice ''Extra''.
#For the lightning sensor the parameter ''LightningSensor=true/false'' (de-)activates that sensor which subsequently is displayed as a normal Extra Sensor in the list. The Lichting sensor is currently not charted as it is not logged in the ExtraSensors log.
#Finally, to make it work and to bring system in the ''Extra Sensors'', '''it is required''' for the user to use ''strings.ini'' (copy it from samplestrings.ini in the distribution of CumulusMX) in the CumulusMX directory and give the sensors you want to be handled by CumulusUtils '''a short meaningfull name'''.
LeafTemp= => fill with comma separated digits from 1 - 2
LeafWetness= => fill with comma separated digits from 1 - 2
LaserDist= => fill with comma separated digits from 1 - 4
LaserDepth= => fill with comma separated digits from 1 - 4
CO2= => fill with 1
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 last line of the userdefined charts is:
; ExtraSensorCharts
After this line no changes may be made unless the parameter ''UserModificationExtraSensorCharts=true''. This line marks the beginning of the ''Extra Sensor Chart definitions''.
| |||