Extra Sensor Files: Difference between revisions

m
→‎Design flaw?: new sub-heading, as a break for existing text
(Add table of fields for MX)
m (→‎Design flaw?: new sub-heading, as a break for existing text)
The fields that can appear in the file vary depending on which release you are using. The list of fields available for your release can be seen in a file: <code>Extrafileheader.txt</code> stored in the folder containing the executable. The standard names shown in that list can be [[#General customisation|customised, as described below,]] to names that suit you better.
 
==Design flaw?==
There are lots of extra sensor fields in the legacy Cumulus, with many more in MX. It is probably technically impossible to have hardware that would use all possible fields, so most files will contain an awful lot of zeroes representing sensors not used in your implementation.
 
Unfortunately, MX kept compatibility with the legacy Cumulus, and just added extra fields to the end, rather than redesigning the whole concept and creating a new file design that just contains the fields currently being used.
 
There are lots of extra sensor fields in the legacy Cumulus, with many more in MX. It is probably technically impossible to have hardware that would use all possible fields, so most files will contain an awful lot of zeroes representing sensors not used in your implementation. Over time this represents extremely inefficient storage, as well as difficulty in finding fields of interest...
 
== Uploading the latest log to your web server==
* 40 to 41 (AO to AP): Two leaf temperature values
* 42 to 43 (AQ to AR): Two leaf wetness values
 
 
= Extra Sensors=
5,838

edits