WIZNET 110 SR Serial to Ethernet converter setup instructions

Plugins & Plugin Development General Plugin Discussion
#1

SETUP instructions for WIZNET 110 SR

The WIZNET 110 SR Serial to Ethernet converter is a handy device if you want to connect serial devices to your Very.

It can be purchased in many on-line places for under 30 Euro’s, is supposed to be very stable and also very easy to set up.

Connect the board to your network with UTP, plugin your RS232 female cable and then a 5V 200mA Power supply which has one of these standard round 5mm plugs with + inside.

Then you need to download the configuration tool from the Wiznet site: http://www.wiznet.co.kr/UpLoad_Files/ReferenceFiles/WIZ1xxSR_config_v3.0.2_install.zip, unpack it and run it on a windows machine.

Hit search a few times until you see the unit and then on the network tab either choose DHCP and fix the address in your router if that is supported or choose a the Local IP address manually but make sure it is inside your network range but outside the DHCP range. Set the mask, usually to 255.255.255.0 and the address of your router. The operation mode can be set to server and the server address and port to 0.0.0.0 and 0 respectively.

On the serial tab you select the appropriate baudrate. Also you can if needed change the databit, parity, stopbit and flow values but they are usually as set, 8N1 and none.

The third tab you can leave alone. Hit the setting button and it should report success after which your unit is all set.

Now all is left is to enter the choosen Local IP address and port in the form x.x.x.x:port so for instance 192.168.1.240:5000 in the ip field of the advanced tab of the plugin which takes care of the serial device.

If you had the device connected to the Vera with a USB to serial cable before, then before removing the USB2Serial cable make sure to select a different device to it. I have learned that the setting may persist if you only remove the cable which will stop the device from using the new IP settings to find its serial port.

In case of any issues you can test using hyperterminal with the winsock interface set to the appropriate IP and port again. It should show the serial data although not necessarily in a readable format.

As you see this is all very straightforward and should be easy. If you run into a problem I will be happy to help.

HansW

#2

There is also an Android Application to configure the WIZNET 110. Check it out at [url=https://play.google.com/store/apps/details?id=iSwitchLLC.Wiznet.Configuration.Tool]https://play.google.com/store/apps/details?id=iSwitchLLC.Wiznet.Configuration.Tool[/url]

#3

Is there any reason why this process would not work with a 2 port Wiznet unit ?

http://www.shopwiznet.com/wiz125sr

#4

HansW

I connected my wiznet as per instructions and did not get a connected message tough ip successfully pings Though then I tested directly to my pc and can communicate via serial port

When I plugged back to the Ethernet with PC still connected via putty also get communications birth serial and ip

If I go back the router and connect the wiznet to both the router and the ge alarm serial interface I sometimes get a connect and sometimes it drops …using Vera Plus UI7

Any suggestions…

#5

[quote=“dinochronos, post:4, topic:187078”]HansW

I connected my wiznet as per instructions and did not get a connected message tough ip successfully pings Though then I tested directly to my pc and can communicate via serial port

When I plugged back to the Ethernet with PC still connected via putty also get communications birth serial and ip

If I go back the router and connect the wiznet to both the router and the ge alarm serial interface I sometimes get a connect and sometimes it drops …using Vera Plus UI7

Any suggestions…[/quote]

Hans W and Futzle

I think I found the culprit with why the VERA device looses the communication with the Wiznet 110SR unexpectedly or when it is either caused by:

  1. Zwave Engine Reload
  2. Soft Reboot
    3.Power Cycle (sometimes works but loose connection)

Here is what I was able to reconfigure on the Wiznet Options TAB:

The Wiznet SR110 Options tab has a parameter in the inactivity section that allows the port to be either open indefinitely i.e. setting of 0 or for the port to close after x seconds in this case i have it set to 10 seconds.

The Wiznet instruction manual talks abut the settings in the options tab. Page 16 - Inactivity time , it defaults to 0 port open all the time, but when changed to 10 seconds as and example it allows the port to close and reopen when listening for additional data and then allows lump code to work.

What happens is that when the either a VERA EDGE Or the PLUS reloads via Zwave engine reload or soft reboot, by having a setting of 0 on the serial port, it stays open and therefore the GE CADDX Plugin does not allow it to configure because the port is busy.

When the VERA device is powered down, then it looses communication and closes the serial port sometimes and in that case it can at reboot reconnect and show connected in the wiznet configuration screen. Provided enough time for the serial port to close if the setting was 0 it took longer sometimes and would not work at all.

It seems then that the serial port closes after period of inactivity but it will reopen as soon as it senses serial data activity between the VERA and the Alarm serial connection and then working right. It also allows the LUUP code for the GE CADDX to allow it to reopen and configure since it does not get a sense that is it reserved open and unreachable at that point in time.

I will be testing this for consistency over the next week, but definitely something seems working correctly properly even when a LUUP engine reload is invoked. This has been running all day so far correctly.

Not sure if anyone else has ran into the this issue but for now I am seeing that there is something that actually works by changing the inactivity time from 0 default (always open port) to example 10 seconds of inactivity to allow port to be queried again correctly.

#6

This is going to cause a new problem in the context of the Caddx alarm: if the socket becomes disconnected through inactivity and then something happens on the alarm side (say, a zone is faulted), the Vera plugin isn’t going to find out about it.