This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot:examples:setup:debugging [2019/02/06 09:47] – rim.puks | en:iot:examples:setup:debugging [2021/03/06 10:00] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Debugging ===== | ===== Debugging ===== | ||
| - | The recommended | + | The recommended |
| - | ====Setting up the MQTTBox==== | + | * [[en: |
| - | + | * [[en: | |
| - | The first step after opening the program is creating a new MQTT client. | + | |
| - | + | ||
| - | {{:en: | + | |
| - | + | ||
| - | Here you have to configure the client to connect with your selected | + | |
| - | 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 | + | |
| - | * **Host** - Here enter the IP (or URL) and the port of the broker. It should be formatted as " | + | |
| - | * **Username and password** - If your broker has username and password enabled then enter those. | + | |
| - | + | ||
| - | {{:en: | + | |
| + | 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. | ||
| + | * [[en: | ||