<DIV> </DIV>
<DIV>Thanks Steve, though I'm not sure if that's a good sign or bad that we're sharing the same issue. </DIV>
<DIV> </DIV>
<DIV>The only other thing I can note is that I have been able to get the cable box to respond to send_once commands with repeated numbers. i.e.</DIV>
<DIV><FONT size=2> %rc send_once gi-motorola-dct2000 2 2 2 2 2 2 2</FONT></DIV>
<DIV><FONT size=2>For some reason, it takes seven of these for it to register. And I'd be fine with hacking the channel.pl script for this, but the results aren't reliable enough.</DIV></FONT>
<DIV> </DIV>
<DIV>Finally, nor does my cable box have a serial port.</DIV>
<DIV> </DIV>
<DIV>I'm wondering if there is a parameter in lircd.conf that can be manipulated to maybe send more of a pulse than a flash. <BR><BR><B><I>Steven Bennett <sablists@earthlink.net></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">I'll second this report -- I'm using lirc 0.7.0 pre2 snapshot, with a<BR>DCT2224 cable box and the same Actisys 200L IR Blaster, and have the exact<BR>same issue.<BR><BR>What's really interesting (and somewhat confusing) is that if you do the<BR>send_once and give it a bunch of the same numbers, or do a bunch of<BR>send_once commands for the same numbers in a script, it still doesn't<BR>manager to get picked up by the receiver at all. But the<BR>send_start/send_end does just fine. Looking at the blaster, it's clear that<BR>any sequence of send_once inserts a noticeable delay in-between each<BR>transmission, but the send_start transmits the signal continuously. (Oh<BR>yes, and it appears lirc transmissions adversely affect the system clock --<BR>I've had it lose minutes during heavy testing...)<BR><BR>Unfortunately, while I've been experimenting with a new channel.pl script<BR>to do a
start-delay-stop-delay for each number, I've not been able to get it<BR>to produce accurate results yet, although I'm close with a quarter second<BR>delay in-between the start/stop. (You have to use the system sleep command<BR>instead of the perl one to get it to do fractions of a second...)<BR><BR>Still, sometimes it misses a number, and sometimes it gets it twice, and<BR>more importantly what the cable box happens to be doing at the moment.<BR><BR>I can't really blame this on the blaster, though -- I see similar behavior<BR>(dropped presses, occasional doubles) just using the standard remote. But<BR>there the user has visual feedback and it's just a mild annoyance. With the<BR>blaster, a mistake on this means you record the wrong channel.<BR><BR>And unlike the earlier threads in the archives discussing this cable box and<BR>it's variants, mine does NOT have a serial port I can use to control the box<BR>instead.<BR><BR>I haven't had the time to fool with this recently, but will be
looking at it<BR>again soon. Anyone out there have any suggestions?<BR><BR>Thanks,<BR>-->Steve Bennett<BR><BR><BR>scut erky wrote:<BR><BR>> I've been configuring lirc (0.6.6) and ir blaster (actisys 200L) to work with<BR>> a gi-motorola dct2000 cable box. I'm running mandrake 9.1 and myth 0.11 from<BR>> rpms.<BR>> <BR>> The lirc daemon starts fine, the lircd.conf is unchanged from the<BR>> remotes/motorola/DCT2000 file and the irw and mode2 commands demonstrate that<BR>> the ir blaster responds properly to signals from the cable box remote.<BR>> <BR>> This trouble isn't with mythtv per se, but with the trasmission from the ir<BR>> blaster to the cable box. I've searched all the posts and have seen hints of<BR>> this trouble but no solution.<BR>> <BR>> If I run <BR>> %rc send_once gi-motorola-dct2000 CHUP<BR>> I see lights from the ir blaster but no indication of response from the cable<BR>> box (a little light lights up when it
receives an IR signal)<BR>> <BR>> It's only when I send a repeating signal like<BR>> %rc send_start gi-motorola-dct2000 CHUP<BR>> <BR>> wait a few seconds, then<BR>> %rc send_stop gi-motorola-dct2000 CHUP<BR>> <BR>> that I can get the cable box to respond to signals from the ir blaster. The<BR>> distance between the ir blaster and cable box does not seem to affect<BR>> anything.<BR>> <BR>> So basically, this looks like the ir blaster is transmitting too fast for the<BR>> cable box. And my question is, is there any way to slow down the transmission<BR>> from the ir blaster?<BR>> <BR>> Thanks for any assistance.<BR></BLOCKQUOTE><p><hr SIZE=1>
Do you Yahoo!?<br>
<a href="http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail">The New Yahoo! Shopping</a> - with improved product search