work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

Waqar Ahmed — Fri, 09 Jun 2023 09:37:34 GMT

Hi,

I opened up new Private ticket and mentioned you there.

Thanks

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

Hakon — Wed, 07 Jun 2023 13:47:39 GMT

[quote user="Waqar Ahmed"]will you please help us to debug the issue?[/quote]

Would you mind opening a new ticket for this?

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

Waqar Ahmed — Tue, 30 May 2023 08:42:19 GMT

Hi JOHNATHAN,
I have make changes as per above discussion. We are facing a strange issue on field deployed devices, like yesterday the timestamp we are getting suddenly drift from 29 may2023 to 23 may 2023.This device is running from 3 may without any reboot.

After 2 to 3 hour. Its again reporting accurate timestamps.

will you please help us to debug the issue?

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

Hakon — Wed, 17 Aug 2022 12:23:52 GMT

The modem does not receive the network time the first time and then tried with NTP, which gives the wrong time. You can try setting CONFIG_DATE_TIME_AUTO_UPDATE and not run date_time_core_update_async(). If it doesn't work, try increasing the delay.

Also, the NTP server seems to be giving the wrong time, so it would be nice to have a modem trace to investigate this.

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

Waqar Ahmed — Tue, 09 Aug 2022 11:55:46 GMT

LTE cell changed: Cell ID: 38517279, Tracking area: 9010
RRC mode: Connected
Network registration status: Connected - roaming
D: UpPSM parameter update: TAU: 4200, Active time: 60
connection_poll_started
Next connection retry in 30 seconds
dating date time UTC...
D: Date time never set
D: Getting time from cellular network
D: Modem has not got time from LTE network, so not using it
D: Getting time from NTP server
AWS_IOT_EVT_CONNECTING
D: Connected to LTE, performing NTP UTC time update
D: Date time never set
D: Time obtained from cellular network (XTIME notification)
D: System time updated: 2022-08-09 11:53:15
DATE_TIME_OBTAINED_MODEM
D: IPv4 Address found 54.194.240.240
D: Time obtained from NTP server ntp.uio.no
D: New date time update in: 14400 seconds
D: System time updated: 1970-01-01 00:00:00
DATE_TIME_OBTAINED_NTP
D: Updating date time UTC...
D: Using previously obtained time
DATE_TIME_OBTAINED_NTP
D: Using send socket timeout of 60 seconds
D: AWS IoT broker connection request sent
D: MQTT client connected!
MQTT client connected!AWS_IOT_EVT_CONNECTED

Current RSRP -125
Publishing: {
"state":{
"reported":{
"logging_interval":300,
"app_version":"v2.0.0",
"ts":16743,
"battery":3600,
"psu":0,
"imei":"",
"lat":53.335768,
"long":-6.325005,
"ttff":0,
"last_loc_update_time":0,
"current_network_mode":"NBIOT",
"rsrp":-125,
"rsrq":-12,
"nbiot_rsrp":-125,
"lte_m_rsrp":0
}
}
} to AWS IoT broker
message length 356

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

JONATHAN LL — Tue, 09 Aug 2022 05:46:04 GMT

Hi,

Can you enable CONFIG_DATE_TIME_LOG_LEVEL_DBG and provide the log. This should give us info on what exactly is going on.

Regards,
Jonathan

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

Waqar Ahmed — Thu, 04 Aug 2022 11:48:51 GMT

Hi Jonathan,

I did make the changes according to this lib: date_time: Fix uptime to UTC time conversion · simensrostad/fw-nrfconnect-nrf@5b3af28 (github.com)

but it give me wrong time stamp like 15278,

even after getting the time from modem.

the strange behave is that after 3 to 4 continuously publishing wrong timestamp when modem itself requested time from network then it start publishing timestamp.

so the issue is in function err = clock_gettime(CLOCK_REALTIME, &tp);

I am getting right timestamp here.

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

JONATHAN LL — Mon, 11 Jul 2022 13:39:46 GMT

[quote user=""]please can you confirm us is there any work around for the time drift problem in this sdk.[/quote]

There is no workaround in NCS v1.9.X but you can cherry pick the commit from NCS v2.0.0

lib: date_time: Fix uptime to UTC time conversion · simensrostad/fw-nrfconnect-nrf@5b3af28 (github.com)

This will fix the issue.

Regards,
Jonathan

RE: work around for NCSDK-14235: Timestamps that are sent in cloud messages drift over time

JONATHAN LL — Fri, 08 Jul 2022 14:21:00 GMT

Due to summer holiday staffing is low and response time is slower than usual, pardon the inconvenience.

We will get back to you as soon as we can.

Regards,
Jonathan