Linux Infrared Remote Control

On 2/7/2013 4:03 PM, Ben Drawbaugh wrote:
> I've spent countless hours trying to figure out why I'm able to emit 
> IR using my USB-UIRT connected to my Raspberry Pi that is running 
> Raspbian Wheezy(3.2.27+ #250 PREEMPT). Successfully tested the 
> hardware on another computer.
>
> I installed lirc via "sudo apt-get install lirc" and can verify 
> receive IR is working by creating a remote config file using irrecord 
> and then using irw to verify that the learned commands are detected. 
> But I'm not able to emit IR, instead irsend returns:
> irsend: command failed: SEND_ONCE NewRemote KEY_UP
> irsend: transmission failed
>
>
> If I run lircd with the --nodameon command, there are some errors, but 
> I haven't found a solution online.
> lircd-0.9.0-pre1[5562]: accepted new client on /var/run/lirc/lircd
> lircd-0.9.0-pre1[5562]: uirt2_raw: checksum error
> lircd-0.9.0-pre1[5562]: uirt2_raw: UIRT version 0905 ok
> lircd-0.9.0-pre1[5562]: uirt2_raw: UIRT version 0905
> lircd-0.9.0-pre1[5562]: uirt2_send: remote not supported
> lircd-0.9.0-pre1[5562]: error processing command: SEND_ONCE NewRemote 
> KEY_UP
> lircd-0.9.0-pre1[5562]: transmission failed
> lircd-0.9.0-pre1[5562]: removed client
>
>
> Here is my hardware.conf
> # /etc/lirc/hardware.conf
> #
> # Arguments which will be used when launching lircd
> LIRCD_ARGS="-d /dev/ttyUSB0"
>
> #Don't start lircmd even if there seems to be a good config file
> #START_LIRCMD=false
>
> #Don't start irexec, even if a good config file seems to exist.
> #START_IREXEC=false
>
> #Try to load appropriate kernel modules
> LOAD_MODULES=false
>
> # Run "lircd --driver=help" for a list of supported drivers.
> DRIVER="uirt2_raw"
>
> # usually /dev/lirc0 is the correct setting for systems using udev
> DEVICE=""
> MODULES=""
>
> # Default configuration files for your hardware if any
> LIRCD_CONF=""
> LIRCMD_CONF=""
>
>
> And my lircd.conf created by irrecord:
> # Please make this file available to others
> # by sending it to <lirc@... <mailto:lirc@...>>
> #
> # this config file was automatically generated
> # using lirc-0.9.0-pre1(uirt2_raw) on Sat Feb  2 21:34:49 2013
> #
> # contributed by
> #
> # brand:                       NewRemote
> # model no. of remote control:
> # devices being controlled by this remote:
> #
>
> begin remote
>
>   name  NewRemote
>   bits           13
>   flags RC6
>   eps            30
>   aeps          100
>
>   header       2674   744
>   one           469   360
>   zero          469   360
>   pre_data_bits   24
>   pre_data       0x1BFF83
>   gap          66500
>   toggle_bit_mask 0x8000
>   rc6_mask    0x100000000
>
>       begin codes
>           KEY_UP                   0x1BE1
>           KEY_DOWN                 0x1BE0
>           KEY_RIGHT                0x1BDE
>           KEY_LEFT                 0x1BDF
>           KEY_SELECT               0x1BDD
>       end codes
>
> end remote
>
>
> lsusb shows the device, as expected.
> Bus 001 Device 013: ID 0403:f850 Future Technology Devices 
> International, Ltd USB-UIRT (Universal Infrared Receiver+Transmitter)
>
> And dmesg doesn't indicate there is anything wrong:
> [116119.991487] usb 1-1.3.3: new full-speed USB device number 13 using 
> dwc_otg
> [116120.096829] usb 1-1.3.3: New USB device found, idVendor=0403, 
> idProduct=f850
> [116120.096884] usb 1-1.3.3: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [116120.096903] usb 1-1.3.3: Product: USB-UIRT
> [116120.096915] usb 1-1.3.3: Manufacturer: FTDI
> [116120.100488] ftdi_sio 1-1.3.3:1.0: FTDI USB Serial Device converter 
> detected
> [116120.100706] usb 1-1.3.3: Detected FT232RL
> [116120.100726] usb 1-1.3.3: Number of endpoints 2
> [116120.100740] usb 1-1.3.3: Endpoint 1 MaxPacketSize 64
> [116120.100755] usb 1-1.3.3: Endpoint 2 MaxPacketSize 64
> [116120.100768] usb 1-1.3.3: Setting MaxPacketSize 64
> [116120.103362] usb 1-1.3.3: FTDI USB Serial Device converter now 
> attached to ttyUSB0
>
> lsusb -v -s 001:024 shows:
> Bus 001 Device 024: ID 0403:f850 Future Technology Devices 
> International, Ltd USB-UIRT (Universal Infrared Receiver+Transmitter)
> 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          0xf850 USB-UIRT (Universal Infrared 
> Receiver+Transmitter)
>   bcdDevice            6.00
>   iManufacturer           1 FTDI
>   iProduct                2 USB-UIRT
>   iSerial                 0
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           32
>     bNumInterfaces          1
>     bConfigurationValue     1
>     iConfiguration          0
>     bmAttributes         0xa0
>       (Bus Powered)
>       Remote Wakeup
>     MaxPower              100mA
>     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 USB-UIRT
>       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)
>
>
> The best thing I've come up with is that there is something wrong with 
> the kernel driver that is preventing this from working. But all the 
> posts that lead me to believe that are very old and I'm not sure how 
> to verify the problem.
>
> Any help would be appreciated. Thanks!
> Ben
>
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb

