IC Command
The IC command (Identification Code) enables driver session management through identification codes, tracking who operates the vehicle, for how long, and what distance they cover.
What is it for?
- 👤 Identify drivers via iButton, RF433 or Bluetooth
- ⏱️ Control work shifts with work/rest time tracking
- 📊 Usage statistics (duration, distance, idle time)
- 🔐 Vehicle access control with authorized codes
- 📱 Operation modes for different work types
Syntax
| Operation | Command | Description |
|---|---|---|
| Start session | SICcode,mode | Opens session with code and mode |
| Change mode | SIC,mode | Changes active session mode |
| Close session | SIC* | Ends current session |
| Query | QIC | Gets active session data |
QIC Response
RIC code,mode,datetime,duration,idle,movement,distance,slot| Field | Format | Description |
|---|---|---|
code | 16 chars | Driver identifier |
mode | 1 char | Identification source (N=iButton/OneWire, R=RF433) |
datetime | DDMMYYHHMMSS | Concatenated session start date and time (12 digits) |
duration | 8 digits | Total session time in seconds |
idle | 8 digits | Time with IGN OFF in seconds |
movement | 8 digits | Time with IGN ON in seconds |
distance | 10 digits | Distance traveled in meters |
slot | 4 digits | ICL slot (0000-0099) that opened the session |
IC Signals (Triggers)
| Signal | Event | Description |
|---|---|---|
IC00+ | Session started | New session opened |
IC01+ | Mode change | Session mode modified |
IC02+ | Valid user | Code found in ICL list |
IC03+ | Invalid user | Code NOT authorized |
IC signals do not support negative edges or conditional use in TRG.
Basic Examples
Start session with iButton
>SICAA01234567890123,0<
// Response: RIC AA01234567890123,N,291224143022,00000000,00000000,00000000,0000000000,0003Query active session
>QIC<
// Response: RIC AA01234567890123,N,291224143022,00003600,00001200,00002400,0000045000,0003Interpretation:
| Field | Value | Meaning |
|---|---|---|
| Code | AA01234567890123 | Driver ID |
| Mode | N | Source: iButton / OneWire |
| Start | 291224143022 | 29/12/2024 14:30:22 (concatenated datetime) |
| Duration | 00003600 | 3600 s = 1 hour total |
| Idle | 00001200 | 1200 s = 20 min engine off |
| Movement | 00002400 | 2400 s = 40 min running |
| Distance | 0000045000 | 45000 m = 45 km traveled |
| Slot | 0003 | ICL slot that opened the session |
Close session
>SIC*< // Ends session and saves statisticsChange mode during session
>SIC,1< // Changes to mode 1 while maintaining sessionAuthorized Code Management (ICL)
To manage the authorized code list, use the ICL Command:
>SICL00 AA01234567890123< // Load code at position 00
>QICL00< // Query code
>SICL00*< // Delete codeICL slot in the response (v1.09.23)
From firmware v1.09.23, the RIC response appends at the end the ICL list slot that opened the session, formatted as 4 digits (0000-0099). The field is additive: it appears after the distance.
>QIC<
>RIC AA01234567890123,N,291224143022,00003600,00001200,00002400,0000045000,0003<
// ...,distance=0000045000, ICL slot=0003Applies to QIC, SIC and SIC* responses.
With no active session, RIC comes back bare (no fields, no slot):
>QIC<
>RIC<Limitations
| Parameter | Value |
|---|---|
| Simultaneous sessions | 1 |
| Storable codes (ICL) | 100 (00-99) |
| Code length | 16 characters |
| Persistence | ⚠️ Volatile (lost on restart) |
Sessions are lost on device restart. To maintain records, send periodic reports with QIC or when closing sessions.
Compatibility
💾Firmware v1.03.00
SPLegacy
iButton, Manual
💾Firmware v1.00.00
SP-IOT
SM-IOT
ZE-IOT
Spider IoT:iButton, RF433, BTH, Manual. ICL slot in RIC from v1.09.23
Smart IoT:iButton, BTH, Manual. ICL slot in RIC from v1.09.23
Zero IoT:Manual. ICL slot in RIC from v1.09.23
See Also
- ICL Command - Authorized code management
- OW Command - iButton reading
- CXRF Command - RF433 configuration
- CXBTH Command - Bluetooth configuration
Last updated