You are not logged in.

#1 2015-03-07 15:44:04

milescowan
Member
Registered: 2015-03-07
Posts: 1

Saitek Pro Flight Rudder Pedals ACL Issue

I have some USB input flight control input devices that I use with X-Plane. The devices include a Saitek Pro Flight Yoke System, which I plug directly into my computer, a separate throttle quadrant which plugs into what looks like a PS-2 connector on the yoke and Saitek Pro Flight Rudder Pedals, which plug into a USB port on the yoke.

When I plug the yoke in (with the throttle quadrant and rudder pedals already connected), "event12", "event13", "js1" and "js2" are created in /dev/input. ls -l there shows me the following:

ls -l
total 0
drwxr-xr-x  2 root root     260 Mar  7 10:33 by-id
drwxr-xr-x  2 root root     300 Mar  7 10:33 by-path
crw-rw----  1 root input 13, 64 Mar  7 06:28 event0
crw-rw----  1 root input 13, 65 Mar  7 06:28 event1
crw-rw----  1 root input 13, 74 Mar  7 06:28 event10
crw-rw----  1 root input 13, 75 Mar  7 06:28 event11
crw-rw----  1 root input 13, 76 Mar  7 10:33 event12
crw-rw----+ 1 root input 13, 77 Mar  7 10:33 event13
crw-rw----+ 1 root input 13, 78 Mar  7 08:06 event14
crw-rw----+ 1 root input 13, 66 Mar  7 06:28 event2
crw-rw----  1 root input 13, 67 Mar  7 06:28 event3
crw-rw----  1 root input 13, 68 Mar  7 06:28 event4
crw-rw----  1 root input 13, 69 Mar  7 06:28 event5
crw-rw----  1 root input 13, 70 Mar  7 06:28 event6
crw-rw----  1 root input 13, 71 Mar  7 06:28 event7
crw-rw----  1 root input 13, 72 Mar  7 06:28 event8
crw-rw----  1 root input 13, 73 Mar  7 06:28 event9
crw-rw-r--+ 1 root input 13,  0 Mar  7 06:28 js0
crw-rw-r--  1 root input 13,  1 Mar  7 10:33 js1
crw-rw-r--+ 1 root input 13,  2 Mar  7 10:33 js2
crw-rw----  1 root input 13, 63 Mar  7 06:28 mice
crw-rw----  1 root input 13, 32 Mar  7 06:28 mouse0
crw-rw----  1 root input 13, 33 Mar  7 06:28 mouse1

If I start up X-plane now the yoke and the throttle quadrant work, but not the rudder pedals. I believe this relates to the missing ACL on event12 and js1...

getfacl event12 shows me:

# file: event12
# owner: root
# group: input
user::rw-
group::rw-
other::---

and getfacl event13 returns:

# file: event13
# owner: root
# group: input
user::rw-
user:miles:rw-
group::rw-
mask::rw-
other::---

setfacl -m "u:miles:rw-" event12 (and js1) puts everything right and x-pane now sees my rudder pedals.

What is the correct way to automatically set these ACLs when the device is plugged in next time? I believe a UDEV rule is needed, but I'm not sure where to start.

Offline

Board footer

Powered by FluxBB