Positioning Universal FJ1510LW
Protocol:
positioning-universal
Manufacturer:
Positioning Universal
Change log:
positioning-universal
Usage specifics
Parameters (64)
Commands (1)
Positioning Universal FJ1510LW
Flespi parses telemetry data from your Positioning Universal FJ1510LW into a standardized JSON and
lets you send commands to Positioning Universal FJ1510LW via API.
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": "Positioning Universal FJ1510LW",
"channel.id": 1111,
"protocol.id": "positioning-universal"
"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'
How to send commands to Positioning Universal FJ1510LW?
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 alarm.panic.status
boolean
Panic alarm event occurred
battery.low.alarm
boolean
Battery low alarm event
battery.voltage
number
volts
Internal battery voltage
ble.beacons
array
Standard parameter names used:
*id* - beacon identification string. Usually it is beacon's UUID or MAC-address
*local_name* - Beacons's Local Name
*rssi* - BLE signal level. Units = dBm
*battery.voltage* - Beacon's battery voltage. Units = volts
*battery.level* - Beacon's battery level. Units = percentage
*temperature* - Beacon's temperature. Units = celsius
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)
can.dtc.number
number
Number of diagnostic trouble codes
can.engine.run.time
number
seconds
Run time since engine start read from CAN
can.fuel.type.enum
number
Fuel type read from CAN
can.mil.status
boolean
Malfunction indicator lamp status read from CAN
channel.id
number
ID of channel that received a message
crash.event
boolean
Crash event detected
custom
any
Any custom parameter
device.id
number
ID of device that received a message
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
din
number
Digital inputs bitmask
dout
number
Digital outputs bitmask
engine.ignition.status
boolean
Engine ignition or ACC status
event.code
string
Protocol-specific event code string
event.enum
number
Protocol-specific event code
event.seqnum
number
Unique event sequence number
external.powersource.voltage
number
volts
External power voltage
gps.satellites.status
boolean
GPS positioning system status
harsh.acceleration.event
boolean
Harsh acceleration detected
harsh.braking.event
boolean
Harsh braking detected
harsh.cornering.event
boolean
Harsh cornering detected
harsh.turn.left.event
boolean
Harsh left turn detected
harsh.turn.right.event
boolean
Harsh right turn detected,
ident
string
Device unique identifier like serial number, IMEI, etc
main.power.status
boolean
Main power state
movement.status
boolean
Current movement state
network.signal.rssi
number
dbm
Network signal strength
obd.pid00
number
OBD Bit encoded value showing supported PIDs 01-20
obd.pid20
number
OBD Bit encoded value showing supported PIDs 21-40
obd.pid40
number
OBD Bit encoded value showing supported PIDs 41-60
obd.pid60
number
OBD Bit encoded value showing supported PIDs 61-80
obd.pid80
number
OBD Bit encoded value showing supported PIDs 81-A0
obd.pidA0
number
OBD Bit encoded value showing supported PIDs A1-C0
obd.standard.code
string
OBD standard this vehicle conforms to
obd.standard.enum
number
OBD standards this vehicle conforms to
overspeeding.status
boolean
Overspeeding detected
peer
string
IP:port from which device connecting to the channel
position.accuracy
number
meters
Position data accuracy in meters
position.direction
number
degrees
Heading angle at position detection moment
position.hdop
number
Horizontal dilution of precision
position.latitude
number
degrees
Latitude coordinate value
position.longitude
number
degrees
Longitude coordinate value
position.satellites
number
Quantity of satellites used to calculate coordinates for given position information
position.speed
number
km/h
Instant speed at position detection moment
position.timestamp
number
seconds
Timestamp when coordinates where calculated
power.on.status
boolean
Power-on device status
private.status
boolean
Device is in private mode
product.id
string
Product ID
protocol.id
number
ID of protocol
report.reason
number
Transmission reason code
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
towing.alarm.status
boolean
Towing alarm state
towing.event
boolean
Towing event detected
vehicle.mileage
number
km
Total calculated mileage
vehicle.state.bitmask
number
Vehicle state flags bitmask
vehicle.vin
string
VIN of vehicle
vibration.alarm
boolean
Vibration alarm event
virtual.engine.ignition.status
boolean
Virtual engine ignition status
Properties
Custom command
custom
Send custom command to device without waiting for response
payload: Command payload
More devices from Positioning Universal (16)
Tags
