CXIP Command - TCP/UDP Communication Protocol
Configures the communication protocol (TCP/UDP) for each channel independently: main server (MAIN) and backup server (BACK).
What is it for?
| Use case | Description |
|---|---|
| 🔀 Mixed protocols | TCP for main, UDP for backup |
| ⚡ Optimization | UDP for lower latency, TCP for reliability |
| 🏢 Varied infrastructure | Adapt to different servers |
| 🔧 Flexibility | Change protocol without firmware update |
Features
- Independent protocol per channel (MAIN and BACK)
- TCP or UDP per channel
- Optional time window (1-9)
- Persistent configuration
- Backward compatible with legacy format
Commands
Configure
SCXIP[proto_main][proto_back][window]Parameters:
proto_main= P (UDP) | T (TCP) - Protocol for main serverproto_back= P (UDP) | T (TCP) - Protocol for backup serverwindow= 1-9 (optional) - Time window
Query
QCXIPResponse
RCXIP[main][back][window]0Examples
>SCXIPPP5< // UDP on both servers, time window 5
>SCXIPTT3< // TCP on both servers, time window 3
>SCXIPPT< // UDP on main, TCP on backup
>SCXIPTP< // TCP on main, UDP on backup
>SCXIPT5< // Legacy format: TCP both, window 5 (backward compatible)
>SCXIPP< // Legacy format: UDP both (backward compatible)TCP vs UDP: TCP guarantees delivery but consumes more data. UDP is faster but without delivery confirmation.
Query response
>RCXIPPP50< # UDP/UDP, window 5Compatibility
💾Firmware:v1.00.00
SPLegacy
ULLegacy
MTLegacy
C3Legacy
C5Legacy
SP-IOT
SM-IOT
ZE-IOT
Last updated