Configuring a RN-131/134/171/174 Wifi-Serial device

Plugins & Plugin Development General Plugin Discussion
1

@guessed and others!

Well I had time today to try to connect the WiFiy RN-134. I was able to find a DC charger (6 V) and connect it to the board for power. I then powered it up with the Jumper 1 in place to put the unit in Adhoc mode. It booted up and I found it on my network and connected to it. I then used my terminal connector to connect to the module and I have been messing with it for several hours. It seems to log me out after a while and then will not let me back in. I have to jumper 1 on and off 5 times to rest the module and then log back in again??? Anyway, no problem with that. I have the settings you gave me from the post above, but what I cannot figure out is how the connection to Vera works. I think I have to connect the module to my home network (can’t get this to work). I scan and find my network and then I try to set the key or passphrase and for the key it says bad command??? I set the passphrase (I have a netgear dual router). Usually we connect by using the key. However, it will not accept my command to set the key. It did take the passphrase but then when I tried to join it did not work??? Anyway, I think what I am supposed to do is connect the module to my home network and assign a static IP address to the RN-134 so that it always has the some one on my home computer. Question: Why does the module need to access my home network? Can I control the DSC 1832 from my home network??? Some other reason? Then I think I have to somehow set the Ad Hoc network on the RN-134 to be the Vera 3 network. Is this correct? Do I also have to set the module to have a static IP address (and turn off DHCP?) and then give this static IP address to Vera? Then I think I have to go back into Vera and program the DSC Panel (or system device???) anyway the IT-100 to have this RN-134 static IP address also (or not?). Is there anything else I need to do? Also, I know I probably have the configuration logic wrong some where!! Please help!!! Thank you so very much!

Can Vera 3 be setup as an Access Point? I read on the forum that it cannot. I am assuming that as an access point the Vera would be part of my home network and therefore have broader reach.

Also, how do you set up so that the footer has your equipment listed? Thanks!

2

[quote=“MTB, post:1, topic:172082”]@guessed and others!

Well I had time today to try to connect the WiFiy RN-134. I was able to find a DC charger (6 V) and connect it to the board for power. I then powered it up with the Jumper 1 in place to put the unit in Adhoc mode. It booted up and I found it on my network and connected to it. I then used my terminal connector to connect to the module and I have been messing with it for several hours. It seems to log me out after a while and then will not let me back in. I have to jumper 1 on and off 5 times to rest the module and then log back in again???[/quote]
I’ve never played with the Jumpers. For configuration, I’ve always done it via it’s Serial interface, directly connected to my Mac. If you can Adhoc to it, you can also connect to it over port 2000 on it’s IP Address and configure it that way… without the serial interface (something you can block out through configuration also, if you were worried about security)

