AB9 Active Shifter / AS23 runtime force-profile control via MOZA SDK?
K
Kensuke Sasaki
创建话题
14分钟 以前
Hello MOZA Developer Support,
I am working on a third-party integration for the MOZA AB9 Base with the MOZA Active Shifter.
I have already checked the MOZA SDK ZIP, including `docsEng`, headers, and examples. I found APIs for SDK initialization, wheelbase force-feedback effects, generic motor settings, HID helpers, shifter gear reading, shifter auto-blip, calibration, and device enumeration.
However, I could not find an explicit public API for AB9 Active Shifter runtime force-profile control, such as:
- shift resistance
- damping
- vibration
- deadband
- virtual H-gate / detent / wall-force behavior
- rail-capture or gear-pocket force behavior
During static, read-only inspection of the installed Pit House files, I found `as23_parameter.db`. A read-only SQLite mapping shows structured parameter/operator rows such as:
- `UsbHidAxis_SerialCmd_*`
- `HidReportDescriptorMode`
- `UsbMode`
- `SpringTorqueNolineardeadband_*`
- `Steer_GameForceFeedbackCoefficient`
- `Steer_SpringCoefficient`
- `Steer_TorqueMax`
- `SteerForceSensing*`
The `UsbHidAxis_SerialCmd_*` rows appear to have read/write pairs and command/operator-like mappings. `HidReportDescriptorMode` and `UsbMode` also appear as read/write mode parameters.
My questions are:
1. Are these AS23 parameters part of an official or supported API surface for AB9 Base + Active Shifter?
2. Does the public MOZA SDK support reading or writing these parameters?
3. If yes, which SDK API should be used?
4. If not public, is there a developer, beta, NDA, or partner SDK that exposes AB9 Active Shifter runtime force/profile control?
5. Are `UsbHidAxis_SerialCmd_*`, `HidReportDescriptorMode`, and `UsbMode` intended for third-party use, or are they Pit House internal-only?
6. Can third-party software create Pit House-like virtual H-gate / detent / wall-force behavior through an official API?
I am not asking for reverse-engineering guidance. I am trying to confirm whether there is an official supported path before attempting any device-level access.
Kensuke Sasaki
Hello MOZA Developer Support,
I am working on a third-party integration for the MOZA AB9 Base with the MOZA Active Shifter.
I have already checked the MOZA SDK ZIP, including `docsEng`, headers, and examples. I found APIs for SDK initialization, wheelbase force-feedback effects, generic motor settings, HID helpers, shifter gear reading, shifter auto-blip, calibration, and device enumeration.
However, I could not find an explicit public API for AB9 Active Shifter runtime force-profile control, such as:
- shift resistance
- damping
- vibration
- deadband
- virtual H-gate / detent / wall-force behavior
- rail-capture or gear-pocket force behavior
During static, read-only inspection of the installed Pit House files, I found `as23_parameter.db`. A read-only SQLite mapping shows structured parameter/operator rows such as:
- `UsbHidAxis_SerialCmd_*`
- `HidReportDescriptorMode`
- `UsbMode`
- `SpringTorqueNolineardeadband_*`
- `Steer_GameForceFeedbackCoefficient`
- `Steer_SpringCoefficient`
- `Steer_TorqueMax`
- `SteerForceSensing*`
The `UsbHidAxis_SerialCmd_*` rows appear to have read/write pairs and command/operator-like mappings. `HidReportDescriptorMode` and `UsbMode` also appear as read/write mode parameters.
My questions are:
1. Are these AS23 parameters part of an official or supported API surface for AB9 Base + Active Shifter?
2. Does the public MOZA SDK support reading or writing these parameters?
3. If yes, which SDK API should be used?
4. If not public, is there a developer, beta, NDA, or partner SDK that exposes AB9 Active Shifter runtime force/profile control?
5. Are `UsbHidAxis_SerialCmd_*`, `HidReportDescriptorMode`, and `UsbMode` intended for third-party use, or are they Pit House internal-only?
6. Can third-party software create Pit House-like virtual H-gate / detent / wall-force behavior through an official API?
I am not asking for reverse-engineering guidance. I am trying to confirm whether there is an official supported path before attempting any device-level access.
Thank you.