Xensiv Game Controller debug Trace. Controller connects but the buttons do not work.

[Dred500]

BlueRetro firmware version

25.01

BlueRetro firmware specification

HW1

BlueRetro firmware variant

System specific

BlueRetro hardware type

External adapter dongle (1 port only)

Manufacturer

Retro Scaler For SNES

System used

Nintendo SFC SNES

Bluetooth controller brand & name

Infineon Xensiv BLE Controller

What is the problem? (only list ONE problem per report)

Controller connects but none of the buttons work.

I am using the Retro Scaler SNES, but also have a Retro Scaler for Genesis, and Sega Master System.

What did you expect to happen?

The controller buttons to work.

Up, Down, Left, Right
T, F, I, X
L1, R1
L2, R2
Analog left push button
Analog right push button

Analog left = Up, Down, Left, Right
Analog right = Up, Down, Left, Right

*The analog sticks are both a button when pushed down and rotation. When I push the button down, this will also cause a little movement in the rotation. Windows 11 trace gave 04 for Left, and 08 for right when I pushed the button down.

I traced both with windows 11 and BlueRetro Debug Trace and attached both files.

Attach BlueRetro debug trace here

XensivWindows11Trace.zip

br_debug_trace.bin.zip

[Dred500]

I'm not sure if this can help but the values when using the Microsoft Bluetooth test Platform. These values come up in different locations in the packet and I have no idea how it works. I looked for these values to make sure that all my button presses were registered.

You can delete this if it is useless information.

Again, I want to thank you for your work here. This is the only controller I can use because I get finger pain now in my 40's if I use a normal controller, this controller is touch sensitive so I don't have to push on any button.

UP = 10
Down = 20
Left = 40
right = 80

T = 08
F = 01
I = 04
X = 02

L2 = 40 R2 = 80
L1 = 10 R1 = 20

Left Analog stick push button = 04
Right Analog stick push button = 08

Movement of the analog sticks too complicated to list, but they seem to have an XX XX value.

[Dred500]

I decided to update the firmware on my controller to make it work with blue retro. It was difficult and took many days to figure it out as I am not a programmer and only using Chat GPT.

However, after messing around enough, I updated all the code, remapped the buttons, updated bluetooth, and now it works perfectly with blue retro with the default buttons set at the right places.

What really through me off was Chat GPT was not telling me that BLE bluetooth is different in that the first report sent is not the report ID. Classic Blue tooth will have the report id in report[0]j.

I only learned this after trial and error and seeing that the controller was stuck down right, which was because it was seeing my report id 3 as a hatswitch.

I had a lot of trouble because I was able to get it to work in windows, but then blue retro was not seeing the controller. I was also using the 8bitDo hid descriptors from blueretro database.

I used the 8bitduo hid descriptors: Here is the code I used. You can see in report[0] is the hat switch. This is where Chat GPT was saying it has to be the report id 3. It wasn't until I google gemini told me that BLE doesn't work like this as it looks for the report in report_reference[]

uint8_t app_hids_gamecontrolller_report[] = {0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
0x00, };

uint8_t app_hids_gamecontrolller_report_report_reference[] = {0x02, 0x01,};

app_hids_gamecontrolller_report[0] = (hatValue & 0x0F); // Report ID (matches Report ID used in BlueRetro for gamepad)
app_hids_gamecontrolller_report[1] = 0x00;
app_hids_gamecontrolller_report[2] = 0x00;
app_hids_gamecontrolller_report[3] = 0x00;
app_hids_gamecontrolller_report[4] = 0x00;
app_hids_gamecontrolller_report[5] = 0x00;
app_hids_gamecontrolller_report[6] = 0x00; //
app_hids_gamecontrolller_report[7] = (uint8_t)(buttonStates & 0xFF);
app_hids_gamecontrolller_report[8] =(uint8_t)((buttonStates >> 8) & 0xFF);

uint8_t app_hids_report_map[] = {
0x05, 0x01, // Usage Page (Generic Desktop Ctrls)
0x09, 0x05, // Usage (Game Pad)
0xA1, 0x01, // Collection (Application)
0x85, 0x02, // Report ID (3)
0x05, 0x01, // Usage Page (Generic Desktop Ctrls)
0x15, 0x00, // Logical Minimum (0)
0x25, 0x07, // Logical Maximum (7)
0x46, 0x3B, 0x01, // Physical Maximum (315)
0x95, 0x01, // Report Count (1)
0x75, 0x04, // Report Size (4)
0x65, 0x14, // Unit (System: English Rotation, Length: Centimeter)
0x09, 0x39, // Usage (Hat switch)
0x81, 0x42, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,Null State)
0x75, 0x01, // Report Size (1)
0x95, 0x04, // Report Count (4)
0x81, 0x01, // Input (Const,Array,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x15, 0x00, // Logical Minimum (0)
0x26, 0xFF, 0x00, // Logical Maximum (255)
0x09, 0x30, // Usage (X)
0x09, 0x31, // Usage (Y)
0x09, 0x32, // Usage (Z)
0x09, 0x35, // Usage (Rz)
0x95, 0x04, // Report Count (4)
0x75, 0x08, // Report Size (8)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x05, 0x02, // Usage Page (Sim Ctrls)
0x15, 0x00, // Logical Minimum (0)
0x26, 0xFF, 0x00, // Logical Maximum (255)
0x09, 0xC4, // Usage (Accelerator)
0x09, 0xC5, // Usage (Brake)
0x95, 0x02, // Report Count (2)
0x75, 0x08, // Report Size (8)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0x05, 0x09, // Usage Page (Button)
0x19, 0x01, // Usage Minimum (0x01)
0x29, 0x10, // Usage Maximum (0x10)
0x15, 0x00, // Logical Minimum (0)
0x25, 0x01, // Logical Maximum (1)
0x75, 0x01, // Report Size (1)
0x95, 0x10, // Report Count (16)
0x81, 0x02, // Input (Data,Var,Abs,No Wrap,Linear,Preferred State,No Null Position)
0xC0, // End Collection

[darthcloud]

Sorry I didn't had the time to help you out, but I'm glad you figured it out!

Thanks for sharing the solution!