> i suppose the solution is to add 9/5 +32 to my parsing extension to log
> the reading as F'
>
Provided your 1 wire sensor always reports in C and your vantage driver
always emits F then yes, a more robust approach might be (pseudo code):
if packet['usUnits'] == US:
packet['1wire_temp'] = CtoF(temperature)
else:
packet['1wire_temp'] = temperature
one thing that iam not sure is why i cannot alter the readings under
>
> [StdCalibrate]
>
> [[Corrections]]
> # For each type, an arbitrary calibration expression can be given.
> # It should be in the units defined in the StdConvert section.
> # Example:
> foo = foo + 0.2
>
>
> cctemp = cctemp *1.8
>
> extraTemp7 = extraTemp7 + 10
>
> the cctemp is logged with my extension ok i will modify it
> but the extraTemp7 is logged with the 1wire extension that 's freely
> available from weewx
>
>
> trying to add 10 to extraTemp7 has no effect on what is displayed on the
> html pages
>
> strange?
>
>
You should be able to correct like that in StdCalibrate, though its rather
clunky/inflexible and not without risk. One thing to keep in mind is that
the weeWX services are run sequentially as per the [Engine] [[Services]]
stanza in weewx.conf. So if your 1 wire service is adding data to the
packet/record after StdCalibrate has run then anything that StdCalibrate
does (or attempts to do) to your 1 wire data will fail as the 1 wire data
is not yet in the packet/record. The risk in this approach is that for the
period between when your 1 wire service places your 1 wire data in the
packet/record and StdCalibrate 'fixes' the 1 wire data there is an anomaly
in the packet/record and any services that act on this anomalous data (ie
before StdCalibrate 'fixes' it) will possibly be at risk.
Gary
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
