Testing Driver key on the bench

Once you have confirmed that you have configured your device and the driver key to immobilize a vehicle, the next test is to confirm that the driver key is registered. After registering the driver key, you need to ensure that the information required to identify when a driver has tagged is available.

As part of the device configuration, make sure that you can view from the debug window when a driver has tagged. This will help you verify that the tagging process is functioning correctly.


invalid driver tag  :

• Related Articles

• Driver key configuration and Mhub 369B wiring instruction

  Below are the steps to configure your device to use Input 1 has a source of ignition : How to set input 1 as a source of ignition [for Trip start ]: 1.Ensure that you have set the following setting on your device configuration ( you can search for ...

• MHub369 DriverKey and Immobilization and Disablement

  The Immobilization and Disablement feature on the MHub369 is very similar to the feature on all previous MHubs. One addition that was recently added to the MHub369 is to allow disablement only when the Ignition or Trip flag goes off. How does it ...

• Mprofiler Manual.

  Kindly see the attached, Mprofiler Manual PDF. Table of Contents: 1. Introduction ...............................................................................................................3 2. Notice ...

• MHub369 Temperature Guide

  INTRODUCTION After completing this manual, you will be able configure the MHub369 unit with all the necessary parameters required for the use of temperature sensors. The 369 allows for a maximum of four temperature sensors to be connected at the ...

• Introduction on how create a Workspace in D-Insight Fleet.

  In DIF (D-Insight Fleet), on the top left corner of the landing page, there is a 'tab' called 'WORKSPACE' that users can use to display multiple pages. You can use these pages to summarize information that is important to you as a fleet manager or ...