Skip to content
  • There are no suggestions because the search field is empty.

Edit vehicle and hardware tracker settings

Understand and update a vehicle's identity, map display, operating counters and model-specific hardware tracker options.

Edit a vehicle when its identity, map appearance, operating totals or tracker behaviour no longer matches the vehicle in service. The available hardware settings depend on the tracker model and how it is installed.

Before you start

You need permission to edit records. Check the physical vehicle, tracker model and wiring before changing tracker behaviour. Incorrect ignition, sleep, input or output settings can cause missing journeys, delayed updates or unintended accessory operation.

If many vehicles need the same identity or operational changes, use a CSV import instead. Use the editor for model-specific tracker controls and one-off corrections.

Steps

  1. Open Vehicles.
  2. Find the vehicle and select its pencil Edit action.
  3. Review the settings below. Only change values you can verify.
Vehicle editor showing identity, operating totals, input nicknames and the TMR-S8 Driver login beep mode.
Vehicle editor showing identity, operating totals, input nicknames and the TMR-S8 Driver login beep mode.
  1. Select Save. Identity and display changes appear after the record refreshes. Hardware commands take effect after the tracker next connects and accepts them.
  2. Reopen the vehicle to confirm the saved values. After changing tracker behaviour, test it safely and review Vehicles > Events, Map or a journey report as appropriate.

Vehicle details and display

Setting: Name
What it controls: The main vehicle name shown in lists, map labels, vehicle selection fields and reports.
When to change it: Rename a vehicle, correct a spelling error or apply your fleet naming standard. Use a unique, recognisable name.

Setting: Registration #
What it controls: The vehicle registration stored with the record.
When to change it: Update it after registration changes or correct a mismatch used in fleet records.

Setting: Map icon
What it controls: The vehicle or equipment symbol displayed on the map.
When to change it: Choose a symbol that helps users distinguish cars, trucks, machinery, marine assets or other equipment. It does not change tracking behaviour.

Setting: Company ID
What it controls: Your organisation's unique vehicle or asset identifier. It accepts letters, numbers, hyphens and underscores.
When to change it: Match Track My Ride to an internal fleet, payroll or asset-management system. Each vehicle should use a unique value.

Setting: Timezone
What it controls: The vehicle's local time offset and daylight-saving rule.
When to change it: Correct event, journey and report times when a vehicle operates in another region or the wrong daylight-saving option was selected.

Setting: Path colour
What it controls: The colour used for this vehicle's path on the map and playback.
When to change it: Make overlapping vehicle paths easier to distinguish.

Setting: Notes
What it controls: Internal free-text information about the vehicle, installation or operating requirements. Notes accept up to 2,000 characters.
When to change it: Record useful context that authorised users should see when editing the vehicle, such as installation details, equipment references or service instructions. Do not store passwords, access keys or other secrets.

Vehicle editor Notes field containing synthetic installation and service information.
Vehicle editor Notes field containing synthetic installation and service information.

Operating totals

HRM means hour-run meter: a total of operating time recorded in decimal hours.

Setting: Odometer
What it controls: The current distance total in kilometres used as the starting or corrected value for distance-based records.
When to change it: Enter the dashboard odometer during setup or correct drift after checking the physical vehicle. Do not reduce it without confirming the reporting effect.

Setting: Journey HRM
What it controls: Decimal hours accumulated while the vehicle is on journeys.
When to change it: Align journey runtime with an existing hour meter or correct an imported starting value. Decimal increments represent tenths of an hour.

Setting: Engine HRM
What it controls: Decimal hours accumulated while the tracker detects the engine as on.
When to change it: Align engine runtime with machinery records or correct a known starting value. A continuing mismatch usually means engine detection needs review.

Powered hardware tracker settings

These controls appear only on compatible hardware. Settings shown behind an Edit or Toggle Output button are sent to the tracker only when changed.

Setting: Sleep mode
What it controls: How aggressively the tracker turns off GPS and mobile communications after inactivity.
Why and when to change it: Use deeper sleep to reduce parked-vehicle power use; use lighter sleep when faster wake-up or more frequent communication matters. Some ultra-deep modes suppress scheduled heartbeat wake-ups; confirm the behaviour shown for the selected tracker.

