How to make Vera recognize your USB-to-Serial Adapter

hello all,

need some help with my usb to Serial connection.
I am trying to connect my Vera light to my Caddx Alarm system and cant seem to get the usb to serial recognized.
I managed to understand how to log onto vera via putty and run the required commands.

this is what i get

root@MiOS_35102760:~# dmesg > /tmp/dmesg-post
root@MiOS_35102760:~# diff -u /tmp/dmesg-pre /tmp/dmesg-post
— /tmp/dmesg-pre
+++ /tmp/dmesg-post
@@ -167,3 +167,4 @@
JFFS2 notice: (375) check_node_data: wrong data CRC in data node at 0x005a1ca4: read 0x148d3253, calculated 0x1a98721e.
JFFS2 notice: (375) check_node_data: wrong data CRC in data node at 0x0032f7a4: read 0x1463a5e3, calculated 0x5b00e93b.
ramips-wdt: timeout value 60 must be 0 < timeout < 25
+usb 2-1: new full speed USB device using rt3883-ohci and address 2

any advice?

thanks a lot

alexk, those JFFS messages may be coincidental (but they are a worry). You may find that they spontaneously appear in the dmesg output even without you messing with USB ports. For the moment, ignore them.

The rt3883-ohci note confirms that you’ve got an electrical connection between the USB adapter and the Vera. The fact that there are no further messages shows that the adapter isn’t one that Linux knows about. So the next step is to identify the vendor and product strings.

Run the lsusb command twice, once without and once with your adapter connected. Any difference in the output?

(What is your adapter, by the way? Did they say what chipset it used?)

Hi Futzle,

Thanks for the answer much appreciated.

firstly. while i am an electronic engineer by degree it has been a long time since I did anything technical (switched to marketing) so pls be gentle. :o

now on to the issue at hand.

If the JFFS messages relate to the zwave devices which make up the network i wouldn’t worry (yet) as I am doing all my installation on a block of wood with switches(test bed) so that i learn how everything works before I install them behind my switches. So from time to time the Nodes dissapear because i unplug the test bed.

If the error message isnt related to above then lets see latter.

on to the serial connection (with the NX584 i am trying to achieve)
I only understood vera has a preference for speicific serial connections last night :). I have two cables already from previous pcs so I will try both. So far i only tried one.

