← User guide

Vehicle hardware

Inputs and outputs (IO)

How wired inputs and outputs on a tracker turn into events and alerts, how immobilisation is kept safe, and where each signal is set up.

Inputs and outputs (IO) are extra wired signals on a professionally-fitted tracker. Inputs tell AutoM8 when something happens on the vehicle - the ignition comes on, a panic button is pressed, a door opens. Outputs let AutoM8 switch something on the vehicle - a beacon, or an immobiliser. Each wire is labelled with a role during installation, and AutoM8 uses that role to decide what an event means.

Hardware required. Inputs and outputs need the extra wires fitted and commissioned (wired up and switched on - your installer does this when the device is fitted) when the tracker is installed. What a vehicle can report or switch depends on how it was wired.

Permissions. Permissions live in Settings > Roles and Permissions (in the FMS (Fleet Management) group). Editing a vehicle’s IO settings needs Io Edit; managing reusable IO templates needs Io Templates; switching an output (such as an immobiliser) needs Devices Output Control; and commissioning the wires during installation needs Io Commissioning. Administrator and Manager include these by default.


Inputs

An input is a wire that reports a state on the vehicle. Each input is given a role that sets a sensible label, and whether it raises an event, an alert, or an emergency state on the live map. The labels below are suggestions - your installer or an administrator can rename any of them.

Input What it means Raises
Ignition The vehicle’s ignition state. This is always the first input. An event
Blue lights Emergency blue lights are on (Section 19 exemption). Shows a blue ring on the live map. An alert and an emergency state
Siren The siren is on. An alert
Panic button The driver has pressed a panic or duress button. This is critical - it shows a red ring on the live map and cannot be missed. A critical alert and an emergency state
PTO / Equipment Power take-off or auxiliary equipment is running. An event
Door A vehicle or cargo door has opened or closed. An event
Tail lift The tail lift is operating. An event
Bin lift A refuse bin lift has activated. An event
Refrigeration The refrigeration unit’s power or temperature alarm. An alert
Low fuel A low fuel warning. An alert
High temperature An engine or cargo high-temperature warning. An alert
Auxiliary A general-purpose input for anything else. An event
Custom Any other input, with a free-text label you choose. An event

How an input becomes an event

Each input has trigger settings so it reports meaningfully and does not spam you:

  • a debounce - it ignores brief flickers on the wire,
  • a qualify time - the input must stay on for a set number of seconds before it counts (for example, a door has to stay open for a moment, so a swing does not count), and
  • a cooldown - a minimum gap before the same input can report again.

When an input meets its trigger conditions it is written as a driving event and appears on the Driving events page, labelled with its role (for example “Panic button activated” or “Door opened”). Panic and Blue lights also raise an emergency state on the live map, so anyone watching sees the coloured ring straight away.


Getting alerted

Some inputs raise an alert as well as an event. Which inputs alert, who is notified and on which channel is set up by an administrator in Driving event alerts under Settings > Fleet - see Notifications. Alerts can go to the assigned driver, to fleet managers, or to named people, on In-app, Email or SMS.

Two things keep alerts sensible:

  • Storm control (an automatic limit - you do not configure it) caps the number of non-critical alerts for a single vehicle in an hour, so a noisy wire cannot flood you.
  • Escalation - if a non-critical alert is not acknowledged in time, it is escalated to your fleet-manager group.

Critical alerts (a panic button) bypass both of these - they are always delivered and never held back.


Outputs and immobilisation

An output is a wire AutoM8 can switch. The shipped output roles are a Beacon (a rooftop warning light) and an Immobiliser. Switching an output needs the Devices Output Control permission.

Safety interlock. An immobilise command is only accepted when the vehicle is confirmed stationary with a recent position reading. If the vehicle is moving, or its speed or position is unknown or too old to trust, the command is refused and you see “Blocked for safety - the vehicle must be stationary.” This protects the driver - a vehicle is never immobilised while it is moving. Immobilisation is a wired output, so it needs the immobiliser fitted (Hardware required).

Who can do this: any role with the Devices Output Control permission.


Where it is set up

There are three places IO is configured, and day to day you will rarely touch the first one - your installer handles it.

During installation. Your installer commissions and labels each wired input and output using the installer app (the Io Commissioning permission). Tenants do not commission wires in the web app - the installer does it when the tracker is fitted.

Per vehicle. On a vehicle’s I/O settings you can adjust the labels and trigger settings for that one vehicle. This needs the Io Edit permission.

Reusable IO templates. In fleet settings you can build an IO template that bundles a set of input and output definitions (and their rules) and apply it to many vehicles at once. This needs the Io Templates permission. When you save a template that already has vehicles on it, you choose:

  • Save only - just saves the template, without changing any vehicle, or
  • Save & push - saves the template and sends the configuration, including the output settings, to every vehicle the template applies to.

Who can do this: commissioning needs Io Commissioning (installer); per-vehicle IO settings need Io Edit; templates need Io Templates; switching an output needs Devices Output Control.


Troubleshooting

Why was my immobilise command blocked? The safety interlock refused it because the vehicle was not confirmed stationary. An immobiliser is only switched when the vehicle is stopped with a recent position reading; if it is moving, or its speed or position is unknown or too old, the command is blocked and you see “Blocked for safety - the vehicle must be stationary.” Wait until the vehicle is stopped and reporting, then try again.

Why is there no event for an input I expected? Either that input is not wired or labelled on that vehicle, or the trigger conditions were not met - the wire may not have stayed on long enough for its qualify time, or it fired again inside its cooldown. Check the vehicle’s I/O settings, and remember only the inputs your fleet is actually wired for will report.

Why did nobody get an alert? Either no driving-event alert rule is set up for that event, or the rule has no recipients chosen. Open Driving event alerts under Settings > Fleet, check a rule exists for the event, and make sure at least one recipient (driver, managers or named people) and a channel are selected.

For permission, scope or licence causes (you cannot see or do something you expect to), see Troubleshooting.