Data request problems with PCE-FWS 20 (WH-1080)

[Wirus]

Yesterday I got a Asus WL-330N3G and a PCE-FWS 20 which should be a WS-1080 clone
http://www.pce-instruments.com/deutsch/ ... _listpos=1

Flashing of the Asus and also start & connection of the weather station works easy, however meteobridge doesn´t request any data. In system tab the message is

logger (05.05.2013 14:28:02): data logger (version 4.9u, build 1885) started.
logger (05.05.2013 14:28:05): connect station 0 (WH-1080/3080 via USB HID).
logger (05.05.2013 14:29:33): unexpected 0 bytes delivered from weather station 0 (WH-1080/3080)
logger (05.05.2013 14:29:33): disconnect station 0 (WH-1080/3080).

Any idea why this happen and what to do against?

Remark: I´ve cleared the memory and set up a log save time of 5 min. Data will be shown in easyweather but not in the meteobridge.

[admin]

Could you please set the mark on "system" tab (to allow me to login remotely) and power cycle the unit? I guess your MAC ends with 6D:5C?

[Wirus]

ould you please set the mark on "system" tab (to allow me to login remotely) and power cycle the unit?

Done

I guess your MAC ends with 6D:5C?

You are right

[admin]

standard password does not apply. could you please reset to defaults or send to "info(at)meteobridge.com"?

[Wirus]

Sorry for the effort - i´ve reset it to standard.

[admin]

ok, I can login and USB HID reads do fail for an unknown reason, hm...
Could you please disconnect the weather station from power AND meteobridge
AND remove the batteries? Please wait a minute and then connect/power on
the station again. WH1080 and clones do sometimes lock up and I would like
to have this ruled out before I dig deeper. Thanks.

[Wirus]

Done
I´ve done the following:
- unplug all devices
- remove batteries
- wait app. 5 minutes
- put in batteries
- wait app. 5 minutes
- plug in bridge power
- wait app. 5 minutes
- plug in bridge to weather station

Unfortunately the situation is unchaned

[admin]

I can't login right now. could you please do a power cycle, again.

[Wirus]

Done.
Looks like the Asus hung. Last message was from 17:38

logger (05.05.2013 17:38:33): connect station 0 (WH-1080/3080 via USB HID).

Remark: Maybe the block of the Asus was due the DCF of the station has changed time after connecting the asus

[admin]

could you please do another power cycle, sorry, I locked out myself again...

[Wirus]

Done.

[admin]

I did a couple of tests. Unfortunately, I cannot get rid of the problem,
that data cannot be read from the station. That is very strange as I just
tested locally to read out USB HID data from a TE923 station (also connected
via USB HID) with a WL-330N3G equipped with the same firmware and
application stack as you use. I don't have a WH1080 to make 1:1 tests
right now, but the same drivers are proven to work on Meteohubs.

Could you please connect your WH1080 to a PC to check that the station is
working correctly via USB? Do you use any range extenders to connect
the station via USB or is a plain simple cable?

[Wirus]

Could you please connect your WH1080 to a PC to check that the station is
working correctly via USB?

I can do that in the evening today, but it worked yesterday noon without problems.

Do you use any range extenders to connect the station via USB or is a plain simple cable?

The WL-330N3G and also the station are brand new and connected together with the original cable coming with the weather station. This cable works without problems using EasyWeater @ Win7pro.

The WL-330N3G is powered by the original power plug and the original cable @ the microUSB port. It is connected to a FritzBox 7390 via WLAN and recognized well

Additional remark: The station doesn´t work with WinXP due driver problems / lack of HID driver

[admin]

Additional remark: The station doesn´t work with WinXP due driver problems / lack of HID driver

But I guess it comes with some SW that allows to use it with the PC?

[Wirus]

But I guess it comes with some SW that allows to use it with the PC?

Yes, of course. It´s Easyweather 6.2 and it does work with Win7pro (tested a few minutes ago)

Problem is only with WinXP die lack of driver.