Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logitech f710 config and minor fixes #7

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

jithu83
Copy link

@jithu83 jithu83 commented Mar 27, 2019

This series does the following:

  1. Adds Logitech F710 Joystick (which uses a proprietary wireless dongle) support to this part
  2. Bench-marked it alongside the Wii-U and added the results in README
  3. Made some minor enhancements and fixes

Device selection assumes that the search term from yaml file is fully
lower-case. It fails to recognise the device if for e.g we specify
"Nintendo" instead of "nintendo".

Fix this trivial bug by converting the search string to lower-case
before matching to evdev.list_devices().

Signed-off-by: Jithu Joseph <jithu83@gmail.com>
People tend to duplicate this file to add newer controllers.

The code in part.py looks for the key "joystick_max_value" and not
"joystic_max_value", and fallback to Nintendo's default fallback
value which is hard-coded in the code 1280.

Signed-off-by: Jithu Joseph <jithu83@gmail.com>
Logitech F710 joystick uses a dongle for wireless connectivity.
Hence it can be used with boards which doesn't have bluetooth buitin
like Nvidia JetSon Nano for e.g.

While this part is (wrongly) named bluetooth_game_controller, it
works over any game controllers which expose /dev/input/event* device
files.

Signed-off-by: Jithu Joseph <jithu83@gmail.com>
The D-pad buttons in Logitech F710 events identify as
event.type == ecodes.EV_ABS. Consequently the current code in
read_loop() tends to scale it.

Map the throttle scaling to two other buttons which report as regular
buttons, so that the current throttle scaling logic works correctly.

Signed-off-by: Jithu Joseph <jithu83@gmail.com>
When the user starts the script with log cli option, it displays the
key presses to the console. This info is helpful in knowing the
key-mappings for a new controller.

However some details like maximum and minimum values for absolute
axes are missing. Displaying capabilities will help resolve this.

Here is a snippet from this:
...
{('EV_ABS', 3): [(('ABS_X', 0),
                  AbsInfo(value=-386, min=-32768, max=32767, fuzz=16, flat=128, resolution=0)),
...

Signed-off-by: Jithu Joseph <jithu83@gmail.com>
Also added benchmark section.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant