Differences

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

--- en:iot:examples:setup [2021/03/04 21:05] – [Driver for CH340] heiko.pikner
+++ en:iot:examples:setup [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Setup ======
-Here you can find information about how to set up your IoT Homelab kits. Once the setup is complete you can use MQTTbox (or any other MQTT software) to check if everything is working correctly.
+Here you can find information about how to set up your IoT Homelab kits. Once the setup is complete, you can use MQTTbox (or any other MQTT software) to check if everything works correctly.
 ====IDE for programming====
-An environment for writing the code, a compiler for the corresponding language and software for uploading written programs to the controller are needed in order to program the IoT modules. A PC with Atom text editor or Visual Studio Code and PlatformIO plugin is required.
+In order to program the IoT modules, a PC with IDE. There are two options where Visual Studio Code text editor with PlatformIO plugin is recommended.
+  * [[en:iot:examples:setup:quickstart|Visual Studio Code text editor and PlatformIO plugin installation manual.]]
   * [[en:iot:examples:setup:usb|Atom text editor and PlatformIO plugin installation manual.]]
 ====Driver for CH340====
-When an IoT MCU Module is connected, to the Windows computer then the Device Manager should show that USB-SERIAL CH340 is present.
+When an IoT MCU Module is connected to the Windows computer, the Device Manager should show that USB-SERIAL CH340 is present.
 {{:en:iot:examples:ch340.png|CH340}}
@@ Line 15: / Line 16: @@
   * [[https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all|Sparkfun]]
   * [[http://www.wch-ic.com/downloads/CH341SER_ZIP.html|CH340/CH341 USB to serial port Windows driver]]
 ====MQTT broker====
 At Tallinn University of Technology, the address of a public broker is available to everyone. However, if you need a separate  broker to set up, a guide to do it is below:
   * Set up your own MQTT broker ( [[en:iot:examples:setup:broker|A Raspberry Pi is a good candidate for this job.]]).
-====The configuration of IoT MCU modules ====
+====Using IoT MCU modules without a configuration====
-The IoT modules have a default configuration for connecting to the classroom WIFI. The settings can be overwritten for home or other use as follows:
+The IoT modules have a default configuration for connecting to the classroom WIFI. The settings can be overwritten for home or other use cases as follows:
 <code c>
   iot.setConfig("wname", "Your WiFi name");
@@ Line 27: / Line 29: @@
 More information [[en:iot:examples:setup:ittiot|]].
-If an IoT module configuration needs to be changed, the device should put on a setup mode. In setup mode, the IoT module starts a WiFi base station with the name IoT- <ESP_ID>, where ESP_ID is the device chip ID.
+====Configuration of IoT MCU modules ====
+If an IoT module configuration needs to be changed, the device should be put on setup mode. In setup mode, the IoT module starts a WiFi base station with the name IoT- <ESP_ID>, where ESP_ID is the device chip ID.
 The option to switch to a setup mode can be integrated into the software, or the following example code can be used:
   * [[en:iot:examples:setup:confmode|Configuration mode example]]
+{{:en:iot:examples:buttonshield.png?200|}}
-Then if the button shield is connected and the switch is pushed, then the IoT module should enter configuration mode and Advanced REST Client (ARC) should be used:
+Then if the button shield is connected and the switch is pushed, the IoT module should enter configuration mode, and Advanced REST Client (ARC) should be used:
   * [[en:iot:examples:setup:arcconf|Configure the IoT modules to connect to the local router and selected MQTT broker.]]

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