Differences

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

--- en:iot-open:remotelab:sut:generalpurpose3 [2020/04/28 13:41] – pczekalski
+++ en:iot-open:remotelab:sut:generalpurpose3 [Unknown date] (current) – external edit (Unknown date) 127.0.0.1
@@ Line 14: / Line 14: @@
 ===== Sensors =====
 Each node contains the following set of sensors:
-  * DHT sensor measuring temperature and humidity (Blue is DHT11, White is DHT22) connected to the D4/GPIO2.
+  * DHT sensor measuring temperature and humidity DHT11, connected to the D4/GPIO2.
-  * Bosch BMP280 air pressure sensor, reporting absolute air pressure measurements in Pa, located inside of the yellow air chamber (operating of the fan changes pressure reported by the sensor when the fan is off, it measures absolute air pressure - please note, the laboratory is located at the 3rd floor + base floor, so it is not a ground-level pressure). This sensor uses I2C protocol and is connected to the D1 and D2 GPIOs (D2 is SDA, D1 is SCL). The sensor I2C address is 0x76.
+  * Bosch BMP280 air pressure sensor, reporting absolute air pressure measurements in Pa, located inside of the yellow air chamber (operating of the fan changes pressure reported by the sensor when the fan is off, it measures absolute air pressure - please note, the laboratory is located at the 3rd floor + base floor, so it is not a ground-level pressure). This sensor uses the I2C protocol and is connected to the D1 and D2 GPIOs (D2 is SDA, D1 is SCL). The sensor I2C address is 0x76.
 ==== Technical overview of the node and air pressure chamber overview ====
@@ Line 26: / Line 26: @@
 <figure VREL8_9_10_11>
 {{:en:iot-open:remotelab:sut:vrel8-11_bb.png?470|}}
-<caption>VREL components (circuit)</caption>
+<caption>VREL #8-#11 components (circuit)</caption>
 </figure>
@@ Line 88: / Line 88: @@
 <note important>Setting too high PWM frequency causes fan to operate binary (on/off) and limits controlling range.</note>
-=== Platformio.ini ===
-<code>
-</code>
 ===== Communication =====
@@ Line 111: / Line 105: @@
 ===== Limits =====
-At the same time, only one user can be programming the controller, although analysing the signal by others (unlimited number) the user has sense. Model is provided to work continuously, without service breaks.
+At the same time, only one user can be programming the controller, although analysing the signal by others (unlimited number) the user has sense. ode does not require physical human interaction and is supposed to work continuously, without service breaks.
 ===== Support =====
-piotr.czekalski@polsl.pl
+In case the LCD display hangs and you are sure that your code should work but it does not, it may be the case the I2C bus is stuck and hang the I2C to LCD controller converter.\\
+In this case, please use the following code to reset the I2C bus (you can embed it to your source code or run separately, then run your original code, again). Mind to use appropriate I2C address, regarding the node booked (nodes 8 and 9 are using 0x3F, nodes 10 and 11 use 0x27):
+<code c>
+#include <Arduino.h>
+#include <LiquidCrystal_I2C.h>
+LiquidCrystal_I2C lcd(0x3F,20,4);  // set the LCD address to 0x27 for nodes 10 and 11
+void setup()
+{
+  pinMode(4,OUTPUT);
+  pinMode(5, OUTPUT);
+  digitalWrite(4,LOW);
+  digitalWrite(5,LOW);
+  delay(2000);
+  pinMode(5, INPUT);       // reset pin
+  pinMode(4, INPUT);
+  delay(2050);
+  lcd.init(D2,D1);
+  lcd.backlight();
+  lcd.home();
+  lcd.print("Hello world...");
+}
+void loop()
+{
+}
+</code>
+Finally, you should see Hello World message on the LCD and I2C bus should be recovered now.

en/iot-open/remotelab/sut/generalpurpose3.1588081276.txt.gz · Last modified: 2020/07/20 09:00 (external edit)