A-GPS Time Info error. | Thales IoT Developer Community
November 4, 2019 - 10:19pm, 5536 views
Hi,
A product we've developed using Gemalto's PLS8-US module relies on A-GPS for faster time to first fix. Devices starting the GNSS engine in A-GNSS **** using the AT^SGPSC command have worked well until recently. For the last few days, every attempt to start devices in A-GNSS **** has resulted in the AT^SGPSC command's, "AssistDataError" parameter reporting"Time Info Error". Automatic time zone updates are not enabled and devices seem to have have been set correctly to GMT when this error occurs.
For example, with one test device at 6:52 PM, November 4, 2019 GMT, firmware correctly sends the AT^CCLK command to the PLS8-US module and the command is acknowledged:
AT+CCLK="19/11/04,18:53:18"
OK
However, the subsequent start up attempt in A-GPS **** still fails with an "AGPS: TIME INFO ERROR" result.
A previously developed device using the 3G only PHS8-US ****m and essentially the same A_GPS startup sequence works properly without error.
Can you please tell me, why this might occur with LTE and not 3G and if this might be some odd daylight savings time issue or perhaps something else going wrong?
Thank you,
Ed Haslam
Integrated Tracking Technologies Inc.
Hello,
So this was working fine on the same modules and nothing was changed before the problem occured? Can you check ATI1 reply to identify the module version?
It is not clear for me if by "occur with LTE and not 3G" you mean the module veriosn or the problem occurence depends on the network registration to 3G or 4G.
Is it only one device or more or all PLS8-US affected?
Have you also verified AT+CCLK? after the problem occured - was the time still correct?
Have you tried to remove the exisitng XTRA data from the module and load the new XTRA file?
Regards,
Bartłomiej
Hi Bartłomiej,
Thanks very much for your reply. Starting in A-GNSS **** has been working well for a few months now. There have been no hardware changes and no firmware changes that would directly relate to A-GNSS startup. We are using GPS only and disabling GLONASS and Galileo with the AT^SGPSC command. This is the response to the ATI1 command:
PLS8-US R4
REVISION 04.004
A-REVISION 01.000.06
The problem affects every device checked so far. The firmware deletes the existing XTRA data file before attempting to download a new one. In this debug trace of the process, I've put an AT+CCLK? command both before the attempt to download the A-GNSS file and after trying to start the GNSS engine. In both cases, the GMT time is correct:
41 54 5e 53 49 43 41 3d 31 2c 31 0d AT^SICA=1,1.
45406 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
47956 MODEM 39
50456 MODEM 7
50457 MODEM 8
50557 MODEM 9
41 54 2b 43 47 50 41 44 44 52 3d 31 0d AT+CGPADDR=1.
50561 MODEM 10
0d 0a 2b 43 47 50 41 44 44 52 3a 20 31 2c 22 32 ..+CGPADDR: 1,"2
35 2e 37 36 2e 33 35 2e 31 37 36 22 0d 0a 0d 0a 5.76.35.176"....
4f 4b 0d 0a OK..
50605 MODEM 39
50725 MODEM 7
50726 MODEM 8
50826 MODEM 9
41 54 5e 53 49 53 53 3d 32 2c 22 73 72 76 54 79 AT^SISS=2,"srvTy
70 65 22 2c 22 53 6f 63 6b 65 74 22 0d pe","Socket".
50837 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
50964 MODEM 39
51084 MODEM 7
51085 MODEM 8
51185 MODEM 9
41 54 5e 53 49 53 53 3d 32 2c 22 61 64 64 72 65 AT^SISS=2,"addre
73 73 22 2c 22 73 6f 63 6b 74 63 70 3a 2f 2f 78 ss","socktcp://x
74 72 61 32 2e 67 70 73 6f 6e 65 78 74 72 61 2e tra2.gpsonextra.
6e 65 74 3a 38 30 22 0d net:80".
51212 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
51354 MODEM 39
51473 MODEM 7
51474 MODEM 8
51574 MODEM 9
41 54 5e 53 49 53 53 3d 32 2c 22 63 6f 6e 49 64 AT^SISS=2,"conId
22 2c 31 0d ",1.
51585 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
51617 MODEM 39
51736 MODEM 7
51737 MODEM 8
51837 MODEM 9
41 54 5e 53 49 53 4f 3d 32 0d AT^SISO=2.
51841 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
51954 MODEM 39
52073 MODEM 7
52074 MODEM 8
52174 MODEM 9
41 54 5e 53 49 53 54 3d 32 2c 35 2c 31 0d AT^SIST=2,5,1.
52178 MODEM 10
0d 0a 2b 43 4d 45 20 45 52 52 4f 52 3a 20 6f 70 ..+CME ERROR: op
65 72 61 74 69 6f 6e 20 74 65 6d 70 6f 72 61 72 eration temporar
79 20 6e 6f 74 20 61 6c 6c 6f 77 65 64 0d 0a y not allowed..
0d 0a 5e 53 49 53 57 3a 20 32 2c 31 0d 0a ..^SISW: 2,1..
54675 MODEM 7
54676 MODEM 8
54776 MODEM 9
RETRY **1**
41 54 5e 53 49 53 54 3d 32 2c 35 2c 31 0d AT^SIST=2,5,1.
54781 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
54863 MODEM 23
54883 MODEM 24
54886 MODEM 25
HTTPLEN 24394
56080 MODEM 7
56082 MODEM 8
56181 MODEM 9
41 54 2b 43 43 4c 4b 3f 0d AT+CCLK?.
56185 MODEM 10
0d 0a 2b 43 43 4c 4b 3a 20 22 31 39 2f 31 31 2f ..+CCLK: "19/11/
30 38 2c 32 33 3a 31 33 3a 33 32 2d 33 32 22 0d 08,23:13:32-32".
0a 0d 0a 4f 4b 0d 0a ...OK..
56232 MODEM 7
56233 MODEM 8
56333 MODEM 9
41 54 5e 53 42 4e 57 3d 61 67 70 73 2c 2d 31 0d AT^SBNW=agps,-1.
56337 MODEM 10
0a 0d 0a 43 4f 4e 4e 45 43 54 0d 0a 0d 0a 41 47 ...CONNECT....AG
50 53 20 52 45 41 44 59 3a 20 52 45 53 45 54 20 PS READY: RESET
47 50 53 20 45 4e 47 49 4e 45 20 41 4e 44 20 44 GPS ENGINE AND D
45 4c 45 54 45 20 58 54 52 41 20 46 49 4c 45 2e ELETE XTRA FILE.
2e 2e 0d 0a 0d 0a 41 47 50 53 3a 20 45 4e 44 20 ......AGPS: END
4f 4b 0d 0a 0d 0a 4f 4b 0d 0a OK....OK..
56572 MODEM 7
56573 MODEM 8
56673 MODEM 9
41 54 5e 53 42 4e 57 3d 61 67 70 73 2c 32 34 33 AT^SBNW=agps,243
39 34 0d 94.
56683 MODEM 10
0d 0a 43 4f 4e 4e 45 43 54 0d 0a ..CONNECT..
0d 0a 41 47 50 53 20 52 45 41 44 59 3a 20 53 45 ..AGPS READY: SE
4e 44 20 46 49 4c 45 20 2e 2e 2e 0d 0a ND FILE .....
57154 MODEM 27
62085 MODEM 10
0d 0a 41 47 50 53 3a 20 54 49 4d 45 20 49 4e 46 ..AGPS: TIME INF
4f 20 45 52 52 4f 52 0d 0a O ERROR..
62644 MODEM 7
62646 MODEM 8
62746 MODEM 9
41 54 5e 53 49 53 54 3d 32 2c 35 2c 30 0d AT^SIST=2,5,0.
62750 MODEM 10
0d 0a 2b 43 4d 45 20 45 52 52 4f 52 3a 20 6f 70 ..+CME ERROR: op
65 72 61 74 69 6f 6e 20 66 61 69 6c 65 64 0d 0a eration failed..
57211 MODEM 7
57212 MODEM 8
57312 MODEM 9
RETRY **1**
41 54 5e 53 49 53 54 3d 32 2c 35 2c 30 0d AT^SIST=2,5,0.
57317 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
57470 MODEM 39
57590 MODEM 7
57591 MODEM 8
57691 MODEM 9
41 54 5e 53 49 53 43 3d 32 0d AT^SISC=2.
57694 MODEM 10
0d 0a 4f 4b 0d 0a ..OK..
57743 MODEM 39
A-GPS Not Updated!
62743 MAIN 8
62744 MODEM 17
62863 MODEM 7
62865 MODEM 8
62964 MODEM 9
41 54 2b 43 43 4c 4b 3f 0d AT+CCLK?.
62968 MODEM 10
0d 0a 2b 43 43 4c 4b 3a 20 22 31 39 2f 31 31 2f ..+CCLK: "19/11/
30 38 2c 32 33 3a 31 34 3a 34 34 2d 33 32 22 0d 08,23:14:44-32".
0a 0d 0a 4f 4b 0d 0a ...OK..
Thank you,
Ed
Hello,
So it looks like you get this error while uploading the xtra file to the module. I thought that maybe it happens when you start the GPS engine.
If the app downloads the file every time and the problem started at some point in time without any software modifications it could mean that maybe there's some problem with the xtra file. It looks like for some reason it is treated as outdated. Have you also tried the other links?
On the other hand I can see a timezone offset in your +CCLK: output - it is displayed only when automatic time zone update is enabled with AT+CTZU and provided by the network. So maybe here's the problem.
Regards,
Bartłomiej
Hi Bartłomiej,
We've tried all three A-GNSS xtra file servers with the same results. With and without automatic time zone update deosn't seem to make a difference in the outcome either. One strange result happened when the RTC was not set at all but started with its default date and time in 1980. It appears the A-GNSS file did download successfully in this case but checking the file with the AT^SGPSC: "Info","Xtra", command shows the file is 200 years in the future! I've attached the log file.
Thank you,
Ed
WAKEUP 2000/1/1 00:00:02
^SYSSTART
ATE0
OK
AT^SSRVSET="actSrvSet"
^SSRVSET: 1
OK
AT^SGPSC="Power/Antenna","off"
^SGPSC: "Power/Antenna","off"
OK
AT+CMEE=2
OK
AT\Q3
OK
AT^SIND=simstatus,1
^SIND: simstatus,1,5
OK
AT+CTZU=0
OK
AT+CNMI=2,1,0,0,1
OK
AT+CMGF=1
OK
AT+CPMS="ME","ME","MT"
+CPMS: 0,255,0,255,0,255
OK
AT+CGDCONT=1,"IP","apn.zerogravitywireless.com"
+CME ERROR: operation temporary not allowed
AT+CGDCONT=2,"IP","apn.zerogravitywireless.com"
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,0
OK
AT^SIND=service,2
^SIND: service,0,1
OK
AT^SGPSC="Engine","0"
^SGPSC: "Engine","0"
OK
AT+CMUX=0
OK
AT+CCLK?
+CCLK: "80/01/06,00:00:44"
OK
AT^SIND=nitz,1
^SIND: nitz,1,"19/11/12,00:31:31",-32
OK
AT+COPS?
+COPS: 0,0,"ROGERS",2
OK
AT^SGAUTH=1,0
OK
AT^SICA=1,1
OK
AT+CGPADDR=1
+CGPADDR: 1,"10.178.135.143"
OK
AT^SISS=2,"srvType","Socket"
OK
AT^SISS=2,"address","socktcp://xtra2.gpsonextra.net:80"
OK
AT^SISS=2,"conId",1
OK
AT^SISO=2
OK
AT^SIST=2,5,1
+CME ERROR: operation temporary not allowed
^SISW: 2,1
RETRY **1**
AT^SIST=2,5,1
OK
AT+CCLK?
+CCLK: "80/01/06,00:00:55"
OK
AT^SBNW=agps,-1
CONNECT
AGPS READY: RESET GPS ENGINE AND DELETE XTRA FILE...
AGPS: END OK
AT^SBNW=agps,24394
CONNECT
AGPS READY: SEND FILE ...
AGPS: END OK
OK
AT^SIST=2,5,0
OK
AT^SISC=2
OK
A-GPS Updated!
AT^SGPSC="Info","Xtra"
^SGPSC: "Info","Xtra","13550","27976","10079"
OK
AT^SGPSC="Engine/Glonass","0"
^SGPSC: "Engine/Glonass","0"
OK
AT^SGPSC="Engine/Galileo","0"
^SGPSC: "Engine/Galileo","0"
OK
AT^SGPSC="Engine","1"
^SGPSC: "Engine","1"
OK
AT^SGPSC="Nmea/Output","on"
^SGPSC: "Nmea/Output","on"
OK
AT+CPMS?
+CPMS: "ME",0,255,"ME",0,255,"MT",0,255
OK
Hi Bartłomiej,
Apparently, we're not the only ones having recent trouble with Qualcomm's gpsOneXTRA service:
https://developer.qualcomm.com/forum/qdn-forums/software/qualcomm-lte-io...
https://forums.quectel.com/t/gpsonextra-not-working-in-bg96/2703
Thank you,
Ed
Hello,
Indeed it seems that there's something with Qualcomm's gpsOneXTRA files - they might have changed somenting or have some issues with their service. So are you sure that it still works with your PHS8-US modules?
I have tried with a few Qualcomm modules and also have issues. With my PLS8-E module I have some other error message. But I have found some historical xtra.bin files on my PC and id did work with the old files (I have also set the appropriate date for those files). I'll try to get some more information.
Regards,
Bartłomiej
Hi Bartłomiej,
With our PHS8 based trackers, A-GPS does still seem to work. That's an xtra.bin file though, rather than the A-GNSS based, xtra2.bin files for the PLS8 that we've been having trouble with.
However we've just found that if you try this server, A-GNSS should work:
http://xtrapath4.izatcloud.net/xtra2.bin
One clue there's something weird going on with the existing xtra2.bin servers is the different file sizes on the three recommended sites. My understanding is, it should be the same file hosted on all three servers. How can Qualcomm arbitrarily make a change like this, potentially affecting tens of thousands of devices and nobody is informed of the change? Thanks very much for your help and definitely looking forward to any further information you might be able to find.
All the best,
Ed
Hello,
This http://xtrapath4.izatcloud.net/xtra2.bin file did also work for me. Yesterday I was trying this path but with xtra.bin file (http://xtrapath4.izatcloud.net/xtra.bin) and it didn't work. So I didn't try with xtra2.bin then.
Indeed it's interesting that the sizes are different.
It seems that we also haven't been informed.
I'll push this internally and hope it will be clarified.
Regards,
Bartłomiej
Hi Bartłomiej,
Just wondering if you've heard anything from Qualcomm yet.
Thank you,
Ed
Hi Ed,
We've also had another similar report. It will be clarified with Qualcomm. However I don't have the results yet. I'll write it here when I have more information.
Regards,
Bartłomiej
Pages