|
From: Sahbi <sa...@ze...> - 2019-11-07 20:20:17
|
> Ouch!! Have you had a look at it (for example graphically in > IrScrutinizer)? It is not even remotely close to what it is supposed > to be. So we conclude that your /dev/lirc (lirc_rpi) is not even close > to working correctly. Case closed! I did look at it, but I'm not all that familiar with raw IR stuff yet so I had no idea what to look for exactly. > It gets the timing all messed up. (Recall that generating a 38kHz > carrier in software requires an interrupt every 1/(2 * 38000) = > 0.000013 s = 13 microseconds.) I see. Oddly enough though, the stereo remote also uses a frequency of 38KHz and that works fine. But its signals are half the length of the TV so that might be why I guess. > How to do it better is another topic. Let me just remark that I know > of an unofficial driver using the hardware PWM of the RPi: > https://github.com/Al-/lirc_rpi_hardpwm . See also > http://lirc.10951.n7.nabble.com/hardware-pulse-wave-modulation-modified-kernel-module-tc11134.html Sounds interesting, I changed my IR sender's pin to one that supports PWM according to a few docs. I'll try compiling the module and mess with that. > To my knowledge, the lirc_rpi is deprecated by the Linux/RPi > communities, but I am not sure it is for the "right" reason... ;-\ Yeah it is, but the replacement gpio-ir doesn't even work half as well as lirc_rpi. :D Thanks so far. =] |