Fwd: Receives only 1 input
Guilherme Furst Bittencourt <[email protected]> Tue, 10 Jul 2018 16:29:24 -0300
| Newsgroups | gmane.comp.hardware.lirc |
|---|---|
| Message-ID | <CAKDyC2Jz2my2nV=UZdMDmKDeh4_jVQ73i9DXNwT4j_o4pMkUGw@mail.gmail.com> |
On Sun, Jul 8, 2018 at 6:31 AM, Bengt Martensson <[email protected]> wrote: > To pinpoint the problem, I would recommend starting mode2 in a separate > "terminal" (lircd NOT run nunning), and see if it exhibits the same > behavior. If that works, the problem is with lircd. The way to search for > these problems is to start lircd with high logging >= TRACE1, and either > analyze the log yourself or to post it. > > Greetz, > > Bengt > > Okay, so I'm not really sure what is going. I've tested with mode2 and indeed it reads signals, though I'm not sure if correctly. For one, I was never able to detect proper spacing with irrecord, always having to use raw signals instead, no matter which remote even when it worked years back, I'm not sure if its relevant but I didn't many people complaining about it either. Second point, now this is the weird part because it lacks some consistency. It took a bit of time messing around but I've managed to get a good test sample, tried to keep it short because usually logs are so big. > root@guiu-top /etc/lirc/lircd.conf.d # nano /etc/systemd/journald.conf > root@guiu-top /etc/lirc/lircd.conf.d # lircd --loglevel=trace2 > root@guiu-top /etc/lirc/lircd.conf.d # irw > 000000000000000b 00 KEY_OK NET > 0000000000000001 00 KEY_1 NET > 0000000000000001 00 KEY_1 NET > 0000000000000001 01 KEY_1 NET > 0000000000000001 00 KEY_1 NET > 0000000000000001 01 KEY_1 NET > ^C > 130 root@guiu-top /etc/lirc/lircd.conf.d # killall > lircd I had redone irrecord quickly with some most used keys, in this case only KEY_OK was read properly, and indeed if you read remote config, it was wrongly coded. Remote config file https://ptpb.pw/jGGV.conf Syslog of the brief period above: https://ptpb.pw/EBsE Still nothing obvious for me to pinpoint what the issue might be, what else can I check? And regarding "irrecord --force" am I doing something wrong since I'm always needing to use it? And is it possible for a faulty sensor to be half working like that? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot