well, I've gone and looked over your HEX dump(below), and
although I'm not entirely sure what represents a "press" and what is a
"release", I do notice the following characteristics:
2character hex representation: 32 ints
long. (is this 16 for "press" and 16 for "release", or just 32 on
"press, or 32 on "release"?)
2) 4 clearly defined non-zero sections in each at
offset 1,9,17,25 (or 0,8,16,24 + 1) - I'll call them
3) lets focus on the int (two characters) immediately prior
to each 'ff' . eg: for the onoff, that's 7d,85,80,78. It appears
that the 'D' positioned one (in this case 78) is repeated into the 'C'
position on the following key press, AND the 'B' positioned one ( in this case
85) is repeated in the 'A' position on the following key
4) conjecture: perhaps this "repeating D in C
and B in A" is to help identify the "released" key?
5) It also tells me that since A&C are
deterministic(from the previous key press), then the "relevant" part of the hex
that represents the key press/release is B(85) and/or D(78), and surrounding
good luch with fiddling with hw_hiddev.c.
<missing button press
Well, irrecord doesn't quite work, well, it does and it
doesn't. I get to the part where it tells me to hold down a button and get
nothing, unless I press alternating keys. If I cat the /dev/usb/hiddev0,
it doesn't show anything when I press the button more that once, it shows data
for the first press and then nothing unless I press another button. As far
as editing the file for the receiver itself, I wouldn't know where to begin
other than it's probably hw_hiddev.c. I did try the latest cvs version but
have the same issue.
I posted a hex dump of the output when I press the
keys, but I don't know if that would be useful.
On 12/18/05, Buzz
<email@example.com > wrote:
from those pic's it;s quite obviously noting at all like the dvico model,
apart from the fact that the symptoms are the same as I got when I was trying
to get my DViCO remote to work initially.....
detected by linux as a 'hiddev' device (human interface device) - shows
USB reciever hardware is OK.
/dev/usb/hiddev0 gives binary data on remote key press - shows remote
transmitter hardware is OK
using irrecord and see if you can get it to create a config file... and if
not, then get the CVS version of irrecord and try again... finially, do what I
did, and hack the irrecord tool with a dogied-up version of the
devinput.c (or similar driver file)- which you'll have to mess-with
yourself to get it working. If you get it working (whick hopefully
you will eventually), sent the changes and/or config file to the list and
christoph, and he'll hopefully be able to add support to lircd for everyone
else in the future who has one of those remotes.