Welcome to the Cumulus Support forum.
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
(Note that 4.1.0 (build 4024) - 05 June 2024 remains available, but usage of this version is not recommended - particularly for Davis stations - and the included utility in this distribution for migrating to v4 is known to contain errors affecting conversion of dayfile.txt)
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V4 release 4.0.1 (build 4023) - 16 May 2024
(Note that 4.1.0 (build 4024) - 05 June 2024 remains available, but usage of this version is not recommended - particularly for Davis stations - and the included utility in this distribution for migrating to v4 is known to contain errors affecting conversion of dayfile.txt)
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Erratic Readings Which Are Too Low
Moderator: mcrossley
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Erratic Readings Which Are Too Low
I use Linux quite a lot and have not had any issues really with CMX other than the libudev.so.0 issue I came up with a fix for. I reinstalled Windows 7 for the free Windows 10 upgrade (still on Windows 7 at the moment). I installed CMX 3026 and I am noticing a strange issue. It seems to happen when I first start up CMX. I get really low readings: negative temperatures and low barometric pressure readings. I think it must be some sort of USB data read issue, but I am unsure.
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Erratic Readings Which Are Too Low
Yes, it got bad data in one of the logger entries:
2015-07-29 10:20:07.684 Reading current address DFF0
10:20:07 AM Read logger entry for 7/29/2015 10:20:07 AM address DFE0: 01 36 07 01 51 0E 01 03 27 25 36 00 0E 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:19:07 AM address DFD0: 01 36 07 01 50 0E 01 01 27 0E 11 00 0D 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:18:07 AM address DFC0: 01 36 07 01 51 0E 01 01 27 0E 14 00 0E 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:17:07 AM address DFB0: 01 36 07 01 52 0D 01 02 27 18 25 00 0D 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:16:07 AM address DFA0: 01 36 07 01 52 0D 01 01 27 14 1B 00 0E 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:15:07 AM address DF90: 01 36 07 01 52 0D 01 01 27 0A 14 00 00 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:14:07 AM address DF80: 01 36 07 01 52 0D 01 01 27 1B 29 00 0E 4C 0B 80
10:20:09 AM Read logger entry for 7/29/2015 10:13:07 AM address DF70: 01 36 07 01 52 0C 01 00 27 0A 14 00 0F 4C 0B 80
10:20:09 AM Read logger entry for 7/29/2015 10:12:07 AM address DF60: 32 02 22 00 01 01 00 80 00 0A 00 07 05 81 03 08
2015-07-29 10:20:09.204 Number of history entries = 9
See how that last entry (actually the earliest) is clearly different - it's not valid data. I can't say whether it's the station memory that's corrupt, or whether it got corrupted in the USB transfer. It might have been informative to see other examples.
2015-07-29 10:20:07.684 Reading current address DFF0
10:20:07 AM Read logger entry for 7/29/2015 10:20:07 AM address DFE0: 01 36 07 01 51 0E 01 03 27 25 36 00 0E 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:19:07 AM address DFD0: 01 36 07 01 50 0E 01 01 27 0E 11 00 0D 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:18:07 AM address DFC0: 01 36 07 01 51 0E 01 01 27 0E 14 00 0E 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:17:07 AM address DFB0: 01 36 07 01 52 0D 01 02 27 18 25 00 0D 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:16:07 AM address DFA0: 01 36 07 01 52 0D 01 01 27 14 1B 00 0E 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:15:07 AM address DF90: 01 36 07 01 52 0D 01 01 27 0A 14 00 00 4C 0B 80
10:20:08 AM Read logger entry for 7/29/2015 10:14:07 AM address DF80: 01 36 07 01 52 0D 01 01 27 1B 29 00 0E 4C 0B 80
10:20:09 AM Read logger entry for 7/29/2015 10:13:07 AM address DF70: 01 36 07 01 52 0C 01 00 27 0A 14 00 0F 4C 0B 80
10:20:09 AM Read logger entry for 7/29/2015 10:12:07 AM address DF60: 32 02 22 00 01 01 00 80 00 0A 00 07 05 81 03 08
2015-07-29 10:20:09.204 Number of history entries = 9
See how that last entry (actually the earliest) is clearly different - it's not valid data. I can't say whether it's the station memory that's corrupt, or whether it got corrupted in the USB transfer. It might have been informative to see other examples.
Steve
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
From MXdiags?steve wrote:It might have been informative to see other examples.
Also this hasn't happened in Linux. I could log in now and open CMX and it will get the data perfectly fine.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Erratic Readings Which Are Too Low
If it's the same PC that you were using with Linux, same USB hardware etc, then perhaps some kind of timing issue that happens only when you're running Windows. In all of the testing I've done on Windows, Linux and OS/X, I haven't seen that problem myself.
I was thinking of making the time that it allows for the USB transfer to be configurable to see if that would help with the issue that someone is seeing with Charlie's Arduino emulation; perhaps it might also help in your case.
I was thinking of making the time that it allows for the USB transfer to be configurable to see if that would help with the issue that someone is seeing with Charlie's Arduino emulation; perhaps it might also help in your case.
Steve
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
Yup same PC. Alright I will await 3027. Thanks.
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
I missed getting 3027 so I am on 3028. My Windows 7 also upgraded to Windows 10 which is actually kind of nice other than the privacy invasion settings one needs to be careful of not enabling. I am still having the same issue. I added this under the Station section of Cumulus.ini:
FineOffsetReadTime=200
Then, in Windows 10, I fired up CumulusMX and then looked at the interface and it is telling me the low temperature was 32.2 °F at 3:06 PM which obviously it was not. Attached is the Diag.
FineOffsetReadTime=200
Then, in Windows 10, I fired up CumulusMX and then looked at the interface and it is telling me the low temperature was 32.2 °F at 3:06 PM which obviously it was not. Attached is the Diag.
You do not have the required permissions to view the files attached to this post.
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
Attached is another Diag with the ms set to 500 instead of 200.
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Erratic Readings Which Are Too Low
Changing the read time hasn't helped in the case of the Arduino system, and it doesn't seem to have helped in your case either, you are still getting the occasional bad reading. I'm not aware of anyone else with this problem, but I note that you have the station set to a 1-minute logger interval, which Fine Offset do not support with their standard software - perhaps there is a reason for this.
It would be informative to see what happens when the same data is downloaded twice - if you 'rewind', by copying the files from this folder:
2015-08-08 22:43:04.893 Creating backup folder backup\20150808224304\
into your data folder, with Cumulus stopped, then when you start it up it will download the same memory locations again (along with all the others since that point).
It would be informative to see what happens when the same data is downloaded twice - if you 'rewind', by copying the files from this folder:
2015-08-08 22:43:04.893 Creating backup folder backup\20150808224304\
into your data folder, with Cumulus stopped, then when you start it up it will download the same memory locations again (along with all the others since that point).
Steve
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
The station I am using is branded Weatherwise, but it's a Fine Offset WH2080:
http://foshk.com/Weather_Professional/WH2080.htm
Attached are the diags. The first two were done from the backup you requested. The third was data from Linux. As far as I can tell, the Linux data looks fine. The two Windows ones may have too low of a dew point, but I am not sure.
http://foshk.com/Weather_Professional/WH2080.htm
Attached are the diags. The first two were done from the backup you requested. The third was data from Linux. As far as I can tell, the Linux data looks fine. The two Windows ones may have too low of a dew point, but I am not sure.
You do not have the required permissions to view the files attached to this post.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Erratic Readings Which Are Too Low
All three of those were from Windows, but anyway... it read the 'bad' locations correctly this time, in fact it seems to have read all 1150 entries correctly. So it looks like you have some kind of intermittent issue with the transfer of the data, rather than it being a problem with the memory locations in the station.
Steve
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
Third one was from Linux but yes ran in Windows. I copied the data folder over from the Linux install to the Windows install then ran CMX in Windows. I'll keep an eye on it today as I have a few things I need to do in Windows. If there is an error, I'll report back.
I wonder if an option to ignore bad data would be possible. Like setting CMX to where if the temperature is off by 20 °F or more from the previous minute or the barometer is off by 10 hPa or more from the previous minute that the data is not logged by CMX.
I wonder if an option to ignore bad data would be possible. Like setting CMX to where if the temperature is off by 20 °F or more from the previous minute or the barometer is off by 10 hPa or more from the previous minute that the data is not logged by CMX.
- steve
- Cumulus Author
- Posts: 26701
- Joined: Mon 02 Jun 2008 6:49 pm
- Weather Station: None
- Operating System: None
- Location: Vienne, France
- Contact:
Re: Erratic Readings Which Are Too Low
It already has that (the 'spike removal' settings), just the same as Cumulus 1 has had for a very long time, because of the 'spikes' which Fine Offset stations tend to produce. But these don't operate when reading logger data, firstly because Fine Offsets stations don't tend to produce spikes when data is being read from logger data, and secondly because it wouldn't be easy, in general, to specify the differences because of the longer intervals involved in logger data (when using the intervals supported by Fine Offset).Buford T. Justice wrote:I wonder if an option to ignore bad data would be possible. Like setting CMX to where if the temperature is off by 20 °F or more from the previous minute or the barometer is off by 10 hPa or more from the previous minute that the data is not logged by CMX.
Independently of the 'spike removal' settings, it also automatically discards obviously bad data, i.e. where readings are outside reasonable absolute limits.
But your issue is apparently nothing to do with the traditional Fine Offset problems, it is apparently some kind of USB transfer problem. And as far as I am aware, no-one else has the same issue.
Steve
- Buford T. Justice
- Posts: 423
- Joined: Fri 17 Aug 2012 9:21 pm
- Weather Station: Ecowitt GW1002
- Operating System: Windows 11 Pro
- Location: USA
Re: Erratic Readings Which Are Too Low
13:30 it said my pressure was 909.8 but that hurricane sure was not windy, lol. I might format drive and do the full install of Windows 10 since the Windows 7 license upgraded to a Windows 10 one. Diag attached if you want to see it. I also tried different USB ports before but that didn't solve it so I am not sure what is messed up on my end in Windows.
You do not have the required permissions to view the files attached to this post.
- pete_c
- Posts: 228
- Joined: Wed 12 Oct 2011 11:22 pm
- Weather Station: Davis Vue-Pro2 - Fine Offset
- Operating System: W2003-XPSP3-Linux
- Location: Time Traveler
Re: Erratic Readings Which Are Too Low
Here have left the Fine Offset on the old Wintel box running still with Cumulus 1 mostly cuz its not here in the Midwest with me. I do still get an occasional disconnect of the USB port where the batteries have to be removed from the Fine Offset tablet receiver. It is a PITA to fix this remotely.
That said I have recently upgraded one Windows 8.1 mini pc to Windows 10. I have it installed on my home office desk with a multitouch 19" screen and using an Intel Atom Baytrail CPU. It is more configured right now to play rather than to use. I have noticed that the computer totally shuts itself down (NIC, USB et al). The update here to Windows 10 from Windows 8.1 was just an update that showed up. It did leave all of my stuff on the computer so that was a plus here. I did though disable all the chatting to the Microsoft Mothership stuff, advertising and using the cloud drive stuff. I am too liking Windows 10 more than Windows 7 and much more than Windows 8 and 8.1. I am though mostly here in the Linux world of things and intended purpose of the Windows 10 computer / screen is relating to automation stuff (well too adding the use of the Kinect and Amazon Echo stuff to it).
Today I touched the touchscreen and it woke up the Windows 10 from its totally shutdown state. It did come back up in a second or two.
I am guessing you have shut off the power savings features on your Windows 10 connecting to the Fine Offset device eh?
I was going to try an experiment here using the existing VPN tunnel and doing a virtual USB connection from the Wintel box with the Fine Offset to the Wintel Windows 10 box here in the midwest to see if it will work relating to CumulusMX and the Fine Offset USB device. This would involve remotely shutting down the Cumulus 1 running there and enabling the CumulusMX running here on Windows 10.
I have done this with a serial connection but never with a USB connection. I have historically just used Lantronix or Digi for USB to network connectivity; but only in Windows and not in Linux. I have had issues with particular USB drivers not working well in virtual USB fashion.
That said I have recently upgraded one Windows 8.1 mini pc to Windows 10. I have it installed on my home office desk with a multitouch 19" screen and using an Intel Atom Baytrail CPU. It is more configured right now to play rather than to use. I have noticed that the computer totally shuts itself down (NIC, USB et al). The update here to Windows 10 from Windows 8.1 was just an update that showed up. It did leave all of my stuff on the computer so that was a plus here. I did though disable all the chatting to the Microsoft Mothership stuff, advertising and using the cloud drive stuff. I am too liking Windows 10 more than Windows 7 and much more than Windows 8 and 8.1. I am though mostly here in the Linux world of things and intended purpose of the Windows 10 computer / screen is relating to automation stuff (well too adding the use of the Kinect and Amazon Echo stuff to it).
Today I touched the touchscreen and it woke up the Windows 10 from its totally shutdown state. It did come back up in a second or two.
I am guessing you have shut off the power savings features on your Windows 10 connecting to the Fine Offset device eh?
I was going to try an experiment here using the existing VPN tunnel and doing a virtual USB connection from the Wintel box with the Fine Offset to the Wintel Windows 10 box here in the midwest to see if it will work relating to CumulusMX and the Fine Offset USB device. This would involve remotely shutting down the Cumulus 1 running there and enabling the CumulusMX running here on Windows 10.
I have done this with a serial connection but never with a USB connection. I have historically just used Lantronix or Digi for USB to network connectivity; but only in Windows and not in Linux. I have had issues with particular USB drivers not working well in virtual USB fashion.
You do not have the required permissions to view the files attached to this post.
- Pete
Automator
Automator
-
- Posts: 3337
- Joined: Sat 13 Aug 2011 9:33 am
- Weather Station: Ecowitt HP2551
- Operating System: Windows 10 64bit
- Location: Burnham-on-Sea
- Contact:
Re: Erratic Readings Which Are Too Low
Why do you have to guess, the top of the forum says in BIG RED Letters "Do not allow your PC to go into standby mode while Cumulus is running - read the readme.txt!"I am guessing you have shut off the power savings features on your Windows 10 connecting to the Fine Offset device eh?