Debugging communications

--===============8569770553723569632==
Content-Type: multipart/alternative; boundary="000000000000b2864405bb64f343"

--000000000000b2864405bb64f343
Content-Type: text/plain; charset="UTF-8"

I think I've set up my hardware and software correctly, but the command I
send isn't received by my television. I'm looking for tips on how to debug
this situation.

I've got a Raspberry Pi Zero W running Raspbian Linux 10 (codename
"buster") and Linux kernel 5.10.11+. I'm running lircd 0.10.1, installed
via apt-get and standard repos.

My IR hardware is homemade and connected to one of the Raspberry Pi's
GPIO pins. I used the same wiring diagram as used in this post
<https://www.raspberrypi.org/forums/viewtopic.php?t=232688>. I'm using the
kernel module gpio_ir_tx, configured to use the correct GPIO pin. By
swapping out a yellow LED for the IR LED, I can verify that running irsend
will make the LED flash.

The problem is, when I switch back to the IR LED, nothing happens. I'm not
sure where to go from here, but I can imagine a few scenarios:
1) *The IR LED is faulty*. I've tried two LEDs from the same batch and get
the same result. I can't see a visual flash, but I assume that's because
the light is not visible to the naked eye. I don't have an IR camera, so I
have no idea how to verify this. Any tips?
2) *I got the wrong kind of IR LED*. I'm using this model
<https://www.digikey.com/en/products/detail/vishay-semiconductor-opto-division/TSAL6200/1681339>,
which has the same specs recommended by a different tutorial. Perhaps it's
not bright enough, or needs a different circuit to drive it correctly (I'm
using this circuit diagram
<https://www.raspberrypi.org/forums/viewtopic.php?t=232688>)? Is anyone
familiar enough with this sort of hardware that you can confirm whether or
not I've got this right?
3) *I'm sending the wrong code*. I have a Samsung TV with a BN59-00856A
remote control. I downloaded the matching config file here
<https://sourceforge.net/p/lirc-remotes/code/ci/master/tree/remotes/samsung/BN59-00856A.lircd.conf>,
and that's what I'm using. I only care about sending KEY_POWER, and I
notice that key has the same code across many Samsung remotes, so this
seems unlikely.
4) *The LED signal is blocked before it reaches the TV*. This seems
unlikely, since a signal from the manufacturer's remote sent from
approximately the same spot works fine.
5) *Something else?* No idea.

Any advice is appreciated,
  -- Nate

--000000000000b2864405bb64f343
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think I&#39;ve set up my hardware and software corr=
ectly, but the command I send isn&#39;t received by my television. I&#39;m =
looking for tips on=C2=A0how to debug this situation.</div><div><br></div><=
div>I&#39;ve got a Raspberry Pi Zero W running Raspbian Linux 10 (codename =
&quot;buster&quot;) and Linux kernel=C2=A05.10.11+. I&#39;m running lircd 0=
.10.1, installed via apt-get and standard repos.</div><div><br></div><div>M=
y IR hardware is homemade and connected to one of the=C2=A0Raspberry Pi&#39=
;s GPIO=C2=A0pins. I used the same wiring diagram as used in=C2=A0<a href=
=3D"https://www.raspberrypi.org/forums/viewtopic.php?t=3D232688" target=3D"=
_blank">this post</a>. I&#39;m using the kernel module gpio_ir_tx, configur=
ed to use the correct GPIO pin. By swapping out a yellow LED for the IR LED=
, I can verify that running irsend will make the LED flash.<br></div><div><=
br></div><div>The problem is, when I switch back to the IR LED, nothing hap=
pens. I&#39;m not sure where to go from here, but I can imagine a few scena=
rios:</div><div>1)=C2=A0<b>The IR LED is faulty</b>. I&#39;ve tried two LED=
s from the same batch and get the same result. I can&#39;t see a visual fla=
sh, but I assume that&#39;s because the light is not visible to the naked e=
ye. I don&#39;t have an IR camera, so I have no idea how to verify this. An=
y tips?</div><div>2)=C2=A0<b>I got the wrong kind of IR LED</b>. I&#39;m us=
ing=C2=A0<a href=3D"https://www.digikey.com/en/products/detail/vishay-semic=
onductor-opto-division/TSAL6200/1681339" target=3D"_blank">this model</a>, =
which has the same specs recommended by a different tutorial. Perhaps it&#3=
9;s not bright enough, or needs a different circuit to drive it correctly (=
I&#39;m using this=C2=A0<a href=3D"https://www.raspberrypi.org/forums/viewt=
opic.php?t=3D232688" target=3D"_blank">circuit diagram</a>)? Is anyone fami=
liar enough with this sort of hardware that you can confirm whether or not =
I&#39;ve got this right?</div><div>3)=C2=A0<b>I&#39;m sending the wrong cod=
e</b>. I have a Samsung TV with a=C2=A0BN59-00856A remote control. I downlo=
aded the matching config file=C2=A0<a href=3D"https://sourceforge.net/p/lir=
c-remotes/code/ci/master/tree/remotes/samsung/BN59-00856A.lircd.conf" targe=
t=3D"_blank">here</a>, and that&#39;s what I&#39;m using. I only care about=
 sending KEY_POWER, and I notice that key has the same code across many Sam=
sung remotes, so this seems unlikely.</div><div>4)=C2=A0<b>The LED signal i=
s blocked before it reaches the TV</b>. This seems unlikely, since a signal=
 from the manufacturer&#39;s remote sent from approximately the same spot w=
orks fine.</div><div>5)=C2=A0<b>Something else?</b>=C2=A0No idea.</div><div=
><br></div><div>Any advice is appreciated,</div><div>=C2=A0 -- Nate</div></=
div>

--000000000000b2864405bb64f343--


--===============8569770553723569632==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============8569770553723569632==--