Configuring Observer example to only accept Coded Phy messages

RE: Configuring Observer example to only accept Coded Phy messages

Edvin — Mon, 29 Apr 2024 11:32:24 GMT

Can you please show me what your advertising is set up (the init and start function) after your modification?

I would like to be able to say that "you need to do this and that", but I don't know exactly what to do, and whether it is possible using our SoftDevice controller. And I don't have a peripheral that behaves like the one you have. I believe it is out of specification, which is why it may not be supported out of the box.

BR,
Edvin

RE: Configuring Observer example to only accept Coded Phy messages

AndrewC — Thu, 25 Apr 2024 14:33:43 GMT

Just retried and it doesn't detect the beacon. Are you sure the example is only using the basic advertising and not using auxiliary channels?

RE: Configuring Observer example to only accept Coded Phy messages

AndrewC — Thu, 25 Apr 2024 13:01:05 GMT

IIRC I just commented out the filter. I'll try the code again in a couple of minutes

RE: Configuring Observer example to only accept Coded Phy messages

Edvin — Thu, 25 Apr 2024 12:59:03 GMT

How did you set up the scan filter when you tried? If you didn't change anything, it will not find your device (unless it happens to be advertising the heart rate service UUID.

BR,
Edvin

RE: Configuring Observer example to only accept Coded Phy messages

AndrewC — Thu, 25 Apr 2024 12:19:13 GMT

I did try before posting and it didn't see anything, but will revist it and give it another go to be sure.

Regards

Andrew

RE: Configuring Observer example to only accept Coded Phy messages

Edvin — Thu, 25 Apr 2024 12:16:58 GMT

Have you tried it against the central_hr_coded sample? I believe this is exactly what it does. It does however set up a UUID filter, and trigger the filter_match callback whenever it finds a match, but if you change the filter, you should be able to find your device.

Best regards,

Edvin

RE: Configuring Observer example to only accept Coded Phy messages

AndrewC — Tue, 23 Apr 2024 16:17:26 GMT

Thank you, this solved part of my problem as I was able to get my gateway to accept a coded phy message from an advertiser dev board (nRF52840-DK). However it looks like my real problem is with the beacon hardware I am using. This is an InPlay IN100 beacon which does not properly support the coded phy mechanism. Their support message is as follows,

"the IN100 uses a non-standard LE Coded PHY. Our LE Coded PHY works by changing the data rate on the same primary advertising channels as 1 M and using the same format as 1 M. We do not use any auxiliary channels or change our format at all. This means if your scanner is looking on auxiliary channels or looking for a different format, it will not pickup our nonstandard LE Coded PHY"

"We have had customers modify Nordic gateways to detect our LE Coded PHY, but we are not privy to the exact details as to how this was done, and it would vary from device to device. If your team has the software expertise to do so, you may be able to ‘hack’ your Nordic gateway to work with us"

I don't have the knowledge or expertise to know the right way to do this, so if you have any advice on the simplest way to do this I would be very grateful.

RE: Configuring Observer example to only accept Coded Phy messages

Edvin — Wed, 10 Apr 2024 14:14:09 GMT

Hello,

I don't know if you are intentionally using "vanilla" Zephyr, but in our nRF Connect SDK (NCS) we have a sample pair called "peripheral_hr_coded" and "central_hr_coded" which run the peripheral and central side of the heart rate profile in BLE, only using CODED_PHY. Perhaps this is something you can check out?

To get started with NCS, I recommend you check out nRF Connect for Desktop -> Toolchain Manager, in addition to the NCS documentation:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/index.html

Best regards,

Edvin