Request: for Magnometter, need separe 2 psmove with same PID
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 528
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
so, issue is for psmove ps4 without magnometter, is Model_ZCM1U for me, same VID/PID, just get difference reference with 460 and no 400 for real PS3 psmove with Magnometer.
Here is probleme because it not have magnometter but psmoveapi think it have that, and that causing probleme for all, no can works correctly, on psmove test ogl, i get coàntroll return alone in center possition after it rotate etc, ps3 psmove no have this, because it have magnometter.
So, need add one thinke likefor Model_ZCM2, for can use it normally without magnometter.
I have see on psmove service, it said megnometter is disable, and not get same issue return center axis alone in rotate.
See on things, if i delete magnetometer file "XX_XX_XX_XX.magnetometer.csv" that ffix this issue
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior in psmove test ogl and compare the Model_ZCM1U and Model_ZCM2 handling. Check how psmove service detects or disables the magnetometer and how the VID/PID plus reference values 460 and 400 are used. Done means the non-magnetometer PS4 device no longer recenters its axis after rotation while the PS3 device keeps magnetometer behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100