aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUnavailableDev <ggwildplay@gmail.com>2023-01-17 20:58:41 +0100
committerUnavailableDev <ggwildplay@gmail.com>2023-01-17 20:58:41 +0100
commit0f0202d979ed24f8640cd239fdad23d6154a8f61 (patch)
treed1f75d6495f40a18b117e15798660007a7cb62d0
parent3c351794f00f283b2977aa5b25e00b0598382131 (diff)
UART vs Bluetooth
-rw-r--r--docs/design.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/design.md b/docs/design.md
index e63dff2..f63bad9 100644
--- a/docs/design.md
+++ b/docs/design.md
@@ -85,3 +85,27 @@ For now, there are two semaphores created in the provisioner software. The first
<figcaption>Software and library functions</figcaption>
</figure>
+
+
+
+
+
+# Data transfer between GUI and mesh network
+
+## Asynchronous data handling
+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.
+
+## Communication standards
+There are two options available, each has its own set of benefits listed in the table below.
+
+<figure>
+| UART | Bluetooth |
+| --------------------- | ---------- |
+| Less interference | Wireless |
+| Simpler | Complexer |
+| Available on all pc's | (opposite) |
+<figcaption>Benefits of UART vs Bluetooth</figcaption>
+</figure>
+Seeing that there are more pro's to using UART then Bluetooth, it makes the most sense to use UART.
+
+## Custom protocol \ No newline at end of file