I think I have to connect the module to my home network (can't get this to work). I scan and find my network and then I try to set the key or passphrase and for the key it says bad command???
I'd need to know exactly the command you're running, and possibly the exact response text as well. The device has a very specific command syntax, so if there are any typo's, or missing keywords, it'll fail (and tell you about it)
I set the passphrase (I have a netgear dual router). Usually we connect by using the key. However, it will not accept my command to set the key. It did take the passphrase but then when I tried to join it did not work???? Anyway, I think what I am supposed to do is connect the module to my home network and assign a static IP address to the RN-134 so that it always has the some one on my home computer.

Question: Why does the module need to access my home network?


The module is a Wifi-based IP to Serial gateway. You’re going to plug the IT100 (a Serial to DSC gateway) into it so that [effectively] you have an IP to DSC gateway (via various middlemen)

So the module needs to connect to “a” WiFi network. It could either be your standard home one, or any other one that you have setup that Vera is also connected to… since, ultimately, the DSC Alarm Plugin needs to connect to it, in order to be connected to the DSC Alarm Panel itself.

Can I control the DSC 1832 from my home network??? Some other reason?
Yes, the RN-134 "bridges" your Alarm Panel's IT100 onto your Home network so that Vera can connect to it. Technically, if you have a WiFi enabled Vera unit (Vera1, Vera2 or Vera3, but [i]not[/i] Vera Lite) you could setup a distinct WiFi channel that the RN-134 could connect to... again it just needs to be something that the Vera can use to connect to the RN-134.
Then I think I have to somehow set the Ad Hoc network on the RN-134 to be the Vera 3 network. Is this correct?
Adhoc is really just for configuring the RN-134 device. There are certain application use-cases for the RN-134 where it might permanently run in Adhoc mode.

eg. a WiFi server, where an iPhone or Android device (with WiFi) would initiate a connection directly.

But in this case, it’s not what we’re doing.

Do I also have to set the module to have a static IP address (and turn off DHCP?) and then give this static IP address to Vera?
I leave DHCP on the RN-134 enabled, and instead configure a Static IP Address in my household Router. I do this with all my devices, since it's a PITA to reconfigure them all when I change the subnets around in my house.... it gives me a central place to configure the IP Addresses of all my Network stuff, without having to remember how to manually reconfigure everything.
Then I think I have to go back into Vera and program the DSC Panel (or system device???) anyway the IT-100 to have this RN-134 static IP address also (or not?).
Once you've configured your home router to dole-out a static IP Address to the RN-134, and the RN-134 has been setup to connect to your home router (SSID, Passphrase and "WPA2" or whatever) then you should test that it's all working... at the baud rates that the IT-100 is expecting (9600 baud, from memory)

Only after all this stuff has been bench-validated would I recommend that you then go into the DSC Plugin’s configuration, and change it to connect to the RN-134’s Port 2000 connection

Can Vera 3 be setup as an Access Point? I read on the forum that it cannot. I am assuming that as an access point the Vera would be part of my home network and therefore have broader reach.
It would, but I'd strongly recommend get it working on your home network [i]first[/i]. Once you have it working there (which is an already working WiFi network) you can move it over to one hanging off the Vera3 unit.

The less moving parts/steps the easier it’ll be to understand what’s going on. Adding Vera 3’s Wifi channel in now will just complicate things until the basics are working.

Also, how do you set up so that the footer has your equipment listed? Thanks!
Certain forum features are disabled until you get out of Newbie status (currently, 25 posts). Once you reach that limit, more editing options are exposed to you in the Forum Profile page.
3

Thank you for your response!
I do not have a serial port on any of my Mac computers so I bought the cables to connect the RN-134 to my computers using a usb cable to serial cable and then a serial to 10 pin cable. However, when I plug the device directly into my Mac or Macbook pro the device does not show up in Finder under devices??? I also plugged the device into my PC and downloaded Tera Term. I plugged the cables into my open serial port and when I open Tera Term on Port 1 it is scrolling letters and numbers across the screen and I cannot stop it or type anything. I think this is the port for my monitor. The only other port that shows up under Tera is Port 4 but when I open this port I cannot type anything on the screen?? So I cannot put in telnet 169.254.1.1 2000. As I stated earlier I can start up the RN-134 in adhoc mode and see the device and open and start configuring it. However, after a bout a minute or so it kicks me out. Is there a timer setting that I can turn off so that I have enough time to configure the settings?
Here is what I get and what I have done when I use my Mac and Terminal to log on to the RN-134 and try to configure it.

[code]michael-browns-imac:~ Admin$ telnet 169.254.1.1 2000
Trying 169.254.1.1…
Connected to 169.254.1.1.
Escape character is ‘^]’.
HELLO$$$
CMD
show net
show net

SSid=Wifly-GSX-bd
Chan=1
Assoc=OK
Rate=12, 24Mb
Auth=OK
Mode=NONE
DHCP=OK,renew=-74
Boot=22416
Time=FAIL
Links=0

<2.23> show ssid
show said

Conns=1, WRX=3/26, WTX=7/200, RTRY=0, RTRYfail=0
URX=0, UTX=267, RXdrop=0, RXerr=0,
FlwSet=0, FlwClr=0
TX-UDP=0, netbufs=0, evt=0, adhoc_lost=0
Boots=1, Wdogs=0,E=111scan

<2.23> set wlan ssid brown$wifi
set wlan ssid brown$wifi

AOK
<2.23> set wlan phrase brownpool
set wlan phrase brownpool

AOK
<2.23> show net
show net

SSid=brown wifi
Chan=1
Assoc=OK
Rate=12, 24Mb
Auth=OK
Mode=NONE
DHCP=OK,renew=-173
Boot=22416
Time=FAIL
Links=0

<2.23> get wlan phrase
get wlan phrase

SSID=brown wifi
Chan=0
ExtAnt=0
Join=1
Auth=OPEN
Mask=0x1fff
Rate=12, 24 Mb
Linkmon=0
Passphrase=brownpool

<2.23> scan
scan

Disabling ADHOC
<2.23> IF=DOWN
DHCP=ON
IP=169.254.1.1:2000
NM=255.255.0.0
GW=0.0.0.0
Creating ADhoc network
ADhoc on brown wifi chan=1

SCAN:Found 4
Num SSID Ch RSSI Sec MAC Address Suites
1 Brown Wifi 01 -70 WEP e0:91:f5:87:a2:58 1104 2
2 Wifly-GSX-bd 01 -43 Open 00:06:66:14:e4:bd Adhoc 200 2
3 Brown Wifi 01 -31 WEP 00:26:f2:fa:f3:86 1100 7
4 estrogen&drama 06 -85 WPA_Mix c0:c1:c0:da:15:4b AES/TKIPM-TKIP 1104 0
Connected via Ad-Hoc on brown wifi
Using Static IP
IF=UP
DHCP=ON
IP=169.254.1.1:2000
NM=255.255.0.0
GW=0.0.0.0

<2.23> join #1
join #1Connection closed by foreign host.
michael-browns-imac:~ Admin$
[/code]
Question: It seems to show “Connected via Ad-Hoc on brown wifi” but I cannot find the Mac address of the RN-134 on my Router as a Connected Device. I placed the command “get mac” in earlier and it gave me the Mac address of the RN-134. Shouldn’t this number show up as a device that is connected to my home network?

Question: I tried to set up Vera 3 as a access point on my home network but it did not seem to work. However, since my attempt the Vera shows the WiFi light on. But I have a Vera(with my Vera serial number) network that shows up under “join networks”. I also have my home network. When I join Vera’s network I cannot get on the internet. How do I join the two networks so that when I set the static IP address for the RN-134 (if it ever shows up as connected on my router configuration) on my home network it will also be available with the same static address on my Vera 3. I have set my Vera 3 to have a static address already.

This is enough for now. Then we can address exactly how to configure the RN-134. Thanks for your patience with me!! Let me know what other info you need and I will try to get it for you. I really appreciate your help. I think you are about the only one that has ever got this to work. I do not think it will be that hard if I can get the connection to stay live for more than a minute or to quit dropping me when i try to join my home network. All the instruction in the RN manual tell me to do exactly what I am doing. Question: Is it not joining and dropping me because it is already joined to my network as it shows in the configure return language above??

4

I’ve split this post-series out, since this part is focused on setting up the Wifi-Serial dongle. The DSC thread can then be used for DSC specific questions, and this one for stuff relating to the configuration of the Roving Networks RN-131/171/134/174 style WiFi-Serial boards.

5

A few quick comments:
a) Do you really have a space in the SSID Name, and should it be mixed-case?
b) Is your WiFi really OPEN or is it actually using WPA/WPA2 or (god forbid) WEP?
c) It looks like it’s running in ADHOC mode, instead of connecting to your Home Network
d) I don’t think you’ve set [tt]comm open[/tt] to [tt]0[/tt] since you’re getting a HELLO response on TCP Connect

The Auth stuff is probably what’s causing it not to connect to your Network.

6

[quote=“guessed, post:5, topic:172082”]A few quick comments:
a) Do you really have a space in the SSID Name, and should it be mixed-case?[/quote]Yes, but I changed it to remove the space and it made no difference. I will try it without the cap’s.

b) Is your WiFi really OPEN or is it actually using WPA/WPA2 or (god forbid) WEP?
No my wifi is not open. It is a combination WPA1 and WPA2. I tried the command to set it to 3 which is the command for this auth. Still did not work.
c) It looks like it's running in ADHOC mode, instead of connecting to your Home Network.
Yes. I have reset the said and phrase to match my home network including the auth but still no connection. I have had the RN-134 rename itself as a device with the same name as my home network but I still cannot see the RN-134 mac address on my router. I have also sent in a help request to Roving Network!
d) I don't think you've set [tt]comm open[/tt] to [tt]0[/tt] since you're getting a *HELLO* response on TCP Connect.
I actually have tried every combination - setting the comm open and closed first before setting the ssid and phrase and also after. Neither worked. I have tried every combination I can think of and read almost all of the 85+ page manual. I have tried almost everything I can think of. It just cannot be this hard to connect to my home network. I have followed the directions in the manual 50 times with no connection!!!! I am ready to throw in the towel after 5 days and probably 40 hours of messing with this. Not worth it! Probably need to just run the cable and see if I can get that to work!!! Any other suggestions?????? I have bought all the cables and connected it to my Mac, Macbook Pro, and PC. Nothing works following the exact instructions and all my guesses. I have tried it in adhoc also in every conceiviable combination. No luck!!
The Auth stuff is probably what's causing it not to connect to your Network.
The only thing I can think of is that my Netgear router is a combination of 2.4 GHz and 5 Ghz with two different auth modes (will not allow both to be the same). Can I just try to connect the RN-134 directly to the Vera 3???
7

When I configured mine, I’ve done it over USB-Serial cable config. This allows you to remain attached to the RN-device, through all of the config steps of getting onto your Network.

If something goes amiss, you don’t get disconnected and/or have to force the device to reset and start from scratch.

To do this, I use a USB-Serial cable, a Null Modem adapter and a Gender-bender (you’ll see the trio in my initial pics). After the initial setup, you don’t need these bits anymore, and I tend to have this sort of stuff floating around so I don’t have to run out and buy all these bits (hopefully you can borrow them from someone if you don’t already have them)

On a Mac, when you plugin a USB-Serial device, you’ll get something along the lines of /dev/tty.PL2303*. I don’t have it handy right now, so the exact path misses me, and yours will be slightly different…

From that, I run something like the following to connect at 9600 baud:

screen /dev/tty.PL2303-0000201A 9600

NOTE: Use [Ctrl A][Ctrl ] to get out!!!

You’ll get the same interface you’re getting through Adhoc mode, but will be able to experiment a lot more. There are other papers showing the [Network-side] setup, similar to what I was referencing up front. Perhaps one like this will make it clearer:
wifly - Cookbook | Mbed

It really is just a few commands to get onto the Network, at least for me.

For reference, my Network is Airport Express units, WPA2-PSK @2.4GHz (only). It’s also a little odd that the WiFi scan that you ran is reporting WEP for your [2] Networks. Not sure what that’s about.

8

Wow!!! I spent about 10 hours so far today and made a lot of progress. Based on Guessed’s comments (they really helped me think thru what I had that might be wrong). I bought all the cables including the null modem and connected the RN-134 up to my PC. I had already loaded the Tera Term software. I connected it up using the USB to Serial cable. Was able to find the device in Tera and get into program mode. Guessed, you were correct, it was much more stable while directly connected. The first thing I did was update the firmware. Mine was 2.23! I had thought that it was up to date since I just purchased it, but was wrong. So a lot of the information in the Manual that I thought I had - I really didn’t. Anyway, got the RN-134 connected to my home network. In order to do this I renamed my home network to be all lower case with no spaces. I also had to turn off the security and leave it open. I have a repeater setup and due to this I cannot use any security higher than WEP. When trying to connect with WEP configured the RN-134 would not connect. It would not accept my key. So for now I have the home network open. Configured the rest of the language that Guessed suggested above and saved. I then was able to open a terminal on my Mac and telnet into the RN-134 (on my PC) and talk to the RN-134. However I could not talk back from the Terminal on my PC to the Mac Terminal session??? I also set a static IP address for the RN-134 on my network. I then connected the RN-134 to the IT-100. I then went into the DSC Panel in Vera 3 to the Advanced tab and set the IP to be the static IP address and port 2000. When I saved and reloaded, the DSC Panel open port alarm went away and the software reloaded. I thought I was finally there. However, after a minute or so I got an alarm on the DSC Panel that says Lua Failure. Any ideas??? Thanks for all the help! I think I am getting really close!

