Rain Error Weatherlink Live

[grapee]

Hi,

For the last 2 mornings when firing up MX, I have a rainfall error of 50.4mm.

This is added once the catchup from WWL is completed for the overnight shutdown of PC.

I'm not 100% certain but the timing of the rainfall may coincide with me powering down the PC as I don't run it it 24/7 ?

Capture7.PNG

[water01]

Do you stop CumulusMX with a Ctrl+C before you power down the PC?

[grapee]

No I don't, I just

Capture8.png

Guess I may be doing it wrong ?

[water01]

That will be the problem then because CumulusMX needs to clean close in order to write out the files it has open and because you just close the window it does not get the chance to do so.

You ONLY close CumulusMX with a Ctrl+C with the Window open and wait for it to say program terminating and close the window. Any other way and you risk corrupting the files as is happening in your case.

[grapee]

That will be the problem then because CumulusMX needs to clean close in order to write out the files it has open and because you just close the window it does not get the chance to do so.

You ONLY close CumulusMX with a Ctrl+C with the Window open and wait for it to say program terminating and close the window. Any other way and you risk corrupting the files as is happening in your case.

Cheers David,

I'll do that, although having tried it, I don't get any program terminating message, it just closes the window.

Graeme

[water01]

As long as it closes the CumulusMX command window cleanly that is all you have to worry about. Probably your computer reacted so quickly you didn't get a chance to see the terminated message, mine is slower so I do

[grapee]

My PC doesn't normally react quickly to anything

And the problem hasn't gone away.
I've tried a few CTRL-C's, some of which close it immediately and some it takes a couple to close.

Either way, I now have 75.6mm of rain today (25.2 x 3), so it seems I do have an issue with closing it

[water01]

In which case you will need Mark Crossley's expertise on Davis Stations.

[sfws]

I have no knowledge of Davis stations or your specific problem.
But I can try to verify other assertions in this topic about how to close MX cleanly in Windows.

That will be the problem then because CumulusMX needs to clean close in order to write out the files it has open and because you just close the window it does not get the chance to do so.

You ONLY close CumulusMX with a Ctrl+C with the Window open and wait for it to say program terminating and close the window. Any other way and you risk corrupting the files as is happening in your case.

This is what I would do, if I need to close MX (a lot recently with my power going off for the rewiring I am having done).

No I don't, I just

Capture8.png

Guess I may be doing it wrong ?

I tried what is shown in this screen shot. I got the same messages as with my usual method (as per David). I saw message "Cumulus terminating", then message "Cumulus stopped", then the command window closed. So I conclude both methods are closing MX tidily for me (you learn something new each day). I guess for Windows any method within MX task will do a tidy close, but an external windows process like taskKill or Task Manager will mess up MX. I remember with Cumulus 1, it closed tidily whether you picked exit from File menu or clicked the "X", but if you had a power cut or you used Task Manager, C1 did not either close or restart normally.

I will add, that how long you have to see these messages depends when you try to close MX. If you pick a time when it is doing an upload (real time or standard), the messages will be seen for longer as it will finish that upload before it starts to update the "today.ini" and "Cumulus.ini" files it does as it finally closes.

My knowledge of C# is not sufficient to fully understand how Program.cs works, because it seems to be several processes nested (and Mark has changed some aspects recently), but the top level bit seems to be a loop with waits while check for exit confirmed, then simply stopping process. So I am guessing any action that lets MX finish what it is doing and do its own stop of process will work. It appears that clicking "X" is not a stop, but an instruction to MX to do what it does for leading to a stop.

[grapee]

I have no knowledge of Davis stations or your specific problem.
But I can try to verify other assertions in this topic about how to close MX cleanly in Windows.

That will be the problem then because CumulusMX needs to clean close in order to write out the files it has open and because you just close the window it does not get the chance to do so.

You ONLY close CumulusMX with a Ctrl+C with the Window open and wait for it to say program terminating and close the window. Any other way and you risk corrupting the files as is happening in your case.

