• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 32 replies
  • Subscribers 65 subscribers
  • Views 5680 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 239077
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

Parents
  • 0

    Hello , 

    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

  • 0 in reply to Øyvind

    Hi Øyvind,

    It's brand new out of the box. I just stuck the SIM in and hoped that it would magically work :) 

    I am sure the path is not the problem, actually. I can use mcumgr from whatever folder I am in. It sounds like it the .hex file causing the grief with mcumgr. I'll try the bin version.

    I am a complete novice as far as Nordic goes. Had the thingy:52, though. Excellent for demos.

    I'll look into a jlink programmer.

    Thanks for your help!

    Pat

  • 0 in reply to patmolloy13

    Ok, I re-read your message and understand .. run the mcumgr command from the folder where the .bin file is located.

    This has worked, I think .. I was not sure which com port but 30 works, and 29 does not.

    C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_dfu>mcumgr --conntype=serial --connstring=COM30 image upload thingy91_nbiot_v0.2.2.bin
    294.77 KiB / 294.77 KiB [===================================================================] 100.00% 3.12 KiB/s 1m34s
    Done

  • 0 in reply to patmolloy13

    Hi Pat, 

    patmolloy13 said:
    It's brand new out of the box. I just stuck the SIM in and hoped that it would magically work :) 

    Yes, usually they do magically work out of the box, but sometimes the conditions for the magician is not optimized ;) LTE-M and NB-IoT are two different types of technologies. 

    patmolloy13 said:
    I am a complete novice as far as Nordic goes. Had the thingy:52, though. Excellent for demos.

      Yes, and that's what we based the Thingy:91 on. We want it to be just as excellent for demos, however, the nRF9160 is a more advanced device compared to nRF52 devices.

    patmolloy13 said:
    I'll look into a jlink programmer.

    Did you find one? Based on the following comment, it seems as though you have solved it. 

     

    patmolloy13 said:

    This has worked, I think .. I was not sure which com port but 30 works, and 29 does not.

    C:\Users\patmo\Downloads\thingy91_fw_v0.2.3\images_dfu>mcumgr --conntype=serial --connstring=COM30 image upload thingy91_nbiot_v0.2.2.bin
    294.77 KiB / 294.77 KiB [===================================================================] 100.00% 3.12 KiB/s 1m34s

     As I mentioned, one COM port is for the board controller (COM29 - does not work) and the other COM30 is for the nRF9160.

    From the initial post: 

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

    Are you getting any further? If not, you may need to try with another SIM from your local NB-IoT provider.

    Let me know how it goes, and if you have any further questions, just ask :)

    Cheers!

    -Øyvind

  • 0 in reply to 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

  • 0 in reply to patmolloy13
    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.

      

Reply
  • 0 in reply to patmolloy13
    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.

      

Children
  • 0 in reply to Øyvind

    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 Slight smile

    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

  • 0 in reply to patmolloy13
    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 Slight smile

    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!

  • 0 in reply to Øyvind
    Ø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?

  • 0 in reply to patmolloy13

    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. 

  • 0 in reply to Øyvind

    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 ...

Related