Xirgo FM-500 Light

Xirgo FM-500 Light is a device with GPS/GLONASS and GSM connectivity, designed for object tracking. It is able to acquire information on object location, speed, direction, etc. and transfer the data via GSM network. Digital and analog inputs of the device together with 1-Wire interface may be used to connect different external sensors/devices. Outputs of the device may be used to control external equipment remotely. Flexible configuration allows users/dealers to adjust the device to meet their specific requirements.

Protocol: bce Manufacturer: Xirgo Global Change log: bce

Usage specifics

Parameters (113)

Commands (1)

AI Assistant

Here’s the like of JSON you get

{
    "ident": "352625333222111",
    "position.altitude": 273.61,
    "position.hdop": 0.7,
    "position.latitude": 49.069782,
    "position.longitude": 28.632826,
    "position.satellites": 18,
    "server.timestamp": 1650636570.426424,
    "timestamp": 1650636570.426424,
    "device.type.id": "Xirgo FM-500 Light",
    "channel.id": 1111,
    "protocol.id": "bce"
    "engine.ignition.status": true
    ...
}

How to consume this nice JSON

The easiest way is to make a REST API request like this

curl -X GET  --header 'Authorization: FlespiToken XXX' 'https://flespi.io/gw/devices/<device id>/messages'

Explore REST API Show more ways to consume data How to connect my Xirgo FM-500 Light to flespi

How to send commands to Xirgo FM-500 Light?

You can send a specific command. Show all commands

You can also

Modify messages

Add or remove parameters, inject data from LBS and reverse-geocoding services, etc.

Learn what plugins can do

Aggregate data

Determine trips and stops, catch events, detect geofence ins/outs, and more.

Learn about flespi analytics capabilities

Name

Type

Unit

Description

Sources

accident.event

boolean

Accident event detected

Data Type 1,
Data Type 7

ain

number

volts

Voltage on the analog input

Data Type 7

alarm.event

boolean

Alarm event triggered

Data Type 7

arm.status

boolean

Device arm status (true - device armed, false - device disarmed)

Data Type 7

axle.weight

number

Axle weigth

Data Type 7

battery.voltage

number

volts

Internal battery voltage

Data Type 7

can.acceleration.pedal.level

number

percentage

Acceleration pedal position, read from CAN

Data Type 7,
Mask2: acc_pedal

can.adblue.level

number

percentage

AdBlue (diesel exhaust fluid) level read from CAN

Data Type 7

can.ambient.air.temperature

number

celsius

CAN ambient air temperature

Data Type 7,
Mask2: j1939_air_temp

can.calculated.instant.fuel.consumption

number

liters

Instant fuel consumption calculated from non standard can bus messages

Data Type 7,
Mask4: fuel_con_ins

can.central.lock.status

boolean

CAN central lock is locked

Data Type 7

can.dtc

array

Diagnostic trouble code array read from CAN May content list of OBDII codes or list of objects with codes. Standard object parameter names used: *standard* - Protocol standard (J1939, J1708(J1587), OBDII) *mid* - Message Identifier (J1708) *sid* - Subsystem Identifier (J1708) *fmi* - Failure Mode Identifier (J1939, J1708) *spn* - Suspect Parameter Number (J1939) *sa* - Source Address (J1939, OBDII) *oc* - Occurrence Count (J1939) *cm* - Conversion Method (J1939) *status* - Status of error code (active, pending, historical, permanent)

Data Type 12

can.dtc.type

string

Error types by status (confirmed, pending, permanent, history, mil) read from CAN *confirmed* - Confirmed faults, Check Engine is on *pending* - Pending faults, may disappear *permanent* - Stored faults, only cleared after a successful test *history* - Historical faults that have cleared but remain in memory *mil* - Faults that trigger the Check Engine light (MIL - Malfunction Indicator Lamp)

Data Type 12 with Sub Data Type 4,
Data Type 12 with Sub Data Type 5,
Data Type 12 with Sub Data Type 6

can.engine.coolant.temperature

number

celsius

Engine coolant temperature read from CAN

Data Type 7,
Mask2: engine_temp

can.engine.fuel.rate

number

liters/h

Engine fuel rate read from CAN

Data Type 7,
Mask2: j1939_fuel_rate

can.engine.ignition.status

boolean

CAN engine ignition status

Data Type 7

can.engine.load.level

number

percentage

Calculated engine load level read from CAN

Data Type 7,
Mask2: j1939_eng_load

can.engine.motorhours

number

hours

Total engine motorhours (engine work time) read from CAN

Data Type 7,
Mask2: can_engine_hrs

can.engine.rpm

number

rpm

Engine RPM read from CAN

Data Type 7,
Mask2: can_taho

can.engine.temperature

number

celsius

Engine temperature read from CAN

Data Type 7

can.front.left.door.status

boolean

CAN front left door is opened

Data Type 7

can.front.right.door.status

boolean

CAN front right door is opened

Data Type 7

can.fuel.consumed

number

liters

Fuel volume totally consumed by vehicle read from CAN

Data Type 7,
Mask2: total_fuel

can.fuel.economy

number

km/liters

CAN instantaneous fuel economy

Data Type 7

can.fuel.level

number

percentage

Fuel level in tank read from CAN

Data Type 7,
Mask2: can_fls,
Mask2: j1939_fuel_lvl2

can.hood.status

boolean

CAN hood is opened

Data Type 7

can.j1587.dtc.lci

number

J1587 PID 194 (Diagnostic Touble Code) low character identifier for a standard diagnostic code

Data Type 12 with Sub Data Type 3

can.j1587.dtc.oc

number

J1587 PID 194 (Diagnostic Touble Code) occurrence count

Data Type 12 with Sub Data Type 3

can.j1587.dtc.status

boolean

J1587 PID 194 (Diagnostic Touble Code) current status of fault

Data Type 12 with Sub Data Type 3

can.j1587.dtc.type

number

J1587 PID 194 (Diagnostic Touble Code) type of diagnostic code

Data Type 12 with Sub Data Type 3

can.j1939.dm1.dtc.awl

number

J1939 Diagnostic Message 1 (Active Diagnostic Trouble Codes) amber warning lamp status: 0 - off, 1 - on, 2 - reserved, 3 - unknown