Skip to content

Commit 3aac496

Browse files
Update content/arduino-cloud/01.guides/04.micropython/content.md
Co-authored-by: Karl Söderby <[email protected]>
1 parent f2c5888 commit 3aac496

File tree

1 file changed

+4
-1
lines changed
  • content/arduino-cloud/01.guides/04.micropython

1 file changed

+4
-1
lines changed

content/arduino-cloud/01.guides/04.micropython/content.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -138,7 +138,10 @@ For more options on how to install libraries on your board, check out our [Insta
138138
You can connect the GIGA R1 to the Arduino Cloud with MicroPython. There are two main methods to create this connection `async` and `sync`.
139139

140140
#### Async (Default)
141-
This is the method currently implemented by default with the Cloud. Asynchronous operations allow tasks to run independently of the main program flow. Functions can start and continue without waiting for other tasks to finish. This non-blocking behavior is achieved using techniques like callbacks, coroutines, or the async and await keywords in MicroPython. Asynchronous functions are particularly useful for handling network communication, as they enable the GIGA R1 to perform other operations (like reading sensors or updating outputs) while waiting for data from the Arduino Cloud.
141+
This is the method currently implemented by default with the Cloud. Asynchronous operations allow tasks to run independently of the main program flow. Functions can start and continue without waiting for other tasks to finish. This non-blocking behavior is achieved using techniques like callbacks, coroutines, or the async and await keywords in MicroPython.
142+
143+
Asynchronous functions are particularly useful for handling network communication, as they enable the boards to perform other operations (like reading sensors or updating outputs) while waiting for data from the Arduino Cloud.
144+
142145

143146
**Code example:**
144147
```python

0 commit comments

Comments
 (0)