<![CDATA[Design strategy for qt mqtt networking]]>Hello guys i'm trying to ue qt mqtt for communication between robot and qt application with azure cloud. As i know if the sensor data from robot is passed through cloud to the qt app their will be some delay, so considering that robot is in the range of qt application radio/wifi ragne, what is the best design strategy to do the both?

]]>https://forum.qt.io/topic/132755/design-strategy-for-qt-mqtt-networkingRSS for NodeWed, 01 Jul 2026 02:10:41 GMTMon, 13 Dec 2021 07:35:16 GMT60<![CDATA[Reply to Design strategy for qt mqtt networking on Wed, 15 Dec 2021 16:44:28 GMT]]>It does not matter how robot is connected. Qt mqtt goes with your qt app. You may have to use mqtt + C++(or whatever, java, or c) inside robot since you do not use qt in the robot. You can do it, but it is not necessary.

]]>https://forum.qt.io/post/694872https://forum.qt.io/post/694872Wed, 15 Dec 2021 16:44:28 GMT<![CDATA[Reply to Design strategy for qt mqtt networking on Wed, 15 Dec 2021 16:30:09 GMT]]>@Dinesh-Lama remember that the MQTT protocol is publish/subscribe oriented, and it uses a broker as middle-man.
So if the answer to @SGaist question is yes, you can connect directly to your robot, you may want to run the MQTT broker in the same location where you run your Qt application.
This way you'll remove the dependency with the cloud approach.

]]>https://forum.qt.io/post/694871https://forum.qt.io/post/694871Wed, 15 Dec 2021 16:30:09 GMT<![CDATA[Reply to Design strategy for qt mqtt networking on Mon, 13 Dec 2021 20:11:54 GMT]]>Hi,

Does your robot provide a mean to connect to it directly ?

]]>https://forum.qt.io/post/694571https://forum.qt.io/post/694571Mon, 13 Dec 2021 20:11:54 GMT