Thingy91: AT+CGDCONT? and AT+CGACT? time out

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Tue, 28 Feb 2023 12:22:43 GMT

I will ask them, this seems like a plausible cause of the connection error. Thank you for your assistance!

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Mon, 27 Feb 2023 11:40:08 GMT

Here is the response from the modem team;

In the attached log the SIM is activated correctly. The problem is that there is no response from DNS server. The device sends DNS query to "californium.eclipseprojects.io" but there is no response for that and DNS query fails to timeout.

Could the customer check the data plan in that SIM? If the problem is solved by changing the SIM it could be that the other SIM has run out of active data plan.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Fri, 24 Feb 2023 13:31:48 GMT

The modem fw is v1.3.3 (mfw_nrf9160_1.3.3)

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Fri, 24 Feb 2023 13:14:31 GMT

What is the modem firmware version?

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Thu, 23 Feb 2023 13:58:48 GMT

Thanks, I will look at it.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Mon, 20 Feb 2023 10:12:48 GMT

Hi, I used this sample: Cellular-IoT-Fundamentals/lesson7/cellfund_less7_exer1_solution at master · NordicDeveloperAcademy/Cellular-IoT-Fundamentals · GitHub

Here is the modem trace file, I let it run until it was 247 kB. Let me know if I need to let the modem tracing run longer.

devzone.nordicsemi.com/.../trace_2D00_2023_2D00_02_2D00_20T10_2D00_08_2D00_02.560Z.bin

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Thu, 16 Feb 2023 16:13:49 GMT

Try other samples, like the mqtt_simple or similar, and see if you are able to get a modem trace then. It's kinda important to get the modem trace to work to make any progress.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Mon, 13 Feb 2023 11:35:36 GMT

Yes, I checked both ports, and with the other port nothing happened, the bin file size was stuck at 0.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Tue, 07 Feb 2023 19:13:45 GMT

This trace file looks empty to me. Are you sure you are using the right COM port? The .bin file should be alot bigger than 1 KB.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Wed, 01 Feb 2023 14:56:16 GMT

I must have forgot to check the COM ports. Here is the modem trace bin file. devzone.nordicsemi.com/.../trace_2D00_2023_2D00_02_2D00_01T14_2D00_53_2D00_11.850Z.bin

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Wed, 01 Feb 2023 13:30:31 GMT

Which SDK version are you using?

Are you using the correct COM port?

Have you tried changing it?

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Mon, 30 Jan 2023 06:01:06 GMT

Yes, I have flashed the connectivity bridge to nrf52840. I don't have an external debug probe, I use the USB cable. The hex file is the build file from the nrf asset_tracker_v2 application template, sdk-nrf/applications/asset_tracker_v2 at main · nrfconnect/sdk-nrf · GitHub.

I says to set CONFIG_NRF_MODEM_LIB_TRACE , hence I did so in prj.conf of that application template, built the code, and flashed the hex file to Thingy91 using nRF Connect.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Sun, 29 Jan 2023 17:33:24 GMT

Did you flash the connectivity bridge to the nrf52840? Do you have a DK, so that you can program using external debug probe?

[quote user="MHInv"]app_signed.hex file[/quote]

Where did you get this file from?

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Thu, 26 Jan 2023 07:14:48 GMT

Hi, I tried doing it as it says here: Nordic Semiconductor Infocenter .

I sat CONFIG_NRF_MODEM_LIB_TRACE=y in the prj.conf file in the asset_tracker_v2 application in VS Code, was able to build, and programmed the Thingy91, using Programmer from nRF Connect for Desktop, with the app_signed.hex file, since I am only using a USB cable, as was suggested here: Developing with Thingy:91 — nRF Connect SDK 2.2.99 documentation (nordicsemi.com) , but nothing happened when I used the Trace Collector from nRF Connect for Desktop.

My Thingy91 also seemed completely dead after programming it with the app_signed.hex file. (No LED light)

I programmed the Thingy91 as instructed in: Getting started with Thingy:91 — nRF Connect SDK 2.2.99 documentation (nordicsemi.com) . I also updated to the latest firmware before starting on anything else, as was suggested.

What am I doing wrong here, have I misunderstood the steps specified in Nordic Semiconductor Infocenter ?

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Wed, 25 Jan 2023 13:05:28 GMT

Looks like there are some DNS issues, and also later the modem shuts down for some reason. Can you try doing a modem trace(raw) and upload the file here?

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

MInv — Mon, 23 Jan 2023 06:16:49 GMT

Hi,

Yes, both SIM cards are activated in nrfCloud, under "SIM CARDS", and they have a lot of data left on them, 10.47 / 10.49 Mb.

RE: Thingy91: AT+CGDCONT? and AT+CGACT? time out

Hakon — Fri, 20 Jan 2023 14:11:43 GMT

Hello,

[quote user=""]The SIM card provider is iBASIS eSIM.[/quote]

have you activated the SIM card in nrfcloud? Have you checked that the SIM has data on it?