BGS5T wrong date

45 views
Skip to first unread message

Jure Cerovšek

unread,
Oct 12, 2015, 4:01:43 AM10/12/15
to Cinterion Java enabled chips support
Hi,
has anyone experienced problem on BGS5T or any other module, where after a while date would be wrong? I am sending some data over GPRS and I just discovered that while module clock is correct and is not even 1 second behind, module date is 1 day behind.
Anyone know why this could happen?

Regards,
Jure

Jure Cerovšek

unread,
Oct 12, 2015, 4:54:09 AM10/12/15
to Cinterion Java enabled chips support
I also discovered that month is wrong. So today my date is: 11.11.2015. Could it happen that month was incremented instead of day?

Dne ponedeljek, 12. oktober 2015 10.01.43 UTC+2 je oseba Jure Cerovšek napisala:

Jérémie Faucher-Goulet

unread,
Nov 28, 2015, 2:52:53 PM11/28/15
to Cinterion Java enabled chips support
Yes, we've seen this happen on some of our products using a cinterion chip, assuming you also see this behavior being related to restarts. It seems that the RTC is not 100% reliable so we've stopped using it as a trusted source to restore time after a restart of our midlets.

Our best guess is that the RTC gets corrupted in brownout conditions or other unclean events with the power supply where the RTC will show a value that seems valid through AT commands instead of the default value you would expect after a cold start.

In our server logs we've seen dates that were wrong up to saying we are in the year 2067 :P

Relegating the RTC to time keeping only during runtime fixed our issues. At startup we get the time from other sources and no longer assume that a non-default value from the RTC means it kept the correct time since the last time the midlet was running.
Reply all
Reply to author
Forward
0 new messages