asset_tracker is starting, but modem_configure does not return in ().
What could be the cause?
asset_tracker is starting, but modem_configure does not return in ().
What could be the cause?
Hi!
It seems like the device might be struggling with connecting to the network. To make it easier for me to help you could you answer the following questions:
- Which version of NCS are you using?
- What network are you trying to connect to (NB-IoT/LTE-M)?
- Which version of the Thingy:91 do you have?
- Who is your SIM-provider?
Best regards,
Carl Richard
NCS V1.4.2
LTE-M
Thingy91 1.4.0
I'm using the SIM that comes with it.
The LTE Link Monitor uses the UART interface, so you must have a USB cable connected to the device. This also enables you to send AT Commands.
Best regards,
Carl Richard
Even if thingy91 is connected via USB, lte link monitor will be "No devices available".
at_client saw the .c main, but only printk.
Is this all right?
C:\Users\m-koike\ncs\v1.4.2\nrf\samples\nrf9160\at_client\src\main.c
That is correct, yes. The sample should simply enable you to communicate directly with the modem over UART. You can read more about it in the documentation. Lets step back a little and try from the beginning.
1. Download the latest Thingy:91 firmware.
2. Flash img_app_bl/thingy91_nrf52_connectivity_bridge_2020-10-30_5522ca2b.hex to the nRF52840
3. Flash img_app_bli/thingy91_at_client_2020-10-30_5522ca2b.hex to the nRF9160
4. Open LTE link monitor and see of you can find the device (make sure USB is connected). Try with and without Auto device/port filter enabled if it doesn't show up.
5. Send the command "AT+CFUN=1"
6. Send the command "AT+CFUN?"
7. Wait 1 minute.
8. Send "AT+CFUN?" again.
9. Post the log here.
This is just to verify that the Thingy can in fact connect using the original code.
Best regards,
Carl Richard
I wrote both hex files in Programmer.
We launched LTE Link Monitor, which is still "No devices available".
I removed j-link and tried connecting the PC and Thingy:91 directly to USB, but there was no change.
The J-Link RTT Viewer can connect.
I wrote both hex files in Programmer.
We launched LTE Link Monitor, which is still "No devices available".
I removed j-link and tried connecting the PC and Thingy:91 directly to USB, but there was no change.
The J-Link RTT Viewer can connect.
Hi again!
If you are able to connect with J-Link RTT Viewer that means that a debugger is still connected to the computer, and you are likely connected to that and not the Thingy. Are you able to send me a picture of your setup?
I know this isn't related to your actual issue, but it could help us solve it. In addition, please update the modem firmware.
Best regards,
Carl Richard
Because it was a dedicated cable for charging,
I was able to connect it when I changed it to a cable that can communicate.
log file
2021-02-10T05:46:36.732Z INFO Application data folder: C:\Users\m-koike\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor 2021-02-10T05:46:36.761Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official 2021-02-10T05:46:36.761Z DEBUG App path: C:\Users\m-koike\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor 2021-02-10T05:46:36.761Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0) 2021-02-10T05:46:36.761Z DEBUG nRFConnect path: C:\Users\m-koike\AppData\Local\Programs\nrfconnect\resources\app.asar 2021-02-10T05:46:36.761Z DEBUG HomeDir: C:\Users\m-koike 2021-02-10T05:46:36.761Z DEBUG TmpDir: C:\Users\m-koike\AppData\Local\Temp 2021-02-10T05:46:50.211Z INFO Modem port is opened 2021-02-10T05:46:50.217Z DEBUG modem >> AT+CFUN? 2021-02-10T05:46:50.428Z DEBUG modem << +CFUN: 0 2021-02-10T05:46:50.431Z DEBUG modem << OK 2021-02-10T05:47:03.153Z INFO Modem port is closed 2021-02-10T05:47:03.194Z INFO Modem port is opened 2021-02-10T05:47:03.199Z DEBUG modem >> AT+CFUN? 2021-02-10T05:47:03.215Z DEBUG modem << +CFUN: 0 2021-02-10T05:47:03.216Z DEBUG modem << OK 2021-02-10T05:49:34.794Z INFO Modem port is closed 2021-02-10T05:49:34.804Z INFO Modem port is opened 2021-02-10T05:49:34.811Z DEBUG modem >> AT+CFUN? 2021-02-10T05:49:34.827Z DEBUG modem << +CFUN: 0 2021-02-10T05:49:34.829Z DEBUG modem << OK 2021-02-10T05:59:37.393Z DEBUG modem >> AT+CFUN=1 2021-02-10T05:59:37.439Z DEBUG modem << OK 2021-02-10T06:01:39.533Z INFO Modem port is closed 2021-02-10T06:01:39.546Z INFO Modem port is opened 2021-02-10T06:01:39.549Z DEBUG modem >> AT+CFUN? 2021-02-10T06:01:39.558Z DEBUG modem << +CFUN: 1 2021-02-10T06:01:39.559Z DEBUG modem << OK 2021-02-10T06:01:39.565Z DEBUG modem >> AT+CGSN=1 2021-02-10T06:01:39.574Z DEBUG modem << +CGSN: "352656101122565" 2021-02-10T06:01:39.575Z DEBUG modem << OK 2021-02-10T06:01:39.578Z DEBUG modem >> AT+CGMI 2021-02-10T06:01:39.587Z DEBUG modem << Nordic Semiconductor ASA 2021-02-10T06:01:39.589Z DEBUG modem << OK 2021-02-10T06:01:39.594Z DEBUG modem >> AT+CGMM 2021-02-10T06:01:39.603Z DEBUG modem << nRF9160-SICA 2021-02-10T06:01:39.605Z DEBUG modem << OK 2021-02-10T06:01:39.608Z DEBUG modem >> AT+CGMR 2021-02-10T06:01:39.615Z DEBUG modem << mfw_nrf9160_1.1.1 2021-02-10T06:01:39.616Z DEBUG modem << OK 2021-02-10T06:01:39.617Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.1.1] SerNr: 352656101122565 2021-02-10T06:01:39.620Z DEBUG modem >> AT+CEMODE? 2021-02-10T06:01:39.628Z DEBUG modem << +CEMODE: 2 2021-02-10T06:01:39.629Z DEBUG modem << OK 2021-02-10T06:01:39.637Z DEBUG modem >> AT%XCBAND=? 2021-02-10T06:01:39.647Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66) 2021-02-10T06:01:39.651Z DEBUG modem << OK 2021-02-10T06:01:39.661Z DEBUG modem >> AT+CMEE? 2021-02-10T06:01:39.670Z DEBUG modem << +CMEE: 0 2021-02-10T06:01:39.672Z DEBUG modem << OK 2021-02-10T06:01:39.675Z DEBUG modem >> AT+CMEE=1 2021-02-10T06:01:39.680Z DEBUG modem << OK 2021-02-10T06:01:39.686Z DEBUG modem >> AT+CNEC? 2021-02-10T06:01:39.694Z DEBUG modem << +CNEC: 0 2021-02-10T06:01:39.695Z DEBUG modem << OK 2021-02-10T06:01:39.698Z DEBUG modem >> AT+CNEC=24 2021-02-10T06:01:39.704Z DEBUG modem << OK 2021-02-10T06:01:39.707Z DEBUG modem >> AT+CGEREP? 2021-02-10T06:01:39.713Z DEBUG modem << +CGEREP: 0,0 2021-02-10T06:01:39.714Z DEBUG modem << OK 2021-02-10T06:01:39.720Z DEBUG modem >> AT+CGDCONT? 2021-02-10T06:01:39.725Z DEBUG modem << OK 2021-02-10T06:01:39.728Z DEBUG modem >> AT+CGACT? 2021-02-10T06:01:39.737Z DEBUG modem << OK 2021-02-10T06:01:39.740Z DEBUG modem >> AT+CGEREP=1 2021-02-10T06:01:39.746Z DEBUG modem << OK 2021-02-10T06:01:39.749Z DEBUG modem >> AT+CIND=1,1,1 2021-02-10T06:01:39.756Z DEBUG modem << OK 2021-02-10T06:01:39.758Z DEBUG modem >> AT+CEREG=5 2021-02-10T06:01:39.763Z DEBUG modem << OK 2021-02-10T06:01:39.765Z DEBUG modem >> AT+CEREG? 2021-02-10T06:01:39.776Z DEBUG modem << +CEREG: 5,90,"FFFE","FFFFFFFF",9,0,0,"00000000","00000000" 2021-02-10T06:01:39.778Z DEBUG modem << OK 2021-02-10T06:01:39.781Z DEBUG modem >> AT%CESQ=1 2021-02-10T06:01:39.788Z DEBUG modem << OK 2021-02-10T06:01:39.792Z DEBUG modem >> AT+CESQ 2021-02-10T06:01:39.803Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:01:39.804Z DEBUG modem << OK 2021-02-10T06:01:39.808Z DEBUG modem >> AT%XSIM=1 2021-02-10T06:01:39.813Z DEBUG modem << OK 2021-02-10T06:01:39.819Z DEBUG modem >> AT%XSIM? 2021-02-10T06:01:39.826Z DEBUG modem << %XSIM: 0 2021-02-10T06:01:39.827Z DEBUG modem << OK 2021-02-10T06:01:46.659Z DEBUG modem >> AT+CESQ 2021-02-10T06:01:46.668Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:01:46.671Z DEBUG modem << OK 2021-02-10T06:01:59.664Z DEBUG modem >> AT+CESQ 2021-02-10T06:01:59.672Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:01:59.673Z DEBUG modem << OK 2021-02-10T06:02:12.668Z DEBUG modem >> AT+CESQ 2021-02-10T06:02:12.678Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:02:12.679Z DEBUG modem << OK 2021-02-10T06:02:25.656Z DEBUG modem >> AT+CESQ 2021-02-10T06:02:25.670Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:02:25.673Z DEBUG modem << OK 2021-02-10T06:02:38.667Z DEBUG modem >> AT+CESQ 2021-02-10T06:02:38.677Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:02:38.678Z DEBUG modem << OK 2021-02-10T06:02:51.673Z DEBUG modem >> AT+CESQ 2021-02-10T06:02:51.684Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:02:51.685Z DEBUG modem << OK 2021-02-10T06:03:04.655Z DEBUG modem >> AT+CESQ 2021-02-10T06:03:04.667Z DEBUG modem << +CESQ: 99,99,255,255,255,255 2021-02-10T06:03:04.670Z DEBUG modem << OK
Hi again!
Great that you figured that out! From what I can see it doesn't connect at all. Have you registered the SIM-card as described in the Thingy:91 getting started video?
Also make sure that the SIM (iBasis) is supported in your area. You can find information about this in the coverage map.
Best regards,
Carl Richard
We struggled, but we were able to communicate with LTE. Thank you very much.
By the way, it is no longer available to connect thingy91 and PC via USB.
I was able to connect twice, but it is not connected to the charging mode.
Is there any possible cause?
Hi, Makoto!
That's good to hear! The Thingy:91 relies on the Connectivity Bridge sample on the nRF52840 to enable USB-communication. Ensure that any code you have running on the nRF52840 also enables what the connectivity bridge implements. If this doesn't help I suggest that your open a new ticket, as I'm going on holiday.
Best regards,
Carl Richard