Re: Help with completely unknown remote

Bengt Martensson <[email protected]> Tue, 26 Feb 2019 18:42:00 +0100
Newsgroups gmane.comp.hardware.lirc
Message-ID <[email protected]>
On 2/26/19 5:56 PM, Richard Evans wrote:
> Hi
> 
> I'm trying to configure LIRC for a strange remote for a stair lift, with 
> just two buttons - up and down.
> 
> I've tried:
> 
> _irrecord in default mode: _
> 
> gets the signals, sees the gap, but however many times I press the 
> buttons, it never terminates, just filling the screen with dots.
> _
> __irrecord in raw mode: _
> 
> works, I can get a good config file with raw codes and can send signals 
> via lircd. However for cleanliness I'd like a non-raw config file.
> _
> __irscrutinzer: _
> 
> gets signals, but cannot decode them, writing a conf file in raw mode gives
> 
>       begin raw_codes
>           #  not renderable, skipped
>       end raw_codes
> 
> I'm using the irtoy driver reading from an irdroid USB transceiver on a 
> raspberry pi.  lirc version 0.10.
> 
> I've run mode2 -m for each button, results attached.
> 
> The raw config file written by irrecord is:
> 
> begin remote
> 
>    name  sta1
>    flags RAW_CODES
>    eps            30
>    aeps          100
> 
>    gap          120905
> 
>        begin raw_codes
> 
>            name KEY_UP
>                810    1898     447    1898     447
> 
>            name KEY_DOWN
>                810    1919     447     981     831
> 
>        end raw_codes
> 
> end remote

This file looks reasonable. Your thing uses a very simple protocol (as 
compared to the "normal" consumer electronic protocols). Since there is 
only two signals, there is nothing essentially simpler than the raw 
form. (Possibly the timings can be cleaned up, though.)

The long conf files simple consists of the same signal repeated with 121 
milliseconds between the repeats.

This is not at all uncommon for "non-standard" stuff using IR remotes. I 
recall the protocol used by (some) DSRL Canon cameras: two commands 
(immediate trigger, delayed trigger) just two pulses with somewhat 
different parameters.

> So I'm just wondering if there is anything else I should try?  I can 
> probably get by with the raw codes (I want this for transmit only) but 
> would like to be able to contribute a finished config file if possible.

As above, no need really. Of course it is possible to come up with 
something "cooked", but there is no real advantage.

Greetz,

Bengt