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,

Did you try to follow the advice in https://devzone.nordicsemi.com/support-private/support/302149#permalink=832315? Is there anything not clear?

Except for this issue, I have one more advice. I remember you did not get your HW reviewed by us before reporting this issue. This is not common if you have talked with our local sales and FAE team, keep in mind you could get advice and support alongside your project from our local team.

Anyway, please try to clarify your needs, and we will try our best to help you figure out the issue.

Best regards,

Charlie

[Jagadish M]

Hi charlie,

Jagadish M said:

Please find the modem tracings.

I'm expecting to clear out soon. Since nearly one month onwards I'm trying to clear out. Any how Please tell me now how to take tracings from custom board. We are connected JTAG, by using this how can we get the tracings.

Charlie said:

I remember you did not get your HW reviewed by us before reporting this issue.

We got the hardware review from your team. They said to follow you. Hardware no issue.

Yesterday I was noted, the signal strength.

AT COMMAND is AT+CESQ and response is +CESQ: 44,2,15,2.

Please tell me in this four parameters what is best value each, to connection establish with AWS.

Thanks,

Jagadish

[Charlie]

Hi Jagadish,

Jagadish M said:

I'm expecting to clear out soon. Since nearly one month onwards I'm trying to clear out. Any how Please tell me now how to take tracings from custom board. We are connected JTAG, by using this how can we get the tracings.

There is no official support to use JTAG RTT for modem trace collection, uart1 is the default option. Let me elaborate more about https://devzone.nordicsemi.com/support-private/support/302149#permalink=832315.

1. Programming your custom board with modem trace enabled firmware.

2. Use nRF9160DK as a USB to UART Converter. Erase the nRF9160DK board, connecting customer board UART1 TX Pin -> nRF9160 P0.1.

3. Use Trace Collector V2 preview connect with nRF9160DK VCOM2, and you would be able to collect modem trace from your custom board.

Jagadish M said:

We got the hardware review from your team. They said to follow you. Hardware no issue.

Yes, we can assume we have excluded the hardware issue after your modification following my colleague's advice.

Jagadish M said:

AT COMMAND is AT+CESQ and response is +CESQ: 44,2,15,2.

Please tell me in this four parameters what is best value each, to connection establish with AWS.

This means that your Reference Signal Received Power is -140dBm + 44dBm = -96 dBm, which satisfies the requirements for Cat-M1.

You can refer to our Feild Test to learn more: (+) LTE-M vs NB-IoT Field Test: How Distance Affects Power Consumption - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com).

Best regards,

Charlie

[Jagadish M]

Hi charlie,

We tried but we failed to get tracings.

Will you please tell me which pins need to connect in development kit and which pins need to connect in custom board. Please mention little bit details.

[Chbo]

Hi Jagadish,

Thankyou for your time during teams meeting. I hope, the issue is solved and able to connect AWS with three different ESIM network (1nce, wlapn and truphone). Can we close the ticket if you don't have any further query on this.

[Jagadish M]

Hello chandru,

Thank you for your support. As of now issue was resolved. There is no further quires on this we can close the ticket.

We done certificate change also now it's working fine.

Thanks & Regards,

Riosh Team