Re: girs driver issues

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

Hi Tim,

On 2020-03-15 00:16, Tim Pletcher wrote:
> Hi all,
> 
> I am using GirsLite 1.0.2 via a self-compiled firmware on an Arduino 
> nano clone configured with a Vishay TSOP38438 for receiving only.  I 
> have customized the girs firmware to include only:
>      Base Receive Led Parameters
> On Xubuntu 20.04, this configuration works great with IrScrutinizer 
> using the girs client for capturing via receive.  I have generated some 
> lirc files that are working just fine with a custom built Iguana-IR 
> design RS-232 serial receiver i built a long time ago.
> 
> Unfortunately, I am encountering a few issues with the girs lirc driver 
> producing some odd behavior when testing with irw.  For testing, I am 
> using the following remote lircd.conf file from the lirc remote 
> database: https://pastebin.com/JZVFzBE9
> 
> First:
> I tested with GirsLite compiled using the default BEGINTIMEOUT value of 
> 10000 ms as found in the Agirs configuration from github (consequently, 
> i couldn't figure out how to pass PARAMETERS values to the girs lirc 
> driver to change this on the fly.....).

beginTimeout is not really interesting, in particular since you are not 
sending. You can leave it by default. Using the Girs driver, there is 
currently no possibility to change in at runtime.

> This configuration produced the following behavior:
> Upon pressing a remote key, irw indicates the signal was received and 
> then after a delay with no further remote keypresses, irw repeats 
> another of the same keypress.
> Example irw output sequence:
> 00000000e0e020df 00 KEY_1 SamsungBN59-01054A    <- pressed at time=0
> 00000000e0e020df 00 KEY_1 SamsungBN59-01054A    <- appears 10 seconds 
> later  (as an example, see line 316 in first log linked below).
> 
This is weird. On line 84, a sensible line is received, consisting of 
two copies of the expected signaö. The first half is decoded (line 
199ff), then for some reason, lircd goes in siesta for 10 seconds (why 
is line 203 empty??) and (line 208ff) it decodes the rest -- without 
recognizing it as repeat.

Try changing (in GirsLiteConfig.h) DEFAULT_RECEIVE_ENDINGTIMEOUT t0 30 
and undefine PARAMETERS and report back.

> If I press a remote key, followed by another different one shortly 
> thereafter, it first emits another repeat of the first key and then show 
> the second keypress 10 seconds later.

Let's concentrate on the first problem for now.

Greetz,

Bengt