Page 1 of 2
Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 8:57 am
by Adrian Hudson
Hi Steve,
Looks like you are updating the clock in the Davis every few minutes between 04:00 and 05:00. It further looks like setting the clock makes the Davis throw away its wind averages for a few seconds - but thats to be expected I guess.
See attached log file
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 9:08 am
by Adrian Hudson
oh, and Twitter fell over in a heap at 05:00:07 - I guess because of the wind averages being zero or similar or 255 - due to the clock update at 04:59:39 still causing the Console to be in a bit of a quiver...
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 9:12 am
by steve
My clock didn't get updated at all - I'll check the code.
Twitter updates using a twitter.txt file are broken in 3015.
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 9:18 am
by mcrossley
I had the same, every minute between 04:00 and 05:00
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 10:10 am
by Adrian Hudson
mcrossley wrote:I had the same, every minute between 04:00 and 05:00
Did you get all the 255's as well?
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 10:34 am
by mcrossley
Nope.
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 12:44 pm
by Adrian Hudson
mcrossley wrote:Nope.
Do you have cumulus set to calculate the average or do you use the console figure?
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 1:03 pm
by mcrossley
Adrian Hudson wrote:Do you have cumulus set to calculate the average or do you use the console figure?
I use the console average.
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 5:28 pm
by Adrian Hudson
mcrossley wrote:Adrian Hudson wrote:Do you have cumulus set to calculate the average or do you use the console figure?
I use the console average.
Now, there is really odd! Same setup, same firmware - my console throws its hands in the air for a few seconds after time update - returns 255 for wind average - yours doesn't.
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 5:31 pm
by mcrossley
Yep, odd, I wonder if Steve (or anybody else running a VP2 and b3015) saw the 255 'issue'?
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 5:38 pm
by steve
No, I haven't had any, and I'm using the console average. And I've been setting the clock quite a bit just now, fixing the multiple/no setting bug.
Re: Davis console clock update at 04:00hrs
Posted: Tue 27 Jan 2015 5:49 pm
by n9mfk
I did not see the 255 here
beau
Re: Davis console clock update at 04:00hrs [fixed]
Posted: Wed 28 Jan 2015 8:07 pm
by Adrian Hudson
Fixed. Updated fine at 040017 this morning... once only.
Re: Davis console clock update at 04:00hrs
Posted: Wed 28 Jan 2015 8:47 pm
by steve
Did the wind speed drop out again when it set the clock?
Re: Davis console clock update at 04:00hrs
Posted: Mon 21 Sep 2015 5:08 am
by MCQ
I have an RPi 2 running MX b3030 connected to a Davis VP2 Console with FW 3.15 and a USB Datalogger.
My Davis Console displays a time 37 mins behind the current time.
My RPi has the correct time set.
I have the "Synchronise station clock" checked in the ini.
On startup:
2015-09-20 17:17:41.254 ========================== Cumulus MX starting ==========================
2015-09-20 17:17:41.276 Command line: /home/pi/CumulusMX//CumulusMX.exe -port 8998
2015-09-20 17:17:41.278 Cumulus MX v.3.0.0 build 3030
2015-09-20 17:17:41.286 Platform: Unix
2015-09-20 17:17:41.288 OS version: Unix 4.1.6.7
2015-09-20 17:17:41.288 Current culture: English (United States)
2015-09-20 17:17:41.290 Directory separator=/ Decimal separator=. List separator=,
2015-09-20 17:17:41.291 Date separator=/ Time separator=:
2015-09-20 17:17:41.291 Standard time zone name: PST
2015-09-20 17:17:41.291 Daylight saving time name: PDT
2015-09-20 17:17:41.292 Daylight saving time? True
2015-09-20 17:17:41.294 9/20/2015 5:17:41 PM
2015-09-20 17:17:44.673 Setting console time
2015-09-20 17:17:44.774 Wait for ACK...
2015-09-20 17:17:44.845 ACK received
2015-09-20 17:17:44.848 Wait for ACK...
2015-09-20 17:17:44.854 ACK received
2015-09-20 17:17:44.860 Reading console time
2015-09-20 17:17:46.263 2E-11-11-14-09-73-1D-7C
2015-09-20 17:17:46.263 Console clock: 9/20/2015 5:17:46 PM
So, it looks like Cumulus is setting the console time and reporting that it was set correctly, however the console still displays a time 37 minutes behind the current time.
Shouldn't the console display the same time as set by Cumulus?