Should have remembered to look at the Davis Serial Communications Reference Manual <https://www.davisinstruments.com/support/weather/download/VantageSerialProtocolDocs_v261.pdf>. Extra temperatures in loop packets are covered at page 22, with whole degrees F clearly stated (note the 90 degree F offset and 1 byte field size per sensor compared to 2 bytes for outside temperature). Archive records are covered at pages 32 (rev A) and 33 (rev B) and whilst not stated as whole degrees, the fact the data is stored in a single byte with a 90 degree F offset (same as loop packets) means the extra temperatures in the archive records are also whole degrees F.
I thought I had read something somewhere (not from Davis) about a way around this, can't recall where or what though - may have been dreaming. Maybe an odd limitation but who knows what constraints/backwards compatibility issues Davis may have been working under. May have been just not enough bytes/bits to go around in a fixed length message format. Gary On Tuesday, 18 June 2019 10:03:17 UTC+10, vince wrote: > > On Monday, June 17, 2019 at 2:44:33 PM UTC-7, GCC Observatory wrote: >> >> My database is showing both extraTemp1 and extraHumid1 with 1 decimal >> place precision, but it appears the values are rounded to the nearest >> integer. For example, the temperature increases from 78.0 to 79.0. The >> loop packets show the same thing. >> >> > ok, that makes sense. It wasn't clear what specific kind of sensors you > were referring to in your original question. Sounds like you hit a > limitation in the Davis sensors (odd to have that limitation, eh). > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/c83823d7-5148-4319-b34d-2ea20c63cee8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
