Hi, can anyone offer a little advice to a Davis Pro 2 user, please.

For some reason my USB Weather Envoy data logger is no longer
communicating with the computer. It used to run via Com Port 4, but
now the diagnostics can't find it on any port. I've changed the
batteries in both the console (which is working fine) and the data
logger.
The data logger beeps twice (as it's supposed to) when the batteries
are replaced, so I'm rather up a gum tree.
It just stopped recording data, yesterday for no apparent reason. I'd
be glad of any suggestions from fellow users.

CK

Really need some further background info to offer any useful advice.
For example, presumably you've tried rebooting the PC,
unplugging/replugging the USB connection? While it's not totally out
of the question, the 6510 loggers rarely suffer any hardware failure
(surges, eg lightning-induced, aside) so it's much more likely to be a
PC-related issue.

You might be interested to take a look at our new VP knowledgebase,
currently in beta - see:

http://vp-kb.wikispaces.com

NB Quite a lot of this content is publicly viewable but full wiki
access requires registration.

John Dann
www.weatherstations.co.uk

On Mon, 8 Jun 2009 12:35:36 -0700 (PDT),
wrote:

...I've changed the
batteries in both the console (which is working fine) and the data
logger.

I should also have added that this needs clarifying too. The data
logger doesn't have any batteries of its own so this doesn't really
make sense. Are you suggesting that you run both a standard console
(ie with the LCD screen) AND an Envoy console, with the data logger
being fitted to the latter? If this is the case then are both consoles
receiving direct from the ISS or, for example, is the main console set
to retransmit data to the Envoy console?

Especially if you don't have a simple configuration (ie just one
console and ISS), the more detail you can provide about the
installation, the easier it might be to suggest a diagnosis. We don't
even know for sure whether it's a wireless or a cabled system for
instance - I'm guessing it must be wireless but it is just a guess.

JGD

On 9 June, 09:52, John Dann wrote:
On Mon, 8 Jun 2009 12:35:36 -0700 (PDT),
wrote:

...I've changed the
batteries in both the console (which is working fine) and the data
logger.

I should also have added that this needs clarifying too. The data
logger doesn't have any batteries of its own so this doesn't really
make sense. Are you suggesting that you run both a standard console
(ie with the LCD screen) AND an Envoy console, with the data logger
being fitted to the latter? If this is the case then are both consoles
receiving direct from the ISS or, for example, is the main console set
to retransmit data to the Envoy console?

Especially if you don't have a simple configuration (ie just one
console and ISS), the more detail you can provide about the
installation, the easier it might be to suggest a diagnosis. We don't
even know for sure whether it's a wireless or a cabled system for
instance - I'm guessing it must be wireless but it is just a guess.

JGD

Thanks for the reply, John - I expected to be required to give more
info, my post was really an opener to see if anyone had had similar
experiences with Windows ports.

I run the Advantage Pro2 wireless, with a wireless repeater. The
console retransmits wirelessly to the Weather Envoy data logger. This
is connected to the PC via a USB cable. The data logger DOES have its
own batteries - 3 x AA, which I have replaced. As I said, all was
working perfectly until a day or so ago, when logging unexpectedly
stopped.

I run Weatherlink v5.8.2, and if I run the Console diagnostics, the
results a
Firmware ...
Total Received 0
Total Resynchs 0
Total Misses 0
Max in a Row 0
CRC Errors 0
% Good ...
Console Battery 192.00v

None of which makes much sense.

When I run the Communications Port menu, Auto Detect searches the Com
Ports and returns the message " No station could be found. Try once
more to make sure."
If I run Test, with the USB option checked, it tells me that "No Davis
USB device connected"

The LCD console is working perfectly.

I really don't know what other useful information I can provide, but
I'm quite happy to resort to E mail rather than clutter up the
newsgroup.

Thanks for your help

CK

On 9 June, 10:35, wrote:
On 9 June, 09:52, John Dann wrote:





On Mon, 8 Jun 2009 12:35:36 -0700 (PDT),
wrote:

...I've changed the
batteries in both the console (which is working fine) and the data
logger.

I should also have added that this needs clarifying too. The data
logger doesn't have any batteries of its own so this doesn't really
make sense. Are you suggesting that you run both a standard console
(ie with the LCD screen) AND an Envoy console, with the data logger
being fitted to the latter? If this is the case then are both consoles
receiving direct from the ISS or, for example, is the main console set
to retransmit data to the Envoy console?

Especially if you don't have a simple configuration (ie just one
console and ISS), the more detail you can provide about the
installation, the easier it might be to suggest a diagnosis. We don't
even know for sure whether it's a wireless or a cabled system for
instance - I'm guessing it must be wireless but it is just a guess.

JGD

Thanks for the reply, John - I expected to be required to give more
info, my post was really an opener to see if anyone had had similar
experiences with Windows ports.

I run the Advantage Pro2 wireless, with a wireless repeater. *The
console retransmits wirelessly to the Weather Envoy data logger. *This
is connected to the PC via a USB cable. *The data logger DOES have its
own batteries - 3 x AA, which I have replaced. *As I said, all was
working perfectly until a day or so ago, when logging unexpectedly
stopped.

