8BitDo Ultimate C 2.4g Wireless Controller not working

[Scdk]

First of all thanks continuing the project!!

Information Atmosphere version: 1.6.2 Switch OS version: 17.0.1 Syscon version: 1.2.1 Controller: 8BitDo Ultimate C 2.4g Wireless Controller

Description I connect the controller in both d-input or x-input mode and even though the light of the controller stays on, indicating a successful connection, the controller is not recognized by the switch. Neither buttons, analog sticks of dpad works and the controller doesn't even show up in the controllers menu.

I tried to verify the HID code for the 8bitdo in the device manager, but when I was going to insert it into the config file I noticed that it was already there (2dc8-3106). I noticed that in x-input mode the button layout resemble more the xbox template than the xbox360, but even changing this configuration the controller still not works.

When I enabled the log level 0 I got the message "No HID or XBOX interfaces found !" in the logs.

Both my config and log files are in the zip attached to the issue.

Logs logs.zip

[o0Zz]

HI, yeah the profile don't have any impact regarding the detection, it will have an impact only for the configuration. Here the switch don't detect controller at all. What happen if you do exactly the same thing on a PC ? Does your PC detect the controller ? I assume you tried it with the dongle, could you try just to plug it with a USB cable to see if it change something ? Thanks

[o0Zz]

Any progress on this issue ?

[Scdk]

The logs previously sent were in fact made using the dongle. I had made tests with the cable but unfortunately the controller didn't even show signs of connection, the center LED kept blinking, indicating it was searching for connection.

My PC with Windows detects the controller normally, both with the dongle and the cable.

The log file of my tests can be found bellow.

log.log

[texita]

May i ask if you have Mission control enabled?

[o0Zz]

Ok sounds to be a controller issue,. I did some research on the net and people have same issue than you with various systems (linux etc ...) a workaround is to force the system to detect this controller with vid/pid and associate the correct driver.

So let's try it, edit you configuration file like that:

[global]
discovery_mode=1
discovery_vidpid=2dc8-3106

Reference: https://gist.github.com/ammuench/0dcf14faf4e3b000020992612a2711e2

Let us know if its better.

[Scdk]

I had mission control enabled, just to be sure I disabled it.

Unfortunately even with the edited configuration file the controller still wasn't detected.

The log file of my tests can be found bellow.

log.log

[texita]

I had mission control enabled, just to be sure I disabled it.

Unfortunately even with the edited configuration file the controller still wasn't detected.

The log file of my tests can be found bellow.

log.log

Just to be sure:

• have you tried with mission control disabled (once you disabled mission control, you have to reboot the switch, and be sure is disabled again after reboot, if you are not sure, best way to do that using https://github.com/ppkantorski/Ultrahand-Overlay )
• and discovery_mode=0? (untouched config.ini or log level 0)
• try again with dongle and only cable
• x-input (this should work in mode discovery_mode=0) and d-input just to try
• i don't think this matter, but have you tried a firmware upgrade? https://support.8bitdo.com/firmware-updater.html
• another thing, have you tried what they say here? like, put in X mode, press and hold [minus+LB] buttons for 5 seconds https://support.8bitdo.com/faq/ultimate-2-4g-controller.html

[Scdk]

I disabled the mission control via hekate toolbox and restarted the switch, I even tried to connect my ps4 controller but it didn't work so motion control was in fact not working.

Just to be sure I attached both my config and log files bellow. But I tried both discovery mode 0 and 1 with discovery_vidpid=2dc8-3106.

I tried both cable and dongle in both modes, the cable doesn't seem to send any signal to the switch, it just charges the controller.

I updated the firmware of both the dongle and the controller and tried every combination again, but unfortunately had the same result. The combinations wore: cable, X input dongle, D input dongle and all those again with discovery mode in 0.

In the 8BitDo Ultimate C 2.4g Wireless Controller the change between X mode and D mode are done by turning the controller on by pressing the X button or the B button. I tried on my PC and could see that the controller was in fact changing modes.

config_and_log.zip

[texita]

Thanks for your tests, i explain why asked you this for everyone:

Because of the behavior of no logs when a pad is connected was similar to ps3 pads when mission control is enabled, i personally tested that. The problem is the bluetooth, have a look on this issue, is still valid for this sys-con https://github.com/ndeadly/MissionControl/issues/782 So i was thinking your pad got bluetooth feature because of this issue https://github.com/ndeadly/MissionControl/issues/651 if you read the last comment from ndeadly he's not sure C version of this pad is without bluetooh. So best thing to do is try your pad without Mission control enabled until we get it working.

At this point i don't know why you get empty logs, more questions that i can ask: have you got other controllers working? like ps4 pad is working with sys-con? other installed modules? without sys-con enabled is your controller working on the switch?

Maybe with these informations @o0Zz can think something

[o0Zz]

Hi, 4 questions here: 1) Could you try this verion and let us know if it change something: sys-con-1.2.2-ATMOSPHERE-1.6.x-custom.zip 2) Could you let us know if you installed any driver on your windows PC ? 3) Could you send a screenshot of your 'joy.cpl' and your 'Device Manager' to try to understand how the controller is detected by windows 4) Additionnaly, could you can get the VID/PID reported by windows

Thanks