From: Alex K. <ale...@gm...> - 2013-01-06 13:03:11
|
Hello, I've got a Digitus USB serial converter with an FTDI chip inside. I've been trying to use it with an Technisat TTS35AI remote but I can't. OS: Xubuntu 12.10 LIRC: 0.9.0 libftdi: 0.20 serial IR receiver: serial dongle that came with a Technisat AirStar FTDI device: http://www.digitus.info/en/products/accessories/adapter-and-converter/usb-to-serial-adaptor-usb-20-da-70156/ alex@vdr:~$ dmesg | grep 3-1 [ 1.296018] usb 3-1: new full-speed USB device number 2 using ohci_hcd [ 1.474081] usb 3-1: New USB device found, idVendor=0403, idProduct=6001 [ 1.474084] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.474086] usb 3-1: Product: FT232R USB UART [ 1.474088] usb 3-1: Manufacturer: FTDI [ 1.474090] usb 3-1: SerialNumber: A800dFin alex@vdr:~$ sudo lsusb -vvv -d 0403:6001 Bus 003 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0x6001 FT232 USB-Serial (UART) IC bcdDevice 6.00 iManufacturer 1 FTDI iProduct 2 FT232R USB UART iSerial 3 A800dFin bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 90mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 2 FT232R USB UART Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x0000 (Bus Powered) remote: http://lirc.sourceforge.net/remotes/technisat/TTS35AI Mode 2 is giving me some output. But it's giving me for each key pressed multiple pulse and space infos. What seems strange to me is that pushing the same button creates a different output each time. (I have never worked with anything else but the devinput LIRC driver, so I can't really tell if that's okay.) alex@vdr:~$ sudo mode2 -H ftdi -d input=5 [initial] space 3 [pressed button 1] pulse 9348990 space 960 pulse 774 space 2373 pulse 1578 space 1793 pulse 1595 space 1764 pulse 768 space 914 pulse 758 space 927 pulse 761 space 927 pulse 527 space 71 pulse 764 space 904 pulse 1608 space 947 pulse 83369 space 950 pulse 768 space 1031 pulse 400 space 940 pulse 1575 space 1803 pulse 1601 space 1748 pulse 800 space 927 pulse 758 space 927 pulse 761 space 1520 pulse 761 space 917 pulse 1591 space 937 [pressed button 1 again] pulse 3013177 space 970 pulse 751 space 960 pulse 738 space 1783 pulse 1588 space 1764 pulse 1598 space 680 pulse 771 space 934 pulse 761 space 940 pulse 742 space 917 pulse 761 space 917 pulse 761 space 904 pulse 1604 space 930 pulse 82317 space 970 pulse 751 space 940 pulse 751 space 1787 pulse 1601 space 1764 pulse 817 space 1442 pulse 774 space 930 pulse 755 space 914 pulse 764 space 930 pulse 761 space 904 pulse 777 space 924 pulse 1601 space 917 The parameter input=5 and input=6 are giving me this type of output. The others don't. Is it correct that there are 2 working inputs? LIRC doesn't do anything with the lircd.conf for the TTS35AI. No error but also no success. Therefore I tried to create my own lircd.conf. The program irrecord is opening the device properly but it's not creating any dots. But it keeps running as long as I keep pushing buttons. After I stop pushing the buttons on the remote irrecord quits after 10 seconds. So irrecord receives data but can't handle it. Using the --force option doesn't help either. Any ideas? Alex |