Vehicle Track

Mon, 01 Jan 0001 00:00:00 +0000

The OGLAS Vehicle Track wires into the accessory rail of a vehicle — or any engine on the site — and logs every run. Trips, hours, fuel-time, GPS, battery state. Equally happy on a tractor, a ute, a forklift, a golf cart, a generator, or the irrigation pump’s diesel — a single asset or a whole fleet.

What it does

Power up = new run — each start records a fresh log entry at zero minutes, with a GPS fix and the starting battery voltage.
Counts minutes while running — re-persisted to flash every minute so a flat battery never costs more than 60 seconds of log.
Records a path, not just a duration — periodic GPS waypoints during the run (configurable interval), so you have where it went, not just for how long.
Captures battery voltage at start, periodically during the run, and at shutdown. Lets you spot a failing alternator before the day it doesn’t crank.
Reads the engine via OBD-II (optional) — on vehicles with an OBD-II port: RPM, coolant temp, fuel level, speed, and fault codes (DTCs), logged with the run.
Measures how it’s driven via an IMU (optional) — harsh use, idle vibration, and tip/roll angle for a rollover warning on a tractor, quad, or forklift.
Back-walks unsent runs on each start — sends the most recent run first, waits for confirmation, then walks back to the next unconfirmed run until it hits one already recorded.
Rolls over — fixed ring buffer of 500 records by default; newest id overwrites oldest slot.
Shows alerts in the cab — sensor and site alerts appear on the on-board display while you’re in the vehicle. Low water, fence down, gate left open, engine service due — see alerts in the cab below.
Identifies the operator (optional) — a short list of names selectable at start, so the run log records who drove, not just what drove.
Triggers external devices — built-in button or configurable proximity rules can open a gate, ring a bell, or activate any other OGLAS device.

OBD-II and IMU

Two optional add-ons turn Vehicle Track from a run-logger into a condition-logger:

Engine

Mon, 01 Jan 0001 00:00:00 +0000

An engine that never moves still wears out — and the backup generator nobody logged is the one that won’t start when you need it. The OGLAS Engine sensor brings the Vehicle Track run-log to fixed engines: generators, pump engines, compressors, anything that runs in place.

What it does

Detects runs — from the engine’s accessory output, a vibration sensor, or current on the load. Every run is logged with start time and duration.
Counts hours — accumulated run-time per engine, so service intervals are by hours, not by a date someone guessed.
Trends battery and starting — for engines that fail to crank, the battery is usually the culprit; trend the voltage and you’ll see it coming.
Flags exercise gaps — is the backup genset actually being run monthly, or has it sat idle since spring?
Raises service alerts — hours-since-service past the limit rings the bell or pushes a notification.

Why it’s its own sensor

It shares the run-log engine with Vehicle Track — the difference is the trigger and the fact that GPS doesn’t move. For anything with a cab and a journey, use Vehicle Track; for a genset bolted to a slab, use this.

Vehicles & Engines on OGLAS — Off-Grid Local Alert System

Vehicle Track

What it does

OBD-II and IMU

Engine

What it does

Why it’s its own sensor