Version 4.0 b4022 Spike Setting Issues

[rogerthn]

i hope that this is an appropriate topic?

Version 4.0 b4022 did send an alert E-mail as below on startup

A Cumulus MX alarm has been triggered.
A data spike from your weather station has been suppressed.
Last message: Temp difference greater than spike value - NewVal=18.9 OldVal=999.0 SpikeTempDiff=9.0

Temp on console was 0.0
Enclosing ServiceConsoleLog, MXdiag and Cumulus.ini

[water01]

OK I had this happen and was busy posting it when I deleted the Version 4 Topic.

You need to look in Settings > Calibrations > Outdoor Temperature and change Spike Removal to the default 999.

In one case of my three running versions it did this because that setting was set to 6 instead of 999.

I thought I had made a mistake in reporting it as it did not happen on Synology NAS or my Windows 11 install only on the Windows 10 and it was then that I deleted the Topic!!!

[rogerthn]

Hence, change 9 below to 999 before the upgrade should do the trick?

Screenshot 2024-05-11 170902.png

But I do find it a bit strange that actions like this is needed when upgrading from RC b4021 to 4022

[mcrossley]

Hence, change 9 below to 999 before the upgrade should do the trick

But I do find it a bit strange that actions like this is needed when upgrading from RC b4021 to 4022

It's a problem in my spike handling "improvements", normally if the previous value is 999 the spike difference will be ignored, an extra 9 snuck in and it was comparing the previous value to 9999

So normally your spike value of 9.0 would be OK.

I'll have to push a patch out to fix this.

[rogerthn]

OK and THANKS for your efforts!

[delleray]

Hi,

did the removal of temp spike setting which fixed 0 temp.

FYI if the pressure value for spike removal is not 9999 then pressure shows 0 in the dahboard.


I had to revert since my error log shows virtually all my datafile has duplicate warnings as shown here.

2024-05-14 10:29:25 - ERROR: Duplicate entry in dayfile for 01/01/0001

a sample of entries in my dayfile are below.

23/06/2009,0,0,00:00:00,10.5,23:55:00,27.4,16:35:00,1026.1,19:20:00,1028.1,14:00:00,0,00:00:00,0,21,0,0,00:00:00,34,16:45:00,74,23:50:00,0,0,26.9,16:35:00,27.6,16:35:00,9.6,23:55:00,0,00:00:00,10.5,23:55:00,12.3,14:35:00,6,23:55:00,90,0,2.7,0,00:00:00,0,00:00:00
24/06/2009,8,132,19:20:00,7.8,03:15:00,27.2,14:35:00,1018.8,23:40:00,1026.9,00:00:00,0,00:00:00,0,17.3,41.2,4,19:25:00,38,15:05:00,87,05:15:00,0,0,27,14:35:00,28,14:35:00,6.8,03:15:00,0,00:00:00,7.8,03:15:00,12.6,07:50:00,5.3,01:15:00,140,1,0,0,00:00:00,0,00:00:00
.....
20/09/2018,1,90,00:00:00,12.3,06:30:00,19.6,16:20:00,997,23:40:00,1014.3,00:40:00,3.6,03:40:00,3.6,16,0,0,00:00:00,62,16:30:00,100,07:30:00,0,0,19.6,16:20:00,20.3,15:30:00,12.9,06:30:00,0,00:00:00,12.3,06:30:00,16.8,12:50:00,11.7,06:30:00,90,2.3,0,0,00:00:00,0,00:00:00
21/09/2018,1,225,21:20:00,9.6,07:21:00,18,12:04:00,994.7,01:36:00,1018.1,23:43:00,0,00:00:00,0,13.7,0,0,00:00:00,38,12:10:00,91,02:22:00,0,0,18,12:04:00,18.9,00:39:00,8.6,07:21:00,0,00:00:00,9.6,07:21:00,14.9,01:29:00,2.5,12:26:00,0,4.6,0,0,00:00:00,0,00:00:00
......

