Extra Sensors: Difference between revisions

120 bytes added ,  05:22, 13 September 2021
m
Line 15: Line 15:
== Operation ==
== Operation ==
#CumulusUtils must be run once with the  command ''ExtraSensors'' or ''Website'' to create the required parameters in the section ''[ExtraSensors]'' in the inifile.
#CumulusUtils must be run once with the  command ''ExtraSensors'' 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).
#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.  
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.  
#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 or remove the default value to make an empty string'''. Default value or empty define a sensor as NOT PRESENT. Existing Sensors which keep their default names will be displayed in the CMX interface but will not be used by CumulusUtils.
#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. Existing Sensors which keep their default names will be displayed in the CMX interface but will not be used by CumulusUtils.


For the [[Website_Generator|Website Generator]] this means everything is automatically available in the menu of the website. <br>
For the [[Website_Generator|Website Generator]] this means everything is automatically available in the menu of the website.
Using as a module requires some additional editing to make use of the table with the current values (Note [[Modules#Javascript_libraries|the libraries]] as well). The charts are always available (see outputs). It is disadvised to use this outside the context of the [[Website_Generator|Website Generator]] but skilled users can use the module as the basis for their own website (as has been done with AirLink and other modules).
 
Using as a module requires some additional editing to make use of the table with the current values (Note [[Modules#Javascript_libraries|the libraries]] as well). The charts are always available (see outputs). It is advised not to use this module outside the context of the [[Website_Generator|Website Generator]] but skilled users can use the module as the basis for their own website (as has been done with AirLink and other modules).


To receive the data for the ExtraSensors you have to run ''CumulusUtils [[UserAskedData]]''. It would be logical to do this on the normal FTP frequency on which all other chart data are generated by CMX and by the requirements of the [[ChartsCompiler]] and the [[AirLink]] module.
To receive the data for the ExtraSensors you have to run ''CumulusUtils [[UserAskedData]]''. It would be logical to do this on the normal FTP frequency on which all other chart data are generated by CMX and by the requirements of the [[ChartsCompiler]] and the [[AirLink]] module.