From: Jarod W. <ja...@wi...> - 2009-07-24 05:21:04
|
On 07/20/2009 03:52 PM, Christoph Bartelmus wrote: > Hi! > > Jarod Wilson "ja...@wi..." wrote: > >> On Jul 20, 2009, at 2:15 PM, Peter Budny wrote: > >>> I have a serial IR blaster to control my cable TV set-top box. It's a >>> standard Comcast/Motorola deal, and I'm using the codes from >>> >>> http://lirc.sourceforge.net/remotes/motorola/DCT2524 >>> >>> My problem is that the code for "0" won't send. This is the right >>> remote control, AFAIK, and all the other numbers work, just not 0. > [...] >> Heh, I've hit this exact same problem, just forgot about it 'til you >> mentioned it. I suspect there's something not quite right with the >> handling of the IR code for '0', which is 0x00000000, aka NULL, for >> Motorola set top boxes... Christoph may know off the top of his head >> how to fix this, otherwise, I need to put this on my TODO list for one >> of these evenings... > > My guess is that the timing data is slightly off and the receiver gets out > of sync if you send the same bit over and over again (the value is 0xffff > in this config file because the values of one and zero are swapped > compared to other config files): I'm actually using the DCT2224 config file, which doesn't have them swapped, but same difference. I've got: one 563 4420 zero 563 2180 > > one 556 2185 > zero 556 4424 > > I'd try with > one 556 2085 > or > one 556 2285 I tried both 'zero 556 2080' and 'zero 556 2280' with no change in behavior. > Adding > min_repeat 2 > may also help. Going back to 2180 and adding min_repeat 2 seems to be the ticket. --jarod |