SN Command — Serial Number
Query the device’s electronic serial number (SN), assigned during manufacturing for hardware traceability.
What is it for?
The SN command allows you to obtain the manufacturing identifier for:
- 📋 Warranty management — Equipment registration and validation
- 🔍 Traceability — Tracking from manufacturing
- ✅ Validation — Verify original Rinho products
- 🔧 Technical support — Identification in RMA tickets
- 📊 Inventory — Hardware control
The SN is unique for each device and does not change even if the cellular module is replaced.
Syntax
| Action | Command | Response |
|---|---|---|
| Query | QSN | RSN xxx...xxx (24 hex characters) |
Practical Examples
Basic query
>QSN<
>RSN3459343937350604000B006B;ID=974862;*6D< // SN: 3459343937350604000B006BSN breakdown
| Section | Bytes | Description |
|---|---|---|
| Prefix | 34593439 | Production identifier |
| Batch | 37350604 | Manufacturing date/batch |
| Sequential | 000B006B | Unique sequential number |
SN by Model
Rinho Spider IOT
>QSN<
>RSN5350494445523031323334;ID=123456;*1A< // "SPIDER012344" in ASCIIRinho Smart IOT
>QSN<
>RSN534D415254303030313233;ID=654321;*2B< // "SMART000123" in ASCIIRinho C5
>QSN<
>RSN4335303032303135303630;ID=974862;*3C< // "C5002015060" in ASCIISN vs IMEI — Differences
| Characteristic | SN (Serial Number) | IMEI |
|---|---|---|
| Identifies | Device hardware | Cellular module |
| Format | Hexadecimal (24 chars) | Decimal (15 digits) |
| Assigned by | Rinho manufacturer | Modem manufacturer |
| Main use | Traceability, warranties | Mobile operators |
| Changes if… | Never | Modem is replaced |
| Command | QSN | QIMEI |
After replacing a cellular module, the SN remains the same but the IMEI changes.
Hex to ASCII Conversion
Some SNs represent readable text:
# Python
sn_hex = "5350494445523031323334"
sn_ascii = bytes.fromhex(sn_hex).decode('ascii')
print(sn_ascii) # "SPIDER012344"# PowerShell
$sn = "5350494445523031323334"
$bytes = [byte[]]::new($sn.Length / 2)
for ($i = 0; $i -lt $sn.Length; $i += 2) {
$bytes[$i/2] = [Convert]::ToByte($sn.Substring($i, 2), 16)
}
[System.Text.Encoding]::ASCII.GetString($bytes) # "SPIDER012344"Use Cases
Technical support registration
// 1. Query SN
>QSN<
>RSN3459343937350604000B006B;ID=974862;*6D<
// 2. Query IMEI
>QIMEI<
>RIMEI865851037974862;ID=974862;*4D<
// Data for ticket:
// - SN: 3459343937350604000B006B
// - IMEI: 865851037974862Verify modem replacement
// Before replacement
>QSN<
>RSN3459343937350604000B006B;ID=974862;*6D< // Same SN ✓
>QIMEI<
>RIMEI865851037974862;ID=974862;*4D< // Old IMEI
// After replacement
>QSN<
>RSN3459343937350604000B006B;ID=974862;*6D< // Same SN ✓
>QIMEI<
>RIMEI865851038012345;ID=974862;*5A< // New IMEI ✓Compatibility
| Model | Minimum Version |
|---|---|
| Rinho Spider | v1.03.00 |
| Rinho Ultralite | v1.03.00 |
| Rinho Minitrack | v1.03.00 |
| Rinho C3 | v1.03.00 |
| Rinho C5 | v1.03.00 |
| Rinho Spider IOT | v1.00.00 |
| Rinho Smart IOT | v1.00.00 |
| Rinho Zero IOT | v1.00.00 |
See Also
- IMEI Query - Modem IMEI
- Configure ID - Equipment identifier
- VR Command - Firmware version
Last updated