CalAmp LMU-4200

CalAmp LMU-4200 product has the features, expandability, and flexibility with the intelligence to meet all customer's ever changing needs in fleet management. The LMU-4200 offers a full set of features, comprehensive I/O system and expandable accessories that make it an industry leading value proposition. The LMU-4200 expandability and flexibility lowers the cost of delivering, supporting, and growing fleet management solutions.

Make your CalAmp LMU-4200 devices a part of any infrastructure by connecting them via flespi telematics hub. Manage the device settings using flespi device management platform. Learn how to configure CalAmp LMU-4200 with flespi.

Protocol: calamp Manufacturer: CalAmp Change log: calamp

Usage specifics

Parameters (49)

Settings (1)

Commands (2)

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": "CalAmp LMU-4200",
    "channel.id": 1111,
    "protocol.id": "calamp"
    "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 CalAmp LMU-4200 to flespi

How to send commands to CalAmp LMU-4200?

You can send a specific command. Show all commands

You can use pre-defined settings to send instructions more conveniently. Show all settings

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

accumulator

number

Custom accumulator, index starting from 0

Message Type 10,
Message Type 12,
Message Type 14,
Message Type 2,
Message Type 5,
Message Type 8,
Message Type 9

accumulator.exceed.threshold

number

Bitmask shows which accumulator exceeded its threshold value

Message Type 10,
Message Type 12,
Message Type 14,
Message Type 2,
Message Type 5,
Message Type 8,
Message Type 9

can.dtc.number

number

Number of diagnostic trouble codes

Message Type 12,
Message Type 14,
Message Type 5

channel.id

number

ID of channel that received a message

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

Message Type 10,
Message Type 12,
Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

dout

number

Digital outputs bitmask

Message Type 12,
Message Type 14,
Message Type 5

engine.ignition.status

boolean

Engine ignition or ACC status

Message Type 10,
Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

esn

string

Electronic Serial Number of the device

event.enum

number

Protocol-specific event code

Message Type 10,
Message Type 2

event.seqnum

number

Unique event sequence number

geofence.status.bitmask

number

This is a bit mapped field indicating if the LMU is either inside (bit set) or outside (bit cleared) of a defined zone. If the zone is undefined, the bit is also cleared.

Message Type 12,
Message Type 14,
Message Type 5

gnss.antenna.status

boolean

GNSS receiver antenna status

Message Type 10,
Message Type 2

gsm.cellid

number

Mobile network (GSM, 3G, 4G, LTE, 5G, ...) base station ID

Message Type 2

gsm.lac

number

Mobile network (GSM, 3G, 4G, LTE, 5G, ...) location area code

Message Type 2

gsm.mcc

number

Mobile network (GSM, 3G, 4G, LTE, 5G, ...) country code

Message Type 2

gsm.mnc

number

Mobile network (GSM, 3G, 4G, LTE, 5G, ...) code

Message Type 2

gsm.network.roaming.status

boolean

Mobile network (GSM, 3G, 4G, LTE, 5G, ...) in roaming mode

Message Type 10,
Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

gsm.sim.iccid

string

Integrated Circuit Card Id of SIM card of the Mobile network (GSM, 3G, 4G, LTE, 5G, ...)

Message Type 3

ident

string

Device unique identifier like serial number, IMEI, etc

message.buffered.status

boolean

Black box message

Message Type 2

message.type.enum

number

Message Type

network.signal.rssi

number

dbm

Network signal strength

Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

payload.hex

string

HEX Payload received from device

Message Type 11,
Message Type 4,
Message Type 9

peer

string

IP:port from which device connecting to the channel

peg.bitmask

number

This is a bit mapped field indicating the state of each of the available PEG Flags.

Message Type 12,
Message Type 14,
Message Type 5

position.2dfix.status

boolean

Is true when 3 or fewer satellites are seen/used in the GPS fix, and therefore altitude value cannot be calculated

Message Type 2

position.altitude

number

meters

Altitude value for position

Message Type 2

position.corrected.status

boolean

Ground base stations used to correct satellite-sourced position. E.g. DGPS or RTK for Galileo"

Message Type 2

position.direction

number

degrees

Heading angle at position detection moment

Message Type 10,
Message Type 2

position.hdop

number

Horizontal dilution of precision

Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

position.last.known.status

boolean

Is true when the current GPS fix is invalid but the value of the previous fix is available.

Message Type 2

position.latitude

number

degrees

Latitude coordinate value

Message Type 10,
Message Type 2

position.longitude

number

degrees

Longitude coordinate value

Message Type 10,
Message Type 2

position.predicted.status

boolean

Is true when the position update has a horizontal position accuracy estimate that is less that the Horizontal Position Accuracy Threshold defined in device configuration

Message Type 2

position.satellites

number

Quantity of satellites used to calculate coordinates for given position information

Message Type 10,
Message Type 2

position.speed

number

km/h

Instant speed at position detection moment

Message Type 10,
Message Type 2

position.timestamp

number

seconds

Timestamp when coordinates where calculated

Message Type 2

position.valid

boolean

Is position information accurate and valid for given timestamp

Message Type 10,
Message Type 2

protocol.id

number

ID of protocol

server.timestamp

number

seconds

Timestamp when server received a message

timestamp

number

seconds

Message timestamp

Message Type 10,
Message Type 11,
Message Type 12,
Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

timestamp.key

number

Message timestamp in seconds with message sequence number appended as the value fractional part. Used to distinguish between several messages that have the same timestamp.

Message Type 10,
Message Type 11,
Message Type 12,
Message Type 14,
Message Type 2,
Message Type 4,
Message Type 5,
Message Type 8,
Message Type 9

user.message.id

number

User message ID

Message Type 11,
Message Type 4,
Message Type 9

user.message.route

number

User message route

Message Type 11,
Message Type 4,
Message Type 9

vehicle.state.bitmask

number

Vehicle state flags bitmask