Cyberlink Remote Help
#1
Hi guys,

I have this remote control
Image

Just wondering if anyone has actually got it working well using LiRc? or some other means?

If so how would you like to send me your config files..

I have tried till Im at my wits end to get it working and this is my last ditch attempt at a fully functional remote for xbmc Smile
Reply
#2
Do you know the model number of the remote, model number of the receiver device?
Reply
#3
I think that one connects as a keyboard/mouse? Does it do anything?

Does it show up in if you do cat /proc/bus/input/devices?
Reply
#4
Works on mine without lirc.... you just plug it in and it works.

This is the case with both XBMC Live and a minimal install.
Reply
#5
The Remote works but only with a few buttons.
Play, forwards - Backwards stop etc
Volume

I was just wondering if someone had fully mapped it to XBMC ?
Reply
#6
use the search feature there are at least 3 other threads on this remote, one of them contains my mapping.

FYI the 2.29+ kernel has a driver specifically for this:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
MC1 (SD & HD): Asus A8N SLI, AMD x2 4600+, 2GB DDR 400 Cosair, Palit Nvidia 9400GT 1GB (Passive), ARTIC 500W PSU, Lian Li PC-C32B, Samsung 250GB SATA
MC2 (SD&HD): RaspberryPi
MC3 (SD&HD): RaspberryPi
NAS1: HP Prolient Microserver N40L 2Gb Ram, 250Gb OS Disk, 1x2TB HDD ext4, 5.25" to 3.5" disk drive added to ODD Slot for OS disk

Blog: http://ninet.org
Reply
#7
Sorry, I am a bit of a noob at this sort of thing.

What do I do with the driver?
what does the driver do?

Thanks for the help - I am now searching for your other posts
Reply
#8
The driver provides an interface to the device. Allowing it to "talk" to the system and vice versa.

If you install the .29 or later kernel (.30 (avoid .30.1 critical security bug in it)) you will automatically get the driver. Just connect the remote and it should be recognised.
MC1 (SD & HD): Asus A8N SLI, AMD x2 4600+, 2GB DDR 400 Cosair, Palit Nvidia 9400GT 1GB (Passive), ARTIC 500W PSU, Lian Li PC-C32B, Samsung 250GB SATA
MC2 (SD&HD): RaspberryPi
MC3 (SD&HD): RaspberryPi
NAS1: HP Prolient Microserver N40L 2Gb Ram, 250Gb OS Disk, 1x2TB HDD ext4, 5.25" to 3.5" disk drive added to ODD Slot for OS disk

Blog: http://ninet.org
Reply
#9
Ok hunted out my remote..
Code:
Linux lt1 2.6.30-020630-generic #020630 SMP Wed Jun 10 09:45:40 UTC 2009 i686 GNU/Linux

under this kernel the device is presented as 3 devices:
/dev/input/event12
/dev/input/event13
/dev/input/mouse3

event12 controls:
Homekey (top left)
Arrow Keys and OK
NumberKeys, clear and enter.

event13 controls:
all keys and correctly maps OK to enter, enter, arrowkeys, clear (not sure what it is mapped to but it is mapped)

there is a program written by the guy here:
http://twe.awardspace.com/cyberlink/New_...codes.html
that gets the scancodes directly but i can't find a direct link. I can send the program and src upon request though.
MC1 (SD & HD): Asus A8N SLI, AMD x2 4600+, 2GB DDR 400 Cosair, Palit Nvidia 9400GT 1GB (Passive), ARTIC 500W PSU, Lian Li PC-C32B, Samsung 250GB SATA
MC2 (SD&HD): RaspberryPi
MC3 (SD&HD): RaspberryPi
NAS1: HP Prolient Microserver N40L 2Gb Ram, 250Gb OS Disk, 1x2TB HDD ext4, 5.25" to 3.5" disk drive added to ODD Slot for OS disk

Blog: http://ninet.org
Reply
#10
Hi,

This is my first post. I'm trying to get the Cyberlink remote to work on a Linux machine. So far I have the 2.6.29 kernel and my Cyberlink remote seems to be working.

The kernel maps about 60% of the buttons to 2 events, mouse2 and event 6. The whole bottom half of the remote is maped, it is only the coloured buttons at the top and most of the white area that is unmapped. This is from xev output, is there any way to get the other buttons to be recognised?

I've managed to remap to some of the keys by putting a file in userdata/Keymap.xml. XBMC seems to recognise at least some of the buttons, ones that are normal keyboard codes, as a keyboard.

So the next question is how do I assign a button like 'BACK' or 'DVD Menu'. The keymap.xml file has a <key_id=YYYYY> field. But what I get from xev for the 'DVD Menu' button is a keycode 147, the event 0x1008ff65 and the name XF86MenuKB. Which do I use or are one of them correct?