Q1. When doing all the testing etc. Should the usb to serial adapter be connected to the end device or not? (the NX 584 in this case)
Q2. If yes (or for latter use) do i need to do something to the nx to switch the tx and rx of the cable or should it work as is?
Q3. As I never did get into linux could you clarify what command exactly? (when you guys say run XXXX does it translates to type in the string after run at the command prompt?

thanks again and i hope to have more info by tonight!

Alex

Alex,

lsusb is a command, yes. At the prompt, type those five characters and press Enter. Case is important.

For the moment there is little point connecting the NX-584. Just leave the serial DB9 end dangling loose.

When it comes to connecting the NX-584 you need to ensure that the Transmit and Receive pins are swapped an odd number of times, so that the Transmit of one connects to the Receive of the other. Null modem cables include a built-in swap. Gender changers and straight-through cables generally do not. Jiggling the jumpers on the NX-584 constitute a swap. In practice, you either change all of the NX-584 jumpers, or none of them. One of these options won’t work. With any luck, the other one does.

re command got it (the enter part wasnt necessary) :smiley:

ok will disconnect nx-584.

and will test having switched the jumpers (most probably)

thanks!

hello again.

long story short.
tried one of the cables i had - according to windows it is manufactured by wch.cn and no further info offered. it didnt work. I tried a second usb serial cable i got my hands on (prolific) and it was recognized.

so i got that far.

installed nx-584 app and connected the cable. now at first i got a message saying failed to connect or register (something like that) and then i switched all the pins (4 of them) on the card. now the message on Vera is reading: Caddx NX584 Security System[11] : Running Lua Startup.

it has been stuck there for 30 mins or so.

does this means the connection is correct? ie usb serial is connected? does it mean that the tx and rx are correctly connected?
Depending on if this message means everything is conected (any way i can check it?) perhaps i should move the rest of the chat to the specific thread.

Wait! :slight_smile:

got it. changed the baud rate to 9600 and it worked. probably didnt change the nx584 setting after all.
so i am sorted for this thread!

Alex

this adapter works also

Startech.com 1 Port FTDI USB to Serial RS232 Adapter Cable with COM Retention bought from Amazon.co.uk
Item model number: ICUSB2321F
ASIN: B004ZMYTYC

I also had difficulties using a PL2302 based adapter with a Caddx alarm panel.

I bought a FTDI-based adapter manufactured by Sabrent, and it’s working well.
https://www.sparkfun.com/products/11304

I followed this guide to get my tripplite usb to serial adapter working. The vera recognized it as a pl2303 but I had to edit serproxy.ports to make the UI recognize the adapter. I installed the vizia RF emulator and started sending commands. I think I just need to buy a new cable (one of the ones that work), but I would like this one to work. this is from my log, does anyone have any advice as to how I can fix this? I’m just trying to send a basic command to the plugin, but the log keeps saying “recvfailed”

and when I try to send a test command i get

GetLuaInterface can’t find device type: -1/0xf22a60 str: (null) <0x2d02d680>
01 01/23/13 13:41:04.728 luup_io_write 0xf78bb0 args 1 <0x2d02d680>

Here’s the other messages:

02 01/23/13 13:28:57.545 ZWaveSerial::GetFrame 0x2bc2cf60 timed out now 0 m_listGetFramePending 0 <0x2bc2d680>
02 01/23/13 13:28:57.545 ZWaveJobHandler::SendDataAbort got m_iFrameID 0 <0x2bc2d680>
01 01/23/13 13:28:57.546 ZWJob_PollNode::Run job job#392 :pollnode #99 (0xed46b8) N:99 P:100 S:1 ZW_Send_Data to node 99 failed 1 req 0xe88250/1 abort m_iFrameID 0 <0x2bc2d680>
02 01/23/13 13:28:57.546 ZWJob_PollNode::PollFailed job job#392 :pollnode #99 (0xed46b8) N:99 P:100 S:1 node 99 battery 0 <0x2bc2d680>
06 01/23/13 13:28:57.546 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastError was: Poll failed now: Poll failed #hooks: 0 upnp: 0 v:0xf7f838/NONE duplicate:1 <0x2bc2d680>
04 01/23/13 13:28:57.547 <0x2bc2d680>
02 01/23/13 13:28:57.548 JobHandler::PurgeCompletedJobs purge job#392 :pollnode #99 (0xed46b8) N:99 P:100 S:2 pollnode #99 1 cmds status 2 <0x2bc2d680>
02 01/23/13 13:29:10.101 LOG_CHECK_MEMORY_LEAK pMem start 0x1075000 now 0x1081000 last 0x105b000 leaked 49152 LEAK this:155648 start:155648 to 0x1081000 <0x2ba2d680>
02 01/23/13 13:29:25.102 ZW_Send_Data node 100 USING ROUTE 255.114.101.100 <0x2bc2d680>
04 01/23/13 13:29:25.245 <0x2ba2d680>
02 01/23/13 13:29:53.512 IOPort::Run RecvFailed 0 close 13 <0x2d82d680>
02 01/23/13 13:29:55.102 ZW_Send_Data node 41 USING ROUTE 255.105.99.101 <0x2bc2d680>
04 01/23/13 13:29:55.285 <0x2ba2d680>
02 01/23/13 13:30:00.100 Energy::LogEnergyUsageOnServer <0x2b82d680>
02 01/23/13 13:30:00.101 Energy::LogEnergyUsageOnServer 2013-01-23 13:30:00 <0x2b82d680>
02 01/23/13 13:30:02.556 IOPort::Run RecvFailed 0 close 13 <0x2d82d680>
02 01/23/13 13:30:07.578 IOPort::Run RecvFailed 0 close 13 <0x2d82d680>
02 01/23/13 13:30:12.600 IOPort::Run RecvFailed 0 close 13 <0x2d82d680>
02 01/23/13 13:30:17.620 IOPort::Run RecvFailed 0 close 13 <0x2d82d680>

I think you’re best off buying a FTDI adapter. I have had no end of problems with the PL2303, regardless of OS. I was using one at work with Windows 7 for the serial console on Cisco networking gear, and it would drop connections there as well. The FTDI is the most failsafe way to go.

I have the StarTech FTDI Cable (ICUSB232FTN) and it appears to be recognized OK, but I am not able to communicate with the CADDX NX-8 via the NX-584 home automation board.

After connecting cable, DMESG shows:

usb 2-1: new full speed USB device using rt3883-ohci and address 3 ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected usb 2-1: Detected FT232RL usb 2-1: Number of endpoints 2 usb 2-1: Endpoint 1 MaxPacketSize 64 usb 2-1: Endpoint 2 MaxPacketSize 64 usb 2-1: Setting MaxPacketSize 64 usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

And that’s it. All good, and fully recognized?

I have the Vera Lite, Plugin and the NX all configured for the same 38400 baud rate. The CADDX plugin and Luaa code starts fine. But I can not get a response from the NX via the CADDX plugin. Before I seek help in the plugin forum, I would sure appreciate a confirmation if my USB/Serial connection is set up properly, and how else I can test it.

Thanks!
[url=http://www.amazon.com/StarTech-com-Modem-Serial-Adapter-ICUSB232FTN/dp/B008634VJY]http://www.amazon.com/StarTech-com-Modem-Serial-Adapter-ICUSB232FTN/dp/B008634VJY[/url]

Wait! :wink:

I encountered the exact same situation as AlexK. I discovered the NX was still configured for 9600 baud after I had reprogrammed it for 38400. Although my change was echoed back properly on the LCD keypad, after exiting, it obviously wasn’t saved. Maybe I missed some important step to save NX 584 changes that I didn’t find in the documentation?

Anyway, after setting up all components for 9600, connectivity is fine. Add another model of StarTech FTDI to the “works” list.

Now, does anyone know why it wouldn’t save? Because if I don’t know how to save NX programming changes, I’m going to have to hope all the defaults are OK. (ASCII(?), Transition-based broadcasting(?),etc.)

For me I need the Vera Lite to recognize my mbed !
It see it as an USB Flash disk
I know for Windows, there is a special driver to load
[url=http://mbed.org/handbook/Windows-serial-configuration]| Mbed

I have the following log when I plug the mbed in the Vera USB port:

[code]root@MiOS_xxxxxx:~# dmesg > /tmp/dmesg-pre
root@MiOS_xxxxxx:~# dmesg > /tmp/dmesg-post
root@MiOS_xxxxxx:~# diff -u /tmp/dmesg-pre /tmp/dmesg-post
— /tmp/dmesg-pre
+++ /tmp/dmesg-post
@@ -203,3 +203,16 @@
eth0: link up (100Mbps/Full duplex)
eth0: link down
eth0: link up (100Mbps/Full duplex)
+usb 2-1: new full speed USB device using rt3883-ohci and address 4
+scsi2 : usb-storage 2-1:1.0
+cdc_acm 2-1:1.1: ttyACM0: USB ACM device
+scsi 2:0:0:0: Direct-Access MBED microcontrolleur 1.0 PQ: 0 ANSI: 2
+sd 2:0:0:0: Attached scsi generic sg0 type 0
+sd 2:0:0:0: [sda] 4096 512-byte logical blocks: (2.09 MB/2.00 MiB)
+sd 2:0:0:0: [sda] Write Protect is off
+sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
+sd 2:0:0:0: [sda] Assuming drive cache: write through
+sd 2:0:0:0: [sda] Assuming drive cache: write through

  • sda:
    +sd 2:0:0:0: [sda] Assuming drive cache: write through
    +sd 2:0:0:0: [sda] Attached SCSI removable disk[/code]

Is it possible to see the Serial interface over the USB as in Windows ?

Thanks

It doesn’t look like there has been any effort to get OpenWrt and mbed to talk to each other. A Google search comes up empty. I think that you are out of luck unless you feel like writing a kernel module.

tried this

http://forum.micasaverde.com/index.php/topic,10000.msg68246.html#msg68246

as you can see my mbed is here :
+cdc_acm 2-1:1.1: ttyACM0: USB ACM device

os.execute(“ser2net -C 5000:raw:0:/dev/ttyACM0:115200”)
or directly on the ssh interface : ser2net -C 5000:raw:0:/dev/ttyACM0:115200
telnet 127.0.0.1 5000

it works (a little)
Update : It works well, after the first initialisation bad answer

root@MiOS_xxxxx:~# telnet 127.0.0.1 5000
j:1, Data: NET:0 ID:1 RH:57 T:22.5 TIME:Thu Jan 1 00:00:00 1970
$$$$1010ff93b29ba879c0db8b10031e043bd0e7j:1, Data: NET:0 ID:1 RH:56 T:22.6 TIME:Thu Jan 1 00:02:59 1970
j:2, Data: NET:0 ID:1 RH:56 T:22.6 TIME:Thu Jan 1 00:03:59 1970

relevent data in bold, and then freeze, no more data comes, but often, I got the
$$$$1010ff93b29ba879c0db8b10031e043bd0e7
msg ???

now how I can get these data to exploite the in a Module I can add to the web interface and integrate them for some scenes
(I measure temperature T:22.6 and humidity RH:56)

Thanks

Hello,

I have an USB to RS485 adapter that I’m trying to get to show up as a USB-serial device, but I don’t get the information mentioned in the article above but I get the following information:

usb 2-2: new full speed USB device using rt3883-ohci and address 2
usb 2-2: USB disconnect, address 2
usb 2-1: new full speed USB device using rt3883-ohci and address 3

Can anyone suggest what the problem might be?

Thanks,
Pete

got it working by adding the vendor: + product: into the serproxy.ports file and now it shows up now

Thanks :slight_smile:

Has anyone got the cp210x serial chip on the nano arduino unit to work with Vera 2(firmware 1.5.622 ) . I created a /etc/cmh/serproxy.port file with one line (vendor:10c4 product:ea60). This allows Vera 2 to recognize the serial port and it shows up in the serial port config tab. If I set the baud rate > than 9600, the serial port only allows one way communication from the Nano unit to Vera, but not the other way. Someone suggesting lowering the baud rate to 9600, when I do that it does not work at all. Any help would be appreciated. Even if you just tell me that cp210x is not capable with Vera 2.

Just to document here, I was able to make Vera identify my USB serial device by following this post:

http://forum.micasaverde.com/index.php/topic,4668.msg34066.html#msg34066