diff options
| author | lonkaars <loek@pipeframe.xyz> | 2023-01-17 22:20:32 +0100 |
|---|---|---|
| committer | lonkaars <loek@pipeframe.xyz> | 2023-01-17 22:20:32 +0100 |
| commit | 9696a9678f02d2808b4a17481d6668e776c86731 (patch) | |
| tree | 880fc5db61169023cb2ec8863ecdc44e4ea92e9f | |
| parent | d6b9985602e12dd612891604d79241aacc978401 (diff) | |
baby wipe
| -rw-r--r-- | docs/design.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/design.md b/docs/design.md index 91e0047..e1ef1cc 100644 --- a/docs/design.md +++ b/docs/design.md @@ -48,7 +48,7 @@ Thus the desicion has been made to use this option. Because the data will be received asynchronously, certain decisions will have to be made about how to deal with this. In this case the GUI or client sends out requests/tasks to the border router. The border node then responds after x time. In both cases this triggers a callback function on the receiving end, so that the data can be handled accordingly, see the image below. - + ## Communication standards @@ -155,4 +155,4 @@ There are two semaphores created in the provisioner software. The first one is c |Zephyr|3.1| |nRF SDK|2.1.2| <figcaption>Software and library functions</figcaption> -</figure>
\ No newline at end of file +</figure> |