[weewx-user] Re: WMR300 - intermittent and partial loss of loop data

OK thanks. I will test this driver in weewx 3.9.1 tomorrow. El domingo, 17 de febrero de 2019, 7:57:54 (UTC+1), Cameron D escribió: > > The 3.9.1 driver does not have my changes, but does have some > modifications for python 3. I expect that means the default driver will > have the same problem

Re: [weewx-user] Re: Second crash after 11 days

I saw no errors during the run of over 30 minutes. I edited out the DISABLED_ under the get_time and set_time portion of the driver and restarted with debugs commented out. TOP show weexd at 3.3% -- You received this message because you are subscribed to the Google Groups "weewx-user" group.

Re: [weewx-user] Re: Second crash after 11 days

I guess so. Are you worried about the log size? I just want to make sure we capture any data gaps. -tk On Thu, Feb 21, 2019 at 9:28 AM Steve2Q wrote: > Tom..is 30 minutes enough time with debug and debug_serial both set to 1 ? > > -- > You received this message because you are subscribed to th

Re: [weewx-user] Re: Second crash after 11 days

Tom..is 30 minutes enough time with debug and debug_serial both set to 1 ? -- 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 weewx-user+unsubscr...@googlegroups.com.

Re: [weewx-user] Re: Second crash after 11 days

Be sure to run with debug=1 and debug_serial=1 as per my earlier email . On Thu, Feb 21, 2019 at 9:18 AM Ralph Underwood wrote: > I have v0.22 running now and it appears to work - no buffer errors. > > Ralph > > -- > You receiv

Re: [weewx-user] Re: Second crash after 11 days

I have v0.22 running now and it appears to work - no buffer errors. Ralph -- 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 weewx-user+unsubscr...@googlegroups.com.

Re: [weewx-user] Re: Second crash after 11 days

I am presently testing 0.22, Tom and Matthew. So far the output is not showing any buffer length errors. I will let it run for at least 30 minutes. Steve -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop rec

Re: [weewx-user] Re: Second crash after 11 days

I will test v0.22. Thanks!! On Thursday, February 21, 2019 at 9:04:04 AM UTC-8, Ralph Underwood wrote: > > The URL for the development station is http://www.mapleleaf.ruresearch.com. > This station is in my basement lab area - the wind and rain stuff is > sitting on a counter so that's why the

Re: [weewx-user] Re: Second crash after 11 days

The URL for the development station is http://www.mapleleaf.ruresearch.com. This station is in my basement lab area - the wind and rain stuff is sitting on a counter so that's why there are no readings for them. The "Temperature 1" reading is from a DS18B20 sensor connected to an Adafruit Huzz

Re: [weewx-user] Re: Second crash after 11 days

OK, thanks, Ralph. Let's try this version of the driver, v0.22. This one is a little more sophisticated. It reads in buffer fulls (and, thus, is more efficient), but parcels them out byte-by-byte. It has the ability to throw away anything leading up to the buffer header (b'!!'). This is v0.22. I

Re: [weewx-user] Re: Second crash after 11 days

Ralph. Thanks for joining this discussion. A few questions: 1. What is your station URL? There are not too many of us Ultimeter users, but I think it is great that Tom, Matt, Andrew, Vince and so many other help out our small population as best they can. Having another 2100 user may make debugg

Re: [weewx-user] Re: Second crash after 11 days

I have a couple of stations with Ultimeter 2100 and usb-serial connections to RPi 3 B+. Both appear to have increasing memory usage. I just copied the "new" ultimeter.py driver to the driver directory and restarted - this was my result. I went back to "old" version of driver and restarted OK

Re: [weewx-user] Re: Second crash after 11 days

I read this as 48 data bytes + 2 for header + cr +lf = 52 On Thursday, 21 February 2019 15:39:42 UTC+2, Steve2Q wrote: > > A follow up: According to Peet Bros web site the Ultimeter 2100 (and > several other models) emit data in 48 byte chunks in Data Logger Mode, > while ultimeter.py (version

Re: [weewx-user] Re: Second crash after 11 days

Oops. The set of valid buffer lengths was wrong. Try this one. On Thu, Feb 21, 2019 at 5:49 AM Thomas Keffer wrote: > Possibly, but I don't think so. The way I read the documents, a given > instrument has a given buffer length. Yours seems to be 52 bytes, which is > what the driver is expectin

Re: [weewx-user] Re: Second crash after 11 days

Possibly, but I don't think so. The way I read the documents, a given instrument has a given buffer length. Yours seems to be 52 bytes, which is what the driver is expecting. The trouble is there is a communications glitch. Then the number of bytes may be unknown. It would help if you could incl

Re: [weewx-user] Re: Second crash after 11 days

A follow up: According to Peet Bros web site the Ultimeter 2100 (and several other models) emit data in 48 byte chunks in Data Logger Mode, while ultimeter.py (version .20) apparently expects 52 bytes. Could this be the problem?. Here is a snip from their web site: - *Data Logger Mode**: t

Re: [weewx-user] Re: Second crash after 11 days

Hello: I have been out of town for several days. The good news is top shows weexd using only 4.6% of memory. The bad news is there are now many gaps in the charts (see example), which apparently are caused by the "unexpected error byte messages" I have been getting. So the question remains shoul