From: <li...@ba...> - 2010-04-04 19:33:15
|
Hi! Scott Maddox "sm...@gm..." wrote: > Okay, after a few hours with an oscilloscope I managed to get one of > the buttons transmitting, although irw still doesn't recognize the > button from the actual remote. No matter, I just needed to transmit > this one button, but maybe some info about what I found might be > useful to others. > > It turns out that Lutron's odd choice to use "Presence of IR modulated > at 40.0 kHz" as Logic One caused problems (Maybe the usb_uirt_raw > driver for the USB-UIRT could be modified to accommodate remotes like > this?). I have committed a patch to CVS right now. Would be good if someone could test this. > The problem was with a constrain on LIRC's raw mode (which is > required due to the Logic One constraint). It doesn't seem to allow > pulse/space times longer than about 13300 us. Actually the limit is 255*50 + 49 = 12799 for raw mode transmissions and 255*52 + 51 = 13311 in your case for struct transmissions @ 38kHz. There's an overflow in the signal length calculation for values above that which cause corruption of the signal sent. > I managed to get around > this by breaking up any pulses/spaces longer than that into two or > more pulses/spaces with a 75 us space/pulse in between. I had to use > 75 us because anything under 52 us would fail to transmit. 75 us is > perfect, though, because it just skips one of the 40khz pulses, which Doesn't matter. Both 52 and 75 are mapped to the same value internally due to integer calculaton. And you didn't set 40kHz in the config file btw. [...] > Also, I ran into a problem with the USB-UIRT going into a locked > resonance when I tried to simulate the FULL_ON code. No idea what you mean by that. What I'd like to see is the mode2 data that is received for this remote. Christoph |