Migration Guide 2.18

Migration SDK from old versions

This section will provide a detailed description of the API changes during the upgrade. We strongly recommend reading this documentation when upgrading the SDK version to understand the API differences and update your API calls accordingly based on the version disparities.

Migration to version 2.18.5

The SDK provides a series of APIs for M-NSP2.0.

Note

Please ensure the enableEdgeMatcher is true in the DriveMotion sdk settings.

Get Recommended Peripherals

This API retrieves a list of currently connected Bluetooth devices or those cached from previous trips. It allows applications to identify peripherals that can be linked to a vehicle. To retrieve the recommended peripherals, use the TNGetRecommendedPeripheralsCall API. For more details, refer to the API Usage documentation.

Link Vehicle to Peripheral

This API links a vehicle to a specific peripheral device, such as a Bluetooth accessory, for trip data association. To link a vehicle to a peripheral, use the TNLinkVehicleToPeripheralCall API. For more details, refer to the API Usage documentation.

Replace Vehicle Peripheral

This API replaces the peripheral linked to a vehicle, allowing seamless transition from an old peripheral to a new one. To replace a vehicle’s peripheral, use the TNReplaceVehiclePeripheralCall API. For more details, refer to the API Usage documentation.

Get Cumulative Safety Score

This API retrieves the cumulative safety score for a specified vehicle or user within a given date range. To fetch the cumulative safety score, use the TNGetCumulativeSafetyScoreCall API. For more details, refer to the API Usage documentation.