TAG Command — Configuration Tag
Allows recording a reference title to identify and document the programming assigned to the device.
What is it for?
The TAG command allows you to tag your device to:
- 🏷️ Identify fleets — Differentiate configurations by vehicle group
- 📋 Version control — Document programming changes
- 🔍 Auditing — Track specific configurations by client
- 🐛 Debugging — Quickly identify the device’s active profile
The tag is stored in non-volatile memory and persists after reboots.
Syntax
| Action | Command | Response |
|---|---|---|
| Configure | STAGetiqueta | RTAGetiqueta |
| Query | QTAG | RTAGetiqueta |
Parameter: etiqueta — Alphanumeric text up to 60 characters
Practical Examples
Configure custom title
>STAG CONFIGURACION BASICA<
>RTAG CONFIGURACION BASICA;ID=974862;*5E< // ✓ Tag savedQuery current tag
>QTAG<
>RTAG CONFIGURACION BASICA;ID=974862;*5E< // Returns current tagClient/fleet identifier
>STAG FLOTA_TRANSPORTE_001<
>RTAG FLOTA_TRANSPORTE_001;ID=974862;*3A< // ✓ Fleet identificationThe tag should not contain special characters like <, >, ; as they are protocol delimiters.
Use Cases in Rules
You can use the tag to organize your devices:
>STAG PERFIL_ECO_v2.1< // Low consumption profile
>STAG MONITOREO_24H< // Continuous tracking
>STAG CLIENTE_ABC_TAXI< // Specific configurationCompatibility
💾Firmware v1.03.00
SPLegacy
ULLegacy
MTLegacy
💾Firmware v1.00.00
SP-IOT
SM-IOT
See Also
- VR Command - Firmware version
- IMEI Query - Module identification
- SN Query - Serial number
Last updated