Line 272: |
Line 272: |
| | 01004C01001CF99DD263333030323334303634303730383330000018000059282DBC03000B0036A2B8193D120000000302001C59282BA391F5ABCDBFDD0180000059282BA891F5ABCDBFDD0180000059282BA391F5AB<br /> | | | 01004C01001CF99DD263333030323334303634303730383330000018000059282DBC03000B0036A2B8193D120000000302001C59282BA391F5ABCDBFDD0180000059282BA891F5ABCDBFDD0180000059282BA391F5AB<br /> |
| |} | | |} |
| + | {01} – Protocol revision number |
| + | {00}{4C} – overall message length |
| + | {01} – MO header IEI |
| + | {00}{1C} – MO header length |
| + | {F9}{9D}{D2}{63} – CDR Reference |
| + | {33}{30}{30}{32}{33}{34}{30}{36}{34}{30}{37}{30}{38}{33}{30} – IMEI of the device |
| + | {00} – Session status (Transfer OK in this case) |
| + | {00}{18} – MOMSN |
| + | {00}{00} – MTMSN |
| + | {59}{28}{2D}{BC} – Time of session |
| + | {03} – MO Location information IEI |
| + | {00}{0B} – MO Location information length |
| + | {00}{36}{A2}{B8}{19}{3D}{12} – MO latitude and longitude as described in Iridium documentation. |
| + | {00}{00}{00}{03} – CEP radius |
| + | {02} – Payload IEI |
| + | {00}{1C} – Payload length |
| + | {59}{28}{2B}{A3}{91}{F5}{AB}{CD}{BF}{DD}{01}{80}{00}{00} – Record 1 |
| + | {59}{28}{2B}{A8}{91}{F5}{AB}{CD}{BF}{DD}{01}{80}{00}{00} – Record 2 |
| + | There blue part of record is satellite device generated data and green is actual record payload which was sent to server from FM63 device. Information of the first record should be parsed like this: |
| + | {59}{28}{2B}{A3} – Timestamp of record generation in GMT0; |
| + | {91}{F5}{AB} – Longitude (recalculated value is 25,255756) |
| + | {CD}{BF}{DD} – Latitude (recalculated value is 54,832396) |
| + | {01} – DIN1 generated event |
| + | {80} – DIN1 on, while DIN2, DIN3, DIN4, DOUT1, DOUT2, DOUT3, DOUT4 – off |
| + | {00} – Reserved byte |
| + | {00} – Vehicle was stopped then record is generated |