Bluetooth Configuration (BLTC)
To configure Bluetooth features use command:
$BLTC,<min_rssi>,<scan_period>
Where
<min_rssi> 0-127 The lower the number the stronger a signal has to be to be
accepted (default 75)
<scan-period> range 10-60 seconds (default 30)
The <driver_id_source> must be set to 3 in the DRIC command to enable Bluetooth.
BLUETOOTH PAIRING:
Bluetooth devices can be ‘seen’ without pairing, but we recommend pairing to speed up
device detection. When <driver_id_source> is set to 3, a Bluetooth a device may be
paired at any time.
To pair your bluetooth device with the AT200, initiate a bluetooth device search from your
mobile phone handset whilst in close proximity to the AT200, select the device ‘AT200’
and enter the PIN code 0000 when prompted.
If DRIC <server_authorisation> is set to 0 the paired device is immediately added to the
whitelist. If DRIC <server_authorisation> is set to 1 the paired device is added to the
whitelist only if it is accepted by the server.
SELECTION CRITERIA / PRIORITIES FOR BLUETOOTH DEVICES:
When the vehicle ignition is switched on, bluetooth devices will be scanned and
considered in range if the received signal strength is a lower value than the BLTC
<min_rssi> setting (note that <min_rssi> is in –dBm, hence lower values are stronger
signals). Paired devices will automatically reconnect each time they are in range. The
AT200 will select bluetooth devices for use with driver ID based on the following priority:
1. Paired devices
2. Device IDs in whitelist
3. Strongest ID in view
During a journey (ignition on) the bluetooth device scan will be repeated periodically until
a device in range is found and the bluetooth device ID reported according to the DRIC
options.
If the <immobilisation> option in the DRIC command is set then the authorised driver ID
whitelist will be used to turn off immobilisation.
Driver ID Server Authorisation (DRID)
Host server authentication / authorisation for driver IDs can be enabled using the DRIC
command (see above). When enabled, the AT200 will store a list of up to 10 approved
Driver IDs and up to 10 declined Driver IDs. The source of the Driver ID is set using the
DRIC command.
Each time a 'new' Driver ID is read (i.e. not currently in the approved list), the device will
query the host server for approval to accept the new Driver ID. This process should take
approximately 10 seconds. Driver IDs approved by the host will be added to the
approved list and when presented again in the future they will be immediately authorised
by the device.
Driver IDs that are declined will not be added to the approved list and will not allow the
vehicle to be started. These are stored in a declined list. Declined Driver IDs send a
query to the host so that if they are changed to approved in future they will be added to