When I asked earlier - before Matthew's detailed response - if you had tried ignore_bounds set to True you said you had tried, but it had had the same result. What had you actually done - which did not work - compared to True/True which did work - just so others do not misinterpret the original thread I referred you to, which you said you had already seen??
On Friday, 30 December 2016 21:37:42 UTC+2, Dennis Hall wrote: > Thank you very much > > The True/True did the trick and it is working now. The things we do for > fun! > > D~ > > On Friday, December 30, 2016 at 10:25:07 AM UTC-8, mwall wrote: >> >> >> >> On Friday, December 30, 2016 at 1:05:51 PM UTC-5, Dennis Hall wrote: >>> >>> Are we talking about in the weewx.conf file? (Yes) >>> Or in the acurite.py driver? >>> >>> What is the location of the driver file? >>>> >>>> >>>>>> >> dennis, >> >> the drivers built-in to weewx are located in the weewx/drivers >> directory. additional drivers are installed to the user directory. >> >> has your 01035 ever worked properly with weewx? you might want to power >> cycle the 01035 (remove batteries and disconnect usb), just in case the >> firmware somehow got into a weird state. >> >> there are two parameters that would affect you: use_constants and >> ignore_bounds. these are specified in the [Acurite] section of your weewx >> configuration file. the defaults should work with most stations. >> >> if you have a 01035 or 01036 and you see 'unknown calibration constants', >> then you should first try this configuration (you must restart weewx for >> weewx.conf changes to take effect): >> >> [Acurite] >> ... >> use_constants = True >> ignore_bounds = False >> >> if you still see the 'unknown calibration constants' message, then try >> this: >> >> [Acurite] >> ... >> use_constants = True >> ignore_bounds = True >> >> if you still see 'unknown calibration constants', then try: >> >> [Acurite] >> ... >> use_constants = False >> ignore_bounds = True >> >> although if you get this far, your station is behaving in a way that no >> one else has ever reported. >> >> here are the comments about the parameters from the driver itself: >> >> use_constants - Indicates whether to use calibration constants >> when >> decoding pressure and temperature. For consoles that use the HP03 >> sensor, >> use the constants reported by the sensor. Otherwise, use a >> linear >> approximation to derive pressure and temperature values from the >> sensor >> >> readings. >> [Optional. Default is >> True] >> >> >> >> ignore_bounds - Indicates how to treat calibration constants from >> the >> pressure/temperature sensor. Some consoles report constants that >> are >> outside the limits specified by the sensor manufacturer. Typically >> this >> would indicate bogus data - perhaps a bad transmission or noisy >> USB. >> But in some cases, the apparently bogus constants actually work, >> and >> no amount of power cycling or resetting of the console changes the >> values >> that the console emits. Use this flag to indicate that this is one >> of >> those quirky >> consoles. >> [Optional. Default is >> False] >> >> hope that helps, >> >> m >> >> -- 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.
