• namo

  • Post #84

Queclink protocol updated:

  • fixed parsing of GTFRI report with multiple positions for GL320M
  • for GTIDA report field ID Report Type is now registered as parameter ibutton.authorized.state with possible values 0, 1 or 2, instead of boolean parameter ibutton.authorized.status. Applicable for all Queclink devices that can send GTIDA report.
9 days later

  • namo

  • Post #85

Queclink protocol is updated, the following changes are introduced:

  1. from now on command acknowledgement packets +ACK:GTXXX won't be registered as channel messages.
    Applicable for all Queclink devices.

  2. Setting "Data Transmission" (Actions tab) is refactored.
    Applicable for the GV300, GV300N, GV300L, GV300W, GV300CAN devices.

Now "Data Transmission" has the following fields:

  • Data - data to be transferred to equipment connected to the serial port of the device
  • Send data without CRLF - enable this option to send data to serial port without CRLF characters
  • Command ACK - enable/disable command acknowledgement +ACK:GTDAT from device.
    If this option is enabled - command will be marked es executed when acknowledgement message +ACK:GTDAT is received from the device.
    If this option is disabled - command will be marked as executed when +RESP:GTDAT report is received from the device, and data received from the equipment connected to the serial port of the device, will be stored into the response field of command result, as well as into payload.text parameter of GTDAT channel message.
20 days later

  • namo

  • Post #86
  • Edited

Queclink protocol updated.

Added custom command what allows to send any arbitrary text to the device: the text specified in payload parameter will be sent to the device as is.

The command has boolean parameter wait_ack that allows to disable waiting for the acknowledgement from the device to finish the command. In the other words, with wait_ack=false, command will be considered as successfully executed once it's sent to the device's connection.

19 days later
7 days later
12 days later
a month later

Queclink protocol updated: now +ACK:GTXXX command acknowledgement is stored as "response" field in the command execution log:
113: channel's command executed or discarded

{
  "address": {
    "ident": "867162027111111",
    "type": "connection"
  },
  "channel_id": 8,
  "event_code": 113,
  "executed": true,
  "id": 7084,
  "name": "at",
  "origin_id": 8,
  "origin_type": 9,
  "properties": {
    "cmd": "GTDAT",
    "password": "gv300",
    "payload": "1,,MYCMD,100,1,,,"
  },
  "response": "+ACK:GTDAT,867162027111111,,FFFF,20220210165847,C17A$",
  "timestamp": 1652103162.013741,
  "transport": "tcp"
}

    The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

      18 days later

      protocol.vesion parameter added to parsing scheme for all device types

        12 days later

        Queclink protocol updated: fixed parsing of GTDTT report (Data Transmission report) with comma-separated data.

        namo
        Queclink protocol updated: parsing of GTDTT report (Data Transmission report) is modified further, so that parsing will be able to process packets with dollar-signs $ inside data sent from the peripheral device.

          13 days later

          Queclink protocol updated: fixed parsing of GTFRI report with multiple positions for Queclink GL320M

          Queclink protocol is updated: parameter position.hdop (GNSS Accuracy field) was skipped if it's value is 0. This is a bug and it's fixed and now position.hdop parameter will be registered if is has valid number value.

            6 days later

            Queclink protocol is updated: added parsing of Battery Voltage field of GTFRI, GTGEO, GTNMR, GTDOG, GTSOS etc reports that was added from the version 2.02 of Queclink GL500M protocol - flespi parameter battery.voltage, volts is registered for this field.

              Queclink protocol is updated: now channel messages won't be registered for reports GTALS, GTALL, GTALC and GTALM. This is done because these reports contain only configuration settings of the device and no telemetry data. That's why channel messages for these reports don't contain any valuable parameters and won't be registered any more.

                • namo

                • Post #100
                • Edited

                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.

                  namo
                  Queclink protocol is updated: HEX protocol format is removed.

                      6 days later

                      • namo

                      • Post #102
                      • Edited

                      Queclink protocol is updated: cornering events are supported for GTHBM report. Now depending on Report Type value the following flespi parameters will be registered:

                      • 0: Harsh braking behavior - harsh.braking.event=true
                      • 1: Harsh acceleration behavior - harsh.acceleration.event=true
                      • 2: Harsh turning behavior - harsh.cornering.event=true
                      • 3: Harsh braking and cornering behavior - harsh.cornering.event=true and harsh.braking.event=true
                      • 4: Harsh acceleration and cornering behavior - harsh.cornering.event=true and harsh.acceleration.event=true
                        6 days later