High CPU usage

[Nelsoncasey13]

Hi, I'm using the program a few months ago and I love it (we use a FM radio station). But I have a big problem:
Approximately every two or three weeks CPU usage rises to 25% and remains so until restart the program. (Cumulus normal use of 0%)
Cumulus is on the same PC (Intel i3) with Stereo Tool (software used by radio stations to improve the sound, which uses much CPU).
When Cumulus starts using both CPU, Stereo Tool hangs, and the radio is silent.

We have a meteorological station WH1080.
And the version of Cumulus 1.9.4, build 1097.

Deputy some error logs.

Thank you for your help.

[steve]

When the problem next occurs, please zip up the diags folder and attach it. Please also tell me at what time the problem occurred! It's not easy looking through logs to try to find something unusual if I don't know when it is supposed to have happened. If it last happened quite recently, you could zip up the diags folder now and attach it.

One thing that you could do, if you haven't already, is to turn off the animation for the wind gauge.

[Nelsoncasey13]

When the problem next occurs, please zip up the diags folder and attach it. Please also tell me at what time the problem occurred! It's not easy looking through logs to try to find something unusual if I don't know when it is supposed to have happened. If it last happened quite recently, you could zip up the diags folder now and attach it.

Well the last time that happened was yesterday. can not remember the time but it was between 11 am and 3 pm.
Attached files dialog.

One thing that you could do, if you haven't already, is to turn off the animation for the wind gauge.

I just did this. Does this serves to reduce CPU usage?

[steve]

You have a problem with the USB connection to your console:

08/12/2014 14:58:45.528 : 02:58:45 p.m. EWUSB: HidControl Arrival
08/12/2014 14:58:45.528 : VID = 04D9 PID = 1602
08/12/2014 14:58:45.528 : 02:58:45 p.m. EWUSB: HidControl Arrival
08/12/2014 14:58:45.528 : VID = 04D9 PID = 1602
08/12/2014 14:58:45.528 : 02:58:45 p.m. EWUSB: HidControl Arrival
08/12/2014 14:58:45.528 : VID = 1941 PID = 8021
08/12/2014 14:58:47.588 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.590 : VID = 1941 PID = 8021
08/12/2014 14:58:47.591 : Error - station removed - check connections
08/12/2014 14:58:47.633 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.633 : VID = 1941 PID = 8021
08/12/2014 14:58:47.633 : Error - station removed - check connections
08/12/2014 14:58:47.659 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.659 : VID = 1941 PID = 8021
08/12/2014 14:58:47.659 : Error - station removed - check connections
08/12/2014 14:58:47.684 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.684 : VID = 1941 PID = 8021
08/12/2014 14:58:47.684 : Error - station removed - check connections
08/12/2014 14:58:47.706 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.706 : VID = 1941 PID = 8021
08/12/2014 14:58:47.706 : Error - station removed - check connections
08/12/2014 14:58:50.955 : Error!!! Failed to write to USB!
08/12/2014 14:59:00.958 : Error!!! Failed to write to USB!
08/12/2014 14:59:10.970 : Error!!! Failed to write to USB!
08/12/2014 14:59:20.977 : Error!!! Failed to write to USB!
08/12/2014 14:59:30.986 : Error!!! Failed to write to USB!
08/12/2014 14:59:41.000 : Error!!! Failed to write to USB!
08/12/2014 14:59:51.004 : Error!!! Failed to write to USB!
08/12/2014 15:00:00.748 : *** Data input appears to have stopped
08/12/2014 15:00:00.757 : Writing today.ini, LastUpdateTime = 08/12/2014 03:00:00 p.m. raindaystart = 675,900024414063 rain counter = 675,900024414063
08/12/2014 15:00:00.757 : Latest reading: 1CE0: Data: 04 18 9F 01 18 61 01 CC 26 14 1B 00 0E CD 08 00
08/12/2014 15:00:01.015 : Error!!! Failed to write to USB!
08/12/2014 15:00:11.020 : Error!!! Failed to write to USB!
08/12/2014 15:00:21.030 : Error!!! Failed to write to USB!
08/12/2014 15:00:31.033 : Error!!! Failed to write to USB!
08/12/2014 15:00:41.044 : Error!!! Failed to write to USB!
08/12/2014 15:00:51.044 : Error!!! Failed to write to USB!
08/12/2014 15:01:00.760 : *** Data input appears to have stopped
08/12/2014 15:01:01.059 : Error!!! Failed to write to USB!
08/12/2014 15:01:11.076 : Error!!! Failed to write to USB!
08/12/2014 15:01:21.078 : Error!!! Failed to write to USB!
08/12/2014 15:01:31.090 : Error!!! Failed to write to USB!
08/12/2014 15:01:41.094 : Error!!! Failed to write to USB!
08/12/2014 15:01:51.104 : Error!!! Failed to write to USB!
08/12/2014 15:02:00.765 : *** Data input appears to have stopped
08/12/2014 15:02:01.113 : Error!!! Failed to write to USB!
08/12/2014 15:02:11.119 : Error!!! Failed to write to USB!
08/12/2014 15:02:21.128 : Error!!! Failed to write to USB!
08/12/2014 15:02:31.136 : Error!!! Failed to write to USB!


