Queclink protocol is one of the most deeply integrated protocols in flespi telematics hub. Here is a guide how to obtain telematics data from Queclink devices over API . The following devices are supported Queclink GB100 Queclink GB100MG Queclink GB130MG Queclink TMR100MG Queclink GV50 Queclink GV50M Queclink GV53MG Queclink GV55 Queclink GV55N Queclink GV55 Lite Queclink GV55S Queclink GV55W Queclink GV56 Queclink GV57 Queclink GV65 Queclink GV75MG Queclink GV200 Queclink GV300 Queclink GV300CAN Queclink GV300N Queclink GV300L Queclink GV300W Queclink GV320 Queclink GV350CEU Queclink GV350M Queclink GV500 Queclink GV500MA Queclink GV500MAP Queclink GV500N Queclink GV500VC Queclink GV600 Queclink GV600M Queclink GV600MG Queclink GV620MG Queclink GV75 Queclink GV75W Queclink GV800 Queclink GMT100 Queclink GMT100N Queclink GMT200 Queclink GL50B Queclink GL50MG Queclink GL53MG Queclink GL100 Queclink GL100M Queclink GL200 Queclink GL300 Queclink GL300A Queclink GL300M Queclink GL300N Queclink GL300L Queclink GL300W Queclink GL300VC Queclink GL310M Queclink GL320M Queclink GL500 Queclink GL500M Queclink GL500N Queclink GL501M Queclink GL502MG Queclink GL505 Queclink GL520(M) Queclink GL521M Queclink GL530(M) Queclink GL530MG Queclink GT300 Queclink GS100 Queclink GT301 Queclink CV100LG Queclink GV58CEU Queclink GV355CEU Queclink GV310LAU Queclink GV58LAU Queclink CV200 Queclink GV305CEU Queclink GV57CEU Queclink GV57MGP Queclink GL53MGP Queclink GV500CG Queclink GV50CG Queclink GB100CG Queclink SC350M Queclink T-Panel(ZK601)

GTMAI report is supported. This report is sent to backend server when analog input voltage enters predefined alarm range. To configure alarm parameters of analog input ports use AT+GTMAI command. Applicable for Queclink GV200 device.

GTLOC packet is supported. This packet contains device real time position and is sent to the server after long press of a Function Key button. Function Key should be previously configured to work in Location mode by AT+GTFKS command. Applicable for Queclink GL300M device.

New device supported: Queclink GV50M

GTDRM packet is supported: device removal alarm. To enable this alarm use command AT+GTCFG with bit 17 of Event mask activated. Applicable for Queclink GV50 device.

GTIFG report parsing fixed for Queclink GMT200 devices.

GTLBS packet is supported for Queclink protocol.

New device supported: Queclink GL50B Parsing of GTSTR and GTCTN packets is fixed for this device type.

GTAIF report parsing fixed for Queclink GL300M devices.

GTBPL report parsing fixed for Queclink GL520 and GL530 devices.

Queclink protocol updated: Device type GL100 is renamed to GL100M (changes was automatically applied to all existing GL100 devices) GL100 legacy device type is added for queclink protocol (this device has different messages format - messages end with '\0' character)

[Changelog] queclink protocol

namo

namo
The update postponed till tomorrow, 2020-09-02 12:00 UTC

namo

namo
Queclink protocol is updated to new parsing engine

namo

New device type added for Queclink protocol GB100MG

namo

A significant improvement has been introduced for Queclink protocol.
From now on, if device sends multiple positions in one packet - all positions will be registered as separate channel messages. Before the update only the last position was registered.
For example, packet:
+RESP:GTFRI,490501,111111111111111,MY_DEVICE,0,0,3,1,61.2,267,95.6,13.615221,44.925836,20200928151148,0222,0010,522D,C294,337.0,1,55.9,266,97.3,13.615022,44.925828,20200928151149,0222,0010,522D,C294,337.1,1,37.3,267,99.4,13.614588,44.925812,20200928151152,0222,0010,522D,C294,337.1,90,20200928151153,0C12$

will result into the following messages registered

[
  {
    "device.self.name": "MY_DEVICE",
    "gsm.cellid": 49812,
    "gsm.lac": 21037,
    "gsm.mcc": "0222",
    "gsm.mnc": "0010",
    "ident": "111111111111111",
    "message.buffered.status": false,
    "position.altitude": 95.6,
    "position.direction": 267,
    "position.hdop": 1,
    "position.latitude": 44.925836,
    "position.longitude": 13.615221,
    "position.speed": 61.2,
    "position.timestamp": 1601305908,
    "report.code": "GTFRI",
    "report.reason": 0,
    "server.timestamp": 1601363656.642626,
    "timestamp": 1601305908,
    "vehicle.mileage": 337
  },
  {
    "device.self.name": "MY_DEVICE",
    "gsm.cellid": 49812,
    "gsm.lac": 21037,
    "gsm.mcc": "0222",
    "gsm.mnc": "0010",
    "ident": "111111111111111",
    "position.altitude": 97.3,
    "position.direction": 266,
    "position.hdop": 1,
    "position.latitude": 44.925828,
    "position.longitude": 13.615022,
    "position.speed": 55.9,
    "position.timestamp": 1601305909,
    "report.code": "GTFRI",
    "server.timestamp": 1601363656.642626,
    "timestamp": 1601305909,
    "vehicle.mileage": 337.1
  },
  {
    "battery.level": 90,
    "gsm.cellid": 49812,
    "gsm.lac": 21037,
    "gsm.mcc": "0222",
    "gsm.mnc": "0010",
    "ident": "111111111111111",
    "position.altitude": 99.4,
    "position.direction": 267,
    "position.hdop": 1,
    "position.latitude": 44.925812,
    "position.longitude": 13.614588,
    "position.speed": 37.3,
    "position.timestamp": 1601305912,
    "server.timestamp": 1601363656.642626,
    "timestamp": 1601305913,
    "vehicle.mileage": 337.1
  }
]

