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.

SmartConfig does not acknowledge

Other Parts Discussed in Thread: CC3200

Hello,

I'm trying to adapt the code from TI SimpleLink Wifi starter app (Android) to my mobile app.

The CC3200 receives the wifi parameters from the Android device and connects to the wifi network. But the Android device does not receive acknoledgement. Thus, the FTC_SUCCESS event is not fired.

I suspect that it is an issue with the parameter "ackstring". According to the following doc, on CC3000 ackstring is set to "CC3000" by default.

processors.wiki.ti.com/.../CC31xx_%26_CC32xx_Wi-Fi_Starter_App_Development_Information_(Android)

But this doc is does not seem to be up to date. And I can't figure out how to set ackstring, neither on the CC3200 board nor on the Android device.

Could you help me with this issue? And could you also tell me where to find the updated documentation of SmartConfig library for iOS and Android?

Thanks.

  • I was just about to post a similar question for the same problem
    I look forward to seeing the answer
    Trevor
  • Same problem here.

    I think this can help us:
    e2e.ti.com/.../1480280
  • I've spent some time to better understand TI simplelink Wifi starter app. It does not use any acknowledgement from SmartConfig lib. Here is the process of the app :

    1. The app scans all devices found on the local wifi network, using mDNS protocol.

    2. The app sends configuration to CC3200 using SmartConfig.

    3. The app scans again the network with mDNS. If it finds a device that has not been seen previously, it assumes it is the CC3200, and notifies user that SmartConfig has succeeded.

    Thus, I understand that we cannot rely on SmartConfig lib for acknowledgement. We have to get acknowledgement by another way. mDNS is one possibility. I thought about another possibility: CC3200 posts an acknowledgement to a cloud server while connected, and the mobile app gets the acknowledgement from the server.

    These solutions are not perfect. If someone founds a better solution, please tell us about it.

  • Hi All,

    Lior is correct. The WiFi Starter App is not using the acknowledgement system build inside the Smart Config library. The app has another thread running mDNS detection.

    In SmartConfigFragment.java, you can see the method lookForNewDevice() is initiating mDNS scanning. Once a device is found, the foundNewDevice flag becomes true.