Cumulus Support

@Steve...here now using a buffered cable versus a regular serial cable....should I try going back to the serial cable?

I do not use tweeter (well not on any social sites these days)...well I see a V.28...will give that a try...just copying over the exe and pdb file for now eh?

I don't know what a buffered cable is?

Just the exe and the pdb have changed between 3027 and 3028, yes. But it must be easier just to unzip the whole thing and not worry about what's changed, surely?

Updated to V.28 this morning...Cumulus Mx 3.0.0 b3028 (from web GUI).....looks good....

FYI...yesterday WUN sent me a tickle about the weather station being down which had me looking....

Today just renamed the two V.25 files and copied over the exe and pdb files ...

2015-08-06 12:53:29.784 ========================== Cumulus MX starting ==========================
2015-08-06 12:53:29.796 Command line: /CumulusMX/CumulusMX.exe
2015-08-06 12:53:29.797 Cumulus MX v.3.0.0 build 3028
2015-08-06 12:53:29.806 Platform: Unix
2015-08-06 12:53:29.808 OS version: Unix 3.18.11.7
2015-08-06 12:53:29.808 Current culture: English (United States)
2015-08-06 12:53:29.810 Directory separator=/ Decimal separator=. List separator=,
2015-08-06 12:53:29.810 Date separator=/ Time separator=:
2015-08-06 12:53:29.811 Standard time zone name: CST
2015-08-06 12:53:29.811 Daylight saving time name: CDT
2015-08-06 12:53:29.814 Daylight saving time? True
2015-08-06 12:53:29.816 8/6/2015 12:53:29 PM
2015-08-06 12:53:29.818 Data path = data/
2015-08-06 12:53:29.833 Creating backup folder backup/20150806125329/
2015-08-06 12:53:29.920 Reading Cumulus.ini file
2015-08-06 12:53:30.002 ASM=10 AST=00:10:00
2015-08-06 12:53:30.008 Cumulus start date: Sunday, June 14, 2015
2015-08-06 12:54:29.912 Starting 1-minute timer
2015-08-06 12:54:29.922 Attempting realtime FTP connect
2015-08-06 12:54:31.032 Starting Realtime timer, interval = 30 seconds
2015-08-06 12:56:17.766 Reading reception stats
2015-08-06 12:57:13.520 !!! loop data not received
2015-08-06 12:57:13.520 Reading reception stats
2015-08-06 12:57:13.825 Array index is out of range.
2015-08-06 12:57:34.838 !!! loop data not received
2015-08-06 12:57:34.838 Reading reception stats
2015-08-06 12:57:56.150 !!! loop data not received
2015-08-06 12:57:56.150 Reading reception stats
2015-08-06 12:58:17.462 Reading reception stats
2015-08-06 12:58:17.763 Array index is out of range.
2015-08-06 13:00:00.941 Hour changed:13
2015-08-06 13:00:00.941 Calculating sunrise and sunset times
2015-08-06 13:00:00.942 Sunrise: 05:49:19
2015-08-06 13:00:00.943 Sunset : 20:03:01
2015-08-06 13:00:00.944 Tomorrow sunrise: 05:50:20
2015-08-06 13:00:00.944 Tomorrow sunset : 20:01:47
2015-08-06 13:00:00.982 Writing log entry for 8/6/2015 1:00:00 PM
2015-08-06 13:00:00.989 Written log entry for 8/6/2015 1:00:00 PM
2015-08-06 13:00:00.996 Writing today.ini, LastUpdateTime = 8/6/2015 1:00:00 PM raindaystart = 13.75 rain counter = 13.75
2015-08-06 13:00:00.999 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('15-08-06 13:00',81.6,57,64.9,2.4,10.0,23,0.00,0.00,29.912,13.75,71.0,50,1.0,81.6,83.4,0.0,0,0.000,0.000,85.5,933,0.0,23,0.00,0.00,'NNE','NNE')
2015-08-06 13:00:01.006 MySQL: 1 rows were affected.
2015-08-06 13:00:03.672 Reading reception stats
2015-08-06 13:01:41.685 Reading reception stats
2015-08-06 13:03:31.040 Updating CWOP



@Steve...what is the loop data not received in the diagnostic logs about?

pete_c wrote:@Steve...what is the loop data not received in the diagnostic logs about?

It's not getting complete packets of data from the station. This is with the logger directly connected to the Pi, and no other program trying to use the same logger at the same, yes?

