From 0f0202d979ed24f8640cd239fdad23d6154a8f61 Mon Sep 17 00:00:00 2001 From: UnavailableDev Date: Tue, 17 Jan 2023 20:58:41 +0100 Subject: UART vs Bluetooth --- docs/design.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) 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
Software and library functions
+ + + + + +# 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. + +
+| UART | Bluetooth | +| --------------------- | ---------- | +| Less interference | Wireless | +| Simpler | Complexer | +| Available on all pc's | (opposite) | +
Benefits of UART vs Bluetooth
+
+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 -- cgit v1.2.3 From 95101cb750b8f749509f757cd1cd8ebbad7c67ad Mon Sep 17 00:00:00 2001 From: UnavailableDev Date: Tue, 17 Jan 2023 21:46:56 +0100 Subject: framework --- docs/design.md | 65 +++++++++++++++++++++++++++++++--------------------------- 1 file changed, 35 insertions(+), 30 deletions(-) diff --git a/docs/design.md b/docs/design.md index 17e09cc..eff342a 100644 --- a/docs/design.md +++ b/docs/design.md @@ -26,9 +26,43 @@ details are: # Framework +The following two are the possible frameworks for this project to use: +## segger: +For this there was very little to non research before starting this project. +## Zephyr: + +This can be used with either a makefile system and the correct libraries or with the highly integrated visualstudio code extension. Because of this integration making a custom makefile is too time intensive for this project and the visualstudio code extension works great already. + +Further more zephyr and nordic both keep supporting their software with frequent updates and there are plenty of examples made with this. + +Thus the desicion has been made to use this option. + + + +# 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, see the image below. + +![img](img/fig-AsyncCommunication.svg) + +## Communication standards + +There are two options available, each has its own set of benefits listed in the table below. + +
+| UART | Bluetooth | +| --------------------- | ---------- | +| Less interference | Wireless | +| Simpler | Complexer | +| Available on all pc's | (opposite) | +
Benefits of UART vs Bluetooth
+
+Seeing that there are more pro's to using UART then Bluetooth, it makes the most sense to use UART. # Custom serial protocol @@ -112,33 +146,4 @@ For now, there are two semaphores created in the provisioner software. The first |Zephyr|3.1| |nRF SDK|2.1.2|
Software and library functions
- - - - - - - -# 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, see the image below. - -![img](img/fig-AsyncCommunication.svg) - -## Communication standards - -There are two options available, each has its own set of benefits listed in the table below. - -
-| UART | Bluetooth | -| --------------------- | ---------- | -| Less interference | Wireless | -| Simpler | Complexer | -| Available on all pc's | (opposite) | -
Benefits of UART vs Bluetooth
-
-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 + \ No newline at end of file -- cgit v1.2.3