Forum

Full Version: Logitech K700 some multimedia keys don't work
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi

I'm just trying to make all the remaining multimedia keys work on this remote.

I went through the tutorial Configuring a Remote but Step 1 (lirc mode2) gave nothing - perhaps understandable as its a wireless keyboard.

I enabled debugging and got details of the key presses, but they have no OnKey value - unlike the the other keys that DO work.

Can I use the scancodes or sym values below to map the keys in keyboard.xml? Do they need converting to decimal?

REWIND
14:41:20 T:3042783232 DEBUG: Keyboard: scancode: a8, sym: 0153, unicode: 0000, modifier: 0
14:41:20 T:3042783232 DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
14:41:20 T:3042783232 DEBUG: Previous line repeats 3 times.
14:41:20 T:3042783232 DEBUG: OnKey: 0 (f200) pressed, action is

PLAY
14:41:25 T:3042783232 DEBUG: Keyboard: scancode: cf, sym: 0155, unicode: 0000, modifier: 0
14:41:25 T:3042783232 DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
14:41:25 T:3042783232 DEBUG: Previous line repeats 3 times.
14:41:25 T:3042783232 DEBUG: OnKey: 0 (f200) pressed, action is

FAST FORWARD
14:41:33 T:3042783232 DEBUG: Keyboard: scancode: d0, sym: 0157, unicode: 0000, modifier: 0
14:41:33 T:3042783232 DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
14:41:33 T:3042783232 DEBUG: Previous line repeats 3 times.
14:41:33 T:3042783232 DEBUG: OnKey: 0 (f200) pressed, action is


Thanks
Maybe this can help you?
(11th May, 2013 03:21 PM)sarah663 Wrote: [ -> ]Hi

I'm just trying to make all the remaining multimedia keys work on this remote.

I went through the tutorial Configuring a Remote but Step 1 (lirc mode2) gave nothing - perhaps understandable as its a wireless keyboard.

I enabled debugging and got details of the key presses, but they have no OnKey value - unlike the the other keys that DO work.

Can I use the scancodes or sym values below to map the keys in keyboard.xml? Do they need converting to decimal?

REWIND
14:41:20 T:3042783232 DEBUG: Keyboard: scancode: a8, sym: 0153, unicode: 0000, modifier: 0
14:41:20 T:3042783232 DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
14:41:20 T:3042783232 DEBUG: Previous line repeats 3 times.
14:41:20 T:3042783232 DEBUG: OnKey: 0 (f200) pressed, action is

PLAY
14:41:25 T:3042783232 DEBUG: Keyboard: scancode: cf, sym: 0155, unicode: 0000, modifier: 0
14:41:25 T:3042783232 DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
14:41:25 T:3042783232 DEBUG: Previous line repeats 3 times.
14:41:25 T:3042783232 DEBUG: OnKey: 0 (f200) pressed, action is

FAST FORWARD
14:41:33 T:3042783232 DEBUG: Keyboard: scancode: d0, sym: 0157, unicode: 0000, modifier: 0
14:41:33 T:3042783232 DEBUG: GetActionCode: Trying Hardy keycode for 0xf200
14:41:33 T:3042783232 DEBUG: Previous line repeats 3 times.
14:41:33 T:3042783232 DEBUG: OnKey: 0 (f200) pressed, action is


Thanks

Did you ever figure this out? I am also looking to fix non-working mulltimedia keys on a K400 keyboard. Specifically, for me the volume up works but volume down does not. If you could detail your aproach a little I would appreciate it - I am rusty in linux and new to the raspberry/xbian

Regards,
Rich
@scubaman I use a K400 and have never had a problem with the volume keys.

Within Beta 2 there is a keymap editor (Probably downgradable to Beta 1.1 Key Map Editor. I've never used it but it's Gui based so should be fairly simple Smile

I've just had a quick look at it - and it does seem pretty simple. Select what you want and then assign a key to it.
(21st Nov, 2013 01:27 AM)IriDium Wrote: [ -> ]@scubaman I use a K400 and have never had a problem with the volume keys.

Within Beta 2 there is a keymap editor (Probably downgradable to Beta 1.1 Key Map Editor. I've never used it but it's Gui based so should be fairly simple Smile

I've just had a quick look at it - and it does seem pretty simple. Select what you want and then assign a key to it.

I fixed it, in a way. Looks like the keys are not mapped correctly. I saw that the volume up key is mapped like
DEBUG: Keyboard: scancode: 73, sym: 00af, unicode: 0000, modifier: 0
DEBUG: OnKey: volume_up (f0b9) pressed, action is VolumeUp
but the volume down key is
DEBUG: Keyboard: scancode: 72, sym: 0127, unicode: 0000, modifier: 0
DEBUG: OnKey: f14 (f09d) pressed, action is
Apparently it is mapped to "F14"

Similarly I found the mute button mapped to F13

So I created a ~/xbian/.xbmc/userdata/keymaps/keyboard.xml containing
<keymap>
<global>
<keyboard>
<f14>VolumeDown</f14> <!-- MCE Vol down -->
<f13>Mute</f13> <!-- MCE mute -->
</keyboard>
</global>
</keymap>
and now it all works as intended! Ideally this should be fixed at a lower level, mapping the scancode properly but I'll settle for this :-)
Reference URL's