Please let me know what the instrumented driver shows. But, this is definitely abnormal behavior --- the station should never brick, no matter what the driver does.
Not to say it couldn't possibly be the driver, but it has a has a 10 year history on thousands of stations. I'd look elsewhere first. If you, or a friend, has a second logger, you could try swapping them. And/or give Davis a call. If they give you some pushback on weewx, let me know. I have a working relationship with them. -tk On Sun, Feb 25, 2018 at 11:34 AM, <ddur...@gmail.com> wrote: > That is likely me terminating it . I'd have to go find the very first > version of the log, but suffice to say once it get the DMPAFT error 4 > times, it is down for the count. It never recovers (I've tried probably > hundreds of times and have tried restarting the USB port and restarting the > serial interface ...) > > > 1. I know you have found that power cycling the Vantage clears the error. >> Have you tried clearing the log? Use the utility wee_device: >> >> wee_device --clear-memory >> >> >> > This will only work if you do it before you get the CRC16 error. Once you > get that the envoy seems bricked until you remove power. You can't get to > it with minimum, wee_device won't connect, it just doesn't respond any more. > > >> 2. Are you using a USB-to-Serial cable? If so, try another one. They are >> often flaky. >> > > No I have the USB version and it has the really short usb cable to the Pi > with ferrites on each end. It is also wrapped in foil and very properly > seated including a little support under the logger so it can't push down > towards circuit board and potentially lift off of pins. > >> >> 3. Make sure the logger is properly seated in the console. >> >> comment above > >> >> >> >> On Sat, Feb 24, 2018 at 10:42 PM, <ddu...@gmail.com> wrote: >> >>> Here are the logs. >>> >>> This will continue indefinitely until you pull power on envoy or davis >>> console. And will keep doing this maybe posting 5 to 25 records and then >>> failing. running a dump clears this up and it starts fine and goes in to >>> loop. No timeouts when it is a straight dump to the database. >>> >>> .Feb 23 09:13:39 Raspberry weewx[6019]: engine: Initializing weewx >>> version 3.8.0 >>> Feb 23 09:13:39 Raspberry weewx[6019]: engine: Using Python 2.7.13 >>> (default, Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516] >>> Feb 23 09:13:39 Raspberry weewx[6019]: engine: Platform >>> Linux-4.9.59-v7+-armv7l-with-debian-9.1 >>> Feb 23 09:13:39 Raspberry weewx[6019]: engine: Locale is 'en_US.UTF-8' >>> Feb 23 09:13:39 Raspberry weewx[6019]: engine: pid file is >>> /var/run/weewx.pid >>> Feb 23 09:13:39 Raspberry weewx[6005]: Starting weewx weather system: >>> weewx. >>> Feb 23 09:13:39 Raspberry systemd[1]: Started LSB: weewx weather system. >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Using configuration file >>> /etc/weewx/weewx.conf >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Loading station type >>> Vantage (weewx.drivers.vantage) >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: StdConvert target unit is >>> 0x1 >>> Feb 23 09:13:39 Raspberry weewx[6024]: wxcalculate: The following values >>> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, >>> dewpoint=prefer_hardware, appTemp=prefer_hardware, >>> rainRate=prefer_hardware, windrun=prefer_hardware, >>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, >>> humidex=prefer_hardware, pressure=prefer_hardware, >>> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, >>> cloudbase=prefer_hardware >>> Feb 23 09:13:39 Raspberry weewx[6024]: wxcalculate: The following >>> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS >>> Feb 23 09:13:39 Raspberry weewx[6024]: crt: service version is 0.18 >>> Feb 23 09:13:39 Raspberry weewx[6024]: crt: output goes to >>> /var/www/html/weewx/realtime.txt >>> Feb 23 09:13:39 Raspberry weewx[6024]: crt: 'None' values will be >>> displayed as NULL >>> Feb 23 09:13:39 Raspberry weewx[6024]: crt: zambretti forecast: False >>> Feb 23 09:13:39 Raspberry weewx[6024]: crt: binding is loop >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Archive will use data >>> binding wx_binding >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Record generation will be >>> attempted in 'hardware' >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Using archive interval of >>> 300 seconds (specified by hardware) >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Using binding >>> 'wx_binding' to database 'weewx.sdb' >>> Feb 23 09:13:39 Raspberry weewx[6024]: manager: Starting backfill of >>> daily summaries >>> Feb 23 09:13:39 Raspberry weewx[6024]: restx: StationRegistry: >>> Registration not requested. >>> Feb 23 09:13:39 Raspberry weewx[6024]: restx: Wunderground-PWS: Data for >>> station XXXXXXX will be posted >>> Feb 23 09:13:39 Raspberry weewx[6024]: restx: PWSweather: Posting not >>> enabled. >>> Feb 23 09:13:39 Raspberry weewx[6024]: restx: CWOP: Posting not enabled. >>> Feb 23 09:13:39 Raspberry weewx[6024]: restx: WOW: Posting not enabled. >>> Feb 23 09:13:39 Raspberry weewx[6024]: restx: AWEKAS: Posting not >>> enabled. >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Starting up weewx version >>> 3.8.0 >>> Feb 23 09:13:39 Raspberry weewx[6024]: engine: Clock error is -76303.50 >>> seconds (positive is fast) >>> Feb 23 09:13:39 Raspberry weewx[6024]: vantage: Clock set to 2018-02-23 >>> 09:13:40 CST (1519398820) >>> Feb 23 09:13:42 Raspberry weewx[6024]: manager: Added record 2018-02-22 >>> 10:45:00 CST (1519317900) to database 'weewx.sdb' >>> Feb 23 09:13:42 Raspberry weewx[6024]: manager: Added record 2018-02-22 >>> 10:45:00 CST (1519317900) to daily summary in 'weewx.sdb' >>> Feb 23 09:13:42 Raspberry weewx[6024]: restx: Wunderground-PWS: >>> Published record 2018-02-22 10:45:00 CST (1519317900) >>> Feb 23 09:13:43 Raspberry weewx[6024]: manager: Added record 2018-02-22 >>> 10:50:00 CST (1519318200) to database 'weewx.sdb' >>> Feb 23 09:13:43 Raspberry weewx[6024]: manager: Added record 2018-02-22 >>> 10:50:00 CST (1519318200) to daily summary in 'weewx.sdb' >>> Feb 23 09:13:43 Raspberry weewx[6024]: restx: Wunderground-PWS: >>> Published record 2018-02-22 10:50:00 CST (1519318200) >>> Feb 23 09:13:44 Raspberry weewx[6024]: manager: Added record 2018-02-22 >>> 10:55:00 CST (1519318500) to database 'weewx.sdb' >>> Feb 23 09:13:44 Raspberry weewx[6024]: manager: Added record 2018-02-22 >>> 10:55:00 CST (1519318500) to daily summary in 'weewx.sdb' >>> Feb 23 09:13:45 Raspberry weewx[6024]: restx: Wunderground-PWS: >>> Published record 2018-02-22 10:55:00 CST (1519318500) >>> *Feb 23 09:13:48 Raspberry weewx[6024]: vantage: DMPAFT try #1; error: >>> Time out in get_data_with_crc16* >>> Feb 23 09:14:04 Raspberry weewx[6024]: vantage: Unable to wake up console >>> Feb 23 09:14:04 Raspberry weewx[6024]: vantage: DMPAFT try #2; error: >>> Unable to wake up Vantage console >>> Feb 23 09:14:20 Raspberry weewx[6024]: vantage: Unable to wake up console >>> Feb 23 09:14:20 Raspberry weewx[6024]: vantage: DMPAFT try #3; error: >>> Unable to wake up Vantage console >>> Feb 23 09:14:21 Raspberry systemd[1]: Stopping LSB: weewx weather >>> system... >>> Feb 23 09:14:21 Raspberry weewx[6024]: engine: Terminating weewx version >>> 3.8.0 >>> Feb 23 09:14:26 Raspberry weewx[6150]: Stopping weewx weather system: >>> weewx.. >>> Feb 23 09:14:26 Raspberry systemd[1]: Stopped LSB: weewx weather system. >>> Feb 23 09:14:34 Raspberry systemd[1]: Starting LSB: weewx weather >>> system... >>> Feb 23 09:14:35 Raspberry weewx[6234]: engine: Initializing weewx >>> version 3.8.0 >>> Feb 23 09:14:35 Raspberry weewx[6234]: engine: Using Python 2.7.13 >>> (default, Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516] >>> Feb 23 09:14:35 Raspberry weewx[6234]: engine: Platform >>> Linux-4.9.59-v7+-armv7l-with-debian-9.1 >>> Feb 23 09:14:35 Raspberry weewx[6234]: engine: Locale is 'en_US.UTF-8' >>> Feb 23 09:14:35 Raspberry weewx[6234]: engine: pid file is >>> /var/run/weewx.pid >>> Feb 23 09:14:35 Raspberry weewx[6238]: engine: Using configuration file >>> /etc/weewx/weewx.conf >>> Feb 23 09:14:35 Raspberry weewx[6238]: engine: Loading station type >>> Vantage (weewx.drivers.vantage) >>> Feb 23 09:14:35 Raspberry weewx[6223]: Starting weewx weather system: >>> weewx. >>> Feb 23 09:14:35 Raspberry systemd[1]: Started LSB: weewx weather system. >>> Feb 23 09:14:51 Raspberry weewx[6238]: vantage: Unable to wake up console >>> Feb 23 09:14:51 Raspberry weewx[6238]: import of driver failed: Unable >>> to wake up Vantage console (<class 'weewx.WakeupError'>) >>> Feb 23 09:14:51 Raspberry weewx[6238]: engine: Unable to load driver: >>> Unable to wake up Vantage console >>> Feb 23 09:14:51 Raspberry weewx[6238]: **** Exiting... >>> >>> >>> >>> On Saturday, February 24, 2018 at 6:45:06 AM UTC-6, Tom Keffer wrote: >>> >>>> I don't think I am following you. What do you mean by "vantage driver >>>> fails a CRC16 error well documented?" >>>> >>>> It's hard to offer much of an opinion without seeing the log. >>>> >>>> -tk >>>> >>>> >>>> On Fri, Feb 23, 2018 at 10:04 PM, <ddu...@gmail.com> wrote: >>>> >>>>> Every time my logger gets a lot of data that hasn't been sent to weewx >>>>> because system is offline (like power outage for last 2 days), the system >>>>> comes up, vantage driver fails a CRC16 error well documented and then the >>>>> only thing you can do is manually pull all the power to the envoy and >>>>> restart weewx. it will download some data to the database and then get an >>>>> error again and exit the vantage driver. You may get and hour or 2 of >>>>> data >>>>> and then have to stop, pull power, start weewx and view log. >>>>> >>>>> >>>>> I used to have the data being pumped to CWOP and WUNDERGROUND. I >>>>> turned off CWOP and it behaved slightly better but it seems as soon as a >>>>> WUNDERGROUND record went out it would stop working pretty close to that >>>>> point. >>>>> >>>>> Today I decided to do a wee_device --dump. I'm confused why using the >>>>> exact same drivers it has no problem reading and streaming all the data in >>>>> to the database (obviously error-ing out on duplicate keys) and never gets >>>>> a CRC error. Obviously no WUNDERGROUND data is sent but the process >>>>> does >>>>> finish. If I then start weewx, it goes right in to the loop process and >>>>> doesn't fail. >>>>> >>>>> I know people have chased the USB cable, power supply (my logger is >>>>> wrapped in AC duct foil tape (including the cable) and has a 2 ferrite >>>>> ended cable. Doesn't help. Power supply is new and fine on Rpi. >>>>> >>>>> I think it may be the vantage driver and trying to pause during a push >>>>> to one of the services while downloading all this data. Can't prove that >>>>> but that is my observation. >>>>> >>>>> I modified vantage.py today to allow me to not have to say yes to the >>>>> dump command with a --dumpauto option. I took weewx out of rc.d and run a >>>>> job a startup using cron that calls wee_device --dumpauto and then >>>>> immediately starts weewx. >>>>> >>>>> While that is the backstory, what am I missing by taking this approach >>>>> that at least has the system back up and running when the power goes down >>>>> or multiple hours of data end up on the logger without weewx running? >>>>> >>>>> I get I am probably not getting data to wunderground for all those >>>>> periods. it is in the database. not sure what else to try. >>>>> >>>>> -- >>>>> 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+...@googlegroups.com. >>>>> 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 weewx-user+...@googlegroups.com. >>> 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 weewx-user+unsubscr...@googlegroups.com. > 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
