• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Controllers v
« Previous 1 ... 65 66 67 68 69 ... 321 Next »

Can't get -TR model wiimote connected in Linux (udev working)
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Can't get -TR model wiimote connected in Linux (udev working)
06-07-2018, 01:30 PM (This post was last modified: 06-07-2018, 02:27 PM by camus.)
#1
camus Offline
Junior Member
**
Posts: 5
Threads: 2
Joined: Jun 2018
I can't get my brand new wiimote -TR model working in dolphin.
I am running current Arch linux.
Now using XFCE but have also been using enlightenment WM.
Code:
[camus@camus ~]$ lsusb
'Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 13fe:5500 Kingston Technology Company Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[camus@camus ~]$
Using the plugable usb 4.0 dongle with Broadcom chipset as above.
Code:
[BluetoothPassthrough]
Enabled = True
VID = 2652
PID = 8680
LinkKeys =
[USBPassthrough]
Devices = 0a5c:21e8
[AutoUpdate]
UpdateTrack =
HashOverride =
[NetPlay]
TraversalChoice = direct
I have converted the VID & PID to decimal and hardcoded for bluetooth passthrough to ~/.config/dolphin-emu/Dolphin.ini as instructed elsewhere.
Code:
[camus@camus rules.d]$ sudo cat 10*

#SUBSYSTEM=="usb", ATTRS{idVendor}=="24c0", ATTRS{idProduct}=="0003", SYMLINK="weather", MODE="0666", GROUP="users"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0a5c", ATTRS{idProduct}=="21e8", TAG+="uaccess", TAG+="udev-acl"

# Set bluetooth power up
#ACTION=="add", KERNEL=="hci0", RUN+="/usr/bin/hciconfig hci0 up"
[camus@camus rules.d]$
Udev rule set-up and functioning. No longer getting the "Failed to open Bluetooth device: LIBUSB_ERROR_ACCESS" error.

Now I'm stuck. The wiimote simply doesn't interface with dolphin, but games work.
Before I got the udev rule set-up I did confirm that the wiimote paired with bluetooth-manager and was able to interact with my desktop.
I have since unpaired the wiimote and passthrough appears to be working properly.

Any help is appreciated....
Find
Reply
06-08-2018, 04:49 AM
#2
camdbug Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Jun 2018
Are they third party wiimotes? I've literally just posted a question around a similar problem with 3rd party TR01 remotes. I can get them to sync after 3-4 minutes of trying, but they disconnect after a couple of minutes and you have to start again. My original wiimote (pre 2010) works just fine though.
Find
Reply
06-08-2018, 04:50 AM (This post was last modified: 06-08-2018, 05:04 AM by camdbug.)
#3
camdbug Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Jun 2018
I'm also using Bluetooth passthrough with appropriate udev permissions. It's definitely remote specific at this stage as I've had the third party ones synced at primary controller but even if my old one is secondary, it retains connection whereas the 3rd party ones don't.
Find
Reply
06-08-2018, 05:20 AM
#4
camus Offline
Junior Member
**
Posts: 5
Threads: 2
Joined: Jun 2018
This is a brand new Nintendo branded wiimote.
Find
Reply
06-08-2018, 05:27 AM (This post was last modified: 06-08-2018, 05:29 AM by camdbug.)
#5
camdbug Offline
Junior Member
**
Posts: 8
Threads: 1
Joined: Jun 2018
Damn. All I can say right now is that my old style remote works perfectly. It's the new style TR ones, third party for me, original for you, that are causing the issue. I know dolphinbar issued firmware updates to support new style remotes, but I'm already about to send my Dolphinbar back as it underperforms compared to Bluetooth plus custom IR bars. I wonder if we have a TR specific problem with direct Bluetooth pass through... Which is a relatively new feature after all...
Find
Reply
06-08-2018, 10:56 AM
#6
camus Offline
Junior Member
**
Posts: 5
Threads: 2
Joined: Jun 2018
(06-08-2018, 05:27 AM)camdbug Wrote: Damn. All I can say right now is that my old style remote works perfectly. It's the new style TR ones, third party for me, original for you, that are causing the issue. I know dolphinbar issued firmware updates to support new style remotes, but I'm already about to send my Dolphinbar back as it underperforms compared to Bluetooth plus custom IR bars. I wonder if we have a TR specific problem with direct Bluetooth pass through... Which is a relatively new feature after all...

I'm not using the dolphinbar but a battery powered IR bar.
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode