1,606
edits
Changes
Iridium Edge Communication Protocol (view source)
Revision as of 08:42, 14 March 2023
, 08:42, 14 March 2023no edit summary
<br></br>
<br></br>
For example: to enable Din1, Din2 and Dout1: 0x01 + 0x02 + 0x10 = 0x13.
For example: to enable Din1, Din2 and Dout1: 0x01 + 0x02 + 0x10 = 0x13.
===SDB record structure===
SDB Record which will be sent through the Iridium satellites network will be different than the regular record. It will contain 4 bytes timestamp, 3 bytes longitude, 3 bytes latitude, 1 byte record generation info, 1 byte DIN,DOUT info, 1 byte Speed value.
{| class="nd-othertables_2" style="width:100%;"
|-style="text-align:center"
!Timestamp
!Longitude
!Latitude
!SDB AVL ID and flags
!DIN/DOUT info
!Reserved
!Speed
|- style="font-weight:normal;"
|4B
|3B
|3B
|1B
|1B
|1B
|1B
|}
'''''Timestamp''''' - Indicates when record was generated.
<br></br>
'''''Longitude''''' - In this packet is encoded in 3 bytes data. The server that gets this data should divide the result from 46603,375 and subtract 180 to get the actual longitude value. This coefficient is got in the following way: 16777215(maximum 3 bytes value) divided by 360 (maximum longitude value then 180 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.
<br></br>
'''''Latitude''''' - Is calculated in the same way as longitude but since latitude maximum value is two times smaller than longitude it can produce a bit more accurate data. The coefficient for latitude is 93206,75. This coefficient is got in the following way: 16777215(maximum 3 bytes value) divided by 180 (maximum latitude value then 90 is added). This calculation is used to fit negative and positive values to 3 bytes width variable.
<br></br>
'''''SBD AVL ID and flags''''' – Custom ID that will indicate what caused the record to be generated (final ID will (as only periodic records are generated, ID is not used)).
This byte is divided in two parts of four bits, as shown in table below:
{| class="nd-othertables_2" style="width:100%;"
|-
! colspan="4" style="font-weight:bold;" | <br />Flags (not used yet)
! colspan="4" style="font-weight:bold;" | <br />SBD AVL ID
|- style="color:#fe0000;"
| <br />Bit 7
| <br />Bit 6
| <br />Bit 5
| <br />Bit 4
| style="color:#3531ff;" | <br />Bit 3
| style="color:#3531ff;" | <br />Bit 2
| style="color:#3531ff;" | <br />Bit 1
| style="color:#3531ff;" | <br />Bit 0
|}
<br></br>
SBD AVL ID is used to show which IO element generated the Panic element. The list of currently implemented possible values is described below:
<br></br>
{| class="nd-othertables_2" style="width:100%;"font-weight:bold; vertical-align:middle;"
! style="font-weight:bold;" | <br />ID
! <br />0
! <br />1
! <br />2
! <br />3
! <br />4
! <br />5
! <br />6
! <br />7
! <br />8
! <br />9
|-
| style="font-weight:bold;" | <br />IO element
| <br />Periodic rec.
| <br />Digital Input 1
| <br />Digital input 2
| <br />Digital output 1
| <br />Speed
|}
<br></br>
Data from Bit 7 to Bit 4 are not used at the moment. The server should ignore this data part.
<br></br>
'''''DIN/DOUT info''''' - Displays configured IO elements values of enabled IO elements in SBD IO source settings - (parameter ID 99422). Since digital inputs can contain only logic 1 or 0 they are bit masked in one byte.
{| class="nd-othertables_2" style="width:100%;"font-weight:bold; vertical-align:middle;"
|-
! <br />DIN1
! <br />DIN2
! <br />DOUT1
|- style="font-weight:normal;"
| <br />Bit 7
| <br />Bit 6
| <br />Bit 5
| <br />Bit 4
| <br />Bit 3
| <br />Bit 2
| <br />Bit 1
| <br />Bit 0
|}
<br></br>
'''''Reserved''''' - Not used.
<br></br>
'''''Speed''''' – Indicates the speed of the vehicle if configured. If not (or in case of no GPS) – it will display 255.
<br> </br>
