search

MLopezJ / asset-tracker-cloud-coiote-azure-converter-js

Convert the LwM2M JSON encoding written by AVSystem's Coiote Azure integration to nRF Asset Tracker's LwM2M JSON encoding.
0 stars 0 forks source link

Missing firmware definition for nRF Asset Tracker values #19

Closed MLopezJ closed 1 year ago

MLopezJ commented 1 year ago

This project relies in the assumption that the data required in nRF Asset Tracker will be provided by the integration of Coiote with Thingy91 and Azure.

Thingy:91 -> Coiote -> nRF Asset Tracker

That integration follows the last flow, and in each step the LwM2M data change its name.

For that reason it is desired to have a track of those transitions for the following LwM2M objects

Object ID
~LwM2M Server~ (It is not used in nRF Asset Tracker app) 1
Device 3
Connectivity Monitoring 4
~Firmware Update~ (It is not used in nRF Asset Tracker app) 5
Location 6
Temperature 3303
Humidity 3304
Pressure 3323
~Push Button~ (It is not used in nRF Asset Tracker app) 3347
~ECID-Signal Measurement Information~ (It is not used in nRF Asset Tracker app) 10256
~Ground Fix (Cellular and Wi-Fi location)~ (It is not used in nRF Asset Tracker app) 33626
~GNSS Assistance (A-GPS / P-GPS)~ (It is not used in nRF Asset Tracker app) 33625
Configuration 50009

It is not used in nRF Asset Tracker app: Objects were discarded after document data flow transition in nRF Asset Tracker through Coiote flow

MLopezJ commented 1 year ago

Location

Object

LwM2M ID Firmware Coiote LwM2M converter lib nrf Asset Tracker
6 LWM2M_OBJECT_LOCATION_ID 6 6 gnss

Props

MLopezJ commented 1 year ago

This could be an option about how to represent it.

Object Value
LwM2M ID: 0
Name: Latitude
Mandatory: true
Type: Float
Description: The decimal notation of latitude, e.g. -43.5723 [World Geodetic System 1984].
firmware Value: 0
Variable Name: LATITUDE_RID
Coiote Azure Position: 6.0.0
LwM2M Converter Lib Position: 6.0
nRF Asset Tracker Equivalent Value: gnss.properties.v.properties.lat
MLopezJ commented 1 year ago

Lets document it in .json format for the moment

MLopezJ commented 1 year ago

Keep it simple

MLopezJ commented 1 year ago

Location: Firmware -> nRF Asset Tracker

LwM2M firmware coiote azure LwM2M converter lib nRF Asset Tracker
0 LATITUDE_RID "6.0.0" 6.0 "gnss.properties.v.properties.lat"
1 LONGITUDE_RID "6.0.1" 6.1 "gnss.properties.v.properties.lng"
2 ALTITUDE_RID "6.0.2" 6.2 "gnss.properties.v.properties.alt"
6 SPEED_RID "6.0.6" 6.6 "gnss.properties.v.properties.spd"

GNSS: nRF Asset Tracker -> Firmware

nRF Asset Tracker LwM2M LwM2M converter lib coiote azure firmware Required
lng 6.1 6.1 "6.0.1" LONGITUDE_RID Yes
lat 6.0 6.0 "6.0.1" LATITUDE_RID Yes
acc ??????? ??????? ??????? ??????? No
alt 6.2 6.2 "6.0.2" ALTITUDE_RID Yes
spd 6.6 6.6 "6.0.6" SPEED_RID Yes
hdg ??????? ??????? ??????? ??????? Yes
MLopezJ commented 1 year ago

What does "hdg" and "acc" means?

MLopezJ commented 1 year ago

Is there any variable related to "Heading of movement in degrees" and "Accuracy (2D 1-sigma) in meters" in the firmware?

MLopezJ commented 1 year ago

The scope of the current repo is until the "LwM2M converter lib" step of the transition. This is what the contract says about the expected output. However, this complete data flow would be very helpful to understand the dynamic of the data.

A new repo could be created in order to document the mentioned flow.

MLopezJ commented 1 year ago

New repo about data flow: nRF Asset Tracker Data Flow

MLopezJ commented 1 year ago

Issue will be continue here: https://github.com/MLopezJ/nRF-Asset-Tracker-through-Coiote-flow/issues/2