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

On Sun, Sep 15, 2024 at 01:48:19PM +0200, Mariusz Ferdyn wrote:
> On 9/15/2024 10:12 AM, Sean Young wrote:
> > Hi,
> > 
> > On Sat, Sep 14, 2024 at 10:43:35PM +0200, Mariusz Ferdyn wrote:
> > > Using command mode2 -d /dev/lirc0 I received:
> > > 
> > > 
> > > Using driver devinput on device /dev/lirc0
> > > Trying device: /dev/lirc0
> > > Using device: /dev/lirc0
> > > code: 0xfd695000a94d50001f23000182110000
> > > code: 0x54020001740600005b02000182060000
> > > code: 0x4f0200010302000063020001ff010000
> > > code: 0x64020001030200005c0200010a020000
> > > code: 0x5d020001740600005902000171060000
> > > Partial read 4 bytes on /dev/lirc0
> > I think you need to run `mode2 -H default -d /dev/lirc0`, driver devinput
> > is not the right one.
> > 
> > > and now I would like to send these ad-hock mode without writing them to the
> > > config file etc. How to do it?
> > Please get the right codes first.
> > 
> > 
> > Sean
> > 
> 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.

Put all the pulse/space lines into a file. Then you can send it with

ir-ctl -s file

I don't know that this can be done easily with the lirc tooling. Maybe it
can be put into lircd.conf raw_codes remote definition, but this might be
too heavyweight for what you're looking for.


Sean