Cumulus Support

Lately I have been getting some wacky readings when I first connect. I shut my system down every night before I go to bed and in the morning if I am going to be home I will start it back up, during weekdays I usually wait till I come home from work before starting it up.
This past week I have been on vacation so I started my system up shortly after I woke up. The problem is after I start up Cumulus it states that there is a new record and the new record is the average daily temperature One morning it showed a reading of 8.3 Degrees Now I live in Jacksonville, Florida so a temperature like that would set a record indeed. I am using a USB cable with a ferrite bead on it I am not sure what to do to stop this from happening. I thought about the data spike tool but unless I read wrong it will not fix a spike coming from the data logger
I changed the interval that it transmits.
Can anyone explain why this is happening.

Steve is taking a short break and he would have the definitive answer, but I seem to recall that the spike filters do now apply to readings from the logger. It would be worth trying setting the temperature spike value to something sensible, if you have bad values in the logger then you could get them when 'live' running too.

Cumulus Help still says spike filters do not apply to data from the logger, and my quick search of 'Announcements and News' does not reveal any mention of such a change.

sfws wrote:

mcrossley wrote: I seem to recall that the spike filters do now apply to readings from the logger

Whilst I've no reason to doubt Mark

garybuska wrote:spike tool but unless I read wrong it will not fix a spike coming from the data logger

Cumulus Help still says spike filters do not apply to data from the logger, and my quick search of 'Announcements and News' does not reveal any mention of such a change.

It is highly probable that I am wrong!

Thanks for the replies As for the change I made I made it after I noticed the wacky readings. This just started happening this week. This morning when I started Cumulus up I get a reading of 19.8 no way is this even close.
I just discovered that there has been a update of Cumulus that I seemed to have missed I will download and install the update and let you know if this keeps happening.

I am still having the same problem. When I started up Cumulus today the low daily temp was 17.2
Where is this coming from and why is this happening. Starting Monday 9/15/14 I have to go back to work so I will not be starting up Cumulus until sometime after 5:00 PM ESDT.

Are those Fahrenheit or Celsius degrees?

Paul

I am not sure why that matters but these are Fahrenheit
I am old school I do not like the metric system. It is hard for me to visualize 2 kilometers.
It is hard to teach a old dog new tricks.

Sorry, I didn't clarify the question . Just thought that if those values of 19.8 and 17.2 were Celsius that might be more realistic for your area.

As I am not familiar with the WS2090, do those incorrect readings also show on the station console as well as the download from the data logger by Cumulus?
Paul

The spike removal settings don't apply to the logger; because of the larger interval, it wouldn't make sense to apply the same values. Generally it appears that data from the logger does not suffer from spikes anyway, for the most part.

If you zip up the diags folder and attach it, I'll take a look.

I Run Cumulus mostly off the logger but using a La Crosse station with a 5 minute interval and I get regular spikes, more frequent in the cooler months. In the last 3 months about 50 out 90 spikes have been recorded by the logger. It is hard to expect that such a large number can coincide with the logger entry time with the 5 minute interval and depending on how long the spike lasts for. But it only takes me a few minutes to remove the spikes.

I know next to nothing about La Crosse stations, other than the fact that their PC interface design is pants; I was talking about Fine Offset stations - note the forum section

I do realise that this is about Fine Offset, it seems that the Fine Offset has similar trouble with spikes problems. I was only making the point that it is very likely for logger data to get affected by spikes as the spikes are mostly created by the base unit (with my station).
btw I have found with the La Crosse that not many spikes occurred when using the poor La Crosse connection to Cumulus it was the base station.

(deleted)

I Hope you get this
Thanks Steve