← All projects

Mobile / compliance-oriented systems

LogiIQ ELD

A driver-focused electronic logging application with duty controls, hours-of-service presentation, logs and diagnostics.

BuiltHours-of-service clocks (11 h drive, 14 h window, 30-min break, 70 h / 8 days) derived from an append-only duty-event history on every evaluation.

Verification notesDriver source reviewed · hardware verification pending

System sketch
  1. 01Driver and vehicle signals
  2. 02Append-only event history
  3. 03Derived clocks and review
Conceptual design. Not a certified ELD and not a verified hardware integration.
Demo data · no backend

Runs entirely in your browser. Opens with fictional sample data; Regenerate builds fresh rows from the project's schema. Clears on refresh.Open full screen ↗

Authorization in this portfolio

Only the driver surfaces backed by the source are shown: Home, Logs, DVIR and Diagnostics, plus a Rules view for the ported split sleeper, restart and exception logic. Clocks are derived from fixture duty events by a compact port of the source rules and do not certify compliance.

01

Operational problem

Drivers need to understand duty status, available time and missing vehicle signals without losing the history behind a clock. The source Driver Home composes these concerns from a snapshot rather than calculating them inside presentation components.

02

Technical constraints

Offline events, corrections, vehicle motion and diagnostics complicate driver records. A static portfolio cannot reproduce hardware behavior or validate regulated clock calculations. The portfolio therefore derives its clocks from fixture duty events with a compact port of the source rules and labels it as such.

03

Architecture

DriverHomeScreen consumes useDriverHome snapshots and composes connection, duty, alert and HOS components. Expo Router tabs include Home, Logs, DVIR, Documents and Settings. Services adapt HOS state separately from the interface. The portfolio shows only these source-backed driver surfaces.

04

Implementation

The portfolio recreates the dark driver layout, PT30 disconnected card and OFF/SB/D/ON controls. A compact HOS engine adapted from domain/hos derives Drive (11 h), Shift (14 h window), Break (30 min after 8 h driving) and Cycle (70 h / 8 days) from append-only events over a rolling 8-day history, with a simulated clock. It also ports split sleeper pairing (7 h sleeper + 2 h, recalculated from the end of the first period), the 34-hour restart, and explicitly declared adverse-driving and 16-hour short-haul exceptions with their eligibility checks; the two exceptions do not stack. Three fixture scenarios show a standard day, a split sleeper day and a post-restart week. Logs rebuild today's 24-hour duty graph from those events; DVIR enforces complete inspection; Diagnostics can be acknowledged but not cleared. The demo never scans or opens a hardware connection.

05

Testing

The reference tree contains tests for home-HOS adapters, events, diagnostics and PT30-related components. These suites and real-device sessions were not run for this task. Portfolio tests cover the derived clocks, 10-hour reset, 30-minute break, window overrun, cycle totals, split sleeper pairing rules, the 34-hour restart, adverse and 16-hour limits, exception cooldown and non-stacking, append-only events, DVIR certification rules and diagnostic acknowledgement.

06

Current status

The separate mobile source was reviewed. This is not an approved ELD. PT30 integration is unverified on real hardware in this review, and certification is not claimed. The demo engine ports split sleeper, the 34-hour restart, adverse driving and the 16-hour exception from the source; it is a compact port, not the full engine.

Project links

Public demo and source links have not been approved for this portfolio.

Continue exploring

All case studies →