Some other device is also apparently affected by this, or perhaps causing it - VID = 04D9 PID = 1602

This is presumably causing the Windows USB driver to use excessive CPU. You will need to determine what is causing the USB issue and correct it.

I also noticed that you have Windows configured to use a comma for both the decimal and the list separator. This cannot work, as there is no way to parse a comma-separated list of numbers which use commas for decimals. As a result, all of your Cumulus data logs are effectively useless. This is the cause of all of the errors which Cumulus has been telling you about for some time now:

07/12/2014 01:44:58.553 : Error plotting charts at line 2 of dayfile.txt: '00:00' is not a valid floating point value
07/12/2014 01:44:58.553 : Please correct the error by editing dayfile.txt
07/12/2014 01:44:58.554 : Error plotting charts at line 3 of dayfile.txt: '21:59' is not a valid floating point value
07/12/2014 01:44:58.554 : Please correct the error by editing dayfile.txt
07/12/2014 01:44:58.554 : Error plotting charts at line 4 of dayfile.txt: '22:00' is not a valid floating point value
07/12/2014 01:44:58.554 : Please correct the error by editing dayfile.txt
07/12/2014 01:44:58.554 : Error plotting charts at line 5 of dayfile.txt: '22:00' is not a valid floating point value
07/12/2014 01:44:58.554 : Please correct the error by editing dayfile.txt

[Nelsoncasey13]

You have a problem with the USB connection to your console:

08/12/2014 14:58:45.528 : 02:58:45 p.m. EWUSB: HidControl Arrival
08/12/2014 14:58:45.528 : VID = 04D9 PID = 1602
08/12/2014 14:58:45.528 : 02:58:45 p.m. EWUSB: HidControl Arrival
08/12/2014 14:58:45.528 : VID = 04D9 PID = 1602
08/12/2014 14:58:45.528 : 02:58:45 p.m. EWUSB: HidControl Arrival
08/12/2014 14:58:45.528 : VID = 1941 PID = 8021
08/12/2014 14:58:47.588 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.590 : VID = 1941 PID = 8021
08/12/2014 14:58:47.591 : Error - station removed - check connections
08/12/2014 14:58:47.633 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.633 : VID = 1941 PID = 8021
08/12/2014 14:58:47.633 : Error - station removed - check connections
08/12/2014 14:58:47.659 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.659 : VID = 1941 PID = 8021
08/12/2014 14:58:47.659 : Error - station removed - check connections
08/12/2014 14:58:47.684 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.684 : VID = 1941 PID = 8021
08/12/2014 14:58:47.684 : Error - station removed - check connections
08/12/2014 14:58:47.706 : EWUSB: HidControl Device Removal
08/12/2014 14:58:47.706 : VID = 1941 PID = 8021
08/12/2014 14:58:47.706 : Error - station removed - check connections
08/12/2014 14:58:50.955 : Error!!! Failed to write to USB!
08/12/2014 14:59:00.958 : Error!!! Failed to write to USB!
08/12/2014 14:59:10.970 : Error!!! Failed to write to USB!
08/12/2014 14:59:20.977 : Error!!! Failed to write to USB!
08/12/2014 14:59:30.986 : Error!!! Failed to write to USB!
08/12/2014 14:59:41.000 : Error!!! Failed to write to USB!
08/12/2014 14:59:51.004 : Error!!! Failed to write to USB!
08/12/2014 15:00:00.748 : *** Data input appears to have stopped
08/12/2014 15:00:00.757 : Writing today.ini, LastUpdateTime = 08/12/2014 03:00:00 p.m. raindaystart = 675,900024414063 rain counter = 675,900024414063
08/12/2014 15:00:00.757 : Latest reading: 1CE0: Data: 04 18 9F 01 18 61 01 CC 26 14 1B 00 0E CD 08 00
08/12/2014 15:00:01.015 : Error!!! Failed to write to USB!
08/12/2014 15:00:11.020 : Error!!! Failed to write to USB!
08/12/2014 15:00:21.030 : Error!!! Failed to write to USB!
08/12/2014 15:00:31.033 : Error!!! Failed to write to USB!
08/12/2014 15:00:41.044 : Error!!! Failed to write to USB!
08/12/2014 15:00:51.044 : Error!!! Failed to write to USB!
08/12/2014 15:01:00.760 : *** Data input appears to have stopped
08/12/2014 15:01:01.059 : Error!!! Failed to write to USB!
08/12/2014 15:01:11.076 : Error!!! Failed to write to USB!
08/12/2014 15:01:21.078 : Error!!! Failed to write to USB!
08/12/2014 15:01:31.090 : Error!!! Failed to write to USB!
08/12/2014 15:01:41.094 : Error!!! Failed to write to USB!
08/12/2014 15:01:51.104 : Error!!! Failed to write to USB!
08/12/2014 15:02:00.765 : *** Data input appears to have stopped
08/12/2014 15:02:01.113 : Error!!! Failed to write to USB!
08/12/2014 15:02:11.119 : Error!!! Failed to write to USB!
08/12/2014 15:02:21.128 : Error!!! Failed to write to USB!
08/12/2014 15:02:31.136 : Error!!! Failed to write to USB!

