Lirc not working on pi3

[gwidaz]

I am trying to make my Raspberry pi3 to receive IR signal from controller so I could then set it up to output IR signals to my led strip lights from rpi3.

Now I am using this http://www.instructables.com/id/How-To- ... pberry-Pi/ tutorial here and did everything according to it, but once I write

mode2 -d /dev/lirc0

and then start pushing buttons on my controller, the IR receiver's light is flashing in response to my button pushes, but there is no data being output to the console. What could be the problem? I wired the sensors all fine as well.

UPDATED:
I used 2 remote controllers and samsung s6 remote app as well. Used 2 IR receivers and none of that was working

[mattmiller]

Couple of things

You need to stop lirc from working to test using mode2

Code: Select all

sudo /etc/init.d/lirc stop
mode2 -d /dev/lirc0

and just in case - LIRC uses Broadcom numbering scheme not physical pin numbers


JFI I've used this guide myself for all my IR projects just inc case there are any diffs
http://alexba.in/blog/2013/01/06/settin ... spberrypi/

[gwidaz]

Couple of things

You need to stop lirc from working to test using mode2

Code: Select all

sudo /etc/init.d/lirc stop
mode2 -d /dev/lirc0

and just in case - LIRC uses Broadcom numbering scheme not physical pin numbers


JFI I've used this guide myself for all my IR projects just inc case there are any diffs
http://alexba.in/blog/2013/01/06/settin ... spberrypi/

Well thats the same tutorial. And like I said I did all the steps, probably 10 times, all updates are installed, I did stopped lirc, I even took apart my led light IR receiver to test if maybe arduino receiver is bad or smth, but same result..

[mattmiller]

mm - I've got it running on 4 Pi so it def (used to) work - I've not installed it on my current Pi3 so I'll run thru it and see what happens

[mattmiller]

Works fine for me

Code: Select all

pi@raspberrypi:~ $ mode2 -d /dev/lirc0
space 16777215
pulse 9268
space 4508
pulse 593
space 557
pulse 595
space 557
pulse 591
space 557
pulse 595
space 557
pulse 595
space 553
pulse 595
space 557
pulse 596
space 557
pulse 590
space 558
pulse 595
space 1684
pulse 577
space 1671
pulse 594
space 1670
pulse 591
space 1669
pulse 596
space 557
pulse 595
space 1666
pulse 595
space 1678
pulse 590
space 1666
pulse 593
space 562
pulse 593
space 557
pulse 593
space 1667
pulse 594
space 553
pulse 598
space 557
pulse 588
space 556
pulse 597
space 556
pulse 592
space 555
pulse 595
space 1672
pulse 590
space 1669
pulse 596
space 552
pulse 595
space 1676
pulse 587
space 1669
pulse 596
space 1670
pulse 591
space 1671
pulse 595
space 1665
pulse 596
space 41316
pulse 9257
space 2227
pulse 590

I even followed your script (whic is sligtly different in that it has extra gpio pullup command - but it makes no diff - i tried it with or without )

Looking at hardware wiring - I always wire to the 3.3V pin not the the 5V one so it may be possible that the receiver has damaged your gpio pin (people are always warning about not mixing 5V and 3.3V so you may have been caught out by this)
Try moving red wire to 3.3V and see what happens

Next change to BCM23 (physical pin 16) and alter /etc/modules and /boot/config.txt for new pin number (in case old one has been blown up)

After that - buy another receiver

[mattmiller]

I also didn't update - this is with new 23Sep16 image

[gwidaz]

Works fine for me

Code: Select all

pi@raspberrypi:~ $ mode2 -d /dev/lirc0
space 16777215
pulse 9268
space 4508
pulse 593
space 557
pulse 595
space 557
pulse 591
space 557
pulse 595
space 557
pulse 595
space 553
pulse 595
space 557
pulse 596
space 557
pulse 590
space 558
pulse 595
space 1684
pulse 577
space 1671
pulse 594
space 1670
pulse 591
space 1669
pulse 596
space 557
pulse 595
space 1666
pulse 595
space 1678
pulse 590
space 1666
pulse 593
space 562
pulse 593
space 557
pulse 593
space 1667
pulse 594
space 553
pulse 598
space 557
pulse 588
space 556
pulse 597
space 556
pulse 592
space 555
pulse 595
space 1672
pulse 590
space 1669
pulse 596
space 552
pulse 595
space 1676
pulse 587
space 1669
pulse 596
space 1670
pulse 591
space 1671
pulse 595
space 1665
pulse 596
space 41316
pulse 9257
space 2227
pulse 590

