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.

TIDC-01002: Cannot connect my device to the cloud.

Part Number: TIDC-01002
Other Parts Discussed in Thread: SENSOR-TO-CLOUD

Hello,

I'm follow the example "Sub-1 GHz Embedded Sensor to Cloud Industrial IoT Gateway Reference Design (Rev. A)" and I cannot connect my device to the cloud.

I'm not so sure if the information I provide in section 3.2.1.1.8 step 17 are being saved properly and the same thing in section 3.2.1.1.9.1 step 11. I fill up both forms and press "save changes" but in the last step I mentioned earlier, the Cloud led should turn green after saving the changes but the led never turns green, it stays red. I checked in the IBM Watson IoT Platform and the device I created stays as disconnected.

Has anyone experienced the same thing?

Thanks.

  • Hello Pablo,

    have you checked the output of the device on the uart terminal? 

    This will help in knowing where it can be failing.

    Regards,

    AB

  • Hello AB,

    Yes, I have checked the UART Terminal and this is the message that gives me after I try to enter the information in the Sensor-To-Cloud Local Dashboard.

    [Cloud Service] TOPIC# 0: iot-2/type/gateway/id/gateway_pruebaV2/evt/nwkUpdate/fmt/json

    [Cloud Service] TOPIC# 1: iot-2/type/gateway/id/gateway_pruebaV2/evt/permitJoinCnf/fmt/json

    [Cloud Service] TOPIC# 2: iot-2/type/gateway/id/gateway_pruebaV2/evt/deviceUpdate/fmt/json
    [Cloud Service] CLIENT ID: g:choichoi92@gmail.com:gateway:
    [Cloud Service] SERVER ADDRESS: choichoi92@gmail.com.messaging.internetofthings.ibmcloud.com

    Version: Client LIB 1.1.0, Common LIB 1.2.0.
    [Cloud Service] Connection to broker failed
    , ERRORNUM: -11[Cloud Service] MQTT CLIENT disconnected, exit pthread

     


    I did all the steps shown in the guide as slowly as possible to avoid making any mistakes.

    Regards,

    Pablo

  • I think Client ID is too long, try increasing the buffer allocated for client ID on the code or make the client ID shorter. This should fix the problem

  • Ok, I'll give it a try.

    Thank you