Not connecting to nRFCloud

RE: Not connecting to nRFCloud

Smythey — Thu, 28 Nov 2019 08:24:29 GMT

Hi Ian

I am in the same situation that you were in five months ago and I'd appreciate some help.

How/where did you order the pack of NB-IoT SIMs, and did you have to pay for them, or buy a data plan?

Did you eventually get the Thingy:91 connected to the nFR cloud and get the asset tracker working?

Thanks

Steve

RE: Not connecting to nRFCloud

Markus Tacker (he/him) — Tue, 20 Aug 2019 13:52:19 GMT

Hei Ian,

I understand that you want to access the nRF Connect for Cloud MQTT broker using a static IP.

This is not supported right now.

RE: Not connecting to nRFCloud

Yano — Tue, 20 Aug 2019 13:35:09 GMT

Hi,

how can we change the AWS IOT IP range (URL) to a fixed IP address?

Thanks

Ian

RE: Not connecting to nRFCloud

MJD093 — Fri, 26 Jul 2019 13:01:27 GMT

You would need to create an EC2 Instance and then edit the options to request an elastic IP for that instance. Information on how to set-up EC2 Instances and elastic IPs should be in the AWS documentation. Note this all does require a paid AWS account, EC2 Instances all have different costs attached, this wasn't an issue for us as we use EC2 on applications.

You then need to create a UDP server, or whatever protocol server you plan to use and install it into the EC2 Instance's Linux machine.

Yes, you will need to get an Elastic IP and then request with Vodafone to change to that one. It will take like a week for them to make that change. Please note that the elastic IP is defined by AWS and not you so get the IP from AWS first.

RE: Not connecting to nRFCloud

Yano — Fri, 26 Jul 2019 11:23:59 GMT

I agree they don't seem flexible. I'm not familiar with EC2 instance how did you set up the IP forwarding? Where in the project did you change to a static IP address and did you get Vodafone to update to that static? Sorry some many questions.

RE: Not connecting to nRFCloud

Didrik Rokhaug — Fri, 26 Jul 2019 11:18:57 GMT

Hi.

Can you try to connect to the device in the programmer app in nRF Connect, and erase all, then try again?

RE: Not connecting to nRFCloud

MJD093 — Fri, 26 Jul 2019 11:13:08 GMT

You would have to look that up on the AWS website. I can imagine they wouldn't be too thrilled at whitelisting that volume of IP addresses but worth a try. Also looking at our contract, I see the line you indicated. I doubt they would let you do this as you don't own those IP ranges.

RE: Not connecting to nRFCloud

Yano — Fri, 26 Jul 2019 11:08:20 GMT

Cool sounds like a good solution, but first I'll ask Vodafone if they can add an IP range to our test, do you know the AWS IP address range? It does say in the form "provided that the IP ranges belong to the customer" but I'll try first.

RE: Not connecting to nRFCloud

MJD093 — Fri, 26 Jul 2019 11:01:46 GMT

I set up an EC2 instance on AWS and set it to a static IP address. From there, I can send data to the EC2 instance which has a UDP Server set-up on it and it can forward data to elsewhere.

RE: Not connecting to nRFCloud

Yano — Fri, 26 Jul 2019 10:58:17 GMT

Thanks for that.

Wow I never though of that, so effectively Vodafone won't allow the traffic through!

I will contact them and ask but it seem very limited.

How did you get over this problem?

RE: Not connecting to nRFCloud

MJD093 — Fri, 26 Jul 2019 10:42:01 GMT

Yano, quick question.

Now that you have Vodafone NB-IoT SIMs, did you ask Vodafone if you can use dynamic IP addresses on their network with those SIMs?

Our trial NB-IoT SIMs from Vodafone only support connection to whitelisted IP addresses (of which we are only allowed to supply two addresses) and therefore would not support AWSs dynamic range of IP addresses for the AWS IoT core. Which is what you need to connect to in order to get to nRF Cloud.

RE: Not connecting to nRFCloud

Yano — Fri, 26 Jul 2019 10:31:53 GMT

Hi Dirdik,

We're under pressure here, so to speed things up we purchased a new DK rev 0.8.5.

But....it will not update its firmware.

Any ideas please?

Ian

RE: Not connecting to nRFCloud

Yano — Thu, 25 Jul 2019 14:08:27 GMT

Thanks Didrik,

Just to explain what we did, since we have rev 0.8.3 there doesn't seem to be a way to register.

