Re: Trouble with irrecord, mode2 works fine

Bengt Martensson <[email protected]> Sun, 19 May 2019 11:52:51 +0200
Newsgroups gmane.comp.hardware.lirc
Message-ID <[email protected]>
On 5/3/19 12:28 PM, lgac_pi wrote:
> I'm trying to record IR codes for an LG Air Conditioning unit.
> When using mode2, both regularly and with -m, I see data from the sensor,
> either in the form of pulses and spaces, or as raw data. However, when I
> start irrecord and reach the point where it tells me to press random buttons
> until two lines of dots are generated, I run into a problem.
> Only the first button I press, whichever it might be, generates a single dot
> and then nothing after it, until irrecord aborts after 10 seconds.
> 
> I've tried using mode2 -m to capture the raw data of the poweron and
> poweroff button presses and attempted to create a raw codes file from that
> data, but irrecord is stubborn and says it cannot parse my raw codes file.

When asking for help, list your configuration, operating system 
including kernel (uname -a), lirc version, and in particular the driver 
and the hardware you are using.

Secondly, irrecord is ... making a long story short ... a catastrophe. 
Use IrScrutinizer instead. Since your configuration is unknown to me, 
cannot give you more advice right now.

Third,
> 
> Here's how it looks:
> /begin remote
>    name lgac
>    flags RAW_CODES
>    eps 30
>    aeps 100
>    gap 40991
> 
>    begin raw_codes
> 
>      name poweron
>        8518     3423      215      620      569      629
>        237      667      653      527      575      446
>        648      519      586      546      201      875
>        575      446      647      532      573      528
>        575      392      702      532      572      529
>        574      527      567      534      570      530
>        574      527      577      498      595      531
>        573      528      575      454      331      383
>        254      197      569     1625      573      528
>        576     1538      649      531      573      528
>        576      524      569     1625      572     1622
>        577     1616      570
> 
>      name poweroff
>        8519     4254      571     1616      572      501
>        603      525      568      537      567     1622
>        576      524      570      533      572      528
>        626      678      395      338      786      689
>        251      494      753      480      572      421
>        673      532      572      530      575      419
>        674      534      570      531      572      367
>        788      473      572      529      573      527
>        577     1617      570      532      575     1437
>        807      330      714      478      626      528
>        579      926      226      463      569      802
>        415      570      391      878      256      499
>        229      838      234      812      259     1035
>        275      628      199      514      937     5787
>        215
> 
>     end codes
> end remote

This looks completely bonkers. "Normally" AC IR signals consists of two 
values (not accounting  for lead-in etc) , which, with random 
measurement errors, make up the signal. So your hardware may need to be 
fixed.