9

A few pre-flight checks, just after you have it connected to the Network but before you enter the details into Vera (or Vera might need to be off at the time you do this)

a) Connect a Mac/PC to the Serial Port, and use TELNET from the Mac to the other end ([tt]telnet 192.168.1.x 2000[/tt]).
Of course, both “ends” can be on the same machine, to make it easier to test.
You should be able to type characters on one end, and see them come out the other end… and the other way around of course. You should use the BAUD Rate that you’re planning to use on the IT100 when you’re testing in this manner.

b) Assuming (a) completes, connect the IT100 to the “Serial” end of the mix
From here, you should be able to send test characters to the IT100, and get it to respond. Sending it a “000” sequence should result in a “500” result code.
If this doesn’t work, then the potential issues are either an incorrect cable, or an incorrect baud rate setting.

10

[quote=“guessed, post:9, topic:172082”]A few pre-flight checks, just after you have it connected to the Network but before you enter the details into Vera (or Vera might need to be off at the time you do this)

a) Connect a Mac/PC to the Serial Port, and use TELNET from the Mac to the other end ([tt]telnet 192.168.1.x 2000[/tt]).[/quote]
Yes, I did this from my PC telnet session (USB to Serial to RN-134) to my Mac telnet session connecting back to the RN-134. I typed in the Mac session and the PC session responded with the same letters. However, I could not type in the PC session and get a response in the Mac session. Is this OK? Is there another way to test the other way? I tried Pira port redirector and could not get it to work. I do not know the port of my PC just the IP address. I looked on line for info on how to find the port but no luck. I tried 2000 and several others but got error messages.

Of course, both "ends" can be on the same machine, to make it easier to test. You should be able to type characters on one end, and see them come out the other end... and the other way around of course. You should use the BAUD Rate that you're planning to use on the IT100 when you're testing in this manner.
Yes, I am pretty sure I used 9600 for both.
b) Assuming (a) completes, connect the IT100 to the "Serial" end of the mix From here, you should be able to send test characters to the IT100, and get it to respond. Sending it a "000" sequence should result in a "500" result code.
OK, not sure I understand this. I disconnect the RN-134 and cables from my PC and connect them to the IT-100. How will I be able to see the response on the IT-100? Won't I loose the session on my PC when I unplug the RN-134? Do I send the "000 from the Mac session? Where will I look to see the "500" result?
If this doesn't work, then the potential issues are either an incorrect cable, or an incorrect baud rate setting.

