AT+CCLK reporting bogus time

[vkbakken]

I am seing odd time strings from AT+CCLK... Like: "+CCLK: "15/02/01,00:00:08"\r\nOK\r\n"

I think it is required that AT+CCLK responds error until it has gotten network time. Otherwise how can I trust it?

Is there a point where the AT+CCLK is not safe?

[tesc]

Hi,

A short update:

We plan to implement an error to be returned from AT+CCLK if time has not been received from the network.

We are not planning to implement a Unix timestamp AT command. Use AT+CCLK and convert in application space instead.

Regards,
Terje