Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:iot-open:practical:hardware:sut:esp32:iot_5 [2024/04/28 20:25] – [Task to be implemented] 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.\\ | 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.\\ | 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 === | === Step 2 === | ||
| Line 54: | Line 55: | ||
| #include < | #include < | ||
| </ | </ | ||
| + | WiFi UDP is part of the Arduino for the ESP32 framework, so you do not need to add it explicitly to the '' | ||
| === Step 3 === | === Step 3 === | ||
| Line 62: | Line 64: | ||
| === Step 4 === | === Step 4 === | ||
| - | Declate | + | Declare |
| <code c> | <code c> | ||
| WiFiUDP udp; //UDP Communication class | WiFiUDP udp; //UDP Communication class | ||
| Line 123: | Line 125: | ||
| coap.loop(); | coap.loop(); | ||
| </ | </ | ||
| - | If you plan to make frequent requests, decrease the time above ('' | + | < |
| - | <todo @pczekalski>Skończyć</todo> | + | |
| + | ==== Result validation ==== | ||
| + | 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: | ||
| + | |||
| + | <note tip>Sample command line client (Linux/ | ||
| + | <code bash> | ||
| + | $ coap-client -e " | ||
| + | </code> | ||
| + | </ | ||
| + | |||
| + | <note tip> | ||
| + | <code bash> | ||
| + | $ coap-client -m get coap:// | ||
| + | </ | ||
| + | </ | ||
| + | |||
| + | |||
| + | ===== 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: | ||
| + | |||
| + | <WRAP noprint> | ||
| + | ===== Project information ===== | ||
| + | {{: | ||
| + | This Intellectual Output was implemented under the Erasmus+ KA2.\\ | ||
| + | Project IOT-OPEN.EU Reloaded – Education-based strengthening of the European universities, | ||
| + | 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, | ||
| + | The content is Copyrighted and distributed under CC BY-NC [[https:// | ||
| + | <figure label> | ||
| + | {{: | ||
| + | </ | ||
| + | |||
| + | </ | ||
