<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
+2 for a dual channel device. Possibly only +0.5 for a single channel device.<br>
<br>
What might a device like this look like on the transmitting side? Is<br>
it an external USB device? Plugs into any USB slot? Has two ports on<br>
it to hook up to two IR transmitter devices? What IR transmitters<br>
would you support so I can check out the costs on those? Can I use<br>
multiple devices if I want to control more than 2 STBs?<br>
<br>
I'd certainly pony up a little money (say $25-$50) to help with your<br>
initial PCB costs, etc. I assume that if and when I works I get at<br>
least a 2-channel device to own, etc.<br>
<br>
As an alternative a 2 or 4 channel 1x PCI-Express card for internal<br>
use might be of interest if you already know of an appropriate<br>
microcontroller and want to go that way.</blockquote><div><br></div><div><br></div><div>It could be made to meet all your requirements. Internal USB headers are a possibility, but they don't seem to be 100% standardized like the external plugs are. As for transmitter devices, they are nothing more than an IR LED on a stick with a mono 1/8" jack on the end for the most part. Just about anything would work in that case. I could easily drive about 8 of them without issue, possibly with different signals for all 8. Once one of them works, it's really not a big deal to add more. You could even build your own if you wanted to, though I know I've seen these things pretty cheaply out there on the net. <a href="http://irblaster.info">irblaster.info</a> has them for about $6, they look to be the same as the ones Smarthome sells. </div>
<div><br></div><div>PCIe is a real pain to talk to. USB is far easier and significantly cheaper to interface to for this level of project. We don't need the bandwidth, so there's no reason to deal with the problems, IMO. </div>
<div><br></div><div>I'm willing to do the hardware and firmware as an OSS project if others want to contribute either funds or code. The biggest code help that would be nice is someone to write the LIRC driver. It's going to take me some time to get that part working if I have to do it myself. Or is there an easier way to get Myth talking to it? The simplest method to do the firmware I can think of right now is to make it look like a serial port to the computer, so you just open /dev/ttyS0 or whatever the device name is and send it commands like "SEND CH1 <IR timing string>". We could even toss a receiver in while we're at it. May as well cover all the bases. It shouldn't be hard to be very competitive with the existing products price wise with the parts I have in mind, and it would be OSS, so no need to worry about binary drivers and such. </div>
<div><br></div><div>If there are a few interested people out there, please contact me directly so we don't clutter the list. I can probably knock up a prototype on the bench pretty quick. PCBs will take a little time to be made after I can verify correct operation. </div>
<div><br></div></div>