Calibrating locked controller into 100% #5

Closed
opened 2026-02-10 18:42:49 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @traydays on GitHub (Jul 4, 2024).

Basically, I wanted to calibrate my Dualsense, and when I finished the find midpoint steps. My controller has now been locked into a 100% state, only Diagonal corners. I hit reset on the web, and it didn't help. This is a brand-new controller, BDM-040(CFIZCT1B) - firmware 0458 that's been used less than a month. Just wanted to test seeing if I can get Err % down. But, unfortunately, I've encountered the reverse.
I only used the GUI of the website to calibrate alongside gamepad-tester when this happened. Here's an image of the 100% in diagonal directions, only the corners I'm able to move and when I press a direction, it holds it.
Seeing that, it is likely to brick a controller if one was using the DS4-tool python. But, possible through the GUI as well? I only did midpoint steps when this happened after finishing. Any fix, or lost cause?
2024-07-03_19-36-26

Originally created by @traydays on GitHub (Jul 4, 2024). Basically, I wanted to calibrate my Dualsense, and when I finished the find midpoint steps. My controller has now been locked into a 100% state, only Diagonal corners. I hit reset on the web, and it didn't help. This is a brand-new controller, BDM-040(CFIZCT1B) - firmware 0458 that's been used less than a month. Just wanted to test seeing if I can get Err % down. But, unfortunately, I've encountered the reverse. I only used the GUI of the website to calibrate alongside gamepad-tester when this happened. Here's an image of the 100% in diagonal directions, only the corners I'm able to move and when I press a direction, it holds it. Seeing that, it is likely to brick a controller if one was using the DS4-tool python. But, possible through the GUI as well? I only did midpoint steps when this happened after finishing. Any fix, or lost cause? ![2024-07-03_19-36-26](https://github.com/dualshock-tools/dualshock-tools.github.io/assets/38870234/b9e724f5-d540-4208-bb7b-f894150a0e7a)
Author
Owner

@traydays commented on GitHub (Jul 4, 2024):

Something must have been wrong with my Chromium Browser. I switched to another browser, Chrome, and were able to calibrate the stick range permanent. I was able to do the test without it auto-completing the test.

@traydays commented on GitHub (Jul 4, 2024): Something must have been wrong with my Chromium Browser. I switched to another browser, Chrome, and were able to calibrate the stick range permanent. I was able to do the test without it auto-completing the test.
Author
Owner

@kantr1ej commented on GitHub (Jul 5, 2024):

I am also having this issue even using chrome

@kantr1ej commented on GitHub (Jul 5, 2024): I am also having this issue even using chrome
Author
Owner

@dualshock-tools commented on GitHub (Aug 13, 2024):

Hi, do again the range calibration following the instructions (aka click on the button, slowly rotate the sticks and click continue when done). If the window opens and closes instantly, there are issues with your browser. Clear the caches, try in incognito or change browser.

@dualshock-tools commented on GitHub (Aug 13, 2024): Hi, do again the range calibration following the instructions (aka click on the button, slowly rotate the sticks and click continue when done). If the window opens and closes instantly, there are issues with your browser. Clear the caches, try in incognito or change browser.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dualshock-tools/dualshock-tools.github.io#5