Recalbox Forum

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • recalbox.com
    • Gitlab repository
    • Documentation
    • Discord

    Solved Can't pair bluetooth MadCatz C.T.R.L.R

    GamePad/GPIO/USB encoder
    cant pair bluetooth madcatz c.t.r.l.r
    5
    27
    16858
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • elchhome
      elchhome last edited by

      mmh. In order to get even an emulated mouse function running the device has to be paired.
      I think the gamepad should be exactly the same as yours, but I tried all three modes and it doesn't pair.
      The home button keeps blinking read and blue and nothing is working although the GUI said "ok".

      1 Reply Last reply Reply Quote 0
      • marchegiano
        marchegiano last edited by

        I just tried it again. All I can tell you is exactly what I'm doing and what I'm experiencing. I have the dongle plugged in and the controller, in BT mode, on and searching before I turn on the pi. While recalbox is booting it connects, or at least stops blinking and stays blue, and after it's done booting when I slide the slider over to mouse and I can use the d-pad. At no point am I prompted to configure anything or pair anything. This time around I went ahead and tried to configure it. Nothing comes up under BT pairing and when I went to configure a controller and held down a direction on the d-pad it comes up as keyboard. I turned off the controller, and plugged it in through the micro usb port, I meant to unplug the dongle but I forgot, dunno if that matters or not. the home button went red, but I still got the same functions. on mouse mode the d-pad comes up as a keyboard. Nothing else works and nothing comes up under bluetooth.

        The only other thing I can say is I have kept my firmware up to date. if you have owned the controller for a few years without updating, updating the firmware might be why i'm getting a d-pad.

        Have you tried the moderator's suggestion? I've been trying to but I can't find any of my dongles.

        1 Reply Last reply Reply Quote 0
        • elchhome
          elchhome last edited by elchhome

          You're completely right. I tried anothe dongle and now I have exactly the same behavior as you described.
          The interesting thing is, that the additional buttons like fastforward/fastbackward/pause and the digital arrow keys are then received as keyboard strokes and not as gamepad buttons.

          btw. my controller firmware is on latest level v1.2.5 that can be downloaded from madcatz.com

          1 Reply Last reply Reply Quote 0
          • Substring
            Substring last edited by

            Guyz, seems to me it's an android pad ONLY which means it may not trigger any joypad event. Very easy to find out : once paired (in that "mouse" mode or whatever), run evtest, select your pad, foold around with the buttons. If you only get some keys starting with KEY_, you're screwed because we don't handle keyboards. Well there might be a solution with the xarcade2jstick driver, but it's very restrictive on keys it handles (MAME keys in fact).

            But if you get some BTN_ events, we could do something probably

            Former dev - Please reply with @substring so that i am notified when you answer me
            Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

            1 Reply Last reply Reply Quote 0
            • elchhome
              elchhome last edited by

              evtest brings for me something like:

              Event: time 1471421830.222857, -------------- SYN_REPORT ------------
              Event: time 1471421839.037076, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
              Event: time 1471421839.037076, type 1 (EV_KEY), code 311 (BTN_TR), value 1
              Event: time 1471421839.037076, -------------- SYN_REPORT ------------
              Event: time 1471421839.222181, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
              Event: time 1471421839.222181, type 1 (EV_KEY), code 311 (BTN_TR), value 0
              Event: time 1471421839.222181, -------------- SYN_REPORT ------------
              Event: time 1471421839.747441, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
              Event: time 1471421839.747441, type 1 (EV_KEY), code 310 (BTN_TL), value 1
              Event: time 1471421839.747441, -------------- SYN_REPORT ------------
              Event: time 1471421839.935186, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
              Event: time 1471421839.935186, type 1 (EV_KEY), code 310 (BTN_TL), value 0
              Event: time 1471421839.935186, -------------- SYN_REPORT ------------
              Event: time 1471421841.059117, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
              Event: time 1471421841.059117, type 1 (EV_KEY), code 311 (BTN_TR), value 1
              Event: time 1471421841.059117, -------------- SYN_REPORT ------------
              Event: time 1471421841.184228, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90008
              Event: time 1471421841.184228, type 1 (EV_KEY), code 311 (BTN_TR), value 0
              Event: time 1471421841.184228, -------------- SYN_REPORT ------------
              Event: time 1471421850.286365, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
              Event: time 1471421850.286365, type 1 (EV_KEY), code 304 (BTN_SOUTH), value 1
              Event: time 1471421850.286365, -------------- SYN_REPORT ------------
              Event: time 1471421850.384091, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
              Event: time 1471421850.384091, type 1 (EV_KEY), code 304 (BTN_SOUTH), value 0
              Event: time 1471421850.384091, -------------- SYN_REPORT ------------
              Event: time 1471421851.221895, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
              Event: time 1471421851.221895, type 1 (EV_KEY), code 305 (BTN_EAST), value 1
              Event: time 1471421851.221895, -------------- SYN_REPORT ------------
              Event: time 1471421851.320732, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90002
              Event: time 1471421851.320732, type 1 (EV_KEY), code 305 (BTN_EAST), value 0
              Event: time 1471421851.320732, -------------- SYN_REPORT ------------
              

              and the button names doesn't even change when changing between the three controller modes (android/mouse/windows)
              So finally it comes down to a button name mapping issue

              Substring 1 Reply Last reply Reply Quote 0
              • acris
                acris last edited by

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • Substring
                  Substring @elchhome last edited by

                  @elchhome so it's paired, sends joypad events. If there are also mouse events sticked to it, it won't be recognized as a joypad but as a mouse. Need a udev rule. We need you to run /recalbox/scripts/recalbox-support.sh with your pad paired and upload the file somewhere. With this, we will know if your pad is seen as a mouse/keyboard or pad, and make what's necessary to have it recognised as a pad

                  Former dev - Please reply with @substring so that i am notified when you answer me
                  Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                  1 Reply Last reply Reply Quote 0
                  • elchhome
                    elchhome last edited by

                    I hope you can download it:
                    h_t_t_p_s://drive.google.com/open?id=0BxMwQBosHAcbUUVWVkxoVkVnN2M

                    1 Reply Last reply Reply Quote 0
                    • elchhome
                      elchhome last edited by

                      @subs
                      Did you download the file and do you already have an idea how to fix that?

                      1 Reply Last reply Reply Quote 0
                      • Substring
                        Substring last edited by

                        nope, didn't have the opportunity yet

                        Former dev - Please reply with @substring so that i am notified when you answer me
                        Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                        1 Reply Last reply Reply Quote 0
                        • elchhome
                          elchhome last edited by

                          @subs
                          is there a file where I can add the button mapping by hand?

                          1 Reply Last reply Reply Quote 0
                          • Substring
                            Substring last edited by

                            @elchhome sorry dude, I was out for the weekend. Gonna check your file today and report back.

                            Former dev - Please reply with @substring so that i am notified when you answer me
                            Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                            1 Reply Last reply Reply Quote 0
                            • Substring
                              Substring last edited by

                              @elchhome try those commands through SSH :

                              mount -o remount, rw /
                              echo 'SUBSYSTEM=="input", ATTRS{name}=="Mad Catz C.T.R.L.R", MODE="0666", ENV{ID_INPUT_JOYSTICK}="1"' >> /etc/udev/rules.d/99-joysticks-exotics.rules
                              reboot && logout
                              

                              Your pad is, as I expected, considered as a mouse/keyboard. Those commands above will force the joystick bit, and it should then work. Can you confirm ? If yes, we'll add your pad to 4.1 so that it's automatically detected as a pad

                              Former dev - Please reply with @substring so that i am notified when you answer me
                              Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                              1 Reply Last reply Reply Quote 1
                              • elchhome
                                elchhome last edited by elchhome

                                @subs
                                Thanks a lot! This change makes the controller available to the system.
                                Good work! 🙂

                                1 Reply Last reply Reply Quote 0
                                • Substring
                                  Substring last edited by Substring

                                  @acris a reminder for you to include the udev rule in 4.1

                                  Former dev - Please reply with @substring so that i am notified when you answer me
                                  Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                                  1 Reply Last reply Reply Quote 0
                                  • acris
                                    acris last edited by

                                    @subs it s done
                                    https://github.com/recalbox/recalbox-buildroot/pull/461/commits/a00f6c3a6c226a2bcd54044fd0e477c10c61e2e0

                                    1 Reply Last reply Reply Quote 0
                                    • Substring
                                      Substring last edited by

                                      @acris Nice !

                                      Former dev - Please reply with @substring so that i am notified when you answer me
                                      Ex dev - Merci de me répondre en utilisant @substring pour que je sois notifé

                                      1 Reply Last reply Reply Quote 0
                                      • wden86
                                        wden86 last edited by

                                        Hi all,

                                        I just got a raspberry pi3, installed recalbox 4.0 on it and tried to set up my gamepads.

                                        No trouble with 8bitDo NES pro, nor with an USB generic gamepad.

                                        I tried to set up my Mad Catz C.T.R.L.R with this topic's solution.

                                        Adding a line in the joystick rule file didn't work at first because of device name.
                                        Indeed, the sdptool command on the MAC address told me the device's name is not "Mad Catz C.T.R.L.R", but "HID Gamepad".

                                        The CTRLR switch is set on the gamepad.

                                        Regars,

                                        Denis

                                        1 Reply Last reply Reply Quote 0
                                        • First post
                                          Last post

                                        Want to support us ?

                                        74
                                        Online

                                        99.6k
                                        Users

                                        28.1k
                                        Topics

                                        187.1k
                                        Posts

                                        Copyright © 2021 recalbox.com