the approved list. Driver IDs previously approved can be removed from the approved list
by the host.
If there are no communications with the host server, approved Driver IDs will allow the
vehicle to be started and declined Driver IDs will not allow the vehicle to be started.
Unknown Driver IDs will be temporarily allowed to start the vehicle and approval will be
requested as soon as communications resume. If declined at that point, the vehicle will
be immobilised.
If the approved list becomes full and a new Driver ID is presented and authorised, the
oldest Driver ID will be removed from the list to make room for the new one. The oldest
Driver ID is based on the last time that the Driver IDs were presented, so regularly used
Driver IDs should never be removed from the approved list.
The device can re-request authorisation from the server of all Driver IDs in the approved
list periodically.
In the command descriptions the <family-code> and <serial-number> are formatted as
follows:
Argument
Format
<family-code>
Driver ID family code, fixed length, 2 hexadecimal digits (leading
zeros), e.g. 01. For Bluetooth Driver IDs the <family-code> is always
00.
<serial-number> Driver ID serial number, fixed length, 12 hexadecimal digits (leading
zeros), e.g. 0000125408C9
The following table describes the commands. The first command is from device to host
whilst the rest are from host to device.
Command
Description
$DRID,<model>,CHECK,<imei>,<family-code>,
<serial-number>
Device requests Driver ID
authorisation from host
$DRID,<model>,CHECK,<imei>,00,<serial-number>,
<bluetooth-device-name>
Device requests Driver ID
authorisation from host
(Bluetooth only)
$DRID,APPROVE,<family-code>,<serial-number>
Host approval of Driver ID
$DRID,DECLINE,<family-code>,<serial-number>
Host declines Driver ID
(unknown)
$DRID,ADD,<family-code>,<serial-number>
Host request to add Driver ID to
approved list
$DRID,REMOVE,<family-code>,<serial-number>
Host request to remove Driver
ID from approved list
$DRID,CLEAR
Host request to delete approved
and declined list
$DRID,CLEAR,WHITE
Host request to delete approved
list
$DRID,CLEAR,BLACK
Host request to delete declined
list
$DRID,BLOCK,<family-code>,<serial-number>
Host request to add Driver ID to
declined list
$DRID,VERIFY,<hours>
Host request to set the device
whitelist verification period (0-
65535). 0 disables the request
For example:
$DRID,AT200,CHECK,351777042187300,01,0000125408C9
For Bluetooth Driver IDs the CHECK command uses family code 00 and has an extra field
<bluetooth-device-name> at the end.