This is what I would do, if I need to close MX (a lot recently with my power going off for the rewiring I am having done).

No I don't, I just
Capture8.png
Guess I may be doing it wrong ?

I tried what is shown in this screen shot. I got the same messages as with my usual method (as per David). I saw message "Cumulus terminating", then message "Cumulus stopped", then the command window closed. So I conclude both methods are closing MX tidily for me (you learn something new each day). I guess for Windows any method within MX task will do a tidy close, but an external windows process like taskKill or Task Manager will mess up MX. I remember with Cumulus 1, it closed tidily whether you picked exit from File menu or clicked the "X", but if you had a power cut or you used Task Manager, C1 did not either close or restart normally.

I will add, that how long you have to see these messages depends when you try to close MX. If you pick a time when it is doing an upload (real time or standard), the messages will be seen for longer as it will finish that upload before it starts to update the "today.ini" and "Cumulus.ini" files it does as it finally closes.

My knowledge of C# is not sufficient to fully understand how Program.cs works, because it seems to be several processes nested (and Mark has changed some aspects recently), but the top level bit seems to be a loop with waits while check for exit confirmed, then simply stopping process. So I am guessing any action that lets MX finish what it is doing and do its own stop of process will work. It appears that clicking "X" is not a stop, but an instruction to MX to do what it does for leading to a stop.

That all makes total sense and I remember Cumulus 1 taking a little time to close down.

But I'm still seeing no evidence of anything other than an immediate close or after a second CTRL-C.

This morning I have another 25.2mm recorded at 10:05, at this rate we'll be flooded out in a few days, living 500m from the River Thames !

[sfws]

This morning I have another 25.2mm recorded at 10:05, at this rate we'll be flooded out in a few days, living 500m from the River Thames ! :D

My MX is off because I am having my home rewired. Just before I shut MX down when the electrician said he needed power off, I was looking at my monthly logs. They seem to be getting a second line with same time whenever MX is shut down and does catch up when I can run it again.

I don't know if this is affecting my data as without power I can't investigate.

I hope you don't have actual flooding. Many decades ago I was at school beside the Thames and sometimes saw flooding. My pc desktop background had a flooding picture from near where I previously lived and I have replaced that with a picture of flooding near here last February. Local homes and businesses hardly recovered from the flooding when lockdown hit.

[grapee]

My MX is off because I am having my home rewired. Just before I shut MX down when the electrician said he needed power off, I was looking at my monthly logs. They seem to be getting a second line with same time whenever MX is shut down and does catch up when I can run it again.

This morning, I have no rain recorded but I suspect it will happen again, when it does, I'll have a look at the log files.
I have a degree of familiarity having had to modify various erroneous values whilst using Cumulus 1 for 10 years.
My old Fine Offset was getting more and more unreliable towards the end, giving me over 300mm of rain rain every day !

I hope you don't have actual flooding. Many decades ago I was at school beside the Thames and sometimes saw flooding. My pc desktop background had a flooding picture from near where I previously lived and I have replaced that with a picture of flooding near here last February. Local homes and businesses hardly recovered from the flooding when lockdown hit.

We've lived here in leafy Bucks since 2002 and in the first winter we had the worst flooding for 56 years.
We were cut off in one direction for around 2 weeks but even in the worst flooding recorded, had we lived here then, we would have been totally cut off but not flooded as we would have been on a very small island

[grapee]

My PC doesn't normally react quickly to anything

And the problem hasn't gone away.
I've tried a few CTRL-C's, some of which close it immediately and some it takes a couple to close.

Either way, I now have 75.6mm of rain today (25.2 x 3), so it seems I do have an issue with closing it

Just a quick update, the CTRL-C thing seems to have been the problem.

Since being made aware, it has been faultless and I am seeing the message, albeit only appearing for less than a second.

Many thanks for the advice.

Graeme