Engine start only after driver authorization
Your customer wants vehicles that only start for authorised drivers — site vehicles, rental fleets, trucks with driver rosters. A platform-side solution fails exactly when it's needed: no signal, no enforcement.
How the logic runs
Driver presents an iButton key or RFID card to the reader wired to the tracker.
The algorithm checks the identifier against the list stored on the device.
Valid ID → the tracker switches its output and the starter relay releases. Invalid or no ID → the engine does not start.
Every start attempt is logged and reported to your platform when connectivity allows.
The identifier list and the relay decision live in the tracker. Underground parking, border crossings, jammed sites — authorisation still works with zero connectivity.
- Starting the engine after authorization
- Controlling outputs by iButton keys
- Access to cargo only for authorized employees
Proven templates from the Easy Logic library — we commission and adapt them to your fleet.
Straight answers
Does this need a server connection to work?
No. The algorithm and the authorised-ID list run on the device. Connectivity is only used to sync logs and update the list.
What identification hardware does it use?
iButton keys or RFID readers wired to the tracker — both are ready-made patterns in the Easy Logic template library.
Can the same setup control cargo doors instead of the engine?
Yes — the template library includes iButton-controlled cargo access with violation logging; same pattern, different output.
Want this running on your fleet?
Describe the operation — we quote the hardware and commission the algorithm with you. Stock in Johannesburg, no MOQ.