I set the baud rate at 9600 when configuring the RN-134 (so I should be good there! I can check when I put it back on the PC. I think the default on the DSC integration board is 9600 also. How do I check this?

Thanks so much! What a trip!!! But almost there!!

11

Roughly, if A can send stuff to B over the Serial link, then B can send stuff back to A.

If you’re typing chars on A and they show up on B, but the other way around isn’t working then all likelihood the Serial cable isn’t wired correctly.

This needs to work before hooking up the IT100, otherwise we’ll only get 1/2 of the data (we’ll send commands, and get no responses, or we’ll see responses but not be able to send commands)

Once that part is working correctly, then we effectively put the IT100 at the “Serial port” end of the RN-13x, and then send it commands from the Telnet session (Network end) as you’re already doing to Port 2000. A “test” command would be sending something like “000” to the IT100, whereupon it’ll respond with a “500” response string.

9600 baud it the correct speed:
UI5 – DSC Alarm Panel

12

OK! I set it up again last night and it is communicating both ways except that when I type on the PC (Tera Term) screen the letters do not show up on the screen but the letters do show up on the Mac in the telnet. I do not know if this is normal or if I have to change a setting. So it is talking both ways! Will this work? Do I need to do the port redirect test also?

[quote] Once that part is working correctly, then we effectively put the IT100 at the “Serial port” end of the RN-13x, and then send it commands from the Telnet session (Network end) as you’re already doing to Port 2000. A “test” command would be sending something like “000” to the IT100, whereupon it’ll respond with a “500” response string. [quote/]

To do this I would have the IT-100 actually connected to RN-134 and connected to the DSC panel (actual panel not in Vera). It this how it is done? Or can this be done virtually so how?

13

“local echo” is usually just a terminal program option, nothing to worry about. If its sending chars in both directions, then your set to connect the IT100 to the other end , send the 000 test chars from your Mac (telnet to port 2000 again) to the device and have it provide the response. (this checks the cabling setup for the IT100, since it may not need the gender bender and/or Null modem)

14

Well, I connected the RN-134 to the IT-100 and when I try to remote connect thru mac terminal it will not connect. It times out. I tried it with the null modem and without. The RN-134 shows up on my network with the static IP address. I am also still getting the Lua failure! Any suggestions?

Is there anything else I need to do in Vera 3 under the DSC Panel as far as settings go? I just put the IP address and port in this format:
192.168.1.1:2000. Anything else?

If the other test worked does that prove that the wiring is correct or could the wiring still be off. I bought a serial to 10 pin cable and it was prewired.

One other thought. I had to change my network name and security to get the RN-134 to connect to it. How do I reset these values in Vera 3? Do I have to do a factory reset or can I just change the settings somehow?

I checked my pin connections between the IT-100 and the RN-134 and they are straight thru - pins 2,3 and 5. So do I need the null modem or not? I tried plugging the IT-100 straight into the Vera (I had this working) and it will not work now???

I disconnected the RN-134 from the IT-100 and talented into it off of my network and all worked well. I checked the settings and all look good. Any suggestions???

15

[quote=“MTB, post:14, topic:172082”]Well, I connected the RN-134 to the IT-100 and when I try to remote connect thru mac terminal it will not connect. It times out. I tried it with the null modem and without. The RN-134 shows up on my network with the static IP address. I am also still getting the Lua failure! Any suggestions?

Is there anything else I need to do in Vera 3 under the DSC Panel as far as settings go? I just put the IP address and port in this format:
192.168.1.1:2000. Anything else? [/quote]
The RN-134 can only accept 1 (one) TCP connection at a time. In order to bench test it with the Mac, you cannot have Vera configured to talk to it… effectively they’ll both try and connect to it, and the first one will win (likely, Vera)

We need to bench test it first with the Mac, before moving on to Vera. You’ll need to blank-out the IP setting you’ve put into Vera, and then (Save) so that it won’t attempt to connect.

Then the TCP from your Mac to the RN-134 will work again, and you can proceed with the bench test.

PS: 192.168.1.1 is probably your router, it’ll be something more like 192.168.1.45:2000 (or wherever you set the static IP for the RN-134)

If the other test worked does that prove that the wiring is correct or could the wiring still be off. I bought a serial to 10 pin cable and it was prewired.
Hard to know without the Bench test. IIRC, I just plugged the IT100 directly into the [Male] RS-232 connector from the RN-134 (via a 10PIN Hdr -> RS232 Male cable).... but it's been a while, so I can't be sure that I didn't stick in a Null Modem or whatever.
One other thought. I had to change my network name and security to get the RN-134 to connect to it. How do I reset these values in Vera 3? Do I have to do a factory reset or can I just change the settings somehow?
I don't understand the question. I was assuming your Vera unit is connected to your Network over ethernet. If it's connected over WiFi, then you'll need to re-enter those settings into Vera's [Wifi Client] configuration UI. I've never done that, but I'm sure others will chime in with the appropriate details as needed.
I checked my pin connections between the IT-100 and the RN-134 and they are straight thru - pins 2,3 and 5. So do I need the null modem or not?
That's the bit I can't remember. These things have always been resilient for me, so I tent to "try" configurations.
I tried plugging the IT-100 straight into the Vera (I had this working) and it will not work now?????
Presumably because you switched Vera to use IP instead of Serial-attachment in the config as it cannot be set to "both". If it's still not working, check the Baud rate settings of the [assigned] Serial port to ensure they're 9600-N-8-1.
I disconnected the RN-134 from the IT-100 and talented into it off of my network and all worked well. I checked the settings and all look good.
I'm not sure what you did, looks like something auto-corrected the spelling... in an odd way
16

Thank you for your reply. I think we are getting to the root of my problem. This is why I kept asking about the ability of the Vera 3 to work on my network as an access point on my network. My thought is that then the Vera 3 network would merge with mine home network into one network. Is this how the access point would work (if Vera 3 had that capability)? Right now I have two networks, my home network and the one Vera setup when I initially booted it up when it was connected to my home network. My Vera 3 is connected to my home network thru a ethernet cable for the internet service so that it can be accessed thru the internet. Vera 3 shows up as connected to my home network under attached devices. The RN-134 is programed to connect to my home network when it boots up and it shows up as an attached device on my home network. So in my mind the Vera 3 and RN-134 are connected to my network but I need the data from the RN-134 to be on the Vera network not mine home network. I hope this makes sense. If the RN-134 can only talk to one network, then I would think I should program it to join the Vera 3 network. So I would program the ssid, security, passphrase, etc for the Vera network into the RN-134 instead of my home network. Where can I get this information for the Vera network? Or since they are both connected to my home network will the data transfer as expected?

I did what you said about removing the IP address from Vera (DSC Panel) and retesting the RN-134 with my Mac again last night. That is what the auto correct messed up - telnet instead of talented. It worked just as before. I also checked the configuration settings of the RN-134. I am pretty sure everything is setup correctly. On the IP address, yes I did not want to put the real address in so I used the generic router address just to show the format. Mine is actually 10.0.0.13:2000.

So I think the problem is getting the RN-134 (DSC) data onto the Vera 3 network instead of my home network. Or if they are both showing up on my home network as attached devices will they be able to talk.

So to run the bench test, I will attach the TI-100 and the RN-134 and not program the DSC panel with the RN-134 IP address and telnet into the RN-134 and type in the command “000” enter. Is this correct? And the RN-134 should send me back onto the screen 500. Do I have this right?

Thanks again. I really appreciate the help.

17

Yes.

Do this on your home network. Let’s get it working, end-to-end, before you try Vera’s network.

Once it’s been validated, in pieces and end-to-end, you’ll have all the tools you need to try it on other networks on your own, and to diagnose the various problems that occur along the way.

Introducing those now just complicates things…

18

I performed the communication test and got the following response. Sent 000 and received back 50196.

90100032 Date Time JUL 19/12 3:31p24
000
50196
000
50196
550153207191299
90100032 Date Time JUL 19/12 3:32p25
90100032 Date Time JUL 19/12 3:33p26
90100032 Date Time JUL 19/12 3:34p27
90100032 Date Time JUL 19/12 3:35p28

The IT-100 manual says: For 500 - This command indicates that a Command has been received by IT-100. This command is always the first response to a command from the application unless there is a checksum error then a Command Error (501) is sent. For 501 - This command indicates that a Command has been received with a bad checksum. No additional data is available.

So I am communicating both ways but apparently the command needs more information or numbers after the 000 for the command to make sense. Or is there some kind of error in the wiring or programing?

I found this statement in the Appendix (C I think)These instructions assume that you are connected to an IT-100 and are able to send a Poll (00090) command and receive an Acknowledgment (50000025) command.

I put in 00090 and received back the 50000025. I think I am good to go!

19

You are good to go. You can disconnect you Mac from the Telnet connection to the RN-134, and connect Vera up. It should now correctly recognize it, and load the Labels (etc)

20

OK, I connected everything up and put the IP address in the DSC Panel device created by the app. All of the error messages I had before (open port and Lua Failure) are now gone in the Dashboard. However, I cannot arm the system from the Dashboard or see the system arm when I arm the security system at the keypad. I still think it has to do with Vera 3 having its own network that is separate from my home network. Is this how others have their systems setup? Two networks??

UPDATE: I reloaded my connection thru UI5 and tried arming the DSC 1832 again. IT WORKS!!! I see the change in status as the system arms. My scene to turn it on and off also works!!!

Thank you Guessed for all your help and patience!!! Now on to the next system!