AVL ID differences between FMB and FT platforms

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

Property ID in AVL packet	Property Name in FMB platform	Property Name in FT platform	Reason for change
70	Geofence zone 11	PCB Temperature	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.
155	Geofence zone 01	Manual Geofence Scenario	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.
156	Geofence zone 02	Manual Geofence Scenario Zone Event	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.
157	Geofence zone 03	Manual Geofence Scenario Speed Event	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.
358	Total Operation Time (TST100 AVL ID)	Custom Scenario 1	Custom scenario was initially developed in FMX6 devices and AVL ID for the first scenario event matches between FMX6 and FT platform.
359	Total Riding Time (TST100 AVL ID)	Custom Scenario 2	Custom scenario was initially developed in FMX6 devices and AVL ID for the second scenario event matches between FMX6 and FT platform.
360	Single Operation Time (TST100 AVL ID)	Custom Scenario 3	Custom scenario was initially developed in FMX6 devices and AVL ID for the third scenario event matches between FMX6 and FT platform.
800	External voltage (TFT100 AVL ID)	External voltage	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.
641	ICCID	ICCID	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.