Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
en:iot_homelab_kit:hardware:itt_iot [2017/12/08 10:46] Somepuben:iot_homelab_kit:hardware:itt_iot [2020/07/20 09:00] (current) – external edit 127.0.0.1
Line 19: Line 19:
 To use ITT IoT framework, you need to include the source code of the framework <code c>#include <ittiot.h></code> To use ITT IoT framework, you need to include the source code of the framework <code c>#include <ittiot.h></code>
  
-==== Setup mode ====+===== Setup mode =====
  
 This operating mode is required to initialize the device to allow the device to start in normal operation and This operating mode is required to initialize the device to allow the device to start in normal operation and
Line 29: Line 29:
 the device uses JSON format data structures and HTTP GET and POST to exchange data inquiries. the device uses JSON format data structures and HTTP GET and POST to exchange data inquiries.
  
-=== Setup mode HTTP interface ===+==== Setup mode HTTP interface ====
  
 The information in this section is not relevant when used for configuring The information in this section is not relevant when used for configuring
Line 36: Line 36:
 application for setting up the device. application for setting up the device.
  
-=== Device visibility check (ping) ===+==== Device visibility check (ping) ====
  
 http: // <ipaddr> / ping query allows you to check the device's visibility from the network. Every successful query http: // <ipaddr> / ping query allows you to check the device's visibility from the network. Every successful query
Line 43: Line 43:
 <code c>{"success": "true"}<code> <code c>{"success": "true"}<code>
  
-=== Device Hardware Information Query ===+==== Device Hardware Information Query ====
  
 http: // <ipaddr> / get / info query provides a quick overview of the device. http: // <ipaddr> / get / info query provides a quick overview of the device.
Line 51: Line 51:
 "cpu_freq": "80", "cpu_freq": "80",
 "f_free": "2797568", "f_free": "2797568",
-f_size: 4194304 +f_size: 4194304, 
-f_speed: "40000000"+f_speed: "40000000",
 "fw_build": "May 27 2017 17:25:08", " "fw_build": "May 27 2017 17:25:08", "
 "fw_size": "344528", "fw_size": "344528",
Line 60: Line 60:
 </code> </code>
  
-=== Download the settings from your device ===+==== Download the settings from your device ====
  
 http: // <ipaddr> / get / config query loads the device settings (if any). http: // <ipaddr> / get / config query loads the device settings (if any).
Line 77: Line 77:
 </code> </code>
  
-=== Search for WiFi networks ===+==== Search for WiFi networks ====
  
 The device searches for and returns for each network found a name, signal strength, security information (* The device searches for and returns for each network found a name, signal strength, security information (*
Line 96: Line 96:
 </code> </code>
  
-=== Changing settings to the device ===+==== Changing settings to the device ====
  
 http: // <ipaddr> / set / config POST request to the device in the JSON format setup. In the example http: // <ipaddr> / set / config POST request to the device in the JSON format setup. In the example
Line 110: Line 110:
 if the JSON validated and the device had enough free space to store data. if the JSON validated and the device had enough free space to store data.
  
 +==== Restart your device ====
  
-=== Restart your device === 
- 
-http: // <ipaddr> / restart p 
 restarts the device in normal mode. Rebooting is necessary for new ones restarts the device in normal mode. Rebooting is necessary for new ones
 to activate the settings. to activate the settings.
Line 122: Line 120:
 } }
 </code> </code>
 +
 +
 +===== Normal mode =====
 +
 +Normal mode is the mode in which a device executes a user program. A prerequisite for normal operation is the running of WiFi and
 +MQTT server connection. If the connection can not be made, the device will be started in setup mode.
 +In this case, you should check the device settings (usernames, passwords, ...) and make sure that
 +network connection and server are working.
 +
 +==== Data exchange with the server====
 +
 +The data exchange with the server takes place through the MQTT protocol. The MQTT protocol uses publish-
 +subscribe pattern (https://en.wikipedia.org/wiki/Publish-subscribe_pattern) where the messages to be transmitted
 +(data) is organized by theme. The IoT framework has been tested on Mosquitto (http://mosquitto.org/)
 +server, but you can use another server or service that follows the MQTT protocol (for example:
 +Amazon AWS IoT, Azure IoT).
 +
 +==== MQTT items ====
 +
 +The IoT Framework defines some of the default themes used to track and track the device
 +remote management. If necessary, the user can create a thread as needed. Subject name
 +The name of the device is used for compilation. The device name is a unique name assigned by the user, which is
 +prefix device themes. For example, if the device name is "dev1", then the device's themes would be
 +"Dev1 / log", "dev1 / cfg", ... To achieve a better logical organization, devices should be distributed.
 +sub themes, to add a device to a sub theme, the name of the device must be named as the device containing the name
 +sub-topic For example, if you want to add "dev1" to the "itt / devices" subteme, the device should be
 +to name it "itt / devices / dev1"
 +
 +
en/iot_homelab_kit/hardware/itt_iot.1512730011.txt.gz · Last modified: 2020/07/20 09:00 (external edit)
CC Attribution-Share Alike 4.0 International
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0