false monthly rainfall of 2000mm!

[lu3fbm_arg]

Today I created a rain cumulus 2000mm at 9am. That might be genereando this error?
this rain appeared as monthly but the strange thing is that today does not indicate rain!
This may be the problem, a data logger setup?, any failure of cumulus?
help!

[steve]

Please zip up the diags folder and attach it, together with your dayfile.txt file.

[lu3fbm_arg]

Please zip up the diags folder and attach it, together with your dayfile.txt file.

The problem is that the station is 150km from where I am now and I can not access remotely.

[steve]

The problem is that the station is 150km from where I am now and I can not access remotely.

Then upload the files when you do have access.

[lu3fbm_arg]

Please zip up the diags folder and attach it, together with your dayfile.txt file.

The problem is that the station is 150km from where I am now and I can not access remotely.

the site is www.meteolitoral.com.ar

[steve]

Looking at your graphs, your station was generating complete garbage before 0900 today. My guess is this: that data came from the logger, and you have selected the wrong station type. If you have a WH1081, which doesn't have a solar sensor, then you have selected the station type which does have a solar sensor. This means that any data which Cumulus downloads from the logger will be wrong, because the logger entries are different sizes. That is just a guess, though.

[lu3fbm_arg]

I use cumulus 1.9.2 and I have selected cumulus where it says fine offset WH1080. I have wh1081 no UV or solar-powered is the standard.
Another option I see in cumulus.

Looking at your graphs, your station was generating complete garbage before 0900 today. My guess is this: that data came from the logger, and you have selected the wrong station type. If you have a WH1081, which doesn't have a solar sensor, then you have selected the station type which does have a solar sensor. This means that any data which Cumulus downloads from the logger will be wrong, because the logger entries are different sizes. That is just a guess, though.

[steve]

It was just a guess as I have nothing else to go on. I'll need to see the diags files.

It looks like you restarted Cumulus at 0900? You didn't notice a problem at the time, and now you're 150 km away? If you're often 150 km away, it would be a good idea to set up remote access to the PC.

[lu3fbm_arg]

Thanks Steve for your replies, this weekend I'll be able to get the files and I'll rise. It strikes me that the wrong data received on the console what happened.
I will analyze in depth to provide a solution to the problem. As for remote access I will set within 15 days when traveling to the village.
Greetings.

It was just a guess as I have nothing else to go on. I'll need to see the diags files.

It looks like you restarted Cumulus at 0900? You didn't notice a problem at the time, and now you're 150 km away? If you're often 150 km away, it would be a good idea to set up remote access to the PC.

[lu3fbm_arg]

Steve let setup labeled RESTARS IF DATA STOPS, and from what I see on my site the station is reset to the time 9AM frame 2000mm reading.
Can this be the problem?

Thanks Steve for your replies, this weekend I'll be able to get the files and I'll rise. It strikes me that the wrong data received on the console what happened.
I will analyze in depth to provide a solution to the problem. As for remote access I will set within 15 days when traveling to the village.
Greetings.

It was just a guess as I have nothing else to go on. I'll need to see the diags files.

It looks like you restarted Cumulus at 0900? You didn't notice a problem at the time, and now you're 150 km away? If you're often 150 km away, it would be a good idea to set up remote access to the PC.

[steve]

If you didn't restart Cumulus yourself at 0900, that's probably why it restarted. There were definitely problems up to that point, looking at the data that was being read. But it's impossible for me to say anything for certain without seeing the diags files.

[lu3fbm_arg]

Archivos adjuntos!!

It was just a guess as I have nothing else to go on. I'll need to see the diags files.

It looks like you restarted Cumulus at 0900? You didn't notice a problem at the time, and now you're 150 km away? If you're often 150 km away, it would be a good idea to set up remote access to the PC.

[steve]

It was really the diags files that I needed, but as it happens I can see what the problem is from the data files:

05/08/12,09:30,10,4,95,9,6,5,0,8,6,115,0,0,0,0,1018,0,2,1,27,1,43,7,2,10,2,10,4,0,0,0,0,00,0,00,9,4,182,0,0,90

You have your Windows list separator and decimal separator both set to a comma, which makes it impossible for Cumulus to read back the data files and make sense of them.

[lu3fbm_arg]

as it should configure windows then?

It was really the diags files that I needed, but as it happens I can see what the problem is from the data files:

05/08/12,09:30,10,4,95,9,6,5,0,8,6,115,0,0,0,0,1018,0,2,1,27,1,43,7,2,10,2,10,4,0,0,0,0,00,0,00,9,4,182,0,0,90

You have your Windows list separator and decimal separator both set to a comma, which makes it impossible for Cumulus to read back the data files and make sense of them.

[steve]

Countries which use a comma for decimals normally use a semicolon for a list separator. You need to change your Windows settings.