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.

Feb 21 07:26:54 RanchWx weewx[7135]: engine: Starting up weewx version 3.9.1
Feb 21 07:26:54 RanchWx weewx[7135]: engine: Station does not support 
reading the time
Feb 21 07:26:54 RanchWx weewx[7135]: engine: Starting main packet loop.
Feb 21 07:26:54 RanchWx weewx[7135]: ultimeter: Failed attempt 1 of 5 to 
get readings: Unexpected buffer length 49
Feb 21 07:26:57 RanchWx weewx[7135]: ultimeter: Failed attempt 2 of 5 to 
get readings: Unexpected buffer length 446
Feb 21 07:27:00 RanchWx weewx[7135]: ultimeter: Failed attempt 3 of 5 to 
get readings: Unexpected buffer length 446
Feb 21 07:27:03 RanchWx weewx[7135]: ultimeter: Failed attempt 4 of 5 to 
get readings: Unexpected buffer length 463
Feb 21 07:27:06 RanchWx weewx[7135]: ultimeter: Failed attempt 5 of 5 to 
get readings: Unexpected buffer length 461
Feb 21 07:27:09 RanchWx weewx[7135]: ultimeter: Max retries (5) exceeded 
for readings
Feb 21 07:27:09 RanchWx weewx[7135]: engine: Main loop exiting. Shutting 
engine down.
Feb 21 07:27:09 RanchWx weewx[7135]: ultimeter: close serial port 
/dev/ttyUSB0
Feb 21 07:27:10 RanchWx weewx[7135]: engine: Caught WeeWxIOError: Max 
retries (5) exceeded for readings
Feb 21 07:27:10 RanchWx weewx[7135]:     ****  Waiting 60 seconds then 
retrying...


On Thursday, February 21, 2019 at 5:51:41 AM UTC-8, Thomas Keffer wrote:
>
> Oops. The set of valid buffer lengths was wrong. Try this one.
>
>
>
> On Thu, Feb 21, 2019 at 5:49 AM Thomas Keffer <[email protected] 
> <javascript:>> 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 expecting.
>>
>> The trouble is there is a communications glitch. Then the number of  
>> bytes may be unknown.
>>
>> It would help if you could include the log for one of these glitches. Be 
>> sure to not only set debug=1 at the top of weewx.conf, but also set 
>> debug_serial in the [Ultimeter] section:
>>
>> debug = 1
>> ...
>>
>> [Ultimeter]
>>   port = XXX
>>   debug_serial = 1
>>
>>
>> At the risk of confusing things, here's another version of the driver. 
>> This one looks for the number of bytes in the serial port buffer, then 
>> reads exactly that many. So, it should work for 48, 50, or 52 byte buffers. 
>> But, it could still have a sync problem.
>>
>> -tk
>>
>> On Thu, Feb 21, 2019 at 5:39 AM Steve2Q <[email protected] <javascript:>> 
>> 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 .20) apparently expects 52 bytes. Could this be 
>>> the problem?. Here is a snip from their web site:
>>>
>>>
>>>    - *Data Logger Mode**:  to manually select, press CLEAR + WIND SPEED 
>>>    for 3 seconds. ** While in this mode, records are sent out 
>>>    continuously at up to about 120 per minute.  The total record size is 48 
>>>    hex digits + header, carriage return and line feed.  (All models)* 
>>>    - *Packet Mode**:  to manually select, press CLEAR + WIND CHILL for 
>>>    3 seconds.  While in this mode, one record is output every five minutes 
>>> (at 
>>>    5 min past the hour, 10 min past, 15 min past, etc.). The total record 
>>>    length is 52 hex digits + header, carriage return and line feed.  (All 
>>>    models)*
>>>
>>> and this:
>>>
>>> *DATA LOGGER MODE - RECORD STRUCTURE* 
>>>
>>>    - *Header = !!  (or || if in Multiple Output Mode) * 
>>>    - *Data Fields * 
>>>       - *1. Wind Speed (0.1 kph) * 
>>>       - *2. Wind Direction (0-255) * 
>>>       - *3. Outdoor Temp (0.1 deg F) * 
>>>       - *4. Rain* Long Term Total (0.01 inches) * 
>>>       - *5. Barometer (0.1 mbar) * 
>>>       - *6. Indoor Temp (0.1 deg F) * 
>>>       - *7. Outdoor Humidity (0.1%) * 
>>>       - *8. Indoor Humidity (0.1%) * 
>>>       - *9. Date (day of year) * 
>>>       - *10. Time (minute of day) * 
>>>       - *11. Today's Rain Total (0.01 inches)* * 
>>>       - *12. 1 Minute Wind Speed Average (0.1kph)* *
>>>    - *Carriage Return & Line Feed *
>>>
>>>
>>> **Some instruments may not include field 12, some may not include 11 or 
>>> 12. Please contact Peet Bros. if this presents any problem. Total size: 40, 
>>> 44 or 48 characters (hex digits) + header, carriage return and line feed. *
>>>
>>> *PACKET MODE - RECORD STRUCTURE* 
>>>
>>>    - *Header = $ULTW * 
>>>    - *Data Fields * 
>>>       - *1. Wind Speed Peak over last 5 min. (0.1 kph) * 
>>>       - *2. Wind Direction of Wind Speed Peak (0-255) * 
>>>       - *3. Current Outdoor Temp (0.1 deg F) * 
>>>       - *4. Rain Long Term Total (0.01 in.) * 
>>>       - *5. Current Barometer (0.1 mbar) * 
>>>       - *6. Barometer Delta Value(0.1 mbar) * 
>>>       - *7. Barometer Corr. Factor(LSW) * 
>>>       - *8. Barometer Corr. Factor(MSW) * 
>>>       - *9. Current Outdoor Humidity (0.1%) * 
>>>       - *10. Date (day of year) * 
>>>       - *11. Time (minute of day) * 
>>>       - *12. Today's Rain Total (0.01 inches)** 
>>>       - *13. 5 Minute Wind Speed Average (0.1kph)* *
>>>    - *Carriage Return & Line Feed*
>>>
>>>
>>>
>>> **Some instruments may not include field 13, some may not include 12 or 
>>> 13. Please contact Peet Bros. if this presents any problem. *
>>>
>>> *Packet Mode records are output every five minutes:  first, upon 
>>> selection of Packet Mode; then, at every 5 minutes past the hour (12:00, 
>>> 12:05, 12:10, etc.), continuosly.*
>>>
>>> *Total size: 44, 48 or 52 characters (hex digits) + header, carriage 
>>> return and line feed. *
>>>
>>>
>>> -- 
>>> 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.

Reply via email to