Besavior Controller DIY Kit + BDM-020: R2 capped at 69%, Self Test stuck at L2

blizzarder

Hi everyone,

I'm trying to find out whether anyone has experienced a similar issue with the BK-BSV-KIT on a DualSense BDM-020 motherboard.

Hardware

• Sony DualSense Controller
• Motherboard: BDM-020
• BK-BSV-KIT installed
• GuliKit TMR (720° Tension Adjustable) thumbsticks installed
• Back buttons installed
  

Background

Before the modification, the controller was fully functional.

I confirmed that both L2 and R2 reached 100% input before sending it to the modding service.

The installer also tested the controller after installation and informed me that:

R2 only reaches about 69%.

At the time I accepted it because I wanted the controller back quickly.

However, after using it for a while, the issue became more noticeable in games.

SymptomsR2 only reaches 69%

In Gamepad Tester:

• L2 = 0% ~ 100% (normal)
• R2 = 0% ~ 69% only
  

R2 increases smoothly and linearly from 0% to 69%.

It is not jumping, flickering, or unstable.

Examples:

• Racing games: throttle reaches only ~69%
• Horizon series: bow draw is incomplete
• Some games do not register a full trigger press
  

Back button mapped to R2

This is the strange part.

When I map a back button to R2:

• Pressing the back button instantly sets R2 to exactly 69%
• Never 100%
  

This makes me think the issue may not be the physical trigger sensor itself.

It looks like the BK-BSV-KIT internally believes that the maximum R2 value is 69%.

Self Test issue

Using the OLED Self Test:

• Touchpad test seems abnormal
• It shows an X on the touchpad icon
• However, pressing a button allows the test to continue
  

Then:

• The test reaches the L2 step
• The test completely stops there
• Pressing L2 does not advance the test
  

What's strange is:

• In actual gameplay, L2 works perfectly (0%~100%)
• Only the Self Test gets stuck at L2
  

Firmware testing

Current firmware:

• Besavior controller 202504241229 firmware
  

Other firmwares I tried:

• Besavior controller 241101 beta firmware
• Besavior new firmware 202303080936 released
  

Results:

• One firmware causes L2/R2 to appear permanently pressed
• Another firmware causes L2/R2 not to respond at all
• The current firmware is the only one that mostly works, but R2 remains capped at 69%
  

Factory Reset

I have already tried:

• Factory Reset from the BK-BSV-KIT menu
  

Result:

• No change
• R2 still capped at 69%
  

Additional information

The modding service told me:

They had seen similar trigger issues a few times before.

They originally said BDM-030 boards were known to have compatibility problems, while BDM-020 boards were generally fine.

However, they were unable to explain why this particular controller behaves this way.

Questions

• Has anyone seen an R2 cap at exactly 69% on BK-BSV-KIT?
• Has anyone experienced Self Test getting stuck at the L2 step?
• Is there any hidden trigger calibration procedure for BK-BSV-KIT?
• Could this be a BDM-020 compatibility issue?
• Is there a firmware known to fix trigger calibration problems?
  

Any help would be greatly appreciated.

Thank you.

hayate188

Hi, I just installed the the DIY kit on BDM-030 using GuliKit TMR (720° Tension Adjustable) thumbsticks with 202504241229 firmware, my numbers for L2 and R2 are almost the same. Self check also get stucked on L2 press.

L2 = 0% ~ 94%
R2 = 0% ~ 59% only

aheroant3

I had the same problem. I posted a query about it, but they deleted my thread and account. I had also installed a TMR stick, and since I experienced the same symptoms, it seems this issue occurs when using either the TMR or the Hall effect sensor. It looks like I’ll have to give up one of them.

hayate188

aheroant3 replied at 2026-07-24 00:03
I had the same problem. I posted a query about it, but they deleted my thread and account. I had als ...

I don't know exactly if this is only a problem on sticks... even after replace gulikits with orignal alps i had the same issue, lucky that i had 2 DIY kits and managed to swap mainboard, after that everything worked properly, but now i have what it seems to be a defective board...