This shows you the differences between two versions of the page.
dsc:use [2018-06-22 17:49] jk created |
dsc:use [2018-06-22 17:58] jk |
||
---|---|---|---|
Line 2: | Line 2: | ||
To fit the requirements of all platforms it is necessary to split the firmware/software in two parts: | To fit the requirements of all platforms it is necessary to split the firmware/software in two parts: | ||
- | * The IoT-device-part to aquire data from the sensors and deliver them to MQTT broker or DB servers in the web | + | * The IoT-device-part to aquire data from the sensors and deliver them to MQTT broker or DB servers in the web |
- | * The web-server-part to provide configuration web pages (HTML). The user can configure IoT-device-part with a browser (FireFox, Chrome, Edge, ...) by clicking web GUI | + | * The web-server-part to provide configuration web pages (HTML). The user can configure IoT-device-part with a browser (FireFox, Chrome, Edge, ...) by clicking web GUI |
+ | |||
+ | |||
+ | ---- | ||
- | --- | ||
======= Running the IoT-Device ======= | ======= Running the IoT-Device ======= | ||
Line 12: | Line 14: | ||
===== IoT-Device with web access (e.g. MQTT) ===== | ===== IoT-Device with web access (e.g. MQTT) ===== | ||
- | If the IoT-device is already configured no Web-server-part is necessary. The IoT-device-part can aquire data from the connected sensors and deliver them to MQTT broker or DB servers in the web via WiFi. | + | If the IoT-device is already configured no Web-server-part is necessary to run the device. The IoT-device-part can aquire data from the connected sensors and deliver them to MQTT broker or DB servers in the web via WiFi. |
{{ :arc:modules_con5.svg?300 }} | {{ :arc:modules_con5.svg?300 }} | ||
Line 23: | Line 25: | ||
{{ :arc:modules_con6.svg?200 }} | {{ :arc:modules_con6.svg?200 }} | ||
- | *** | + | |
+ | ---- | ||
======= Configuration the IoT-Device - Communication between Parts ======= | ======= Configuration the IoT-Device - Communication between Parts ======= |