Support Home Portal Log in
Open navigation

Driver ID & Immobilisation methods with Powered Devices

The Dart, Dart2, G62 and G100 all have immobiliser functions available. 


Digital Matter does not advise connecting an immobilisation relay to a safety critical system such as the ignition or fuel pump. A starter motor cut is recommended.


This guide uses the Dart2 as an example, where there are differences, a link will be provided to the device.

Wiring Configurations

There are different ways to wire in a relay and configure the device settings to achieve a similar result.

However the aim is to try to avoid having the relay coil energised for an extended period of time - so as to not drain the vehicle battery if it is not driven for some time. 

There are 2 common use cases

  1. Default state is that the vehicle can always be started - unless via Telematics Guru or another software platform an 'immobilise' command is sent. In this case we want the relay when not energized to be closed, allowing the vehicle to start. Sending the command will energize the relay.
  2. The vehicle cannot be started until the right driver ID tag is scanned. In this case when the relay is not energized we want there to be a break in the start motor circuit.

Note we can combine these 2 methods. i.e. we can have it so that a valid ID is required to start the vehicle, but then, send a command from the server to immobilise the asset and prevent anyone from starting it, even if they have a valid ID. If one form of immobilistion (server command or Driver ID) OR the other is active, the asset can't start. 

Set up for immobilisation when a command is sent to the server.

The device's switched ground cable is attached to pin 85/Coil Negative and the starter motor connections to pin 30/Common and pin 87A/Normally Closed. 


The device will work as normal until the immobilise command is sent to the device from the server. This can be sent from Telematics Guru or a 3rd party platform. 

When the immobilise function is activated on the server, the starter motor is cut. This wiring configuration is used when you want the vehicle to operate as normal until you need to immobilise.

Dart2 Wiring DiagramG62 Wiring DiagramG100 Wiring DiagramG120 Wiring Diagram

For the OEM Server system parameters, Add 'Digital Output 1' and set;

Function: Immobiliser

Active High: Yes

Set up in Telematics Guru for Immobilisation

To immobilise an asset in Telematics Guru, first navigate to Assets >> Manage Assets and edit the asset by clicking on the name, or selecting the checkbox and clicking on the cog menu on the right.

Select the Advanced tab in Edit Asset and check 'Can immobilise Asset' as shown below.

Once a device has been set up to allow immobilisation through the edit menu, simply click on the cog menu on the right of the Manage Assets screen, and select Immobilise.

Or, from the app:

Check user permissions!

In order to see and use the 'immobilise' buttons on the app or website, your user account must have the Asset Manage permission. Remove this permission to take away a user's ability to immobilise an asset.

Sending an Immobilisation message from a 3rd Party Server

A 3rd party server can also send a message to the device to immobilise. 

  • For those using OEM server and a TCP or HTTP connector, the OEM Web API can be used to send this message
  • For those taking the device data directly, the device can be messaged directly. 

Contact DM support for details/integration documents. 

Immobilisation based on Driver ID.

The device's switched ground cable is attached to pin 85/Coil Negative and the starter motor connections to pin 30/Common and pin 87/Normally Open.


This wiring method requires the correct Driver ID to be scanned before motor can start.

This means the Vehicle will not start unless the Driver ID is accepted.

Dart2 Wiring DiagramG62 Wiring DiagramG100 Wiring DiagramG120 Wiring Diagram

Driver ID is available on the G62, Dart/2 and G100/G120.

To enable immobilisation without a valid Driver ID, the system parameter tab is named 'Driver ID' and the drop down box for Immobilise should be 'Yes' as shown below. The Digital output Parameter tab Function should also be set up for Immobiliser as shown below with Active High set to No

Async Messages

This wiring set up is the same as the Telematics guru wiring method.

Dart2 Wiring DiagramG62 Wiring DiagramG100 Wiring DiagramG120 Wiring Diagram

Async messages are used to send messages from the server to the device. These are used to:

  • Immobilise: enable or disable remotely
  • Set Digital Outputs: set or clear remotely
  • Trigger Accident Upload: trigger an upload of the accident data partition

These messages can only be sent to the device when it is connected to the server. Connections are triggered by the device. Triggers for the device to upload include:

  • On heartbeat: default is 60 min on the Dart. 
  • In trip: externally powered devices will do their best to stay connected. If ignition is on, the device is in trip by default.
  • On accident: device will do an upload
  • On digital input change: if the input is configured to “upload on change”, it will trigger a connection.
  • On tamper detection

The times when it is not connected, the message will not be delivered until the next connection. This includes:

  • After a trip end and upload, when the device is idle and sleeping
  • Between heartbeats, until the next upload trigger.
  • If the device cannot make a connection to the server because of network issues.

Driver ID

Scanning DriverID tags

After scanning a DriverID tag, the tag data will be forwarded to your end platform, or reported in OEM under Device logs if data capture is on.

It will also appear in TG Telemetry, Assets -> Telemetry

Setting up Drivers in Telematics Guru

A driver list layout will need to be assigned in the specific organization that the list will be. You would need to go to Admin->Organization Manage->Organization and select edit on the organization that you intend to have a driver list set up for. Most RFID readers (all of Digital Matter readers) would use short identifier. Once selected, save your changes and move on to creating your drivers below.

Using the tag data you can create a new driver in TG from Admin > Drivers > New and fill out the details as below. 

The Driver ID tags that are available from Digital Matter are the Yellow DM RFID keyfobs and the blue iButton tags.

After adding the new driver details, you can assign the driver permission to drive a specific vehicle, or allow all enabled drivers in the Drivers tab in Edit Assets

Driver ID Features

Some screenshots of system features that utilise driver ID are shown below.

Assets can be allocated to Drivers which can be useful to identify Assets by Driver.


When a Driver Tags on for a trip, the driver will be displayed on reports . The following are speeding reports that list the driver names, and a speed group percentage report by vehicle.

Fleet Management Summary Report

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.