Data Input Appears To Have Stopped

[JimDantin]

Apparently Davis are saying that this problem doesn't occur with DLL 2.42. So I've done a test build using that DLL again; the installer is here

http://nybbles.co.uk/downloads/test/CumulusSetup.exe

Perhaps Pascal and Jim could try this, and see if you get the data stopped problem? You will also need to note how often the data gets updated with this DLL to see if it is the same 8 or 9 seconds that I (and others) have seen with their older stations.

Edit: If anyone else with v3 firmware feels like joining in with this game - please do!

Updates are every 4-5 seconds. I'll monitor for errors.

[steve]

Updates are every 4-5 seconds.

That's interesting. Do you still have the VP2SleepInterval setting in cumulus.ini, set at 1100? If so, that will be adding 1.1 seconds to the update interval. I've added some code which automatically does an interval of 1500 (1.5 seconds) if one isn't specified, so perhaps you could try stopping Cumulus and setting the value to 1 (so my code doesn't take effect)? Then you should be getting an update closer to the normal 2 or 3 seconds.

This is getting even more complicated...

[JimDantin]

Updates are every 4-5 seconds.

That's interesting. Do you still have the VP2SleepInterval setting in cumulus.ini, set at 1100? If so, that will be adding 1.1 seconds to the update interval. I've added some code which automatically does an interval of 1500 (1.5 seconds) if one isn't specified, so perhaps you could try stopping Cumulus and setting the value to 1 (so my code doesn't take effect)? Then you should be getting an update closer to the normal 2 or 3 seconds.

This is getting even more complicated...

I changed VP2SleepInterval to be 1

Updates are now every 3-4 seconds.

[JimDantin]

Updates are every 4-5 seconds.

That's interesting. Do you still have the VP2SleepInterval setting in cumulus.ini, set at 1100? If so, that will be adding 1.1 seconds to the update interval. I've added some code which automatically does an interval of 1500 (1.5 seconds) if one isn't specified, so perhaps you could try stopping Cumulus and setting the value to 1 (so my code doesn't take effect)? Then you should be getting an update closer to the normal 2 or 3 seconds.

This is getting even more complicated...

I changed VP2SleepInterval to be 1

Updates are now every 3-4 seconds.

And now I am getting the errors logged again "Data input appears to have stopped - check your station and connections"

What next?

[steve]

Updates are now every 3-4 seconds.

That's similar to the old DLL with the old firmware. On my system, most of the updates are 3 seconds (using the Cumulus status bar time) with one or two updates each minute taking 4 seconds.

[steve]

And now I am getting the errors logged again "Data input appears to have stopped - check your station and connections"

What next?

I don't know; Davis claim there isn't a problem with the latest DLL and the latest firmware.

Perhaps I should contact them; perhaps I'm doing something wrong that up until now hasn't been an issue. Clearly something has changed.

[steve]

I've contacted Davis, and had a reply; my query has been passed on to an engineer.

[JimDantin]

I've contacted Davis, and had a reply; my query has been passed on to an engineer.

A milestone - we now have communications established about the communications problem!

I appreciate the update, Joe.

[Vossenberg]

Steve,

Yesterday I was not able to check the board. If you want I can test using the 2.42 DLL as well. Just to have more information.
I am very happy with the fact that you have managed to get actual contact with Davis

I will follow this topic very closely!

Update: Just installed the new version. The interval is about 3 seconds with the VP2sleepinterval=1 statement. I will post later on to check if the error still occurs.

Greetings,

Pascal

[Vossenberg]

Steve,

Also over here the same error occurs:

9-1-2013 17:53:00 : Data input appears to have stopped - check your station and connections
9-1-2013 17:54:00 : Data input appears to have stopped - check your station and connections

Kind Regards,

Pascal

[steve]

Let's hope Davis can come up with something...

[optrex]

Let's hope Davis can come up with something...

Steve,

I've started getting this issue with a VP2+. The only change I've made is to go from 1.9.2 to 1.9.3 in the New Year. Nothing else has been changed.

[steve]

I've started getting this issue with a VP2+.

What firmware version?

[optrex]

I've started getting this issue with a VP2+.

What firmware version?

1.90

[steve]

I've started getting this issue with a VP2+.

What firmware version?

1.90

Then it's not the same problem (with firmware 3.0). To avoid confusion in this thread, please start another thread in the Davis section, and attach your zipped up diags folder.

Thanks.