LARA-R6 modem not working, NCS V3.0.0

[ViditP]

Development Environment :

SDK version: nRF Connect SDK v3.0.0

Toolchain version: nRF Connect SDK Toolchain v3.0.0

Development environment: Ubuntu 22.04

Development tool: Visual Studio Code

Development board: nrf5340dk_nrf5340_cpuapp

Example refference path: ~/ncs/v3.0.0/zephyr/samples/net/cellular_modem

Hello, 

We are using the above sample code for interfacing of lara-r6401 LTE module with the nrf5340 DK. 

When we flash the sample code we are facing the below error.

Powering on modem
Bring up network interface
Waiting for L4 connected
[00:00:10.799,438] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_set_baudrate_chat_script
[00:00:10.799,468] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_set_baudrate_chat_script: step: 0
[00:00:10.799,499] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:00:11.799,591] <wrn> modem_chat: u_blox_lara_r6_set_baudrate_chat_script: timed out
[00:00:11.799,774] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_init_chat_script
[00:00:11.799,804] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_init_chat_script: step: 0
[00:00:11.799,835] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:00:21.799,926] <wrn> modem_chat: u_blox_lara_r6_init_chat_script: timed out
[00:00:32.300,201] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_set_baudrate_chat_script
[00:00:32.300,231] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_set_baudrate_chat_script: step: 0
[00:00:32.300,262] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:00:33.300,354] <wrn> modem_chat: u_blox_lara_r6_set_baudrate_chat_script: timed out
[00:00:33.300,537] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_init_chat_script
[00:00:33.300,567] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_init_chat_script: step: 0
[00:00:33.300,598] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:00:43.300,689] <wrn> modem_chat: u_blox_lara_r6_init_chat_script: timed out
[00:00:53.800,994] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_set_baudrate_chat_script
[00:00:53.801,025] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_set_baudrate_chat_script: step: 0
[00:00:53.801,055] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:00:54.801,147] <wrn> modem_chat: u_blox_lara_r6_set_baudrate_chat_script: timed out
[00:00:54.801,330] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_init_chat_script
[00:00:54.801,361] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_init_chat_script: step: 0
[00:00:54.801,361] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:01:04.801,483] <wrn> modem_chat: u_blox_lara_r6_init_chat_script: timed out
[00:01:15.301,788] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_set_baudrate_chat_script
[00:01:15.301,818] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_set_baudrate_chat_script: step: 0
[00:01:15.301,849] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:01:16.301,940] <wrn> modem_chat: u_blox_lara_r6_set_baudrate_chat_script: timed out
[00:01:16.302,124] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_init_chat_script
[00:01:16.302,154] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_init_chat_script: step: 0
[00:01:16.302,185] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:01:26.302,276] <wrn> modem_chat: u_blox_lara_r6_init_chat_script: timed out
[00:01:36.802,551] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_set_baudrate_chat_script
[00:01:36.802,581] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_set_baudrate_chat_script: step: 0
[00:01:36.802,612] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:01:37.802,703] <wrn> modem_chat: u_blox_lara_r6_set_baudrate_chat_script: timed out
[00:01:37.802,886] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_init_chat_script
[00:01:37.802,917] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_init_chat_script: step: 0
[00:01:37.802,947] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:01:47.803,039] <wrn> modem_chat: u_blox_lara_r6_init_chat_script: timed out
[00:01:58.303,314] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_set_baudrate_chat_script
[00:01:58.303,344] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_set_baudrate_chat_script: step: 0
[00:01:58.303,375] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:01:59.303,466] <wrn> modem_chat: u_blox_lara_r6_set_baudrate_chat_script: timed out
[00:01:59.303,649] <dbg> modem_chat: modem_chat_script_start: running script: u_blox_lara_r6_init_chat_script
[00:01:59.303,649] <dbg> modem_chat: modem_chat_script_next: u_blox_lara_r6_init_chat_script: step: 0
[00:01:59.303,680] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
L4 was not connected in time

Attaching the sample code with few modifications we made in it for testing purpose, can you please look into it and let us know if we are missing something.

2158.cellular_modem_lara_r6.zip

Thanks.

[Michal]

Hello,

Since the modem used is not a Nordic product, there is a limited amount that I am able to help out with this issue.

I see that it is a u-blox module (though their LTE business is now owned by Trasna). Have you checked if they have any specific code samples or instructions for using that module? I seem to remember that u-blox had their own SDK as well.

Possibly you may want to contact Trasna as well, or check on the Zephyr discord server for any people with possibly more experience with that setup.

Best regards,

Michal

[ViditP]

 Michal ,

Thanks for the feedback,

We are having one more issue maybe you will be able to help with that.

On a working setup, using LARA-R6 we are making a connection with the AWS server and periodically sending data, Moreover, when we are not sending the data we are sending a ping at a regular intervals to ensure that AWS is connected.

Our issue regarding this is, we are able to make the connection and send the data periodically and also getting the acknowledgement for the sent data.

But after an our or so, we are sending the data but not receiving the response from the server. This behaviour becomes more frequent and we don't get the ACK from the server.

Any guidance about what can be causing this kind of behaviour will be helpful.

Thanks.

[Michal]

Do you have any kind of logs showing that issue?

How are you connecting to AWS, which library are you using?