Setting: Heartbeat
What it controls: How often a tracker in a supported deep-sleep mode wakes and reports location and status.
Why and when to change it: Shorten it for fresher parked status at higher power use, or lengthen it to conserve vehicle or tracker power.

Setting: Engine detect
What it controls: Whether engine on/off is detected by voltage, ignition wire, motion, or a supported combination.
Why and when to change it: Match the installed wiring and vehicle behaviour. Use Ignition sense wire only when the correct switched source is physically connected.

Setting: Engine volts
What it controls: The voltage threshold above which voltage-based detection considers the engine on.
Why and when to change it: Adjust only when verified charging voltage causes false engine events or missed journeys. Choose an appropriate 12 V or 24 V threshold.

Setting: Input 1 sensing
What it controls: Whether TMR-S8 Input 1 is active from a positive signal or a ground connection. Positive sensing (+12 V active) is the default; negative sensing is available for a deliberately installed ground-active circuit.
Why and when to change it: Match the setting to the physical Input 1 wiring. Have the installer disconnect the previous switched source before changing modes. Input 2 remains positive sensing.

Setting: Input 1 and Input 2
What it controls: The event action assigned to each supported physical input, including No action (default) or Panic button.
Why and when to change it: Enable a wired panic switch only on the input to which it is physically connected.

Setting: Input nickname
What it controls: An optional name of up to 20 letters, numbers, spaces, hyphens or underscores for each physical input.
Why and when to change it: Name the equipment or signal connected to the channel, such as Door, Pump or Panic, so users can distinguish Input 1 from Input 2.

Setting: Output 1 mode
What it controls: Manual control (default), the ignition-based Driver login reminder, or Driver login beep on a TMR-S8. Driver login beep pulses Output 1 for 200 ms after a successful Driver ID read.
Why and when to change it: Use Driver login beep only when the included buzzer is connected to Output 1 and a short confirmation beep is required. Use the reminder only with its supported hardwire and ignition configuration.

Setting: Output nickname
What it controls: A user-facing name for the accessory connected to an output.
Why and when to change it: Replace a generic channel name with the accessory purpose so authorised users know what they are controlling.

Setting: Output state and duration
What it controls: Enables or disables a supported output permanently or for a selected period.
Why and when to change it: Operate an installed accessory only after confirming its wiring and safe state. A timed action reverses when its duration expires.

Output controls can operate physical equipment. If you do not know what is connected, cancel the edit and ask the installer or account administrator.

Battery tracker settings

These options appear only for compatible battery-powered models.

Setting: Operating mode
What it controls: Real-time tracking records detailed trips and supports motion alerts; Interval tracking wakes periodically to report a position.
Why and when to change it: Choose real-time mode for active movement visibility. Choose interval mode when long battery life matters more than journey detail or motion alerts.

Setting: Motion sensitivity
What it controls: The movement threshold that wakes the tracker and can generate motion alerts in real-time mode.
Why and when to change it: Increase sensitivity for smaller movements, or reduce it if vibration causes unwanted wakes and alerts.

Setting: Ping interval
What it controls: How often an interval-mode tracker wakes to report its position.
Why and when to change it: Use a shorter interval for fresher locations at the cost of battery life, or a longer interval for maximum endurance.

Current charge and Estimated battery life are status estimates, not editable parameters. Use them to assess the effect of the operating mode and ping interval. Actual battery life varies with coverage, temperature and movement.

What happens next

Names, identifiers, counters and display options update the vehicle record. Tracker options are queued for compatible hardware and may remain pending while the tracker is asleep or offline. New settings affect future tracking and events; they do not reconstruct previous journeys.

Troubleshooting

  • If Edit is unavailable, ask an account administrator for record-editing permission.
  • If a setting is missing or disabled, it is not supported by that tracker model, installation or account feature.
  • If a hardware change does not take effect, confirm the tracker has connected since saving. Sleeping and offline trackers cannot receive commands immediately.
  • If journeys start or stop incorrectly, restore the previously verified engine-detection setting and check the wiring and voltage with a qualified installer.
  • If odometer or hour-meter totals continue to drift after correction, verify engine detection and reporting data before repeatedly changing the counters.