I even followed your script (whic is sligtly different in that it has extra gpio pullup command - but it makes no diff - i tried it with or without )

Looking at hardware wiring - I always wire to the 3.3V pin not the the 5V one so it may be possible that the receiver has damaged your gpio pin (people are always warning about not mixing 5V and 3.3V so you may have been caught out by this)
Try moving red wire to 3.3V and see what happens

Next change to BCM23 (physical pin 16) and alter /etc/modules and /boot/config.txt for new pin number (in case old one has been blown up)

After that - buy another receiver

Many thanks for that. I might of messed up with that to be honest as I hooked with 5v as it was shown on the arduino receiver I used that it uses 5v not 3.3. Then I used my led light IR receiver which I hooked with 5v as well and then of course, being an absolute stupidido, I wired up the IR receiver cables with the cables corresponding to the GPIO and 1 of the signal GPIO cables touched with 5v one and of course raspberry passed out. But it looks that it works fine (for now). I shall try once I get home to use 3.3v and different signal GPIO in case I blowed up everything.
But before that happened, with my very first try, it didn't worked as well, but I think I used 5v too.. Oh me..

I shall let you know if 3.3v and different GPIO pin will help it

[goforthanddie]

Hey,

I just recently updated my PI 2B to the latest kernel, running arch linux. Since then my lirc seems to be broken, it can not allocate the gpio pins, to verify I installed a fresh raspbian, updated and did everything as proposed in the mentioned tutorial.
I still get the following from the debug:

Code: Select all

root@raspberrypi:/home/pi# cat /sys/kernel/debug/gpio
GPIOs 0-53, platform/3f200000.gpio, pinctrl-bcm2835:

GPIOs 100-101, platform/soc:virtgpio, brcmvirt-gpio, can sleep:
 gpio-100 (                    |?                   ) out lo

Which earlier looked like:

Code: Select all

cat /sys/kernel/debug/gpio
GPIOs 0-53, bcm2708_gpio:
 gpio-17  (lirc_rpi ir/out     ) in  lo
 gpio-18  (lirc_rpi ir/in      ) in  lo

So, since I have no exact idea how stuff is going down for lirc, I think it might be an issue of the kernel module pinctrl-bcm2835 which seems to replace the old bcm2708_gpio. Can anyone maybe confirm this issue with the newest kernel (here Linux raspberrypi 4.4.26-v7+)?

[gwidaz]

Just an update..

Tried 3.3v and different GPIO signal inputs + different sensors and nothing.. Same crap.. Just nothing showing up. The sensor shows the response to the clicks.. Have no idea whats wrong with this.. Maybe drivers, maybe updates wrecked my raspberry.. Have no idea

[mattmiller]

The sensor shows the response to the clicks..

I don't understand what you mean by this?

I think its time to buy another sensor before throwing the Pi into the bin

These are the ones I use
http://cpc.farnell.com/webapp/wcs/store ... reId=10180

[joan]

A photo of your connections will be useful. People make mistakes.

http://abyz.co.uk/rpi/pigpio/piscope.html will let you independently check for IR activity.

[gwidaz]

The sensor has its own led light which flashes once it gets signal from the remote. I will add some photos this evening to show everything what I am doing.

The sensor shows the response to the clicks..

I don't understand what you mean by this?

I think its time to buy another sensor before throwing the Pi into the bin

These are the ones I use
http://cpc.farnell.com/webapp/wcs/store ... reId=10180

[gwidaz]

Many thanks for that. I will check it out and I will upload some photos later on!

A photo of your connections will be useful. People make mistakes.

http://abyz.co.uk/rpi/pigpio/piscope.html will let you independently check for IR activity.

[mattmiller]

Do you know what device it is that you have?

[gwidaz]

I used KY-022 or similar sensor
And from my led strip lights

Do you know what device it is that you have?

[gwidaz]

Ok there is a connection I did, It might be something wrong with this, but I doubt that..tried multiple GPIO pins for the signal, nothing was working (yes I did changed in the config files the inputs etc). I even uploaded a video to show how useless this is

This one is from my led strip lights (same connection as the second pic)

Thats from the arduino sensors kit (all of the sensors works just fine with raspi3)

And thats a video

[douglas_CED]

What is my language, sorry for my language, is not my native language, I am using the google translator.

This is a problem with the myRpi3 stretch and IR receiver Tsop1838, I am using the LIRC package in the latest version, installed via the command apt-get install lirc, using youtube procedures, google, make own site lirc.org, and without success, a driver that receives is as follows
" Using default driver on device / dev / lirc0
Targeting failed. "

Can someone help me?