LTE connected but cannot able nto connect AWS.

[Jagadish M]

Hi,

we are using nrf9160 custom board. Modem connected to LTE network but it is not connected to AWS cloud service. It's giving the -111 error, means connection refused. But with same esim card connected to AWS modem version of 1.2.3. 

[Charlie]

Hi Jagadish,

I assume you are playing NCS2.2.0 nRF9160: AWS IoT with your custom board. If yes, please check if you are using nRF9160 Rev2 and confirm you have updated the modem firmware to MFW v1.3.4.

Please share the full log printout and modem trace recording, so we would be able to help you analyse more details on the communication traffic.

Best regards,

Charlie

[Jagadish M]

Hi charlie,

My custom board modem firmware version is 1.3.2. Yes, it is NCS2.2.0 nRF9160: AWSIoT.

And my nrf9160 development kit MFW is 1.3.2 Our aws_iot code is working in my development kit and i have another nrf9169 custom board with MFW is 1.3.2 in this also aws_iot code is working

But is not working our new nrf9160 custom  board which is MFW is 1.3.2 

I will try to upgrade the modem firmware also and i will update you the response.

please let me know is their any other reason why our new nrf9160 custom is not working when i use aws_iot.

thank you

[Jagadish M]

Hi Charalie,

is their any document available to update modem firmware in nrf9160 custom board using J-tag or any other way

Thank you

[Charlie]

Hi Jagadish,

It is same as nRF9160DK Updating the modem firmware.

Best regards,

Charlie

[Jagadish M]

Hi charlie,

i have upgraded the modem firmware but still issue was not resolved its not connecting to AWS in our custom board.

Jagadish M said:

And my nrf9160 development kit MFW is 1.3.2 Our aws_iot code is working in my development kit and i have another nrf9169 custom board with MFW is 1.3.2 in this also aws_iot code is working

As previous reply i said our aws_iot code is working in development kit and another custom board too

but not working in our new custom board

thank you

[Charlie]

Hi Jagadish,

1) Did you require HW require for your new custom board? what is the link to this case?

2) Can you share the modem trace recording?

Best regards,

Charlie

[Jagadish M]

Hello charlie, 

we have updated Modem firmware 1.3.2 to 1.3.4 and SDK version  is 2.2.0

Please find the below log for your reference aws_iot in  nrf9160  example giving this below logs. I have  tested same code in nrf9160dk board its working fine. 

when i run same code in our nrf9160 custom board its not working and below is the log

*** Booting Zephyr OS build v3.2.99-ncs1 ***
The AWS IoT sample started, version: v1.0.0

LTE cell changed: Cell ID: 26892034, Tracking area: 1500

RRC mode: Connected

RRC mode: Idle

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


LTE cell changed: Cell ID: 2840579, Tracking area: 49200

RRC mode: Connected

Network registration status: Connected - roaming

PSM parameter update: TAU: 3240, Active time: -1

Date time obtained

Next connection retry in 30 seconds

AWS_IOT_EVT_CONNECTING

RRC mode: Idle

RRC mode: Connected

W: sntp_query, error: -116

E: mqtt_connect, error: -111

Awaiting for your response 

Thank you

[Charlie]

Hi Jagadish,

Can you provide the information I requested in the former reply?

1) Did you require HW require for your new custom board? what is the link to this case?

2) Can you share the modem trace recording?

The two error codes show the connection may be bad and not stable. Have you checked the signal quality through %CESQ notification?

#define ECONNREFUSED 111 /* Connection refused */

#define ETIMEDOUT 116 /* Connection timed out */

Best regards,

Charlie