try to run lircd with strace.

ex.

"strace lircd --device=/dev/lirc0 --output=/var/run/lirc/lircd 
--pidfile=/var/run/lirc/lircd.pid --logfile=/var/log/lircd.log"

then run irsend using your remote name

ex "irsend -d /var/run/lirc/lircd SEND_ONCE NewRemote KEY_UP"

Please reference my experience with USB drivers with a new z77 chipset

https://www.centos.org/modules/newbb/viewtopic.php?topic_id=40935&forum=55

My end solution was going back to a serial blaster from irblaster.info

With any luck the strace will show you where it's failing.

Joe

On 2/8/2013 4:43 PM, Joe wrote:
> On 2/7/2013 4:03 PM, Ben Drawbaugh wrote:
>> I've spent countless hours trying to figure out why I'm able to emit 
>> IR using my USB-UIRT connected to my Raspberry Pi that is running 
>> Raspbian Wheezy(3.2.27+ #250 PREEMPT). Successfully tested the 
>> hardware on another computer.
>>
>> I installed lirc via "sudo apt-get install lirc" and can verify 
>> receive IR is working by creating a remote config file using irrecord 
>> and then using irw to verify that the learned commands are detected. 
>> But I'm not able to emit IR, instead irsend returns:
>> irsend: command failed: SEND_ONCE NewRemote KEY_UP
>> irsend: transmission failed
>>
>>
>> If I run lircd with the --nodameon command, there are some errors, 
>> but I haven't found a solution online.
>> lircd-0.9.0-pre1[5562]: accepted new client on /var/run/lirc/lircd
>> lircd-0.9.0-pre1[5562]: uirt2_raw: checksum error
>> lircd-0.9.0-pre1[5562]: uirt2_raw: UIRT version 0905 ok
>> lircd-0.9.0-pre1[5562]: uirt2_raw: UIRT version 0905
>> lircd-0.9.0-pre1[5562]: uirt2_send: remote not supported
>> lircd-0.9.0-pre1[5562]: error processing command: SEND_ONCE NewRemote 
>> KEY_UP
>> lircd-0.9.0-pre1[5562]: transmission failed
>> lircd-0.9.0-pre1[5562]: removed client
>>
>>
>> The best thing I've come up with is that there is something wrong 
>> with the kernel driver that is preventing this from working. But all 
>> the posts that lead me to believe that are very old and I'm not sure 
>> how to verify the problem.
>>
>> Any help would be appreciated. Thanks!
>> Ben
>>
>>
>> ------------------------------------------------------------------------------
>> Free Next-Gen Firewall Hardware Offer
>> Buy your Sophos next-gen firewall before the end March 2013
>> and get the hardware for free! Learn more.
>> http://p.sf.net/sfu/sophos-d2d-feb
>
> try to run lircd with strace.
>
> ex.
>
> "strace lircd --device=/dev/lirc0 --output=/var/run/lirc/lircd 
> --pidfile=/var/run/lirc/lircd.pid --logfile=/var/log/lircd.log"
>
> then run irsend using your remote name
>
> ex "irsend -d /var/run/lirc/lircd SEND_ONCE NewRemote KEY_UP"
>
> Please reference my experience with USB drivers with a new z77 chipset
>
> https://www.centos.org/modules/newbb/viewtopic.php?topic_id=40935&forum=55
>
> My end solution was going back to a serial blaster from irblaster.info
>
> With any luck the strace will show you where it's failing.
>
> Joe
>
>
>
>
>
>

Użytkownik Joe napisał:
> On 2/8/2013 4:43 PM, Joe wrote:
>> On 2/7/2013 4:03 PM, Ben Drawbaugh wrote:
>>> I've spent countless hours trying to figure out why I'm able to emit
>>> IR using my USB-UIRT connected to my Raspberry Pi that is running
>>> Raspbian Wheezy(3.2.27+ #250 PREEMPT). Successfully tested the
>>> hardware on another computer.

Hi people, I am working on transmitter / receiver that is based on 
ATMega328P, now it has serial interface. (it is planned to be USB).

But it is expected to work with ANY serial port, including USB->serial 
dongles.

If the time is not pressing, in a week or two, I'll have "alpha" version 
of firmware to test. (sending "side"). (need an Atmel ISP programmer).

[on hardware side it will be extremely simple, so anyone with soldering 
skills will be able to make it. - 1uC, 1IR diode, 1NPN transistor, 7805 
(or not, if You have 5V supply), some resistors. MAX232+4capacitors OR 
RS-232->TTL serial micro board], 1x24C256/512 eeprom.

Now I am on a stage, that I can send (Space-encoded) codes, hardcoded in 
internal EEPROM (one remote only as there is 1024bytes). RC5/6 not yet 
implemented (as my primary concern is to replace dead Yamaha RAV-12).

And it is controlled very simple way: just issue "send remote_name 
key_name" to serial port... :) [limited irsend syntax]

Please write if You are interested.

Wawrzyniec (Laurent) Piotrzkowski,
Poland.
>>>
>>> I installed lirc via "sudo apt-get install lirc" and can verify
>>> receive IR is working by creating a remote config file using irrecord
>>> and then using irw to verify that the learned commands are detected.
>>> But I'm not able to emit IR, instead irsend returns:
>>> irsend: command failed: SEND_ONCE NewRemote KEY_UP
>>> irsend: transmission failed
>>>
>>>
>>> If I run lircd with the --nodameon command, there are some errors,
>>> but I haven't found a solution online.
>>> lircd-0.9.0-pre1[5562]: accepted new client on /var/run/lirc/lircd
>>> lircd-0.9.0-pre1[5562]: uirt2_raw: checksum error
>>> lircd-0.9.0-pre1[5562]: uirt2_raw: UIRT version 0905 ok
>>> lircd-0.9.0-pre1[5562]: uirt2_raw: UIRT version 0905
>>> lircd-0.9.0-pre1[5562]: uirt2_send: remote not supported
>>> lircd-0.9.0-pre1[5562]: error processing command: SEND_ONCE NewRemote
>>> KEY_UP
>>> lircd-0.9.0-pre1[5562]: transmission failed
>>> lircd-0.9.0-pre1[5562]: removed client
>>>
>>>
>>> The best thing I've come up with is that there is something wrong
>>> with the kernel driver that is preventing this from working. But all
>>> the posts that lead me to believe that are very old and I'm not sure
>>> how to verify the problem.
>>>
>>> Any help would be appreciated. Thanks!
>>> Ben
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> Free Next-Gen Firewall Hardware Offer
>>> Buy your Sophos next-gen firewall before the end March 2013
>>> and get the hardware for free! Learn more.
>>> http://p.sf.net/sfu/sophos-d2d-feb
>>
>> try to run lircd with strace.
>>
>> ex.
>>
>> "strace lircd --device=/dev/lirc0 --output=/var/run/lirc/lircd
>> --pidfile=/var/run/lirc/lircd.pid --logfile=/var/log/lircd.log"
>>
>> then run irsend using your remote name
>>
>> ex "irsend -d /var/run/lirc/lircd SEND_ONCE NewRemote KEY_UP"
>>
>> Please reference my experience with USB drivers with a new z77 chipset
>>
>> https://www.centos.org/modules/newbb/viewtopic.php?topic_id=40935&forum=55
>>
>>
>> My end solution was going back to a serial blaster from irblaster.info
>>
>> With any luck the strace will show you where it's failing.
>>
>> Joe
>>
>>
>>
>>
>>
>>
>
>
>
>
> ------------------------------------------------------------------------------
> Free Next-Gen Firewall Hardware Offer
> Buy your Sophos next-gen firewall before the end March 2013
> and get the hardware for free! Learn more.
> http://p.sf.net/sfu/sophos-d2d-feb
>