[mythtv-users] Remote control. IRW strange behavior after making conf with irrecord? Alternating results.

Mark Hutchinson 8012900 at gmail.com
Sun Mar 19 22:24:04 UTC 2017


Do I just add that in to the config that irrecord creates?

I added that right under "begin remote" and it did not seem to make a 
difference.


Perhaps I am misunderstanding though.


Thanks for the help!


On 2017-03-19 4:07 PM, Karl Newman wrote:
> On Sun, Mar 19, 2017 at 7:47 AM, Mark Hutchinson <8012900 at gmail.com 
> <mailto:8012900 at gmail.com>> wrote:
>
>     Hello,
>
>     I have made a conf file for a remote control with irrecord ( see
>     below )
>
>     Using that conf file, I get odd behavior testing it with irw.
>
>     on pressing number one for instance, it will give KEY_1 the first
>     time then KEY_2 the second time, then KEY_1 the third time.
>
>     It alternates.  Same every time I try it.  I have tried to make a
>     new irrecord conf file, but got the same results.
>
>     Any ideas on what I can try?
>
>
>     This is me pressing the 1 key, three times:
>
>     root at mythbuntu:~# irw
>     0000000000000002 00 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 01 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 02 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 03 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 04 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 05 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000003 00 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000003 01 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000003 02 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000003 03 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000003 04 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000003 05 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000003 06 KEY_2 /etc/lirc/own_remote.conf
>     0000000000000002 00 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 01 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 02 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 03 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 04 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 05 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 06 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 07 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 08 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 09 KEY_1 /etc/lirc/own_remote.conf
>     0000000000000002 0a KEY_1 /etc/lirc/own_remote.conf
>
>
>     Here is my conf file:
>
>     root at mythbuntu:~# cat /etc/lirc/own_remote.conf
>
>     # Please make this file available to others
>     # by sending it to <lirc at bartelmus.de> <mailto:lirc at bartelmus.de>
>     #
>     # this config file was automatically generated
>     # using lirc-0.9.0(default) on Sat Mar 18 23:40:06 2017
>     #
>     # contributed by
>     #
>     # brand: /etc/lirc/own_remote.conf
>     # model no. of remote control:
>     # devices being controlled by this remote:
>     #
>
>     begin remote
>
>       name  /etc/lirc/own_remote.conf
>       flags RAW_CODES|CONST_LENGTH
>       eps            30
>       aeps          100
>
>       gap          99800
>
>           begin raw_codes
>
>               name KEY_0
>                   550     100     350     100     350 500
>                   250     350     300     150     300 500
>                   250     150     300     150     300 150
>                   300     150     300     500     250 350
>                   300     500     250     200     250 200
>                   250     200     250     200     250
>
>               name KEY_1
>                   500     100     350     150     300 500
>                   300     300     300     150     300 500
>                   250     150     300     150     300 150
>                   300     500     300     500     250 350
>                   250     550     250     200     250 200
>                   250     200     250     350     250
>
>               name KEY_2
>                   550     100     350     100     300 500
>                   300     350     250     150     300 500
>                   300     150     300     150     300 150
>                   300     150     250     550     250 350
>                   250     550     250     200     250 150
>                   300     150     250     550     250
>
>               name KEY_3
>                   550     100     300     150     300 500
>                   300     300     300     150     300 500
>                   250     200     250     150     300 150
>                   300     550     250     500     250 350
>                   300     500     250     200     250 200
>                   250     200     250     700     250
>
>               name KEY_4
>                   550     100     350     100     350 500
>                   250     350     250     150     300 500
>                   300     150     300     150     300 150
>                   300     150     250     550     250 350
>                   250     550     250     200     250 200
>                   250     350     250     200     250
>
>               name KEY_5
>                   550     100     300     150     300 500
>                   300     350     250     150     300 500
>                   300     150     250     200     250 200
>                   250     550     250     500     250 400
>                   250     500     250     200     250 200
>                   250     350     250     400     250
>
>           end raw_codes
>
>     end remote
>
>
> It's normally best if you can find a lircd.conf for the device 
> somewhere, or at least a similar device to start with when you do 
> irrrecord, so that the header information is correct. You will get 
> much more reliable operation. However, if that's not available you can 
> proceed as you have been. For your particular situation, it looks like 
> a toggle bit is active but not configured as such in your file. See 
> the lircd.conf documentation here: 
> http://www.lirc.org/html/lircd.conf.html The relevant part is this:
>
> *toggle_bit_mask <hexadecimal mask>*
>     Bits which are toggled between one and zero each time a button is
>     pressed. The mask is applied to the concatenated value of pre data
>     - data - post_data. 
>
> I would suggest adding toggle_bit_mask 0x2 (it appears to be bit 2 
> which is toggled) to the header of your lircd.conf and see how that 
> affects your irw results. You may have to restart lirc after making a 
> change to the file; I can't remember.
>
> Karl
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170319/5cb46263/attachment-0001.html>


More information about the mythtv-users mailing list