Do I need to go down the recompiled kernel rat hole to get this to work ( I'd prefer not to as it gets fairly messy ).

Colin.
Reply
#11
It maps to 3 events.

If some buttons don't work on that event then look again you are using the wrong one.

ignore the mouse event.

I'd guess the event you may want is 7 or if it doesnt exist then 5
MC1 (SD & HD): Asus A8N SLI, AMD x2 4600+, 2GB DDR 400 Cosair, Palit Nvidia 9400GT 1GB (Passive), ARTIC 500W PSU, Lian Li PC-C32B, Samsung 250GB SATA
MC2 (SD&HD): RaspberryPi
MC3 (SD&HD): RaspberryPi
NAS1: HP Prolient Microserver N40L 2Gb Ram, 250Gb OS Disk, 1x2TB HDD ext4, 5.25" to 3.5" disk drive added to ODD Slot for OS disk

Blog: http://ninet.org
Reply
#12
In /dev/input/by-id part it seems to be mapped to 2 places ( event7 and mouse2 today ). But /dev/input/by-path has event6 as well.

I still don't know what to do with this information though.

I understand that it is producing XEvents. Some of these are keyboard codes that XBMC recognises and I can put into a keymap.xml file ( such as the clear key at the bottom being delete ). How do I map the other XEvents?

A button like 'DVD Menu' has a multimedia XEvent associated with it, with keycode and XEvent keysym. I can get this from xev. How do I tell XBMC to use it for something. Do I use the <key_id=YYYYY> tag? If so how?

Zotac 9300 Mini ITX, 2GB, Intel E2180 2.0Ghz,
Cyberlink Remote,
Ubuntu 9.04
Reply
#13
http://keytouch.sourceforge.net/dl-getscancodes.html

and run in a terminal as sudo. This will display the codes for the keys.

Look at the kernel source Linux/input.h ( I think) it provides the key mappings, the last 2 digits of the scan code (0x000000cd) are the ones that map to the key. if you seach the input.h file for 0xcd (as per my above example) it should map to something like KEY_HOME.

Be aware I am sitting in work atm pulling this from memory so allow some room for error.
MC1 (SD & HD): Asus A8N SLI, AMD x2 4600+, 2GB DDR 400 Cosair, Palit Nvidia 9400GT 1GB (Passive), ARTIC 500W PSU, Lian Li PC-C32B, Samsung 250GB SATA
MC2 (SD&HD): RaspberryPi
MC3 (SD&HD): RaspberryPi
NAS1: HP Prolient Microserver N40L 2Gb Ram, 250Gb OS Disk, 1x2TB HDD ext4, 5.25" to 3.5" disk drive added to ODD Slot for OS disk

Blog: http://ninet.org
Reply
#14
Thanks for the response. I'm at work so don't have access to my remote either.

I do have a multimedia keyboard though with some buttons ( mail, play etc. ). I just tested the getscancodes program and it recognises these extra keys on the second0 event device. So I do have a way of getting the codes now.

However it seems to generate a different number to what the xev program does and also these scancodes don't correlate with what is in /usr/include/linux/input.h. Are these numbers the ones that I put in the keysym.xml or is it the input.h values.

That keyTouch project that the getscancodes looks like another direction to be taken. Have you tried it? It looks like it is for keyboard remapping, which is another way I could do this. Possibly a simpler way too.

Zotac 9300 Mini ITX, 2GB, Intel E2180 2.0Ghz,
Cyberlink Remote,
Ubuntu 9.04
Reply
#15
http://tomoyo.sourceforge.jp/cgi-bin/lxr...-topseed.c

that's the source for the driver, see how it maps the codes. Just follow the same logic.

yes i used "getscancodes" all it does is tell you the code for the key pressed. you can use that code to find what key the system maps it to.

You could recompile the driver defining all the keys so they are presented however you want.
MC1 (SD & HD): Asus A8N SLI, AMD x2 4600+, 2GB DDR 400 Cosair, Palit Nvidia 9400GT 1GB (Passive), ARTIC 500W PSU, Lian Li PC-C32B, Samsung 250GB SATA
MC2 (SD&HD): RaspberryPi
MC3 (SD&HD): RaspberryPi
NAS1: HP Prolient Microserver N40L 2Gb Ram, 250Gb OS Disk, 1x2TB HDD ext4, 5.25" to 3.5" disk drive added to ODD Slot for OS disk

Blog: http://ninet.org
Reply

Logout Mark Read Team Forum Stats Members Help
Cyberlink Remote Help0