In order to transfer data from device via Iridium communication you create in your flespi account a dedicated channel that is capable to parse data in the Iridium format. Then you use URI of this channel in the Iridium communication section of your tracking device to instruct its Iridium modem to send data to this host and port.
Once correctly configured and activated you should be able to see in your Iridium channel device messages in Logs & Messages section. Messages will be parsed according to the generic Iridium binary standard with minimal information extracted and contain payload.hex portion with device manufacturer specific data.
In essence, the Iridium device in this case acts primarily as a modem for satellite connectivity and can be connected to any GPS tracker with an RS232 port. In flespi we already have the preset parsers for most common device manufacturers. Other hardware data is stored as payload.hex string parameter and requires parsing per the respective protocol specification. You may write your own PVM plugin for that or ask flespi team to do the integration.
Usually you will have a pair of two channels and two devices - one pair for normal (GPRS) connectivity and another pair for Iridium (satellite based). In that case your primary device is the one that uses normal connectivity with more regular reporting and much more parameters in the message. In such cases synchronizing messages between two devices is made seamless with the msg-copy plugin.
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
km
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
