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 GV65 Plus 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) Queclink GV50CNA Queclink GL601CEU Queclink GV500CNA Queclink GV501LG Queclink GL533CG Queclink GL601MG Queclink GV50CEU Queclink GV58CG Queclink GL50B Lite Queclink GL33CG Queclink GV75CG Queclink GL320MG

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

Queclink protocol is updated: parsing of GTJDR report of GB130MG device is fixed.

namo

Queclink protocol updated: parsing of GTCIF and GTALM reports of GV350CEU device is fixed.

namo

Queclink protocol updated: parsing of GTCRD report of GV57CEU device is fixed.

namo

Queclink protocol is updated: added new E-GENSET parameters, introduced in the 11.04 firmware version of GV350CEU device.

namo

Queclink protocol in updated: added new parameters that were introduced in the 11.04 firmware version of GV350CEU device under the CAN Report Expansion Mask1

YuryAheichyk

Added CSQ RSSI and CSQ BER data parsing from GV500MA, GB130MG devices
Added RAT and BAND data parsing for GV53MG devices

YuryAheichyk

Added new devices:

YuryAheichyk

Added CSQ RSSI and CSQ BER data parsing from GV53MG devices

EvgenyShatilo

Tacho functionality update: added a mechanism for parsing the tachograph file and dynamic generation of the full file name. The file name is formatted automatically based on the file content. Also, depending on the region, the name format will be changed. Here are some examples of files:

VDO format which applies to all countries except France and Spain:

VU file: M_20250801_1406_LT01STR_VINNUMBER00001001.DDD
Driver file: C_20240808_1228_E_Smith1407_1200000000110200.DDD

C1B, V1B format for France:

VU file: FXX-NNN-ZZ2508011746.V1B
Driver file: FXX-NNN-ZZ2508011746.C1B

TGD format for Spain

VU file: V_1234ABC_E_20250801_1745.TGD
Driver file: C_1200000000110200_E_20250801_1745.TGD

Post scriptum: the tracker at the firmware level can generate a file name, for example: C_20241105_1004_Musterfrau_735_Kristina_735_1220000000735000.DDD. The file parsing mechanism that was added improves this functionality and generates a completely correct file name that meets all standards regardless of the file type or tachograph generation. If for some reason the file cannot be read, the default file name will be used automatically.

YuryAheichyk

Fixed GTSTC, GTBPL, GTMSA, GTLSA reports parsing from TMR100MG devices

EvgenyShatilo

Tacho functionality update: Fixed file name formatting.

fixed a problem where an incomplete file name was registered, for example: DRIVERNAME_DRIVERID00000000001.ddd instead of the full name: "C_20250820_1023_S_LASTNAME_DRIVERID00000000001.ddd". The problem was that if the driver has a double last name or if the last name is written in a file as a double last name, for example "SURENAME/SURENAME", the server cut the file name to the "/" character because such a character is not allowed in a file name and is prohibited in most versions of operating systems, such as MacOS and Linux, and is not always correctly detected in Windiws. Now such a symbol is cut at the parser level, so if the driver has a double surname, the full file name will look like this: "C_20250820_1023_S_SURENAMESURENAME_DRIVERID00000000001.ddd".
The problem of registering an incorrect extension for the regions of France and Spain has been fixed. Despite the correct definition of the driver's region in the file, the extension was always ddd. Previously it was: V_0001_E_20250812_1235.ddd, now it is: V_0001_E_20250812_1235.tgd.
Fixed the problem of an empty name in a correctly formatted file name, for example: C_20250819_1001___XXX0000003X00001.ddd, will now be C_20250819_1001_S_SURENAME_XXX0000003X00001.ddd. The problem was related to the fact that the fields with the driver's first/last name unloaded from different tachograph standards have an internal flag that specifies the presence and validity of the name, which is now processed correctly.
Added additional check for file extension (ddd, tgd, v1b, c1b), it will always be in lower case so that it is equally well processed by different operating systems and applications.

namo

Queclink protocol is updated: added Network Setup setting (Connectivity tab) for the GB100CG, GB130MG and GL53MG device types.

namo

Queclink protocol is updated: fixed Network Setup setting (Connectivity tab) for Queclink GL520(M) device type.