[BG600L-M3] queries the real time clock (RTC) of the module returns wrong date

Hi,

I am faced with a bug or something like that when I query the module to get NITZ information (after network is successfully attached).

BEHAVIOR 1 (suspicious):

openocd: 015243 AT< +QNWINFO: "NBIoT","20810","LTE BAND 20",6310 
openocd: 015243 AT= OK 
openocd: 015243 AT> CEREG=0 
openocd:  
openocd: 015243 AT= OK 
openocd: 015243 AT> CEREG? 
openocd:  
openocd: 015243 AT= +CEREG: 0,1 
openocd: 015243 AT= OK 
openocd: 015243 AT> CCLK? 
openocd:  
openocd: 015243 AT< +CCLK: "80/01/06,00:00:20+04"
openocd: 015243 AT= OK 
openocd: 015243 AT> CTZU=3 
openocd:  
openocd: 015243 AT= OK 
openocd: 015243 AT> CCLK? 
openocd:  
openocd: 015243 AT< +CCLK: "80/01/06,00:00:21+04"
openocd: 015243 AT= OK 
openocd: 015243 AT> CCLK? 
openocd:  
openocd: 015243 AT= +CCLK: "80/01/06,00:00:21+04"
openocd: 015243 AT= OK

BEHAVIOR 2 (normal):

openocd: 020402 AT= OK 
openocd: 020402 AT> CCLK? 
openocd:  
openocd: 020402 AT< +CCLK: "21/02/04,10:20:51+04" 
openocd: 020402 AT= OK 
openocd: 020402 AT> CTZU=3 
openocd:  
openocd: 020402 AT= OK 
openocd: 020402 AT> CCLK? 
openocd:  
openocd: 020402 AT< +CCLK: "21/02/04,10:20:51+04" 
openocd: 020402 AT= OK 
openocd: 020402 AT> CCLK? 
openocd:  
openocd: 020402 AT= +CCLK: "21/02/04,10:20:52+04" 
openocd: 020402 AT= OK 
openocd: 020402 ]

current module informations :
openocd: 005731 AT< Quectel
openocd: 005731 AT< BG600L-M3
openocd: 005731 AT< Revision: BG600LM3LAR02A03

Does the module needs an extra time before queries its RTC ?

Thanks for your help,

Regards,

Marco

normally , if your module has not registered network , the modem time ( AT+cclk?) will begin from “80/01/06,00:00”

if your module has registered network , the module will sync the NITZ time from cell network .

I have test it , BG600GL work fine in my side , could you send the email to stephen.li@ quectel.com , give us more detail ,What are the details of the difference between your first and second test case steps

Hello,
Facing same issue (on BG95), we are on a battery operating system:
“Wake-up, send data, sleep” use case, so we can’t afford to lose time during wake-up.
I used to wake-up, wait for network registration with AT+CGREG and then get time with AT+CCLK? and everything was good but now we have device in Colombia and we are getting 2080 date ;(
Any delay recommended between network registration and AT+CCLK? command ?
Thank you,
Thomas

Maybe NITZ is just not available on all operators?

Any other option to sync time from network?

Even with latest modem updates and correctly registered (+CEREG: 0,1), NITZ seems (rarely) unreliable.
You could use NTP to sync time or discard hazardous AT+CCLK responses.