Error 32.701 in beta 1007.

[ajcm]

Hello again:

I was using the beta 1006 and worked well with virtual vp but since upgrade to 1007 beta fails me once a day with error 32.701, I reset cumulus but continues with error 32.701, so I must restart the pc. I connect the cumulus via tcp/ip with From virtual vp, using port 5512 and I changed to the first 5511 of the virtual vp.

I will add the bugreporter to tell me what the problem is or maybe I should upgrade to the 1008 beta?

Thanks and hope your answer.

[steve]

That file is from the 4th August, and the crash occurred just after you had clicked OK on the station settings form. It seemed to think it needed to open the serial port, so I don't know what settings you were changing to make it think that? Are you using TCP/IP or serial?

But it doesn't sound like this file is anything to do with this '32.701' error you're reporting. I don't even know what a 32.701 error is. Where are you seeing that?

Edit: You mean a '-32701 error', I think? It means that the Davis DLL can't talk to Virtual VP.

Do you get this at a particular time of day? Have you seen this thread - https://cumulus.hosiene.co.uk/viewtopic.php?f=4&t=5781

[ajcm]

Hello:

I use TCP/IP, in the cumulus settings I have set TCP IP, port 5511 and IP 127.0.0.1.

I have 3 programms connected to Virtual VP (VWS, Cumulus, Weatherlink) and the 3 programms are connected via TCP/IP with virtual vp..

Thanks.

[ajcm]

Hello again:

Today, the program returned to cumulus to the error, as I add information to you that other programs connected to the Virtual VP still working, but I must restart the virtual vp to run the program cumulus.

The error also 32,701 tells me to check connections but the connections are always the same.

I should also say that the options "Restart if unplugged" and "Restart if data stops" were selected and then deselected have to see how it works cumulus.

Thanks.

[steve]

The error means that the Davis DLL which Cumulus uses cannot get a response from Virtual VP. Do you get the error when you start Cumulus, or at other times (while Cumulus is running)?

What value have you set for VP2SleepInterval?

[ajcm]

quote="steve"The error means that the Davis DLL which Cumulus uses cannot get a response from Virtual VP. Do you get the error when you start Cumulus, or at other times (while Cumulus is running)?

-For example now the program works fine and suddenly tomorrow I see my website on the internet is not updated, so I from my place of work with my laptop pc remotely access to the weather station PC and see that the program cumulus appears with the message cumulus error, and you can not connect to the station, ie it has lost connection and could not be reconnected and the cumulus program every time I try open it I get this error, and remains so until I restart virtual VP, and it works well again. As you have seen when I sent you the bugreport file August 4, this error does not create a new bugreport file.

quote="steve"What value have you set for VP2SleepInterval?

-I see in the file "cumulus.ini" but I do not see "VP2SleepInterval," that I see is "VP2PeriodicDisconnectInterval = 0"

Thanks Steve.

[steve]

-For example now the program works fine and suddenly tomorrow I see my website on the internet is not updated, so I from my place of work with my laptop pc remotely access to the weather station PC and see that the program cumulus appears with the message cumulus error, and you can not connect to the station, ie it has lost connection and could not be reconnected and the cumulus program every time I try open it I get this error, and remains so until I restart virtual VP, and it works well again.

Right - so it gets an error that says the DLL can't read the data from VirtualVP, so it restarts itself but then it can't reconnect anyway.

-I see in the file "cumulus.ini" , plus I do not see "VP2SleepInterval,"

You have to add it. See the readme.txt file.

[ajcm]

Ok, assuming I can add it what values ​​I need put?

Nothing all is ok, in the readme is all clear:

If you use VirtualVP, it is recommended that you edit the
cumulus.ini file (created after you run Cumulus for the first
time) and in the [Station] section, add a line:

VP2SleepInterval = 1100

Is the same if I put "VP2SleepInterval = 1100" or "VP2SleepInterval=1100" ?

Thanks.

[steve]

Is the same if I put "VP2SleepInterval = 1100" or "VP2SleepInterval=1100" ?

Yes.

[duke]

Unfortunately I did not find the sleep interval to help, I have the same problem as stated in the other thread. This is not a Problem caused by Cumulus and although Steve is extremely helpful I suggest you do a search for problems relating to running WL (the Davis DLL) and VVP together. It shouldn't take long for you to realise WL & VVP don't like each other. Other people are experiencing the same problem with software other than Cumulus.

From what I read I beleive WL causes VVP to hang which then prevents Cumulus or other software accessing the logger.

Duke

To save you a little leg work, here's one for you: http://www.wxforum.net/index.php?topic=8353.0

[ajcm]

Mr. Duke:

I have a 3 software connected to Virtual VP (Weatherlink, VWS and cumulus), but the program was a failed Cumulus, the other 2 programs were working well. Now I added the line cumulus.ini "VP2SleepInterval = 1100" as Steve told me and we'll see if it fails more. But if you fail you what is WeatherLink, the problem will be at the WL and not in the cumulus.