Change destination server for agps code

RE: Change destination server for agps code

Marte Myrvold — Wed, 06 Jan 2021 07:53:27 GMT

Hi,

Is the problem that you're unable to get A-GPS data, or that you're unable to send it to your AWS server? Have you tried printing the A-GPS data to make sure it works? Have you tried sending another message to make sure publishing to your AWS server works?

Best regards,

Marte

RE: Change destination server for agps code

Rkidechaa — Tue, 05 Jan 2021 00:00:55 GMT

Hi,

I made the above changes but did not receive the GPS data on the AWS server.

We have connected to our own AWS server by using the AWS_IOT sample code. Now need to send the GPS data so i referred the AGPS code.

I merged the AWS and AGPS code but did not get output on the server. Can you help us out?

RE: Change destination server for agps code

Marte Myrvold — Mon, 04 Jan 2021 06:21:22 GMT

Hi,

Great to hear that you successfully connected to the server now!
Yes, you have to enable AGPS_SRC_SUPL in order to use an external SUPL client for A-GPS. The A-GPS data can be sent to your ASW cloud server using MQTT as in the AWS IoT sample.

Best regards,

Marte

RE: Change destination server for agps code

Rkidechaa — Thu, 31 Dec 2020 16:34:49 GMT

Hi,

Finally, I successfully connected to my own AWS cloud server using AWS_IOT sample code.

Now, what needs to be changed in AGPS code to send the data to the AWS cloud. will do configuration setting for AWS IOT

what else?

Do i need to enable CONFIG_AGPS_SRC_SUPL in prj file?

RE: Change destination server for agps code

Marte Myrvold — Mon, 28 Dec 2020 13:07:48 GMT

Hi,

mqtt_connect error -22 indicates that you're not able to connect to the AWS IoT broker.

Which version of NCS are you using?

[quote user="Rkidechaa"]Do I need to do any other changes to the main.c file or any prj file except you mentioned in Readme file?[/quote]

You have to complete the steps in the setup, like setting up an AWS account and a connection to AWS IoT. Besides this, you shouldn't have to make any changes to the files except the ones mentioned (CONFIG_AWS_IOT_BROKER_HOST_NAME, CONFIG_AWS_IOT_SEC_TAG, and CONFIG_AWS_IOT_CLIENT_ID_STATIC to reflect the values retrieved when setting up the AWS account).

The sample might require increasing the values of CONFIG_AWS_IOT_MQTT_RX_TX_BUFFER_LEN and CONFIG_AWS_IOT_MQTT_PAYLOAD_BUFFER_LEN, but I don't see how this will affect the initial connection to the broker.

Which version of the modem firmware are you using? You can find newer versions here.

Could you provide a modem trace showing the problem?

Best regards,

Marte

RE: Change destination server for agps code

Rkidechaa — Fri, 25 Dec 2020 03:13:09 GMT

Hi,

[quote userid="92402" url="~/f/nordic-q-a/69490/change-destination-server-for-agps-code/286464#286464"]Please be aware that we have reduced staff due to holiday season, so response time might be slower than normal.[/quote]

I can understand and really appreciate your effort.

I checked the AWS_IOT sample code which is intended to connect the aws_IOT cloud and display the messages. we have made the changes mentioned in Readme file. We added the certificate and sec tag too.

After the changes, we load the code and checked on the link monitor.please check Below:

