LTE connected but cannot able nto connect AWS.

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Mon, 27 Feb 2023 11:35:34 GMT

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

RE: LTE connected but cannot able nto connect AWS.

Chbo — Mon, 27 Feb 2023 10:59:21 GMT

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.

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Fri, 24 Feb 2023 06:29:31 GMT

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.

RE: LTE connected but cannot able nto connect AWS.

Charlie — Wed, 22 Feb 2023 11:18:04 GMT

Hi Jagadish,

[quote user="Jagadish M"]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.[/quote]

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.

[quote user="Jagadish M"]We got the hardware review from your team. They said to follow you. Hardware no issue.[/quote]

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

[quote user="Jagadish M"]

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.

[/quote]

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

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Wed, 22 Feb 2023 06:51:46 GMT

Hi charlie,

[quote userid="122928" url="~/f/nordic-q-a/96209/lte-connected-but-cannot-able-nto-connect-aws/409514"]Please find the modem tracings.[/quote]

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.

[quote userid="93921" url="~/f/nordic-q-a/96209/lte-connected-but-cannot-able-nto-connect-aws/411121"] I remember you did not get your HW reviewed by us before reporting this issue.[/quote]

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

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Wed, 22 Feb 2023 04:35:06 GMT

Hi Markus Tacker,

[quote userid="24652" url="~/f/nordic-q-a/96209/lte-connected-but-cannot-able-nto-connect-aws/411214"]do you use the same SIM card in both boards[/quote]

1. Yes we used same ESIM in both custom board and developement kit board. It's working fine in developement kit but it's not working in custom board.

[quote userid="24652" url="~/f/nordic-q-a/96209/lte-connected-but-cannot-able-nto-connect-aws/411214"]does the problem happen with all your custom boards (how many have you tried)?[/quote]

2.we have 4 custom board in all 4 we are facing same issue.

[quote userid="24652" url="~/f/nordic-q-a/96209/lte-connected-but-cannot-able-nto-connect-aws/411214"]Do you use the same firmware on the DK and the custom board?[/quote]

3. Yes same firmware code used in boath custom and development board.

RE: LTE connected but cannot able nto connect AWS.

Markus Tacker (he/him) — Tue, 21 Feb 2023 22:04:04 GMT

Just to make sure, let's rule out these causes of errors:

You write that the connection works with a DK but does not with your custom board

do you use the same SIM card in both boards, if not ensure that the SIM card is activated and has data
does the problem happen with all your custom boards (how many have you tried)?
Do you use the same firmware on the DK and the custom board? If not please make sure that aws_iot module configuration aligns.

RE: LTE connected but cannot able nto connect AWS.

Charlie — Tue, 21 Feb 2023 13:40:26 GMT

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

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Tue, 21 Feb 2023 08:59:40 GMT

Hi,

waiting for your reply.

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Mon, 20 Feb 2023 12:09:04 GMT

Will you please tell me step by step procedure how can we get the modem tracings in custom board.

1. We are using JTAG for programming.

RE: LTE connected but cannot able nto connect AWS.

Markus Tacker (he/him) — Mon, 20 Feb 2023 11:31:05 GMT

It that case it would be really helpful to get a modem trace from both device so we can compare and maybe spot the differences.

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Mon, 20 Feb 2023 10:09:44 GMT

Hi Markus Tacker,

Thank you for your response,

1. We tried in developmenrt kit with same credentials it's working fine but when we tried with our custom it's not connecting to AWS.

2. We created new certificates and we tried with the development KIT and my custom board. It's working fine in development kit but it's not working in my custom board.

3. Please refer above, my custom board AT COMMAND logs.

RE: LTE connected but cannot able nto connect AWS.

Markus Tacker (he/him) — Mon, 20 Feb 2023 09:19:31 GMT

Hei, chiming in because customer asked me nicely on LinkedIn for support.

Please make sure that you have followed all the steps outlined in Create a Thing in AWS IoT exactly
To verify this step then, create and download a certificate for the device
use the downloaded certificate to verify that you have set up the permissions correctly using Mosquitto by running this command on you computer:
mosquitto_pub --cert <thing.pem> --key <thing.key> --cafile <aws-iot-rootCA.pem> -h <iothubendpoint> -p 8883 -t 'test/thing' -m "Hello from Mosquitto"
Observe the incoming message using the AWS IoT MQTT client

RE: LTE connected but cannot able nto connect AWS.

Charlie — Mon, 20 Feb 2023 08:56:41 GMT

Hi Jagadish,

Sorry for confusing you. The previous exercises on nRF9160DK help you to understand how to set up modem trace recording. nRF9160DK USB power provides a virtual COM port to access UART1.

