• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 42 subscribers
  • Views 319 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CC3220SF: CC3220SF:

Yashavanth B
Prodigy 100 points
Part Number: CC3220SF


Tool/software: Code Composer Studio

CC322OSF: Azure SDK failing sometimes

I am facing some issues in Azure SDK 

IoTHubClient_LL_SendEventAsync(gIoTHubClientHandle, message->messageHandle, SendConfirmationCallback, (void *)message); 

I am calling the above function after the MQTT initialization when I am pushing the data using these function some times I am getting IOTHUB_CLIENT_CONFIRMATION_ERROR.

these are the response message I got Confirmation[112] received for message tracking id = 114 with result = IOTHUB_CLIENT_CONFIRMATION_ERROR, internet connection is also good.

1. IOTHUB_CLIENT_CONFIRMATION_ERROR I will come after some  100 to  200 packets transmitted.

2. In that stage the internet acess will be their of CC322OF.

Regards 

Yashvanth B

  • 0
    TI__Mastermind 30820 points

    Hi Yashvanth,

    Are you making sure the ..._DoWork() function is being called to actually operate on the events?

    Are your messages all the same size? The code may be unable to build the message based on your payload and send it.

    Can you check to see which location is triggering the IOTHUB_CLIENT_CONFIRMATION_ERROR by dropping the source in your code and using breakpoints?

    Thanks,
    Ben M

  • 0 in reply to Benjamin Moore
    Prodigy 100 points

    Thanks for replay 

    1. _Dowork() function is called after pushing the data to the cloud.

    2. The message length is the same.

    3. After pushing data to cloud I am getting IOTHUB_CLIENT_CONFIRMATION_ERROR, after some packets has been sent to cloud.

  • 0 in reply to Yashavanth B
    TI__Mastermind 45025 points

    Hi Yashavanth,

    Are you able to see your device's communication log in the Azure IoT Hub website? If so, do you seen anything related to this issue there? Perhaps there will be a hint in the IoT Hub.

    Also, please let me know the version  of CCS you're using and also the version of the Azure Plugin.

    Steve

  • 0 in reply to Steven Connell
    Prodigy 100 points

    1. I am able to see the data logs in Azure IoT websites, Nothing related to  IOTHUB_CLIENT_CONFIRMATION_ERROR.

    2. CCS Version: 8.1.0.00011  Azure version 3.20.0.02.

    IOTHUB_CLIENT_CONFIRMATION_ERROR will appear only after some data push, like 10 - 15 packets.

  • 0 in reply to Yashavanth B
    TI__Mastermind 45025 points

    OK, the next thing to try is to enable logs and hopefully this would give us some more info about the error:

    These are the steps to enable logs:

    1. Link against the debug version of the library instead of release. So in your linked libraries modify:

    ${COM_TI_AZURE_CC32XX_INSTALL_DIR}/source/third_party/azure-iot-pal-simplelink/build_all/pal/lib/ccs/m4/pal_sl_release.a

    To:

    ${COM_TI_AZURE_CC32XX_INSTALL_DIR}/source/third_party/azure-iot-pal-simplelink/build_all/pal/lib/ccs/m4/pal_sl_debug.a

    And similarly do the same change from release to debug for any other linked libraries in:

    ${COM_TI_AZURE_CC32XX_INSTALL_DIR}/source/third_party/azure-iot-pal-simplelink/build_all/sdk/lib/ccs/m4/… “

     

    2. Enable the runtime log option in their application if it hasn’t been enabled already, this is done with this call:

    bool traceOn = true;

    IoTHubClient_LL_SetOption(iotHubClientHandle, OPTION_LOG_TRACE, &traceOn);

    Steve

  • 0 in reply to Steven Connell
    Prodigy 100 points

    Thanks steve for the replay

    As u told I changed release to debug of ${COM_TI_AZURE_CC32XX_INSTALL_DIR}/source/third_party/azure-iot-pal-simplelink/ and traceOn is enabled.

    But no use after 20 - 25  packets again IOT_CLIENT_CONFORMATION_ERROR

    Do anyone know the reason for this issue. 

    Is there is any other way to solve these issues.

  • 0 in reply to Yashavanth B
    TI__Expert 5825 points

    Hi Yashavanth,

    Enabling logging is done to get more info into what's causing the error, it doesn't fix the error itself. Once you performed the changes you should be seeing more output on your Console, the same place the examples output info to, can you post that output here?

    Regards,
    Gerardo