In cases where the extended driver ID is used for driver identification but no match is found, extended config driver list users can choose to enable the setting: Unknown Extended Driver IDs will disarm unit, and be matched to a known driver during the data download.
If this is checked the driver can disarm the vehicle and at the end of the trip when the trip is processed, the system will check if the driver is an existing driver in MiX Fleet Manager and all passive data will be matched and associated to a known driver during the data download.
First ensure that the following are checking in organization settings:
- Click Manage.
- Under Operations, click Organization settings.
- Click on the Driver defaults tab on the left.
- Make sure the
- Click Save.
After linking an extended driver ID to a driver remember to load the driver to the asset's config.
Set the asset's asset control to All new drivers in this organization may operate this asset and select the driver you linked to the extended driver ID as the default driver.
You can now connect the extended driver ID reader to the MiX 4000 unit via the mobile device template on the serial port.
- Click Manage.
- Under Config admin, click Templates.
- Click the Mobile device templates tab on the left.
- Search for the relevant template and select Edit.
- Open the mobile device properties.
- Connect the Extended Driver ID reader to the MiX 4000 unit via the mobile device template on the serial port.
- Click Save.
- Check the “Unknown Extended Driver IDs will disarm unit, and be matched to a known driver during the data download” checkbox.
- Enter the “Duration until extended id is cleared”. This is the grace period that the mobile device will keep the extended driver ID before assuming that the card has been removed from the reader.
- Click Save.
- Compile and upload config.