2020-12-25T02:48:20.900Z DEBUG modem >> AT%CMNG=0,201,0,"MIIDQTCCAimgAwIBAgITBmyfz5m/jAo54vB4ikPmljZbyjANBgkqhkiG9w0BAQsF\n
2020-12-25T02:48:20.915Z DEBUG modem >> ADA5MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6\n
2020-12-25T02:48:20.930Z DEBUG modem >> b24gUm9vdCBDQSAxMB4XDTE1MDUyNjAwMDAwMFoXDTM4MDExNzAwMDAwMFowOTEL\n
2020-12-25T02:48:20.951Z DEBUG modem >> MAkGA1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJv\n
2020-12-25T02:48:20.967Z DEBUG modem >> b3QgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALJ4gHHKeNXj\n
2020-12-25T02:48:20.994Z DEBUG modem >> ca9HgFB0fW7Y14h29Jlo91ghYPl0hAEvrAIthtOgQ3pOsqTQNroBvo3bSMgHFzZM\n
2020-12-25T02:48:21.009Z DEBUG modem >> 9O6II8c+6zf1tRn4SWiw3te5djgdYZ6k/oI2peVKVuRF4fn9tBb6dNqcmzU5L/qw\n
2020-12-25T02:48:21.024Z DEBUG modem >> IFAGbHrQgLKm+a/sRxmPUDgH3KKHOVj4utWp+UhnMJbulHheb4mjUcAwhmahRWa6\n
2020-12-25T02:48:21.040Z DEBUG modem >> VOujw5H5SNz/0egwLX0tdHA114gk957EWW67c4cX8jJGKLhD+rcdqsq08p8kDi1L\n
2020-12-25T02:48:21.057Z DEBUG modem >> 93FcXmn/6pUCyziKrlA4b9v7LWIbxcceVOF34GfID5yHI9Y/QCB/IIDEgEw+OyQm\n
2020-12-25T02:48:21.073Z DEBUG modem >> jgSubJrIqg0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMC\n
2020-12-25T02:48:21.092Z DEBUG modem >> AYYwHQYDVR0OBBYEFIQYzIU07LwMlJQuCFmcx7IQTgoIMA0GCSqGSIb3DQEBCwUA\n
2020-12-25T02:48:21.108Z DEBUG modem >> A4IBAQCY8jdaQZChGsV2USggNiMOruYou6r4lK5IpDB/G/wkjUu0yKGX9rbxenDI\n
2020-12-25T02:48:21.125Z DEBUG modem >> U5PMCCjjmCXPI6T53iHTfIUJrU6adTrCC2qJeHZERxhlbI1Bjjt/msv0tadQ1wUs\n
2020-12-25T02:48:21.142Z DEBUG modem >> N+gDS63pYaACbvXy8MWy7Vu33PqUXHeeE6V/Uq2V8viTO96LXFvKWlJbYK8U90vv\n
2020-12-25T02:48:21.229Z DEBUG modem >> o/ufQJVtMVT8QtPHRh8jrdkPSHCa2XV4cdFyQzR1bldZwgJcJmApzyMZFo6IQ6XU\n
2020-12-25T02:48:21.243Z DEBUG modem >> 5MsI+yMRQ+hDKXJioaldXgjUkK642M4UwtBV8ob2xJNDd2ZhwLnoQdeXeGADbkpy\n
2020-12-25T02:48:21.258Z DEBUG modem >> rqXRfboQnoZsG4q5WTP468SQvvG5\n"
2020-12-25T02:48:21.437Z DEBUG modem << OK
2020-12-25T02:48:21.441Z INFO Updating client certificate...
2020-12-25T02:48:21.442Z DEBUG modem >> AT%CMNG=0,201,1,"MIIDWTCCAkGgAwIBAgIUfmLe0K7GkGsVXcvC0xcXgvrrEkIwDQYJKoZIhvcNAQEL\n
2020-12-25T02:48:21.461Z DEBUG modem >> BQAwTTFLMEkGA1UECwxCQW1hem9uIFdlYiBTZXJ2aWNlcyBPPUFtYXpvbi5jb20g\n
2020-12-25T02:48:21.477Z DEBUG modem >> SW5jLiBMPVNlYXR0bGUgU1Q9V2FzaGluZ3RvbiBDPVVTMB4XDTIwMTIyNDAzNDk0\n
2020-12-25T02:48:21.494Z DEBUG modem >> OVoXDTQ5MTIzMTIzNTk1OVowHjEcMBoGA1UEAwwTQVdTIElvVCBDZXJ0aWZpY2F0\n
2020-12-25T02:48:21.510Z DEBUG modem >> ZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALz732T+tCgER2y5nn21\n
2020-12-25T02:48:21.526Z DEBUG modem >> 0Pk+O6cXYy9yOGv0kL5oJkTQ4YLPFAlHgr8KrXW/v1JGgT6NirsuhQZX8G7IXet2\n
2020-12-25T02:48:21.549Z DEBUG modem >> q7ygMa5kW39vzwVSA6ThmZGV7ffGh4f/tIQ4y94BUf2ZSAYLXiXzItUnKWoeEhH2\n
2020-12-25T02:48:21.564Z DEBUG modem >> /7GaJpDkjJ+loFdRoJaYiwuhD5izE2pGRgMORaOHj3PS9bCaLjY6YXBMm9Js13XL\n
2020-12-25T02:48:21.577Z DEBUG modem >> m6U6tIbTqav3XQbYXouW0161eT7CbBJQftJus/4ZPNqJzyuIOTmDh1yvlf2ohz3P\n
2020-12-25T02:48:21.594Z DEBUG modem >> QCX0CB7IKCFwSEPrIPPOOESCdT+p19tfhZS3K/UCHL0MOskM7r1iXeMquMfQGre5\n
2020-12-25T02:48:21.611Z DEBUG modem >> qSkCAwEAAaNgMF4wHwYDVR0jBBgwFoAUgjvxMWwRS5zRp5CsMtNiIehI8P4wHQYD\n
2020-12-25T02:48:21.704Z DEBUG modem >> VR0OBBYEFKkkABIKWFw3Ed1YTSkMu4qAUrFaMAwGA1UdEwEB/wQCMAAwDgYDVR0P\n
2020-12-25T02:48:21.720Z DEBUG modem >> AQH/BAQDAgeAMA0GCSqGSIb3DQEBCwUAA4IBAQBKlYnhzpfzw+Fo2avO81llZFXq\n
2020-12-25T02:48:21.737Z DEBUG modem >> cfpl5/GBwXtpJtFAHXShUpk4sxmsKP7pTdkMNhOPmZ5fSGbN7eV63ZJ0v7dwAgFz\n
2020-12-25T02:48:21.753Z DEBUG modem >> OJ9mVTQh/RIA+I0w3x5JO+/oXCjWuGScURa4bhTXAL3L+VZ4HGjKrygRgfpMANTh\n
2020-12-25T02:48:21.772Z DEBUG modem >> 3svwXpBvx5Uq11Sip8Fda9Av1JJbZLkz4WCD7Y3dXHpcP2GdCWkilpOzqM+mOCv7\n
2020-12-25T02:48:21.787Z DEBUG modem >> quYiK6l91h6OQO8PWRF9k0nr8DUfT4JRSZ+mbgBVyBMBi3l8/0+dPFqhTQdr5fgP\n
2020-12-25T02:48:21.804Z DEBUG modem >> 7kMBp9BRpTMtNwXktDgdySxOsPgczEb41aaUtVfFBc4nc1I+XDIWIK2Na3il\n"
2020-12-25T02:48:21.978Z DEBUG modem << OK
2020-12-25T02:48:21.979Z INFO Updating private key...
2020-12-25T02:48:21.981Z DEBUG modem >> AT%CMNG=0,201,2,"MIIEowIBAAKCAQEAvPvfZP60KARHbLmefbXQ+T47pxdjL3I4a/SQvmgmRNDhgs8U\n
2020-12-25T02:48:21.992Z DEBUG modem >> CUeCvwqtdb+/UkaBPo2Kuy6FBlfwbshd63arvKAxrmRbf2/PBVIDpOGZkZXt98aH\n
2020-12-25T02:48:22.006Z DEBUG modem >> h/+0hDjL3gFR/ZlIBgteJfMi1Scpah4SEfb/sZomkOSMn6WgV1GglpiLC6EPmLMT\n
2020-12-25T02:48:22.020Z DEBUG modem >> akZGAw5Fo4ePc9L1sJouNjphcEyb0mzXdcubpTq0htOpq/ddBthei5bTXrV5PsJs\n
2020-12-25T02:48:22.033Z DEBUG modem >> ElB+0m6z/hk82onPK4g5OYOHXK+V/aiHPc9AJfQIHsgoIXBIQ+sg8844RIJ1P6nX\n
2020-12-25T02:48:22.051Z DEBUG modem >> 21+FlLcr9QIcvQw6yQzuvWJd4yq4x9Aat7mpKQIDAQABAoIBAQCD904z9DhRiUtm\n
2020-12-25T02:48:22.069Z DEBUG modem >> /OdT2Van9XEqaQZ150jG+ezpSUkP3Nzcv0W6hRkj1ozyIIe1KE6wI56wvvddSqM2\n
2020-12-25T02:48:22.160Z DEBUG modem >> eOw8tI2QFj0bDjFmd+kUSgUJahAWvZ+C2jtiGIkxm4eg60MZ16OXtPB1h6bXOZWN\n
2020-12-25T02:48:22.178Z DEBUG modem >> 6JmtudErb/1mSHJ6OOoSj4mYH8VYxFdkRU9TbHLg7nqNDiSeIBQn051B95UZqL01\n
2020-12-25T02:48:22.193Z DEBUG modem >> jXYEhmZ+aMXYmwuI74OK4O9RJTKMyMyecQ9rbsviud9qq9oj59WRrfs+VmcSLCYN\n
2020-12-25T02:48:22.209Z DEBUG modem >> hyAaV/lBhHzn4hsrcC/RgNubs/EYYKkPEvWA9NHOiGYnJEYS5rFqfZ4GKHjXrkdx\n
2020-12-25T02:48:22.225Z DEBUG modem >> zFeINphRAoGBAOyAkN3Wq1Ne9w9sxZl6jXnJxyZ7cT3dTYJWqa7P+OGtVLChLK4x\n
2020-12-25T02:48:22.241Z DEBUG modem >> NDlAQr2RJQxxN+IbMYXV/XiUNJYZgObx0uPr5MUuq13SXdown3KxmJBY7y9MpcP9\n
2020-12-25T02:48:22.258Z DEBUG modem >> pe6/+GkPo9lZZS3XDX4zuwxqGJgO7f6U7sESx4kKERAeB5V+GcroUJqXAoGBAMyQ\n
2020-12-25T02:48:22.275Z DEBUG modem >> a9mQUTrAAgZgmKVgBD8Em44KurCC9xhrQaxW/chfrlIdXNnZWXqrX31jrKBz7V8R\n
2020-12-25T02:48:22.292Z DEBUG modem >> 24ME6OaBgDUu13Pqic0lFMItKNGUDpr3aIxRAdZvbyPjnYHkC7aQ/UX++V0U8nGi\n
2020-12-25T02:48:22.313Z DEBUG modem >> DInf+K4LNsupVmNB4zrUaqCjpAKFFKSvnLTgwxI/AoGAEPBsb9cuUjxdCbfKt2F1\n
2020-12-25T02:48:22.332Z DEBUG modem >> vKFdKD5zL/En2gwG/0RaGR/nDvecUaWojekyXo2Ez81UKVe1Rla7XuWOlqmg9+me\n
2020-12-25T02:48:22.349Z DEBUG modem >> J0EAE7dyArhMjJIq+XYK7VvRVdvxi4YhWmZZjnzWSX0DqDLc/osJ/Kuks09ucGuO\n
2020-12-25T02:48:22.367Z DEBUG modem >> ZjnIHOKhsjvUYzqy8juNemUCgYBZZUO8cDUPV5mK7+vFWZCBeaIBEO9E8/bH1Rd+\n
2020-12-25T02:48:22.383Z DEBUG modem >> GQYO6sFjYTGSgkl4Miwov8ZQ2FiDk2o6d4rQMQe2NiIxpe1SmUHZGaMc83bugfBO\n
2020-12-25T02:48:22.399Z DEBUG modem >> YZhL/aa0KGRMvzvfLL2COUsAQocw4YBZQGeMp5nqprX56nFC5FE0ok6qSz4aOiRh\n
2020-12-25T02:48:22.417Z DEBUG modem >> Z1fYQQKBgF2XX/ZJ+1/r1KU/KgSs84TLTUx4nkB3PNkDCYeOw8C02crlOUP4Eyhc\n
2020-12-25T02:48:22.435Z DEBUG modem >> ZvjXRyEzp7JOoKWn8xFCDPt0yD+XqEC8LPI/YmmdZTwmY9L9p4g4eK8ODJrA83aU\n
2020-12-25T02:48:22.449Z DEBUG modem >> w6FHJu04l36nM8A+tsLzg7WDwo1n4OcHjC0WRGzfVN0D2OB/86PN\n"
2020-12-25T02:48:24.091Z DEBUG modem << OK
2020-12-25T02:48:24.094Z INFO Certificate update completed
2020-12-25T02:48:39.950Z DEBUG modem << Next connection retry in 30 seconds
2020-12-25T02:48:39.954Z DEBUG modem << AWS_IOT_EVT_CONNECTING

2020-12-25T02:48:40.023Z DEBUG modem << E: getaddrinfo, error -11
2020-12-25T02:48:40.026Z DEBUG modem << E: client_broker_init, error: -10
2020-12-25T02:48:40.029Z DEBUG modem << E: mqtt_connect, error: -22
2020-12-25T02:48:40.032Z DEBUG modem << AWS_IOT_EVT_CONNECTING

Now I am getting above error. And got stuck.

Do I need to do any other changes to the main.c file or any prj file except you mentioned in Readme file?

RE: Change destination server for agps code

Marte Myrvold — Wed, 23 Dec 2020 13:16:01 GMT

Hi,

Error -95 is EUPNOTSUPP, which is "operation not supported on transport endpoint", and from your log I can see that you're able to connect to the network, but not to AWS cloud. Are your certificates and your sec tag correct, are they the same as for your device on AWS IoT? You check out creating a thing in AWS IoT.

Please be aware that we have reduced staff due to holiday season, so response time might be slower than normal.

Best regards,

Marte

RE: Change destination server for agps code

Rkidechaa — Tue, 22 Dec 2020 23:04:37 GMT

HI,

As mentioned I have made changes in prj file of the cloud client sample. changes are mentioned below:

1) change the cloud backend to the AWS_IOT

2) Enable AWS IOT setting and added ID, HOSTNAME and SEC TAG.

3) Updated the modem certificates.

after that when build and run the code got below output.

2020-12-22T22:46:26.583Z INFO Application data folder: C:\Users\rahul\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2020-12-22T22:46:26.608Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2020-12-22T22:46:26.608Z DEBUG App path: C:\Users\rahul\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2020-12-22T22:46:26.608Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2020-12-22T22:46:26.608Z DEBUG nRFConnect path: C:\Users\rahul\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-12-22T22:46:26.608Z DEBUG HomeDir: C:\Users\rahul
2020-12-22T22:46:26.608Z DEBUG TmpDir: C:\Users\rahul\AppData\Local\Temp
2020-12-22T22:46:35.543Z INFO Modem port is opened
2020-12-22T22:46:35.548Z DEBUG modem >> AT+CFUN?
2020-12-22T22:46:35.566Z DEBUG modem << +CFUN: 1
2020-12-22T22:46:35.568Z DEBUG modem << OK
2020-12-22T22:46:35.581Z DEBUG modem >> AT+CGSN=1
2020-12-22T22:46:35.592Z DEBUG modem << +CGSN: "352656101080789"
2020-12-22T22:46:35.594Z DEBUG modem << OK
2020-12-22T22:46:35.599Z DEBUG modem >> AT+CGMI
2020-12-22T22:46:35.607Z DEBUG modem << Nordic Semiconductor ASA
2020-12-22T22:46:35.608Z DEBUG modem << OK
2020-12-22T22:46:35.613Z DEBUG modem >> AT+CGMM
2020-12-22T22:46:35.620Z DEBUG modem << nRF9160-SICA
2020-12-22T22:46:35.621Z DEBUG modem << OK
2020-12-22T22:46:35.624Z DEBUG modem >> AT+CGMR
2020-12-22T22:46:35.633Z DEBUG modem << mfw_nrf9160_1.2.0
2020-12-22T22:46:35.635Z DEBUG modem << OK
2020-12-22T22:46:35.636Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.2.0] SerNr: 352656101080789
2020-12-22T22:46:35.641Z DEBUG modem >> AT+CEMODE?
2020-12-22T22:46:35.648Z DEBUG modem << +CEMODE: 2
2020-12-22T22:46:35.650Z DEBUG modem << OK
2020-12-22T22:46:35.664Z DEBUG modem >> AT%XCBAND=?
2020-12-22T22:46:35.675Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,18,19,20,25,26,28,66)
2020-12-22T22:46:35.678Z DEBUG modem << OK
2020-12-22T22:46:35.688Z DEBUG modem >> AT+CMEE?
2020-12-22T22:46:35.694Z DEBUG modem << +CMEE: 0
2020-12-22T22:46:35.696Z DEBUG modem << OK
2020-12-22T22:46:35.699Z DEBUG modem >> AT+CMEE=1
2020-12-22T22:46:35.705Z DEBUG modem << OK
2020-12-22T22:46:35.709Z DEBUG modem >> AT+CNEC?
2020-12-22T22:46:35.717Z DEBUG modem << +CNEC: 0
2020-12-22T22:46:35.718Z DEBUG modem << OK
2020-12-22T22:46:35.721Z DEBUG modem >> AT+CNEC=24
2020-12-22T22:46:35.726Z DEBUG modem << OK
2020-12-22T22:46:35.729Z DEBUG modem >> AT+CGEREP?
2020-12-22T22:46:35.738Z DEBUG modem << +CGEREP: 0,0
2020-12-22T22:46:35.741Z DEBUG modem << OK
2020-12-22T22:46:35.745Z DEBUG modem >> AT+CGDCONT?
2020-12-22T22:46:35.753Z DEBUG modem << +CGDCONT: 0,"IP","","",0,0
2020-12-22T22:46:35.754Z DEBUG modem << OK
2020-12-22T22:46:35.763Z DEBUG modem >> AT+CGACT?
2020-12-22T22:46:35.770Z DEBUG modem << +CGACT: 0,0
2020-12-22T22:46:35.771Z DEBUG modem << OK
2020-12-22T22:46:35.775Z DEBUG modem >> AT+CGEREP=1
2020-12-22T22:46:35.781Z DEBUG modem << OK
2020-12-22T22:46:35.787Z DEBUG modem >> AT+CIND=1,1,1
2020-12-22T22:46:35.793Z DEBUG modem << OK
2020-12-22T22:46:35.797Z DEBUG modem >> AT+CEREG=5
2020-12-22T22:46:35.803Z DEBUG modem << OK
2020-12-22T22:46:35.807Z DEBUG modem >> AT+CEREG?
2020-12-22T22:46:35.818Z DEBUG modem << +CEREG: 5,2,"8402","02066D02",7,0,0,"11100000","11100000"
2020-12-22T22:46:35.820Z DEBUG modem << OK
2020-12-22T22:46:35.830Z DEBUG modem >> AT%CESQ=1
2020-12-22T22:46:35.835Z DEBUG modem << OK
2020-12-22T22:46:35.839Z DEBUG modem >> AT+CESQ
2020-12-22T22:46:35.847Z DEBUG modem << +CESQ: 99,99,255,255,8,39
2020-12-22T22:46:35.848Z DEBUG modem << OK
2020-12-22T22:46:35.853Z DEBUG modem >> AT%XSIM=1
2020-12-22T22:46:35.863Z DEBUG modem << OK
2020-12-22T22:46:35.867Z DEBUG modem >> AT%XSIM?
2020-12-22T22:46:35.875Z DEBUG modem << %XSIM: 1
2020-12-22T22:46:35.877Z DEBUG modem << OK
2020-12-22T22:46:35.888Z DEBUG modem >> AT+CPIN?
2020-12-22T22:46:35.897Z DEBUG modem << +CPIN: READY
2020-12-22T22:46:35.898Z DEBUG modem << OK
2020-12-22T22:46:35.906Z DEBUG modem >> AT+CPINR="SIM PIN"
2020-12-22T22:46:35.920Z DEBUG modem << +CPINR: "SIM PIN",3
2020-12-22T22:46:35.921Z DEBUG modem << OK
2020-12-22T22:46:35.927Z DEBUG modem >> AT+CIMI
2020-12-22T22:46:35.935Z DEBUG modem << 204080813563573
2020-12-22T22:46:35.936Z DEBUG modem << OK
2020-12-22T22:46:35.936Z INFO IMSIdentity: 204080813563573
2020-12-22T22:46:36.299Z DEBUG modem << +CGEV: ME PDN ACT 0,0
2020-12-22T22:46:36.302Z DEBUG modem << +CNEC_ESM: 50,0
2020-12-22T22:46:36.308Z DEBUG modem >> AT+CGDCONT?
2020-12-22T22:46:36.309Z DEBUG modem << +CEREG: 5,"8402","02066D02",7,,,"11100000","11100000"
2020-12-22T22:46:36.310Z DEBUG modem << I: Network registration status: Connected - roaming
2020-12-22T22:46:36.311Z DEBUG modem << I: Connected to LTE network
2020-12-22T22:46:36.311Z DEBUG modem << I: Connecting to cloud
2020-12-22T22:46:36.312Z DEBUG modem << I: Next connection retry in 30 seconds
2020-12-22T22:46:36.313Z DEBUG modem << +CIND: "service",1
2020-12-22T22:46:36.314Z DEBUG modem << +CIND: "roam",1
2020-12-22T22:46:36.314Z DEBUG modem << I: CLOUD_EVT_CONNECTING
2020-12-22T22:46:36.321Z DEBUG modem << +CGDCONT: 0,"IP","ibasis.iot","10.165.46.0",0,0
2020-12-22T22:46:36.322Z DEBUG modem << OK
2020-12-22T22:46:36.325Z DEBUG modem >> AT+CGACT?
2020-12-22T22:46:36.335Z DEBUG modem << +CGACT: 0,1
2020-12-22T22:46:36.336Z DEBUG modem << OK

2020-12-22T22:46:36.692Z DEBUG modem << E: mqtt_connect, error: -95
2020-12-22T22:46:36.693Z DEBUG modem << I: CLOUD_EVT_CONNECTING
2020-12-22T22:46:39.126Z DEBUG modem << %CESQ: 39,1,3,0
2020-12-22T22:46:39.726Z DEBUG modem << %CESQ: 34,1,3,0

If you see the last four lines getting one error and it always stuck at CLOUD_EVT_CONNECTING.

In the cloud client sample, it displays the message on the nrf cloud terminal. Does the same thing suppose to happen on the AWS cloud?

But it did not display anything? Do I miss any other setting in prj file or on AWS CLOUD?

RE: Change destination server for agps code

Marte Myrvold — Tue, 22 Dec 2020 07:47:09 GMT

Hi,

The security tag can be chosen as whatever you want it to be, however, the default security tag 16842753 is reserved for the nRF Cloud. This tag is set when you program the certificates to the on-board modem.

Have you read the documentation for the AWS IoT library? The simplest way to do this in your project, would probably be to change the example such that you send the A-GPS data (which you get from the external SUPL client) over MQTT to the AWS IoT message broker. How to set up this is described in the documentation for the AWS IoT library, from the part about initializing and out. There's also an AWS IoT sample that shows how to do this as well.

