Skip to Content
GuidesGetting Started

🚀 Getting Started

Quick guide to configure your Rinho IoT device and start receiving position data.


📋 Requirements

  • 📦 Rinho device (Spider IoT, Smart IoT or Zero IoT)
  • 🔌 USB cable (Spider/Zero: direct, Smart: USB-TTL adapter)
  • 💻 Serial terminal or Web Serial
  • 📱 SIM chip with active data plan
  • 🌐 Server to receive reports (public IP or domain)

🔌 Device Connection

Connect the USB cable

DeviceConnection
Spider IoTDirect USB (internal converter)
Zero IoTDirect USB (internal converter)
Smart IoTRequires USB-TTL adapter

Open serial terminal

Configure your terminal with:

  • Baudrate: 115200
  • Data bits: 8
  • Stop bits: 1
  • Parity: None

You can use Web Serial from the browser or any serial terminal (PuTTY, Termite, etc.)

Verify communication

Send the version command:

>QVR<

Expected response:

>RVR RINHO IOT v1.09.16 SP EG915U LC86G 16MB WIFI 2025-12-12 14:52:18;ID=865413053386354;*37<

If you receive a response, communication is working.


⚙️ Basic Configuration

Configure cellular operator (COPS)

Set the network operator manually:

>SCOPS4,2,"72234"<

The code 722 is Argentina, 34 is Personal. Check MCC/MNC codes  for other operators.

Common operators Argentina:

OperatorCode
Personal72234
Claro722310
Movistar72207

Configure APN

Set your operator’s access point name:

>SCXAPNm2m.personal.com,,<

Common APNs Argentina:

OperatorAPN
Personalm2m.personal.com
Clarointernet.ctimovil.com.ar
Movistarm2m.movistar.com.ar

Verify cellular connection

>QCEL<

Response:

>RCEL,NOCONN,LTE,722,34;ID=...
StatusMeaning
NOCONNRegistered on network, not connected to server
CONNConnected to server
LTENetwork type (can be GSM, 3G, LTE)

Configure destination server

Set the IP or domain where the device will send reports:

Using IP:

>SIP0064.120.108.024/22496< >SIP1064.120.108.024/22496<

Using domain:

>SIP0"server.example.com",4031< >SIP1"server.example.com",4031<

IP0 is the primary server, IP1 is the secondary (backup). It’s recommended to configure both.


⏱️ Configure Periodic Reports

For the device to send position automatically, you need to configure a timer and a rule.

Create 60-second timer

>STD00E00060<

This creates timer TD00 enabled (E = Enable) that triggers every 60 seconds.

Create report rule

>SRL00E;TRG=TD00+;ACC={GCQ00H}<

This rule says: “When timer TD00 expires (TRG=TD00+), generate and send a position report (GCQ00H)”

If you want the rule to only execute with ignition on, add the condition CND=IGN:

>SRL00E;TRG=TD00+;CND=IGN;ACC={GCQ00H}<

With this configuration, the device will send its position every 60 seconds.


✅ Verify Operation

🔧 Check I/O status

>QIO<

Response:

>RIO;IGN1;IN1111111;XP000;V125;VBU425;ID=...
FieldExampleMeaning
IGN1Ignition on
IN1111111Digital inputs status
V125Main voltage: 12.5V
VBU425Backup battery: 4.25V

📍 Check current position

>QCQ<

Response:

>RCQ00311225191529-2778104-06425850000348FF00125000000A3030105FFFF1123;ID=...

🛰️ Check GPS status

>QSSGPS<

Response:

>RSSGPS11;ID=...
ValueMeaning
00No GPS position
11Valid GPS position

If SSGPS returns 00, the device doesn’t have a valid GPS position. Make sure the antenna is connected and has sky view.

This value doesn’t indicate signal quality or satellite count, only whether it has position or not.


🐛 Enable Debug Mode

To see in real time what the device is doing:

>SDB1<

You’ll see the sent reports and server confirmations:

[CEL] TX MAIN -> >RCQ00311225191529-2778104-0642585... [CEL] RX MAIN <- >ACK;#05E4;ID=865413053386354;*35<

To disable:

>SDB0<

📖 Command Summary

CommandFunctionReference
>QVR<Check firmware versionVR
>SCOPS...Configure operatorCOPS
>SCXAPN...Configure APNCXAPN
>SIP0...Configure primary serverIP
>SIP1...Configure secondary serverIP
>STD00E00060<60-second timer enabledTD
>SRL00E;TRG=TD00+;ACC={GCQ00H}<Periodic report ruleRL
>QIO<Input/output statusIO
>QCEL<Cellular connection statusCEL
>QCQ<Current positionCQ Report
>QSSGPS<GPS statusSS
>SDB1<Enable debugDB

🎯 Next Steps

Last updated