I run Weatherlink v5.8.2, and if I run the Console diagnostics, the
results a
Firmware * * * * *...
Total Received * 0
Total Resynchs *0
Total Misses * * 0
Max in a Row * 0
CRC Errors * * 0
% Good * * * * *...
Console Battery *192.00v

None of which makes much sense.

When I run the Communications Port menu, *Auto Detect searches the Com
Ports and returns the message " No station could be found. *Try once
more to make sure."
If I run Test, with the USB option checked, it tells me that "No Davis
USB device connected"

The LCD console is working perfectly.

I really don't know what other useful information I can provide, but
I'm quite happy to resort to E mail rather than clutter up the
newsgroup.

Thanks for your help

CK- Hide quoted text -

- Show quoted text -

Further to my last, It's the Weather Envoy that has the batteries, the
actual data logger is a small plug-in device inside! The Weather
Envoy does communicate with the console, the problem appears to lie
between the Weather Envoy and the computer.

CK

But have you unplugged/replugged the USB lead and rebooted the PC? (I
dare say that you will probably have tried this but I just need to be
sure.)

(This is just a matter of terminology admittedly, but the Envoy is
generally regarded as a type of console and it's the Envoy unit that
has the batteries in. The data logger is just the small separate
module that plugs into the Envoy or other console and so, strictly
speaking, the logger has no batteries of its own.)

There's a lot more VP-related info on the vp-kb link that I suggested.

JGD

On 9 June, 10:53, John Dann wrote:
But have you unplugged/replugged the USB lead and rebooted the PC? (I
dare say that you will probably have tried this but I just need to be
sure.)

(This is just a matter of terminology admittedly, but the Envoy is
generally regarded as a type of console and it's the Envoy unit that
has the batteries in. The data logger is just the small separate
module that plugs into the Envoy or other console and so, strictly
speaking, the logger has no batteries of its own.)

There's a lot more VP-related info on the vp-kb link that I suggested.

JGD

Thanks for the link, and yes, I have unplugged the USB cable and
rebooted - no difference. It used to happily use Com Port 4, but
doesn't any more...

CK

On Tue, 9 Jun 2009 02:36:35 -0700 (PDT),
wrote:

Thanks for the link, and yes, I have unplugged the USB cable and
rebooted - no difference. It used to happily use Com Port 4, but
doesn't any more...

OK, I would check:

1. Whether the VCP driver is still correctly loaded (If you look in
Windows Device Manager can you see a CP210x entry under the Ports
section, along with a com port number that it's assigned to use?)

2. If [1] looks OK then - assuming this is feasible, at least for test
purposes - move the data logger to the main console and see if it
works successfully there. (Power down the consoles _fully_ while
you're doing this.

John Dann
www.weatherstations.co.uk

On 9 June, 12:11, John Dann wrote:
On Tue, 9 Jun 2009 02:36:35 -0700 (PDT),
wrote:

Thanks for the link, and yes, I have unplugged the USB cable and
rebooted - no difference. *It used to happily use Com Port 4, but
doesn't any more...

OK, I would check:

1. Whether the VCP driver is still correctly loaded (If you look in
Windows Device Manager can you see a CP210x entry under the Ports
section, along with a com port number that it's assigned to use?)

2. If [1] looks OK then - assuming this is feasible, at least for test
purposes - move the data logger to the main console and see if it
works successfully there. (Power down the consoles _fully_ while
you're doing this.

John Dannwww.weatherstations.co.uk

Thanks, John. Well, Device Manager does show an exclamation mark
against the CP2102 USB to UART Bridge Controller, and further
examination reveals that the drivers are not installed. Are these
drivers a Windows XP component, or a WeatherLink component?
Attempting to reinstall either automatically or manually results in
failure, even with the Weatherlink CD installed. I am beginning to
hate Windows...

CK

CK

On Tue, 9 Jun 2009 05:11:05 -0700 (PDT),
wrote:

Thanks, John. Well, Device Manager does show an exclamation mark
against the CP2102 USB to UART Bridge Controller, and further
examination reveals that the drivers are not installed. Are these
drivers a Windows XP component, or a WeatherLink component?
Attempting to reinstall either automatically or manually results in
failure, even with the Weatherlink CD installed.

Hmm, that's an interesting one. Did the USB/WL link just stop working
with nothing else done to the PC or is it possible that some other
application, specific Windows update or piece of hardware has recently
been installed on the PC?

The CP210x USB driver is not a Windows component but is actually
written by Silicon Labs (the maker of the USB chip inside the logger).
A copy of this driver is supplied on the Weatherlink CD.

What happens in Device Manager when you unplug/replug the logger
connection. Does the CP210x entry change at all?

Can you see an option to uninstall the driver in Add/Remove Programs?

I would suggest:

Download the latest WL version (v5.8.3) from the Davis website
(http://www.davisnet.com/support/weat...ware_sftwr.asp) and install
that, taking care to point the update to the same install folder that
you're currently using. This should reinstall the driver, assuming
that the existing copy hasn't somehow become corrupted or
write-protected. (This shouldn't affect any of your WL data files but
it's obviously a sensible precaution to have these backed up
somewhere.)

John Dann
www.weatherstations.co.uk