On Sunday, February 6, 2022 at 9:26:38 AM UTC-5 [email protected] wrote:
> may have fixed it. used rtl_433 set only to 915mhz to time interval of > WH32B ... it is 1 minute between packets. > atlas is much faster than 1 minute. > need to add time for rtl_433 finding "minimum detection level based on > noise" for each frequency hop. > set "hop_interval 120" in rtl_433.conf. set "archive_interval = 300" in > weewx.conf. > 300 sec = two times 120 ... one for atlas and one for WH32B plus an extra > minute for "minimum detection level based on noise". > This fixed the problem. Now weewx draws lines not points when plotting. > excellent! as you discovered, there are two approaches: either get more data samples, or adjust the 'line_gap_fraction' to connect the dots (as explained in the weewx user guide: http://weewx.com/docs/usersguide.htm#dots_in_plots) i am not familiar with the internals of belchertown skin, but i think that 'gapsize' is the parameter that the belchertown skin uses for a similar purpose to line_gap_fraction. as for record_generation, when using the SDR driver you want 'software'. but it won't matter. the SDR driver cannot do hardware-based record generation (that only works if there is a hardware data logger), so it tells this to weewx when it is loaded. so weewx uses record_generation=software, even if 'hardware' is specified in the config file. you should see this in the log file during startup. -- 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/87ffd60d-5cae-44c4-8ee9-ff1279b2ac90n%40googlegroups.com.
