Tweaking the Logitech R400 presenter tool on Linux
This article is outdated, please refer to a new version.
Updated on April 9th, 2013, after comments by Jim Diamond
For Christmas I received a Logitech R400 presenter tool as a replacement for the php|architect one that has now fallen apart. However, to use it together with my presentation system—pres2, about which I previously wrote—I need it to provide left and right arrow keypresses. By default its left and right buttons generate Prior and Next events in X.
It took me a while to get this to work, so in short, this is how I changed it. First of all, I created the file /etc/udev/logitech-r400 as root with contents:
0x70037 f5 0x70029 f11 0x7003E f11 0x7004B left 0x7004E right
This maps the two scan codes that the Play button (lower-left) both to f11, the empty screen button to f5 and the left and right buttons to the left and right arrow keys.
The first column represents the scancode, which I obtained by first looking up with input event the device was tied to:
stat -t /dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd --printf "%N\n"
Which showed the following for me:
‘/dev/input/by-id/usb-Logitech_USB_Receiver-event-kbd’ -> ‘../event16’
Then with event16 I ran:
/lib/udev/keymap -i input/event16
And pressed all four buttons (and the Play button twice). This then showed up on the screen:
scan code: 0x7004B key code: pageup scan code: 0x7004E key code: pagedown scan code: 0x7003E key code: f5 scan code: 0x70029 key code: esc scan code: 0x70037 key code: dot
After creating the file, to test things I ran:
sudo /lib/udev/keymap input/event16 /etc/udev/logitech-r400
Which showed:
Remapped scancode 0x70037 to 0x3f (prior: 0x34) Remapped scancode 0x70029 to 0x57 (prior: 0x01) Remapped scancode 0x7003e to 0x57 (prior: 0x3f) Remapped scancode 0x7004b to 0x69 (prior: 0x68) Remapped scancode 0x7004e to 0x6a (prior: 0x6d)
After this ran, the presenter tool now sends the key presses that I want. To make this permanent, I added as root a new file /etc/udev/rules.d/logitech.rules, with as contents:
ENV{ID_VENDOR}=="Logitech*", ATTRS{idProduct}=="c52d", RUN+="keymap $name /etc/udev/logitech-r400"
The changes will now also persist after rebooting as well.
My first possibility to test the new tool will be at PHP Benelux where I will be giving a MongoDB tutorial on January 25th. Tickets are still available.
Comments
Very nice and useful. Thanks!
In new Ubuntu (13.10 or 14.04) this way have changed.
Now, you must edit the file: /lib/udev/hwdb.d/60-keyboard.hwdb
- Find for "Logitech Presenter R400" and change this lines:
-
KEYBOARD_KEY_070029=esc KEYBOARD_KEY_07003e=f5
Example:
- # Logitech Presenter R400 keyboard:usb:v046DpC52Dd*dc*dsc*dp*ic*isc*ip*in00*
-
KEYBOARD_KEY_070029=esc KEYBOARD_KEY_07003e=f5 KEYBOARD_KEY_070037=displaytoggle
After that, run this command: # udevadm hwdb --update
Now reboot you computer. And that's it!
Life Line
TIL that Kingfishers can hover just like hummingbird. I'll hopefully have some reasonable shots after I've gone through my nearly thousand shots today...
I hiked 9.8km in 3h40m47s
Updated a restaurant
Updated a vacant business
I walked 7.1km in 1h16m56s
I walked 3.9km in 45m56s
I walked 1.1km in 10m47s
I think this was my favourite photo of the set that I took. It's not at maximum coverage, but it does have a sun spot group (4508) just on the cusp of the terminator.
#eclipse #eclipse2026 #SolarEclipse #London #Astronomy #AstroPhotography #Photography
No totality here in London, but still had a great evening out in the local park and taking some snaps.
I did have a nice Solar Filter that I made for my lens, and had many conversations with people from different backgrounds. Kids loves to look through my filter after I was done (ran out of battery power).
More photos later...
I walked 0.9km in 9m28s
I walked 1.2km in 19m05s
Merged pull request #1100
Fixed issue #2267: Application slow when debugger is not listening on…
I walked 4.7km in 48m18s
I walked 3.0km in 1h10m24s
Is there somebody who runs PHP on native windows (with Xdebug) and can run a simple script for me?
It must be in a file (`test.php`):
```
<?php
echo microtime(true), "\n";
xdebug_connect_to_client();
echo microtime(true), "\n";
```And run like:
php -dxdebug.log_level=11 -dxdebug.log=c:\temp\xdebug-i.log -dxdebug.client_host=localhost -dxdebug.client_port=9111 -dxdebug.mode=debug c:\temp\test.php
With the port 9111 not open.
Would love to see the output and log file (in a DM).
I walked 5.5km in 55m06s
@harry_wood This is this list of 100 Go-mistakes that I was talking about: https://100go.co/
Updated a crossing
I walked 2.1km in 20m08s
Enjoying my afternoon and evening out at Lords for some cricket!
I walked 3.2km in 38m54s
I walked 9.1km in 1h34m28s
Updated a gate
Updated a bakery shop




Shortlink
This article has a short URL available: https://drck.me/r400-a1r