Iridium Edge Communication Protocol - Revision history

Arijus.C at 08:15, 4 November 2025

2025-11-04T08:15:20Z

← Older revision		Revision as of 11:15, 4 November 2025
Line 330:		Line 330:
	===Additional Information===		===Additional Information===

	1 Iridium data packet uses 14 bytes of data, this means when using SBD8 service plan we get 8000/14=571 records, please keep this in mind when testing out the iridium terminal.		*1 Iridium data packet uses 14 bytes of data, this means when using SBD8 service plan we get 8000/14=571 records, please keep this in mind when testing out the iridium terminal.

	The device is able to generate 1 record every minute. ~~Which~~ is about 9,5 hours of continuous record generation (once every minute) which can deplete the plan.		*The device is able to generate 1 record every minute. That is about 9,5 hours of continuous record generation (once every minute), which can deplete the plan.

	Exceeding the plan will introduce overdraft fees, unless SBD upload limit is configured.		*Exceeding the plan will introduce overdraft fees, unless SBD upload limit is configured.

	Once device reaches SBD limit it will stop sending records via Iridium terminal.		*Once device reaches SBD limit it will stop sending records via Iridium terminal.

Arijus.C at 12:51, 28 October 2025

2025-10-28T12:51:07Z

Show changes

Arijus.C at 08:01, 22 October 2025

2025-10-22T08:01:53Z

