iButton Driver Identification: Complete Guide

An iButton is a stainless steel key with a chip that stores a unique 64-bit serial number. The driver touches it to a reader wired to the GPS tracker, and the device instantly knows who is behind the wheel. It is one of the simplest and most reliable methods for driver identification in fleets. Our iButton and 1-Wire driver identification page summarizes everything you can do with Rinho devices.

Video Tutorial

Watch our complete tutorial on iButton keys:

What is iButton?

iButton is an electronic chip encased in a button-shaped stainless steel container. The most common key for driver identification is the DS1990A (Dallas/Maxim). Its features:

• Unique ID: each key has a factory 64-bit ROM (16 hexadecimal characters) that never repeats
• Durability: stainless steel, with a service life of 10+ years
• Simplicity: touch-based identification, just press the key against the reader
• No battery: no cell to replace and no maintenance

How It Works

The Process

1. Driver touches the iButton to the reader
2. The Rinho device reads the key's unique ROM over the 1-Wire bus
3. If the code is on the authorized driver list, the device opens a driver session
4. The device reports the identification to the platform along with the position
5. The platform associates the trip with the driver

Components

• iButton keys: one per driver
• Touch reader: connects to the Rinho device with just 2 wires (signal and ground); the reader needs no power
• 1-Wire interface: the communication protocol. The same port also takes wired temperature sensors

Benefits

For Fleet Managers

Benefit	Description
Accountability	Know who drove each trip
Security	Detect unauthorized keys
Reporting	Per-driver analytics in your platform
Compliance	Record of who drove, when, and how far

For Drivers

• Simple authentication
• No PINs to remember
• Quick and easy
• Durable key fob

Installation

Reader Installation

1. Connect the reader to the Rinho device's 1-Wire port:
   • Spider IoT: reader center contact (signal) to the OW terminal, pin 4, purple wire; metal ring (ground) to GND, pin 7, black wire
   • Smart IoT: has two 1-Wire ports (A and B), and the key can go on either one
2. Mount the reader in an accessible location (dashboard)
3. Secure wiring away from moving parts
4. Test the connection: with the key touching the reader, the >QOW00< command answers ROW00,<ROM>,<age>

⚠️ Important: never connect a reader wire to +12/24 V. The 1-Wire input cannot handle it and will burn out. If you swap the two wires nothing gets damaged, but the device won't read any key.

The complete wiring guide, with photos, is in the documentation: iButton keys on Spider IoT and iButton keys on Smart IoT.

Configuration

1. Load the authorized keys into the device: >SICL00 01234567890ABCDE< stores a key's ROM in position 00, and >SICL+ <code>< adds it to the first free position
2. Configure the platform to receive the driver ID
3. Match each key code with the driver's name in the platform
4. Optional: create rules in the event engine to react to the identification (buzzer, relay, immobilizer)

Use Cases

Basic Identification

• Track which driver used each vehicle
• Associate trips with drivers
• Generate per-driver reports in the platform

Access Control

• Detect an attempt with a key that is not on the list (IC03 signal, failed login)
• With event engine rules, activate an output (buzzer, relay) depending on the key
• Engine immobilization without a valid key is built with rules + output + relay, tailored to your operation

Behavior Tracking

• Individual driver scoring in your platform
• Behavior comparison between drivers
• Coaching and training focus

Time Tracking

• Duration of each driver session
• Time with ignition on and time with ignition off
• Distance driven per driver

What's New in Firmware 1.09.28

With firmware 1.09.28 you can now use the iButton key and temperature sensors on the same wire. On the Spider IoT, which has a single 1-Wire port, key and sensors work together: the device checks for the key between one sensor measurement and the next (roughly once per second), so a quick touch is never missed. On the Smart IoT the key can go on either port.

You can also load a list of up to 100 authorized drivers (positions 00 to 99), stored in the device and kept across restarts. Each session records the driver code, start time, duration, time with ignition on and off, and distance in meters, and the device raises signals (IC00, IC03, ICL00…ICL99) so you can build per-driver rules in the event engine. More detail in the IC and ICL commands.

Integration with Platforms

The Rinho protocol includes a dedicated iButton report (RIB) with the position and the key code. How the driver is displayed depends on each platform and its integration:

• Rinho protocol: the code travels in the iButton report along with the position, and the platform associates it with the driver
• Other protocols: validate with your platform how it receives the driver data before rollout

Best Practices

Key Management

• Keep a registry of all keys and their position on the device list
• Have backup keys available
• Process for lost or stolen keys: delete their position from the list (>SICL02*< deletes position 02)

Installation Tips

• Mount the reader where the driver can reach it easily
• Protect from weather in open vehicles
• Label the reader clearly

Policy Considerations

• Mandatory ID before driving?
• What happens if the key is forgotten?
• Sharing vehicles between drivers?

Troubleshooting

Issue	Solution
Reader doesn't detect any key	Check which wire is ground: it must have continuity with the reader's outer ring
>QOW00< returns an error or the ROM doesn't change when the key is touched	Swapped wires: exchange signal and ground
Unknown driver alert	Load the key into the device list and register it in the platform
Intermittent reads	Clean the iButton contact surface and check for loose connections

Rinho Support

Spider IoT

• 1 1-Wire port for the reader
• Key and temperature sensors on the same wire
• Identification also via RF433 remote or Bluetooth wristband

Smart IoT

• 2 1-Wire ports (A and B)
• The key can go on either port
• Identification also via Bluetooth wristband

💡 Zero IoT has no 1-Wire port or iButton reader: on that device the driver code is entered manually or from the platform. If you prefer contactless identification, check out the ID Band wristband (Bluetooth, for Spider and Smart).

Conclusion

iButton driver identification adds accountability to your fleet management with a battery-free key that lasts 10+ years. To see every identification and temperature option on the same bus, visit iButton and 1-Wire on Rinho devices.

Need help setting up driver ID? Contact us.

---

Related articles

• How to connect an iButton reader to a GPS tracker
• iButton vs RFID vs BLE for driver identification
• Access control and driver management