Since once out of every dozen reboots my Caddx connection gets lost I purchased myself a Wiznet SR110.
Who can give me some pointers on how to set this up?
Thanks in advance,
Hans
I use one of these. The initial setup is a mite fiddly. If you have a Windows machine then you can run the setup tool that Wiznet provides. Connect the Ethernet port to your LAN, power it up, and run the setup tool. Most options are fine left at the default. You will need to set the baud rate, data bits, parity and stop bits just as you have been doing on the Vera. If you don’t have a Windows machine, and Wine wouldn’t work for me, then there is a little Python tool floating around that does the trick.
Oddly, the Wiznet seems to come set with a static IP address rather than using DHCP. If the default subnet doesn’t match your LAN’s then there is some additional fiddling needed to get your computer to communicate with it. It’s definitely worthwhile changing the Wiznet to use DHCP and then adding a static DHCP reservation to your router so the Wiznet gets the same IP address every time it starts up on your LAN.
There is a guide to running the Windows setup software on Wiznet’s site. Since there are non-Vera uses for this device you may also find help on other forums or on the wider Internet.
Once you’ve done this setup the Wiznet behaves flawlessly. I’ve never had to reboot it.
Give it a try and tell us where you get stuck.
So I gave it a static address in my range and also set this address in the Vera serial setting. See attached screenshots.
Unfortunately it does not work…
Hope you can help me out here, it is probably something very obvious I am doing wrong?
Hans
Searched some more and came up with alternative WizNet setting as server with server ip set to 0.0.0.0 and port 0. Also tried removing the Serial and setting the advanced tab of the Caddx to 192.168.1.240:5000, also no luck…
Then replaced the Wiznet with an other unit, no result. The Caddx works with the USB cable.
Log says:
04/25/15 14:16:04.314 luup_log:13: Initializing Caddx NX-584 <0x2b4e6680>
50 04/25/15 14:16:04.335 luup_log:13: Opening serial port <0x2b4e6680>
24 04/25/15 14:16:04.336 Device_Basic::m_iLastContactFailed_set 13 = 0 <0x2b4e6680>
06 04/25/15 14:16:04.336 Device_Variable::m_szValue_set device: 13 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailure was: 1 now: 0 #hooks: 0 upnp: 0 skip: 0 v:0xe4f498/NONE duplicate:0 <0x2b4e6680>
10 04/25/15 14:16:04.337 UserData::m_iDataVersion_Variables_incr CommFailure user data 964146001 variables 964146073 <0x2b4e6680>
10 04/25/15 14:16:04.337 UserData::DataIsDirty UpdateStateList was 1 incr 0 user data 964146001 variables 964146073 <0x2b4e6680>
10 04/25/15 14:16:04.338 AlarmManager::AddRelativeAlarm current time 1429964164 delay 0 type 45 <0x2b4e6680>
10 04/25/15 14:16:04.339 AlarmManager::AddAbsoluteAlarm alarm 0x9684f8 entry 0xf09f70 id 91 type 45 param=(nil) entry->when: 1429964164 time: 1429964164 bCancelFirst 0=0 <0x2b4e6680>
06 04/25/15 14:16:04.339 Device_Variable::m_szValue_set device: 13 service: urn:micasaverde-com:serviceId:HaDevice1 variable: CommFailureTime was: 1429964075 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x2b4e6680>
10 04/25/15 14:16:04.340 UserData::m_iDataVersion_Variables_incr CommFailureTime user data 964146001 variables 964146074 <0x2b4e6680>
10 04/25/15 14:16:04.341 UserData::DataIsDirty UpdateStateList was 1 incr 0 user data 964146001 variables 964146074 <0x2b4e6680>
22 04/25/15 14:16:04.352 Alert::Alert 0x116b8f8 <0x2b4e6680>
10 04/25/15 14:16:04.352 AlarmManager::AddRelativeAlarm current time 1429964164 delay 0 type 155 <0x2b4e6680>
02 04/25/15 14:16:04.355 GetSunriseSunset error#1 sunrise: 1429849497/2015-04-24 06:24:57 sunset: 1429901700/2015-04-24 20:55:00 midnight: 1429912800/14125036 <0x2aba8000>
31 04/25/15 14:16:04.341 AlarmManager::Run 0x9684f8 notified of a change entry 0x116c110 id 90 deleted 0 <0x2b2e6680>
31 04/25/15 14:16:04.362 AlarmManager::Run callback for alarm 0x9684f8 entry 0xf09f70 type 45 id 91 param=(nil) entry->when: 1429964164 time: 1429964164 tnum: 1 slow 0 tardy 0 <0x2b2e6680>
10 04/25/15 14:16:04.363 UserData::m_iDataVersion_Variables_incr count user data 964146001 variables 964146075 <0x2b2e6680>
31 04/25/15 14:16:04.364 AlarmManager::Run finish callback for alarm 0x9684f8 entry 0xf09f70 type 45 id 91 param=(nil) entry->when: 1429964164 time: 1429964164 tnum: 1 slow 0 duration 0 <0x2b2e6680>
10 04/25/15 14:16:04.365 AlarmManager::AddAbsoluteAlarm alarm 0x9684f8 entry 0xde32c0 id 92 type 155 param=0x116b8f8 entry->when: 1429964164 time: 1429964164 bCancelFirst 0=0 <0x2b4e6680>
25 04/25/15 14:16:04.365 luup_io_intercept 13 <0x2b4e6680>
25 04/25/15 14:16:04.367 luup_io_intercept 13 <0x2b4e6680>
01 04/25/15 14:16:04.369 luup_io_write NULL port 0x11d08c8 size 5 <0x2b4e6680>
10 04/25/15 14:16:04.370 XXX-ADDMESSAGE-1 (null) / Missing port = 2 timeout 0/-1429964164 <0x2b4e6680>
10 04/25/15 14:16:04.370 XXX-UpdateSystemMessagesTasks now 1=Caddx NX584 Security System[13]: Running Lua Startup timeout 0 (-1429964164) count: 2pend:Running Lua Startup/err:(null)/done:(null) <0x2b4e6680>
10 04/25/15 14:16:04.371 UserData::m_iDataVersion_Variables_incr short sys message user data 964146001 variables 964146076 <0x2b4e6680>
10 04/25/15 14:16:04.382 UserData::m_iDataVersion_Variables_incr AddMessage_Dev user data 964146001 variables 964146077 <0x2b4e6680>
10 04/25/15 14:16:04.382 XXX-ALARM_UPATE_DEVICE_INCR Device_Basic::AddMessage 13=964146077 timeout <Invalid date 0> Missing port <0x2b4e6680>
01 04/25/15 14:16:04.383 lu_io_read NULL port 0x11d08c8 <0x2b4e6680>
01 04/25/15 14:16:04.384 luup_io_write NULL port 0x11d08c8 size 5 <0x2b4e6680>
01 04/25/15 14:16:04.384 lu_io_read NULL port 0x11d08c8 <0x2b4e6680>
01 04/25/15 14:16:04.385 luup_io_write NULL port 0x11d08c8 size 5 <0x2b4e6680>
01 04/25/15 14:16:04.386 lu_io_read NULL port 0x11d08c8 <0x2b4e6680>
01 04/25/15 14:16:04.387 LuaInterface::CallFunction_Startup-2 device 13 function caddxInitialize failed Caddx NX584 Security System[13] with return false <0x2b4e6680>
10
Who can help out here?
Hans
Have you tried to connect to the Wiznet using HyperTerminal to see if it is communicating? Also after you have hooked it up to your Caddx you may need to kill power to the Caddx panel. Also, I dropped my baud rate down to 9600. Also note that I did not set the serial port in the serial port config under apps.
Thanks for your response rstrouse!
Killing the power to the Caddx panel would get me a call from the security company, why would killing the power to the caddx panel help?
Hans
I tried to connect with Hyperterminal to the wiznet without the serial line connected and could not…
Hans
HansW, let’s try and resolve some of the confusion. You’re making multiple changes at once so you may well be jumping over the correct solution.
Let’s check that both Vera and the Wiznet are on the same subnet. You’ve set the WizNet to the static address 192.168.1.240 with a subnet mask of 255.255.255.0. What are the corresponding two values for your Vera? You can see this information on Vera from Settings > Net & Wi-Fi > Troubleshoot Network. Here’s mine:
=== IP Configuration ===
eth0 Link encap:Ethernet HWaddr 00:0E:8F:7B:72:A3
inet addr:192.168.81.1 Bcast:192.168.81.255 Mask:255.255.255.0
eth0:0 Link encap:Ethernet HWaddr 00:0E:8F:7B:72:A3
inet addr:10.191.21.248 Bcast:10.191.255.255 Mask:255.255.0.0
inet addr:127.0.0.1 Mask:255.0.0.0
For me the answers are 10.191.21.248 and 255.255.0.0.
Take Vera out of the picture by connecting the WizNet to both your security system’s serial cable and to your LAN. Then using a terminal program (you said you use Hyperterminal), connect to the Wiznet. Do a walk test to trigger a few motion sensors. You should see output on the terminal program. Garbage output, but output nonetheless. If you don’t, then you’ve still got some configuration to do on the Wiznet and no amount of fiddling on the Vera UI will help.
If you are using an IP-serial gateway, there should be no mention of the Caddx plugin in the Vera serial port configuration page. The IP address/port fields in that page are red herrings and should not be filled in in this case. The only place you should mention the IP address and port is on the plugin’s advanced tab (see the attached screenshot).
Well Futzle, you are very right!
And I do apologize for my crossposts but I was desperate after again spending so many hours solving something that should be an easy thing.
But then again, that’s Vera and in spite of that, I love it when it works since there is no limit apparently to what it can do as long as you are willing to spend entire weekends with it.
I am not sure how this can be improved but sometimes it takes me hundreds of messages to read on this forum and the documentation, wiki, and all other places where I can find stuff over Vera, just to solve a simple issue.
I guess my wiznet was broken because when I did the what I now found out are the proper steps to get it to work with the second board it just worked while the first board does not respond to Hyperterminal.
I will look into that later today and also make a neat description on the steps to take to set up the Wiznet.
I have made an instruction on how to set up the Wiznet here: http://forum.micasaverde.com/index.php/topic,31963.0.html
Thanks for your help and your great plugin!
Hans
Hello,
I discovered that the latest Wiznet 110 SR firmware is not version 5.13 but instead 0.84 and informed wiznet about it. Downgrading to 5.11 makes both my units function well.
Hans
I’m glad you are up and running. Sincere thanks for posting the howto topic; that should be useful to those who come along afterwards.
[quote=“HansW, post:6, topic:187035”]Thanks for your response rstrouse!
Killing the power to the Caddx panel would get me a call from the security company, why would killing the power to the caddx panel help?
Hans[/quote]
I found that I my NX was just sending a response repeatedly through the RS232 when I was originally configuring the NX584. Resetting the panel cleared it up. I assume that it was looking for an ACK. I suppose killing the power to the 584 could have cured it as well.
I just recently tried to switch over to a wiznet 110SR. Previously I was using a USB to serial adapter to my nX8e using Vera 3 and UI5. I also used a null modem adapter and the connection worked perfectly. When I switched to VERA Pus and Ui7 I noticed that every 24 hours the serial communication was lost to the vera and had to reload the engine …The baud is 9600 8,n,1
Now with the Wiznet 110 SR on the Vera Plus UI7 I have still not been able to get the serial communications to connect. I got the IP connections working with the same IP address 192.168.0.240 and port 5000 settings tested the ping on the wiznet config app and the communications on IP are working as i get packets sent and received. The modem also shows on the same IP listing the mac address of the wiznet which tells me the device and the router have handshaken. Furthermore I was able to change the firmware to V.81 on wiznet per someones recent post. Also using same null modem cable between the GE ribbon and wiznet device as before which worked via USB.
But the serial communications on the wiznet says not connected. The baud rates is same as the GE Panel 9600 set for binary on the segment for that. Also the GE Plugin I setup under the advanced tab the ip address 192.168.0.240:5000 and saved that parameter.
Plugin still says “failed to setup interface” and also in the child window is says missing port can’t detect device.
I am not sure what other things I should correct to get the wiznet to communicate to the GE and VERA, any suggestions much appreciated.
[quote]I just recently tried to switch over to a wiznet 110SR. Previously I was using a USB to serial adapter to my nX8e using Vera 3 and UI5. I also used a null modem adapter and the connection worked perfectly. When I switched to VERA Pus and Ui7 I noticed that every 24 hours the serial communication was lost to the vera and had to reload the engine …The baud is 9600 8,n,1
Now with the Wiznet 110 SR on the Vera Plus UI7 I have still not been able to get the serial communications to connect. I got the IP connections working with the same IP address 192.168.0.240 and port 5000 settings tested the ping on the wiznet config app and the communications on IP are working as i get packets sent and received. The modem also shows on the same IP listing the mac address of the wiznet which tells me the device and the router have handshaken. Furthermore I was able to change the firmware to V.81 on wiznet per someones recent post. Also using same null modem cable between the GE ribbon and wiznet device as before which worked via USB.
But the serial communications on the wiznet says not connected. The baud rates is same as the GE Panel 9600 set for binary on the segment for that. Also the GE Plugin I setup under the advanced tab the ip address 192.168.0.240:5000 and saved that parameter.
Plugin still says “failed to setup interface” and also in the child window is says missing port can’t detect device.
I am not sure what other things I should correct to get the wiznet to communicate to the GE and VERA, any suggestions much appreciated.
/quote]
Further more, I used Putty to check and when selecting telnet and entering the Ip and Port to and run the terminal which showed the ip address on the top, then I restarted the wizen config program and refreshed , the adapter came up and it shows connected. I am not sure why by using putty, the wiznet connects and stays connected? while in binary mode on the panel id so see repeating characters including a Y moving across the screen. I then closed the putty screen.
I went back to the VERA Unit and then made sure the IP and Port we’re entered in advanced 192,168,0,240:5000 but the unit now says failed to setup interface after reloading the engine…
I checked and IP address and port are correctly stated in the GE plugin advanced tab…
Not sure what else to check next, appreciate feedback.
thanks
You aren’t actually using commas between the octets on your ip address are you?
192,168,0,240:5000 → 192.168.0.240:5000
[quote]You aren’t actually using commas between the octets on your ip address are you?
192,168,0,240:5000 → 192.168.0.240:5000
/quote]
I am using periods on the ip address with the column for the port i.e. 192.168.0.240
Incidentally after running putty first I got the wiznet to show connected status… ( that was not the case had I not ran putty before) also checked out Serial communication between PC directly connected to wiznet and it checked out as well. I then went to the VERA 3 UI7 to connect , I was able to connect. Then checked the zones scan I found out that some zones scanned and displayed and the some did not show and said waiting.
Then when I went to reboot the vera engine… It ended up with the same exact settings not connecting to the wiznet. I checked via putty and the wizard showed connected. I also took the VERA3 UI7 and powered off and tried the same thing on the new VERA Plus and same settings and also the VERA Plus ge plug in is also not finding the device.
I have the ability to downgrade the VERA3 to UI5 (which works perfectly on the USB connection ) and re-test the wiznet connection as a baseline, then test it to a VERA EDGE UI7 (both USB and Wiznet) and then test to to the new VERA PLUS UI7 same two connection choices since I have all three to use. Ultimately I will move everything to VERA PLUS provided all elements work consistently as I step through these models.
But one thing that also has me in a quandary is how the wiznet connected status was activated only to the extent that i ran putty on telnet using the IP and Port of the wiznet device that kept the unit in connected status from that point on. Which I am not sure why the wiznet would not show connected without using Putty.
Looking for further input on both the connected status on the wizened as well as to why the connection worked to the VERA3 on UI7 and then when re-booted it lost and could not connect again. Maybe the wiznet had lost connection in the interim, will try again to get status up and see if the VERA connects successfully again.