USB and TCP/IP support

[pinto]

I wonder if it's something to do with firmware versions, mine is quite old, I think: April 10 2006 (EU) is what it says. Yours?

Steve

Februari 12 2008 V1.75 (EU)

[pinto]

Firmware it is, I think
From http://www.davisnet.com/support/weather ... _frmwr.asp

Firmware version 1.75
1. Fixed a bug that causes the console to display incorrect yearly rain values when the unit of measure for rain is set to millimeters.
2. Supports direct updates using USB or TCP/IP connections.

[steve]

Firmware it is, I think
From http://www.davisnet.com/support/weather ... _frmwr.asp

Firmware version 1.75
1. Fixed a bug that causes the console to display incorrect yearly rain values when the unit of measure for rain is set to millimeters.
2. Supports direct updates using USB or TCP/IP connections.

I think that just means you can update the firmware using USB or TCP/IP.

I could update my firmware and see if that fixes it. But the problem then is that some people may have the pre-Nov '05 firmware where they can't easily update to the latest firmware.

Steve

[steve]

Steve mine is a VP1 with a non-Davis datalogger. The only difference in the logger is that it is supposed to keep a larger amount of data than the usual Davis one, they are no longer manufactured though. Yes mine goes via VVP, its the only way I can run it as I need WD to support my website at present since Cumulus cannot do all I need.

Is there any way you can try it temporarily by-passing VVP? Don't do it if it's a lot of trouble or is likely to screw up any data!

Anyone else reading this feel like having a go? Just needs an ordinary, directly connected serial port VP/VP2.

Steve

[broadstairs]

Is there any way you can try it temporarily by-passing VVP? Don't do it if it's a lot of trouble or is likely to screw up any data!

Anyone else reading this feel like having a go? Just needs an ordinary, directly connected serial port VP/VP2.

Steve

I'd prefer not to as my website is updated close to real time by WD and have several other sites which carry my weather banner. NO WD means no weather data on main site. If no one else has a go I might try for a short while later tonight for say 30 minutes or so, but it would also be on a W2K system not XP as that is what my weather PC runs. I'm hoping some others may jump on this and give it a go.

Stuart

[steve]

That's OK, Stuart, no problem. I'm doing some experiments with a serial sniffer, and I'll continue with that. I suspect the problem isn't related to the VP2 itself anyway, but the way the serial port is handled.

Steve

[steve]

I seem to have a workaround. I've added a call to the function in the DLL to set the timeouts, just after I tell it to open the com port. This seems to allow it to work even after a reboot. This is despite the fact that (a) I'm setting the timeouts to the default value anyway, and (b) the call returns an error. Oh well.

I'll wait to see if it still works from a cold start tomorrow morning.

Steve

[steviegal]

Hi Steve,

I am having no end of problems since moving to build 701 as you have noticed after initial download of data when starting Cumulus no more data read.

Also on closing Cumulus the program fails to respond and the only way to close is via Task Manager.

I also tried to switch to USB and restart Cumulus but just get Error message.

Is there anyway I can download and revert to a pre 7** build I don't want to go back to 1.8.4?

Thanks

Steve G

PS. My VP2 is latest firmware.

[steve]

If you could bear with me, I'll have a version uploaded very soon (this morning) which should fix this.

What error message do you get with USB? Could you let me have the diags file for the USB attempt?

Steve

[steviegal]

Steve,

Have now loaded build 717 and now Cumulus a lot better (downloading data OK and program closing OK) but still unable to
switch my VP2 to USB (one thought should I set my com port to zero before changing to USB).

Have attached bug report and Diags file.

Steve G

[steve]

I'm a bit confused (as usual ) - the diags file is for a successful run where you have it set to serial, yes? I assume the bug report is when you set it to USB? the crash is in the call to set the timeouts, which is the thing I added to fix the serial problem. I guess I could take it out of the USB path. Does it crash like this every time you set it to USB?

And you're running Windows 7, yes? Shouldn't matter, but just another complication to bear in mind.

Thanks for trying it.

Steve

[steviegal]

Steve,

The bug report is for USB start, happens everytime.

I have attached another diags file for a USB start, just in case I sent you an incorrect file last time.

Yes am running Windows 7.

I have also just noticed my rainfall total for today is incorrect against the VP2. (should be 4.6mm but Cumulus says 0.8mm)

Steve G

[steve]

That diags file is for another serial port start up. But it doesn't matter anyway, if it's crashing every time. I'll move the call to set the timeouts so it doesn't do it for USB. Although why the DLL should crash because of that, only Davis know.

Regarding the rainfall total, Cumulus is getting the start of day counter as 149.4 from its own logs and the total so far as 4.4, but then when it reads the current counter from the station, that says 150. Clearly the station counter must have been higher than that at some point for Cumulus to get the 4.4. I can't explain that. You could look in Feb09log.txt and see what the rainfall counter values are in there since midnight.

Steve

[steviegal]

Steve,

I think Cumulus got confused around the time I was restarting from serial to USB because
looking at the logs the errors crept in then. Anyway all running smoothly now.

Thanks again for your outstanding support.

Steve G

[broadstairs]

Steve running build 720 last night I noticed that it had stopped receiving data, it was just when I was about to close it all down to go to bed so I'm afraid that I did not get any diags or check any files. I did stop and restart it quickly but it did not read any archive records as far as I could tell and it had been stopped for about 15-20 mins. Now it is possible that I had caused a problem on my local IP network on this PC because I was installing VirtualBox and setting that up to access the IP network. I'm just wondering what timeouts and recovery you have built in at present for IP connectivity. I'll run it again today and see if anything happens.

Stuart