Now you need to work on collecting modem traces for your custom board. Since it uses P13 and P14, try to connect them with USB to UART Adapter, and collect modem traces in a similar way as you did with nRF9160DK.

Please share the modem trace recording when you repeat the issue.

Best regards,

Charlie

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Fri, 17 Feb 2023 10:05:39 GMT

Hi charlie,

[quote userid="93921" url="~/f/nordic-q-a/96209/lte-connected-but-cannot-able-nto-connect-aws/410576"]Modem trace using UART1 as output backend. Can you enable modem trace in your firmware and collect modem trace from your UART1 port?[/quote]

i have to use nrf9160DK (or) our custom board? and tell me which pins i have to use for uart1?

if need to take modem trace from our custom board then we are using P13 and P14 pins are using for uart1.

is it possible to take modem trace in our custom board?

reply me ASAP so we can test modem trace based on your reply.

Thanks

RE: LTE connected but cannot able nto connect AWS.

Charlie — Fri, 17 Feb 2023 09:51:15 GMT

Hi Jagadish,

Very good! Now we can move forward a bit now.

Modem trace using UART1 as output backend. Can you enable modem trace in your firmware and collect modem trace from your UART1 port?

Maybe you need to use a USB to UART Adapter to collect with your PC. Let me know if you need more help.

Best regards,

Charlie

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Thu, 16 Feb 2023 10:17:35 GMT

Hi charlie,

devzone.nordicsemi.com/.../trace_2D00_2023_2D00_02_2D00_16T10_2D00_02_2D00_50.404Z.pcapng

devzone.nordicsemi.com/.../nfr9160dk.bin

Please find the attached tracing file from nrf9160DK develpement kit. but cannot able to find from custom board. Custom board connected to nrf9160DK board over JTAG.

RE: LTE connected but cannot able nto connect AWS.

Charlie — Wed, 15 Feb 2023 11:11:08 GMT

Hi Jagadish,

The recording nRF9160DK.bin is still not valid. Let's do a simple test with your nRF9160DK.

1) You can build nRF9160: AWS IoT — nRF Connect SDK 2.2.0 documentation (nordicsemi.com) by just adding "CONFIG_NRF_MODEM_LIB_TRACE=y" and getting firmware.

2) Open Trace Collector V2 preview and start tracing, you will see File size increasing.

3) The pcapng file can be opened by Wireshark and you would find communication traffic in different levels of the OSI model.

Can you confirm everything works with this flow?

Best regards,

Charlie

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Tue, 14 Feb 2023 11:07:20 GMT

Hi charlie,

devzone.nordicsemi.com/.../nrf9160DK.bin

Please find the attached file nrf9160 development kit modem tracing.

I can't able to find the custom board tracings, in the trace collector itself port not showing, but port showing in programmer.

RE: LTE connected but cannot able nto connect AWS.

Charlie — Mon, 13 Feb 2023 11:25:55 GMT

Hi Jagadish,

If you convert the file with Trace Collector V2 preview to PCAP and open it with Wireshark. You would be able to find It is still empty. Did you try nRF9160DK first and follow the steps mentioned in the documents? Let me know if you can or not successfully record the modem trace with nRF9160DK first.

Searching "custom nrf9160 modem trace" in Devzone you would find many discussions on this topic.

I really want to help you but I cannot without seeing the modem trace to analyse what happens with the communication traffic of your device.

Best regards,

Charlie

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Mon, 13 Feb 2023 09:22:37 GMT

Hi charlie,

devzone.nordicsemi.com/.../trace_2D00_2023_2D00_02_2D00_07T10_2D00_33_2D00_48.624Z.bin

Please find the modem tracings.

RE: LTE connected but cannot able nto connect AWS.

Charlie — Mon, 13 Feb 2023 08:00:08 GMT

Modem trace is different from log output. Please record a valid modem trace recording from your issue device and share it with me.

Try to use nRF9160DK to record modem trace first they try with your device.

Best regards,

Charlie

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Sat, 11 Feb 2023 10:48:45 GMT

Hi charlie,

Waiting for your response.

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Sat, 11 Feb 2023 04:24:25 GMT

Hi charlie,

Waiting for your reply.

RE: LTE connected but cannot able nto connect AWS.

Jagadish M — Fri, 10 Feb 2023 04:58:38 GMT

Hi charlie,

Sorry for mistake the logs which i have sent in previous reply is to compare our custom board logs (AT+CFUN=1 and AT+CFUN?) with nrf9160dk(Development kit) logs.

please look into previous reply AT commands logs.

please compare those both AT logs and let us know the issue.

Thanks