Hi, so I followed this guide: http://losdos.dyndns.org:8080/public/my ... _LIRC.html
I replaced my conf file with a DCT2000 from http://lirc.sourceforge.net/remotes/motorola/DCT2000 , and renamed it /etc/ledxmitd.conf

I have set my serial port to COM2 and it is ttyS1 IRQ=3. I type /bin/setserial /dev/ttyS1 uart none

Then I type: /sbin/modprobe ledxmit_serial and then I type /usr/local/lirc-ledxmit/sbin/ledxmit-ledxmitd -L /tmp/ledxmitd.log

I then finally test it by typing: /usr/local/lirc-ledxmit/bin/ledxmit-irsend SEND_ONCE DCT2000 2

I then Received this error: /usr/local/lirc-ledxmit/bin/ledxmit-irsend: timeout
I then receive a correct log:
mythtv ledxmitd 0.7.2: accepted new client on /dev/ledxmitd
mythtv ledxmitd 0.7.2: removed client


So I have tried Switching COM ports, I have tried switching the pinout I had,in case i put it together correctly. I have tried this type of Transmitter http://losdos.dyndns.org:8080/public/my ... mitter.jpg
And this type: http://iguanaworks.net/ir/serial/

I have tested buy using a camcorder to detect for IR light, there was none when I triggered it. I have also put it near the cable box, a foot away, and still nothing.

I have no idea what to do. I have tried EVerything.
Help is greatly appreciated.

Thanks,
Mike

You should not have followed directions to recompile lirc. KnoppMyth supports serial IR blasters out of the box. All you should need to do is run irblaster.sh as root, and answer the questions.

that setup didnt work forme
I guess I can delete all this and try that again though if thats what everyone suggets

It's working for everyone else. Have you check that your serial ports are not disabled in your bios?

yes I made sure it was enabled as Com2

Best to try COM1 if that is an option for you, because that is what the lirc-serial module will default to using if there is some sort of problem passing arguments to the module.

Does the stock 'irblaster' kit support a second blaster, or must we recompile for the second instance ?

Greg

If you want two, I think you will need to re-compile. I don't think the lirc_serial module can support two serial devices. Otherwise, you could cable both irblasters to the same serial port and just append the two lircd.conf files for the two devices you want to control together and put the resulting file in /etc/irblaster/irblasterd.conf.

Interesting option... two different receivers in my case. Both blasters would issue each channel change, but only one receiver would acknowledge the signal. Could be problematic when you have two recordings start at the same time, and competing for the blaster, yes ?

When I jumped to R5B7, I ended up grabbing LIRC 8.0.0 and compiling for the PVR-350 IR receiver... This should work 'out of the box' with R5E50, correct ?

Thanks again all.
Greg.

I doubt two receivers would be a problem because the IR signals will have to be channeled through the one driver anyway so the codes will be sent serially and in tact, the only problem may be if the receiver needs a gap before or after the signal to detect it properly. It would be easily worked around with some locking code in the channel change script if it proved to be a problem.

I don't know about that particular receiver.

Seems my post from earlier didn't make it.

With the 'dual blaster, single port' option - do you wire two complete blasters in parallel at the DB9 pins, or just a single diode/resistor and then the IR transmiting LEDs afterwards ?

Have soldered two complete blasters in parallel at the pins, and things seem to be working for the most part, but my second receiver is missing some digits (which didn't happen before my RE50 upgrade, using ledxmit for this unit).

Thanks
Greg.

You could take out the signal diode. That will slightly increase the current (and hence the brightness) the IR diode shouldn't mind being reverse biased. Thats what I have for my blaster (just a resistor and the ir diode in series). The other way to do it is resistor-irdiode-irdiode (ie have them all in series). You would probably want a lower value resistor to keep the same brightness.

updatE: I got it working, and im an idiot.
I was using a serial extension cable, which i took a look at and checked the conductivities and the pins were not going to the same pin on the opposite side of the cable, turns out it was for a UPS supply. Damn.
thanks for thehelp anyways tho

Thanks Greg.

Having some (timing?) issues now, and only getting about an 80% hitrate on channel changes for the second tuner. Short of renice'ing the process, anything else that can be done to help support the changes ?

Greg.

You can make it repeat the signal a number of times when it sends a digit. This would be what happens when you press a button on a remote control anyway. I can't remember exactly how this is done, and I'm away from home for the rest of the week, so I can't look on my box to see how I did it but I have a vaugue recollection that you put something like min_repeat=2 in the lirc configuration file (/etc/irblaster/irblaster.conf).