10 days later

Xirgo-mqtt protocol updated:

Output 1 and Output2, Input/Output tab:

Signal 1 - Signal 5, Actions tab:

9 days later

  • namo

  • Post #3
  • Edited

Xirgo-mqtt protocol updated: new sensor_ids are supported.
Currently mapping of the sensor_id to flespi parameter is the following:

0x0002 - SignalMotion - movement.status
0x0003 - SignalIN6 - din(bit6)
0x0006 - SignalGeozoneInside - geofence.status
0x0008 - SignalGSMJamming - gsm.jamming.alarm.status
0x0010 - SignalIN2 - din(bit2)
...
0x0015 - SignalIN8 - din(bit8)
0x008C - Foot brake signal - can.pedal.brake.status
0x0060 - Armed - armed.status
0x0061 - Locked - locked.status
0x0062 - Front left door - can.driver.door.status
0x0063 - Front right door - can.passenger.door.status
0x0064 - Rear left door - can.rear.left.door.status
0x0065 - Rear right door - can.rear.right.door.status
0x0079 - Sensor_AirBagWarning - can.airbag.fired.status
0x007A - Sensor_CheckEngineWarning - can.check.engine.status
0x007C - Sensor_TirePressureWarning - can.tire.pressure.status
0x0081 - Sensor_ESPWarning- -can.esp.status
0x0085 - Sensor_DriverSeatBeltWarning - can.driver.seatbelt.indicator.status
0x0086 - Sensor_PassengerSeatBeltWarning - can.passenger.seatbelt.indicator.status
0x0094 - Sensor_OUT1 - dout(bit0)
0x0095 - Sensor_OUT2 - dout(bit1)
0x0096 - Sensor_OUT3 - dout(bit2)
0x2000 - GPS_speed - position.speed
0x2007 - Fuel level sensor - fuel.sensor.value
0x200E - Sensor_U8UserDefined3 - sensor.uint8.value.4
0x200F - Sensor_U8UserDefined4 - sensor.uint8.value.5
0x202D - Sensor_Slot1_Activity - tacho.slot.activity.1
0x202E - Sensor_Slot2_Activity - tacho.slot.activity.2
0x3000 - Sensor_VCC - external.powersource.voltage, volts
0x3004 - Sensor_VBAT - battery.voltage
0x300B - Course, degrees - position.direction
0x300C - RPM sensor - can.engine.rpm
0x4003 - Sensor_TotalDistance - can.vehicle.mileage
0x4005 - Sensor_U32UserDefined0 - sensor.uint32.value.1
0x405B - Sensor_Tacho_Odometer - tacho.vehicle.mileage
0xA000 - Sensor_Temperature - onewire.sensor.temperature
0xA001 - Sensor_Acceleration - absolute.acceleration
0xA003 - Sensor_F32UserDefined0 - sensor.float.value.1
...
0xA011 - Sensor_F32UserDefined14 - sensor.float.value.15
0xB002 - Odometer from GPS - vehicle.mileage
0xC000 - Sensor_STRING1 - sensor.string.value.1
0xC001 - Sensor_STRING2 - sensor.string.value.2
0xC002 - Sensor_STRING3 - sensor.string.value.3

  • ysv likes this.
8 days later

  • namo

  • Post #5
  • Edited

