Jump to content
Flirc Forums
Frank

Recording keys - "Button already exists"

Recommended Posts

Hello,

when I try to map the key from the remote with a keyboard key
I have following problem.
When I map a new key the last key would be overwritten.
I got the message "Button already exists".
I can map one key only, actually.

I am using Premium Smart Remote (Samsung Fernbedienung BN59-01259B.)
https://www.fernbedienung.com/hersteller/11-samsung/274-bn59-01259b-samsung-fernbedienung
with
FLIRC USB (2nd Gen) Universal Remote Control Receiver 
https://www.amazon.de/FLIRC-Universal-Control-Receiver-Raspberry/dp/B01NBRBWS6/ref=sr_1_cc_1?s=aps&ie=UTF8&qid=1527694801&sr=1-1-catcorr&keywords=flirc+usb

I am using windows 7.

Flirc v3.11.6
Firmware v4.4.2

#Response cmd flirc_util unit_test:
C:\Program Files (x86)\Flirc>flirc_util.exe unit_test
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'getversion'
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'dmesg_pkv'
[E] lib/libflirc/firmware/fw_4.4.c fl_ver4_set_record_api(247): command error
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'format'
[E] lib/libflirc/firmware/fw_4.0.c fl_ver4_set_interrupt(367): timeout
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(131): error recording test0
Flirc Not Okay
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'clearstate'

# Device Log:
Mi Mai 30 2018 17:54:03
*** Device Disconnected *** 
*** Device Connected *** 
<1>malloc_addblock(49): Heap Block: 0x20001650 - 0x20003BFF (9k)
<3>record_hash(441): hash exists
:e:24318
0,4526,4419,616,1606,612,1610,612,1610,612,478,616,478,612,477,617,478,611,478,616,1606,616,1606,612,1610,612,482,611,478,612,482,612,478,630,459,616,1606,616,477,612,486,608,478,612,1610,611,478,616,1606,616,1605,616,478,612,1610,612,1610,612,1610,612,478,617,1605,616,478,612,478,617
:e:46
0,4525,4419,617,1606,616,1606,612,1610,612,482,612,478,612,483,612,478,612,478,616,1606,617,1606,616,1606,616,478,612,478,616,478,612,478,616,493,597,1606,617,478,612,482,612,478,612,1610,612,478,617,1606,616,1606,617,478,612,1610,612,1606,616,1606,616,478,612,1610,612,478,616,478,612
:e:46
0,4530,4420,612,1610,612,1610,613,1610,613,477,616,478,612,478,612,483,612,478,612,1610,612,1611,612,1610,612,478,616,478,612,478,617,478,612,478,616,1606,612,483,612,478,612,478,616,1606,639,456,612,1610,612,1637,586,478,612,1611,622,1600,612,1611,612,478,616,1606,612,478,617,478,612
:e:46
0,4530,4420,612,1606,616,1606,617,1606,616,478,612,478,617,478,612,478,616,478,612,1606,616,1607,616,1606,617,478,612,478,616,478,612,478,616,527,563,1606,617,478,646,448,612,478,612,1610,613,484,610,1606,616,1606,616,478,612,1610,612,1610,612,1610,612,478,616,1606,616,478,612,478,616
:e:3604
0,4529,4419,612,1606,616,1606,616,1606,616,478,612,478,616,478,612,478,617,478,612,1605,617,1605,616,1606,617,478,612,478,612,482,612,478,612,477,617,1605,616,478,612,478,616,478,612,1610,612,478,616,1606,612,1610,612,478,616,1606,616,1606,616,1606,612,478,616,1606,616,478,612,478,616
:e:2837
0,4527,4420,616,1606,617,1606,612,1610,612,478,616,478,612,478,617,478,612,478,612,1610,612,1611,612,1606,617,478,612,482,612,478,612,478,617,478,612,1606,616,478,612,478,617,478,612,1606,616,478,612,1611,612,1610,612,478,616,1606,616,1606,612,1611,612,478,616,1606,616,478,612,478,617
:e:2603
0,4529,4419,612,1610,612,1610,612,1610,612,478,616,478,612,477,617,478,612,478,616,1606,616,1606,612,1610,612,482,612,478,612,478,616,478,612,478,616,1606,612,483,612,478,612,478,616,1606,617,478,612,1610,612,1606,616,478,612,1611,612,1610,612,1610,612,478,617,1606,616,478,612,478,612

Thank you in advance.

Frank
 

 

Edited by Frank

Share this post


Link to post
Share on other sites

You have to hit the erase key, then press the button on your remote you want erased.

The GUI doesn't overwrite a key that's recorded. Let me know if that makes sense.

Share this post


Link to post
Share on other sites

Hello Jason,

thanks for your reply,
the problem is:
The first button from the remote is taken correctly.
I am getting the message "Button already exist." when I try to pair another one.

Let me give you an example.
(Example with automated paring process (using config "Minimal controller")):

1. I click on "go".
2. The message "Press the button to be paired with 'up' is displayed.
3. I click "up" button on my remote.
4. The message "recorded" successfully appears.
5. The message "Press the button to be paired with 'left'" appears.
6. The popup "Button already exist." appears.

Running "flirc_util.exe" is telling me that "Flirc is not ok".
C:\Program Files (x86)\Flirc>flirc_util.exe unit_test
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'getversion'
[E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(131): error recording test0
Flirc Not Okay
[E] lib/libtransport/transport.c _dev_send_cmd(230): Wrong response: 'getversion'

 

 

Share this post


Link to post
Share on other sites

@Frank, to use flirc_util.exe you need to first close the Flirc GUI app.

Regarding your issue with the remote and the log you've posted, have you pressed the same button 3-4 times to get this log? Or have you pressed different buttons?

I've analysed the signal data from your log and they are all from the same remote button. The remote uses NECx2 protocol with device 7, subdevice 7 and the button you've pressed has the code 209.

Can you create another log, but this time press few different keys? You don't need start recording. Just open the device log, enable IR debugging and press some keys. Save the log to a file and attach it here (don't paste it as it makes it harder to analyse).

Share this post


Link to post
Share on other sites

Hello Yawor,

thanks for your reply.

Regarding to your questions/hints:

1. "to use flirc_util.exe you need to first close the Flirc GUI app."

---> That works. I get the output: "C:\Program Files (x86)\Flirc>flirc_util.exe unit_test
Flirc Okay" now.

2. "Regarding your issue with the remote and the log you've posted, 
have you pressed the same button 3-4 times to get this log? 
Or have you pressed different buttons?"

---> I pressed different buttons.

3. "Can you create another log, but this time press few different keys? ..Just open the device log, enable IR debugging...
..Save the log to a file and attach it here.."

---> I have atached my log. I pressed buttons in this order: up-down-left-right


Thank you for helping me.

Frank

devie_log_buttons_pressed_up_down_left_right.txt

Share this post


Link to post
Share on other sites

It seems that all keys on this remote send the same signal. I've googled around and this remote is actually a Bluetooth remote. It requires pairing with the TV to work. I think that the IR is only used for pairing.

Share this post


Link to post
Share on other sites

Hi Yawor,

thanks a lot for helping me.

I think you are right, the infrared is probably used for power on only.

Best regards

Frank

 

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

×