The Dart, Dart2, G62 and G100 all have immobiliser functions available.
Note: 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.
There are a few ways to enable an immobiliser
- Telematics Guru Immobilise function
- Driver ID
- ASYNC message sent from server
Option 1 - Telematics Immobilisation without Driver ID used, 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. (pdf attached)
This means when the immobilise function is activated in Telematics Guru, the starter motor is cut. This wiring configuration is used when you want the vehicle to operate as normal until you need to Immobilise.
For the OEM Server system parameters, Add 'Digital Output 1' and set;
Active High: Yes
Telematics Guru 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.
Immobilisation via 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 (pdf attached)
This means the Vehicle will not start unless the Driver ID is accepted.
Immobilisation with Driver ID
- Please review the separate device sections for information on setting up Driver ID.
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 Mesages 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.