A-GPS download fails mid session

RE: A-GPS download fails mid session

Simonr — Thu, 30 Jul 2020 11:11:43 GMT

It's preferred to make all configurations first, (store permanent parameters to modem flash with CFUN=0) and activate the modem. This way all configurations are affecting to first LTE registration. However, this is not mandatory, parameters can be changed at any time with some limitations. For example, some commands require that the modem is deactivated.

Please note that CFUN=20/21 is affecting LTE only, CFUN=30/31 are affecting to GNSS only, and CFUN=1/4/0 are affecting to both LTE and GNSS.

Best regards,

Simon

RE: A-GPS download fails mid session

MJD093 — Wed, 29 Jul 2020 11:19:56 GMT

OK, thanks to that little bit of information, I made a change to the modem setup. I moved the AT commands for setting up LTE out of 'activate_lte()' and into setup_modem() where the initial GNSS AT modem parameters are entered.

I added only the full AT commands for "+CGDCONT" and "+CGAUTH", this seems to have had a dramatic effect on the application.

2020-07-29T11:12:58.511Z DEBUG modem << *** Booting Zephyr OS build v2.3.0-rc1-ncs1-3-g2400b4921ea9  ***\x0D
2020-07-29T11:12:58.518Z DEBUG modem << Staring GPS application\x0D\x0A
2020-07-29T11:12:58.520Z DEBUG modem << Sending AT command: AT%XSYSTEMMODE=0,1,1,0\x0D\x0A
2020-07-29T11:12:58.525Z DEBUG modem << Sending AT command: AT%XMAGPIO=1,0,0,1,1,1574,1577\x0D\x0A
2020-07-29T11:12:58.528Z DEBUG modem << Sending AT command: AT%XCOEX0=1,1,1570,1580\x0D\x0A
2020-07-29T11:12:58.542Z DEBUG modem << Sending AT command: AT+CGDCONT=0,"IP","arkessalp.com"\x0D\x0A
2020-07-29T11:12:58.555Z DEBUG modem << Sending AT command: AT+CGAUTH=0,"PAP","arkessa","arkessa"\x0D\x0A
2020-07-29T11:12:58.561Z DEBUG modem << Sending AT command: AT+CFUN=31\x0D\x0A
2020-07-29T11:12:58.579Z DEBUG modem << GPS Socket created\x0D\x0A
2020-07-29T11:12:58.589Z DEBUG modem << Getting GPS data...\x0D\x0A
2020-07-29T11:12:58.599Z DEBUG modem << \x1B[1;1H\x1B[2JNew AGPS data requested, contacting SUPL server, flags 59\x0D\x0A
2020-07-29T11:12:58.728Z DEBUG modem << Sending AT command: AT+CFUN=21\x0D\x0A
2020-07-29T11:13:36.271Z DEBUG modem << *** Booting Zephyr OS build v2.3.0-rc1-ncs1-3-g2400b4921ea9  ***\x0D\x0A
2020-07-29T11:13:36.277Z DEBUG modem << Starting GPS application\x0D\x0A
2020-07-29T11:13:36.281Z DEBUG modem << Sending AT command: AT%XSYSTEMMODE=0,1,1,0\x0D\x0A
2020-07-29T11:13:36.297Z DEBUG modem << Sending AT command: AT%XMAGPIO=1,0,0,1,1,1574,1577\x0D\x0A
2020-07-29T11:13:36.301Z DEBUG modem << Sending AT command: AT%XCOEX0=1,1,1570,1580\x0D\x0A
2020-07-29T11:13:36.303Z DEBUG modem << Sending AT command: AT+CGDCONT=0,"IP","arkessalp.com"\x0D\x0A
2020-07-29T11:13:36.311Z DEBUG modem << Sending AT command: AT+CGAUTH=0,"PAP","arkessa","arkessa"\x0D
2020-07-29T11:13:36.324Z DEBUG modem << Sending AT command: AT+CFUN=31\x0D\x0A
2020-07-29T11:13:36.339Z DEBUG modem << GPS Socket created\x0D\x0A
2020-07-29T11:13:36.347Z DEBUG modem << Getting GPS data...\x0D\x0A
2020-07-29T11:13:36.353Z DEBUG modem << \x1B[1;1H\x1B[2JNew AGPS data requested, contacting SUPL server, flags 59\x0D\x0A
2020-07-29T11:13:36.367Z DEBUG modem << Sending AT command: AT+CFUN=21\x0D\x0A
2020-07-29T11:14:50.866Z DEBUG modem << Established LTE link\x0D\x0A
2020-07-29T11:14:51.205Z DEBUG modem << ip adc2:4cc0::1101:300:1b00:1b00 (c04cc2ad) port 7276\x0D\x0A
2020-07-29T11:14:51.336Z DEBUG modem << Starting SUPL session\x0D\x0D\x0A
2020-07-29T11:14:51.354Z DEBUG modem << ULP encoding length: 38\x0D\x0A
2020-07-29T11:14:51.363Z DEBUG modem << Bytes sent: 38\x0D\x0A
2020-07-29T11:14:51.611Z DEBUG modem << Bytes received: 34, total 34\x0D\x0A
2020-07-29T11:14:51.628Z DEBUG modem << ULP ossDecode success, choice 3\x0D\x0A
2020-07-29T11:14:51.632Z DEBUG modem << SUPL server responded using version 2.0.4\x0D\x0A
2020-07-29T11:14:51.637Z DEBUG modem << SUPL response received\x0D\x0A
2020-07-29T11:14:51.644Z DEBUG modem << ULP encoding length: 57\x0D\x0A
2020-07-29T11:14:51.645Z DEBUG modem << Bytes sent: 57\x0D\x0A
2020-07-29T11:14:52.114Z DEBUG modem << Bytes received: 708, total 708\x0D\x0A
2020-07-29T11:14:52.120Z DEBUG modem << ULP ossDecode more input 4\x0D
2020-07-29T11:14:52.559Z DEBUG modem << Bytes received: 708, total 1416\x0D\x0A
2020-07-29T11:14:52.562Z DEBUG modem << ULP ossDecode more input 4\x0D\x0A
2020-07-29T11:14:52.997Z DEBUG modem << Bytes received: 708, total 2124\x0D
2020-07-29T11:14:53.004Z DEBUG modem << ULP ossDecode more input 4\x0D\x0A
2020-07-29T11:14:53.354Z DEBUG modem << Bytes received: 708, total 2832\x0D\x0A
2020-07-29T11:14:53.357Z DEBUG modem << ULP ossDecode more input 4\x0D\x0A
2020-07-29T11:14:53.898Z DEBUG modem << Bytes received: 162, total 2994\x0D\x0A
2020-07-29T11:14:53.908Z DEBUG modem << ULP ossDecode success, choice 5\x0D\x0A
2020-07-29T11:14:53.911Z DEBUG modem << Injected AGPS data, flags: 1, size: 16\x0D\x0A
2020-07-29T11:14:53.929Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.932Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.935Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.937Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.939Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.942Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.944Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.945Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.954Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.957Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.960Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.962Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D
2020-07-29T11:14:53.970Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.973Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.976Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.982Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.985Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:53.989Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.000Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.002Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.005Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.007Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.009Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.011Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.012Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.024Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.027Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.029Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.030Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.038Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.043Z DEBUG modem << Injected AGPS data, flags: 2, size: 72\x0D\x0A
2020-07-29T11:14:54.045Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.047Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.057Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.059Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.061Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.063Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.065Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.074Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.076Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.078Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.086Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.090Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.092Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.094Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.103Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.105Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.107Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.110Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.112Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.121Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.125Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.126Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.128Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.137Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.140Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.141Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.143Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.152Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.155Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.156Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.159Z DEBUG modem << Injected AGPS data, flags: 3, size: 32\x0D\x0A
2020-07-29T11:14:54.161Z DEBUG modem << No integrity data available\x0D\x0A
2020-07-29T11:14:54.173Z DEBUG modem << Injected AGPS data, flags: 4, size: 8\x0D\x0A
2020-07-29T11:14:54.177Z DEBUG modem << Injected AGPS data, flags: 6, size: 144\x0D
2020-07-29T11:14:54.188Z DEBUG modem << No location data available\x0D\x0A
2020-07-29T11:14:54.190Z DEBUG modem << Injected AGPS data, flags: 7, size: 16\x0D\x0A
2020-07-29T11:14:54.192Z DEBUG modem << MCC location info injected, MCC: 234\x0D\x0A
2020-07-29T11:14:54.194Z DEBUG modem << \x09Lat: 5044349 Lon: -133751\x0D\x0A
2020-07-29T11:14:54.196Z DEBUG modem << \x09Unc semiminor/semimajor: 119/119\x0D\x0A
2020-07-29T11:14:54.203Z DEBUG modem << \x09Confidence: 100\x0D\x0A
2020-07-29T11:14:54.205Z DEBUG modem << \x09Orientation: 0\x0D\x0A
2020-07-29T11:14:54.206Z DEBUG modem << SUPL POS received\x0D\x0A
2020-07-29T11:14:54.993Z DEBUG modem << Bytes received: 34, total 34\x0D
2020-07-29T11:14:55.002Z DEBUG modem << ULP ossDecode success, choice 6\x0D\x0A
2020-07-29T11:14:55.004Z DEBUG modem << SUPLEND:\x0D\x0A
2020-07-29T11:14:55.005Z DEBUG modem << \x09Mask: 0\x0D\x0A
2020-07-29T11:14:55.007Z DEBUG modem << \x09Status: 0\x0D\x0A
2020-07-29T11:14:55.008Z DEBUG modem << SUPL END received\x0D\x0A
2020-07-29T11:14:55.009Z DEBUG modem << SUPL session internal resources released\x0D\x0A
2020-07-29T11:14:55.010Z DEBUG modem << SUPL session finished\x0D\x0A
2020-07-29T11:14:55.011Z DEBUG modem << Done\x0D\x0A
2020-07-29T11:14:57.199Z DEBUG modem << \x1B[1;1H\x1B[2JTracking: 0 Using: 0 Unhealthy: 0\x0D\x0A
2020-07-29T11:14:57.208Z DEBUG modem << Seconds since last fix 81\x0D\x0A\x0D\x0A
2020-07-29T11:14:57.708Z DEBUG modem << Scanning [|] \x1B[1;1H\x1B[2JTracking: 0 Using: 0 Unhealthy: 0\x0D\x0A
2020-07-29T11:14:57.716Z DEBUG modem << Seconds since last fix 81\x0D\x0A\x0D\x0A
2020-07-29T11:14:58.215Z DEBUG modem << Scanning [/] \x1B[1;1H\x1B[2JTracking: 0 Using: 0 Unhealthy: 0\x0D

So it would appear that the issue was where I was entering the AT commands for the LTE control as I needed to set the modem to CFUN=4 to change the above characteristics. Setting them at the beginning negates the problem.

My question is then how does this work with other AT commands that overwrite the controls needed for GPS? Such as adding bandlocking for faster LTE connection and changing MAGPIO settings for platforms like the thingy:91 which require the appropiate config for MAGPIOs for the matching circuits.

EDIT:
Figured the MAGPIOs Sending AT command: AT+CFUN=21 Established LTE link ip adc2:4cc0::1101:300:1b00:1b00 Starting SUPL session ULP encoding length: 38 Bytes sent: 38 Bytes received: 34, total 34 ULP ossDecode success, choice 3 SUPL server responded using version SUPL response received ULP encoding length: 57 Bytes sent: 57 read again Bytes received: 1024, total 1024 ULP ossDecode more input 4 read again read again Bytes received: 712, total 1736 ULP ossDecode more input 4 Bytes received: 1258, total 2994 ULP ossDecode success, choice 5 Injected AGPS data, flags: 1, size: 16 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 2, size: 72 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 Injected AGPS data, flags: 3, size: 32 No integrity data available Injected AGPS data, flags: 4, size: 8 Injected AGPS data, flags: 6, size: 144 No location data available Injected AGPS data, flags: 7, size: 16 MCC location info injected, MCC: 234 Lat: 5044349 Lon: -133751 Unc semiminor/semimajor: 119/119 Confidence: 100 Orientation: 0 SUPL POS received read again read again read again Bytes received: 34, total 34 ULP ossDecode success, choice 6 SUPLEND: Mask: 0 Status: 0 SUPL END received SUPL session internal resources released SUPL session finished Done Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 90 Scanning [-] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 91 Scanning [\] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 91 Scanning [|] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 92 Scanning [/] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 92 Scanning [-] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 93 Scanning [\] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 93 Scanning [|] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 94 Scanning [/] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 94 Scanning [-] Tracking: 0 Using: 0 Unhealthy: 0 Seconds since last fix 95 Scanning [\] Tracking: 1 Using: 0 Unhealthy: 0 Seconds since last fix 95 Scanning [|] Tracking: 1 Using: 0 Unhealthy: 0 Seconds since last fix 96 Scanning [/] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 96 Scanning [-] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 97 Scanning [\] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 97 Scanning [|] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 98 Scanning [/] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 98 Scanning [-] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 99 Scanning [\] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 99 Scanning [|] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 100 Scanning [/] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 101 Scanning [-] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 101 Scanning [\] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 102 Scanning [|] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 102 Scanning [/] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 103 Scanning [-] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 103 Scanning [\] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 104 Scanning [|] Tracking: 2 Using: 0 Unhealthy: 0 Seconds since last fix 104 Scanning [/] Tracking: 3 Using: 0 Unhealthy: 0 Seconds since last fix 105 Scanning [-] Tracking: 3 Using: 0 Unhealthy: 0 Seconds since last fix 105 Scanning [\] Tracking: 3 Using: 0 Unhealthy: 0 Seconds since last fix 106 Scanning [|] Tracking: 3 Using: 0 Unhealthy: 0 Seconds since last fix 106 Scanning [/] Tracking: 3 Using: 0 Unhealthy: 0 Seconds since last fix 107 Scanning [-] Tracking: 3 Using: 0 Unhealthy: 0 Seconds since last fix 107 Scanning [\] for the thingy:91 out using the manual. Added in bandlocking to see what would happen as well.

New AGPS data requested, contacting SUPL server, flags 59 (c04cc2ad) port 7276 2.0.4

A little bit more shaky on the initial network connection but considering I'm in poor cell reception range and indoors, the results speak for themselves, 2 sats are tracked within a few seconds of GNSS resuming whilst indoors.

All that was needed was adding an extra MAGPIO config:

	#define AT_MAGPIO      "AT\%XMAGPIO=1,1,1,2,5,791,849,7,1574,1577"

RE: A-GPS download fails mid session

Simonr — Wed, 29 Jul 2020 05:12:27 GMT

Hi Michael

I've returned from vacation, so this case is back in my hands. Regarding the last file you uploaded, it doesn't seem like a valid modem trace as it's only 22kB in size while the previous ones are way larger, and myself and the R&D team assigned to this case aren't able to decode the modem trace, so you'll have to try making another trace log.

Best regards,

Simon

UPDATE: We took another look at the trace-2020-07-16T12-32-27.611Z.bin file and here it seems like the SUPL data is downloaded and forwarded correctly, and that the problem might be entering the data to GNSS. It seems like you're not activating GNSS after the data download, which might be what's causing the issue, however that's also where the trace stops, so can you confirm whether the GNSS is activated and the data entered to GNSS after the trace ends?

RE: A-GPS download fails mid session

Hakon — Mon, 27 Jul 2020 15:51:37 GMT

There is no progress yet. It seems that many of them are on vacation this week, so I might need to find someone else to look at it.

RE: A-GPS download fails mid session

MJD093 — Mon, 27 Jul 2020 15:16:53 GMT

Hi Hakon,

Have the internal team had a chance to review the new trace today?

Michael

RE: A-GPS download fails mid session

MJD093 — Fri, 24 Jul 2020 15:55:29 GMT

Thanks Hakon

RE: A-GPS download fails mid session

Hakon — Fri, 24 Jul 2020 15:29:26 GMT

Not regarding the last trace as far as I can tell. I will check again on Monday.

RE: A-GPS download fails mid session

MJD093 — Fri, 24 Jul 2020 12:26:01 GMT

Hi Hakon

Any updates?

Michael

RE: A-GPS download fails mid session

MJD093 — Wed, 22 Jul 2020 10:28:46 GMT

[quote userid="73166" url="~/f/nordic-q-a/63085/a-gps-download-fails-mid-session/261136"][/quote]

Did you get any values for +CESQ confirming this?

I don't have a log on this but using the AT client yesterday, CESQ was in the mid 30s. Around 34 RSRP so decently higher than before.

RE: A-GPS download fails mid session

Hakon — Wed, 22 Jul 2020 08:53:23 GMT

[quote user="MJD093"]There should be some improvement in the signal strength in this attempt but it still failed out as shown above.[/quote]

Did you get any values for +CESQ confirming this?

I'll have the modem team look at the trace.

RE: A-GPS download fails mid session

MJD093 — Tue, 21 Jul 2020 16:37:02 GMT

I happen to be in the office today and I have my colleagues v0.8.5 DK instead of my usual DK.

There should be some improvement in the signal strength in this attempt but it still failed out as shown above.

(I believe I followed the trace set-up steps for the modem correctly for this DK)

devzone.nordicsemi.com/.../trace_2D00_2020_2D00_07_2D00_21T16_2D00_31_2D00_26.836Z.bin

RE: A-GPS download fails mid session

Hakon — Tue, 21 Jul 2020 16:21:40 GMT

[quote userid="75438" url="~/f/nordic-q-a/63085/a-gps-download-fails-mid-session/261040"]My application requires at least values of 21 RSRP before I will allow the device to initiate UDP transfers or FOTA.[/quote]

21 seems too low. The product spec gives the following values for RX sensitivity...

"RX sensitivity: -108 dBm for Cat-M1 and -114 dBm for Cat-NB1 and Cat-NB2"

21 corresponds to -119 dBm. For NB-IoT you should stay above 26.

RE: A-GPS download fails mid session

MJD093 — Tue, 21 Jul 2020 16:10:12 GMT

Hi Hakon

I work from home a lot, I live in the countryside and the transmitter would be expected to run at max TX power due to low signal strength. AT logs show that I can still achieve at least values as shown below for the RSRP:

Sending AT command: AT+CESQ                                                     
Modem response: +CESQ: 99,99,255,255,22,23

Is there an expected minimum value of RSRP that is required to improve success rates? My application requires at least values of 21 RSRP before I will allow the device to initiate UDP transfers or FOTA. It would be expected to do the same when I impliment A-GPS into my radio scheduler code in the future.

RE: A-GPS download fails mid session

Hakon — Tue, 21 Jul 2020 16:03:23 GMT

A couple of things have been mentioned since last time...

"Looking at his log in devzone the SUPL connection was totally unsuccessful, and not similar to the previous case.

The modem trace shows to me that transmitter is requested to send at full power which indicates a poor connection. Strange is that RX SNR is still positive +4dB which should be good enough."

And there is a discussion about what is happening in the trace I'm assuming, but that would be internal information so I can't share it.

RE: A-GPS download fails mid session

MJD093 — Tue, 21 Jul 2020 15:10:16 GMT

Hi Hakon,

Has there been any word on this issue. I appreciate that the recent holidays have caused disruptions but we really need a resolution for this issue ASAP. It's been 25 days since we wanted to improve our custom devices with A-GPS.

Michael

RE: A-GPS download fails mid session

MJD093 — Fri, 17 Jul 2020 15:36:25 GMT

Is there anything I can add to the sample that will prevent the GPS side of the application from failing to utilise cold start GPS locating after a failed A-GPS run. I'd imagine that even a successful A-GPS download would fail to start the GPS socket as well.

As I mentioned, the GPS code on it's own works fine so it's whatever is going in the handover between the LTE and GPS configs.

RE: A-GPS download fails mid session

Hakon — Fri, 17 Jul 2020 15:31:21 GMT

[quote user="MJD093"]Does the code call CFUN=20 correctly in the trace after A-GPS failure?[/quote]

Yes that is called and LTE is turned off. Modem still seems to do some wakeups every 1.28 seconds.

RE: A-GPS download fails mid session

Hakon — Fri, 17 Jul 2020 12:57:06 GMT

Thanks for the log, I will forward it for analysis.

RE: A-GPS download fails mid session

MJD093 — Thu, 16 Jul 2020 12:44:03 GMT

I was using the SDK v1.2.0 to do this testing. I have updated to v1.3.0 and attached a modem trace below. Please let me know if there are any issues with the trace.

devzone.nordicsemi.com/.../trace_2D00_2020_2D00_07_2D00_16T12_2D00_32_2D00_27.611Z.bin

For reference, the GPS application is modified to use an AT command array with the following commands, without this LTE set-up, the SIM Cards will never make a connection to the network.

#define AT_CFUN_OFF						"AT+CFUN=4"
#define AT_APN_zzzz					"AT+CGDCONT=0,\"IP\",\"ep.inetd.gdsp\""
#define AT_MAGPIO_LTE      			    "AT\%XMAGPIO=1,1,1,1,5,791,849"
#define AT_BANDLOCK						"AT\%XBANDLOCK=1,\"10000000000000000000\""
#ifdef CONFIG_BOARD_NRF9160DK_NRF9160NS
	#define AT_MAGPIO                   "AT\%XMAGPIO=1,0,0,1,1,1574,1577"
	#define AT_COEX0                    "AT\%XCOEX0=1,1,1570,1580"
	#define AT_APN_xxx				"AT+CGDCONT=0,\"IP\",\"xxx.com\""
	#define AT_xxxx_USER_PASS		"AT+CGAUTH=0,\"PAP\",\"xxx\",\"xxx\""
	#define AT_LEG_PCO					"AT\%XEPCO=1"
#endif

static const char     at_commands_NB[][50]  = {
				AT_CFUN_OFF,
				AT_XSYSTEMMODE,
#ifdef CONFIG_BOARD_NRF9160DK_NRF9160NS
				//AT_MAGPIO_LTE,
				AT_BANDLOCK,
				AT_APN_xxx,
				AT_xxx_USER_PASS,
				AT_LEG_PCO,
#endif
				AT_ACTIVATE_LTE
			};
			
static int activate_lte(bool activate)
{
	if (activate) {
		for (int i = 0; i < ARRAY_SIZE(at_commands_NB); i++) {
			if (at_cmd_write(at_commands_NB[i], NULL, 0, NULL) != 0) {
				printk("Error with at_commands_NB\n");
				return -1;
			}
		}

		at_notif_register_handler(NULL, wait_for_lte);
		if (at_cmd_write("AT+CEREG=2", NULL, 0, NULL) != 0) {
			printk("Error with wait_for_lte 1\n");
			return -1;
		}

		k_sem_take(&lte_ready, K_FOREVER);

		at_notif_deregister_handler(NULL, wait_for_lte);
		if (at_cmd_write("AT+CEREG=0", NULL, 0, NULL) != 0) {
			printk("Error with wait_for_lte 2\n");
			return -1;
		}
	} else {
		if (at_cmd_write(AT_DEACTIVATE_LTE, NULL, 0, NULL) != 0) {
			printk("Error with AT_DEACTIVATE_LTE\n");
			return -1;
		}
	}

	return 0;
}

I have tried with and without setting legecy PCO on v1.3.0 as mentioned to try by Simonr in an earlier reply and had no success.

Note:

I have had a couple instances today of this:

New AGPS data requested, contacting SUPL server, flags 59
Sending AT command: AT+CFUN=4
Sending AT command: AT%XSYSTEMMODE=0,1,1,0
Sending AT command: AT%XBANDLOCK=1,"10000000000000000000"
Sending AT command: AT+CGDCONT=0,"IP","xxx.com"
Sending AT command: AT+CGAUTH=0,"PAP","xxx","xxx"
Sending AT command: AT%XEPCO=1
Sending AT command: AT+CFUN=21
Established LTE link
ip 40e9:a6c0::1001:300:1b00:1b00 (c0a6e940) port 7276
Starting SUPL session
ULP encoding length: 38
Bytes sent: 38
read again
read again
read again
read error: -1
SUPL error: 1
ULP encoding length: 18
Sending SUPL message failed, bytes_sent: -1
SUPL session internal resources released
Done
Failed to start GPS

The last line of GPS failure to start is appearing in the v1.3.0 example, I not sure why but I have played around in the AT client and can see that swapping between AT+CFUN=21 and 31 can ERROR out so I believe that may be the issue. Does the code call CFUN=20 correctly in the trace after A-GPS failure? GPS starts and works as normal when SUPL is not configured 'y' in the prj.conf

RE: A-GPS download fails mid session

Hakon — Wed, 15 Jul 2020 13:47:23 GMT

Are you using the newest version of A-GPS sample? There seems to be an issue with A-GPS injection possibly being intercepted by GNSS search. Can you please capture a modem log? Just follow these instructions.

RE: A-GPS download fails mid session

Hakon — Wed, 15 Jul 2020 08:29:05 GMT

Hello,

not Simon, but I'm handling the case while he is away. Those that were working on your problem are on vacation now, so I got someone else to take over. Hopefully you will get an answer today or in the near future.

RE: A-GPS download fails mid session

MJD093 — Mon, 06 Jul 2020 10:46:20 GMT

Hi Simonr,
Has any progress been made internally on this issue?

Michael

RE: A-GPS download fails mid session

MJD093 — Tue, 30 Jun 2020 12:07:38 GMT

Thank you Simonr

RE: A-GPS download fails mid session

Simonr — Tue, 30 Jun 2020 10:55:23 GMT

I've forwarded this issue internally to confirm whether this might be due to TCP not cooperating with NB-IoT or not (and hopefully find a fix or workaround to this issue). Please note that we are moving into the summer vacation period here in Norway, so it might take a bit longer to get to the bottom of this than expected, as staff during the month of July will be reduced. I'm sorry about the inconvenience, but please be patient. And I'll get back to you as soon as I hear something from the devs.

Best regards,

Simon

RE: A-GPS download fails mid session

MJD093 — Mon, 29 Jun 2020 13:47:24 GMT

UPDATE:
I added in the command to change to legacy PCO:

#define AT_LEG_PCO							"AT\%XEPCO=0"

Unfortunately, it doesn't seem to have made any improvements. (strerror() response is in this log)

Scanning [/] [1;1H[2J
New AGPS data requested, contacting SUPL server, flags 59
Established LTE link
ip 4a7d:8cc0:: (c08c7d4a) port 7276
Starting SUPL session
ULP encoding length: 38
Bytes sent: 38
Bytes received: 34
ULP ossDecode success, choice 3
SUPL server responded using version 2.0.4
SUPL response received
ULP encoding length: 57
Bytes sent: 57
Bytes received: 708
ULP ossDecode more input 4
Bytes received: 1416
ULP ossDecode more input 4
Bytes received: 2124
ULP ossDecode more input 4
Bytes received: 2994
ULP ossDecode success, choice 5
Failed to send AGNSS data, type: 1 (err: 5|I/O error)
UTC conversion/injection failed, rc: 3
Generic assistance data injection failed, rc: 3
SUPL error: 2
ULP encoding length: 34
Bytes sent: 34
SUPL session internal resources released
SUPL session finished
Done