Gemalto is now part of the Thales Group, find out more.

You are here

BGS5 Module - New Year's Eve error? | Thales IoT Developer Community

h2onet_p

April 17, 2019 - 1:45pm, 361 views

Hello,

In the first day of 2019, none of our modules woke up despite the correct configuration at+cala. It seems that this is the problem of changing the year when the module sleeps. There is a listing that reproduces the problem:

ati1
Cinterion
BGS5
REVISION 01.100
A-REVISION 00.000.21

OK
at+cala?
+CALA: "00/01/01,00:00:00",0,0,""
+CALA: "00/01/01,00:00:00",1,0,""
+CALA: "00/01/01,00:00:00",2,0,""
+CALA: "00/01/01,00:00:00",3,0,""
+CALA: "00/01/01,00:00:00",4,0,""

OK
AT+CCLK="18/12/31,23:57:00"
OK
at+cclk?
+CCLK: "18/12/31,23:57:05"

OK
AT+CALA="19/01/01,00:02:00",0
OK
at+cala?
+CALA: "19/01/01,00:02:00",0,0,""
+CALA: "00/01/01,00:00:00",1,0,""
+CALA: "00/01/01,00:00:00",2,0,""
+CALA: "00/01/01,00:00:00",3,0,""
+CALA: "00/01/01,00:00:00",4,0,""

OK
at^smso
^SMSO: MS OFF

OK

^SHUTDOWN

At this point the module never wakes up....

This is because the year 2018 starts over again.

--- After the soft reset ---
at+cclk?
+CCLK: "18/01/01,00:58:17"

Is this the intended behavior?

Maciek