and no other program trying to use the same logger at the same, yes?

Yes it is a single buffered serial cable going from the Davis Console to the RPi2.

I also have buffered USB cable and a direct unbuffered serial cable to play with.

Looking at mxdiags stuff do not see this now...such that it only occurred when starting CumulusMX.

2015-08-06 13:50:00.108 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('15-08-06 13:50',82.4,54,64.1,4.5,13.0,349,0.00,0.00,29.900,13.75,71.0,49,8.0,82.4,83.9,0.0,0,0.000,0.000,84.8,908,0.0,28,0.00,0.00,'N','NNE')
2015-08-06 13:50:00.116 MySQL: 1 rows were affected.
2015-08-06 13:50:41.882 Reading reception stats
2015-08-06 13:52:20.010 Reading reception stats
2015-08-06 13:53:57.954 Reading reception stats
2015-08-06 13:55:35.887 Reading reception stats
2015-08-06 13:57:13.827 Reading reception stats
2015-08-06 13:57:31.033 Updating CWOP
2015-08-06 13:50:00.108 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('15-08-06 13:50',82.4,54,64.1,4.5,13.0,349,0.00,0.00,29.900,13.75,71.0,49,8.0,82.4,83.9,0.0,0,0.000,0.000,84.8,908,0.0,28,0.00,0.00,'N','NNE')
2015-08-06 13:50:00.116 MySQL: 1 rows were affected.
2015-08-06 13:50:41.882 Reading reception stats
2015-08-06 13:52:20.010 Reading reception stats
2015-08-06 13:53:57.954 Reading reception stats
2015-08-06 13:55:35.887 Reading reception stats
2015-08-06 13:57:13.827 Reading reception stats
2015-08-06 13:57:31.033 Updating CWOP
2015-08-06 13:58:51.955 Reading reception stats
2015-08-06 14:00:00.131 Hour changed:14
2015-08-06 14:00:00.131 Calculating sunrise and sunset times
2015-08-06 14:00:00.133 Sunrise: 05:49:19
2015-08-06 14:00:00.133 Sunset : 20:03:01
2015-08-06 14:00:00.134 Tomorrow sunrise: 05:50:20
2015-08-06 14:00:00.134 Tomorrow sunset : 20:01:47
2015-08-06 14:00:00.148 Writing log entry for 8/6/2015 2:00:00 PM
2015-08-06 14:00:00.150 Written log entry for 8/6/2015 2:00:00 PM
2015-08-06 14:00:00.157 Writing today.ini, LastUpdateTime = 8/6/2015 2:00:00 PM raindaystart = 13.75 rain counter = 13.75
2015-08-06 14:00:00.160 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('15-08-06 14:00',80.2,56,63.1,5.8,13.0,13,0.00,0.00,29.900,13.75,71.2,49,4.0,80.2,81.6,0.0,0,0.000,0.000,81.4,898,0.0,42,0.00,0.00,'NNE','NE')
2015-08-06 14:00:00.166 MySQL: 1 rows were affected.
2015-08-06 14:00:29.905 Reading reception stats

The start of the diags file looks very odd, it doesn't seem to be reading the archive data, and there are other items not there that it should have logged when it started up. I wonder if I've broken some more of the Davis USB/serial code. I'll check the code...

I still don't know what a buffered serial cable is. Do Davis say that their stations should work OK with one of those? If 'buffered' means that it has memory which holds the serial data, it is possible that the problem at start up was due to data being left over from when you closed down Cumulus, and thus arriving unexpectedly when you started it up again.

I still don't know what a buffered serial cable is.

Yup the Davis standard USB and serial cables are here. Both Davis logger cables buffer the serial data from the Davis Console.

Standard Data Logger. Log and store data, even when the data logger is not connected to your PC. Transfer the data as often as you like, or leave the software running to transfer it automatically each day.

WeatherLink®, Windows, USB

http://www.davisnet.com/weather/product ... m=06510USB

WeatherLink®, Windows, Serial Port

http://www.davisnet.com/weather/product ... m=06510SER

Personally I just have left the data cable plugged in and have not removed it or shut down (powered off the Davis Console)

Should I power off the Davis Console (remove batteries and power supply connection) before I start up CumulusMX?

Do Davis say that their stations should work OK with one of those?


Yes either serial or USB.

If 'buffered' means that it has memory which holds the serial data, it is possible that the problem at start up was due to data being left over from when you closed down Cumulus, and thus arriving unexpectedly when you started it up again.

I do not know; but I guess it could be relating to a catch up or read of the buffered data. I noticed with Cumulus 1 if I turned on the option to read the buffered data; it would take a very long time (many minutes) to start so I disabled it. I never mentioned it though cuz it wasn't an issue for me.
It would be nice though to see how much of the buffered Davis data logger cable records CumulusMX reads while starting (kind of a neato way to get metrics I suppose).

Unrelated to OP...and just posting here....been running here a mono based application relating to my irrigation on a dockstar debian for about 3 years now. It does have a shutdown button on it...I can also shut down the service via ssh if I want....
Well too running some automation software in Mono on the RPi2 and it also can be shut down via SSH or a button...

You should normally have the option 'use data logger' selected, so that Cumulus (either v1 or MX) reads the logger data when it starts up, to catch up from when it closes down again. This is nothing to do with the type of serial cable, the data is stored in the logger. This is just the normal way that Davis stations operate. If it takes a long time to start up, then you probably have the issue described in the FAQ - http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

You should normally have the option 'use data logger' selected

Thank you Steve.

Where is the use data logger option in CumulusMX?

I see a log interval setting but no use data logger option.

Well I do see it. I have attached a picture. Do I just check this box marked data logging ?

Side Note #1: Reception is spelled wrong here. (IE: Read Davis Reception Stats)
Side Note #2 and request:

I have been moving towards using mostly Linux here and using Wine or Wintel VB's for Windows stuff (but have been playing with Windows 10). I am shutting down most if not my Wintel servers here. I am also using hardware serial servers to access my hardware that is serially connected. That said I was going to manually use a serial console to set the interval via a networked serial port connection and noticed some person wrote a little plug n play utility to do this.

Can I post or attach the serial com utility with instructions to set the Davis datalogger interval manually?

pete_c wrote:You should normally have the option 'use data logger' selected

Thank you Steve.

Where is the use data logger option in CumulusMX?

I see a log interval setting but no use data logger option.

Hi Pete

At least it is present in the Cumulus.ini file Maybe "nano" can solve your problem

Thank you Jan.

So I see it on by default in the INI file. Personally like nano way better than Vi.
So now switching the serial connection from the RPi2 to the network serial server to utilize the serial interval set application. Way easier as I can do this from any part of my network on any computer.

I set my interval to 10. Not sure if that is optimal. Terminal commands are very basic. Here are the terminal commands to set the interval.
1. Install your serial cable in the console as per the Davis instructions. (unplug the mains supply, remove batteries.)
2. Connect the Serial to serial port. (here utilized a virtual serial server port)
3. Figure out which port your serial cable is on.
4. Open terminal program
5. Move the Com port indicator the port that you found your cable on, and hit the "open" button.
6. In the "Message" box type "TEST" (IN CAPITALS) and hit send, you may need to do this a few times to wake the console up. Once you get characters in the "received Messages" box you are ready to set the interval!
7. Using the drop down in the message window hit the "CLRLOG" message and hit send. This will clear any previous data from the logger cable.
8. Now set the interval that you require, use the message drop down to select "SETPER" and the parameter drop down to select the value, then hit send. Remember to set this as the same value in Cumulus.
9. Then use the message drop down to select "START" and hit send.
10. Close the Com port, and then the set up program and your serial logger cable is running.
Shutdown CumulusMX and restarted it and looked at mxdiags. Looks good.

