<div>Drew,</div>
<div> </div>
<div>Have you tried controlling your receiver? I couldn't see the flashes from my blaster in a digital camera, some cameras have stronger IR filters than others. </div>
<div>I hooked it up to my receiver and it worked.</div>
<div> </div>
<div>--Pete<br><br> </div>
<div><span class="gmail_quote">On 6/11/05, <b class="gmail_sendername">Nick</b> <<a href="mailto:knowledgejunkie@gmail.com">knowledgejunkie@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 6/11/05, Drew Zerdecki <<a href="mailto:dzerdecki@gmail.com">dzerdecki@gmail.com</a>> wrote:<br>>
<br>> I do have a PVR-350 and use its IR receiver, which I have read is on<br>> COM1. I have tried both COM1 and COM2 settings in modprobe.conf,<br><br>Not the case. The Hauppauge cards use their own interface via i2c (the
<br>LIRC module is lirc_i2c) to enable the IR receiver to work. It doesn't<br>touch the COM ports at all.<br><br>> mathcing the serial irq settings of my BIOS. Is there a way for me to<br>> ensure that my serial port is working? Would I make a serial
<br>> connection with my laptop's hyperterminal? What would be the easiest<br>> way to ensure /dev/ttytS0 or S1 is outputting anything?<br><br>If you have another machine with a spare COM port, you could try to<br>
connect the two together, and then send and receive to ensure the port<br>is working consistently. Alternatively, if the other machine is<br>running linux you could try the blaster on that machine too (or use a<br>live CD to test it).
<br><br>If there is a single COM port, it is likely set as COM1 with address<br>0x3f8, and IRQ 4. (Check the BIOS on messages on boot to confirm this)<br><br>When I had a machine using a receiver on the Hauppauge card and a
<br>blaster on the serial port, I had to build 2 separate instances of<br>LIRC to control them. The details are explained here:<br><a href="http://losdos.dyndns.org:8080/public/mythtv-info/MythTV_DISH_IR_LED_TX_via_Modified_LIRC.html">
http://losdos.dyndns.org:8080/public/mythtv-info/MythTV_DISH_IR_LED_TX_via_Modified_LIRC.html</a><br><br>The second instance has its own config, own remotes definitions, and<br>own running modified LIRC instance. You need to remove the kernel
<br>serial driver from using the device before you modprobe lirc_serial<br>which will control the device. Assuming the correct device nodes exist<br>for the second instance, and that the physical device actually works,<br>
you should be up and running.<br><br>If you've followed the instructions on lircsetup and still got<br>nowhere, I'd try to see if you can tell if the device works before<br>spending a lot more time trying to configure it. It's pretty much a
<br>case of installing LIRC, supplying the correct remotes definition file<br>for the blaster, and starting it up. It may be easier to first<br>stop/remove the LIRC process using the Hauppauge card whilst you are<br>trying to verify the blaster is working, as you only need to worry
<br>about having a single working instance of LIRC for the blaster. When<br>it's up and running, you can then add back the IR receiver LIRC<br>instance and should then have both running.<br><br>HTH,<br>Nick<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br><br><br>-- <br>Lirc, FC3, and an Irblaster?<br><a href="http://www.lircsetup.com">www.lircsetup.com</a>