missing every second key

[olli]

hi there,

i've got a  FLIRC 2nd Gen.
on my linux-desktop (debian12) i've downloaded the latest tar.gz (Flirc-3.27.16).
starting sudo ./Flirc i managed to assign the keys.
from the "controllers" menu i choose full keyboard, because i need the F-keys for the VDR (MLD)

testing the keys with 3 different linux distros (MLD, debain 10+12) the result is always the same:
every second key press does nothing. i think the time between the keys presses was nearly 1 second.

the first test i made was a Technisat remote, then i use another remote from the DVB-S-Card of my working VDR.
but the result is the same

the Flirc-GUI says Firmware v4.10.5
is this the latest firmware?

what else can i do?

thanks in advance

Olli

[olli]

further testing with my win11 laptop shows the same result:

after one press on the remote which is recognized by an editor, the next press is ignored, no matter which time is between the presses.

i've also tested with very long press on the remote during the programming in normal mode.

i attach the config...

i hope anyone could help me.

thanks in advance

Olli

 

my_flirc_config-technisat-long-press.fcfg

[saul01]

On 2/17/2025 at 10:51 PM, olli said:

hi there,

i've got a  FLIRC 2nd Gen.
on my linux-desktop (debian12) i've downloaded the latest tar.gz (Flirc-3.27.16).
starting sudo ./Flirc i managed to assign the keys.
from the "controllers" menu i choose full keyboard, because i need the F-keys for the VDR (MLD)

testing the keys with 3 different linux distros (MLD, debain 10+12) the result is always the same:
every second key press does nothing. i think the time between the keys presses was nearly 1 second.

the first test i made was a Technisat remote, then i use another remote from the DVB-S-Card of my working VDR.
but the result is the same

the Flirc-GUI says Firmware v4.10.5
is this the latest firmware?

what else can i do?

thanks in advance

Olli  drive zone best car

It sounds like a firmware or timing issue. Try updating Flirc firmware via flirc_util dfu and check for updates. Also, adjust inter-key delay in Flirc GUI under Advanced settings. Let me know if that helps!

[olli]

thank you for the hints.

here is what i've done so far:

sudo -s
./flirc_util dfu
Putting device in Firmware Upgrade Mode...  Done!

started the GUI with
./Flirc
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/user/0/runtime-root'
[DEVICE]        Uploading
[========================================>] 100%
[DEVICE]        Waiting.
[DEVICE]        FW Detected
[DEVICE]        EOK
[E] lib/libflirc/flirc_driver.c fl_major_version(509): something bad happened
[E] lib/libflirc/flirc_driver.c fl_major_version(509): something bad happened
 

I can't find inter-key delay in Flirc GUI !

I've tried to do it with :
./flirc_util interkey_delay
  inter-key delay:  N/A for current firmware

lastly i cleared the configuration and recorded all the keys again with the GUI.

BUT: the result is still the same, every second key press isn't recognized...

Edited February 25, 2025 by olli

[jason]

It's the protocol, you need to record every key twice. Once I get back to development on this, it will be fixed.

No inter-key delay in the second version of Flirc.

Don't hit 'start' on the GUI. Essentially press the button in the GUI you desire to record. Press the remote button you want paired. Do the immediate action again. Every time you hit the same button on your remote, an alternating pattern is sent out. If you press another button before the same button again, some remotes just sound out the first button again. So it's critical you manually record each button twice and in a row.

[olli]

Thank you very much.
it actually works.
Except that the "Cursor-up" + "Vol+" and "Cursor-down" + "Vol-" buttons make some problems
-> the message "Button already exists" appears often.

But in the end i manged it.

[stauf]

Hi Jason,

I appear to be hitting something very similar where I record a button (in this case the blue button on an xbox remote).  I am intending to program this button as the context menu.  However, once I program it, on one press, the C button lights up on the Flirc app (as expected) but the next time I hit it, the CC button lights up.  Is this something similar?  If I try your suggestion and double program a single button, Flirc dumps out an error saying the key is already programmed.  Is there a document somewhere that describes this double programming?