<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><font color="black" face="Verdana,Arial,Helvetica" size="2"><font color="black" face="Verdana,Arial,Helvetica" size="2">
Dave: <br> <br> <br> <br>Thanks for the link. I did indeed follow those directions. The difference <br>between the MCE and non MCE remotes is that the non MCE has the ir blaster <br>connected to the card with a little mono plug jack, whereas the MCE has the
<br>blaster connected to the USB IR receiver. The other thing is that the driver <br>that you need to compile lirc with is mceusb2 rather than the stock prv150. <br>Other than that it should not be to different. <br> <br>
<br> <br>How did you get the firmware to load, the one from marks blog? In my startup <br>file it still shows the default firmware. <br> <br> <br> <br>Thanks. <br> <br> <br> <br>Peter </font></font></blockquote><div><br>
Peter,<br><br>How do you know that the firmware is not loading? I initially had the same problem when setting it up. I would use irsend and the command would run without error, but there were no signals or blinking lights coming from the blaster. I tracked it down to the firmware not being loaded. What is the output of "grep lirc /var/log/messages"? Mine now looks like this:
<br><br>May 2 21:01:05 divo kernel: lirc_dev: IR Remote Control driver registered, at major 61<br>May 2 21:01:05 divo kernel: lirc_pvr150: chip found with RX and TX<br>May 2 21:01:06 divo kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
<br>May 2 21:01:06 divo kernel: lirc_pvr150: firmware of size 258140 loaded<br>May 2 21:01:06 divo kernel: lirc_pvr150: 654 codesets loaded<br>May 2 21:01:06 divo kernel: lirc_pvr150: Hauppauge PVR-150 IR blaster: firmware version
1.3.0<br><br></div><br>