VRE Command — Extended Version

Query detailed and extended information about the firmware, including specific versions of each internal module.

What is it for?

The VRE command provides additional information that VR doesn’t show:

📡 Modem version — Specific firmware of the cellular module
🛰️ GPS version — GNSS module firmware
📶 Bluetooth version — If the device has BLE
✅ Integrity — Firmware CRC verification
🔧 Firmware type — Application and bootloader

Ideal for advanced diagnostics and validation of complete FOTA updates.

Syntax

Action	Command	Response
Query	`QVRE`	`RVRE extended_info`

Practical Examples

Extended query on Spider IOT


>QVRE<
>RVRE SPIDER IOT v2.05.03 BG96_R02A07 L76K_v3.1 BLE5.0 FW:APP+BOOT CRC:OK;ID=123456;*2A<

VR vs VRE comparison


// VR command (basic) - general information
>QVR<
>RVR RINHO SPIDER IOT v2.05.03 u1024 BG96 L76K 2024-03-15;ID=123456;*1A<
 
// VRE command (extended) - module details
>QVRE<
>RVRE SPIDER IOT v2.05.03 BG96_R02A07 L76K_v3.1 BLE5.0 FW:APP+BOOT CRC:OK;ID=123456;*2A<

Response Fields

Field	Description	Example
Modem version	Cellular module firmware	`BG96_R02A07`
GPS version	GNSS module firmware	`L76K_v3.1`
BLE version	Bluetooth Low Energy	`BLE5.0`
FW type	Application and bootloader	`APP+BOOT`
Integrity	CRC verification	`CRC:OK`

If CRC:FAIL appears in the response, the firmware may be corrupted. Consider performing a FOTA update.

Use Cases

🔬 Advanced diagnostics — Verify internal component versions
🐛 Troubleshooting — Identify incompatibilities between modules
✅ FOTA validation — Confirm complete update of all components
📞 Technical support — Detailed information for complex cases

Compatibility

💾Firmware v1.03.00

SPLegacy

ULLegacy

MTLegacy

💾Firmware v1.00.00

SP-IOT

SM-IOT

ZE-IOT