Jump to content
Flirc Forums
Sign in to follow this  

Suggestion for recording keys twice

Recommended Posts

Since some remotes send alternating codes and there are multiple questions/postings about having to record the same key twice, why not record two key presses when going through the setup?  The second press could confirm the original code, or determine if the remote alternates codes between presses.  If users don't want to go through this process, you could also just make this an option in the Advanced menu "My remote uses multiple codes per button".


Possible workflow:

1) Press a button on the gui or use the flirc_util record command

2) Prompt user to press a button on the remote

3) User presses button on the remote

4) Acknowledge the code was received and prompt the user to press the key again

5) User presses same button again

6) Acknowledge the second press. If the codes are the same each time, record the first code.  If they are different, record both.  You could even prompt the user to press the button again, to recognize that the third press matches the first.


This would eliminate the headache for MCE style remotes.

  • Like 1

Share this post

Link to post
Share on other sites

That is a good idea. It think Jason's plan is to somehow predict what the other code would be without the user having to press the key twice (or know their remote sends to button presses).

Share this post

Link to post
Share on other sites

The RC6 protocol usually toggles only a single bit but the problem is that the whole signal is stored in a hashed form. Even single bit change can generate very different hash value in the Flirc. The trick is to properly detect that the signal is an RC6 one and do something with it. The best thing would be to ignore this bit so no matter if it is set or not the hash would be the same. But I don't think it is possible with processing power of microcontroller used in Flirc as this would require to actually decode the signal into raw data. The other course of action would be to ask the user to press the button one more time if RC6 signal is detected - not ideal solution because user still needs to press the button multiple times but at least there is no need to manually record the same key combination again.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this