namo

New setting added for Queclink GV300, GV300N, GV300W, GV300CAN devices - Data Transmission, Actions tab:

This setting should be used to transfer data between the backend server and the external equipment connected to the seconds serial port of the device.

namo

New device added: Queclink GS100

namo

Queclink protocol updated, the following reports are refactored: GTEPS and GTAIS.
Now parameter voltage.range.status is registered for these reports to indicate the state of voltage relative to predefined voltage range:

voltage.range.status=false is registered if current voltage is outside the predefined range
voltage.range.status=true is registered if current voltage is inside the predefined range

namo

The following change in parameter name is introduces for Queclink protocol:

parameter secondary.battery.charge.status has been renamed into battery.charging.status

For the sake of backward compatibility both old and new parameter will be registered during the next week. The old parameter will be removed 29-Oct-2020.

This change is applicable for GTINF report.

namo

namo
Old parameter is removed from Queclink protocol

namo

New device added: Queclink GL501M

namo

HEX protocol format is supported for Queclink GS100

Device can be switched to HEX protocol with the Protocol Format field of Backend Server Setup setting, Connectivity tab.

HEX reports composition can be configured with Hex Report Mask setting, Configuration tab:

namo

namo
Support of HEX protocol format will be removed from Queclink protocol tomorrow, 1st of July 2022.
We decided to abandon maintenance of HEX protocol format because it has limited applicability (only for Queclink GS100 device model).
Analysis of our internal logs shows that HEX protocol format is not used by flespi users.
Anyway, you may switch your devices to ASCII protocol format with Backend Server Setup setting, Connectivity tab.

baja

engine.ignition.status parameter registration added for virtual ignition reports GTVGN - (Virtual Ignition ON = true), GTVGF (Virtual Ignition OFF = false).

namo

Queclink protocol is updated:

GTASS report "Ambient light alarm" is supported
for GTTEM report "Temperature alarm" parameter temperature.alarm.type.enum is renamed to alarm.type, that will have one of the following numeric values:
1 - below lower limit, 2 - between lower and upper limit, 3 - above upper limit
Both old and new parameters will be registered until 25-Jan-2021.
Starting from 25-Jan-2021 parameter temperature.alarm.type.enum won't be registered any longer.

Both changes are applicable for Queclink GL300A device.

namo

New settings for digital outputs manipulation are added for Queclink GMT100 and Queclink GMT100N devices, at Input/Output tab:

Output 1
Cut Relay

namo

namo
Ouptut control settings are added also for Queclink GV300W device, Input/Output tab.

namo

Queclink GV350M - added parsing of Bluetooth Accessories fields for GTERI report.
Bluetooth accessories data is registered into ble.beacons parameter as json array, for example:

  "ble.beacons": [
    {
      "battery.voltage": 3.528,
      "humidity": 23,
      "id": "7776665554443",
      "index": 0,
      "model": "WTH300",
      "status": true,
      "temperature": 20.7
    }
  ]

namo

Queclink protocol is updated: secondary.battery.level parameter is replaced by battery.level.

For the sake of backward compatibility Backup Battery Level field of GTERI and GTFRI Queclink reports will be registered into both secondary.battery.level and battery.level parameters until 27-April-2021.
27-April-2021 secondary.battery.level parameter will be removed.

namo

Queclink protocol is updated:
parsing of optional 1-Wire Data and CAN Data parameters of GTERI report is implemented for GV300 and GV300W devices.

namo

New Queclink device is supported: GL50MG

namo

GTDAR and GTDAM reports are supported for queclink protocol.
Applicable for Queclink GV300W device.

Along with standard position and GSM parameters, the following flespi parameters are registered for those reports:

GRDAR - driver assistance system warnings report:

fatigue.warning.type - Warning Type: 1 - fatigue driving, 2 - calling, 3 - smoking, 4 - distraction, 5 - statistics report
fatigue.driving.status=true is registered additionally when fatigue.warning.type is 1
fatigue.severity - Fatigue Degree: severity of the issue from 0 to 10
fatigue.warning.count - Fatigue driving warnings counter
calling.warning.count - Calling warnings counter
smoking.warning.count - Smoking warnings counter
distraction.warning.count - Distraction warnings counter

GTDAM - driver assistance system multimedia report:

image.id - Multimedia ID
event.enum - Event ID
image.timestamp - Multimedia time
image.frames.total - Total frames
image.frame.seqnum - Current frame index
payload.length - Multimedia data length
payload.hex - Multimedia data