Iridium Digital-Matter

Iridium Digital-Matter is a Digital Matter device that utilizes Iridium Edge modem to deliver data packets to flespi via satellite communication. User-defined payload within Iridium Digital-Matter is parsed according to specific Digital Matter protocol.

Iridium Edge is a cost-effective satellite IoT communications device with an all-in-one SBD module, antenna, and power supply. The plug-and-play satellite IoT terminal can be easily paired with the Digital Matter G130 device in order to expand their functionality to no GSM coverage zones. Current Iridium implementation offers the ability to generate and send SBD records after set period after the GSM signal is lost. This ensures constant connectivity for the clients as Iridium network is available globally.

Check more details here: https://support.digitalmatter.com/support/solutions/articles/16000100489-g120-iridium-quick-start-guide

Protocol: iridium Manufacturer: Iridium Change log: iridium

Usage specifics

Parameters (31)

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": "Iridium Digital-Matter",
    "channel.id": 1111,
    "protocol.id": "iridium"
    "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 Iridium Digital-Matter to flespi

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

can.8bit.value

number

Custom 8bit CAN value

Information Element 0x02

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

Information Element 0x02

dout

number

Digital outputs bitmask

Information Element 0x02

event.seqnum

number

Unique event sequence number

Information Element 0x01,
Information Element 0x02

ident

string

Device unique identifier like serial number, IMEI, etc

iridium.cep

number

Iridium Circular Error Probability radius

Information Element 0x03

iridium.position.latitude

number

degree

Iridium position latitude

Information Element 0x03

iridium.position.longitude

number

degree

Iridium position longitude

Information Element 0x03

payload.hex

string

HEX Payload received from device

Information Element 0x02

peer

string

IP:port from which device connecting to the channel

position.direction

number

degrees

Heading angle at position detection moment

Information Element 0x02

position.latitude

number

degrees

Latitude coordinate value

Information Element 0x02

position.longitude

number

degrees

Longitude coordinate value

Information Element 0x02

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

Information Element 0x02

position.valid

boolean

Is position information accurate and valid for given timestamp

Information Element 0x02

protocol.id

number

ID of protocol

record.seqnum

number

Registered record sequence number

Information Element 0x01

report.reason

number

Transmission reason code

Information Element 0x02

sbd.event.enum

number

SBD event code

Information Element 0x02

server.timestamp

number

seconds

Timestamp when server received a message

session.seqnum

number

Iridium CDR Reference(Auto ID)

Information Element 0x01

session.state.enum

number

Iridium session state

Information Element 0x01

session.timestamp

number

seconds

Iridium session duration

Information Element 0x01

timestamp

number

seconds

Message timestamp

Information Element 0x02

trip.status

boolean

Trip status, true if trip started, false - if stopped

Information Element 0x02

user.data.value

number

User data value

Information Element 0x02

Iridium Digital-Matter

Here’s the like of JSON you get

How to consume this nice JSON

You can also

Modify messages

Aggregate data

More devices from Iridium (2)