Most recent activity
-
I actually managed to compile 2v21.84 for NRF52840DK, however I don't really know how to benefit from window/interval in
NRF.setScan. Is there any way of consulting Espruino API reference (in a human readable manner) for a specific commit? As far as I understand, most of it is generated from comments in source code. -
I'm in the process of getting the first 1500 of https://www.espruino.com/Jolt.js ready
Is there any "TAKE MY MONEY" waiting list in which I can buy a seat?
-
I would love to see a firmware for this platform as well, however it seems that it is a bit different than the other ESP32. Native USB (instead of a USB to serial chip on the board) and RISC-V processor...
-
Yes - you should be able to use cutting edge builds for now though?
I should be able, however I am running the application on a NRF21540 dev board (including PA+LNA chip) and it seems that cutting edge builds do not cover NRF52 dev boards anymore.
-
but recently at least the scan window and interval became configurable if that helps a bit
Seems at least promising, I will have a try once available as a feature. As far as I understand it will be pushed in 2v22...
Well those three channels is how BLE Advertising works, there is a reason for advertising on multiple channels. You risk missing some packets when your selected channel becomes temporarily unusable due to noise.
Well that's for sure, it is generally not a good idea to limit advertising on a single channel only, however in our application we will use specific beacons in outdoor, countryside context, therefore 2.4GHz interference will probably be very limited.
Thank you for your response and also for the work you did at providing scan window and interval to Espruino (not mentioning coded phy, BTW)
-
For a beacon ranging application, we use function NRF.setScan() to scan for beacons (TX every 1 second), with some appropriate filtering.
We experienced some particular behaviour: Scanned packets are not equally spread over time. For some couple of seconds, every beacon advertising packet is beeing received, then nothing for the next few seconds, then again almost every packet received and so on. It seems like a stroboscopic effect, due to scanning window (https://academy.nordicsemi.com/wp-content/uploads/2023/03/blefund_less2_adv_process-1024x576.png).
We want to try scanning on only 1 channel, thus avoiding dead time switching between channels 37, 38 and 39, but it seems that setScan method doesn't allow for such parameter.
How complex would it be to modify setScan method to force receiving channel(s)? Would it make sense to add it as a feature to the official Espruino build? -
- 6 comments
- 166 views
-
Thank you both for your quick replies.
So it seems that anyhow, a specific compilation has to be done with edited bluetooth.c file.
I naively thought that this could be solved directly in javascript, but it seems to be more complex.
-
seems there is already something available, however I am not able to follow it up to the user space
https://github.com/espruino/Espruino/blob/55fbab3847975a40341dd2272d4693b341cc0ffe/targetlibs/nrf5x_12/components/softdevice/s130/headers/ble.h#L109
What I like:
-More Espruino
What I do:
80% Hardware
15% Firmware
5%Software
Linkedin: linkedin.com/in/jprey
Twitter: https://twitter.com/yerpj