xirgo-mqtt protocol update is planned for tomorrow, 11-Dec-2020, 12:00 UTC
Update will introduce changes in channels' configurations.
Short interruptions are expected in the operation of the existing xirgo-mqtt channels.

    namo
    Update installed.

        9 months later

        • namo

        • Post #7
        • Edited

        Dear flespi users,

        As you know, flespi platform is constantly developing and improving in order to bring more qualitative service to all of you.

        As a matter of this course we implemented new xirgo-mqtt protocol instead of the old one (that is now named as xirgo-mqtt-deprecated protocol).
        Channel with the new xirgo-mqtt protocol has an embedded MQTT server inside. This allows you full control on the connections from devices: you may enable TLS encryption, configure your own authentication on the incoming connections, and whitelist the IP addresses allowed to connect to your channel.

        Also, new xirgo-mqtt channel is equipped with TrafficViewer - an indispensable tool for debugging of raw traffic between the channel and connected devices.

        In order to start using this new xirgo-mqtt channel you should:

        • CREATE new channel and select protocol xirgo-mqtt #309.
        • RECONFIGURE the trackers to connect to new MQTT broker - i.e. to the URI of the xirgo-mqtt channel created at the previous step. Please note, that there is no need to keep flespi token at the device any more. You may configure any Username and/or Password on the device, but be aware that they match to those configured in the channel.
        • if you have Xirgo XG3700 devices created in flespi - UPDATE device type to the corresponding device_type_id of the new xirgo-mqtt protocol. For you convenience, the curl commands for the HTTP requests to be executed are given below.
        • when all the devices are successfully connected to the new xirgo-mqtt channel, DELETE the old channel with xirgo-mqtt-deprecated protocol.

        Protocol xirgo-mqtt-deprecated will be removed in a month, 13 October 2021.
        So, we ask you to perform the transition in the nearest future.
        Please, contact us in flespi support chat if you need any assistance from us during this process, or encounter any issue.

        Thank you for the understanding and your readiness to cooperate!

        The commands to change device_type_id are below:

        • Xirgo MQTT (generic) #733:
          curl -X PUT --header 'Authorization: FlespiToken XXX' -d '{"device_type_id":993}' 'https://flespi.io/gw/devices/device_type_id%3D733'

        • Xirgo XG3700 XTCAN SDK #734:
          curl -X PUT --header 'Authorization: FlespiToken XXX' -d '{"device_type_id":994}' 'https://flespi.io/gw/devices/device_type_id%3D734'

        • Xirgo XG3700 LIGHT SDK #739:
          curl -X PUT --header 'Authorization: FlespiToken XXX' -d '{"device_type_id":995}' 'https://flespi.io/gw/devices/device_type_id%3D739'

        • Xirgo XG3700 LIGHT+ SDK #740:
          curl -X PUT --header 'Authorization: FlespiToken XXX' -d '{"device_type_id":996}' 'https://flespi.io/gw/devices/device_type_id%3D740'

        • Xirgo XG3700 STCAN SDK #741:
          curl -X PUT --header 'Authorization: FlespiToken XXX' -d '{"device_type_id":997}' 'https://flespi.io/gw/devices/device_type_id%3D741'

        • Xirgo XG3700 TACHO SDK #742:
          curl -X PUT --header 'Authorization: FlespiToken XXX' -d '{"device_type_id":998}' 'https://flespi.io/gw/devices/device_type_id%3D742'

        Just replace XXX with your flespi token.

        • namo

        • Post #8

        Xirgo-mqtt protocol updated: new sensor_ids are supported.
        New sensor_ids are mapped to flespi parameters is as follows:

        0x006D - Sensor_Ignition - engine.ignition.status
        0x001E - Sensor_SignalIButtonPresent - ibutton.connected.status

          • baja

          • Post #9
          • Edited

          Xirgo-mqtt protocol updated: new sensor_ids are supported.
          New sensor_ids are mapped to flespi parameters as follows:

          0xC016 - Sensor_Driver1_Id - driver.id.1
          0xC017 - Sensor_Driver2_Id - driver.id.2
          0x008B - Sensor_HandBrake - can.handbrake.status
          0x008F - Sensor_CruiseControl -can.cruise.status
          0x2009 - Sensor_FuelLevel2 -fuel.sensor.value[index=2]
          0x200A - Sensor_EngineLoad - can.engine.load.level
          0x2021 - Sensor_adblue_lvl - can.adblue.level
          0x2031 - Sensor_CruiseControlState - can.cruise.state
          0x302D to 0x3031 - Sensor_Axle_weight - can.axle.weight.ID
          0x405C to 0x405D - Slot time from tachograph - tacho.slot.time.ID
          0x405E to 0x405F - Slot distance from tachograph - tacho.slot.distance.ID

          • namo

          • Post #10
          • Edited

          Xirgo-mqtt protocol updated: new sensor_ids are supported.
          New sensor_ids are mapped to flespi parameters as follows:

          0x2037 - Sensor_RetarderTorqueMode - can.retarder.torque.mode
          0x2038 - Sensor_RetarderPercentTorque - can.retarder.torque.load, %
          0x2039 - Sensor_RetarderSelection - can.retarder.selection, %
          0x203C - Sensor_CurrentGear - can.gear
          0x3034 - Sensor_InstantFuelEconomy - can.fuel.economy, km/liters
          0x3039 - Sensor_GrossVehicleWeight - can.gross.combination.vehicle.weight, kg
          0x405A - Sensor_TotalFuelUsedHighRes - can.fuel.consumed.high.resolution, liters
          0x4061 - Sensor_ID_Wiegand26 - wiegand.code
          0x4062 - Sensor_TotalDistanceHighRes - can.vehicle.mileage.high.resolution, km

            • namo

            • Post #11
            • Edited

            Xirgo-mqtt protocol updated: now each record of telemetry data packet is stored as separate channel message with its own timestamp (Please refer Protocol document, section 7.1.1 Telemetry data for more information about records).

            The update is a fix of a bug - previously the whole packet was stored as one channel message, thus losing values of the sensor IDs which was included in a packet multiple times.

            • namo

            • Post #12

            Xirgo-mqtt protocol updated: new sensor_ids are supported.
            New sensor_ids are mapped to flespi parameters as follows:

            0x009E - Sensor_PTOstate - can.pto.status, boolean
            0x3021 - Sensor_Fuel_rate - can.engine.fuel.rate, L/h
            0x5000 - Sensor_Ibutton_ID - ibutton.code, string
            0xC004 ... 0xC006 - Sensor_Script1name ... Sensor_Script3name - script.name.1 - script.name.3
            0xC015 - Sensor_DTC - can.dtc, string
            0x300D ... 0x301C - Sensor_U16UserDefined - sensor.uint16.value.1 ... sensor.uint16.value.16
            0x6000 ... 0x6009 - Sensor_S8UserDefined - sensor.int8.value.1 ... sensor.int8.value.10
            0x7004 ... 0x700D - Sensor_S16UserDefined - sensor.int16.value.1 ... sensor.int16.value.10
            0x8000 ... 0x8009 - Sensor_S32UserDefined - sensor.int32.value.1 ... sensor.int32.value.10

              19 days later

              • namo

              • Post #13
              • Edited

              namo
              Protocol xirgo-mqtt-deprecated is deleted.

                7 days later

                • namo

                • Post #14

                Xirgo-mqtt protocol updated: new sensor_ids are supported.
                New sensor_ids are mapped to flespi parameters as follows:

                0x202C - Sensor_GeozoneID - geofence.id
                0x000B - Sensor_SignalGPRSRegistered - gprs.status, boolean

                2 months later

                • namo

                • Post #15

                Xirgo-mqtt protocol updated: new sensor_ids are supported.
                New sensor_ids are mapped to flespi parameters as follows:

                • 0x2001 Sensor_Satelites (Number of locked in satellites) - position.satellites
                • 0x7000 Sensor_AxesX - x.acceleration, g
                • 0x7001 Sensor_AxesY - y.acceleration, g
                • 0x7002 Sensor_AxesZ - z.acceleration, g
                • 0x7003 Sensor_Altitude - position.altitude, m
                • 0xA002 Sensor_Cornering - turn.acceleration, g
                12 days later

                Xirgo-mqtt protocol updated: new sensor_ids are supported.
                New sensor_ids are mapped to flespi parameters as follows:

                • 0x3022 Sensor_Freq_In2, Hz - sensor.frequency.2, hz
                • 0x3023 Sensor_Freq_In3, Hz - sensor.frequency.3, hz
                • 0x3024 Sensor_Freq_In4, Hz - sensor.frequency.4, hz
                • 0x3025 Sensor_Freq_In5, Hz - sensor.frequency.5, hz
                4 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).

                  3 months later

                  • namo

                  • Post #18
                  • Edited

                  Xirgo-mqtt protocol is updated: maximum allowed length of the payload of custom command is increased up to 2700 characters (previously it was limited to 100 characters).

                  14 days later

                  • namo

                  • Post #19
                  • Edited

                  Xirgo-mqtt protocol is updated: the following Sensor IDs are added:

                  • 0x0067 Sensor_trunk - can.trunk.status
                  • 0x007E Sensor_MasterWarning - can.master.warning.light.status
                  • 0x007F Sensor_ABSWarning - can.abs.failure.indicator.status
                  • 0x0084 Sensor_EPCWarning - can.electronic.power.control.status
                  • 0x3001 Sensor_ADC5 - ain.5
                  • 0x3002 Sensor_ADC4 - ain.4
                  • 0x3003 Sensor_ADC3 - ain.3
                  • 0x3038 Sensor_ServiceDistance - can.service.mileage
                  • 0x4066 Sensor_TachographTimeStamp - tacho.timestamp
                  • 0x5004 Sensor_TemperatureID1 - onewire.sensor.temperature.1
                  • 0x5005 Sensor_TemperatureID2 - onewire.sensor.temperature.2
                  • 0x5006 Sensor_TemperatureID3 - onewire.sensor.temperature.3
                  • 0x5007 Sensor_TemperatureID4 - onewire.sensor.temperature.4
                  • 0xC003 Sensor_STRING4 - sensor.string.value.4
                  • 0xC014 Sensor_ICCID - gsm.sim.iccid
                  a month later

                  • namo

                  • Post #20

                  Xirgo-mqtt protocol is updated: the following Sensor IDs are added:

                  • 0x0076 Sensor_CoolandFluidWarning - can.coolant.level.low.indicator.status
                  • 0x009F Sensor_CANactivityPresent - can.activity.status
                  • 0x2014 Sensor_U8UserDefined9, J1979 Engine coolant temperature - can.j1979.engine.coolant.temperature
                  • 0x302B Sensor_CAN1_command - can.command.id.1
                  • 0x302C Sensor_CAN2_command - can.command.id.2
                  • 0x4056 Sensor_ReceivedCAN - can.messages.received
                  • 0x4057 Sensor_MissedCAN - can.messages.missed
                  • 0x4058 Sensor_CAN1bitrate - can.bitrate.1
                  • 0x4059 Sensor_CAN2bitrate - can.bitrate.2