This page contains detailed information about the Queclink connector service that enables rapid onboarding of Queclink devices into enterprise applications.
19.7position, eventGTGEO, GTFRI, GTPNL, GTNMR, GTRTL, GTDOG, GTLBS, GTSOSGTPNA, GTPFA, GTSTC, GTBTC, GTBPL, GTTEM, GTLTA, GTLSA, GTUPC1.44position, event, obdGTTOW, GTEPS, GTGEO, GTSPD, GTRTL, GTDOG, GTIGL, GTVGL, GTFRI, GTHBMGTPNA, GTPFA, GTMPN, GTMPF, GTBTC, GTSTC, GTSTT, GTPDP, GTIDN, GTSTR, GTSTP, GTLSP, GTBPL, GTIGN, GTIGF, GTVGN, GTVGF, GTIDF, GTUPCGTOBD, GTOER, GTJES17.13position, eventGTPNL, GTTOW, GTAIS, GTDIS, GTIOB, GTFRI, GTSPD, GTRTL, GTDOG, GTIGL, GTEPS, GTSOSGTPNA, GTPFA, GTMPN, GTMPF, GTBTC, GTSTC, GTSTT, GTPDP, GTIDN, GTSTR, GTSTP, GTLSP, GTIGN, GTIGF, GTVGN, GTVGF, GTIDF, GTUPC17.14positionNONEQueclink ASCII to Azure IoT Hub solution template.metric or imperial units depending on your needs.The Queclink Connector enables your account to receive data from Queclink devices.
imperial or metric, determines the units for any speed, distance, and temperature values that are in the packets received form the devices.You need to define an endpoint for each device that you wish to connect. The endpoint has no special configuration parameters, and the key must be the either the name or imei of the device depending on the device configuration.
imperial or metric, determines the units for any speed, distance, and temperature values that are in the packets received form the devices.This event fires anytime a position, event, or obd report is received by the server.
Important Notes
location field will not be present.{
"remoteAddr": "4.3.2.1:12314",
"report": {
"deviceType": "GL500M",
"packetType": "position",
"messageType": "GTNMR",
"messageTypeDetail": "Movement",
"name": "015425000xxxxxx",
"protocolVersion": "1.23",
"firmwareVersion": "19.7",
"reportType": "motion",
"location": {
"accuracy": 1,
"altitude": 13,
"speed": 0,
"heading": 0,
"latitude": 26.379317,
"longitude": -80.179491,
"ts": "2021-05-14T14:17:49Z"
},
"network": {
"mcc": "310",
"mnc": "410",
"lac": "372d",
"cellId": "0a6bbc10",
"rssi": -103,
"ber": 0
},
"battery": 70,
"mode": "psm",
"motion": false,
"motionStatus": "no-motion",
"temperature": 26.6,
"updateResult": "downloading",
"updateUrl": "https://bridge-us.tartabit.com/...",
"ts": "2021-05-14T14:17:53Z"
},
"raw": "<base64 encoded raw packet>"
}
{
"remoteAddr": "4.3.2.1:12314",
"report": {
"deviceType": "GV500MAP",
"packetType": "position",
"messageType": "GTFRI",
"messageTypeDetail": "Fixed Interval",
"name": "861971050041292",
"protocolVersion": "1.0",
"firmwareVersion": "1.44",
"obd2": {
"connected": true,
"protocol": "iso15765",
"vin": "SADCM2FVXJA2xxxxx",
"voltage": 12.75,
"engineRpm": 0,
"engineCoolantTemperature": 78,
"speed": 44,
"fuelLevel": 0,
"fuelConsumption": 76,
"dtcCount": 0,
"dtcClearedDist": 12311,
"milStatus": false,
"milActivatedDist": 0,
"throttle": 12,
"engineLoad": 22,
"journey": {
"fuelConsumption": 10,
"maxRpm": 5400,
"avgRpm": 1800,
"maxThrottle": 90,
"avgThrottle": 32,
"maxLoad": 100,
"avgLoad": 36,
"mileage": 132
}
},
"location": {
"accuracy": 3,
"altitude": 37,
"speed": 0,
"heading": 85,
"latitude": 26.379403,
"longitude": -80.179445,
"ts": "2021-05-14T14:48:07Z"
},
"network": {
"mcc": "310",
"mnc": "410",
"lac": "372b",
"cellId": "0a731811"
},
"motion": false,
"motionStatus": "ignition off rest",
"ignition": false,
"ignitionDuration": 12,
"offDuration": 0,
"idleDuration": 0,
"externalPowerVoltage": 12.75,
"currentMileage": 2.1,
"totalMileage": 5,
"currentHourMeter": 0,
"totalHourMeter": 0,
"updateResult": "downloading",
"updateUrl": "https://bridge-us.tartabit.com/...",
"ts": "2021-05-14T14:50:32Z"
},
"raw": "<base64 encoded raw packet>"
}
position, event, or obd.GV500 only)
GL500 only)GL500 only)GV500 or GV600 only)GV500 or GV600 only)GV500 or GV600 only)GV500 or GV600 only)GV500 or GV600 only)GV600 only)GV600 only)GV600 only)GV500 or GV600 only)GV500 or GV600 only)GV500 or GV600 only)GV500 or GV600 only)GL500 only)The ack event is fired any time an acknowledgement is received from the device. This usually is to complete a request made through the queclink.queue() command.
{
"command": "AT+GTGEO=gl500m,1,3,-75.635354,45.448743,50,,,,,,,,,,$",
"status": "delivered",
"context": <varies>
}
delivered.var options = {
context: { <custom> }
}
This function queues a command to be delivered to a device after the next time it communicates. When the server receives an acknowledgement from the device it will generate a queclink-ack event so you know your command was successful. In addition, the server will try up to 3 times to deliver the message within a 30 day period before abandoning it.
// Send a command to store a geofence
queclink.queue('8911231231234915','AT+GTGEO=gl500m,1,3,-75.635354,45.448743,50,,,,,,,,,,$')
Commands must end with a
,$and not include a command number.
The IoT Bridge can be used to update the configuration of Queclink devices over the air by dynamically building the configuration file to be sent to the devices. To use this feature you need to use the HTTP service to create a handler to retrieve the files.
Queclink Configuration OTA templateDownload URL should be: http://bridge-us.tartabit.com/webhook/<secret>/Handle Queclink configuration updates to suit your needs.You may wish to dynamically create the configuration based on external information, such as information from an Azure IoT Hub Device Twin or from a 3rd party HTTP(s) service. You can build the configuration on the fly within the trigger to return it to the client by retrieving other data and building the configuration string on the fly.
The following events are considered billable:
It is advisable to configure your devices to use the IMEI as the name (name mask value of 0) to ensure uniqueness, if you manually supply the name, it must be unique, if another account uses the same name you will not be able to define the endpoint.
Use of devices or versions that are not mentioned in the features section is not recommended.