Bud, Are you posting to CWOP every 60 seconds? I'm pretty sure that they don't want anything more then every 5 minutes.
Dave-KB1PVH Sent from my Galaxy S7 On May 5, 2017 8:24 PM, "Bud Talbot" <[email protected]> wrote: > Archive interval is set to 60 sec. It seems to be working now and feeding > all data to CWOP. Here's the relevant part of the log: > > >>>>>>>> > May 5 18:20:03 raspberrypi weewx[15549]: engine: Using archive interval > of 60 seconds (specified by hardware) > May 5 18:20:03 raspberrypi weewx[15549]: engine: Use LOOP data in hi/low > calculations: 1 > May 5 18:20:03 raspberrypi weewx[15549]: manager: Daily summary version > is 2.0 > May 5 18:20:03 raspberrypi weewx[15549]: engine: Using binding > 'wx_binding' to database 'weewx.sdb' > May 5 18:20:03 raspberrypi weewx[15549]: manager: Starting backfill of > daily summaries > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.engine.StdArchive > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.restx.StdStationRegistry > May 5 18:20:03 raspberrypi weewx[15549]: restx: StationRegistry: > Registration not requested. > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.restx.StdStationRegistry > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.restx.StdWunderground > May 5 18:20:03 raspberrypi weewx[15549]: restx: Wunderground-RF: Data for > station KCOLOUIS4 will be posted > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.restx.StdWunderground > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.restx.StdPWSweather > May 5 18:20:03 raspberrypi weewx[15549]: restx: PWSweather: Posting not > enabled. > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.restx.StdPWSweather > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.restx.StdCWOP > May 5 18:20:03 raspberrypi weewx[15549]: restx: CWOP: Data for station > W0RMT will be posted > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.restx.StdCWOP > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.restx.StdWOW > May 5 18:20:03 raspberrypi weewx[15549]: restx: WOW: Posting not enabled. > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.restx.StdWOW > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.restx.StdAWEKAS > May 5 18:20:03 raspberrypi weewx[15549]: restx: AWEKAS: Posting not > enabled. > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.restx.StdAWEKAS > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.engine.StdPrint > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.engine.StdPrint > May 5 18:20:03 raspberrypi weewx[15549]: engine: Loading service > weewx.engine.StdReport > May 5 18:20:03 raspberrypi weewx[15549]: engine: Finished loading service > weewx.engine.StdReport > May 5 18:20:03 raspberrypi weewx[15549]: engine: Starting up weewx > version 3.7.1 > May 5 18:20:03 raspberrypi weewx[15549]: engine: Station does not support > reading the time > May 5 18:20:03 raspberrypi weewx[15549]: manager: Daily summary version > is 2.0 > May 5 18:20:03 raspberrypi weewx[15549]: manager: Daily summary version > is 2.0 > May 5 18:20:04 raspberrypi weewx[15549]: fousb: get 1675 records since > 2017-05-06 00:19:30 > May 5 18:20:04 raspberrypi weewx[15549]: fousb: synchronising to the > weather station (quality=1) > May 5 18:20:05 raspberrypi weewx[15549]: fousb: status {'unknown': 0, > 'lost_connection': 0, 'rain_overflow': 0} (0) > May 5 18:21:00 raspberrypi weewx[15549]: fousb: new ptr: 0069c0 (0069b0) > May 5 18:21:00 raspberrypi rsyslogd-2007: action 'action 17' suspended, > next retry is Fri May 5 18:22:30 2017 [try http://www.rsyslog.com/e/2007 > ] > May 5 18:21:00 raspberrypi weewx[15549]: fousb: setting station clock > 0.321794 > May 5 18:21:00 raspberrypi weewx[15549]: fousb: log synchronised > May 5 18:21:00 raspberrypi weewx[15549]: fousb: packet timestamp is > 00:21:00 > May 5 18:21:00 raspberrypi weewx[15549]: fousb: synchronised to > 2017-05-06 00:21:00 for ptr 0x69b0 > May 5 18:21:00 raspberrypi weewx[15549]: fousb: found 2 archive records > May 5 18:21:00 raspberrypi weewx[15549]: fousb: returning archive record > 1494030000 > May 5 18:21:00 raspberrypi weewx[15549]: manager: Added record 2017-05-05 > 18:20:00 MDT (1494030000) to database 'weewx.sdb' > May 5 18:21:00 raspberrypi weewx[15549]: manager: Added record 2017-05-05 > 18:20:00 MDT (1494030000) to daily summary in 'weewx.sdb' > May 5 18:21:00 raspberrypi weewx[15549]: restx: CWOP: record 2017-05-05 > 18:20:00 MDT (1494030000) is stale (60 > 60). > May 5 18:21:00 raspberrypi weewx[15549]: fousb: returning archive record > 1494030060 > May 5 18:21:00 raspberrypi weewx[15549]: manager: Added record 2017-05-05 > 18:21:00 MDT (1494030060) to database 'weewx.sdb' > May 5 18:21:00 raspberrypi weewx[15549]: manager: Added record 2017-05-05 > 18:21:00 MDT (1494030060) to daily summary in 'weewx.sdb' > May 5 18:21:00 raspberrypi weewx[15549]: engine: Starting main packet > loop. > May 5 18:21:00 raspberrypi weewx[15549]: fousb: avoid 2.48599004745 > May 5 18:21:01 raspberrypi weewx[15549]: restx: CWOP: Connected to server > rotate.aprs.net:14580 > May 5 18:21:01 raspberrypi weewx[15549]: restx: CWOP: Published record > 2017-05-05 18:21:00 MDT (1494030060) > May 5 18:21:03 raspberrypi weewx[15549]: fousb: station status > {'unknown': 0, 'lost_connection': 0, 'rain_overflow': 0} (0) > May 4 15:52:31 raspberrypi weewx[1887]: restx: CWOP: Published record > 2017-05-04 15:52:00 MDT (1493934720) > > > > On Thursday, May 4, 2017 at 5:08:22 PM UTC-6, Tom Keffer wrote: >> >> I'm seeing plenty of packets, but not necessarily all types: >> http://www.findu.com/cgi-bin/wxpage.cgi?call=W0RMT!Louisville&last=12 >> >> What is your archive interval? With partial record stations, like the >> WS-2080, if it's too short, the archive record may not have accumulated all >> types. >> >> Set debug=1, restart weewx, post the log from the startup, through the >> first couple of archive records. >> >> -tk >> >> >> On Thu, May 4, 2017 at 2:59 PM, Bud Talbot <[email protected]> wrote: >> >>> Folks- >>> >>> new user here, so bear with me. I've just got weewx up and running on my >>> raspberry pi, interfaced with an Ambient WS-2080. I'm switching over to >>> this from years on a desktop PC to save energy and overhead. I've been >>> publishing my WX data to Wunderground and the APRS network for a long time >>> (14+ yrs on CWOP). >>> >>> I'm having trouble with CWOP- it's not uploading even though it says it >>> is. Here's the relevant section of my config: >>> >>> post_interval = 600 >>> log_success = True >>> log_failure = True >>> server_list = rotate.aprs.net:14580, rotate.aprs2.net:14580, >>> cwop.aprs.$ >>> enable = true >>> station = W0RMT >>> passcode = XXXX >>> >>> And here's what I see in the log: >>> >>> May 4 15:52:31 raspberrypi weewx[1887]: restx: CWOP: Published record >>> 2017-05-04 15:52:00 MDT (1493934720) >>> >>> Yet no upload has occurred. Any ideas where to start looking? My >>> Wunderground uploads are finally looking decent (KCOLOUIS4). >>> >>> thanks, >>> >>> Bud >>> >>> On Wednesday, February 10, 2016 at 3:11:02 PM UTC-7, Tom Keffer wrote: >>>> >>>> This does not surprise me. While the CWOP protocol is not very well >>>> documented, the driver has been around for about 5 years, with very few >>>> problems. >>>> >>>> Let us know what you find. Always something to learn! >>>> >>>> -tk >>>> >>>> On Wed, Feb 10, 2016 at 12:04 PM, erbenton07 <[email protected]> >>>> wrote: >>>> >>>>> I'm still using suse, yeh. I found something interesting tho. When I >>>>> ran my network test i discovered that dropouts increased dramatically. >>>>> Even >>>>> relatively idle i get a dropout every minute or so. So... something in my >>>>> network appears to be not up to snuff. Not sure how to approach diagnosing >>>>> the cause of dropouts, google is some help, but still need to understand >>>>> it >>>>> better. >>>>> >>>>> -- >>>>> 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]. >>> 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. > -- 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.
