279ad4a9b17d1131aaab46af1f094f8a9d3df646
Board-dat/NBL/NBL1107-dat/2024-05-15-17-38-57.png
... | ... | Binary files /dev/null and b/Board-dat/NBL/NBL1107-dat/2024-05-15-17-38-57.png differ |
Board-dat/NBL/NBL1107-dat/NBL1107-dat.md
... | ... | @@ -5,12 +5,18 @@ https://www.electrodragon.com/product/ble-5-0-mesh-sensor-node-mini-board-mesh-n |
5 | 5 | |
6 | 6 | legacy wiki page - https://w.electrodragon.com/w/Mesh-Node |
7 | 7 | |
8 | +## Board Map |
|
9 | + |
|
10 | +![](2024-05-15-17-38-57.png) |
|
11 | + |
|
12 | +- SJ1 setup button output to either Reset or P32 |
|
13 | + |
|
8 | 14 | |
9 | 15 | ## ref |
10 | 16 | |
11 | 17 | - [[AHT20-dat]] - [[KX023-1025-dat]] |
12 | 18 | |
13 | -- [[HC32F003-dat]] |
|
19 | +- [[HC32F003-dat]] - [[HDSC-dat]] |
|
14 | 20 | |
15 | 21 | - [[JDY-25M-dat]] - [[signal-relay-dat]] |
16 | 22 |
Chip-cn-dat/HDSC-dat/2024-05-15-16-48-43.png
... | ... | Binary files /dev/null and b/Chip-cn-dat/HDSC-dat/2024-05-15-16-48-43.png differ |
Chip-cn-dat/HDSC-dat/HC32F003-dat.md
... | ... | @@ -0,0 +1,8 @@ |
1 | + |
|
2 | +# HC32F003-dat |
|
3 | + |
|
4 | +## Applications |
|
5 | + |
|
6 | +For [[mesh-node-dat]] - [[NBL1107-dat]] |
|
7 | + |
|
8 | +![](2024-05-15-16-48-43.png) |
|
... | ... | \ No newline at end of file |
Chip-cn-dat/HDSC-dat/HDSC-dat.md
... | ... | @@ -0,0 +1,17 @@ |
1 | + |
|
2 | +# HDSC-dat |
|
3 | + |
|
4 | + |
|
5 | +## MCU |
|
6 | + |
|
7 | +- [[HC32F003-dat]] |
|
8 | + |
|
9 | + |
|
10 | + |
|
11 | +## ref |
|
12 | + |
|
13 | +- https://github.com/Edragon/MCU-HDSC-SDK-HC32L136 |
|
14 | +- https://github.com/Edragon/MCU-HDSC-HC32F00X |
|
15 | +- https://github.com/Edragon/MCU-HDSC-HC32L110 |
|
16 | +- https://github.com/Edragon/MCU-HDSC-SDK |
|
17 | +- https://github.com/Edragon/MCU-HDSC |
|
... | ... | \ No newline at end of file |
SDK-dat/HDSC-SDK-dat/2024-05-15-17-46-45.png
... | ... | Binary files /dev/null and b/SDK-dat/HDSC-SDK-dat/2024-05-15-17-46-45.png differ |
SDK-dat/HDSC-SDK-dat/HDSC-SDK-dat.md
... | ... | @@ -0,0 +1,6 @@ |
1 | + |
|
2 | +# HDSC-SDK-dat |
|
3 | + |
|
4 | +## HDSC ISP |
|
5 | + |
|
6 | +![](2024-05-15-17-46-45.png) |
|
... | ... | \ No newline at end of file |
Tech/Network-dat/Bluetooth-dat/mesh-node-dat/2024-05-15-16-52-35.png
... | ... | Binary files /dev/null and b/Tech/Network-dat/Bluetooth-dat/mesh-node-dat/2024-05-15-16-52-35.png differ |
Tech/Network-dat/Bluetooth-dat/mesh-node-dat/2024-05-15-16-53-46.png
... | ... | Binary files /dev/null and b/Tech/Network-dat/Bluetooth-dat/mesh-node-dat/2024-05-15-16-53-46.png differ |
Tech/Network-dat/Bluetooth-dat/mesh-node-dat/mesh-node-dat.md
... | ... | @@ -0,0 +1,11 @@ |
1 | + |
|
2 | +# mesh-node-dat |
|
3 | + |
|
4 | +![](2024-05-15-16-52-35.png) |
|
5 | + |
|
6 | +![](2024-05-15-16-53-46.png) |
|
7 | + |
|
8 | +- Relay nodes: These need to always be awake and therefore consume more power. Relay nodes function to receive and forward message packets across the network. In our lighting example, relay nodes will be mains powered, so it is unlikely they would have energy supply concerns. |
|
9 | +- Low-power nodes: These nodes are usually battery powered and are typically in a power-saving sleep mode for the majority of the time. |
|
10 | +- Friend nodes: Low-power nodes are always associated with a friend node, which stores and forwards messages according to an agreed schedule. An ambient light sensor used to control outside lights at dusk and dawn is an example of a low-power node. |
|
11 | +- Proxy nodes: These nodes enable non-BLE-compliant devices to connect into the mesh through the use of the Bluetooth Generic Attribute (GATT) profile interface. |
|
... | ... | \ No newline at end of file |