Unable to activate iBASIS SIM (I Think)

[patmolloy13]

I just received the Thingy 91 this morning. I've inserted the SIM have verified it on the nRF Connect for Cloud.

I cannot proceed to the next step, as the led continues to pulse blue - so I assume not connected to the network.

I am in the UK, South West London (SW15 6BF).

I assume there is no coverage here??

What are my options? If I need a different SIM, what am I looking for?

Thanks

[Øyvind]

Hello patmolloy13, 

I am in the UK, South West London (SW15 6BF).

 The Thingy:91 is shipped with LTE-M activated on the modem. According to GSMA Deployment Map, only NB-IoT is available in the UK. 

What are my options? If I need a different SIM, what am I looking for?

 Please try downloading the Thingy:91 Firmware pack from the download page. This file includes several pre-compiled versions of the Asset Tracker, with different network modes i.e. NB-IoT or LTE-M.

Package Contents:
│   CONTENTS.txt                                This file
│   mfwnrf9160101.zip                           Modem firmware, updated through nRF Connect for Desktop Programmer app
│
├───images_dfu                                  Application images, updated over USB
│       thingy91_at_client_v0.2.3.bin           Firmware for direct modem communication
│       thingy91_ltem_v0.2.2.bin                Asset tracker firmware for nRF9160, LTE-M network mode
│       thingy91_nbiot_legacy_pco_v0.2.2.bin    Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO
│       thingy91_nbiot_v0.2.2.bin               Asset tracker firmware for nRF9160, NB-IoT network mode
│
└───images_hex                                  Application images, updated over SWD (JLINK probe / development kit)
        thingy91_at_client_v0.2.3.hex           Firmware for direct modem communication
        thingy91_ltem_v0.2.2.hex                Asset tracker firmware for nRF9160, LTE-M network mode
        thingy91_nbiot_legacy_pco_v0.2.2.hex    Asset tracker firmware for nRF9160, NB-IoT network mode, legacy PCO
        thingy91_nbiot_v0.2.2.hex               Asset tracker firmware for nRF9160, NB-IoT network mode
        thingy91_nrf52_usb_v0.2.2.hex           USB-UART serial bridge firmware for nRF52840

Please try to program your Thingy:91 with thingy91_nbiot_v0.2.2.hex.

Kind regards,
Øyvind

[patmolloy13]

Thanks, Øyvind, I'll give that a go.

Pat

[patmolloy13]

Ok, I have flashed thingy91_nbiot_v0.2.2.bin to the device. But I am still getting no connection. How do I debug this best? Has the act of flashing this image definitely flashed the modem?

1) Is there any way (via the USB port) to see any diagnostic data that might be being generated?

2) Is there any way to verify whether the iBASIS sim has roamed (or is capable of roaming) to NB-IoT in the UK ? (London)

Thanks

Pat

[Øyvind]

patmolloy13 said:

Has the act of flashing this image definitely flashed the modem?

The application has been loaded, but nothing on the modem itself. In the "Thingy:91 Firmware pack" you'll find mfwnrf9160101.zip = Modem firmware, updated through nRF Connect for Desktop Programmer app. But see point 1 below first.

patmolloy13 said:

1) Is there any way (via the USB port) to see any diagnostic data that might be being generated?

 Yes, you can load the AT Client (thingy91_at_client_v0.2.3.bin) which will more information about the modem and network. 

patmolloy13 said:

2) Is there any way to verify whether the iBASIS sim has roamed (or is capable of roaming) to NB-IoT in the UK ? (London)

 iBasis does, unfortunately, not have NB-IoT support in the UK, and only limited support for LTE-M. Ref. iBasis coverage.

  

[patmolloy13]

Thanks again for all of your help Øyvind. I really appreciate it!

To get this working in the UK is spiralling a bit beyond my capabilities! I just wanted it to work

So .. to get this working in the UK, compared with the out-of-the-box delivery, I need to ..

1) Find an NB-IoT provider in the UK and get a working SIM (may or may not be possible!)

2) Flash the thingy91_nbiot_v0.2.2.bin code (I have done this) .. but this is only the app, not the modem firmware.

3) Install Firmware from  mfwnrf9160101.zip = Modem firmware, updated through nRF Connect for Desktop, which will allow the modem to talk NB-IoT

To get NRF Connect for Desktop working, do I need additional hardware/cables or is this all done via the MicroUSB port?

Sorry for all this :-O 

I work here https://www.digicatapult.org.uk/projects/future-networks-lab/ and am trying to find a nice demonstrator for NB-IoT !

Pat

[Øyvind]

patmolloy13 said:

1) Find an NB-IoT provider in the UK and get a working SIM (may or may not be possible!)

 According to GSMA, Vodafone is your provider of NB-IoT

patmolloy13 said:

2) Flash the thingy91_nbiot_v0.2.2.bin code (I have done this) .. but this is only the app, not the modem firmware.

Correct, this is the application that enables NB-IoT on your board. It is configured with CONFIG_LTE_NETWORK_MODE_NBIOT=y, which selects network mode and configures the modem for this. 

patmolloy13 said:

3) Install Firmware from  mfwnrf9160101.zip = Modem firmware, updated through nRF Connect for Desktop, which will allow the modem to talk NB-IoT

You need to ensure that you have the latest modem FW in order for the modem to talk to NB-IoT or LTE-M networks.

Loading the AT Client will print the current modem FW on your modem when issuing "AT+CFUN?" from the LTE Link Monitor. If you have the same version as included in the Thingy:91 Firmware pack, then you do not need to do anything. Remember to load the "thingy91_nbiot_v0.2.2.bin" afterward.

nRF Connect for Desktop is a software where you can download both the Programmer app (updating modem) and the LTE Link Monitor (issuing AT Commands and printing information). As long as you are able to load the .bin files from the Thingy:91 Firmware pack, you won't need any other external HW. 

patmolloy13 said:

Sorry for all this :-O 

 Nothing to feel sorry about, this is why we are here

The next step for you is to acquire a Vodafone NB-IoT SIM and get your Thingy:91 connected. Then go to nRFCloud.com to demonstrate the NB-IoT. 

Let me know how it goes!

[patmolloy13]

Øyvind said:

If you have the same version as included in the Thingy:91 Firmware pack, then you do not need to do anything. Remember to load the "thingy91_nbiot_v0.2.2.bin" afterward.

Is this the version that shipped with the Thingy:91?

[Øyvind]

No, the shipped version is for LTE-M, while you'll need to load NB-IoT. In the sentence above, I am referring to the modem FW. 

[patmolloy13]

Ok, I am *still* confused .. I have now installed the AT firmware, and the LTE Link monitor software. I have also installed an NB-IoT SIM from Vodafone, that we used earlier in the year here (I don't know it it is still alive). This is what I see from AT+CFUN?

Main question -- can you tell from this whether the modem is configured properly for NB-IoT?

2019-11-14T14:22:51.079Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-11-14T14:22:51.101Z DEBUG modem << +CFUN: 1\x0D\x0A
2019-11-14T14:22:51.127Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.130Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-11-14T14:22:51.147Z DEBUG modem << +CGSN: "352656100826604"\x0D
2019-11-14T14:22:51.150Z DEBUG modem << \x0A
2019-11-14T14:22:51.151Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.167Z DEBUG modem >> AT+CGMI\x0D\x0A
2019-11-14T14:22:51.175Z DEBUG modem << Nordic Semiconductor ASA\x0D
2019-11-14T14:22:51.178Z DEBUG modem << \x0A
2019-11-14T14:22:51.182Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.197Z DEBUG modem >> AT+CGMM\x0D\x0A
2019-11-14T14:22:51.215Z DEBUG modem << nRF9160-SICA\x0D\x0A
2019-11-14T14:22:51.221Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.225Z DEBUG modem >> AT+CGMR\x0D\x0A
2019-11-14T14:22:51.231Z DEBUG modem << mfw_nrf9160_1.0.1\x0D
2019-11-14T14:22:51.244Z DEBUG modem << \x0A
2019-11-14T14:22:51.246Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.246Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.0.1] SerNr: 352656100826604
2019-11-14T14:22:51.256Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2019-11-14T14:22:51.262Z DEBUG modem << +CEMODE: 2\x0D\x0A
2019-11-14T14:22:51.264Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.282Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2019-11-14T14:22:51.291Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)\x0D\x0A
2019-11-14T14:22:51.292Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.296Z DEBUG modem >> AT+CMEE?\x0D\x0A
2019-11-14T14:22:51.314Z DEBUG modem << +CMEE: 1\x0D
2019-11-14T14:22:51.316Z DEBUG modem << \x0A
2019-11-14T14:22:51.317Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.337Z DEBUG modem >> AT+CNEC?\x0D\x0A
2019-11-14T14:22:51.354Z DEBUG modem << +CNEC: 24\x0D
2019-11-14T14:22:51.356Z DEBUG modem << \x0A
2019-11-14T14:22:51.357Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.361Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2019-11-14T14:22:51.366Z DEBUG modem << +CGEREP: 1,0\x0D
2019-11-14T14:22:51.383Z DEBUG modem << \x0A
2019-11-14T14:22:51.385Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.399Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2019-11-14T14:22:51.415Z DEBUG modem << OK\x0D
2019-11-14T14:22:51.419Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2019-11-14T14:22:51.425Z DEBUG modem << OK\x0D
2019-11-14T14:22:51.427Z DEBUG modem >> AT+CEREG?\x0D\x0A
2019-11-14T14:22:51.467Z DEBUG modem << +CEREG: 2,0,"FFFE","FFFFFFFF",7\x0D
2019-11-14T14:22:51.483Z DEBUG modem << \x0A
2019-11-14T14:22:51.485Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.507Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2019-11-14T14:22:51.525Z DEBUG modem << OK\x0D
2019-11-14T14:22:51.541Z DEBUG modem >> AT+CESQ\x0D\x0A
2019-11-14T14:22:51.558Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D
2019-11-14T14:22:51.574Z DEBUG modem << \x0A
2019-11-14T14:22:51.576Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.595Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2019-11-14T14:22:51.610Z DEBUG modem << OK\x0D
2019-11-14T14:22:51.625Z DEBUG modem >> AT%XSIM?\x0D\x0A
2019-11-14T14:22:51.642Z DEBUG modem << %XSIM: 1\x0D
2019-11-14T14:22:51.659Z DEBUG modem << \x0A
2019-11-14T14:22:51.660Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.680Z DEBUG modem >> AT+CPIN?\x0D\x0A
2019-11-14T14:22:51.696Z DEBUG modem << +CPIN: READY\x0D
2019-11-14T14:22:51.713Z DEBUG modem << \x0A
2019-11-14T14:22:51.714Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.735Z DEBUG modem >> AT+CPINR="SIM PIN"\x0D\x0A
2019-11-14T14:22:51.754Z DEBUG modem << +CPINR: "SIM PIN",3\x0D
2019-11-14T14:22:51.772Z DEBUG modem << \x0A
2019-11-14T14:22:51.773Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.778Z DEBUG modem >> AT+CIMI\x0D\x0A
2019-11-14T14:22:51.783Z DEBUG modem << 901288002206279\x0D
2019-11-14T14:22:51.800Z DEBUG modem << \x0A
2019-11-14T14:22:51.801Z DEBUG modem << OK\x0D\x0A\x00
2019-11-14T14:22:51.802Z INFO IMSIdentity: 901288002206279
2019-11-14T14:23:25.933Z DEBUG modem << %CESQ: 255,0\x0D\x0A
2019-11-14T14:23:25.976Z DEBUG modem << +CEREG: 2,"FFFE","FFFFFFFF",7\x0D\x0A\x00
2019-11-14T14:25:06.749Z DEBUG modem << %CESQ: 255,0\x0D
2019-11-14T14:26:47.675Z DEBUG modem << %CESQ: 255,0\x0D

This is what I see in LTE Link Monitor ...

[patmolloy13]

The thing I am still not clear on .. I installed this mfw_nrf9160_update_from_1.0.0_to_1.0.1.bin

and then installed thingy91_nbiot_v0.2.2.bin

which of these is the one that tells the modem to talk NB-IoT rather than LTE-m? Or is it both?

If the SIM was working, should this make the device burst into life?

Installing thingy91_at_client_v0.2.3.bin (which I have installed now) effectively overwrites  thingy91_nbiot_v0.2.2.bin - is that right?

Sorry again!

Pat

[Øyvind]

patmolloy13 said:

which of these is the one that tells the modem to talk NB-IoT rather than LTE-m? Or is it both?

 Yes, both is correct. The modem itself does the communication to the network, but the application tells the modem which network it should use with CONFIG_LTE_NETWORK_MODE_NBIOT=y. 

 

patmolloy13 said:

If the SIM was working, should this make the device burst into life?

 Yes, if the SIM was working, you should see green on everything in the LTE Link Monitor. Have you got a new SIM?

 

patmolloy13 said:

Installing thingy91_at_client_v0.2.3.bin (which I have installed now) effectively overwrites  thingy91_nbiot_v0.2.2.bin - is that right?

 Yes, that is correct. And I hope that the modem settings are saved so that it works as intended to give more debug information to us.

From the log you pasted in last comment, I see that the modem FW is correct at least. However, I can't see anything about NB-IoT, which can mean that your SIM does not work. LTE Link Monitor does not list a network either, another signal that NB-IoT is not working. 

[patmolloy13]

Ok, a little more to report. We have a testbed NBIoT setup here at DC. The team tell me that we need to alter PLMN via the AT+COPS command, and also change the APN via the AT+CGDCONT command.

I am issuing ..

AT+CGDCONT=1,"IP","internet"

Where "internet" is the APN name. This command works, and I get OK back. AT+CGDCONT? confirms set.

AT+CGDCONT?
+CGDCONT: 1,"IP","internet","",0,0
OK

Then I issue

AT+COPS=1,2,"23592"

but I get 

Error: 'AT+COPS=1,2,"23592" ' timed out

and after this, all further commands time out .. I am pretty sure the command is correct, so am I missing something further?