IP Command — Communication Destinations
Configures IP addresses and destination ports for report sending.
What is it for?
🌐 Main use cases:
- 📡 Configure main and redundant tracking servers
- 📶 Define specific destinations for WiFi
- 🔄 Implement backup channel for simultaneous sending
- 🌍 Use DNS domains instead of fixed IPs
- ⬇️ Configure FOTA server for updates
IP Destinations Architecture
Rinho IoT devices support multiple IP destinations organized in two independent communication channels:
MAIN Channel (Primary)
The primary channel for regular reports.
| IP | Function | Medium |
|---|---|---|
| IP0 | 🟢 Primary server | Cellular (and WiFi if IP3 is not defined) |
| IP1 | 🔄 Redundant server | Cellular (and WiFi if IP3 is not defined) |
| IP3 | 📶 WiFi exclusive server | WiFi only (since v1.7.04) |
Behavior: The device tries IP0, if it fails goes to IP1. If IP3 is defined, WiFi uses exclusively IP3.
BACK Channel (Secondary/Simultaneous)
Additional channel for simultaneous sending to a secondary server (since v1.9.15).
| IP | Function | Medium |
|---|---|---|
| IP4 | 🟢 Primary backup server | Cellular (and WiFi if IP6 is not defined) |
| IP5 | 🔄 Redundant backup server | Cellular (and WiFi if IP6 is not defined) |
| IP6 | 📶 WiFi backup server | WiFi only |
Reserved IP
| IP | Function |
|---|---|
| IP2 | ⬇️ Reserved for FOTA (firmware update) |
Commands
| Operation | Syntax |
|---|---|
| Configure IP | SIPabbb.ccc.ddd.eee/ffff |
| Configure DNS | SIPa"domain",ffff |
| Query | QIPa |
Parameters
| Parameter | Description | Values |
|---|---|---|
a | Destination IP index | 0-6 (see architecture above) |
bbb.ccc.ddd.eee | Destination IP address | IPv4 format |
ffff | Port number | 1-65535 |
"domain" | DNS name | Within quotes |
Configuration Examples
Basic configuration (MAIN only)
>SIP0190.168.1.100/5000< // Primary IP
>SIP1190.168.1.101/5000< // Redundant IPWith DNS domain
>SIP0"tracking.mycompany.com",5000<Configuration with exclusive WiFi
>SIP0190.168.1.100/5000< // MAIN via cellular
>SIP1190.168.1.101/5000< // MAIN redundant cellular
>SIP3192.168.0.50/5000< // MAIN exclusive WiFiBasic configuration (MAIN only)
>SIP0190.168.1.100/5000< // Primary IP
>SIP1190.168.1.101/5000< // Redundant IPWith DNS domain
>SIP0"tracking.mycompany.com",5000< // Resolves DNS automaticallyConfiguration with exclusive WiFi
>SIP0190.168.1.100/5000< // MAIN via cellular
>SIP1190.168.1.101/5000< // MAIN redundant cellular
>SIP3192.168.0.50/5000< // MAIN exclusive WiFi (priority when WiFi available)Complete MAIN + BACK configuration
// MAIN Channel (primary tracking)
>SIP0"main.server.com",5000< // Primary
>SIP1"main-backup.server.com",5000< // Redundant
// BACK Channel (simultaneous sending to secondary server)
>SIP4"back.server.com",8000< // Primary backup
>SIP5"back-backup.server.com",8000< // Redundant backupDestinations in G Command
When generating reports with the G Command, specify the destination:
| Destination | Description | IPs used |
|---|---|---|
@GPRS | MAIN channel via cellular | IP0/IP1 |
@WIF | MAIN channel via WiFi | IP3 (or IP0/IP1 if not defined) |
@BACK | Intelligent BACK channel | IP4/IP5 + WiFi |
@BGP | BACK channel cellular only | IP4/IP5 |
@BWI | BACK channel WiFi only | IP6 (or IP4/IP5 if not defined) |
IP2 is reserved exclusively for FOTA (remote firmware update).
Compatibility
💾Firmware:v1.00.00
SPLegacy
ULLegacy
MTLegacy
C3Legacy
C5Legacy
SP-IOT
SM-IOT
ZE-IOT
See Also
- GPRSH Command - Forced socket disconnection
- COPS Command - Carrier selection
- CXAPN Command - APN configuration
Last updated