Skip to main content
Sign in

Set up and remotely control an immobilizer

Marisa Potgieter

Many mobile devices support an immobilizer: a relay-controlled peripheral that prevents a vehicle from starting until a valid driver is identified, or until you release it remotely. You configure the immobilizer as part of the device setup, then arm or release it from Commands to mobile device in On-Road IoT, or let it control access automatically through Driver ID.

The immobilizer peripheral must be assigned to the correct output line in the mobile device configuration (for example, O1 on a Ruptela Eco5 Lite, or Output 2 on a MiX 6000 LTE). If the output line is not configured, the immobilize and mobilize controls are not offered for that asset.

Supported devices

Device Immobilizer control Notes
Ruptela Eco5 Lite Remote (Set Relay Drive) Must be assigned to the O1 output line.
MiX 6000 LTE Remote (Disarm the Asset Remotely) and Driver ID Output 2 can be used for the immobilizer relay. Requires a wired ignition install and a starter interrupt relay (not included).
MiX 4000 Remote (Disarm the Asset Remotely) and Driver ID Uses the blue Driver ID key and Code Plug socket.
MiX 6000 Driver ID Uses the blue Driver ID key and Code Plug socket.
FM 3xxx Driver ID Can only wake from ignition, not from the accelerometer.
Teltonika (MiX Essential Plus) Remote (enable/disable immobilizer) Assign the peripheral to output line O1 or O2 in the mobile device template.
Orbcomm ST6100 (SAT only) Remote (Set Immobilizer command) On/off command only. Limp Mode is also available.
Orbcomm ST9100 (GSM + SAT) Remote (Set Immobilizer command) On/off command only. Limp Mode is also available.

Exact output line names and available commands depend on the mobile device type and how it has been wired. Not every device supports every control listed above.

Set up the immobilizer

Before you can immobilize or mobilize an asset remotely, the immobilizer peripheral must be wired to the mobile device and assigned to the correct output line in the mobile device template.

  1. In On-Road IoT, click Manage.
  2. Under Config Admin, click Templates.
  3. Click the Mobile device templates tab.
  4. Search for the relevant template, then click the hyperlinked template description, or click the three dots menu and select Edit.
  5. Click the link next to the output line used for the immobilizer (for example, O1). If you do not see a link, click Load now to load the available peripherals for the organization.
  6. Select the immobilizer peripheral from the dropdown list.
  7. Click Save.

This example uses a Teltonika device. Exact tab names and output line labels vary by device — read Assign output lines for relay control peripherals on a Teltonika device for the full illustrated example.

If immobilization is not required, the output line does not need to be configured and no additional setup is necessary.

Using Driver ID instead of a remote command

Some devices immobilize the vehicle automatically until a valid Driver ID is presented, instead of or in addition to a remote command:

  • FM 3xxx: Turn on ignition to wake the unit, then insert the blue key into the Code Plug socket. The vehicle can be started once you hear the double beep confirming the Driver ID has been accepted.
  • MiX 6000: Follow the same procedure as the FM 3xxx. Because the MiX 6000 runs a Linux OS, allow about 30 seconds for it to boot from deep sleep before the double beep sounds.
  • MiX 4000: Follow the same procedure as the FM 3xxx. The MiX 4000 responds immediately when ignition is turned on.

On the MiX 6000 LTE, the immobilizer arms automatically after a configured arming period at the end of every trip, and is deactivated as soon as a valid driver is identified. Restarting during the arming delay does not require the driver to be re-identified.

Driver ID based immobilization is controlled per driver — read Driver access control to set up which drivers may start which assets.

Immobilize or mobilize an asset remotely

Once the immobilizer is configured, you can send an immobilize or mobilize command from Commands to mobile device in Live Tracking.

  1. In On-Road IoT, click Monitor.
  2. Under Tracking, click Live Tracking.

AccessLiveTracking.png

  1. Search for the relevant asset.
  2. Click the three dots menu at the end of the asset row, or click the asset to open its details.
  3. Click Commands to mobile device.

SendCommandToMobileDevice.png

  1. Depending on the device type, choose one of the following:
    • Set Relay Drive, then select the immobilize command to prevent the vehicle from starting, or the mobilize command to allow it to start again.
    • Choose an Output Line and New State, then set the output line used for the immobilizer back to Immobilizer to return control to the device firmware.
    • Set Immobilizer command (Orbcomm ST6100/ST9100 only), then choose On or Off.
    • Disarm the Asset Remotely (MiX 4000 and MiX 6000 LTE only).
  2. Click Send.

The asset page also offers Commands to mobile device, so you don't need to go through Live Tracking every time.

If the device is offline or unreachable, On-Road IoT reports "failed to send command to mobile device." The command is not delivered, and you will need to resend it once the device is back online.

You can also set up a stream in the Info Hub to track commands sent to the mobile device.

RECOMMENDED READING

Related to