dualshock-tools/dualshock-tools.github.io
1
0
Fork 0
mirror of https://github.com/dualshock-tools/dualshock-tools.github.io.git synced 2026-03-01 11:19:54 +03:00
Code Issues 9 Packages Projects Releases Wiki Activity

Improvements proposal #1

New Issue
Closed
opened 2026-02-10 18:42:31 +03:00 by OVERLORD · 9 comments
OVERLORD commented 2026-02-10 18:42:31 +03:00
Owner
Copy Link

Originally created by @crozac on GitHub (Apr 18, 2024).

Proposals for improvement:

  • when connected read mac and lock status automatically
  • add battery percentage with indicator e.g.: going up (charging) or going down (discharging)
  • add button status, e.g. when you calibrate game pad you need to check what is the result and you need to use e.g Gamepad tester web page
  • add indicators of 100% for analog sticks, e.g. for up, down, left, right and L2/R2 buttons. sometimes after calibration you cannot reach 100% in all directions, and you cannot reach L2/R2 max value
  • add pre and post calibration results e.g. as on gamepad tester web page: one color for pre and different one for post calibration. percental deviation is an excellent score result.
Originally created by @crozac on GitHub (Apr 18, 2024). Proposals for improvement: - when connected read mac and lock status automatically - add battery percentage with indicator e.g.: going up (charging) or going down (discharging) - add button status, e.g. when you calibrate game pad you need to check what is the result and you need to use e.g Gamepad tester web page - add indicators of 100% for analog sticks, e.g. for up, down, left, right and L2/R2 buttons. sometimes after calibration you cannot reach 100% in all directions, and you cannot reach L2/R2 max value - add pre and post calibration results e.g. as on gamepad tester web page: one color for pre and different one for post calibration. percental deviation is an excellent score result.
OVERLORD commented 2026-02-10 18:42:39 +03:00
Author
Owner
Copy Link

@dotdissent commented on GitHub (Apr 21, 2024):

Additional test proposal, the ability to set the trigger motors on a DualSense for motor testing. I've had a few come through with cracked/slipping gears that I only caught because I used the motor test in DualSenseX.

@dotdissent commented on GitHub (Apr 21, 2024): Additional test proposal, the ability to set the trigger motors on a DualSense for motor testing. I've had a few come through with cracked/slipping gears that I only caught because I used the motor test in DualSenseX.
OVERLORD commented 2026-02-10 18:42:40 +03:00
Author
Owner
Copy Link

@dualshock-tools commented on GitHub (Apr 22, 2024):

Thank you for these suggestions. Just added the first one (automatically read mac and lock status). Will add the others in future.

@dualshock-tools commented on GitHub (Apr 22, 2024): Thank you for these suggestions. Just added the first one (automatically read mac and lock status). Will add the others in future.
OVERLORD commented 2026-02-10 18:42:41 +03:00
Author
Owner
Copy Link

@JuanchoGYT commented on GitHub (May 28, 2024):

If possible, there should be a hardware deadzone adjustment tool, it will be useful for BDM-010 and BDM-020 dualsense since these are the models that i had to fix the most due to how easy it is to get stick drift on these models. I'm getting tired of having to recalibrate a lot to get it just right. Permanently writing the changes does not solve the issue, but makes it a lot easier to get the stick range an calibration just right, only to realize that a deadzone adjustment tool is actually necessary and would help combat stick drift.

@JuanchoGYT commented on GitHub (May 28, 2024): If possible, there should be a hardware deadzone adjustment tool, it will be useful for BDM-010 and BDM-020 dualsense since these are the models that i had to fix the most due to how easy it is to get stick drift on these models. I'm getting tired of having to recalibrate a lot to get it just right. Permanently writing the changes does not solve the issue, but makes it a lot easier to get the stick range an calibration just right, only to realize that a deadzone adjustment tool is actually necessary and would help combat stick drift.
OVERLORD commented 2026-02-10 18:42:42 +03:00
Author
Owner
Copy Link

@Para81szs commented on GitHub (Mar 1, 2025):

Hello, I also have a question, I have 3 joysticks and all with the BDM-020 board but the Touchpad ID says an error, I put other joysticks with a different board model BDM-010, BDM-030 etc and it doesn't show an error... what could be the problem? They work fine
https://ibb.co/xt34Q5Nb

@Para81szs commented on GitHub (Mar 1, 2025): Hello, I also have a question, I have 3 joysticks and all with the BDM-020 board but the Touchpad ID says an error, I put other joysticks with a different board model BDM-010, BDM-030 etc and it doesn't show an error... what could be the problem? They work fine https://ibb.co/xt34Q5Nb
OVERLORD commented 2026-02-10 18:42:43 +03:00
Author
Owner
Copy Link

@JuanchoGYT commented on GitHub (Mar 6, 2025):

Huh, out of all problems i had with BDM-010 and 020 models i never encountered a touchpad id issue, i suggest checking the ribbon's state to ensure the problem is no physical connections that can be the result of broken traces in the connector or the ribbon itself

@JuanchoGYT commented on GitHub (Mar 6, 2025): Huh, out of all problems i had with BDM-010 and 020 models i never encountered a touchpad id issue, i suggest checking the ribbon's state to ensure the problem is no physical connections that can be the result of broken traces in the connector or the ribbon itself
OVERLORD commented 2026-02-10 18:42:44 +03:00
Author
Owner
Copy Link

@Para81szs commented on GitHub (Mar 7, 2025):

The error persists on 4 models I tested. I would like to mention that they work normally in other tests.

@Para81szs commented on GitHub (Mar 7, 2025): The error persists on 4 models I tested. I would like to mention that they work normally in other tests.
OVERLORD commented 2026-02-10 18:42:45 +03:00
Author
Owner
Copy Link

@Para81szs commented on GitHub (Mar 7, 2025):

here I noticed that the battery doesn't look good either and is 100% regardless of whether it is discharged

@Para81szs commented on GitHub (Mar 7, 2025): here I noticed that the battery doesn't look good either and is 100% regardless of whether it is discharged
OVERLORD commented 2026-02-10 18:42:46 +03:00
Author
Owner
Copy Link

@mathiasm74 commented on GitHub (Jun 5, 2025):

Here's a PR for testing the haptic motors https://github.com/dualshock-tools/dualshock-tools.github.io/pull/90

@mathiasm74 commented on GitHub (Jun 5, 2025): Here's a PR for testing the haptic motors https://github.com/dualshock-tools/dualshock-tools.github.io/pull/90
OVERLORD commented 2026-02-10 18:42:47 +03:00
Author
Owner
Copy Link

@dualshock-tools commented on GitHub (Oct 18, 2025):

I think all of these points have been implemented, thanks a lot to @mathiasm74 !

@dualshock-tools commented on GitHub (Oct 18, 2025): I think all of these points have been implemented, thanks a lot to @mathiasm74 !
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dualshock-tools/dualshock-tools.github.io#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?