[weewx-user] Re: weewx data loop error with new Acurite 02064C

[Blake Austin Hughes]

make sure you're in USB mode 4 on your acurite receiver when trying to pair 
with weeWX

On Saturday, January 16, 2016 at 9:03:05 PM UTC-6, Joe Morris wrote:
>
> Trying to get this up and running for the first time. I'm running on the 
> software on Ubuntu Precise (12.04). Here's the output I get from weewx in 
> syslog:
>
> Jan 16 18:57:49 kvm01 weewx[21745]: engine: Initializing weewx version 
> 3.3.1
>
> Jan 16 18:57:49 kvm01 weewx[21745]: engine: Using Python 2.7.3 (default, 
> Apr 20 2012, 22:39:59) #012[GCC 4.6.3]
>
> Jan 16 18:57:49 kvm01 weewx[21745]: engine: Platform 
> Linux-3.2.0-23-generic-x86_64-with-Ubuntu-12.04-precise
>
> Jan 16 18:57:49 kvm01 weewx[21745]: engine: pid file is /var/run/weewx.pid
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Using configuration file 
> /etc/weewx/weewx.conf
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Initializing engine
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading station type AcuRite 
> (weewx.drivers.acurite)
>
> Jan 16 18:57:49 kvm01 weewx[21749]: acurite: driver version is 0.24
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdTimeSynch
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdTimeSynch
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdConvert
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: StdConvert target unit is 0x1
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdConvert
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdCalibrate
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdCalibrate
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdQC
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdQC
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.wxservices.StdWXCalculate
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.wxservices.StdWXCalculate
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdArchive
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Archive will use data binding 
> wx_binding
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Record generation will be 
> attempted in 'hardware'
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Using archive interval of 300 
> seconds
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Use LOOP data in hi/low 
> calculations: 1
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Using binding 'wx_binding' to 
> database 'weewx.sdb'
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Starting backfill of daily 
> summaries
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Daily summaries up to date.
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdArchive
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.restx.StdStationRegistry
>
> Jan 16 18:57:49 kvm01 weewx[21749]: restx: StationRegistry: Data will not 
> be posted. Missing option 'station_url'
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.restx.StdStationRegistry
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.restx.StdWunderground
>
> Jan 16 18:57:49 kvm01 weewx[21749]: restx: Wunderground: Posting not 
> enabled.
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.restx.StdWunderground
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.restx.StdPWSweather
>
> Jan 16 18:57:49 kvm01 weewx[21749]: restx: PWSweather: Posting not enabled.
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.restx.StdPWSweather
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.restx.StdCWOP
>
> Jan 16 18:57:49 kvm01 weewx[21749]: restx: CWOP: Posting not enabled.
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.restx.StdCWOP
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.restx.StdWOW
>
> Jan 16 18:57:49 kvm01 weewx[21749]: restx: WOW: Posting not enabled.
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.restx.StdWOW
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.restx.StdAWEKAS
>
> Jan 16 18:57:49 kvm01 weewx[21749]: restx: AWEKAS: Posting not enabled.
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.restx.StdAWEKAS
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdPrint
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdPrint
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Loading service 
> weewx.engine.StdReport
>
> Jan 16 18:57:49 kvm01 weewx[21749]: engine: Finished loading service 
> weewx.engine.StdReport
>
> Jan 16 18:57:49 

[weewx-user] Re: weewx data loop error with new Acurite 02064C

[nonillion]

Hey Kelly,

Did you ever figure out a better solution to your problem? I have a new 
AcuRite 02032 and have been having a heck of a time getting weewx to 
successfully pull data from the display USB. I've periodically had some 
info successfully post to wunderground, but most of the time weewx is 
sitting there failing to capture input from the USB, cycling 10 times and 
then restarting:

acurite: Found station at bus= device=
acurite: Failed attempt 1 of 10 to get LOOP data: [Errno 110] Operation 
timed out
...
acurite: Found station at bus= device=
acurite: Failed attempt 10 of 10 to get LOOP data: [Errno 110] Operation 
timed out

ver: weewx 3.8.0 / py 2.7.13 / deb stretch

Tx!
-JM

On Friday, February 10, 2017 at 5:00:02 PM UTC-8, Kelly Hewitt wrote:
>
> Acurite 02064C weewx LOOP error on Ubuntu 14.04 LTS
>
> Failed attempt 1 of 10 to get LOOP data: error sending control 
> message: Protocol error 
>
> I've had issues with this for about 13 months. It most often occurs when 
> the weewx host reboots, the Acurite display unit will then have USB 
> protocol issues for several hours until the acurite.py script effectively 
> regains connection with the display unit. I don't like gaps in data and 
> this has plagued me for a year. 
>
> Tested:
>
>1. Ferrite on the USB cable - No effect
>2. Reset the display console - No effect
>3. New USB cable (x2) - No effect
>4. CRON usb script task to reset the USB connection every 4 hours - no 
>effect
>5. Start the weewx host then plug in the display - no effect
>6. Plug in the display then start the weewx host - no effect
>
>
> *The only quick solution I've found is to unplug the display from the 
> weewx host and connect it to a Windows machine with the Acurite Connect 
> software and allow it to complete a data dump, unplug it, then plug the 
> display USB into the weewx host.*
>
> After plugging it back into the weewx host and watching the ubuntu syslog 
> (sudo tail -f /var/log/syslog) it will indicate after a few attempts that 
> the USB connection is active and receiving data in +/- 5 minutes.
>
> This suggests the USB controller in the display device is getting reset 
> with the Acurite Connect software - outside the scope of what weewx 
> currently has access to. It's unfortunate there isn't a method to reset the 
> display device USB connection remotely.
>
> *If someone has the ability to decompose the Acurite Connect software and 
> find out how it is resetting the USB controller on the display device that 
> would be very much appreciated.*
>
>
> *Acurite Connect Software 
> *
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx data loop error with new Acurite 02064C

[Kelly Hewitt]

>
> Acurite 02064C weewx LOOP error on Ubuntu 14.04 LTS

Failed attempt 1 of 10 to get LOOP data: error sending control message: 
Protocol error 

I've had issues with this for about 13 months. It most often occurs when 
the weewx host reboots, the Acurite display unit will then have USB 
protocol issues for several hours until the acurite.py script effectively 
regains connection with the display unit. I don't like gaps in data and 
this has plagued me for a year. 

Tested:

   1. Ferrite on the USB cable - No effect
   2. Reset the display console - No effect
   3. New USB cable (x2) - No effect
   4. CRON usb script task to reset the USB connection every 4 hours - no 
   effect
   5. Start the weewx host then plug in the display - no effect
   6. Plug in the display then start the weewx host - no effect
   

*The only quick solution I've found is to unplug the display from the weewx 
host and connect it to a Windows machine with the Acurite Connect software 
and allow it to complete a data dump, unplug it, then plug the display USB 
into the weewx host.*

After plugging it back into the weewx host and watching the ubuntu syslog 
(sudo tail -f /var/log/syslog) it will indicate after a few attempts that 
the USB connection is active and receiving data in +/- 5 minutes.

This suggests the USB controller in the display device is getting reset 
with the Acurite Connect software - outside the scope of what weewx 
currently has access to. It's unfortunate there isn't a method to reset the 
display device USB connection remotely.

*If someone has the ability to decompose the Acurite Connect software and 
find out how it is resetting the USB controller on the display device that 
would be very much appreciated.*


*Acurite Connect Software 
*

-- 
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.
For more options, visit https://groups.google.com/d/optout.