Differences

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

Link to this comparison view

--- en:iot-open:practical:hardware:sut:esp32:iot_5 [2024/04/28 20:27] – [Start] pczekalski
+++ en:iot-open:practical:hardware:sut:esp32:iot_5 [2024/05/01 13:28] (current) – [Start] pczekalski
@@ Line 47: / Line 47: @@
 Implement the code to display on the selected device.\\
 Connect to the WiFi in the STA mode (as a client) and ensure the connection is OK and you got an IP from the DHCP server.\\
+It is essential to note and present (using a display of your choice) the node's IP address, as you will later need to refer to it with a client to use your service.
 === Step 2 ===
@@ Line 54: / Line 55: @@
 #include <coap-simple.h>
 </code>
+WiFi UDP is part of the Arduino for the ESP32 framework, so you do not need to add it explicitly to the ''platformio.ini'' file.
 === Step 3 ===
@@ Line 62: / Line 64: @@
 === Step 4 ===
-Declate communication objects:
+Declare communication objects:
 <code c>
 WiFiUDP udp;      //UDP Communication class
@@ Line 128: / Line 130: @@
 You should be able to connect to the WiFi and set up a CoAP service. Depending on whether you're fully remote or able to access our networks with an additional device, you need to implement a CoAP client on another laboratory node (as present in the scenario [[[en:iot-open:practical:hardware:sut:esp32:iot_6|]]) or use some other client (such as NodeRED or even command line client): note, your client must be present in the same WiFi network as your CoAP service (laboratory node).
+<note tip>Sample command line client (Linux/MacOS) syntax to make a PUT request to the service (192.168.91.14) is presented below (bash):
+<code bash>
+$ coap-client -e "0" -m put coap://192.168.91.14/light
+</code>
+</note>
+<note tip>Sample command line client (Linux/MacOS) syntax to make a GET request to the service (192.168.91.14) is presented below (bash):
+<code bash>
+$ coap-client -m get coap://192.168.91.14/light
+</code>
+</note>
+===== FAQ =====
+**How do I implement a client to my CoAP service?**: If you're fully remote, the only option is to implement a client on your own - use another laboratory node and scenario [[[en:iot-open:practical:hardware:sut:esp32:iot_6|]] pointing to your service. For this reason, we suggest printing the IP address on the display, as you need to explicitly implement the client to connect to this IP (given by the DHCP server). If you're on a laptop or mobile within the WiFi network range to which the laboratory nodes are connected, you can connect to it with your laptop and use any CoAP client.
+<WRAP noprint>
+===== Project information =====
+{{:en:iot-open:logo_iot_200_px.png?200|}}\\
+This Intellectual Output was implemented under the Erasmus+ KA2.\\
+Project IOT-OPEN.EU Reloaded – Education-based strengthening of the European universities, companies and labour force in the global IoT market.\\
+Project number: 2022-1-PL01-KA220-HED-000085090.
+**__Erasmus+ Disclaimer__**\\
+This project has been funded with support from the European Commission. \\
+This publication reflects the views of only the author, and the Commission cannot be held responsible for any use that may be made of the information contained therein.
+**__Copyright Notice__**\\
+This content was created by the IOT-OPEN.EU Reloaded consortium, 2022,2024.\\
+The content is Copyrighted and distributed under CC BY-NC [[https://en.wikipedia.org/wiki/Creative_Commons_license|Creative Commons Licence]], free for Non-Commercial use.
+<figure label>
+{{:en:iot-open:ccbync.png?100|}}
+</figure>
+</WRAP>
-<todo @pczekalski>Skończyć</todo>

en/iot-open/practical/hardware/sut/esp32/iot_5.1714336063.txt.gz · Last modified: 2024/04/28 20:27 by pczekalski