Extra Sensors - Revision history

HansR: /* Inner working */

2025-02-06T16:29:12Z

Inner working

← Older revision		Revision as of 16:29, 6 February 2025
Line 116:		Line 116:

	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:		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:
	; DO NOT CHANGE ANYTHING BELOW THIS INDICATOR LINE
	; ExtraSensorCharts		; 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''.		After this line no changes may be made unless the parameter ''UserModificationExtraSensorCharts=true''. This line marks the beginning of the ''Extra Sensor Chart definitions''.

HansR: /* Inifile Parameters */

2025-02-06T16:28:30Z

Inifile Parameters

← Older revision		Revision as of 16:28, 6 February 2025
Line 99:		Line 99:
	LeafTemp= => fill with comma separated digits from 1 - 2		LeafTemp= => fill with comma separated digits from 1 - 2
	LeafWetness= => 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		CO2= => fill with 1

HansR: /* Operation */

2025-02-06T16:25:39Z

Operation

← Older revision		Revision as of 16:25, 6 February 2025
Line 37:		Line 37:
	#CumulusUtils must be run once with the command ''ExtraSensors'' (fastest) or ''Website'' to create the required parameters in the section ''[ExtraSensors]'' in the inifile.		#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.		#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''. Filling these with e.g. '''1,2,3''' activates those sensors and a subsequent run will show these under the menu choice ''Extra''.		#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 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. Use the [[Custom Logs\|CustomLogs and its module]] for this.		#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. Use the [[Custom Logs\|CustomLogs and its module]] for this.

HansR: /* Operation */

2024-01-04T10:19:35Z

Operation

← Older revision		Revision as of 10:19, 4 January 2024
Line 39:		Line 39:
	#After the first run the following inifile parameters exist (see below): ''ExtraTemp, ExtraHum, ExtraDP, SoilTemp, SoilMoisture, AirQuality, UserTemp, LeafTemp, LeafWetness''. Filling these with e.g. '''1,2,3''' activates those sensors and a subsequent run will show these under the menu choice ''Extra''.		#After the first run the following inifile parameters exist (see below): ''ExtraTemp, ExtraHum, ExtraDP, SoilTemp, SoilMoisture, AirQuality, UserTemp, LeafTemp, LeafWetness''. 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 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. ~~Currently charting the Lightning sensor can only be done as an External Extra Sensor. Complete charting will be possible with the implementation of~~ the Custom Logs ~~(no date~~ ~~has~~ ~~been~~ ~~set~~ ~~yet)~~.		#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. Use the [[Custom Logs\|CustomLogs and its module]] for this.
	#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'''.		#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'''.

HansR: /* Introduction */

2024-01-04T10:13:15Z

Introduction

← Older revision		Revision as of 10:13, 4 January 2024
Line 5:		Line 5:
	''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.		''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.		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.		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.

HansR: /* Introduction */

2023-10-07T13:50:02Z

Introduction

← Older revision		Revision as of 13:50, 7 October 2023
Line 10:		Line 10:

	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]].		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 ===		=== Dependency ===

HansR: /* Introduction */

2023-03-28T13:33:31Z

Introduction

← Older revision		Revision as of 13:33, 28 March 2023
Line 5:		Line 5:
	''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.		''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.
	''Extra Sensors'' have a certain complexity because, although handled by CumulusMX, they are kind of anarchic: unregulated, CumulusMX does not care, when detected they are always displayed only logged when logging is switched on and then not all of them are logged. There are more webtags than logged sensors etc... This complexity made some additional handling necessary.

⚫	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 ~~(like e.g. LeafTemp3 and 4)~~.

	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.		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.

HansR: /* Translation/Language */

2023-03-26T07:18:16Z

Translation/Language

