MeteoBridge & WLIP interoperability

[Mattk]

I have searched but have not found many comments re the interoperability between MB & WLIP on the same network. Both appear to work fine together in uploading data to the respective end users.

What I have noticed is that with MB connected, WLIP web page is not reachable, disconnect MB and the WLIP webpage is accessible, is this normal and/or expected behaviour? Currently have WLIP as static IP & MB DHCP and yet to change to a static IP for MB. WLIP upload as set in MB is every 1 minute

With a local setup this is fairly easy to fix (simply disconnect MB) but in a remote situation what are the options in trying to reach the WLIP web page (not often needed but sometimes required) with MB also connected?

[Mattk]

Some more comments on this one.

With MB connected, from WeatherLink (v6.03) finding the logger via the TCP/IP Connection by Local Device ID is instantaneous, no problems. Web Download is fine apart from the typical hour (max) behind in the data. Download with Local Device ID checked worked for about the first 20 pages ok then went into retries and failed after the typical (max) 20 attempts. What this did do was create a wlk file (2058-03.wlk) and a single line to the data archive dated 19/3/58 with some fairly erroneous data values.

Anybody experienced anything similar?

[admin]

When having wlip enabled to upload to weatherlink in parallel to meteobridge operation, meteobridge pauses connection to wlip every x minutes for some time to allow the wlip to upload. During that period another program in the lan might be able to also connect to the wlip and to request data from it. But this will ofcourse crash, when meteobridge starts asking for data again.

Not sure if that is what you experienced, but knowing how meteobridge interacts with wlip might help you understanding the situation.

[alison3492]

Looks like you force them by static IP settings in the devices or at your router to identical IPs. That will make trouble.

[Mattk]

There is certainly no identical IP's, WLIP is static, MB is static but both a very different, all the PC's are DHCP so there are no IP conflcits on the network. There's obviously an almost realtime connection between the MB & WLIP which appears to not open any other windows of opportunity (for any lenth of time) for other devices to connect in. Not like say the NAS on the network where multiple PC's can share the same data source.

[wvdkuil]

I have searched but have not found many comments re the interoperability between MB & WLIP on the same network. Both appear to work fine together in uploading data to the respective end users.

What I have noticed is that with MB connected, WLIP web page is not reachable, disconnect MB and the WLIP webpage is accessible, is this normal and/or expected behaviour? Currently have WLIP as static IP & MB DHCP and yet to change to a static IP for MB. WLIP upload as set in MB is every 1 minute

With a local setup this is fairly easy to fix (simply disconnect MB) but in a remote situation what are the options in trying to reach the WLIP web page (not often needed but sometimes required) with MB also connected?

Just to make sure we are talking about the same thing.
A Weatherlink IP logger is a serial logger combined in one package with a serial to IP converter.
It can ONLY talk to one other network device at a time. So it is not a device like a NAS or a server to which multiple devices can talk at the same time.
The WLIP will not listen to other ports when it is used.

So when a computer or a MB is reading the data there is no way you can use a program to access the logger data also.
As MB is a decent device it has a setting to free the WLIP every minute or so. That way the WLIP can send the data to WL.com for further distribution.
In that time you could try to access the WLIP yourself but the Meteobridge will start talking again to the WLIP and mess up your communication.

This is normal behavior for this WLIP device and has nothing to do with static or dynamic adresses and so on. No way to connect two devices to any Davis logger without using a "man in the middle" device like Virtual VP.

Just another warning, please put the static Ip address on a piece of paper and connnect it to the WLIP. You will not be the first person on the fora to find a way to reconnect after a reset of the router where all other DHCP devices suddenly are in another network range.

If you want to make sure the WLIP always get the same IP address you should instruct your router to hand out the same address to the mac of the WLIP. Not specify a fixed IP address in the WLIP itself.

Wim