Rinho Firmware 1.09.24: what's new for integrators
🎯 Who this article is for: integrators, developers and companies that build their own telemetry platform on top of Rinho hardware ("Rinho Inside"). If you operate your own backend, this update is for you.
Version 1.09.24 of the Rinho firmware is, above all, a release for those who integrate. It consolidates the work of several versions (1.09.17 to 1.09.24) with a clear focus: more remote control, less dependency on the field service visit and more autonomy for your platform.
These are the highest-impact new features when the hardware is yours and the software is too.
📋 TL;DR - The 6 that matter most
| Feature | Why it matters to you as an integrator |
|---|---|
| DFOTA | Update the modem firmware without going to the vehicle |
| Robust cellular registration | The device joins the network on any operator, no tuning |
| LIFO/FIFO engine | Choose the ingestion order: freshness or chronological |
| Fine-grained QCEL | Remote coverage diagnostics from your backend |
| Wialon IPS 1.0 | Direct connection to your own platform |
| Binary reports B3/B9 | Up to 70% less traffic at fleet scale |
1. DFOTA — update the modem without a field service visit
Until now, a problem in the cellular modem firmware could mean sending someone out to touch the device. With DFOTA (SCFW / QCFW commands) you now update the firmware of the modem itself remotely, with a delta package and a battery safety net that prevents leaving the device half-done.
For an integrator managing devices scattered across several provinces or countries, this is straightforward: fewer visits, less downtime, hot fixes without disassembling anything.
📖 DFOTA command documentation (CFW)
2. Robust cellular registration, no configuration
The new network registration manager (SCOP / SCRM) brings the device onto the network with no manual per-operator tuning. It applies an automatic ladder (COPS/CEREG) and, if needed, falls back to 2G as a last resort for hard-coverage areas. And if you ever want to return to the previous behavior, SCRM0 disables it by SMS, without OTA.
Translation for whoever provisions fleets: less onboarding friction and a device that registers evenly across different LATAM countries without a custom config per SIM.
📖 Network registration documentation (SCOP / SCRM)
3. LIFO/FIFO download engine — you choose the ingestion order
The device's internal datalog is now downloaded with configurable order (SCXDL, Order field):
- FIFO (default): events in chronological order. Ideal for auditing and forensics.
- LIFO: the most recent events first. After a coverage gap, your platform sees the current status of the vehicle instantly and backfills the history in the background — instead of waiting for the entire old queue to drain.
Also, QCXDLST gives you runtime visibility of the download engine, to monitor ingestion from your own backend. It's fine-grained control over how data arrives, which is exactly what an integrator needs for a solid live experience.
4. QCEL — remote coverage diagnostics
QCEL went from returning 4 data points to exposing up to 17 fields of cellular diagnostics: technology, band, RSRP / RSRQ / SINR (real LTE signal quality) and LAC + Cell ID (cell-based location).
This gives your platform two valuable things: remote connectivity debugging (see why a device reports poorly, without external instrumentation) and an approximate cell-based geolocation as a fallback when there's no GPS fix.
5. Wialon IPS 1.0 + sending to your server
The device supports full Wialon IPS 1.0 (SWL / QWL / QWD): login, data, short messages, bulk and ping. Combined with sending via TAIP to your own server, Rinho hardware connects directly to your backend — with no mandatory intermediate platform.
That's the essence of "Rinho Inside": you provide the software and the business logic; the device measures and transmits in the protocol you already speak.
📖 Wialon IPS documentation (WL)
6. Binary reports B3/B9 — up to 70% less traffic
The new TAU binary reports B3 (47 bytes) and B9 (89 bytes) pack the same information into a fraction of the size of a text report — up to 70% less traffic. The B9 includes accelerometer (XYZ) and a trail of 10 GPS positions.
At fleet scale, that's direct savings on your data plan and more events per byte for your ingestion.
📖 Binary reports documentation
And also
1.09.24 brings more improvements that add up to the operation:
- Fail-safe update (anti-brick rollback): if an update leaves the device unstable, it reverts on its own to the previous version.
- Complete trip send to a destination (
STP,SEND): synthesizes and sends the entire trip —summary, histograms, score and globals— wherever you want. - ToF distance sensor (MOKO S02R) via BLE.
- QMEM: device memory diagnostics, useful for remote support.
- WiFi Free Scanner: automatic connection to the best available open network.
- New EVAL variables
HDG(heading) andALT(altitude) for custom reports.
📖 Full changelog in the documentation
In summary
If you build on Rinho hardware, 1.09.24 gives you more remote levers and fewer reasons to touch the device in the field: you update the modem without a visit, the device registers on its own, you choose how the data arrives, you diagnose coverage remotely and you connect directly to your platform with less traffic.
Want to evaluate Rinho as a hardware base for your solution? Tell us about your case and we'll put together the integration.
Related articles
Send GPS Data to Your Own Server: TAIP & Wialon IPS Guide
Make your GPS tracker report to your own server: TAIP vs Wialon IPS, device setup, a sample UDP receiver and real frame parsing. Read the complete guide.
J1939 GPS Tracking: What Engine Data You Can Read
Which engine parameters a GPS tracker can read over J1939 on heavy trucks —RPM, fuel, hours, odometer— and how to capture custom signals with CXECU.
Best GPS Trackers for Mining in LATAM (2026)
Technical guide to choosing a GPS tracker for mining operations in LATAM: why Starlink demands native WiFi, vendor comparison, and product mapping by use case.