CXTAIP Command — TAIP Frame Format
Adjusts three aspects of the outgoing TAIP format, to interoperate with platforms that expect variants of the protocol:
The first two parameters are available across the whole IoT line; the third (channel label) since firmware v1.09.25.
Parameters
Order (o) — position of the message number
| Value | Resulting frame |
|---|---|
| 0 (default) | >RPV...;#0A21;ID=EQUIPO1;*3F< |
| 1 | >RPV...;ID=EQUIPO1;#0A21;*7C< — the ;# after the ;ID= |
Checksum (c)
| Value | Format |
|---|---|
| 0 (default) | Standard: ;*<CS> — XOR of the frame |
| 1 | Alternative: a variant in checksum calculation and position, for platforms that expect it that way |
Channel label (l)
Adds the name of the logical queue to the message number of the frames drained from the log: ;#LOG:<nnnn>;.
| Value | Effect |
|---|---|
| 0 (default) | No label (classic behavior) |
| 1 | Label on all drained queues (#CEL:, #WIFI:, #LOG:, …) |
| 2 | Label only on the LOG queue → ;#LOG:<nnnn>; |
The label uses the logical queue, not the physical transport: a LOG queue going out over cellular emits #LOG:, not #CEL:. The number is the usual message number, 4 hexadecimal digits. For the typical case (an integration that requires ;#LOG: only on log frames) use l=2 — with 1 the main and backup queues would be labeled too.
Examples
>SCXTAIP1< // order only: ;# after the ID
>SCXTAIP012< // order 0, alternative checksum, label only on LOG
>QCXTAIP<
>RCXTAIP012<Digits 2 and 3 are optional and nested (to set the label you must also write the checksum). A digit that is not sent keeps its value; an out-of-range value is ignored and the response shows the current one. Everything persists in NVS.
LOG queue frame with o=1, l=2:
>RGP...;ID=EQUIPO1;#LOG:0A21;*4D<Compatibility
See Also
- CXDL Command - Log download engine
- DL Command - Datalog download