← Older revision		Revision as of 07:18, 26 March 2023
Line 32:		Line 32:
	The translation tags content for the extra sensor names are defaulted with the extra sensor description texts from ''strings.ini'' when the tags are created in the CUstringsXX.ini and can then be changed by the user. These modifications will be used in subsequent runs for the ''ExtraSensors'' module. As a consequence, the user may choose different descriptions in CMX and in CUtils for the ''Extra Sensors''.		The translation tags content for the extra sensor names are defaulted with the extra sensor description texts from ''strings.ini'' when the tags are created in the CUstringsXX.ini and can then be changed by the user. These modifications will be used in subsequent runs for the ''ExtraSensors'' module. As a consequence, the user may choose different descriptions in CMX and in CUtils for the ''Extra Sensors''.

	To set back the default values of the tag ~~namaes~~ - the values in ''strings.ini'' - just remove the tags from the ''CUstringsXX.ini'' file.		To set back the default values of the tag names - the values in ''strings.ini'' - just remove the tags from the ''CUstringsXX.ini'' file.

	== Operation ==		== Operation ==

HansR: /* Translation/Language */

2023-03-26T07:17:52Z

Translation/Language

← Older revision		Revision as of 07:17, 26 March 2023
Line 26:		Line 26:

	=== Translation/Language ===		=== Translation/Language ===
	The translation of of this module is accommodated via two sections in the ''CUstringsXX.ini'' file: ''Compiler'' and ''ExtraSensors''.		The translation of of this module is accommodated via two sections in the ''CUstringsXX.ini'' file: ''Compiler'' (most) and ''ExtraSensors'' (some).

		⚫	You will find all translation tags for the sensor names in the section ''Compiler'' and this includes the three values for the lightning detector although those are not really explicit sensors. This is analogue to all standard plot variables.
	The basics is that you will find some of translation tags - translation tags used in the HTML part of the module- in the section ''ExtraSensors''.

		⚫	The translation tags content for the extra sensor names are defaulted with the extra sensor description texts from ''strings.ini'' when the tags are created in the CUstringsXX.ini and can then be changed by the user. These modifications will be used in subsequent runs for the ''ExtraSensors'' module. As a consequence, the user may choose different descriptions in CMX and in CUtils for the ''Extra Sensors''.
⚫	~~Subsequently, you~~ will find all translation tags for the sensor names in the section ''Compiler'' and this includes the three values for the lightning detector although those are not really explicit sensors. This is analogue to all standard plot variables.

			To set back the default values of the tag namaes - the values in ''strings.ini'' - just remove the tags from the ''CUstringsXX.ini'' file.
⚫	The translation tags content for the sensor names are defaulted with the sensor description texts from ''strings.ini'' when the tags are created in the CUstringsXX.ini and can then be changed by the user. These modifications will be used in subsequent runs for the ''ExtraSensors'' module. As a consequence, the user may choose different descriptions in CMX and in CUtils for the ''Extra Sensors''

	== Operation ==		== Operation ==

HansR: /* Introduction */

2023-03-08T02:34:09Z

Introduction

← Older revision		Revision as of 02:34, 8 March 2023
Line 24:		Line 24:
	UserModificationExtraSensorCharts=true		UserModificationExtraSensorCharts=true
	the charts will no longer be overwritten and the user may modify the generated charts to his own tasting.		the charts will no longer be overwritten and the user may modify the generated charts to his own tasting.

			=== Translation/Language ===
			The translation of of this module is accommodated via two sections in the ''CUstringsXX.ini'' file: ''Compiler'' and ''ExtraSensors''.

			The basics is that you will find some of translation tags - translation tags used in the HTML part of the module- in the section ''ExtraSensors''.

			Subsequently, you will find all translation tags for the sensor names in the section ''Compiler'' and this includes the three values for the lightning detector although those are not really explicit sensors. This is analogue to all standard plot variables.

			The translation tags content for the sensor names are defaulted with the sensor description texts from ''strings.ini'' when the tags are created in the CUstringsXX.ini and can then be changed by the user. These modifications will be used in subsequent runs for the ''ExtraSensors'' module. As a consequence, the user may choose different descriptions in CMX and in CUtils for the ''Extra Sensors''

	== Operation ==		== Operation ==