Closed coderbyheart closed 4 years ago
Same with latest version:
{
"desired": {
"cfg": {
"act": false,
"actwt": 300,
"mvres": 60,
"mvt": 3600,
"gpst": 100,
"acct": 5
}
},
"reported": {
"bat": {
"v": 4500,
"ts": 1422749560173
},
"gps": {
"v": {
"lng": 8.753493,
"lat": 50.096946,
"acc": 22.198137,
"alt": -473.526978,
"spd": 0.558883,
"hdg": 0
},
"ts": 1572538783000
},
"dev": {
"v": {
"band": 8,
"nw": "NB-IoT GPS",
"iccid": "89882806660004909182",
"modV": "mfw_nrf9160_1.0.0",
"brdV": "nrf9160_pca20035",
"appV": "v0.25.0"
},
"ts": 1422749081135
},
"roam": {
"v": {
"area": 59035,
"mccmnc": 26201,
"cell": 26391562,
"ip": "10.202.80.9",
"rsrp": 0
},
"ts": 1422749081135
},
"cfg": {
"gpst": 100,
"act": false,
"actwt": 300,
"mvres": 60,
"mvt": 3600,
"acct": 5
},
"acc": {
"v": [
1.49061,
0.078453,
-9.414384
],
"ts": 1422749281744
},
"nrfcloud__dfu_v1__app_v": "v1.0.0"
}
}
It seems that the AT+CCLK?
command no longer works, it does not return any thing, but also does not time out.
Background: some network operators do not push the network time to the the device, which means that the real time might not be available until a GPS fix is acquired.
Timestamp:
1422749196593
: 2015-02-01T00:06:36.593ZShadow: