Multiple Cumulus icons showing

[JimDantin]

Thanks - at what time was the 'data stopped' reported?

Didn't record it. When I checked on the status I noticed the monitor wasn't scrolling new data but cumulus looked ok.

I you want i'll do it again and watch it until it fails.

[steve]

There are over half a million lines in there and it's hard to work out where the problem was. The timestamping is a bit strange, too. Could you download this, please: http://nybbles.co.uk/downloads/Cumulus.zip

It's just the cumulus.exe file. Extract it into your existing installation, then start the serial port monitor, then run Cumulus and turn on the debug log. When you get the 'data stopped' reported, wait until you see the data being updated again, then turn off the debug log, then zip up the debug log and the spm file and attach it, please.

[steve]

I've just noticed something. This version of the firmware seems to be returning the data much more quickly than older versions. Normally, Cumulus just sits in a loop, reading the data, and it's self-regulating by virtue of the console taking around 2 seconds to return the data. Users of Virtual VP have to add a setting to the cumulus.ini file to introduce a delay, because VVP returns the data very quickly (because it has it cached).

It looks like this firmware is going to need the same. It could be that reading the data repeatedly so quickly is causing problems. So, could you try this: stop Cumulus and edit cumulus.ini, and anywhere in the [Station] section, add a line:

VP2SleepInterval = 1100

Then start Cumulus. After it's been running for a minute or so, check the 'last data read' time in the status bar. We need to aim for an update every 2 to 3 seconds. See if this change stops the problem occurring. Don't bother with the debug log etc for now.

[JimDantin]

I've just noticed something. This version of the firmware seems to be returning the data much more quickly than older versions. Normally, Cumulus just sits in a loop, reading the data, and it's self-regulating by virtue of the console taking around 2 seconds to return the data. Users of Virtual VP have to add a setting to the cumulus.ini file to introduce a delay, because VVP returns the data very quickly (because it has it cached).

It looks like this firmware is going to need the same. It could be that reading the data repeatedly so quickly is causing problems. So, could you try this: stop Cumulus and edit cumulus.ini, and anywhere in the [Station] section, add a line:

VP2SleepInterval = 1100

Then start Cumulus. After it's been running for a minute or so, check the 'last data read' time in the status bar. We need to aim for an update every 2 to 3 seconds. See if this change stops the problem occurring. Don't bother with the debug log etc for now.

This is looking very good. The 2 second update is clicking right along with no errors after 5 minutes or so. I'm going to let it run for a while and will report back. Keep your fingers crossed, but i think you have it!

If this does fix it, I should take out the line "DavisCalcAltPress=0", right?

[steve]

Unfortunately Pascal is finding that this doesn't fix it for him.

You can take out that line, though, yes, it's turned out to be unrelated to the problem.

[JimDantin]

No errors yet here. The 2-second updates are just clicking along.

I just stopped Cumulus, edited the ini file and removed the line "DavisCalcAltPress=0, restarted and turned on debug logging. I'll let it run for an hour or so.

Might be that the USB and Serial versions have slightly different responses to the problem.

[JimDantin]

Have you seen Davis' updated (as of 8/24/2012) Serial Communication Reference Manual? Might offer some insight if you haven't already checked it out.

[JimDantin]

No errors logged.

[steve]

No errors logged.

Well, I guess that's good. Odd that it didn't make any difference for Pascal.

[JimDantin]

Yesterday I uploaded logs and Diag again with a message that the errors have returned. I just noticed that the posting isn't here. Here is just the error messages - I will upload the rest again if you want it. This pattern of errors is a bit different that it was originally. The errors are more sporadic. I don't know if the timing or pattern indicates anything to you.

Just let me know if you want any additional diagnostic files.

1/2/2013 8:19:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 8:20:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 8:21:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 10:03:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 10:04:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 10:05:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 11:15:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 11:16:00 AM : Data input appears to have stopped - check your station and connections
1/2/2013 2:52:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 2:53:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 2:54:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 6:09:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 6:10:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 9:01:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 9:02:00 PM : Data input appears to have stopped - check your station and connections
1/2/2013 9:03:00 PM : Data input appears to have stopped - check your station and connections
1/3/2013 6:43:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 6:44:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 6:45:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 7:00:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 7:01:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 8:15:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 8:16:00 AM : Data input appears to have stopped - check your station and connections
1/3/2013 8:17:00 AM : Data input appears to have stopped - check your station and connections

[steve]

Yesterday I uploaded logs and Diag again with a message that the errors have returned. I just noticed that the posting isn't here

You posted in the 'other' thread. I assumed you had done it deliberately to keep this discussion in one thread, which makes things easier (for me, anyway). I've posted my current thoughts there.

[JimDantin]

Yesterday I uploaded logs and Diag again with a message that the errors have returned. I just noticed that the posting isn't here

You posted in the 'other' thread. I assumed you had done it deliberately to keep this discussion in one thread, which makes things easier (for me, anyway). I've posted my current thoughts there.

Well, duh on me, but it probably is best to consolidate the discussion on one thread.

I will stop posting here.

Thanks