Re: Send IR without writing them to the config file - How to?

[Bengt M. <bu...@be...>]

On 9/16/24 10:41, Sean Young wrote:
> On Sun, Sep 15, 2024 at 01:48:19PM +0200, Mariusz Ferdyn wrote:
>> The captured codes are:
>>
>>
>> mf@pi1:~ $ mode2 -H default -d /dev/lirc0
>> Using driver default on device /dev/lirc0
>> Trying device: /dev/lirc0
>> Using device: /dev/lirc0
>> pulse 8985
>> space 4468
>> pulse 617
>> space 1651
>> pulse 601
>> space 1652
>> pulse 604
>> space 499
> -snip-
>
> This looks good, this is probably the nec protocol.

Actually, the timing is that of the NEC protocol, but the payload is 104
bytes, instead of 32 for NEC. (Air conditioning?) The second signal can
be described in the IRP notation as

{568,msb}<1,-1|1,-3>(16,-8,A:104,1,-299m){A=0xc3fe070006000400000000a2e7}

Returning to your first question:


 > I would like to send these ad-hock mode without writing them to
the config file etc. How to do it?


Lirc is not intended for this use case. I once submitted a patch to the
then-maintainer Christoph Bartelmus, who was vehemently against it,
meaning that it is cleaner if data bases reside on the server. See
http://www.harctoolbox.org/lirc_ccf.html, but note that article is not
up-to-data any longer.


Have a look at IrScrutinizer (http://www.harctoolbox.org/lirc_ccf.html);
possibly you can use it for your purpose?


Bengt