Cumulus Support

Hi Steve,

Using Cumulus since a lot of time, since a few month I'm experiencing a problem of CPU charge.
I changed the station from a Lacrosse ws 2350 to an Oregon WMR 200 but still annoyed with this leak.
I'm using an Ebox 3300 Mx with 1ghz and 512 Mo memory, turning under xp sp3 with the Cumulus 1.9.4 beta.
Cumulus Version is not the source of the problem, I tried this one to avoid the problem I'm encountering since version 1.9.1.
The only way I found to ensure a quite correct behaviour is to planify a restart of the engine every night ( shutdown -r )
I'm joigning a copy of the debug.log taken during a moment of great use of the CPU.
Hoping you see something there to give me some idea of the problem source.
Thanks a lot
Michel
http://legheer.be/meteo3

There's nothing in there to explain the high CPU usage, and the only issue I'm aware of with high CPU usage is with Davis stations with a particular firmware. If it suddenly started happening and isn't related to the version of Cumulus, then that would suggest a problem with your PC, perhaps something to do with drivers.

I don't understand why restarting the PC helps - doesn't it just go back to 98% again straight away?

One thing you could try is to turn off the animation of the wind gauge, on the display settings.

Thanks for your aswer. It happend so quickly, I did'nt see it.
The only reason to restart the computeer was a freeze of Cumulus after 24 or 36 hours.
It happened I could wait so 48 hours but not so often.
I'm trying to untick the windjauge animation. Will come back to you with some after a day or two.
Also look for newer drivers, but tryig one after the other hoping to isolate the real source.

Thanks again.
Michel

Hi Steve,

so I tried replacing drivers, and de activating the animated windjauge, nothing better...
Finally, got great improvement giving a greater interval for the realtime FTP ( 60 sec) and increasing the update interval to 3 min too.
I now have only a short time of CPU use at 100% ( 7 to 10 sec ) rather better than the 60 -80 sec before these changes, and the peak seems dued to calculation and update before upload . The rest of time Cumulus needs less than 10 % of CPU.

So problem seems to be solved .

Thanks