-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem in getting notifications #187
Comments
Hi, I'm not sure why you're not getting any notifications here. Could you enable logging and show the output? |
Hello,
After sending this data, I expect some data to be received on the characteristic 6E400003-B5A3-F393-E0A9-E50E24DCCA9E, which I do not. Is the notification being enabled properly? |
Hi, May I understand how is the requireAck affecting the notification? After the notifications were enabled, I expected the event In which scenarios is deviceNotifiedOrIndicated fired? I see that even the battery notifications dont land up on deviceNotifiedOrIndicated. Thanks |
Hi, The |
Ooooops! I had interpreted the I still fail to understand how does setting the Another problem I see is w.r.t the RSSI value of element while it is connected. I get the device.rssi as null. How can I get the range of a device while it is connected? Thanks |
The documentation could be more explicit about describing the difference between the two types of events, I agree. By setting the Ack parameter to true, it means that you require the peer to respond with a WriteResponse when writing to the CCCD descriptor. However, by looking at the log it does seem to get a resonse, so all should be ok. I do not understand why it works for you when using Ack=false, and not with Ack=true, from the log it looks fine. Regarding RSSI in a connection, that has not been added API for in adapter.js. However, there exists a function that can be called with adapter._adapter.GapStartRSSI. Disclaimer: Since we haven't made an API for it, it hasn't been tested. See SoftDevice API doc for more info about the arguments. |
Yeah! The ack thing is a puzzle. But that was the only diff between my logs and those of NRF Connect. About the RSSI, I'll check the API you mentioned. |
Hello, There is now way for the event listener to distinguish between these two conditions, or is there? |
Hi, |
Hi, Currently pc-ble-driver-js will only work with SD API v2 and v3, though support for SD API v6 is in progress. |
Hi, About the I need to use the softdevice v5 with the JS library. Can you refer me to any documentation that I can refer to get this done faster? On current softdevice (v3), I see that if I send writeWithoutResponse, it takes nearly 80ms to get the ack back. This seems to much. What can I do to speed it up? Once in a while, it also happens that the scan does not discover any of the advertising devices. No error is generated either. Thanks |
Correct, will add a note in the docs.
There is no documentation avilable on how to update the pc-ble-driver-js language bindings (addon), apart from the source code itself.
There is not much that can be done to speed things up, as the major delay on the devkits is the relaying of traffic through the jlink OB chip, which adds delays for every packet fragment. It should go faster on the new nRF52840 dongle as it does not depend on external usb2uart conversion. |
Thanks for the update on the pc-ble-driver. About the speed problem, I am encountering it on the NRF52840 dongle itself. I have played around with the conn_bw parameters during enableBLE and the conn_interval parameters during connect. None of them seem to be helping. Are there any other knobs which I can try besides these? |
If you want to maximize data throughput you could increase attmtu packert length to get across more data per packet. |
Thanks.
…On Thu 23 Aug, 2018, 9:26 PM Bjørn Inge Hanssen, ***@***.***> wrote:
If you want to maximize data throughput you could increase attmtu packert
length to get across more data per packet.
If you just want to send packets faster I think there is not much to do as
the bottleneck is the transport layer that requires all transport packets
to be acked, adding delays.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#187 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASn2qsxSrmEdcIWRe8qPYCB9DaDqVjqFks5uTtCsgaJpZM4V_U52>
.
|
Hello, |
Hi, |
@bihanssen regards, |
Hi, My recommendation would be to wait until we have finalized the next release of pc-ble-driver. It will contain all the required files to support the various SD APIs on the different HW kits, along with many improvements to builds scripts etc. You can follow the activity in branch feature/consolidate-sd-apis. |
We have March 2020 and last commit on branch |
@SzymonLisowiec, SDK API v6 development in ble-driver-js has been discontinued in favour of SD API v5 only. v5 has been merged to master(#235) and will be published in an upcoming release. |
@bihanssen I have bought nRF42840 Dongle for make a gateway for zigbee devices. Only softdevice s140 and s340 have support for ZigBee and in latest release of https://github.com/NordicSemiconductor/pc-ble-driver/releases/tag/v4.1.1 are |
@SzymonLisowiec s140 is only supported for v6, which you will find support for in pc-ble-driver. Since there is no support for v6 in ble-driver-js, the only option currently is to use pc-ble-driver (not -js). |
Hello,
I have a device to which I can connect correctly using NRF52 DK board.
I do get the services and characteristics also correctly.
I turn on notifications on all the characteristics that support notifications - all of which return success.
I use following code for doing this.
But I am not getting any notifications on them.
Following is the code that I expect should get hit which actually never gets hit.
I can see the characteristic value change if I use the NRF connect app - which means my device "is" correctly sending the notifications.
Am I missing on anything?
Thanks
Amruta
The text was updated successfully, but these errors were encountered: