Need help connecting to MQTT using nRF9160

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Thu, 24 Oct 2024 12:35:17 GMT

Yeah, thanks for the help MQTT works on the DK. I'll talk to the design team and figure out the custom board issues.

RE: Need help connecting to MQTT using nRF9160

Charlie — Tue, 22 Oct 2024 11:55:07 GMT

Ok, I feel we get stuck with firmware debug. There is defiinetly some wrong on you custom HW if eveything works with DK expect your customer HW.

I saw another ticket shows your HW deisgin is OK, but have you done any antenna tuning job either yourself or by your antenna provider?

We also provide free antenna tuning service for our chips, just create a new ticket and follow guide to send us your custom HW if you are not sure about your antenna performace.

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Mon, 21 Oct 2024 10:30:27 GMT

When using RTT shell this is all I get, after this it crashes. When I hit the Enter key after the last command, the shell closes automatically. I have tried this multiple times, always crashes after this point. This might have caused RTT logs to fail. How to fix that?

rtt:~$ at AT+CGMR
mfw_nrf9160_1.3.6
OK

rtt:~$ Modem domain event: Search done
Network registration status: unknown
LTE cell changed: ID: -1, Tracking area: -1

rtt:~$ 
rtt:~$ at AT+CFUN=4
Network registration status: not registered
OK

rtt:~$ at AT%XSYSTEMMODE=0,1,0,0
OK

rtt:~$ at AT+CFUN=1
OK

rtt:~$ at AT+CGDCONT?
OK

rtt:~$ at AT%CONEVAL
%CONEVAL: 1
OK

rtt:~$ Network registration status: searching
Currently active system mode: NB-IoT
LTE cell changed: ID: 279440, Tracking area: 49173

RE: Need help connecting to MQTT using nRF9160

Charlie — Mon, 14 Oct 2024 12:26:08 GMT

It should look like this.

mosh:~$ > at AT+CFUN=1
at AT+CFUN=1
OK

PDN event: PDP context 0 activated
PDN event: PDP context 0 IPv6 up
mosh:~$ > at AT%CONEVAL
at AT%CONEVAL
%CONEVAL: 0,1,9,73,15,34,"03238D05","24201",457,6400,20,0,0,-13,1,1,88
OK

mosh:~$ > at AT%CONEVAL
at AT%CONEVAL
%CONEVAL: 0,1,7,73,11,26,"03238D05","24201",457,6400,20,0,0,-13,1,1,88
OK

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Mon, 14 Oct 2024 11:31:30 GMT

Trace was recorded for about 10mins, but looks like there was only activity for 34sec.

I just tried running AT%CONEVAL just after boot (before connection) on my DK and this is what I got:

rtt:~$ at AT%CONEVAL
%CONEVAL: 1
OK

Is this expected?
I'll try with my custom board a bit later.

RE: Need help connecting to MQTT using nRF9160

Charlie — Mon, 14 Oct 2024 08:50:37 GMT

Hi Pranav,

Thanks for sharing. I mange to open it and see the same information, but unfortunately, the modem trace only show 34-sconds communication and device stop at trying to attched to NB netrowk.

Have you try to wait a bit longer so there might be some reject resone give by basestation side? Or device keeping stucking like this?

Running AT%CONEVAL before CFUN=1 can provide more informaiton about sournding network.

docs.nordicsemi.com/.../coneval_set.html

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Thu, 10 Oct 2024 06:01:38 GMT

Custom Board uses 1.3.5 afaik. It's opening on my system. On the Cellular Monitor app, I don't know why the AT Commands are missing on when I select 1.3.5. When I select 1.3.6 AT commands are shown.

RE: Need help connecting to MQTT using nRF9160

Charlie — Wed, 09 Oct 2024 15:13:43 GMT

Hi Pranav,

Do you convert them to show on Wireshark with Cellular Monitor succesfully?

I can successfully convert nRF9160DK modem trace with MFW1.3.5(after chekcing you another ticket), but not your custom board recording, do you know which MFW version it uses?

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Wed, 09 Oct 2024 10:19:24 GMT

Thanks, I was able to get the log file. I have attached log trace files for DK & custom board. The DK connects to the network and sends messages through MQTT. Custom Board did not send messages, I stopped the trace collection after about 10mins.

devzone.nordicsemi.com/.../nRF9160DK_5F00_mqtt_5F00_pub_5F00_Trace_5F00_09102024_2D00_135810.log

devzone.nordicsemi.com/.../Custom_5F00_Board_5F00_mqtt_5F00_pub_5F00_Trace_5F00_09102024_2D00_154345.log

RE: Need help connecting to MQTT using nRF9160

Charlie — Tue, 08 Oct 2024 13:00:51 GMT

Hi Pranav,

The link you point to using a quite old mfw, so this might be the reason.

Could you refer to the link I point to https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/nrf/libraries/modem/nrf_modem_lib/nrf_modem_lib_trace.html? Assuming your firmware still based on NCS 2.6.1 and using latest MFW 1.3.6.

I did a test with NCS 2.6.1+ MFW 1.3.6+ nrf/samples/net/mqtt smaple on nRF9160DK, and I can collect modem trace RTT log and open with Cellular Monitor as epxected. Following overlay is what I used for building.

CONFIG_NRF_MODEM_LIB_TRACE=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_LOG_BACKEND_RTT=n

CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Tue, 08 Oct 2024 11:06:33 GMT

I was not able to get the modem trace over RTT. I read another post about it. I have followed the steps but it mentions I have to record the .log file from JLinkRTTViewer. I wasn't able to get that part. I use Linux. Is there some software I have to install?
I followed this post: devzone.nordicsemi.com/.../447195

RE: Need help connecting to MQTT using nRF9160

Charlie — Tue, 08 Oct 2024 11:01:01 GMT

Do you manage to get modem trace from nRF9160DK? then how about your custom devcie?

I see another HW reveiw ticket is undergoing. Let me know when you get HW ready and able to provide more debugging info.

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Fri, 04 Oct 2024 07:36:02 GMT

I was able to get MQTT working with Jio in India. But the same firmware isn't working in South Africa with Vodacom NB-IoT. Here's the log and trace. I want to get the firmware working with the DK. I have opened another issue for my custom board connection problems.

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_10_2D00_04T06_2D00_22_2D00_12.925Z.mtrace

*** Booting nRF Connect SDK 3758bcbfa5cd ***
[00:00:00.496,185] <inf> nrf_modem_lib_trace: Trace thread ready
[00:00:00.503,814] <inf> nrf_modem_lib_trace: Trace level override: 2
[00:00:00.508,941] <inf> LTE: Connecting to LTE network
[00:00:00.511,077] <inf> LTE: lte_lc_system_mode_set: 0
[00:00:00.537,811] <inf> LTE: lte_lc_connect_async: 0
[00:01:54.258,575] <inf> LTE: Network registration status: Connected - home network
[00:01:54.258,697] <inf> LTE: Connected to LTE network
[00:01:54.258,728] <inf> LTE: ====== Cell Network Info ======
[00:01:54.260,284] <inf> LTE: Signal strength: 53
[00:01:54.261,047] <inf> LTE: Current LTE band: 8
[00:01:54.261,749] <inf> LTE: Supported LTE bands: (1,2,3,4,5,8,12,13,17,19,20,25,26,28,66)
[00:01:54.262,542] <inf> LTE: Tracking area code: 8CA1
[00:01:54.263,214] <inf> LTE: Current mode: 0
[00:01:54.263,977] <inf> LTE: Current operator name: 65501
[00:01:54.264,923] <inf> LTE: Cell ID of the device: 0E241F17
[00:01:54.266,082] <inf> LTE: IP address of the device: 100.xx.xx.xxx
[00:01:54.266,632] <inf> LTE: Modem firmware version: mfw_nrf9160_1.3.5
[00:01:54.267,364] <inf> LTE: LTE-M support mode: 0
[00:01:54.268,005] <inf> LTE: NB-IoT support mode: 1
[00:01:54.268,676] <inf> LTE: GPS support mode: 0
[00:01:54.269,256] <inf> LTE: Mobile network time and date:
[00:01:54.269,256] <inf> LTE: ===============================
[00:01:54.269,714] <inf> MQTT: Connection to broker using mqtt_init
[00:02:06.240,570] <inf> MQTT: Successfully connected to MQTT broker
[00:03:06.240,753] <err> mqtt_helper: Cloud MQTT keepalive ping failed: -128

RE: Need help connecting to MQTT using nRF9160

Charlie — Tue, 01 Oct 2024 13:49:10 GMT

Ok, could you test with an official sample like https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/applications/serial_lte_modem/README.html?

You can test on nRF9160DK board first if you have one.

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Tue, 01 Oct 2024 10:47:54 GMT

I added the 2 configs to prj.conf file but I can't find the .log trace file

RE: Need help connecting to MQTT using nRF9160

Charlie — Tue, 01 Oct 2024 09:22:25 GMT

You can refer to the following document to enable Modem trace through RTT

https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/libraries/modem/nrf_modem_lib/nrf_modem_lib_trace.html#modem_tracing_with_rtt

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Mon, 30 Sep 2024 14:31:05 GMT

How do I get modem trace through RTT? My custom board does not have free UART ports for logging.

RE: Need help connecting to MQTT using nRF9160

Charlie — Mon, 30 Sep 2024 11:04:58 GMT

1) For the original sample docs.nordicsemi.com/.../description.html, if you want to use username & password to connect with MQTT broker, you need to add username & password parameters here:

https://github.com/nrfconnect/sdk-nrf/blob/2bae3437305bc8f5eb29260ca545fb8033b2b80b/samples/net/mqtt/src/modules/transport/transport.c#L187

struct mqtt_helper_conn_params {

/* The hostname must be null-terminated. */

struct mqtt_helper_buf hostname;

struct mqtt_helper_buf device_id;

struct mqtt_helper_buf user_name;

struct mqtt_helper_buf password;

};

2) For your custom board connection issue, can you attach the log and modem trace?

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Wed, 25 Sep 2024 10:55:47 GMT

I was able to get Jio SIMs and I'm able to connect to the network. But my MQTT program still doesn't work. It works only for brokers without username & password. The broker I want to connect to has username, password & port (My program is in the body of this post).

Also the network is getting connected on the nRF9160DK but not my custom board. What could be the reason?

RE: Need help connecting to MQTT using nRF9160

Charlie — Wed, 18 Sep 2024 13:22:35 GMT

Yes, only JIO network is found by your device according to AT%COPS=? feedback.

MCC	MNC	PLMN	Region	Country	ISO	Operator	Brand	TADIG	Bands
405	861	405861	Asia and the Middle East	India	IN	Karnataka	Jio	INDJ9	LTE 850 / LTE 1800 / TD-LTE 2300

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Wed, 18 Sep 2024 11:16:10 GMT

Airtel says that the SIMs they've sent are NB-IoT SIMs.
But this confirms that there is no Airtel signal right? Is there any other ways of pin pointing the issue?
I'm not able to fine LTE Link Monitor app on nRF Connect. Any idea why? I'm using Linux and the latest appimage.

mosh:~$ > at AT%COPS=?
at AT%COPS=?
%COPS: (1,"","","405861",9)
OK

Network registration status: searching
LTE cell changed: ID: -1, Tracking area: -1
Currently active system mode: NB-IoT
LTE cell changed: ID: 2894737, Tracking area: 49173
mosh:~$ > at AT%COPS=?
at AT%COPS=?
Currently active system mode: None
%COPS: (1,"","","405861",9)
OK

LTE cell changed: ID: -1, Tracking area: -1
RRC mode: Connected
Currently active system mode: NB-IoT
LTE cell changed: ID: 6032786, Tracking area: 49173
RRC mode: Idle
Modem domain event: Search done
mosh:~$ > at AT%COPS=?
at AT%COPS=?
Currently active system mode: None
%COPS: (3,"","","405861",9)
OK

LTE cell changed: ID: -1, Tracking area: -1

RE: Need help connecting to MQTT using nRF9160

Charlie — Mon, 16 Sep 2024 11:52:36 GMT

(+) How to Activate the nRF Cloud using Airtel M2M sim card? - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

(+) steps for lte registration. - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

(+) Verification failed - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

Mobile IoT Deployment Map | Internet of Things (gsma.com) shows only JIO supports NB-IoT in India. Please have a try with JIO NB-IoT network.

Best regards,

Charlie

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Fri, 13 Sep 2024 09:44:58 GMT

I'm trying to figure out why it's not connecting to the network, the ISP says the SIMs are fine. When I try using Modem Shell to connect manually, I'm getting few errors. It would be great if you can help me connect to the network. Please check if the way I'm adding APN details are correct. I have attached the trace file of the Modem Shell, hope that helps.

mosh:~$ > link connect --apn "airteliot.com" -f 'ipv4v6' -A 0 -U "" -P ""
link connect --apn "airteliot.com" -f 'ipv4v6' -A 0 -U "" -P ""
pdn_activate() failed, err -8 esm 0 <unknown>

[00:01:03.817,352] <wrn> pdn: Failed to activate PDN for CID 1, err 65536
mosh:~$ > link funmode -1
link funmode -1
Release 14 features enable AT-command error, type 1 err 0
lte_lc_system_mode_set returned error -14
Functional mode set successfully: normal
[00:01:14.231,323] <err> lte_lc: Could not send AT command, error: 65536
mosh:~$ > link sysmode -n --pref_nbiot
link sysmode -n --pref_nbiot
Cannot set system mode to modem: -14
Requested mode couldn't set to modem. Not in flighmode nor in pwroff?
sysmode 2 saved successfully to settings
LTE preference 2 saved successfully to settings
[00:01:21.959,320] <err> lte_lc: Could not send AT command, error: 65536
mosh:~$ > link connect --apn "airteliot.com" -f 'ipv4v6' -A 0 -U "" -P ""
link connect --apn "airteliot.com" -f 'ipv4v6' -A 0 -U "" -P ""
pdn_activate() failed, err -8 esm 0 <unknown>

[00:01:27.975,372] <wrn> pdn: Failed to activate PDN for CID 1, err 65536
Modem domain event: Search done
Network registration status: searching
LTE cell changed: ID: -1, Tracking area: -1
mosh:~$ > link funmode --normal_no_rel14
link funmode --normal_no_rel14
Release 14 features disable AT-command error, type 1 err 0
lte_lc_system_mode_set returned error -14
Functional mode set successfully: normal
[00:02:51.416,839] <err> lte_lc: Could not send AT command, error: 65536
Network registration status: unknown
Network registration status: searching

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_09_2D00_13T09_2D00_38_2D00_29.062Z.mtrace

RE: Need help connecting to MQTT using nRF9160

Charlie — Tue, 03 Sep 2024 12:53:49 GMT

The firmware support both networks so it is not a problem. Converting the modem trace to pcapng file with Cellular Monitor and open with Wireshark.

I found the devic is rejected by the network with EMM cause 11.

Cause #11 – PLMN not allowed

This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a PLMN where the UE, by subscription or due to operator determined barring, is not allowed to operate.

Please double check with your network operator if you have a valid subscription, and you have correct PDN if it needs to be set.

Best regards,

Charlie

devzone.nordicsemi.com/.../modemtracee.pcapng

RE: Need help connecting to MQTT using nRF9160

pranav-ether — Mon, 02 Sep 2024 12:59:45 GMT

Hi any update on this? I've not been able to get network connection. I'm using Airtel IoT SIM card