Questions, answered

It depends on the model and how often the tracker reports. Veer Pico lasts up to four months with typical use (about three hours a day) or 36 hours of continuous tracking. Veer Max runs up to one week on backup power, while hardwired models draw from the vehicle and use the internal battery only as backup.

Yes — live tracking, alerts, and history run through the VEER cloud. Every subscription tier includes free cloud access with unlimited map data and statistics for every vehicle you add.

Most models connect with a simple power harness and can be fitted in minutes. OBD models plug straight into the vehicle's diagnostic port — no tools required. Veer Pico screws onto a tank or fairing mount; Veer Micro is a compact stick-on or cable-tie install with no vehicle wiring.

VEER trackers report over mobile networks wherever coverage exists. Veer Max also links over LoRa to a Screen Fob or home relay, so alerts still reach you when mobile coverage is unreliable.

Built-in accelerometer and gyroscope sensing detects incidents and unauthorized movement. Veer Max escalates confirmed anti-theft events with a 24/7, 365 call centre response.

VeerSense is a customisable motorcycle sensor kit. Add front and rear suspension, brake pressure, RPM, speed, and temperature sensors to a central hub. The hub connects to a VEER tracker or streams over Bluetooth so those extra channels land in your telemetry sessions alongside GPS.

Only you and the people you explicitly invite to your account. Location history is tied to your account, never sold, and you can delete your data at any time.

Open Race from My Sessions (or Driver Sessions if you are staff). The analyser, video editor, and gallery are the same Race tools on web, desktop, and VEER Replay.

On My Sessions, use Import. RaceBox CSV, VBO, VEER on-device CSV, and Dragy history files (.dragy) use the same import pipeline. Cloud save is a plan feature; if your plan does not include it, the session can stay on this device.

VEER Commander is the Bluetooth companion for Mini and OBD: live data, files, history download, and device settings. VEER Replay is the phone Race app for analysing cloud sessions. Desktop Race matches the web analyser. Download links are on the public Download page.

Both boards have four status lights: red = GPS, white = microSD, blue = Bluetooth, green = recording. On Mini, if Screen / Wi-Fi is enabled, green follows the Wi-Fi link instead of recording. Sleep, low-battery breathe, and Developer Lights override these patterns.

Red follows GNSS. A 3D fix uses an aircraft double-flash (1.2 s in High GPS quality, 0.6 s in Fast). A 2D fix is solid. No fix is off.

White is the SD activity light. It stays on while the card is mounted and idle, ticks like a hard-drive light on GPS writes, format, and file transfers, and is off when the card is unmounted, ejected, or missing.

Blue is Bluetooth. It stays on while a phone or Commander client is connected, and ticks or blinks during notify, receive, downloads, and file transfers. It is off when nothing is connected. Developer Lights can force blue on.

Green is solid while a session is recording. On Mini, if you allow the screen / Wi-Fi link, green instead matches that link: solid while Wi-Fi is enabled, with the same ticks on AP traffic. A slow green double-beat is Sleep now.

That is the 75–89% memory warning. All four lights flash together at 50 ms on / 50 ms off. Recording continues. Fill is the higher of FAT used space and on-device history fill — the same percent Commander shows.

That is the 90% memory error pattern. Recording has stopped. All four lights do five 20 ms flashes, pause, then repeat until you free space. This is faster and more stuttered than the 75% warning so it reads as a fault.

That sequential breathe is low battery (below 10% pack, not on a charger) or Developer Lights → Breathe. In low-battery sleep the board powers down GPS and radios until USB or a voltage rise wakes it.

At 90% fill the device closes the log and will not start another until you free space. Commander’s memory percent is the same gauge: the higher of FAT used space and history sample fill (about 196,608 points). Erase device history, delete files, or format the card from Commander, then recording can start again.

In VEER Commander, open the device history panel to download closed sessions to the phone, or use Files to copy logs from the card. Stop recording if you need the open log. Then open the session in VEER Replay or import it on web/desktop.