namo
Queclink protocol is updated to new parsing engine

    9 days later

    New device type added for Queclink protocol GB100MG

      13 days later
      • Edited

      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$

      [
        {
          "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
        }
      ]
        8 days later
        • Edited

        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.

        6 days later
        6 days later

        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

        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.

        7 days later

        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:

        a month later

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

          a month later
          • Edited

          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.

          2 months later
          5 days later
          7 days later
          • Edited

          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
              }
            ]
          a month later

          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.

          20 days later

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

          2 months later
          9 days later

          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
          2 months later

          Asset tracker Queclink GL501M gained new configuration settings that can be found at Configuration tab:

          • Device Parameters - device password and name

          • Tracking Parameters - various options to configure power saving mode and data sending frequency for the tracker