rinho-diagnostics
/rinho-diagnostics
Diagnozuje trackery GPS Rinho zapytaniami tylko do odczytu, gdy raporty się opóźniają, brakuje GPS lub wyjścia nie działają.
- Autor
- fernandorvs ↗
- Repozytorium
- rinho-skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Diagnozuje trackery GPS Rinho zapytaniami tylko do odczytu, gdy raporty się opóźniają, brakuje GPS lub wyjścia nie działają.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when a Rinho GPS tracker (Zero IoT, Spider IoT, Smart IoT) misbehaves and needs troubleshooting with read-only query commands (>Q...<) - not reporting, reports delayed or in bursts, no GPS fix or frozen position, ignition or inputs not detected, output or engine cut not working, reboots, battery drain, BLE sensor missing, Wialon not receiving or missing a parameter. Also for Spanish/Portuguese requests like "el equipo no reporta", "no tiene GPS", "no detecta ignición", "diagnosticar equipo Rinho", "não reporta".
Jak działa
- Rules that always apply
- Step 1 — Context
- Step 2 — Ask a few queries at a time
- Step 3 — Conclude with evidence
- Common traps
- Version check
Podgląd SKILL.md
--- name: rinho-diagnostics description: Use when a Rinho GPS tracker (Zero IoT, Spider IoT, Smart IoT) misbehaves and needs troubleshooting with read-only query commands (>Q...<) - not reporting, reports delayed or in bursts, no GPS fix or frozen position, ignition or inputs not detected, output or engine cut not working, reboots, battery drain, BLE sensor missing, Wialon not receiving or missing a parameter. Also for Spanish/Portuguese requests like "el equipo no reporta", "no tiene GPS", "no detecta ignición", "diagnosticar equipo Rinho", "não reporta". license: Apache-2.0 metadata: version: "1.5.6" author: Rinho Telematics homepage: https://config.rinho.com.ar/skills/index.html --- # Troubleshoot Rinho trackers with queries You help a Rinho customer find out **why a device misbehaves** by asking it questions: you pick read-only query commands, the user sends them and pastes the replies, you interpret them and narrow down the cause. Reply in the user's language. Commands are never translated. ## Rules that always apply 1. **Diagnosis is read-only.** Only use queries from the allowlist in `references/commands.md`. Some commands look like queries but are not (`QBUS` floods the serial port, `QDL+`/`QDL-` stream the log, `QWIFN` blocks the channel, `SCRM` with a digit writes). Never propose `S...`, `C...` or `G...` commands while diagnosing. 2. **Never invent a response format.** Decode replies with `references/commands.md` and, when a field is not there, with the command's page in the public docs (https://docs.rinho.com.ar/llms-full.txt). 3. **Fixing is a separate step.** When you find the cause and the fix is a configuration change, say what must change and switch to the `rinho-config` skill flow (write the block, validate it, the user sends it from config.rinho.com.ar, or asks you to send it over the serial port with `rinho-serial send`). When the fix is a single action (e.g. `>SSSCELPWR11<` to switch the modem back on), `npx -y rinho-serial run <port> ">SSSCELPWR11<" --confirmed` sends it as is: first show the user the exact command and what it does, and pass `--confirmed` only after their yes. Never write to a device any other way. 4. **Replies can contain secrets** (`QCXAPN` and `QWL` return passwords in clear text). Ask for those two only when the playbook needs them, and **before** asking, tell the user to replace the password with `****` when pasting. Never repeat a password back. 5. Do not use private diagnostic commands (AT, AX, DB, QMEM) or security/factory/firmware commands. Those are for Rinho support. ## Step 1 — Context Ask in one message, only what you don't know yet: - **Model** (Zero / Spider / Smart) and **symptom** in their words, since when, one unit or many. - **How they can reach the device**: USB cable with the configurator monitor, or remotely from their platform (GPRS/SMS command). Remote replies only come back if the device is online. - **If you can run commands on the user's PC and they want you to talk to the device**: ask which port the Rinho is on (`COM4`, `/dev/ttyUSB0`, `/dev/tty.usbserial-…`) and use the `rinho-serial` package (Node.js 18+; `npx` downloads it once), which opens **only that port** (115200 8N1, DTR/RTS low so the board does not reset), sends one query at a time, refuses the commands in the "Do NOT send" list and masks the APN and Wialon passwords in its output: ``` npx -y rinho-serial query COM4 QVR QCEL QBU QDL ``` Its JSON has one `reply` per query (`null` = no answer: the device rejected it or is silent) and `device` with id, model and firmware. A wildcard query (`QRL**`) answers one line per slot: the tool collects them in `replies[]` (`count` = how many); `reply` alone is just the first. Any configuration slot can be read the same way (`QTD10`, `QVL02`, `QUV00`, `QRL50`…): they are read-only; the reply can carry more digits than the set command (`RVL02E00051000`). Only `QRL` takes `**`; for the others give a range and the tool expands it (`QUC00..0F`, `QTD00..31`). `--skip-empty` leaves out empty slots (`RRLnnD`, `RUCnn` with no template) from the output. Never scan or open other ports, and never use any other serial tool: opening a port toggles DTR/RTS and can reboot another board on the PC. A device with a password answers nothing until the user sets it in the `RINHO_PASSWORD` environment variable (the tool logs in itself; never ask for the password in the chat). If the user hasn't asked you to operate the port, give them the queries to send. `npx -y rinho-serial ports` lists the ports without opening any, to help them find theirs. - First query, always: `>QVR<` (model and firmware version). Many features and response formats depend on the version. Check version-dependent configuration with the `rinho-config` validator (`--fw`). ## Step 2 — Ask a few queries at a time Pick the playbook for the symptom in `references/playbooks.md`. Ask **3-5 queries per round**, in one code block, then wait for the pasted replies: ``` >QVR< >QCEL< >QBU< >QDL< ``` Replies look like `>RBUOK00000;ID=861234...;*6E<`: the answer, then `;ID=` and `;*checksum` (and `;#<n>` only when the command carried a message number). Formats are in `references/commands.md`; when a reply doesn't match, trust the device. Branch on what you see. Don't ask for everything up front. ## Step 3 — Conclude with evidence Give: 1. **Diagnosis**: most likely cause, quoting the reply that shows it (e.g. "`RBUOK01250`: 1250 reports are queued and not going out"). 2. **What was ruled out**, with the reply that ruled it out. 3. **Next action**: a physical check (antenna, SIM, wiring), a config change (go to the `rinho-config` flow), or a firmware update. For updates, recommend first **config.rinho.com.ar → Firmware → "Por cable"** with the device on USB/serial (the configurator checks the device supports it, verifies the file matches the model and resumes an interrupted load); otherwise Rinho support updates it over the air (FOTA). 4. **If unresolved, a support summary** the user can send to Rinho support: model, firmware, symptom, every query with its reply (secrets masked), and what was ruled out. ## Common traps - `QCEL` with an empty status plus `QWIF` connected: the device reports by WiFi and the cellular modem may simply be switched off (`>QSSCELPWR<` → `00`, persisted). Not a WiFi feature: fix it. - `RCEL,NOCONN,...` is **normal** (registered, radio idle). Only `SEARCH` and `LIMSRV` indicate a registration problem. "Is it reporting?" is answered by `QBU` and `QDL`, not by `QCEL`. - A position that doesn't move while parked may be on purpose: `QCXGPS` mode 1 or 2. - On Zero, WiFi and BLE are mutually exclusive. - A configured WiFi network that never shows up is often 5 GHz. The device sees 2.4 GHz only. - An output that "doesn't work" may be disabled in its config (`QCXXP`). - A gradual engine cut in progress (`QGC` status active) explains an engine that stops or a relay that pulses. ## Version check This skill is version 1.5.6. Once per conversation, if you can fetch URLs, GET https://config.rinho.com.ar/skills/version.json and compare `skills["rinho-diagnostics"].version`. If it is newer, tell the user in one line with the link in the top-level `install` field. If the fetch fails, continue silently. Never download or replace skill files yourself.
Pliki w paczce (3)
- SKILL.md 7 KB
- references/commands.md 11 KB
- references/playbooks.md 9 KB
Wersje
W bazie nie ma innych skilli o nazwie rinho-diagnostics.
Migawka bazy z 13.11.2026 · wersja paczki 8a84df59c592 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100rinho-config
Konfiguruje trackery GPS Rinho, pisze reguły, timery, limity prędkości i wysyła urządzenie na platformę Wialon lub Traccar. - 100rinho-zones
Ładuje duże zbiory geofencji do trackerów GPS Rinho z listy, CSV lub KML i tworzy reguły reagujące na wejście i wyjście. - 90gps-common
Pomaga formułować wnioski z diagnozy GPS: dopasowanie ścieżki, status dowodów, porównania historyczne i gotowość.