SimTX API v24/Packets/TxUpdateAck: Difference between revisions
SimTX API documentation |
m Clanker moved page SimTX API/Packets/TxUpdateAck to SimTX API v24/Packets/TxUpdateAck: Archive the v24 protocol reference |
||
(No difference)
| |||
Revision as of 16:19, 24 October 2026
| Frame | {{{frame}}}, field {{{field}}}
|
|---|---|
| Member | {{{member}}}
|
| Direction | Server → client |
| Session | Transmitter |
| Roles | |
| Permission | None |
| Answers | TxUpdate |
| Defined in | |
TxUpdateAck reports the outcome of a TxUpdate, one result per field, in the order the fields were sent.
Layout
| Field | Type | Description |
|---|---|---|
packetId |
u8 |
Always 23.
|
n |
u8 |
Number of results. |
results |
n × { u8 fieldId, bool accepted, f32 appliedValue } |
One entry per field of the update. |
Interpreting results
| Situation | accepted |
appliedValue
|
|---|---|---|
| Applied | true | The value now in effect, after any clamping or power limit. |
| Value already in effect | true | The current value. |
| Refused (out of range or too soon) | false | The current, unchanged value. |
| Not a live field | false | The requested value, echoed. |
Always update the user interface from appliedValue, not from the value that was requested. A power request of 1,500 W on an account limited to 400 W is accepted with appliedValue = 400.