• namo

  • Post #2

Meitrack protocol updated: CCE command type is supported.
This is applicable for P99G, TC68S and other devices.

    18 days later

    CCC command type is supported for meitrack protocol.
    This is applicacle for Meitrack T322X device type.

      • namo

      • Post #5

      Parameter ID 0x40 New event code is supported for CCE command type.
      Applicable for Meitrack TC68S

        E91 command type is supported for meitrack protocol: read device's firmware version and serial number.

        Firmware version and serial number are stored in Device Information setting, Info tab:
        device_info

        New parameters IDs are supported for CCE command type:

        • 0x92 - can.wheel.speed
        • 0x99 - can.engine.rpm
        • 0x9C - can.engine.coolant.temperature
        • 0xC9 - can.fuel.consumption.distance

        Applicable for Meitrack TC68S

        Parameter ID 0x4A is supported for CCE command type: additional info about the ignition off event.
        The information is registered in the following parameters:
        trip.mileage
        trip.duration
        trip.average.speed
        trip.max.speed
        Applicable for Meitrack TC68S

          a year later
          a year later

          • namo

          • Post #10

          Meitrack protocol is updated: fixed parsing of wifi.signal.strength parameter.

          3 months later

          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)

            a month later

            • namo

            • Post #12
            • Edited

            Meitrack protocol is updaed:

            1. New device model is supported: Meitrack MD533S
            2. The following parameters IDs are supported for command type CCE:
              • 0x14 Output port status - flespi parameter dout
              • 0x16 Port AD1 analog- flespi parameter ain.1, volts
              • 0x17 Port AD2 analog - flespi parameter ain.2, volts
              • 0x18 Port AD3 analog - flespi parameter ain.3, volts
              • 0x41 Port AD6 analog - flespi parameter ain.6, volts
              • 0x49 - flespi parameters camera.status.1, boolean - camera.status.64, boolean, depending on the number of cameras that device supports. For example, if device supported 2 cameras, then there will be 2 parameters registered camera.status.1 and camera.status.2
              13 days later
              2 months later

              The following parameters IDs are supported for command type CCE:

              • 0x97 - Accelerator pedal position saved as parameter can.throttle.pedal.level
              • 0x98 - total fuel consumption saved as parameter can.fuel.consumed
              • 0x9A - Total engine run time saved as parameter can.engine.motorhours
              • 0x9D - CAN bus fuel level saved as parameter can.fuel.level
              • 0x9E - Actual engine torque saved as parameter can.engine.torque.level
              • 0xA1 - Actual engine torque at current speed saved as parameter can.engine.torque.current.speed.level
              • 0xA2 - Fuel consumption rate saved as parameter can.fuel.consumption
              • 0xA5 - Instantaneous fuel consumption saved as parameter can.fuel.economy
              8 days later

              • namo

              • Post #17

              Meitrack protocol is updated: the following CAN parameters are added for command type CCE:

              • 0x93 - Clutch switch - flespi parameter can.pedal.clutch.status
              • 0x95 - Parking Brake Switch - flespi parameter can.handbrake.status
              • 0x96 - Cruise control - flespi parameter can.cruise.status
              8 days later

              • shal

              • Post #18

              For Meitrack T-366 and T-366G devices the parsing of analog input value has been fixed.
              New parameters battery.voltage and external.powersource.voltage may present in the telemetry message from now while ain.X parameters with previously incorrect values are not more available.

              4 days later

              • namo

              • Post #19

              Meitrack protocol is updated:

              1. Param ID 0x25 RFID number of Command type CCE is supported - flespi parameter rfid.code is registered
              2. Command type CFF (Deleting an Event in the Buffer) is supported
              3. Command type value is now registered into report.code flespi parameter

              • namo

              • Post #20

              Meitrack protocol is updated: fixed parsing of Param ID 0X0E Base station info of CCE command type. 2 bytes <RX_LEVEL> are now parsed as signed integer (flespi parameter gsm.signal.dbm)