Range Check Error

[Signatrol.com]

Hi Forum,

I am new to this forum, and new to Cumulus.
We are an importer for the WH1080 weather station.

We are running a demo of Cumulus from our website

http://www.signatrol.com/weather/index.htm

Please note that the wind data will not be sensible, as we have the sensor mounted close to a building.

But the cumulus software is crashing every few days and uploading flat line graphs to the our web site.
The bugreport identifies the error as:

exception class : ERangeError
exception message : Range check error.

Full bug report attached.

I've attached the screen shoot of the problem, i've reset culumus and you can see the trends recover.



Any help Welcome.

Regards
Nick Price
Signatrol.com

[steve]

Nick, it's crashing in the debug logger. It's a bit buggy, and it has always been my intention to move away from it and use the logger which does the Diags logs throughout. The debug logger can cause problems even when it's not swtiched on, but it looks in this case like you do have it switched on? I wonder if the log file is getting too large and causing the crash?

[Signatrol.com]

Thanks for the reply Steve.

I will disable the debug and see how it goes and let the forum know.

Many thanks

Nick
http://www.signatrol.com

[Signatrol.com]

I'm a little confuzzled. Do you want me to turn off the logger function?? the debug option of the menu is already disabled??

Thanks, Nick

[steve]

The debug function on the menu. I did think it odd that you would have turned it on without being asked. But it is buggy and can cause problems even when turned off. The stack trace did suggest that it was on, though. Could you have a look at the debug.log file and see how big it is and what's in there, please?

[Signatrol.com]

Hi Steve.

This is strange. The debug.log file is 42k is size, and when I turn on debug on the menu the note in the log file says "Logging Disabled", and I turn off the debug again it says "Logging Enabled" and start to log command data to the weather station.

Is it a case of your selection is inverted??

Cheers

Nick
http://www.signatrol.com

[steve]

Is it a case of your selection is inverted??

I don't think so. It's always worked before, and it works OK for me now. Bear in mind that the data is only flushed to the log every few minutes (and when Cumulus closes), so what you see in the log isn't necessarily up to date. But what you describe does fit what I saw in the stack trace, that you had debugging turned on.

There's a facility for turning on the logging at start up by an ini-file setting. It's possible that using this subsequently makes the menu selection reversed - but again, it works fine for me. I assume you haven't used this? It requires the line "Logging=1" in the [Station] section of Cumulus.ini.

What is in your debug.log from before you started trying the debug log menu selection a few minutes ago?

[steve]

Something else I've noticed from the dump - Cumulus is using a huge amount of memory - about 800MB! It normally uses around 20MB or less. I don't know if this is part of the cause of the problem or a result of the problem.

[Signatrol.com]

Hi Steve,

Ok, played around. Finished with logging=1 in the ini file. Now debug file only says debug disabled.

We will see what happens.

Many thanks

Nick

[steve]

That's very odd, I've no idea how yours is apparently backwards. So you have Logging=1 in the [Station] section, menu item untouched, and it's definitely not logging?

[Signatrol.com]

Oops, sorry .... logging=0 ......

Sorry doing to many things at once.

http://www.signatrol.com

[steve]

Sorry doing to many things at once.

I know the feeling

Logging=0 is the default, but anyway... let's see what happens.