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

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

YuryAheichyk

fixed GTPGR report parsing

YuryAheichyk

Fixed GTCAN report parsing from GV300N devices

YuryAheichyk

Updated GTERI report parsing from Gl320M to version 3.03

YuryAheichyk

Added Driving Behavior Alarm, Speed Alarm, Tow Alarm, Crash Alarm settings for GB100CG

YuryAheichyk

Fixed +ACK:GTBID report parsing from GL521M devices

baja

Request position action setting was added to GV300 series, GL320M, GV500MA, GB130MG, GL30MG.
For GV53MG model the setting also accepts timeout to wait for GNSS initialization field.

YuryAheichyk

Fixed GTFRI report parsing from GV56 according to the 13.06 protocol version

YuryAheichyk

Fixed +ACK:GTBID and +ACK:GTHUM report parsing from GV56

YuryAheichyk

Fixed GTBID and GTERI report parsing from GV355CEU

YuryAheichyk

Added new device Queclink SC350M

YuryAheichyk

Protocol parsing for SC350M device updated to version 1.07

YuryAheichyk

Fixed Serial Number field parsing in GTPIC, GTSOD, GTRFQ, GTVDO reports

YuryAheichyk

Fixed position.speed parsing in the GTFRI report from GL320M devices. If speed equals -1, movement.status = false, and position.speed = 0 register, according to the protocol documentation.

YuryAheichyk

Fixed GTBID report parsing from GV620MG devices

YuryAheichyk

YuryAheichyk Fixed GTBIE report parsing as well

YuryAheichyk

Fixed GTCAN report parsing from GV355CEU devices

YuryAheichyk

Fixed GTBAA report parsing from GV620MG

YuryAheichyk

Updated CV200 data parser to version 2.17

EvgenyShatilo

Added the ability to remotely download data from a tachograph.

What you need to do to download the file:

Download the Tacho Bridge Application from our repository on github.
Configure according to the instructions.
Send a command to download the file.
Provided that the tachograph and tracker are configured correctly, authentication will be successful and the file will be uploaded to the server.

Note:

Сontinue downloading file after connection loss (temporarily) not supported. If for some reason the device's connection to the server was lost, the server will ignore incoming parts of the file and try to send a command to the device to complete the communication process with Taho. When the device stops the current file upload, the server will send a command to upload the file again (if attempts have not been exhausted).
The functionality of uploading a tachograph file for several devices simultaneously for one company card has not been fully tested due to the lack of physical capability. In case of errors, please contact us in chat

EvgenyShatilo

Improvements to Tachograph Functionality:

Changed the server's reaction to the absence of a 'Tachograph company card number' field in the device configuration. Now it does not cause an error and does not break the connection. Now it causes wanring 'device data processing warning' and the server controls the timeout and the behavior of the tracker. If the configuration is still not corrected, then it soft repeats the command several times, then forcibly completes the authorization process so as not to block the device, otherwise it will not be able to send telemetry messages normally, but will hang on the authorization process.
Other minor improvements to improve stability.