Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- heating_control_system_with_webinterface [2014/10/31 19:29] – [Webrequest] karl
+++ heating_control_system_with_webinterface [2017/04/04 06:42] (aktuell) – [First Implementation - WiFi-Relay-Board] karl
@@ Zeile 9: / Zeile 9: @@
 ===== Project Goal =====
-  * The overall goal is to keep the temperature in my office at a nice temperature when I'm there, and so save energy, when I'm not there.
+  * The overall goal is to keep the temperature in my office at a nice temperature when I'm there, and to save energy, when I'm not there.
   * Control the central heating system with the circulation pump for the radiators.
-  * Very simple local user interface with LCD and push-buttons.
+  * A local userinterface, which does not relay on a working internet connection.
-  * Webinterface, where I can set the temperature set point for now and for the future. \\ Perhaps a plot of the temperature curve would be nice.
+  * Webinterface, where I can set the temperature set point for now and for the future. \\ Perhaps a plot of the temperature curve would be nice. Encrypted data transfer and user identification is mandatory.
   * The regulator-algorithm should be local in the office. So it will work without any internet connection. But the system will have to relay on a working WiFi connection.
@@ Zeile 33: / Zeile 33: @@
 ===== Communication =====
-==== Webrequest ====
+==== HTTP ====
-When you request a website by entering a url in your web browser, the web server gets a message via TCP. I've tested this with the simple software tool [[Networking#SocketTest from Akshathkumar Shetty]]. \\
+For the communication simple HTTP messages will be used, to tranfer data between the different nodes in the network. Please have a look to [[networking#http_get_vs_post|HTTP GET vs. POST]], where I explained the two different message-types.
-I've opened a TCP server listening to port 8080. When I enter
-  http://localhost:8080/relay1=1&relay2=0
-, I get this message on the TCP server:
-  GET /relay1=1&relay2=0 HTTP/1.1
-  Host: localhost:8080
-  User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0
-  Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
-  Accept-Language: en-US,en;q=0.5
-  Accept-Encoding: gzip, deflate
-  Connection: keep-alive
-The server also knows, which IP address wants to connect to it.
-The most important thing is, that we can transfer data in a very simple way from the browser to the TCP server, by passing some arguments into the URL. In fact it doesn't even matter how the arguments are formatted, because on the Sensor Box we have to write the interpreting code on our own. But for compatibility with PHP we should use "/?relay1=1&relay2=0".
+===== First Implementation - WiFi-Relay-Board =====
+.12.2014
+{{ ::wifi-heating:soldered-board.jpg?direct&300|}}
+{{ :wifi-heating:wifi-relay-board.png?direct&300|}}
+The first version, which has the most important feature - remotly turning on the heating system - has been implemented the last days. \\
+I built the Wifi-Relay-Board. The firmware is very simple. It fetches every 30 seconds a text-file from my webserver, which tells the relay-board, when the heating system has to be enabled and disabled.
+Here is a link to the text-file: [[http://www.zeilhofer.co.at/lackergraben-heating/simple-config.txt|text file]]\\
+This file I can edit with the online text editor, written in PHP. Many thanks to Simon Thorpe, which has written this nice web-application. [[https://github.com/simon-thorpe/editor|Github]]\\
+Here you can download the software and documentation: [[http://www.zeilhofer.co.at/lackergraben-heating/2014-12-16-relay-board.tar.gz|tar.gz-file]]
+{{tag>english project wifi arduino remote_control kicad technical}}