I am monitoring acurite strike data (6045M with rtl_433 not weewx). One tricky thing about acurite is that strike count
1) is a cumulative count of strikes, so it needs differencing if you want strikes in some interval. Presumably that's the count in the archive interval for weewx. 2) rolls over from 255 to 0, so you also need to undo that if you want cumulative count as a number. Then you need to figure out when you do want to reset it, or how you want to deal with that, because the un-wrapped value will increase without bound. But it will likely not overflow an int32_t in your lifetime. I'm really unclear on how people deal with this issue. and then as your code indicates, distance is only valid in a transmission where count has increased from the previous transmission. That's complicated because if you miss a transmssion where it increments, you miss it, but it seems the next one you will perceive the incremented count and the distance will still be the same. Hope this helps more than it is confounding. -- 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/rmih74tzynt.fsf%40s1.lexort.com.
signature.asc
Description: PGP signature
