Tree [r3] /
History



File Date Author Commit
Readme.txt 2009-09-06 dasmuli [r3] Minor changes.
delockIRUSB 2009-09-06 dasmuli [r1] Iniital version. Shows IR commands, raw USB com...
delockIRUSB.conf 2009-09-06 dasmuli [r1] Iniital version. Shows IR commands, raw USB com...
delockIRtoUSBAdapter.c 2009-09-06 dasmuli [r1] Iniital version. Shows IR commands, raw USB com...

Read Me

Readme for the Delock IR to USB adapter 61574.

Simple usage:

-Unpack the zip file. You will get this Readme, the precompiled binary and a key map configuration file.
-Start the program with "sudo ./delockIRUSB -i".
-If the adapter was found, you will see:

   Delock USB Infrared Adaptor Found @ Address 027 
   Delock USB Infrared Adaptor Vendor ID 0x01685
   Delock USB Infrared Adaptor Product ID 0x0200

-In case of problems check the list of usb devices with "lsusb". You should see a line containing
   ...
   Bus 002 Device 027: ID 1685:0200  
   ...
   
   If there is a line with ID "1685:0200", then there is a problem with the program not detecting your adapter.

-Press buttons on your IR remote control. You should see lines like this:
   IR Code: 4426
   IR Code: 9546
   IR Code: 5442
   IR Code: 2376
   IR Code: 580
   Try out different settings of your univeral remote or (if you have) try out different remotes.
   If you can freely configure your remote control, try out device configurations from "Philips".

-When you see IR codes for each button you want to configure, write down BOTH values for each different button press.

-Now open the configuration file "delockIRUSB.conf". In each line, write down an IR code, followed by the key symbol you want to execute. Example symbols are:
  Enter: 65293
  Left:  65361
  Up:    65262
  Right: 65363
  Down:  65364
  Escape:65307
  Tab:   65289

-For example if you see the IR code 4420 and 4424 for your menue button on your remote control and you want to simulate a tabulator keyboard button, the configuration file should include these two lines:
4420 65289
4424 65289

-In order to generate the events for x windows, the program must be started with "sudo ./delockIRUSB". IR codes are not reported, but their according keycode is executed. If for example the enter code is executed for the IR command, a newline will be seen in the console running the application.


Hints:

-A list of symbols can be found in the file keysymdef.h, but the values must be translated from hexadecimal to decimal in order to use them.

-If you absolutely cannot see an IR code, try to run the low level mode with "sudo ./delockIRUSB -l". This will dump the data of the adapter to the screen. If you see a flicker when pressing a button on your remote control, than IR commands appear in the stream but are decoded incorrectly by the application. So there is some hope left :)


Developers:
-Compile with: gcc -lusb -lX11 -lXtst delockIRtoUSBAdapter.c -o delockIRUSB
-Did not find a support for this stick, lirc was too complicated to setup, writing a real linux device driver was too time consuming.
-Usage of USB snoopy allowed to see the data stream, great app. Zeroes are encoded as "0", ones as "128", although this is probably not correct. But it works for some IR frequencies/protocols (RC5) at least.
-libusb allowed to communicate with the device in 5 minutes - great!
-External dependencies: I used a test library from the x server in order to create events. That is bad. I used libusb to communicate with the device, that is good. I will have to check if they are statically linked into the binary because I prefer out of the box functionality.
-Todos:
   *Increase IR detection range somehow. 3m is a not enough.
   *Yes, a real driver with lirc support would be better, but the weekend is over...