0
edits
Changes
→Codec 13 Nebaigta
Codec13 availability depends on device and firmware version.
Codec13 availability depends on device and firmware version.
{| class="wikitable"
|-
!style="background: black; color: white;"| Device !!style="background: black; color: white;"| Availability
|-
| FM11YX || Available since base firmware 01.18.XX
|-
| FM12YX || Not available
|-
| FM10YX || Not available
|-
| FM3400 || Not available
|-
| FM5300 || Not available
|-
| FM5500 || Not available
|-
| FM2200 || Not available
|-
| FM4200 || Not available
|-
| FM6320 || Available in base
|-
| FMAXX || Not available
|-
| FMBXX || Available in base
|-
| FMB630 || Available in base
|}
<small>Table 1. FM firmware requirements</small>
*'''GPRS command session'''
Following figure shows how GRPS command session is started over TCP.
[[Image:fd.png]]
<small>Figure 1. Command session</small>
First FM opens GPRS session and sends AVL data to server (refer FM protocols).
After all records are sent and correct sent data array acknowledgment is received by FM, it will begin TCP link mode message sending.
TCP Link mode messages do not require ACK.
*'''General Codec13 message structure'''
The following diagram shows basic structure of Codec 13 messages.
{| class="wikitable"
|-
! 0x00000000 !! Data size !! 0x0D !!style="background: yellow; color: red;"| 0x01 !!style="background: black; color: red;"| 0x06 !! Command size !! Timestamp !! Payload !!style="background: yellow; color: red;"| 0x01 !! CRC
|-
| 4 bytes || 4 bytes || 1 byte || 1 byte || 1 byte || 4 bytes || 4 bytes || X bytes || 1 byte || 1 byte
|}
{| class="wikitable"
|-
!style="background: black; color: red;"| 0x06||Message type filed - 0x06 = packet FM -> Server
|}
{| class="wikitable"
|-
!style="background: yellow; color: red;"| 0x01||Ignored bytes
|}
== '''<big>Codec 16 Nebaigta</big>''' ==
== '''<big>Codec 16 Nebaigta</big>''' ==
