8BitDo P30 classic Modkit Mapping Problem [solved]

danny007

@mitu first of all thanks for the fast reply.

When you say that "controllers are identicals?" What are you talking about?
The controllers have diferent Bluetooth identificator. But that dont reply your question.
The controllers have the same name. You can see the list of paired items

All my controllers have the same 'connect mode' because is a requirement of 8bitdo to sync with my Raspberry Pi. At least that's what I was told was necessary to sync with the Raspberry Pi.

Thanks for your help & your time

mitu

@danny007 said in 8BitDo P30 classic Modkit Mapping Problem:

When you say that "controllers are identicals?" What are you talking about?

I was asking if the PS classic controllers are identical and they're not different vendor/models. Since they connect via the modkit, their model is 'obscured' by the Bluetooth adapter.

The controllers have diferent Bluetooth identificator. But that dont reply your question.
The controllers have the same name. You can see the list of paired items

Ok, so they have the same name.

You need to check if they also produce the same inputs for the problematic buttons. You can check this with jstest, from the command line.

Exit EmulationStation and just with one of the controllers connected (one of the 2 PS Classic) run

jstest /dev/input/js0

Press the ◯ (Circle) and the X buttons and note the button numbers that are toggled on screen. Press Ctrl + C to stop the test

Then, connect the other PS Classic controller and repeat the test. See if the button numbers match for both controllers.

danny007

@mitu said in 8BitDo P30 classic Modkit Mapping Problem:

I was asking if the PS classic controllers are identical and they're not different vendor/models. Since they connect via the modkit, their model is 'obscured' by the Bluetooth adapter.

PS classic controllers are identical. Same vendor and same model. Info 8BitDo.

@mitu said in 8BitDo P30 classic Modkit Mapping Problem:

Ok, so they have the same name.
You need to check if they also produce the same inputs for the problematic buttons. You can check this with jstest, from the command line.
Exit EmulationStation and just with one of the controllers connected (one of the 2 PS Classic) run
jstest /dev/input/js0

Press the ◯ (Circle) and the X buttons and note the button numbers that are toggled on screen. Press Ctrl + C to stop the test
Then, connect the other PS Classic controller and repeat the test. See if the button numbers match for both controllers.

I connect PS Classic controller 1 and I make the test with result:
O - 1
X - 0
I shut down PS Classic controller 1
I connect PS Classic controller 2 and I make the test with result:
O - 0
X - 1

mitu

@danny007 said in 8BitDo P30 classic Modkit Mapping Problem:

I connect PS Classic controller 1 and I make the test with result:
O - 1
X - 0
[..]
I connect PS Classic controller 2 and I make the test with result:
O - 0
X - 1

Do you see the issue here ? Though they're the same, they have different button actions - A and B (East/South) are switched.

Since they're identified by the same name (8BitDo P30 modkit), they're using the same configuration and that's why the mapping is incorrect for one of them.
Nothing much that RetroPie can do here - can you check if the modkit firmware is identical, maybe upgrade it on both ?

EDIT: now that I think of it, would it be possible that the modkit connection to the gamepad's buttons are different ? So that A/East is connected on 1st gamepad to the same modkit connection as B/South on the 2nd (and vice-versa) ? Hm, looking at the schematics of the modkit, this doesn't seem possible.

danny007

@mitu said in 8BitDo P30 classic Modkit Mapping Problem:

Do you see the issue here ? Though they're the same, they have different button actions - A and B (East/South) are switched.
Since they're identified by the same name (8BitDo P30 modkit), they're using the same configuration and that's why the mapping is incorrect for one of them.
Nothing much that RetroPie can do here - can you check if the modkit firmware is identical, maybe upgrade it on both ?

I have tryed to force mapping "incorrectly" in one of that. For example put one of the controllers the X and O interchanged but... saving the configuration by name...

Other curiosity, to see your oppinion is...

Do you think the next info have logical? I turn on controller 1 first and later controller 2 the first controller will have incorrect mapping. I shut down the sistem and restart. I turn on controller 2 first and next the 1 and the controller 2 that I turn on first have incorrect mapping.

In summary, the problem is in the controller?

I have other 2 NES and having same name... etc... works fine
I have other 2 of SNES and having same name... etc... works fine

mitu

@danny007 said in 8BitDo P30 classic Modkit Mapping Problem:

In summary, the problem is in the controller?

I don't think it's the controller, but the 8BitDo modkit. Try updating the firmware on both, just to make sure they have the same version.

danny007

@mitu said in 8BitDo P30 classic Modkit Mapping Problem:

I don't think it's the controller, but the 8BitDo modkit. Try updating the firmware on both, just to make sure they have the same version.

Sorry, when I said controller I wanted to say 8BitDo modkit or gamepad.

This afternoon I try the update tool to see if there are new versions since I just checked that there are people who have updated the modkit.

I know the reason that I thought that modkits not able to update. In the 8BitDo support site, only appears the option "Firmware Updater" into original controllers, not modkits. However seems that if you connect modkit can be updated.

https://imgur.com/gallery/ZKm3oUu

I will give updates about that

danny007

This post is deleted!

danny007

@mitu said in 8BitDo P30 classic Modkit Mapping Problem:

Try updating the firmware on both, just to make sure they have the same version.

I update all my 7 8BitDo modkits

Desarm and connect
Update

I read that one of the updates fix the issue of A and B being mixed up. Maybe my problem true?
Test Result = Same problem that I have before
Modkit 1
O - 0
X - 1

Modkit 2
O - 1
X - 0

mitu

@danny007 said in 8BitDo P30 classic Modkit Mapping Problem:

I read that one of the updates fix the issue of A and B being mixed up. Maybe my problem true?

As shown by testing, yes.

If the issue still persists after updating the firmware, then you may want to send an email to 8BitDo support and let them know it's not working for you.

danny007

I'm still waiting for a response from technical support...

danny007

Hallelujah

Works Fine. 8BitDo give me the easy 🥺... solution.
Hold SELECT + DPAD DOWN = Switch the positions of the A-B and X-Y keys

8BidDo SOLUTION Video

Big thanks to your support @mitu

mitu

Glad you got it sorted out and thanks for adding the solution to the topic.

Hold SELECT + DPAD DOWN = Switch the positions of the A-B and X-Y keys

It would be nice if 8BitDo would include this info in the Modkit manual, they are mentioning _ SELECT + DPAD DOWN_ as a way to send the Home button only when the modkit is paired in Switch mode.

I'll mark this topic as solved.