First it asks you for the SIM details which I assume is only for iBasis and since we have a Vodafone SIM we clicked the "already have an active SIM link" (Vodafone SIM is active and working). Since we have an old DK we press that link too.

Also below is the CMD line output for the commands.

Ian

RE: Not connecting to nRFCloud

Didrik Rokhaug — Thu, 25 Jul 2019 13:45:02 GMT

Hi.

The "http" commands should be run in the command line after installing httpie. <device ID> should be replaced with the device ID you get from the first command.

However, if your device is not registered to your account in nRF Cloud you will not get any devices. I am working on what to do in that case and will come back to you as soon as I have an answer.

Best regards,

Didrik

RE: Not connecting to nRFCloud

Yano — Thu, 25 Jul 2019 10:37:25 GMT

Hi Didrik,

I have no idea why it stopped working but we re-installed Segger and the project, this worked and it can connect / build+run etc again :)

We use Kiel here and are not familiar with Segger, it seems complex and buggy or maybe we just are not used to it.

We have never registered the device on the cloud so how would we have certificates?

Also how exactly do we get the certificates?

Using the URLs with our API Key in the Chrome window doesn't seem to work (we just get search results).

Here are the actual commands we are putting into URL text box:

http api.nrfcloud.com/.../devices Authorization:"Bearer b8c3ad8b60e4abb110bb67421346f274586306e2"

POST api.nrfcloud.com/.../<device ID>/certificates Authorization:"Bearer b8c3ad8b60e4abb110bb67421346f274586306e2"

Are they formatted OK?

If we remove the http and POST we get this for both.

{
    "message": "Missing Authentication Token",
    "type":  "MISSING_AUTHENTICATION_TOKEN",
    "resourcePath":  "",
    "statusCode": "'404'"
}

Any ideas?

Ian

RE: Not connecting to nRFCloud

Yano — Thu, 25 Jul 2019 08:29:32 GMT

HI Didrik,

No putting back the setting has no affect.

