MHub369 DriverKey and Immobilization and Disablement

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 work?

Any of the outputs on the MHub369 can be configured to be used as the immobilization output. The outputs on the MHub are the “pulled to ground” type, which means if the output is activated it will be pulled to ground. As a practical example you would connect one side of the immobilization hardware (typically a relay) to power and the other side to the MHub’s output. When that output is activated, it will connect to ground, completing the circuit to energize the relay coil.

On the MHubs when the vehicle is immobilized the output is ON which means if a relay is connected it will be energized. This implies that the starter motor, fuel pump or whatever part of the vehicle is used to inhibit driving needs to be wired to the Normally Closed pins of the relay. To ensure there is no excessive current drawn by the relay the powered side of the coil should be connected to “Accessories” on the ignition switch ensuring the coil is only powered when the key is turned.

There are several ways the immobilization output can be controlled:
  1. Follow ignition: This is used where there is no driver identification hardware and the vehicle is allowed to be driven as normal, however this still allow for the disablement of the vehicle in case of theft or any other reason where the vehicle should not be allowed to be driven.
  2. Driver Identification: In this case a driver is issued a driver tag/key/badge/card that he/she would need to scan to de-immobilize the vehicle to allow it to be driven.

Disablement is a feature where the immobilization hardware can be invoked remotely to stop the vehicle from being used even if a valid driver is identified by the MHub369. While a vehicle is Disabled, the only way to drive it again is to Enable it again. 

Configuration

Follow Ignition Mode

As explained above, in this mode there is no driver identification hardware fitted, and the vehicle can be driven as normal. The vehicle is automatically de-immobilized when the ignition is switched ON and immobilized again when it is switched OFF. However, if the vehicle is currently Disabled it will not be allowed to be driven until it is Enabled again using a command.

Do not confuse this with the parameter that specifically configure and output to be in “Follow Ignition” mode as this will not take any of the immobilization or disablement configuration into consideration when determining the state of the output. 

Parameters 

Parameter

Value

Notes

Driver Key->Enable Driver Key

0

Disable the Driver Key functionality as a Driver Identification mechanism is not installed

Immobilization->Driver Key

controls Output used for Immobilization

0

This is to tell the MHub that the Driver Key is not controlling the immobilization output

Inputs and Outputs->Output A Function

16

This configures Output A as an Immobilization Output.

Inputs and Outputs->Output

B Function

16

This configures Output B as an Immobilization

Output.


Driver Identification Mode

In this mode some form of Driver Identification hardware is fitted and it is used then to validate a driver and de-immobilize a vehicle if the driver is valid. There are several different hardware options available, from Dallas DS1990 devices to Scope’s own driver key based on the DS1992 to RFId readers that emulate DS1990 devices. More driver identification devices will be considered for integration in the future.

In this mode the de-immobilization of the vehicle is triggered by the successful validation of a driver. When a driver is successfully validated, the output that is linked to 2 3 the immobilization device will be switched on or off, determined by the configuration of the MHub. If the vehicle is disabled via a remote command, the MHub will not allow another driver to be validated until the vehicle is enabled again.

Also, when a Driver is validated, there is a configurable amount of time available during which the driver needs to start the vehicle. If this time expires the vehicle will be immobilized again making it necessary for the driver to validate again before trying to start the vehicle. During the driver valid timeout any further reads on the Driver Key hardware is inhibited.

There are several parameters that configure this functionality, from configuring the physical outputs to what happens when a vehicle is mobilized to the timeouts and other relevant features.

Parameters

Parameter

Value

Notes

Driver Key->Enable Driver Key

1

Enables the Driver Key functionality.

Driver Key->Driver Key Type

0 or 8 = Scope DS1992

1 = DS1990/SGBras

252 = RF9092A05M12

253 = RF909203-125

254 = Keypad+RFID

This tells the MHub what kind of key to expect.

Driver Key->Pre-Trip Validity

30

How much time does the

Driver have to start the vehicle after a successful validation.

Driver Key->Post Trip Validity

30

How much time does the Driver have after a trip ends to restart the vehicle before

having to revalidate

Immobilization->Driver Key

controls Output used for Immobilization

1

This is to tell the MHub that the

Driver Key is controlling the immobilization output

Inputs and Outputs->Output

A Function

16

This configures Output A as an

Immobilization Output.

Inputs and Outputs->Output B Function

16

This configures Output B as an Immobilization Output.

Parameters – Scope Driver Key

Parameter

Value

Notes

Driver Key->Verify Driver ID

0/1

This will only allow the Driver to be

validated only if the Driver ID

 

 

programmed in the key is in the list of 30 programmed Driver IDs

Driver Key->Driver ID 0..30

 

This is the list of valid Driver IDs

Driver Key->Verify Driver Class

0/1

If the Driver Key is programmed with a Class this value needs to be equal or greater than the programmed Vehicle

Class before the driver will be validated

Driver Key->Vehicle Class

 

Class of the Vehicle

Driver Key->Verify Fleet Code

0/1

If the Driver Key is programmed with a Fleet Code it needs to match the

programmed Fleet Code before the driver will be validated

Driver Key->Fleet Code

 

Fleet Code of the Vehicle

Driver Key->Verify Customer Code

0/1

If the driver key is programmed with a Customer Code it needs to match the programmed Customer Code before the

driver is validated.

Driver Key->Customer Code

0-65535

Customer Code of the vehicle

Driver Key->Driver ID 0 to 30 Blacklist

 

This is a bitmask that specifies which of the Driver IDs programmed in the 30

slots is not allowed to be validated.

Parameters – Other Driver Identification HW 

Parameter

Value

