View source for AVL ID differences between FMB and FT platforms

__TOC__

==Introduction==
FT platform was created with the intent to improve and optimize from previous generation trackers. For this reason some AVL IDs are different compared between FMB and FT platforms.

==AVL ID list==

{| class="nd-othertables_2" width:90%;
|+
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Property ID in AVL packet
! rowspan="1" style="width:20%; vertical-align: middle; text-align: center;" |Property Name in FMB platform
! rowspan="1" style="width:20%; vertical-align: middle; text-align: center;" |Property Name in FT platform
! rowspan="1" style="width:50%; vertical-align: middle; text-align: center;" |Reason for change
|-
|-
| style="vertical-align: middle; text-align: center;" |70
| style="vertical-align: middle; text-align: center;" |Geofence zone 11
| style="vertical-align: middle; text-align: center;" |PCB Temperature
| style="vertical-align: middle; text-align: center;" |Manual geofence scenario was reworked in FT platform, it no longer requires that many AVL IDs which were freed up. Additionally, in FMX6 (PRO) devices this AVL ID was used for PCB temperature and we've decided to use it in FT devices.
|-
| style="vertical-align: middle; text-align: center;" |155
| style="vertical-align: middle; text-align: center;" |Geofence zone 01
| style="vertical-align: middle; text-align: center;" |Manual Geofence Scenario
| style="vertical-align: middle; text-align: center;" |Manual geofence scenario was reworked in FT platform - instead of using AVL ID for each geofence zone (up to 50), there will be only three AVL IDs to define which zone was triggered (AVL ID 155), what type of event occurred (AVL ID 156) and (if configured) whether overspeeding was detected (AVL ID 157). Other AVL IDs which were previously used for Manual Geofence are freed up. 
|-
| style="vertical-align: middle; text-align: center;" |156
| style="vertical-align: middle; text-align: center;" |Geofence zone 02
| style="vertical-align: middle; text-align: center;" |Manual Geofence Scenario Zone Event
| style="vertical-align: middle; text-align: center;" |Manual geofence scenario was reworked in FT platform - instead of using AVL ID for each geofence zone (up to 50), there will be only three AVL IDs to define which zone was triggered (AVL ID 155), what type of event occurred (AVL ID 156) and (if configured) whether overspeeding was detected (AVL ID 157). Other AVL IDs which were previously used for Manual Geofence are freed up.
|-
| style="vertical-align: middle; text-align: center;" |157
| style="vertical-align: middle; text-align: center;" |Geofence zone 03
| style="vertical-align: middle; text-align: center;" |Manual Geofence Scenario Speed Event
| style="vertical-align: middle; text-align: center;" |Manual geofence scenario was reworked in FT platform - instead of using AVL ID for each geofence zone (up to 50), there will be only three AVL IDs to define which zone was triggered (AVL ID 155), what type of event occurred (AVL ID 156) and (if configured) whether overspeeding was detected (AVL ID 157). Other AVL IDs which were previously used for Manual Geofence are freed up.
|-
| style="vertical-align: middle; text-align: center;" |358
| style="vertical-align: middle; text-align: center;" |Total Operation Time (TST100 AVL ID)
| style="vertical-align: middle; text-align: center;" |Custom Scenario 1
| style="vertical-align: middle; text-align: center;" |Custom scenario was initially developed in FMX6 devices and AVL ID for the first scenario event matches between FMX6 and FT platform.
|-
| style="vertical-align: middle; text-align: center;" |359
| style="vertical-align: middle; text-align: center;" |Total Riding Time (TST100 AVL ID)
| style="vertical-align: middle; text-align: center;" |Custom Scenario 2
| style="vertical-align: middle; text-align: center;" |Custom scenario was initially developed in FMX6 devices and AVL ID for the second scenario event matches between FMX6 and FT platform.
|-
| style="vertical-align: middle; text-align: center;" |360
| style="vertical-align: middle; text-align: center;" |Single Operation Time (TST100 AVL ID)
| style="vertical-align: middle; text-align: center;" |Custom Scenario 3
| style="vertical-align: middle; text-align: center;" |Custom scenario was initially developed in FMX6 devices and AVL ID for the third scenario event matches between FMX6 and FT platform.
|-
| style="vertical-align: middle; text-align: center;" |800
| style="vertical-align: middle; text-align: center;" |External voltage (TFT100 AVL ID)
| style="vertical-align: middle; text-align: center;" |External voltage
| style="vertical-align: middle; text-align: center;" |FT and TFT100 devices have voltage from 10 V to 90 V, but FMB AVL ID for External voltage is 66, due to size limitation (it is only 2 bytes), it cannot be used to represent voltage above 60 V, so instead AVL ID 800 is used in new platform.
|-
| style="vertical-align: middle; text-align: center;" |641
| style="vertical-align: middle; text-align: center;" |ICCID
| style="vertical-align: middle; text-align: center;" |ICCID
| style="vertical-align: middle; text-align: center;" |ICCID value was being sent over two IO elements in FMB platform - ID 11 and ID 16, this was limitation of Codec 8 protocol and this was rectified in FT platform.