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

Im not sure what the problem is. I just installed new tmr sticks and everything is fine, however when i try to calibrate the controller I get this error message. #66

New Issue
Open
opened 2026-02-10 18:44:59 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-10 18:44:59 +03:00
Owner
Copy Link

Originally created by @hassan706 on GitHub (Dec 1, 2025).

Image
Originally created by @hassan706 on GitHub (Dec 1, 2025). <img width="1136" height="760" alt="Image" src="https://github.com/user-attachments/assets/2af1760c-a9f4-4b22-8b2d-4b0f52fe919b" />
OVERLORD commented 2026-02-10 18:45:02 +03:00
Author
Owner
Copy Link

@mathiasm74 commented on GitHub (Dec 4, 2025):

Hey! Can you please make sure you're using the latest version here https://dualshock-tools.github.io, and then show us the error details (click the "Details" text below the error message)?

@mathiasm74 commented on GitHub (Dec 4, 2025): Hey! Can you please make sure you're using the latest version here https://dualshock-tools.github.io, and then show us the error details (click the "Details" text below the error message)?
OVERLORD commented 2026-02-10 18:45:03 +03:00
Author
Owner
Copy Link

@dualshock-tools commented on GitHub (Dec 6, 2025):

@mathiasm74 Good point, @hassan706 should definitely try the latest version.

This issue has been haunting me for a long time. I think it should be fixed in the latest version, but not having a JDM-040 makes it hard for me to debug. In my opinion there are two possible causes:

  • The firmware on JDM-040 responds to 0x91 and 0x92 differently than other firmwares.
  • The firmware might be slower to respond than the others. I thought this was the case and added a sleep(..) but the issue probably persists. :/
@dualshock-tools commented on GitHub (Dec 6, 2025): @mathiasm74 Good point, @hassan706 should definitely try the latest version. This issue has been haunting me for a long time. I think it should be fixed in the latest version, but not having a JDM-040 makes it hard for me to debug. In my opinion there are two possible causes: - The firmware on JDM-040 responds to 0x91 and 0x92 differently than other firmwares. - The firmware might be slower to respond than the others. I thought this was the case and added a `sleep(..)` but the issue probably persists. :/
OVERLORD commented 2026-02-10 18:45:04 +03:00
Author
Owner
Copy Link

@serdaltekdal-hub commented on GitHub (Dec 13, 2025):

Ana Hata Yığını:
Hata: Analog dönüşümü başarısız oldu. Özellik raporu alınamadı.
_.calibrateSticksBegin adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:6839)
async UR adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:61954)
async U.calibrationSteps adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:61145)
async U.next adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:60902)
async window.calib_next adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:62969 ( bu şekilde bir hata veriyor bende çözemedim)

@serdaltekdal-hub commented on GitHub (Dec 13, 2025): Ana Hata Yığını: Hata: Analog dönüşümü başarısız oldu. Özellik raporu alınamadı. _.calibrateSticksBegin adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:6839) async UR adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:61954) async U.calibrationSteps adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:61145) async U.next adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:60902) async window.calib_next adresinde (https://dualshock-tools.github.io/app-43871a0c.js:1:62969 ( bu şekilde bir hata veriyor bende çözemedim)
OVERLORD commented 2026-02-10 18:45:05 +03:00
Author
Owner
Copy Link

@leon15032012-byte commented on GitHub (Dec 21, 2025):

`

@leon15032012-byte commented on GitHub (Dec 21, 2025): `
OVERLORD commented 2026-02-10 18:45:06 +03:00
Author
Owner
Copy Link

@zyhanroxz-del commented on GitHub (Dec 29, 2025):

Image

npm run start

@zyhanroxz-del commented on GitHub (Dec 29, 2025): > <img alt="Image" width="1136" height="760" src="https://private-user-images.githubusercontent.com/109545690/520541299-2af1760c-a9f4-4b22-8b2d-4b0f52fe919b.jpg?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjY5Njk1MzgsIm5iZiI6MTc2Njk2OTIzOCwicGF0aCI6Ii8xMDk1NDU2OTAvNTIwNTQxMjk5LTJhZjE3NjBjLWE5ZjQtNGIyMi04YjJkLTRiMGY1MmZlOTE5Yi5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUxMjI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MTIyOVQwMDQ3MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04OTMwMGNkMDYxMGU4OTdlNzNiMzkwY2IwNGQ1ZGQ0MTkwMDE0NTk5ZmViMGYxOGJjNDIxNmZhY2RhMDQ5OTI1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.CHf9LC_gaDGAdqbZSZJmcsq5lgJQtkYpBTOGWGZUFKg"> npm run start
OVERLORD commented 2026-02-10 18:45:07 +03:00
Author
Owner
Copy Link

@zyhanroxz-del commented on GitHub (Dec 29, 2025):

#193 Duplicate of #148 /

@zyhanroxz-del commented on GitHub (Dec 29, 2025): #193 Duplicate of #148 /
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#66
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?