• baja

  • Post #11

Bugfix. Though the timestamp in Morey protocol is integer it caused merging of the messages with the same timestamp on the device storage level.
New parameter timestamp.key added which is timestamp + report.seqnum * 0.00001 . This parameter is used as secondary key in device messages database, thus messages with the same timestamp but different report.seqnum won't be merged.

a month later
6 days later

Morey protocol is updated:

EID 0x016 External Power Voltage is now registered into parameter external.powersource.voltage, volts

The parameter was renamed in order to avoid confusion with EID 0x12A Internal Battery Voltage, which is registered into parameter battery.voltage, volts

    22 days later

    • namo

    • Post #14
    • Edited

    Morey protocol is updated: added support of message type 0x0D BLE Advertisement report.
    Report contains information about several BLE beacons, that are stored into ble.beacons array, e.g.:

    {
  "ble.beacons": [
    {
      "ad.count": 182,
      "ble.event": 3,
      "emerge.timestamp": 1648077900,
      "id": "5B568A17D90E",
      "last.ad.timestamp": 1648078061,
      "payload.hex": "1EFF0600010920027AEC930CE3B5A4B11F8BCCE9D2F28415BFBF79BD70EBFE",
      "rssi": -50
    },
    {
      "ad.count": 252,
      "ble.event": 3,
      "emerge.timestamp": 1648077901,
      "id": "8F061EBD130B",
      "last.ad.timestamp": 1648078337,
      "payload.hex": "1EFF0600010920029FB2D0DAA114E3AE6B6A4866ED50D2E8D47D549D12BB41",
      "rssi": -88
    },
    {
      "ad.count": 312,
      "ble.event": 1,
      "emerge.timestamp": 1648077901,
      "id": "A6DDF02A7E66",
      "last.ad.timestamp": 1648078967,
      "payload.hex": "02011A020A0C0BFF4C00100605199B093708",
      "rssi": -86
    }
  ],
  "channel.id": 166,
  "ident": "1234",
  "peer": "127.0.0.1:47316",
  "protocol.id": 73,
  "server.timestamp": 1649832680.059862,
  "timestamp": 1649832680.059862
}

    Mapping of BLE beacon's fields to flespi parameters is below:

    • ID - id
    • RSSI - rssi
    • Time this node came in view - emerge.timestamp
    • Time of this nodes most recent advertisement - last.ad.timestamp
    • Count of advertisements since in view - ad.count
    • Payload of most recent advertisement - payload.hex
    • BLE Now Entered / Exited / Updated - ble.event
    4 months later

    Morey protocol is updated: added EID 0x126 Asset Operational State - flespi parameter asset.operational.status

      20 days later

      Morey protocol is updated: fixed parsing of message type 0x0D BLE Advertisement

        5 months later
        a month later

        • shal

        • Post #18

        Morey protocol is updated:

        • added EID 0x026 Instantaneous Fuel Economy - flespi parameter can.fuel.economy;
        • added EID 0x024 Engine Crankcase Pressure - flespi parameter can.engine.crankcase.pressure;

        • shal

        • Post #19

        Morey protocol is updated: all CAN parameters with unreadable values (0xFF, 0xFFFF, 0xFFFFFFFF) are removed from message. Parameter fuel.consumed renamed to can.fuel.consumed.

        a month later

        Morey protocol is updated: Added parsing for EIDs 0x3EB ... 0x3EE with Log Entry Data Elements

          13 days later

          Morey protocol is updated: Added parsing for EIDs 0x0D0 ... 0x0DB and 0x0CC ... 0x0CF with parameters script.uint32.variable.5 ... script.uint32.variable.16 and script.int32.variable.5 ... script.int32.variable.8

            6 months later

            • kial

            • Post #22
            • Edited

            Breaking change of the morey protocol scheduled for the next Thursday, October 19.
            Due to an implementation bug the position.speed parameter contains speed value in cm/sec, but that standard parameter should be in km/h. That will be fixed next Thursday, October 19.

            Currently we have added a temporary parameter named "ref.position.speed.kmph" containing vehicle speed in km/h units. That parameter will be deleted with the bug fix on the next Thursday, October 19.

            Please concat us if you need more time to prepare for this change, or if you need help with plugin creation that can convert speed parameter units.

              7 days later

              • kial

              • Post #23

              position.speed parameter units changed from cm/sec to km/h as mentioned in kial

                  3 months later

                  Indexed parameter can.j1708.dtc.{index} parsed from ID 0x05E from renamed to can.obd.dtc.{index}

                    a month later

                    Fixed log.transaction.flags.name parameter parsing from 0x3ED EID

                      3 months later

                      parameter renaming announcement which will happen in a week (May 22):
                      parameter total.idle.seconds will be renamed to total.idle.time

                        Write a Reply...