LTE connected but cannot able nto connect AWS.

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. 

Parents Reply
  • Hi charlie,

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

    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

Children
  • 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

  • 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

  • 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

  • Hi charlie,

    Can you share the modem trace recording?

    Can you help me to get modem trace recording  i have no idea how to get it.

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

    we have already designed a new nrf9160 custom board but in this new custom board only we are getting this AWS connection error.

    Thanks

  • Hi Jagadish,

    Jagadish M said:
    Can you help me to get modem trace recording  i have no idea how to get it.

    Yes, just search "nrf9160 modem trace" and you would find documents and lots of discussion on Devzone.

    Jagadish M said:

    we have already designed a new nrf9160 custom board but in this new custom board only we are getting this AWS connection error.

    Nordic provides free HW reviews for your design to make sure you get good RF performance on your design. In this case, you may have a bad antenna design which causes bad signal quality for your device. This is why I also suggest you check the %CESQ notification with at client sample to confirm.

    Best regards,

    Charlie

Related