Hello Leo, You might have similar symptoms, but I suspect a different cause. The modified driver I posted earlier today should fix some problems with random stopping of data collection. The issue in this thread relates specifically to a problem when running belchertown skin, but not otherwise.
Your previous syslog posted in weewx-devel did not seem to have driver diagnostics enabled, so it is not possible to tell exactly. Cameron. On Monday, 24 September 2018 17:15:19 UTC+10, leo de geer wrote: > > I have the same problem on my wmr300 and need to reload my weewx every > hour to have a working setup. > > Den 2018-09-22 kl. 17:15, skrev Cameron D: > > Hi, > I can interpret the log, but I do not understand what it has to do with > the extension being active or not. > Every 20 seconds you write an "a6" packet to the wmr300 console. This is > the heartbeat that keeps it transmitting. > The console replies with a status packet "57" > Then, at 09:56:58, the driver sends the a6 but there is no reply - the > console stops responding to the a6 packets and after 60 seconds stops > transmitting. > > I do not remember seeing this problem, but I think my driver fix posted > last April might correct it. It tries harder to restart the console loop. > > I ported my fix into rc6 and am just now testing it with 3.8.2. I will > post it in a day or so. > > However, I do not like the fact that the console apparently ignores 3 > heartbeats in a row - it is like something is blocking the usb transmission > to the console. > > Cameron > > > On Saturday, 22 September 2018 18:27:02 UTC+10, Juan Antonio Mosquera > wrote: >> >> ok, then I do not understand anything. Why turning off the extension is >> all good ?. >> Can anyone interpret the debug comm log to identify the error? >> >> greetings and thanks. >> >> El sábado, 22 de septiembre de 2018, 10:19:09 (UTC+2), Paul Lacatus >> escribió: >>> >>> Hi Juan , >>> >>> For me Raspberry Pi debian stretch , weewx 3.8.2 wmr300 driver and >>> Belchertown extension looks like being stable. The messages with dump >>> history disabled appears in the logs >>> >>> Paul >>> >>> Sent from my iPad >>> >>> On 22 Sep 2018, at 10:49, Juan Antonio Mosquera < >>> [email protected]> wrote: >>> >>> I have deleted all the memory of the station and now it does not show >>> the message: *wmr300: dump history is disabled*, but at approximately 3 >>> hours the station stops sending data to weewx. If I deactivate extension >>> everything works correctly. >>> >>> Greetings. >>> >>> El viernes, 21 de septiembre de 2018, 14:26:29 (UTC+2), Juan Antonio >>> Mosquera escribió: >>>> >>>> attach again... >>>> >>>> >>>> >>>> El viernes, 21 de septiembre de 2018, 14:24:48 (UTC+2), Juan Antonio >>>> Mosquera escribió: >>>>> >>>>> >>>>> When I activate the Belchertown WMR300 extension to send data at 3 >>>>> o'clock (random). Attached log with debug_comm activated. >>>>> >>>> -- >>> 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. >>> >>> -- > 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] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- 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.
