@stoprocent/noble 1.11.2 → 1.11.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +3 -0
- package/README.md +3 -21
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -68,27 +68,9 @@ const noble = require('@abandonware/noble/with-custom-binding')({extended: true}
|
|
|
68
68
|
|
|
69
69
|
### Prerequisites
|
|
70
70
|
|
|
71
|
-
#### UART
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
Idea is to use Zephyr HCI over UART firmware and create noble driver to interface with HCI over UART.
|
|
75
|
-
|
|
76
|
-
##### Known Issues
|
|
77
|
-
What I have found so far that when using extended MTU and sending large amount of data Zephyr stops responding in rare cases. I have played with Zephyr configuration parameters in order to increase buffer sizes but with some luck. Sometimes when transfering fast, large payloads, with high MTU you can still hit the limit and Zephyr needs to be rebooted.
|
|
78
|
-
|
|
79
|
-
##### How to use this?
|
|
80
|
-
|
|
81
|
-
1. You will need NRF5x module (e.g. nRF52840 PDK)
|
|
82
|
-
2. If you have `nRF52840 PDK` you can in fact just use compiled HEX [misc/nrf52840dk.hex](misc/nrf52840dk.hex) (Buad Rate set to `1000000`)
|
|
83
|
-
3. If you want to compile it yourself:
|
|
84
|
-
1. You will need to install Zephyr ([https://docs.zephyrproject.org/latest/getting_started/index.html](https://docs.zephyrproject.org/latest/getting_started/index.html))
|
|
85
|
-
2. Compile HCI UART Example - `west build -p auto -b <your-board-name> zephyr/samples/bluetooth/hci_uart`
|
|
86
|
-
- e.g. When using `nRF52840 PDK` call `west build -p auto -b nrf52840dk_nrf52840 zephyr/samples/bluetooth/hci_uart`
|
|
87
|
-
4. Flash the firmware to Nordic Board e.g. using `nrfjprog`
|
|
88
|
-
- e.g. `nrfjprog -f NRF52 --program misc/nrf52840dk.hex –-chiperase --reset`
|
|
89
|
-
5. When you get a nordic board connected to the PC/Mac etc. with UART interface you are good to go.
|
|
90
|
-
6. In order to run any example from the examples folder or your own code you have to provide UART port by defining env variable: `NOBLE_HCI_UART_PORT`. Optionally if you use different Baud Rate you can change it by specifing `NOBLE_HCI_UART_BAUD_RATE`. Default value is `1000000`
|
|
91
|
-
7. e.g. `NOBLE_HCI_UART_PORT=/dev/tty.usbmodem0006837533091 node examples/peripheral-explorer.js b8:27:eb:83:9b:19`
|
|
71
|
+
#### UART (Any OS)
|
|
72
|
+
|
|
73
|
+
Please refer to [https://github.com/stoprocent/node-bluetooth-hci-socket#uartserial-any-os](https://github.com/stoprocent/node-bluetooth-hci-socket#uartserial-any-os)
|
|
92
74
|
|
|
93
75
|
#### OS X
|
|
94
76
|
|
package/package.json
CHANGED
|
@@ -7,7 +7,7 @@
|
|
|
7
7
|
"license": "MIT",
|
|
8
8
|
"name": "@stoprocent/noble",
|
|
9
9
|
"description": "A Node.js BLE (Bluetooth Low Energy) central library.",
|
|
10
|
-
"version": "1.11.
|
|
10
|
+
"version": "1.11.4",
|
|
11
11
|
"repository": {
|
|
12
12
|
"type": "git",
|
|
13
13
|
"url": "https://github.com/stoprocent/noble.git"
|
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
"node-gyp-build": "^4.5.0"
|
|
42
42
|
},
|
|
43
43
|
"optionalDependencies": {
|
|
44
|
-
"@stoprocent/bluetooth-hci-socket": "^0.6.
|
|
44
|
+
"@stoprocent/bluetooth-hci-socket": "^0.6.2"
|
|
45
45
|
},
|
|
46
46
|
"devDependencies": {
|
|
47
47
|
"async": "^3.2.4",
|