Differences

This shows you the differences between two versions of the page.

Link to this comparison view

--- en:iot:examples:setup:debugging [2021/03/05 23:22] – [Debugging] heiko.pikner
+++ en:iot:examples:setup:debugging [2021/03/06 10:00] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ===== Debugging =====
-The recommended debugging software for the IoT modules is MQTTBox (which can be downloaded [[http://workswithweb.com/mqttbox.html|here]]). MQTTBox is an easy to use software that allows publishing and subscribing to various topics.
+The recommended MQTT Client software for the IoT modules is MQTT.fx. MQTT.fx is an easy-to-use software that allows publishing and subscribing to various topics. Alternatively, an MQTTBox can be used as a replacement.
   * [[en:iot:examples:debugging:mqttfx|MQTT.fx installation and user guide.]]
   * [[en:iot:examples:debugging:mqttbox|MQTTBox installation and user guide.]]
-  * [[en:iot:examples:debugging:realterm|RealTerm Serial/TCP Terminal.]]
-====Setting up the MQTTBox====
+USB Serial Port can be used for debugging IoT kits. For this, a serial terminal is needed. One of the most advanced serial terminals is a RealTerm, allowing view and log data in different formats and manually reset the IoT modules.
-The first step after opening the program is creating a new MQTT client.
+  * [[en:iot:examples:debugging:realterm|RealTerm Serial/TCP Terminal.]]
-{{:en:iot:examples:setup:mqttbox_create_mqtt_client.png?400|}}
-Here you have to configure the client to connect with your selected MQTT broker.
-The important fields are on the picture below, you can leave the rest on their default settings.
-  * **MQTT Client name** - Write a name for this settings file. A good idea is to name it after the broker you are connecting to.
-  * **MQTT Client Id** - This is the name you set for your individual device. There should be only one device with this name connected with your broker.
-  * **Protocol** - This is the protocol used for this connection. It should be mqtt/tcp when using the Raspberry broker and mqtts/tls when using the Distancelab one.
-  * **Host** - Here enter the IP (or URL) and the port of the broker. It should be formatted as "111.111.111.111:1234", first IP address and then colon and port address.
-  * **Username and password** - If your broker has username and password enabled then enter those.
-{{:en:iot:examples:setup:mqttbox_settings.png?600|}}
-===MQTT settings for Roboticlabs Raspberry broker===
-If you downloaded and flashed the Raspberry image file that we provided then follow the picture below to configure your MQTTBox broker settings.
-{{:en:iot:examples:setup:rasp_broker_info.png|}}
-====Using MQTTBox====
-If the program does not automatically connect to the broker press the blue "Not connected" sign. When the connection has been established the blue "Not connected" sign will turn into green "Connected". Now you can use the MQTTBox to subscribe to different topics and publish on your own topics.
-{{:en:iot:examples:setup:mqttbox_inwork.png?500|}}

en/iot/examples/setup/debugging.1614986574.txt.gz · Last modified: 2021/03/05 10:00 (external edit)