Some other device is also apparently affected by this, or perhaps causing it - VID = 04D9 PID = 1602

This is presumably causing the Windows USB driver to use excessive CPU. You will need to determine what is causing the USB issue and correct it.

If there is any device doing "- VID = 04D9 PID = 1602" as I can know what?

It may be a problem with the drivers?, I just realized that there is any USB device without driver.
And the weather station is the only USB device connected to the pc. (no mouse or keyboard USB)

I also noticed that you have Windows configured to use a comma for both the decimal and the list separator. This cannot work, as there is no way to parse a comma-separated list of numbers which use commas for decimals. As a result, all of your Cumulus data logs are effectively useless. This is the cause of all of the errors which Cumulus has been telling you about for some time now:
07/12/2014 01:44:58.553 : Error plotting charts at line 2 of dayfile.txt: '00:00' is not a valid floating point value
07/12/2014 01:44:58.553 : Please correct the error by editing dayfile.txt
07/12/2014 01:44:58.554 : Error plotting charts at line 3 of dayfile.txt: '21:59' is not a valid floating point value
07/12/2014 01:44:58.554 : Please correct the error by editing dayfile.txt
07/12/2014 01:44:58.554 : Error plotting charts at line 4 of dayfile.txt: '22:00' is not a valid floating point value
07/12/2014 01:44:58.554 : Please correct the error by editing dayfile.txt
07/12/2014 01:44:58.554 : Error plotting charts at line 5 of dayfile.txt: '22:00' is not a valid floating point value
07/12/2014 01:44:58.554 : Please correct the error by editing dayfile.txt

That is so because it is the decimal format used here in Argentina and several countries. I could change the format manually. but I think it should be corrected, because all of this country will have the same problem.
Anyway us do not use the later analysis of weather data, only data from the current climate.

Thanks for you help.

[water01]

The clue is in what Steve said

I also noticed that you have Windows configured to use a comma for both the decimal and the list separator.

Using a comma as decimal point is quite common in many countries, but you get around the problem by changing the list separator in Windows.

Click on Control Panel, select Regions and Language and when the window opens click on the Additional Settings button at the bottom.

Another window will open and about 2/3rds of the way down the list you will see List separator. Change this to something not used elsewhere such ; and now Cumulus will be able to tell the difference between a decimal , and the character used to separate a list.

[steve]

If you don't have any other USB devices connected externally, then perhaps it's an internal controller of some kind.

I've just tried the "Spanish (Argentina)" setting in Windows, and it does set both decimal and list separator to a comma by default, which is crazy.

[Nelsoncasey13]

If you don't have any other USB devices connected externally, then perhaps it's an internal controller of some kind.

Ok, while the problem parese be a dirver, maybe you could enhance this from Cumulus.
I saw that there is an option "Restart the program should hang" and I think this proglema should I be considered as such.
Especially because the problem is solved by closing and opening Cumulus.

Thanks

[steve]

The "restart if data stops" option already covers this, and Cumulus detected that data had stopped in your case:

08/12/2014 15:00:00.748 : *** Data input appears to have stopped

If Cumulus actually hangs, then it can't restart itself, by definition. Separate software exists which can check for this and restart programs which hang.

But in any case, it is unreasonable to expect Cumulus to cope with every problem on every computer. Closing and restarting Cumulus does not solve the problem, it just gets it going again until the problem on your PC happens again. You need to fix the problem with your computer, whatever it is. That is the solution.