← Older revision		Revision as of 11:01, 22 October 2025
Line 155:		Line 155:
	==Packet Parsing==		==Packet Parsing==

	~~<span style="color~~:~~green">~~{AD}{69}{57}{63}{91}{F6}{A0}{CD}{CC}{64}{00}{00}{FF}{00}		'''Packet:'''

			{AD}{69}{57}{63}<span style="color:blue">{91}{F6}{A0}</span><span style="color:greenyellow">{CD}{CC}{64}</span><span style="color:orange">{00}</span><span style="color:darkgreen">{00}</span><span style="color:purple">{FF}</span><span style="color:red">{00}</span>

	{\| class="wikitable" style="width:50%;"		{\| class="wikitable" style="width:50%;"
Line 200:		Line 202:
	Converted Data:		Converted Data:

	'''GMT:''' ''Sunday, March 12, 2062 4:07:05 AM		*'''GMT:''' ''Sunday, March 12, 2062 4:07:05 AM

	'''Your time zone:''' ''Sunday, March 12, 2062 6:07:05 AM GMT+02:00		*'''Your time zone:''' ''Sunday, March 12, 2062 6:07:05 AM GMT+02:00

	'''Decimal timestamp/epoch:''' ''2909362025		*'''Decimal timestamp/epoch:''' ''2909362025

	===Longitude===		===Longitude===
Line 278:		Line 280:

	{\| class="wikitable"		{\| class="wikitable"
	! Hex 00 !! Converted to binary = !! 0 !! 1 !! 0 !! 0 !! 0 !! 0 !! 1 !! 0		! Hex 42 !! Converted to binary = !! 0 !! 1 !! 0 !! 0 !! 0 !! 0 !! 1 !! 0
	\|-		\|-
	! colspan="2" \|		! colspan="2" \|

Arijus.C at 07:51, 22 October 2025

2025-10-22T07:51:53Z

← Older revision		Revision as of 10:51, 22 October 2025
Line 135:		Line 135:
	#This will enable the “HEX enable” selection, enable this option.		#This will enable the “HEX enable” selection, enable this option.

	~~<!--Insert image per the word doc-->~~		[[File:Iridium SBD test setup 1.png]] [[File:Iridium SBD test setup 2.png]]

	Now Iridium packets can be captured by Hercules.		Now Iridium packets can be captured by Hercules.
Line 141:		Line 141:
	Hercules will receive the full Iridium packet, but '''only last 14 bytes are needed''':		Hercules will receive the full Iridium packet, but '''only last 14 bytes are needed''':

	~~<!--Insert image per the word doc-->~~		[[File:Iridium packet example.png]]

	Full packet looks like this:		Full packet looks like this:
Line 253:		Line 253:

	00000000 -> bits presenting DINs and DOUTs state in 1 - high, 0 - low or turned off (if not configured to be sent in SBD record), DINs and DOUTs are represented in this order in DIN/DOUT info bits DIN1, DIN2, DIN3, DIN4, DOUT1, DOUT2, DOUT3, DOUT4		00000000 -> bits presenting DINs and DOUTs state in 1 - high, 0 - low or turned off (if not configured to be sent in SBD record), DINs and DOUTs are represented in this order in DIN/DOUT info bits DIN1, DIN2, DIN3, DIN4, DOUT1, DOUT2, DOUT3, DOUT4
	~~<!--Insert tables per the word doc-->~~

	===~~RESERVED~~===		{\| class="wikitable"
			! Hex 00 !! Converted to binary = !! 0 !! 0 !! 0 !! 0 !! 0 !! 0 !! 0 !! 0
			\|-
			! colspan="2" \|
			\| DIN1 \|\| DIN2 \|\| DIN3 \|\| DIN4 \|\| DOUT1 \|\| DOUT2 \|\| DOUT3 \|\| DOUT4
			\|}

			Examples with a different value:

			{\| class="wikitable"
			! Hex 16 !! Converted to binary = !! 0 !! 0 !! 0 !! 1 !! 0 !! 1 !! 1 !! 0
			\|-
			! colspan="2" \|
			\| DIN1 \|\| DIN2 \|\| DIN3 \|\| '''DIN4''' \|\| DOUT1 \|\| '''DOUT2''' \|\| '''DOUT3''' \|\| DOUT4
			\|}

			{\| class="wikitable"
			! Hex 69 !! Converted to binary = !! 0 !! 1 !! 1 !! 0 !! 1 !! 0 !! 0 !! 1
			\|-
			! colspan="2" \|
			\| DIN1 \|\| '''DIN2''' \|\| '''DIN3''' \|\| DIN4 \|\| '''DOUT1''' \|\| DOUT2 \|\| DOUT3 \|\| '''DOUT4'''
			\|}

			{\| class="wikitable"
			! Hex 00 !! Converted to binary = !! 0 !! 1 !! 0 !! 0 !! 0 !! 0 !! 1 !! 0
			\|-
			! colspan="2" \|
			\| DIN1 \|\| '''DIN2''' \|\| DIN3 \|\| DIN4 \|\| DOUT1 \|\| DOUT2 \|\| '''DOUT3''' \|\| DOUT4
			\|}

			===Reserved===

	Reserved - Not used anywhere, but left due to compatibility with fm6 project.		Reserved - Not used anywhere, but left due to compatibility with fm6 project.
Line 263:		Line 292:
	<span style="color:purple">13-th</span> byte is reserved for FM devices and on FMB platform not used, therefore it is always <span style="color:purple">FF</span>.		<span style="color:purple">13-th</span> byte is reserved for FM devices and on FMB platform not used, therefore it is always <span style="color:purple">FF</span>.

	===~~SPEED~~===		===Speed===

	Speed – Indicates the speed of the vehicle if configured.		Speed – Indicates the speed of the vehicle if configured.

Arijus.C at 07:17, 22 October 2025

2025-10-22T07:17:52Z

Show changes

Arijus.C at 15:00, 20 October 2025

2025-10-20T15:00:47Z

@@ Line 1: / Line 1: @@
 __TOC__
 ==Iridium Configuration Parameters==
 {| class="wikitable"
 |+
@@ Line 119: / Line 122: @@
 Information here includes the data sending parameters which identifies the naming of the parameter in accordance to its number.
-'''Definitions'''
+'''Parsing of the Iridium SBD record'''
-* Timestamp – Indicates when record was generated
+'''Your time zone:''' ''Sunday, March 12, 2062 6:07:05 AM GMT+02:00
-*Latitude - Latitude is calculated in same way as longitude but since latitude maximum value is two times smaller than longitude it can produce a bit more accurate data. Coefficient for latitude is 93206,75. This coefficient is got in following way: 16777215(maximum 3 bytes value) divided from 180 (maximum latitude value then 90 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.
+'''Decimal timestamp/epoch:''' ''2909362025
 ==Data Sending Parameters==

Arijus.C at 12:03, 16 October 2025

2025-10-16T12:03:04Z

@@ Line 1: / Line 1: @@
 __TOC__
 ==Communication Protocol==
@@ Line 22: / Line 114: @@
 | style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: center; background: white;" | 1 bytes
 |}
 '''Definitions'''

Edgar.dementenko: /* SBD IO source */

2023-10-17T09:24:52Z

SBD IO source

← Older revision		Revision as of 12:24, 17 October 2023
Line 156:		Line 156:
	<br><br>		<br><br>
	In order to configure parameter 99422 manually users must simply set the appropriate values of bit positions, according to their needs:		In order to configure parameter 99422 manually users must simply set the appropriate values of bit positions, according to their needs:
	*~~Bit1~~ - ~~DIN 1~~		* Byte 1 - Din1
	*~~Bit2~~ - ~~DIN 2~~		* Byte 2 - Din2
	*~~Bit5~~ - ~~DOUT 1~~		* Byte 3 - Din3
	*~~Bit9~~ - Speed		* Byte 4 - Din4
	*~~Bit10~~ - ~~Crash~~		* Byte 5 - Dout1
			* Byte 6 - Dout2
			* Byte 7 - Dout3
			* Byte 8 - Dout4
			* Byte 9 - Speed
			* Byte 10 - CrashDetect

	==SDB record structure==		==SDB record structure==

Edgar.dementenko: /* SBD IO source */

2023-10-17T09:24:11Z

SBD IO source

← Older revision		Revision as of 12:24, 17 October 2023
Line 129:		Line 129:
	\|SBD IO source'''*'''		\|SBD IO source'''*'''
	\|0		\|0
	\|8		\|10
	\|0		\|0
	\|SBD IO elements which when enabled are included into the SBD record		\|SBD IO elements which when enabled are included into the SBD record

Edgar.dementenko: /* SBD IO source */

2023-10-17T09:23:56Z

SBD IO source

← Older revision		Revision as of 12:23, 17 October 2023
Line 84:		Line 84:

	==SBD IO source==		==SBD IO source==
	Configures IO source which can trigger SBD record saving. 9 elements can generate Alarm for SDB sending. These elements are:		Configures IO source which can trigger SBD record saving. 10 elements can generate Alarm for SDB sending. These elements are:
	*~~Digital input~~ 1		* Byte 1 - Din1
	*~~Digital input~~ 2		* Byte 2 - Din2
	*~~Digital output 1~~		* Byte 3 - Din3
	*Speed		* Byte 4 - Din4
	*~~Crash~~		* Byte 5 - Dout1
			* Byte 6 - Dout2
			* Byte 7 - Dout3
			* Byte 8 - Dout4
			* Byte 9 - Speed
			* Byte 10 - CrashDetect
			By setting the apropriate bits you'll get a hex number that can be sent to the device to configure. additionally you can set via the configurator and use getparam command to get the correct value.
	<br><br>		<br><br>
	Configurator parameter IDs and their explanation:		Configurator parameter IDs and their explanation: