Attachments (0)
Nordic Case Info
  • Case ID: 240461
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

LTE Network detected, but never connected

alex141592

My thingy:91 does not connect to the LTE network. However it does detect the Swisscom network (Switzerland) and shows it as available. After a few minutes it sometimes changes to "forbidden".

I did:

  • update the modem with mfrw_nrf9160_1.0.1
  • update the firmware with thingy91_fw_v0.2.3 -> thingy91_ltem_v0.2.2.hex
  • update the nrfCloud certificates (not related probably, but first thought it would only not connect to the cloud)

Screenshot 1: trying to connect

Screenshot 2: connection failed with status "forbidden"

Logs:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
2019-11-26T10:01:36.547Z DEBUG modem << ***** Booting Zephyr OS build v2.0.[00:00:00.386,932] \x1B[0m<inf> BH1749: BH1749 initialized\x1B[0m\x0D\x0A
2019-11-26T10:01:36.549Z DEBUG modem << 99-ncs1-rc1-764-gb687d5d02214 *****\x0D\x0A
2019-11-26T10:01:36.550Z DEBUG modem << Asset tracker started\x0D\x0A
2019-11-26T10:01:36.556Z DEBUG modem << [00:00:00.400,421] \x1B[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100441222\x1B[0m\x0D
2019-11-26T10:01:36.567Z DEBUG modem << [00:00:00.409,576] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100441222/shadow\x1B[0m\x0D
2019-11-26T10:01:36.578Z DEBUG modem << [00:00:00.421,142] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100441222/shadow/get/accepted\x1B[0m\x0D
2019-11-26T10:01:36.593Z DEBUG modem << [00:00:00.432,556] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100441222/shadow/get/rejected\x1B[0m\x0D\x0A
2019-11-26T10:01:36.604Z DEBUG modem << [00:00:00.444,976] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100441222/shadow/update/delta\x1B[0m\x0D
2019-11-26T10:01:36.616Z DEBUG modem << [00:00:00.457,763] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100441222/shadow/update\x1B[0m\x0D
2019-11-26T10:01:36.627Z DEBUG modem << [00:00:00.469,482] \x1B[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100441222/shadow/get\x1B[0m\x0D
2019-11-26T10:01:36.633Z DEBUG modem << Connecting to LTE network. This may take several minutes.\x0D\x0A
2019-11-26T10:01:36.645Z DEBUG modem << [00:00:00.488,708] \x1B[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0\x1B[0m\x0D\x0A
2019-11-26T10:01:38.019Z DEBUG modem << +CEREG: 2,"04BC","010BCA05",7,0,0,"11100000","11100000"\x0D
2019-11-26T10:01:38.034Z DEBUG modem << [00:00:01.872,894] \x1B[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2\x1B[0m\x0D\x0A
2019-11-26T10:08:59.393Z DEBUG modem >> AT+CFUN?\x0D\x0A
2019-11-26T10:08:59.410Z DEBUG modem << +CFUN: 1\x0D\x0A
2019-11-26T10:08:59.417Z DEBUG modem << OK\x0D\x0A
2019-11-26T10:08:59.419Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2019-11-26T10:08:59.433Z DEBUG modem << +CGSN: "352656100441222"\x0D\x0A
2019-11-26T10:08:59.436Z DEBUG modem << OK\x0D\x0A
2019-11-26T10:08:59.439Z DEBUG modem >> AT+CGMI\x0D\x0A
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
2019-12-03T11:05:52.007Z INFO Application data folder: /home/skatinger/.config/nrfconnect/pc-nrfconnect-linkmonitor
2019-12-03T11:05:52.068Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2019-12-03T11:05:52.069Z DEBUG App path: /home/skatinger/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2019-12-03T11:05:52.069Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2019-12-03T11:05:52.069Z DEBUG nRFConnect path: /tmp/.mount_nrfconAPQP3k/resources/app.asar
2019-12-03T11:05:52.069Z DEBUG HomeDir: /home/skatinger
2019-12-03T11:05:52.069Z DEBUG TmpDir: /tmp
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2019-12-03T11:05:52.144Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2019-12-03T11:05:52.145Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2019-12-03T11:05:52.145Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2019-12-03T11:05:52.145Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2019-12-03T11:05:52.145Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2019-12-03T11:05:52.145Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2019-12-03T11:05:52.145Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

It seems to me the connection could be established but it was refused by the service provider. The simcard is from IBasis, registered and has already some used data. In nrfCloud it says "not connected to any device".

Should I contact Swisscom or buy a local SimCard?

Parents
  • 0

    Hello,

    Please do a modem trace and post the results here. The procedure is described in the link below.

    devzone.nordicsemi.com/.../how-to-get-modem-trace-using-trace-collector-in-nrf-connect

  • 0 in reply to Hakon

    Hey thank you for your help.

    I tried to follow the described procedure but failed.

    I used the files in the attached zip.

    1) flashed nrfjprog -f NRF52 --program nRF9160_DK_board_controller_FW.hex --chiperase -r --verify with the switch set to nRF52. Then set it to nRF91 and flashed the included merged.hex file. This resulted in the thingy crashing (green and red light).

    2) Tried to update the firmware with the included mfrwnrf9160100.zip, which threw an error:

    3) reinstalled the newest firmware, built the newest version of asset_tracker, adding CONFIG_BSD_LIBRARY_TRACE_ENABLED=y to both prj.config and prj_nrf9160_pca20035ns.conf and flashed it. Thingy started up and shows blinking as usual for the asset_tracker. However it will not show up on any ports to read the output.

    4) Tried setting everything to the previous state (newest modem firmware and precompiled asset_tracker from the nordic site) but the thingy will still not show up on any ports.

    Any idea why this could be and how I could fix it? I cannot proceed with the tutorial otherwise as AT commands are required.

    Thanks!

  • 0 in reply to alex141592

    Hi!

    For one you should be aware the iBasis has limited LTE-M coverage in Switzerland. So that might be the error. 

     

    alex141592 said:
    flashed nrfjprog -f NRF52 --program nRF9160_DK_board_controller_FW.hex --chiperase -r --verify

     Could you try --sectorerase instead?

    And please update to modem firmware v1.1.0, which is the newest one, found here.

     

    alex141592 said:
    However it will not show up on any ports to read the output.

     What do you mean by this? It isn't showing up in LTE Link Monitor?

    Best regards,

    Heidi

  • 0 in reply to Heidi-Irene Harvey Sollie

    "For one you should be aware the iBasis has limited LTE-M coverage in Switzerland. So that might be the error."

    I am aware that the coverage is only partial, however as seen in screenshot 1 in my first message the network is detected, but the thingy will not connect. CEREG? returns a TAC, a cell ID and AcT as seen in the logs of my first message. The state shown in LTE Link Monitor is either "available" or "forbidden". I live in the city center of Bern where I expect coverage, especially as it shows up with all necessary data in the AT output, but I will contact Swisscom to make sure and get a new simCard.

    " Could you try --sectorerase instead?"
    Just in case I tried that as well, with the same results. I used --chiperase as this was added as a correction to the tutorial in the comments.

    "And please update to modem firmware v1.1.0, which is the newest one, found here."

    I already did, as stated in 3) of my second message. I did again now, to no avail.

    " What do you mean by this? It isn't showing up in LTE Link Monitor?"

    Yes exactly. I was able to resolve this issue. I reinstalled the thingy_91_nrf52_usb_v0.2.2.hex from the thingy91 download page. This however is a problem, because the tutorial states that the nRF9160_DK_board_controller_FW must be installed.

    Is it actually necessary to install this controller to get the trace on the thingy91? DK in my understanding means Development Kit and refers to the nRF9160 DK (https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK) while I got the thingy:91. It says in the tutorial to press the reset button, but the reset button is only present on the DK board, not the thingy.

    What would help me now?

    - Steps required to get a modem trace for you

    - Any ideas why my thingy might find a network but not connect to it or steps to debug this problem.

    Thank you very much for your time!

Reply
  • 0 in reply to Heidi-Irene Harvey Sollie

    "For one you should be aware the iBasis has limited LTE-M coverage in Switzerland. So that might be the error."

    I am aware that the coverage is only partial, however as seen in screenshot 1 in my first message the network is detected, but the thingy will not connect. CEREG? returns a TAC, a cell ID and AcT as seen in the logs of my first message. The state shown in LTE Link Monitor is either "available" or "forbidden". I live in the city center of Bern where I expect coverage, especially as it shows up with all necessary data in the AT output, but I will contact Swisscom to make sure and get a new simCard.

    " Could you try --sectorerase instead?"
    Just in case I tried that as well, with the same results. I used --chiperase as this was added as a correction to the tutorial in the comments.

    "And please update to modem firmware v1.1.0, which is the newest one, found here."

    I already did, as stated in 3) of my second message. I did again now, to no avail.

    " What do you mean by this? It isn't showing up in LTE Link Monitor?"

    Yes exactly. I was able to resolve this issue. I reinstalled the thingy_91_nrf52_usb_v0.2.2.hex from the thingy91 download page. This however is a problem, because the tutorial states that the nRF9160_DK_board_controller_FW must be installed.

    Is it actually necessary to install this controller to get the trace on the thingy91? DK in my understanding means Development Kit and refers to the nRF9160 DK (https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK) while I got the thingy:91. It says in the tutorial to press the reset button, but the reset button is only present on the DK board, not the thingy.

    What would help me now?

    - Steps required to get a modem trace for you

    - Any ideas why my thingy might find a network but not connect to it or steps to debug this problem.

    Thank you very much for your time!

Children
  • 0 in reply to alex141592

    Hi!

    It looks like this might be a known issue without a solution yet. If you get me a modem trace, I can confirm.

    alex141592 said:
    - Steps required to get a modem trace for you

     The steps for the modem trace are in the tutorial I linked. Add the line

    CONFIG_BSD_LIBRARY_TRACE_ENABLED=y

    and build your application. 

    Step two can be overlooked unless you have flashed something else to the nRF52840 on the Thingy:91. 

    Then follow the remaining steps to get a modem trace. 

    If the device isn't showing up in Trace Collector, try unchecking "Auto device/port filter". 

    Best regards,

    Heidi

Terms of service