Bluetooth features

From Wiki Knowledge Base | Teltonika SAS

Proximity with GH5200 Quick start guide

Proximity functionality is used to detect personal space violations by measuring RSSI values between GH5200 devices.
More information about how proximity works could be found here.


1. In order to start GH5200 proximity testing you should download testing firmware, configurator and configuration. Contact your sales manager to get Teltonika Drive link for those files.


2. Open configurator and connect GH5200:

First window GH.png



3. Update device with the latest Proximity firmware version:


FW update GH open.png


NOTE! After firmware update – format device memory by pressing Format as shown below. Format button is on "Status" section.

Format GH.png



4. Upload downloaded starting configuration to device:

Cfg upload.png



5. If you plan to use server - configure APN, server address and port. These settings can be found in GPRS section.

Server info GH.png



6. Recommended settings for proximity detection configuration, starting from Bluetooth Features section. In order to use proximity feature, there must be configured Proximity Group ID. Group ID actually defines user groups. If Proximity Group ID value is 0 – device will detect all GH5200 devices which are too close, according to configured RSSI threshold. If device finds another one with the same Proximity Group ID, which value could be from 1 to 255 - alarm will not be triggered, because it means they are in the same group.

Important Proximity parameters in Bluetooth features section:

  • Proximity detection must be Enabled
  • Group ID 0 detects all GH5200 devices
  • Group ID 1 - 255 will not detect those GH5200 devices, which has the same Group ID
  • Recommended Proximity RSSI: -54


NOTE! Proximity feature could be disabled or enabled while device is charging. Just click Disable/Enable on Proximity while charging option.

Settings proximity feature.png



Important Proximity parameters in Bluetooth 4.0 section:

  • Recommended Update Frequency: 3
  • Recommended BLE Scan duration: 3
  • Recommended BT Power Level: 6

NOTE! Higher Update frequency/BLE Scan Duration value will cause longer delay of Proximity detection.

BLE.png



7. Indication of the Proximity Pre-Alarm and Alarm could be set in User Interface section. It is the same option as Home Zone:

Home zone.png



AVL ID’s and Data Structure


AVL ID 889 record describe the causes of violation:
0 – No violation;
16 - RSSI threshold Proximity violation.

AVL ID 875 record represents device IMEI address which violates personal space.

Example of the IMEI conversion from raw data (HEX) to decimal:

1. HEX -> ASCII (String)
3031343731353942383241454643 -> 0147159B82AEFC
2. HEX -> DEC
0147159B82AEFC -> 359633105628924

AVL ID 890 - Violation time. It's time which counts from getting AVL 889 with value 16 (RSSI threshold Proximity violation) to AVL 889 with value 0 (No violation) of each separate device.

Proximity states:

Proximity States v3.png




Example of the data packet:


When Proximity is violated:

00000000000000548E0100000174D44B614000000000000000000000000000000000036B0004000103791000000001037A0000000000000002036B000E3031343

731353546443338414342037B000C434330324332364131454244010000A1F3

Prox start.png


When violator leaves personal space (end of Proximity violation):

00000000000000548E0100000174D44B74C800000000000000000000000000000000036B0004000103790000000001037A0000000400000002036B000E303134373

1353546443338414342037B000C4343303243323641314542440100006512

Prox end.png




Example of the server view:

Server proximimimimi.png