2015-08-07 10:10:55.249 Rainthismonth from dayfile.txt: 0.5
2015-08-07 10:10:55.249 Rainthisyear from dayfile.txt: 6.76
2015-08-07 10:10:55.412 Station type = Davis
2015-08-07 10:10:55.412 LOOP2 enabled
2015-08-07 10:10:55.412 Serial device = /dev/ttyUSB0
2015-08-07 10:10:55.426 Connected OK
2015-08-07 10:10:55.430 Reading firmware version
2015-08-07 10:10:55.747 FW version = 3.0
2015-08-07 10:10:55.750 Reading reception stats
2015-08-07 10:10:56.051 7260 1434 0 28 368
2015-08-07 10:10:56.053 Last update time = 8/7/2015 10:00:00 AM
2015-08-07 10:10:56.058 Setting console time
2015-08-07 10:10:56.158 Wait for ACK...
2015-08-07 10:10:56.167 ACK received
2015-08-07 10:10:56.169 Wait for ACK...
2015-08-07 10:10:56.175 ACK received
2015-08-07 10:10:56.180 Reading console time
2015-08-07 10:10:57.385 39-0A-0A-07-08-73-0B-3F
2015-08-07 10:10:57.386 Console clock: 8/7/2015 10:10:57 AM
2015-08-07 10:10:57.386 Start reading archive data
2015-08-07 10:10:57.390 Reading archive data
2015-08-07 10:10:57.391 Loading last N hour data from data logs: 8/7/2015 10:00:00 AM
2015-08-07 10:10:57.599 Loaded 7 entries to last hour data list
2015-08-07 10:10:57.771 Loaded 19 entries to last 3 hour data list
2015-08-07 10:10:57.950 Loaded 145 entries to last 24 hour data list
2015-08-07 10:10:59.198 Loaded 966 entries to recent data list
2015-08-07 10:10:59.226 Loaded 31 entries to daily data list
2015-08-07 10:10:59.276 Get Archive Data
2015-08-07 10:10:59.277 Rollover hour = 0
2015-08-07 10:10:59.278 Last Archive Date: 8/7/2015 10:00:00 AM
2015-08-07 10:10:59.278 Date: 7943
2015-08-07 10:10:59.278 Time: 1000
2015-08-07 10:10:59.379 Sending DMPAFT
2015-08-07 10:10:59.389 Received response to DMPAFT, sending date and time
2015-08-07 10:10:59.390 07-1F-E8-03-97-07
2015-08-07 10:10:59.390 Wait for ACK...
2015-08-07 10:10:59.398 ACK received
2015-08-07 10:10:59.399 Waiting for response
2015-08-07 10:10:59.423 625 web tags initialised
2015-08-07 10:10:59.444 HTML root path = /CumulusMX/interface
2015-08-07 10:10:59.601 Response: 01 00 04 00 BA 70
2015-08-07 10:10:59.601 Reading data: 1 pages , offset = 4
2015-08-07 10:10:59.717 Starting web socket server on port 8002
2015-08-07 10:10:59.811 Loaded archive record for Page=0 Record=4 Timestamp=8/7/2015 10:10:00 AM
2015-08-07 10:10:59.811 Processing archive record for 8/7/2015 10:10:00 AM
2015-08-07 10:10:59.874 Page=0 Record=4 Timestamp=8/7/2015 10:10:00 AM
2015-08-07 10:10:59.890 Writing log entry for 8/7/2015 10:10:00 AM
2015-08-07 10:10:59.911 Written log entry for 8/7/2015 10:10:00 AM
2015-08-07 10:10:59.932 Writing today.ini, LastUpdateTime = 8/7/2015 10:10:00 AM raindaystart = 13.75 rain counter = 13.75
2015-08-07 10:10:59.972 Creating WU URL #1
2015-08-07 10:10:59.978 Get Archive Data
2015-08-07 10:10:59.979 Rollover hour = 0
2015-08-07 10:10:59.979 Last Archive Date: 8/7/2015 10:10:00 AM
2015-08-07 10:10:59.979 Date: 7943
2015-08-07 10:10:59.979 Time: 1010
2015-08-07 10:11:00.079 Sending DMPAFT
2015-08-07 10:11:00.086 Received response to DMPAFT, sending date and time
2015-08-07 10:11:00.086 07-1F-F2-03-7B-BF
2015-08-07 10:11:00.087 Wait for ACK...
2015-08-07 10:11:00.095 ACK received

Added a found dataloggertimesynceditor program which helps and is quick.

I consciously removed the option from the setup screen in MX (still accessible by editing Cumulus.ini) because I was tiring of the number of people using Cumulus 1 who had turned it off for some reason and then were posting that there were gaps in their data.

Thank you Steve.

With Cumulus 1 I never saw any gaps in data and assumed it was me and my set up.

Just really the time lag was all I saw.

I never really paid attention to the option thinking it was some default non-adjustable option.

Looks to be working fine now and it was an easy and quick adjustment.

Yup; here one year purchased a little bicycle for my daughter many many years ago for Christmas. It came in a box all disassembled. I wanted to assemble it and place it under the Christmas tree Christmas Eve.

Well, decided to assemble it without reading the instructions. That was a mistake and it took that much longer to assembly it correctly by not reading the instructions on first try; then reading the instructions on 2nd try.

It's been many many years now and still today I haven't learned to read instructions.

We IT Techs always said RTFM.

Updated this post.

https://cumulus.hosiene.co.uk/viewtopic.p ... 77#p109777