> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/device-features/ps5-adaptive-triggers.md).
# PS5 adaptive triggers
Adaptive-trigger data has 11 byte fields. Each field is `0..255`. The field selector constants identify these positions:
| Index | Selector | Field |
|---|
| 0 | PS5_ADT_MODE | Effect mode |
| 1 | PS5_ADT_START | Start position |
| 2 | PS5_ADT_FORCE1 | First force parameter |
| 3 | PS5_ADT_FORCE2 | Second force parameter |
| 4 | PS5_ADT_STRENGTH_LOW | Low-zone strength |
| 5 | PS5_ADT_STRENGTH_MID | Mid-zone strength |
| 6 | PS5_ADT_STRENGTH_HIGH | High-zone strength |
| 7 | PS5_ADT_UNK1 | Unknown/reserved byte 1 |
| 8 | PS5_ADT_UNK2 | Unknown/reserved byte 2 |
| 9 | PS5_ADT_FREQ | Effect frequency |
| 10 | PS5_ADT_UNK3 | Unknown/reserved byte 3 |
The separate mode constants, such as `PS5_ADT_CR`, are values placed in field 0; they are not field selectors.
***
### Read one field
{% code title="adt-read-field.gpc" %}
```cpp
int current_mode;
main {
current_mode = get_adt(PS5_R2, PS5_ADT_MODE);
}
```
{% endcode %}
***
### Write one field
```cpp
main {
set_adt(PS5_R2, PS5_ADT_MODE, PS5_ADT_CR);
}
```
***
### Apply an entire profile
{% code title="adt-apply-profile.gpc" %}
```cpp
const ps5adt PROFILE = {
PS5_ADT_CR, // 0: mode
0, // 1: start
128, // 2: force 1
128, // 3: force 2
64, // 4: low strength
128, // 5: mid strength
192, // 6: high strength
0, // 7: unknown/reserved 1
0, // 8: unknown/reserved 2
100, // 9: frequency
0 // 10: unknown/reserved 3
};
main {
if(get_ival(PS5_L2)) {
adt_setx(PS5_R2, addr(PROFILE));
} else {
adt_off(PS5_R2);
}
}
```
{% endcode %}
***
### Compare the current record
{% code title="adt-compare-record.gpc" %}
```cpp
const ps5adt PROFILE = {
PS5_ADT_CR, 0, 128, 128, 64, 128, 192, 0, 0, 100, 0
};
main {
if(adt_cmp(PS5_R2, addr(PROFILE))) {
set_val(TRACE_1, 1);
}
}
```
{% endcode %}
Do not invent meanings for `UNK` fields. Preserve known-good records and retest behavior after firmware changes.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://guide.cronuszen.com/gpcscripting/gpc-script-guide/device-features/ps5-adaptive-triggers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.