nrf9160 Custom Board connectivity to nrf cloud

Dear Nordic devzone community,

I am using nrf connect SDK version 1.8.0 for the asset tracker and 2.0.2 for AT client. IDE is Vscode Studio.

I have designed a custom board using nRF9160 and I am able to send and read out certain AT commands which confirms to me that most of the embedded part of the design functions fine.

1)Now in order to use the dashboard of nordic cloud I need to get the IMEI and Pin #, this is normally on the DK indicated with the sticker.

I am able to get the IMEI # by AT+CGSN command, now the issue is how to get 6 digits PIN # ?

2)To connect with the LTE Link monitor with my custom board I am using a Serial to USB converter (FTDI), the LTE Link monitor does not recognize this device. You can see that in the attached images. however, if I open my COMport I can send and receive AT commands..

3)The same is the case with the programmer, I want to load the certificates and modem firmware on a custom board nrf9160 chip .as you can see in the attached image.

4)Custom Board is replying to the AT commands as mentioned in the attached image but not responding to the AT+CPIN command to recognize the SIM. I have attached the schematic of the custom board as well.

A few observations while debugging the HW 

a)1.8V output to SIM card is not provided by NRF9160(using the asset tracker FW, which is provided to the DK)

b)What we left open is DETECT pin from nrf9160. But the 1.8V output pin from NRF9160 is still connected to the SIM card connector.

I followed the following links 

 Programming/Debugging nRF9160 SiP on custom board 

https://devzone.nordicsemi.com/f/nordic-q-a/58055/nrf9160-custom-board---connect-uart-and-send-at-commands/238646#238646

 nrf9160 custom board AT client not working 

 Getting HWID nRF9160 custom HW board and using LTE LINK monitor with custom Hardware 

Thanks in Advance,

Best Regards,

Muhammad Usman

 

If anything is unclear please let me know then I can send more information or support with additional attachments.

  • Hi Charlie,

    Thank you again for the help!

    I tried with SLM but still no response.

    So I tried with Asset Tracker here is the response!

    12/6/2022 03:55:42.527 [TX] - at<CR><LF>
    
    12/6/2022 03:55:43.399 [RX] - OK<CR><LF>
    
    12/6/2022 03:56:07.015 [TX] - AT+CFUN=4<CR><LF>
    
    12/6/2022 03:56:08.567 [RX] - [00:00:52.586,761] <ESC><inf> asset_tracker: LTE cell changed: Cell ID: -1, Tracking area: 65534<ESC><CR><LF>
    OK<CR><LF>
    
    12/6/2022 03:56:23.217 [TX] - AT+CFUN?<CR><LF>
    
    12/6/2022 03:56:24.257 [RX] - +CFUN: 4<CR><LF>
    OK<CR><LF>
    
    12/6/2022 03:56:33.733 [TX] - AT%XSYSTEMMODE=1,0,0,0<CR><LF>
    
    12/6/2022 03:56:34.539 [RX] - OK<CR><LF>
    
    12/6/2022 03:56:41.843 [TX] - AT+CEREG=5<CR><LF>
    
    12/6/2022 03:56:42.686 [RX] - OK<CR><LF>
    
    12/6/2022 03:56:49.668 [TX] - AT+CFUN=1<CR><LF>
    
    12/6/2022 03:56:50.515 [RX] - OK<CR><LF>
    
    12/6/2022 03:56:57.845 [TX] - AT+CFUN?<CR><LF>
    
    12/6/2022 03:56:58.672 [RX] - +CFUN: 1<CR><LF>
    OK<CR><LF>
    
    12/6/2022 03:57:07.657 [TX] - AT#XPING="www.google.com",45,5000,5,1000<CR><LF>
    
    12/6/2022 03:57:09.727 [RX] - [00:01:53.734,619] <ESC><err> at_host: Error while processing AT command: -8<ESC><CR><LF>
    ERROR<CR><LF>
    
    12/6/2022 03:57:21.462 [TX] - AT#XPING="www.google.com",45,5000,5,1000<CR><LF>
    
    12/6/2022 03:57:23.537 [RX] - [00:02:07.544,525] <ESC><err> at_host: Error while processing AT command: -8<ESC><CR><LF>
    ERROR<CR><LF>

    Thanks & Regards,

    Muhammad Usman

  • Hi Muhammad,

    1) Which SLM you are using? The prebuilt one from nRF9160 DK application and modem firmware or nRF9160: Serial LTE modem — nRF Connect SDK 2.1.2 documentation (nordicsemi.com) built by yourself? Could you try both?

    2) Could you wait longer after AT+CUFN=1? The device needs to take some time to connect to the network.

    You need to wait until +CEREG comes with 1(registered with home network) or 5(registered with roaming network).

    Best regards,

    Charlie

  • Hi Charlie!

    Thank you so much for the response, i tried nRF9160: Serial LTE modem — nRF Connect SDK 2.1.2 documentation (nordicsemi.com)  and it worked

    here is the output

    12/8/2022 01:15:52.162 [TX] - AT+CFUN=4<CR><LF>
    
    12/8/2022 01:15:53.952 [RX] - <CR><LF>
    OK<CR><LF>
    
    12/8/2022 01:16:02.497 [TX] - AT+CFUN?<CR><LF>
    
    12/8/2022 01:16:04.037 [RX] - <CR><LF>
    +CFUN: 4<CR><LF>
    <CR><LF>
    OK<CR><LF>
    
    12/8/2022 01:16:16.858 [TX] - AT%XSYSTEMMODE=1,0,0,0<CR><LF>
    
    12/8/2022 01:16:19.232 [RX] - <CR><LF>
    OK<CR><LF>
    
    12/8/2022 01:16:26.622 [TX] - AT+CEREG=5<CR><LF>
    
    12/8/2022 01:16:27.894 [RX] - <CR><LF>
    OK<CR><LF>
    
    12/8/2022 01:16:37.656 [TX] - AT+CFUN=1<CR><LF>
    
    12/8/2022 01:16:39.311 [RX] - <CR><LF>
    OK<CR><LF>
    <CR><LF>
    +CEREG: 2,"9003","050C4711",7<CR><LF>
    <CR><LF>
    +CEREG: 5,"9003","050C4711",7,,,"00001010","11000001"<CR><LF>
    
    12/8/2022 01:16:48.287 [TX] - AT+CFUN?<CR><LF>
    
    12/8/2022 01:16:49.526 [RX] - <CR><LF>
    +CFUN: 1<CR><LF>
    <CR><LF>
    OK<CR><LF>
    
    12/8/2022 01:16:57.935 [TX] - AT#XPING="www.google.com",45,5000,5,1000<CR><LF>
    
    12/8/2022 01:16:59.886 [RX] - <CR><LF>
    OK<CR><LF>
    #XPING: 0.267 seconds<CR><LF>
    #XPING: 0.270 seconds<CR><LF>
    #XPING: 0.285 seconds<CR><LF>
    #XPING: 0.274 seconds<CR><LF>
    #XPING: 0.280 seconds<CR><LF>
    #XPING: average 0.275 seconds<CR><LF>
    

    Ping successful 

    Then what do you suggest where is the issue?  

    Thanks & Regards,

    Muhammad Usman

  • Hi Mhumannad,

    Great! Good to hear both SLM and XPING work on your device now.

    Next step, let´s provision your custom nRF9160 device with Just-In-Time Provisioning and run the Assert tracker V2 again.

    I have a guide about nRF Cloud Access Provisioning including Decision flow for nRF Cloud Provisioning. You basically follow the red line in the flowchart.

    Please pay attention that your custom board is not officially supported by Assert Tracker V2, so this application may be not fully functional on your board. but if you build with nRF9160dk_nrf9160_ns, we should at least see the device connect with nRF Cloud if you correctly provision the chip to nRF Cloud correctly. Let me see what you can get.

    Best regards,

    Charlie

  • Hi Charlie 

    Thank you so much for the help!

    Sure I will go through it and update you soon on this my findings after testing on "LTE IoT 4 Click board"

    Thanks & regards,

    Muhammad Usman

Related