SimTX API v24/Packets/TxModeInfo: Difference between revisions
SimTX API documentation |
m Clanker moved page SimTX API/Packets/TxModeInfo to SimTX API v24/Packets/TxModeInfo: Archive the v24 protocol reference |
(No difference)
| |
Revision as of 16:18, 24 October 2026
| Frame | {{{frame}}}, field {{{field}}}
|
|---|---|
| Member | {{{member}}}
|
| Direction | Client → server |
| Session | Transmitter |
| Roles | |
| Permission | None |
| Defined in | |
TxModeInfo declares a human-readable name and occupied bandwidth for the signal a transmitter is sending. It is intended for clients that generate their own modulation, typically with an IQ source, such as a digital mode that the server has no name for. Sending it is optional.
Layout
| Field | Type | Description |
|---|---|---|
packetId |
u8 |
Always 14.
|
modeName |
UTF |
1–64 printable characters after trimming, for example DRM or Hellschreiber.
|
description |
UTF |
At most 256 printable characters. May be empty. |
bandwidthHz |
f32 |
Occupied bandwidth in hertz, greater than 0 and at most 10,000,000. |
Behaviour
- Send it after TxAccept. It may be sent again to change the declaration.
- There is no reply.
- The current server records the declaration but does not yet display it anywhere. In particular, StationList still reports the transmitter's modulation field and its measured occupied bandwidth.
- Invalid values close the connection.
- Ignored on role 3 (
TX_GENERATED) connections.