[quote=“guessed, post:18, topic:164602”]@CJ, I borrowed the 8-Port USB-Serial adapter from @nanckekr that he was trying to get working back in June/July. It was discussed in this thread:
http://forum.micasaverde.com/index.php?topic=1170.45
and I’d previously created a placeholder for the device in the Serial USB Wiki page:
http://wiki.micasaverde.com/index.php/Serial_Supported_Hardware
To make it work cleanly out of the box with Vera, there are a few things to be sorted:
a) Default install should pre-configure the [tt]/etc/modules.d/65-usb-serial-ftdi[/tt] file
You reference this in the first post, but it doesn’t appear in the Default Vera build (1.0.980), so folks have to manually add with the command line interface to get this device recognized.
Here is the default setting for this file in 1.0.980:
ftdi_sio
and here’s what’s needed to make it recognise this USB-Serial controller:
ftdi_sio vendor=0x403 product=0x6010
Can you add this to the standard image so folks don’t need to add it manually?
b) “id” code in [tt]serproxy[/tt]/[tt]ser2net[/tt] creates duplicate labels
This device has “Dual” UARTs per USB entry, which shows as follows in the [tt]lsusb[/tt] listing:
...
Bus 001 Device 006: ID 05e3:0604 Genesys Logic, Inc. USB 1.1 Hub
Bus 001 Device 007: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Bus 001 Device 008: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Bus 001 Device 009: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Bus 001 Device 010: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Unfortunately [tt]serproxy[/tt]/[tt]ser2net[/tt] then goes and creates “duplicate” id values as can be seen in the following log:
[tt]11/28/09 17:14:05 ==Found Serial Port: 1 path:/dev/usb/tts/2 name: ftdi_sio id: usb-00:03.0-1.2.4.1
11/28/09 17:14:05 ==Found Serial Port: 2 path:/dev/usb/tts/3 name: ftdi_sio id: usb-00:03.0-1.2.4.1
11/28/09 17:14:05 ==Found Serial Port: 3 path:/dev/usb/tts/4 name: ftdi_sio id: usb-00:03.0-1.2.4.2
11/28/09 17:14:05 ==Found Serial Port: 4 path:/dev/usb/tts/5 name: ftdi_sio id: usb-00:03.0-1.2.4.2
11/28/09 17:14:05 ==Found Serial Port: 5 path:/dev/usb/tts/6 name: ftdi_sio id: usb-00:03.0-1.2.4.3
11/28/09 17:14:05 ==Found Serial Port: 6 path:/dev/usb/tts/7 name: ftdi_sio id: usb-00:03.0-1.2.4.3
11/28/09 17:14:05 ==Found Serial Port: 7 path:/dev/usb/tts/8 name: ftdi_sio id: usb-00:03.0-1.2.4.4
11/28/09 17:14:05 ==Found Serial Port: 8 path:/dev/usb/tts/9 name: ftdi_sio id: usb-00:03.0-1.2.4.4[/tt]
These Id’s are used by Vera in the Serial Port’s “Device Number” field in Vera. Since they’re not unique, Vera only “sees” this as a 4-Port serial device, not an 8-Port device. (See attached screenshot)
c) Plugging this device in, with the above issues, results in loss of connectivity to the ZWave dongle
The devices appear to be claimed correctly by the FTDI drivers, and there’s nothing in particular in dmesg to indicate a problem, but if I boot with the device connected, then the other Serial devices (my Alarm Panel, and the ZWave dongle) both seem to drop out. They show in device listings (Etc) but Vera has problems communicating with them.
I suspect it relates to the duplicate Id’s in (b) above, but can’t tell.
For now, it’s unplugged. Ping me offline directly if you want to debug it more directly on Vera and I’ll plug it in. I’d like to get this (or it’s 4-port equiv) working to help with folks who want direct-wiring of their Media Devices (Amp, TV) and Blinds.[/quote]
I’'l add it to the wiki- but wanted to let the powers that be know that the this 4-port model comes up fine to be configured by the vera UI.
http://www.mcmelectronics.com/product/83-10137
I happened to have it floating around from my old homeseer system also.
just plugged it in.
I saw a post that the to kick things over have to hit save or reboot. SO I hit save. Vera took loingerthan usual to come back. when it came back up i went into serial configuration and all looks well.
