View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 22 posts ] 
Go to page Previous  1, 2

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Wed Feb 01, 2006 10:49 am 
Offline
Joined: Sun Jun 12, 2005 2:39 pm
Posts: 464
Location: UK
I think i see the problem (maybe!)

when you run irrecord u need to run:

irrecord -H dev/input -d /dev/input/event2 /tmp/irrecord

the -H bit tells it which driver to use


Top
 Profile  
 
 Post subject: HA! that did it.
PostPosted: Wed Feb 01, 2006 11:08 am 
Offline
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location: Douglasville, GA
Cool, now I got:
Code:
root@mythtv:~# irrecord -H dev/input -d /dev/input/event2 /tmp/irrecord

irrecord -  application for recording IR-codes for usage with lirc

Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de)

This program will record the signals from your remote control
and create a config file for lircd.


A proper config file for lircd is maybe the most vital part of this
package, so you should invest some time to create a working config
file. Although I put a good deal of effort in this program it is often
not possible to automatically recognize all features of a remote
control. Often short-comings of the receiver hardware make it nearly
impossible. If you have problems to create a config file READ THE
DOCUMENTATION of this package, especially section "Adding new remote
controls" for how to get help.

If there already is a remote control of the same brand available at
http://www.lirc.org/remotes/ you might also want to try using such a
remote as a template. The config files already contain all
parameters of the protocol used by remotes of a certain brand and
knowing these parameters makes the job of this program much
easier. There are also template files for the most common protocols
available in the remotes/generic/ directory of the source
distribution of this package. You can use a template files by
providing the path of the file as command line parameter.

Please send the finished config files to <lirc@bartelmus.de> so that I
can make them available to others. Don't forget to put all information
that you can get about the remote control in the header of the file.

Press RETURN to continue.


Hold down an arbitrary button.


I am doing this via SSH from the office. I tried called my answering machine and ordering the dog to step on the remote, but I think she is sleeping. I'll test the buttons when I get home.

Thanks for all the advice.


Top
 Profile  
 
 Post subject:
PostPosted: Wed Feb 01, 2006 8:49 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
My silence in this case does not mean success, it means I haven't had the time to actually try it yet. :wink:

Soon and i will report back my findings to help others.

_________________
Girkers


Top
 Profile  
 
 Post subject:
PostPosted: Sat Feb 04, 2006 8:07 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
Okay I finally got a little bit of time to have a go at this.

I was able to get irrecord to work with the help of mad_paddler's post earlier:
Code:
rrecord -H dev/input -d /dev/input/event2 /tmp/irrecord


I was able to create a couple of buttons, I got an error when trying to set the toggle bit, I don't know if that means anything.

Anyways I copied the file /tmp/irrecord.conf to /etc/lircd.conf:

Code:
begin remote

  name  /tmp/irrecord.conf
  bits            8
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  pre_data_bits   24
  pre_data       0x800100
  gap          195728
  toggle_bit      0


      begin codes
          FFwd                     0x31
          Rew                      0x17
      end codes

end remote


I modified a section of the /home/mythtv/.mythtv/lircrc to the name of the two buttons I created:
Code:
begin
    prog = mythtv
    button = Rew
    config = Left
end

begin
    prog = mythtv
    button = FFwd
    config = Right
end


I then started lircd via /etc/init.d/lirc start

I went into watch a recording, but alas the keys did not function as expected. The FFwd key did not and the Rew key is display info on the program and the time line.

Any ideas on where to go next?

_________________
Girkers


Top
 Profile  
 
PostPosted: Sat Feb 04, 2006 11:59 pm 
Offline
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location: Douglasville, GA
I tried all the same stuff, and got the same result. I saw on http://knoppmythwiki.org/index.php?page=LIRCHowTo that they were recomending a recompile of LIRC. That's going to be the road I try next week when I am couped up in a hotel in London.

But I would also like to throught in that I had some wierdness with the /dev/ 's. Testing with
Code:
xxd /dev/input/event2

only responded to press the keys with standard keycodes. (numbers, arrows, etc.) While testing with
Code:
xxd /dev/usb/hiddev0

showed responses only for the key without standard key codes. (power, play, home, ffwd, etc.) So I used hiddev0. But, hiddev0 only has button press, and button release data. It didn't have the typematic repeat effect that event2 had when you would hold down the buton. I'm wondering if something is intercepting the native responses from the device and I am "listening" to 2 different driver's interpretations of them. I don't think that either one of those/dev/ 's in their current state are apropriate for LIRC to be trying to handle. I think LIRC should be getting the precursor to the /dev/ 's that I have found so far.

Am I way off on this?

Please advise.


Top
 Profile  
 
 Post subject:
PostPosted: Sun Feb 05, 2006 12:05 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
I don't know about the hiddev stuff, but I have downloaded and compile ver 0.8.0 of LIRC and that is the version I was using to get to where I am now.

_________________
Girkers


Top
 Profile  
 
 Post subject: I found a good lead
PostPosted: Thu Mar 02, 2006 8:21 am 
Offline
Joined: Tue Aug 16, 2005 11:50 am
Posts: 181
Location: Douglasville, GA
http://www.linux-usb.org/USB-guide/x699.html

at the very botom of that page it mentions "showkey -s" which didn't give output for all of the keys, but I tried "showkey -k" and it did. This is encouraging.

One thing I did notice is that holding down one of the buttons that has standard keybard mapping already, like the arrow buttons, has a typematic repeat effect. Holding down a special button, like 'dvd' or 'fwd', did not repeat when held down. This suggests that the input is still being intercepted and alter by a driver. (I don't know the Linux USB subsystem, but I know the Scientific Method) I think I need t modify the way this device is mount to the file system on the driver level to get the proper results. But, I can now proceed with trying to establish event handling for this device.

I'm not sure if I am any further along, but I am glad to have new information.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 22 posts ] 
Go to page Previous  1, 2



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 25 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu