Re: LIRC receiving is working, irsend the ir transmitter blinks, but tv does not see it

Bengt Martensson <[email protected]> Tue, 13 Aug 2019 20:03:49 +0200
Newsgroups gmane.comp.hardware.lirc
Message-ID <[email protected]>
On 8/13/19 7:14 PM, Jake Gaisser wrote:
> Bengt Martensson sorry for the double reply, I have not really used 
> mailing lists before, and I think I was supposed to hit reply to all.
> 
> 
> I am sorry, I should have explicitly said that I do have the emitter. I 
> have the wired IR emitter with the jack, it is plugged in, and I have 
> the emitter positioned about 1 foot in front of my TVs IR Receiver.

It is called "stick-on-emitter" because you are supposed to stick it on, 
just on top of the device's IR receiver. It (normally!) does not cover 1 
foot; such things are sometimes called "blasters".

> 
> When I issue the irsend command I can see that the IR emitter Does blink.
> 
> I decided to capture some raw codes so that I could see if that would 
> make a difference, and also to see what they look like:
> 
> sudo mode2 -m --driver default --device /dev/lirc0 > ~/lirc.conf
> 
> here are the results, this is me quickly pressing the volume up button 
> on my Samsung BN59-01199F remote: https://pastebin.com/bwCMLdpR

First one decodes (with IrScrutinizer) to NECx2: {D=7,F=7,S=7}. Looks OK.

...

> If you were in my situation how would you debug this?

0. Stop Lircd.
1. Install IrScrutinizer 
(https://github.com/bengtmartensson/harctoolboxbundle/releases/tag/Version-2.0.1)
2. Start it. Set sending hw and capturing hw to /dev/lirc, and select 
/dev/lirc0.
3. Capture one interesting signal from the Samsung remote. The send it 
with Transmit to the TV. The tv should now react.
4. Capture the full remote from the Scrutinize remote/Parametric pane.
5. Export it to Lirc format (which gives you a lircd.conf file)
6. Start lircd again with the just generated lircd.conf file.
7. You can now irsend, or better, use IrScrutinizer's "irsend" (Sending 
hw/Lirc, select localhost; you need to start lircd with the  -l flag for 
this.)

...

> On a unrelated side note, every time I try to record with irrecord I 
> must first edit /etc/lirc/lirc_options.conf
> 
> so that driver = devinput and device = auto
> 
> otherwise when I try to use irrecord or mode2 I get an error message:
> 
> sudo mode2 -m --driver default --device /dev/lirc0 > ~/lirc.conf
> Using driver default on device /dev/lirc0
> Cannot initiate device /dev/lirc0

Only one of lircd and mode2 can access /dev/lirc0 at a single time. It 
is enough to stop lircd.

Hope this helps.