Any ideas how I can get it to connect (we've tried re-starting the machine etc).

I can't find any documentation on this error.

Thanks

RE: Not connecting to nRFCloud

Didrik Rokhaug — Thu, 25 Jul 2019 07:57:12 GMT

Hi.

Is it only when you have CONFIG_AT_CMD_RESPONSE_MAX_LEN =2560 in your prj.conf you have problems connecting to the device?

If so, I would not worry too much about it or try a lower number.

It looks like you are missing your nRF Cloud certificates. If you have previously registered the device to your nRF Cloud user, you can use the steps explained here to recover them.

Best regards,

Didrik

RE: Not connecting to nRFCloud

Yano — Wed, 24 Jul 2019 15:47:37 GMT

Hi Didrik,

Currently AT%CMNG=1 old gives an OK response (no data).

We have set CONFIG_AT_CMD_RESPONSE_MAX_LEN=2560 however we can no longer upload the code to the DK. The "build and run" option is grayed out. And when we get the error "Active project is not an executable"

So we are stuck :( The Jlink is there plus we can connect to device.

Do you have any idea what is causing this problem?

Thanks

RE: Not connecting to nRFCloud

Didrik Rokhaug — Wed, 24 Jul 2019 15:17:32 GMT

Hi.

-111 usually indicates that something is wrong with your certificates.

Can you try to follow the steps Hellesvikis describing in his comment here: https://devzone.nordicsemi.com/f/nordic-q-a/49650/asset_tracker-does-not-work-with-firmware-v1-0-0/199421#199421 and tell me the result?

Best regards,

Didrik

RE: Not connecting to nRFCloud

Yano — Wed, 24 Jul 2019 11:23:32 GMT

Hi Martin,

just to be clear we are able to connect to the internet (we get all green LEDS and and IP address) also we have in log "Connected to LTE network".

Does that not show the fault is with connecting to server not the internet?

Ian

RE: Not connecting to nRFCloud

Yano — Tue, 23 Jul 2019 13:43:05 GMT

Hi Martin,

Using the new SIMs we are able to connect to the network using the LTE Link monitor :)

So this is a major step!

However we can't connect to the asset tracker.

Could you have a look at the log and let me know where we might be going wrong?

The error seem to be icloud connect failed -111

Since were not using iBasics SIM do we need to fill in the ICCID?

Also we have a DK rev:0.8.3, I believe it doesn't need a PIN but do we need to add the IMEI?

Thanks

Iandevzone.nordicsemi.com/.../2019_2D00_07_2D00_23T13_5F00_25_5F00_21.285Z_2D00_log.txt

RE: Not connecting to nRFCloud

Yano — Wed, 17 Jul 2019 06:20:56 GMT

Hi Martin,

OK I have egg on my face!

Basically we are using the wrong SIMs.

We are using V-SIM by vodafone https://eshop.v.vodafone.com/ie/v-sim but these are not NB-IOT they are just standard sims provisioned for data only and re-named!

I went into a store looking for and NB-IOT sim and this is what they gave me.

We have ordered a pack of NB-IOT sims from vodafone and when I get them I'll try again and update you.

Thanks for all your help so far. Ian

RE: Not connecting to nRFCloud

Yano — Fri, 12 Jul 2019 14:19:34 GMT

No I left it for an hour with no success!

What about roaming?

Do you have any other UK or Irish clients who have manged to get it going?

Here is the log....

2019-07-12T13:13:24.915Z INFO Application data folder: C:\Users\Ian\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2019-07-12T13:13:24.994Z DEBUG App pc-nrfconnect-linkmonitor v1.0.0 official
2019-07-12T13:13:24.994Z DEBUG App path: C:\Users\Ian\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2019-07-12T13:13:24.994Z DEBUG nRFConnect 3.0.0 is supported by the app (^3.0.0)
2019-07-12T13:13:24.994Z DEBUG nRFConnect path: C:\Users\Ian\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-07-12T13:13:24.994Z DEBUG HomeDir: C:\Users\Ian
2019-07-12T13:13:24.994Z DEBUG TmpDir: C:\Users\Ian\AppData\Local\Temp
2019-07-12T13:13:30.145Z INFO Modem port is opened
2019-07-12T13:13:30.150Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-07-12T13:13:34.899Z INFO Modem port is closed
2019-07-12T13:13:34.905Z INFO Modem port is opened
2019-07-12T13:13:34.912Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-07-12T13:13:45.043Z INFO Modem port is opened
2019-07-12T13:13:45.046Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-07-12T13:13:45.059Z DEBUG modem << +CFUN: 4\x0D\x0A
2019-07-12T13:13:45.060Z DEBUG modem << OK\x0D
2019-07-12T13:13:45.072Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2019-07-12T13:13:45.114Z DEBUG modem << OK\x0D
2019-07-12T13:13:50.318Z DEBUG modem >> AT+CFUN=4\x0D\x0A
2019-07-12T13:13:50.349Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T13:14:09.993Z DEBUG modem >> AT%XSYSTEMMODE=0,1,0,0\x0D\x0A
2019-07-12T13:14:10.007Z DEBUG modem << OK\x0D\x0A
2019-07-12T13:14:14.247Z DEBUG modem >> AT%XEPCO=0\x0D\x0A
2019-07-12T13:14:14.259Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T13:14:15.599Z DEBUG modem >> AT+CGDCONT=0,"IP","ciot.vodafone.com"\x0D\x0A
2019-07-12T13:14:15.613Z DEBUG modem << OK\x0D
2019-07-12T13:14:17.549Z DEBUG modem >> AT+CGAUTH=0,"PAP","vodafone","vodafone"\x0D\x0A
2019-07-12T13:14:17.564Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T13:14:22.542Z DEBUG modem >> AT+COPS=1,2,"90128"\x0D\x0A
2019-07-12T13:14:22.557Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T13:14:28.288Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2019-07-12T13:14:28.329Z DEBUG modem << OK\x0D\x0A
2019-07-12T14:17:31.667Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-07-12T14:17:31.671Z DEBUG modem << +CFUN: 1\x0D\x0A
2019-07-12T14:17:31.677Z DEBUG modem << OK\x0D\x0A
2019-07-12T14:17:31.681Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-07-12T14:17:31.686Z DEBUG modem << +CGSN: "352656100110413"\x0D\x0A
2019-07-12T14:17:31.687Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.690Z DEBUG modem >> AT+CGMI\x0D\x0A
2019-07-12T14:17:31.698Z DEBUG modem << Nordic Semiconductor ASA\x0D\x0A
2019-07-12T14:17:31.701Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.704Z DEBUG modem >> AT+CGMM\x0D\x0A
2019-07-12T14:17:31.708Z DEBUG modem << nRF9160-SICA\x0D\x0A
2019-07-12T14:17:31.709Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.714Z DEBUG modem >> AT+CGMR\x0D\x0A
2019-07-12T14:17:31.719Z DEBUG modem << mfw_nrf9160_1.0.0\x0D\x0A
2019-07-12T14:17:31.720Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.721Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.0.0] SerNr: 352656100110413
2019-07-12T14:17:31.723Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2019-07-12T14:17:31.726Z DEBUG modem << +CEMODE: 0\x0D\x0A
2019-07-12T14:17:31.730Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.735Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2019-07-12T14:17:31.747Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)\x0D\x0A
2019-07-12T14:17:31.749Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.754Z DEBUG modem >> AT+CMEE?\x0D\x0A
2019-07-12T14:17:31.758Z DEBUG modem << +CMEE: 0\x0D
2019-07-12T14:17:31.759Z DEBUG modem << \x0A
2019-07-12T14:17:31.760Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.767Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2019-07-12T14:17:31.770Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.773Z DEBUG modem >> AT+CNEC?\x0D\x0A
2019-07-12T14:17:31.777Z DEBUG modem << +CNEC: 0\x0D\x0A
2019-07-12T14:17:31.777Z DEBUG modem << OK\x0D\x0A
2019-07-12T14:17:31.781Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2019-07-12T14:17:31.785Z DEBUG modem << OK\x0D
2019-07-12T14:17:31.788Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2019-07-12T14:17:31.792Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
2019-07-12T14:17:31.793Z DEBUG modem << OK\x0D\x0A
2019-07-12T14:17:31.798Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2019-07-12T14:17:31.805Z DEBUG modem << +CGDCONT: 0,"IP","ciot.vodafone.com","",0,0\x0D
2019-07-12T14:17:31.806Z DEBUG modem << \x0A
2019-07-12T14:17:31.806Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.815Z DEBUG modem >> AT+CGACT?\x0D\x0A
2019-07-12T14:17:31.819Z DEBUG modem << +CGACT: 0,0\x0D\x0A
2019-07-12T14:17:31.820Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.824Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2019-07-12T14:17:31.827Z DEBUG modem << OK\x0D
2019-07-12T14:17:31.830Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2019-07-12T14:17:31.834Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.837Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2019-07-12T14:17:31.841Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.844Z DEBUG modem >> AT+CEREG?\x0D\x0A
2019-07-12T14:17:31.851Z DEBUG modem << +CEREG: 2,2,"FFFE","FFFFFFFF",9\x0D\x0A
2019-07-12T14:17:31.852Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.856Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2019-07-12T14:17:31.859Z DEBUG modem << OK\x0D\x0A
2019-07-12T14:17:31.865Z DEBUG modem >> AT+CESQ\x0D\x0A
2019-07-12T14:17:31.871Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D\x0A
2019-07-12T14:17:31.872Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.876Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2019-07-12T14:17:31.882Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.887Z DEBUG modem >> AT%XSIM?\x0D\x0A
2019-07-12T14:17:31.890Z DEBUG modem << %XSIM: 1\x0D\x0A
2019-07-12T14:17:31.891Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.896Z DEBUG modem >> AT+CPIN?\x0D\x0A
2019-07-12T14:17:31.902Z DEBUG modem << +CPIN: READY\x0D\x0A
2019-07-12T14:17:31.904Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.907Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2019-07-12T14:17:31.920Z DEBUG modem << +CPINR: "SIM PIN",3\x0D\x0A
2019-07-12T14:17:31.921Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.926Z DEBUG modem >> AT+CIMI\x0D\x0A
2019-07-12T14:17:31.932Z DEBUG modem << 901280990314292\x0D\x0A
2019-07-12T14:17:31.933Z DEBUG modem << OK\x0D\x0A\x00
2019-07-12T14:17:31.934Z INFO IMSIdentity: 901280990314292

RE: Not connecting to nRFCloud

Martin Lesund — Fri, 12 Jul 2019 13:08:56 GMT

Hi Ian,

That's strange.

Could you confirm that you wait at least ~5mins after turning ON the modem and then send the AT+CFUN? command?

The first time connecting to an nb-IoT network can take some time.

RE: Not connecting to nRFCloud

Martin Lesund — Fri, 12 Jul 2019 08:41:58 GMT

Hi Ian,

I think it could be okay, but I would recommend just to run the at_client sample to avoid any interference from the asset_tracker sample.
It would be nice to have it confirmed that the V-SIM is working as it should.
It would be a good idea to contact your carrier and confirm if there is something special that needs to be done to be able to connect to their network.

Best Regards,
Martin L.