10/05/24,4,67,17:48,8.8,05:37,24.4,13:36,1019.3,17:52,1022.4,00:07,0.0,00:00,0.0,16.6,17.4,1,17:52,56,14:23,93,05:05,0.00,0.0,24.4,13:36,26.2,13:35,8.3,05:37,0.0,00:00,8.8,05:37,16.6,13:35,7.7,05:37,109,3.3,1.6,0,00:00,0.0,00:00,26.1,13:35,8.8,05:37,29.2,13:35,1915.2,0.0,00:00
11/05/24,5,67,13:44,6.9,05:19,23.6,15:39,1016.0,23:54,1021.1,00:12,0.0,00:00,0.0,15.1,25.7,1,13:47,55,16:02,95,06:00,0.00,0.0,23.6,15:39,24.8,15:39,6.0,05:19,0.0,00:00,6.9,05:19,16.5,13:55,3.3,21:23,108,4.3,1.1,0,00:00,0.0,00:00,24.8,15:39,6.9,05:19,28.0,13:55,1915.3,0.0,00:00
12/05/24,5,135,15:57,9.3,04:36,26.3,14:33,1006.3,22:00,1016.3,00:01,0.0,00:00,0.0,12.7,22.9,1,15:14,50,15:54,94,04:00,0.00,0.0,26.3,14:33,29.4,15:16,-3.5,17:25,0.0,00:00,9.3,04:36,22.2,15:16,-8.9,17:26,130,7.5,1.9,0,00:00,0.0,00:00,28.3,15:16,0.0,17:25,34.6,15:16,1921.8,0.0,00:00
13/05/24,8,180,15:20,0.0,00:00,0.0,00:00,1001.0,23:30,1006.5,00:00,0.0,00:00,0.0,0.0,9.6,0,15:20,66,15:30,94,03:50,0.00,0.0,0.0,00:00,-2.1,03:50,-2.9,15:20,0.0,00:00,0.0,00:00,-0.9,03:50,-5.6,15:30,213,18.3,0.0,0,00:00,0.0,00:00,0.0,00:00,0.0,00:00,0.0,00:00,1945.8,0.0,00:00

any ideas ?

[mcrossley]

Please post the MXdiags file and the dayfile.txt it was running against.

[delleray]

Please post the MXdiags file and the dayfile.txt it was running against.

R

[mcrossley]

Your dayfile is really malformed, have you edited it in Excel or something like that?

All the dates in the format "dd/mm/yyyy", the year should only be two digits.
All the times are in the form "hh:mm:ss", they should be just hh:mm

Also, the number of entries on each row varies tremendously, like this:

Code: Select all

18/07/2009,14,135,08:39:00,12.8,00:00:00,23.8,13:30:00,1004,00:02:00,1009,23:10:00,3.6,03:02:00,0.3,17.2,129.4,,,,,00:00:00
19/07/2009,15,110,11:55:00,10.4,03:15:00,21.8,12:40:00,1007.4,18:25:00,1010.4,23:50:00,18,21:55:00,12,15.6,382.2,10,16:20:00,55,12:40:00,89,23:30:00,0,0,21.8,12:40:00,17.9,12:35:00,9.5,04:00:00,0,00:00:00,10.4,03:15:00,14.3,17:40:00,8.1,03:15:00,96,2.7,0,0,00:00:00,0,00:00:00
21/07/2009,14,180,19:19:00,9.7,00:14:00,24.2,15:47:00,1001.5,22:50:00,1012.9,00:00:00,3.6,07:42:00,0.3,16.8,53.9,,,,,00:00:00
22/07/2009,21,93,11:20:00,11.9,05:25:00,24.9,16:05:00,999.7,19:50:00,1001.6,00:00:00,3.6,16:20:00,0.3,18,498.9,13,14:45:00,45,15:05:00,90,04:35:00,0,0,24.9,16:05:00,20.3,16:05:00,10.6,05:45:00,0,00:00:00,11.9,05:25:00,13.8,07:50:00,9.5,23:30:00,90,0.3,0,0,00:00:00,0,00:00:00

[delleray]

Thanks,

OOOps

Yes edited due to station crashes causing issues in earlier MX versions which produced duplicate and erroneous entries in historic files, but more recently using the console web editors. My better half is better at spotting issues in past records.

I will change those in the working version 3 dayfile.txt and revert if my issue is fixed - those 2009 entries might have been caused by my attempt at removal of trailing ,,,,,'s ion the version 4 file.

R.