Notes

Driver Key->Verify Driver ID

0/1

This will only allow the Driver to be validated only if the 64Bit Driver ID is in the list of 5000 programmed Driver IDs. If this value is 0 then any key will allow the vehicle to be immobilized, and the

key is just used for Driver Identification. This list is managed by MZone.

Driver Key->Customer Code

0-65535

When the keypad is used to validate a driver entering a PIN this will be the

number reported in the events to ensure secrecy of the PIN.

Important: Only the Driver Identification Event and the Immobilization Event carries the full 64 bit Driver ID. In case of other (older) events like Driver Registered or any other event that contains the 16 Bit Driver ID that it will be set to the bottom 16 bits of the 64 bit number reported by the other driver identification hardware. 

Immobilization and Disablement 

Disablement is where the immobilization hardware is forced into an immobilization state to ensure the vehicle cannot be driven. This is used in cases where a vehicle has been stolen or is being driven without authorization. When a vehicle is Disabled, it cannot be de-immobilized, even with a valid driver key, until it is Enabled again.

It is important to note that this can only work if the necessary immobilization hardware has been installed.

There are two events that indicate the Disablement and Immobilization States of the vehicle and together provide a complete picture of the current situation.

Example: 
  1. Disablement command is sent
  2. MHub raises the Vehicle Disabled Event -> This means the MHub received the command and will disable the vehicle once the conditions as set in configuration have been met.
  3. Conditions for Disablement are met, vehicle is Immobilized
  4. MHub raises the Vehicle Immobilization Event -> This means the vehicle has been immobilized and cannot be de-immobilized unit it is Enabled again.

Parameter

Value

Notes

Immobilization->Global Vehicle Disablement Allowed

1

Enables the ability to Disable the vehicle.

Immobilization->Vehicle Disablement Delay

0

This is the number of seconds after the conditions for Disablement has been met before the vehicle is Disabled. It is

important to note that the MHub needs a valid GPS speed for this to work.

Immobilization->Disable Speed Threshold

10

The speed below which the vehicle has to travel to allow Disablement to kick in. This is a safety parameter to ensure a vehicle traveling at high speed is not

Disabled possibly causing an accident

Immobilization->Disable on Ignition OFF

0/1

Controls if the vehicle should be Disabled when ignition is turned OFF.

This happens regardless of the current GPS Speed state.

Immobilization->Disable on Trip End

0/1

Controls if the vehicle should be Disabled when Trip is ended. This

 

 

happens regardless of the current GPS Speed state.

Event Configuration->Vehicle Disabled

 

This event is raised when the Disable Command is received and indicates the intent and not the current state of the vehicle. Thus, if the Disable command

is received the MHub will raise this event immediately.

Event Configuration->Vehicle Immobilized

 

This event is raised when the vehicle is immobilized and indicates the current immobilization and disablement state of

the vehicle.

Typical Wiring

In a typical installation the relay is wired in such a way that it needs to be de-energized for the vehicle to be started. Usually this would mean the Relay coil is drawing current the entire time the vehicle is switched off. However, to account for this the relay is wired to the accessories position on the ignition switch. This means the relay is not drawing any current unless the key has been turned to at least the accessories position. Most relays have a Normally Open (NO) and a Normally Closed (NC) contacts. This simply means the one contact is active when the relay coil is unpowered (NC) and the other (NO) is active when the relay coil is powered.



In the image above you would connect one side of the coil to the vehicle battery and the other side to one of the MHub369s Outputs. When the output on the MHub is activated, it would complete the coil circuit activating the relay which in turn would join the NO and C (or COM or COMMON) terminals.

The device on the vehicle used to immobilize it would be connected between the NC and C terminals. 



The MHub Output wires are Green (Output 1) and Blue (Output 2) and either or both can be configured as Immobilization Output(s) using the configuration parameters as described above.

As an example, setting:
  1. “Inputs and Outputs->Output A Function” to 16 would change Output A which is physically linked to Output 1 to the immobilization output. 
  2. “Inputs and Outputs->Output B Function” to 0 would change Output B which is physically linked to Output 2 to a normal output that can be controlled via a command or a trigger.

    • Related Articles

    • Mhub Diagnostic Utility Manual.

      Kindly see attached, Mhub Diagnostic Utility Manual PDF Table of Contents: Introduction ................................................................................................................... 5 1. Getting Started ...

    • MHub 369 - Device information

      Online Diagnostic https://mojo.r7d.xyz/MHubDiagnostic.html Files attached in this article Manuals: MHub369 Quick Installation Manual V01 MHub369 Technical V01 Firmware: 2025-01-06_102112_MHub369-6-40-V1R2B-RLS_CANDIDATE_9

    • HOW TO INSTALL MHUB ID LICENCE ON MACHINES (PC).

      HOW TO INSTALL MHUB ID LICENCE ON MACHINES (PC). (When they are Invalid). Contents: 1.) Visual of Machine ID....... 2.) Detailed information required.... 3.) Providing correct application version....... 4.) Installation of new license file..... 5.) ...

    • Scope Mhub Diagnostic Utility Remote Connection.

      Scope Mhub Diagnostic Utility Training. Content: 1.1) Opening Mhub Diagnostic Utility application..... 1.2) Device Selection.... 1.3) Remote connection settings.... 1.4) Establish connection to the device..... 1.5) View read the configuration of the ...

    • Updating device Firmware for the HMub 369B/F

      Below is process where you use to update firmware using the "ESP Tool" Step 1: > Log into the URL: https://espressif.github.io/esptool-js/ > Select the baord rate : 115200 >Click Connect Step 2: Select the device on the comport that it is connected ...