Hello,

I'm trying to record keypresses using flirc_util. It worked for a number of keys, but when I try to record k it gives me:

-

PS C:\Program Files (x86)\Flirc> .\flirc_util.exe record k
 Press any button on the remote to link it with 'k'

[E] lib/libflirc/translate_v2.c translate_v2(297): not a valid keyboard key: k
usage:
 flirc record 'word'Available Options:
  escape, return, enter, escape, backspace, delete,
  tab, space, F[1-12], printscreen, scroll, pause,
  insert, home, pageup, pagedown, end, right, left,
  down, up, wake, media keys:
  eject, vol_up, vol_down, mute, play/pause, stop,
  fastforward, rewind
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_set_record(474): Key does not exist
Error, button exists

-

The error comes before it asks me to press a button on the remote. This is the version:

-

PS C:\Program Files (x86)\Flirc> .\flirc_util.exe
Version: flirc_util.release.v3.27.15
FW Version: v4.10.5
   SKU:     Flirc 2.0 [dori]
   Branch:  release
   Config:  release
   Hash:    0xF7261C8C

-

I'm using the latest Windows 11.

It works using record_api:

-

PS C:\Program Files (x86)\Flirc> .\flirc_util.exe record_api 0 14
hit a key on the remote to be paired with 0 14
  Succesfully recorded button

-

 

Jörg

Edited July 19, 20242 yr by V_J

What does:

flic_util.exe settings

return?

Does the issue also occur when you try and record a different remote (IR signal) key to the letter 'k'?

It does not give me a chance to record an IR signal; it immediately throws the error. This only occurred with k (of the keys that I tested).

I'm not near the flirc to test it now, but it was bought in July, updated to the latest version and using the latest version of the software.

 

It's definitely worth running:

flirc_util.exe device_log --ir -p

and checking if there is any spurious IR coming from any of your equipment. This one confused me initially. However, this affected all keys for me, not just a single key.

It might also be worth formatting the device (to remove all keys) and then trying just the 'k' on its own to see if that sheds any further light on this.

It really puzzled me: there were no spurious IR signals - I've programmed ir devices before and prepared the surroundings as I know the issues. No other key I tried was a problem, but using k as a parameter just made flirc_util immediately throw the error. It systematically does this, but I don't know if it does it only for me. Perhaps you can try to see if you also get the same behaviour?

I've resolved it by programming it using recorc_api, and that went without issues. For the next couple of weeks I will not be near the flirc to try things...

@V_J Sorry, I should have tried to reproduce on my setup first before offering advice :)

I can confirm that under Linux, I get identical behavior:

# flirc_util record k
 Press any button on the remote to link it with 'k'

[E] lib/libflirc/translate_v2.c translate_v2(297): not a valid keyboard key: k
usage:
 flirc record 'word'Available Options:
  escape, return, enter, escape, backspace, delete,
  tab, space, F[1-12], printscreen, scroll, pause,
  insert, home, pageup, pagedown, end, right, left,
  down, up, wake, media keys:
  eject, vol_up, vol_down, mute, play/pause, stop,
  fastforward, rewind
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_set_record(474): Key does not exist
Error, button exists

Settings info:

3.27.15+
FW Version: v4.10.5
   SKU:     Flirc 2.0 [dori]
   Branch:  release
   Config:  release
   Hash:    0xF7261C8C

@jason any chance of taking a look at this one? Thank you.

No need to apologise! I appreciate the attempt. :-) 

Thanks for trying, now we now it is not just on my system. :-) Interesting to see that even on Linux it behaves the same. Probably a small error in the code...

Edited September 19, 20241 yr by V_J

yeah, just checked the code, looks like a bug, I'll get an update out. Thanks for all the due diligence with this, appreciate it and sorry for that.

Thanks! It is a rather small thing for a user, but surprising...

If possible, could you also check delete_index .....? 

8 hours ago, V_J said:

Thanks! It is a rather small thing for a user, but surprising...

If possible, could you also check delete_index .....? 

Yes 

@jason whilst you are in that area, it might be an easy fix to correct the help text for the buttons that are supposed to have an underscore in them. Eg print_screen, fast_forward etc.

I published an update:

Version 3.27.16

• [gui] ARM64 library and software release
• [gui] ARM64 Updating static linux builds
• [gui] ARM32 Updating static linux builds
• [util] flirc_util record 'k' fix
• [util] flirc_util cleanup record help
• [util] flirc_util add delete_index
• [lib] general lib updates
• [lib] documentation cleanup

Please let me know if you have any more trouble or find anything else.

Thanks!

(I'm unable to test at the moment, but will update as soon as I can)