Best regards,

Marte

RE: Change destination server for agps code

Rkidechaa — Sat, 19 Dec 2020 08:18:23 GMT

Hi,

I was referring to the cloud client sample and made changes in the AWS IoT library but I don understand what should put in

CONFIG_AWS_IOT_SEC_TAG

please let me know from where i will get Tag value?

[quote userid="92402" url="~/f/nordic-q-a/69490/change-destination-server-for-agps-code/285083#285083"] AWS IoT library [/quote]

Also while referring to AWS IoT library can you tell me where exactly because i have done changes in prj file.

RE: Change destination server for agps code

Rkidechaa — Sat, 19 Dec 2020 07:17:41 GMT

Hi Marte,

Thank you for your reply.

But if you could help me with the proper steps it would be grateful. This everything is pretty much new for me.

Rahul Kidecha

RE: Change destination server for agps code

Marte Myrvold — Tue, 15 Dec 2020 13:07:17 GMT

Hi,

In order to send the GPS data to another server, you have to change the cloud backend to AWS, and change the endpoint and device ID, as well as any other requirements by AWS. I would recommend taking a look at the Cloud client sample, which shows how to connect to, and communicate with a cloud service using a cloud backend firmware library. This sample supports the AWS IoT library already. In prj.conf in the cloud client sample, you'll find the necessary configurations for AWS under 'AWS IoT'.

The A-GPS sample uses either nRF Cloud A-GPS feature or an external SUPL client in order to use A-GPS. If you're to use the nRF Cloud A-GPS feature, you would have to be connected to nRF Cloud as well. However, I don't know how well the API can handle two instances simultaneously. Another option is to use SUPL client. You can select the different A-GPS sources in the sample via the CONFIG_AGPS_SRC_SUPL configurable option.

Best regards,

Marte