1+ #include < Bluepad32.h>
2+
3+ GamepadPtr myGamepads[BP32_MAX_GAMEPADS];
4+
5+ // This callback gets called any time a new gamepad is connected.
6+ // Up to 4 gamepads can be connected at the same time.
7+ void onConnectedGamepad (GamepadPtr gp) {
8+ bool foundEmptySlot = false ;
9+ for (int i = 0 ; i < BP32_MAX_GAMEPADS; i++) {
10+ if (myGamepads[i] == nullptr ) {
11+ Serial.printf (" CALLBACK: Gamepad is connected, index=%d\n "
12+ // Additionally, you can get certain gamepad properties like:
13+ // Model, VID, PID, BTAddr, flags, etc.
14+ GamepadProperties properties = gp->getProperties ();
15+ Serial.printf (" Gamepad model: %s, VID=0x%04x, PID=0x%04x\n " getModelName ().c_str (), properties.vendor_id ,
16+ properties.product_id );
17+ myGamepads[i] = gp;
18+ foundEmptySlot = true ;
19+ break ;
20+ }
21+ }
22+ if (!foundEmptySlot) {
23+ Serial.println (" CALLBACK: Gamepad connected, but could not found empty slot"
24+ }
25+ }
26+
27+ void onDisconnectedGamepad (GamepadPtr gp) {
28+ bool foundGamepad = false ;
29+
30+ for (int i = 0 ; i < BP32_MAX_GAMEPADS; i++) {
31+ if (myGamepads[i] == gp) {
32+ Serial.printf (" CALLBACK: Gamepad is disconnected from index=%d\n "
33+ myGamepads[i] = nullptr ;
34+ foundGamepad = true ;
35+ break ;
36+ }
37+ }
38+
39+ if (!foundGamepad) {
40+ Serial.println (" CALLBACK: Gamepad disconnected, but not found in myGamepads"
41+ }
42+ }
43+
44+ // Arduino setup function. Runs in CPU 1
45+ void setup () {
46+ Serial.begin (115200 );
47+ Serial.printf (" Firmware: %s\n " firmwareVersion ());
48+
49+ // Setup the Bluepad32 callbacks
50+ BP32.setup (&onConnectedGamepad, &onDisconnectedGamepad);
51+
52+ // "forgetBluetoothKeys()" should be called when the user performs
53+ // a "device factory reset", or similar.
54+ // Calling "forgetBluetoothKeys" in setup() just as an example.
55+ // Forgetting Bluetooth keys prevents "paired" gamepads to reconnect.
56+ // But might also fix some connection / re-connection issues.
57+ BP32.forgetBluetoothKeys ();
58+ }
59+
60+ // Arduino loop function. Runs in CPU 1
61+ void loop () {
62+ // This call fetches all the gamepad info from the NINA (ESP32) module.
63+ // Just call this function in your main loop.
64+ // The gamepads pointer (the ones received in the callbacks) gets updated
65+ // automatically.
66+ BP32.update ();
67+
68+ // It is safe to always do this before using the gamepad API.
69+ // This guarantees that the gamepad is valid and connected.
70+ for (int i = 0 ; i < BP32_MAX_GAMEPADS; i++) {
71+ GamepadPtr myGamepad = myGamepads[i];
72+
73+ if (myGamepad && myGamepad->isConnected ()) {
74+ // There are different ways to query whether a button is pressed.
75+ // By query each button individually:
76+ // a(), b(), x(), y(), l1(), etc...
77+ if (myGamepad->a ()) {
78+ static int colorIdx = 0 ;
79+ // Some gamepads like DS4 and DualSense support changing the color LED.
80+ // It is possible to change it by calling:
81+ switch (colorIdx % 3 ) {
82+ case 0 :
83+ // Red
84+ myGamepad->setColorLED (255 , 0 , 0 );
85+ break ;
86+ case 1 :
87+ // Green
88+ myGamepad->setColorLED (0 , 255 , 0 );
89+ break ;
90+ case 2 :
91+ // Blue
92+ myGamepad->setColorLED (0 , 0 , 255 );
93+ break ;
94+ }
95+ colorIdx++;
96+ }
97+
98+ if (myGamepad->b ()) {
99+ // Turn on the 4 LED. Each bit represents one LED.
100+ static int led = 0 ;
101+ led++;
102+ // Some gamepads like the DS3, DualSense, Nintendo Wii, Nintendo Switch
103+ // support changing the "Player LEDs": those 4 LEDs that usually indicate
104+ // the "gamepad seat".
105+ // It is possible to change them by calling:
106+ myGamepad->setPlayerLEDs (led & 0x0f );
107+ }
108+
109+ if (myGamepad->x ()) {
110+ // Duration: 255 is ~2 seconds
111+ // force: intensity
112+ // Some gamepads like DS3, DS4, DualSense, Switch, Xbox One S support
113+ // rumble.
114+ // It is possible to set it by calling:
115+ myGamepad->setRumble (0xc0 /* force */ 0xc0 /* duration */
116+ }
117+
118+ // Another way to query the buttons, is by calling buttons(), or
119+ // miscButtons() which return a bitmask.
120+ // Some gamepads also have DPAD, axis and more.
121+ Serial.printf (
122+ " idx=%d, dpad: 0x%02x, buttons: 0x%04x, axis L: %4d, %4d, axis R: %4d, "
123+ " %4d, brake: %4d, throttle: %4d, misc: 0x%02x\n "
124+ i, // Gamepad Index
125+ myGamepad->dpad (), // DPAD
126+ myGamepad->buttons (), // bitmask of pressed buttons
127+ myGamepad->axisX (), // (-511 - 512) left X Axis
128+ myGamepad->axisY (), // (-511 - 512) left Y axis
129+ myGamepad->axisRX (), // (-511 - 512) right X axis
130+ myGamepad->axisRY (), // (-511 - 512) right Y axis
131+ myGamepad->brake (), // (0 - 1023): brake button
132+ myGamepad->throttle (), // (0 - 1023): throttle (AKA gas) button
133+ myGamepad->miscButtons () // bitmak of pressed "misc" buttons
134+ );
135+
136+ // You can query the axis and other properties as well. See Gamepad.h
137+ // For all the available functions.
138+ }
139+ }
140+
141+ // The main loop must have some kind of "yield to lower priority task" event.
142+ // Otherwise the watchdog will get triggered.
143+ // If your main loop doesn't have one, just add a simple `vTaskDelay(1)`.
144+ // Detailed info here:
145+ // https://stackoverflow.com/questions/66278271/task-watchdog-got-triggered-the-tasks-did-not-reset-the-watchdog-in-time
146+
147+ // vTaskDelay(1);
148+ delay (150 );
149+ }
0 commit comments