channel number of received advertisements

RE: channel number of received advertisements

MartinBL — Wed, 26 Sep 2018 07:22:58 GMT

This is now possible with S132 and S140 v6+: Here is an excerpt from the Migration document (s132_nrf52_6.0.0_migration-document.pdf):

RE: channel number of received advertisements

ock — Mon, 13 Nov 2017 15:14:47 GMT

To be honest, I've never done something like this before (complete new open source flash). But I will also look at that. Big thanks to you too :)

RE: channel number of received advertisements

endnode — Mon, 13 Nov 2017 15:09:33 GMT

Like seriously this looks to you as optimal solution? Unless you want to use these other features such as BT SIG mesh why not using proper BLE stack like Zephyr with just little mod of reporting adv. channel (if it's not there already which is also possible)?

RE: channel number of received advertisements

ock — Mon, 13 Nov 2017 15:06:32 GMT

Thanks for your quick response. So it will be more work than planned. But at least I know it's possible. Thanks again!

RE: channel number of received advertisements

David Edwin — Mon, 13 Nov 2017 14:59:26 GMT

You will need to write the code in the Mesh SDK to do that at the bearer level, i.e. send the SCAN_REQ and get the SCAN_RSP to make it an active scanner. It is however possible if you have the understanding of the hardware RADIO peripheral and an understanding of the TimeSlot API.

You would extend the existing scanner and also use the existing broadcaster as a reference for the RADIO and Timeslot code.

Edit: You can remove most of the Mesh code base as the bearer part is fairly small. The softdevice and SDK examples can be used side by side to the active scanner.

RE: channel number of received advertisements

ock — Mon, 13 Nov 2017 14:51:21 GMT

@David Edwin: Would it be possible to configure that as an active scanner?

RE: channel number of received advertisements

David Edwin — Mon, 13 Nov 2017 14:49:46 GMT

The Nordicsemi Mesh SDK which implements a passive scanner using the Timeslot API will deliver the RSSI and channel number for the advertisements that are received. The Mesh SDK is available as source code.

RE: channel number of received advertisements

endnode — Mon, 13 Nov 2017 13:12:49 GMT

RK is right, unless Nordic add it into their event structure in some future SD release it's very unreliable reading it from registers directly. But you have other options as usually: don't use Nordic stack and write your won or go with some licensed/open source stack which either has it already or allows you to customize it easily.

RE: channel number of received advertisements

RK — Mon, 13 Nov 2017 12:27:30 GMT

you can't guarantee that. You could end up processing the event ages after it occurred.

RE: channel number of received advertisements

ock — Mon, 13 Nov 2017 12:26:07 GMT

Even if BLE_GAP_EVT_REPORT is the official way of "reading " the advertisements you can read them immediatly (at least it is possible for the Chip im currently using (Different Manufacturer)). What I ned to know is the frequency a SCAN_REQ has been sent on. So i would have enough time ~300us to read the Register value

RE: channel number of received advertisements

RK — Mon, 13 Nov 2017 12:19:43 GMT

no it is not. You have no idea when you receive the report whether the stack has moved on to an entire different channel. If the channel isn't supplied in the event, you can't know what it was.

Why do you need to know?

RE: channel number of received advertisements

ock — Mon, 13 Nov 2017 12:12:11 GMT

Is it Not possible to read the Register for the Synthesizer frequency?

RE: channel number of received advertisements

endnode — Mon, 13 Nov 2017 12:06:34 GMT

HW says nothing, what stack you use? I assume that Nordic S140 Soft Device and then on reception of BLE_GAP_EVT_ADV_REPORT you cannot get this information unfortunately. But that applies only to current API according to Infocenter, might be subject of change.