• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 663 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.

Original question:

CC3220SF-LAUNCHXL: Capturing and analyzing MQTT packets in MQTT Client Demo for CC3220SF Launchpad

CC3220SF-LAUNCHXL: Capturing and analyzing MQTT packets in MQTT Client Demo for CC3220SF Launchpad

Nour mohamed
Expert 2875 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

Hello everyone, 

I have followed the MQTT Client demo in:

using a CC3220SF Launchpad and it's working properly. Now does this demo follow the MQTT standards? I mean the packets sent and received are they following all the MQTT standards?

Thank you,

  • 0
    TI__Mastermind 34960 points
    Hi Nour,

    The demo works with 3rd party devices (eg. m2m.eclipse.org, mqtt apps for Android/IOS, etc) which use MQTT, so it should follow the MQTT standards.

    Let us know if you have any doubts on some part of the standard with regards to the demo.


    Regards,
    Toby
  • 0 in reply to Toby
    Expert 2875 points
    Hello sir,

    I am working on it, I'll let you know!

    Is there a way to know if a certain subscriber is connected to which broker? In other words, can I know which broker the launchpad is connected to without looking at the code?


    Thank you,
  • 0 in reply to Nour mohamed
    TI__Mastermind 34960 points
    MQTT is based on TCP connection, so it's equivalent to asking if you know which server (broker) the client (launchpad) is connected to.

    To use the provided MQTT library, you need to define which server will act as broker (Check MqttClient_start() in mqtt_client_app.c. The SERVER_ADDRESS field in Mqtt_ClientCtx is the broker). Afterwards, the underlying MQTT process (including TCP) is taken care of by the library.

    You can always print the SERVER_ADDRESS via UART.