How to Implement Long range in BLE central peripheral example(relay)?

[Alan Ajit]

Dear Nordic,

what are the changes to achieve long range in Relay example ?

I need some help to achieve this 

[Bjørn Kvaale]

Jared already gave you a lot of hints on how to achieve this in this case. Did you try what he mentioned?

"Did you check the example code on the blogpost i linked in the previous reply? I suggest that you compare your code with the example code from the guide so that you can see what's missing. In the mtu_throughput example you should change the tx_phys , rx_phys, scan_phys to BLE_GAP_PHY_CODED to achieve long range in advertising and scanning. But again, all of this is done in the example code."

[Alan Ajit]

I face some problem achieving BLE long range in my custom board . i tested relay example its phy automatically update to 1 mbps that's why iam asking is it any wrong in my procedure. one of your developer will ask me to open a new ticket for this and he will assure some help to achieve this

https://devzone.nordicsemi.com/f/nordic-q-a/39460/related-to-ble-lon-range

that's why i am started new ticket here. 

I tried research from my own side and found  app ble  uart long range example(from github) i tested the example with nrf52840 dongle but phone doesn't recognize the advertising(hope coded phy not support in phone) so i make one dongle as receiver.  receiver find the advertising. 

The same code i tested with my custom board and debug it (no hang) works fine but receiver doesn't find my custom board advertising

why this happen? i need some help

[Bjørn Kvaale]

Are you referring to this github example? If you look under requirements, you can see that the dongle is not supported out of the box. You will need to make some changes in the board header file to make it work on the dongle. Also, how are you planning on debugging the dongle if you run into problems? You need to hook up some kind of J-Link device to the dongle like shown in the images below. The debug in pin was desoldered from the 52 dev kit & soldered onto the back of the dongle (i.e. P1). The best idea IMHO is to buy a 52840 dev kit (or two). The 52840 dongle is not meant to be used as a development kit.

There are currently no smartphones that support long range support as far as I am aware. The DevZone case you linked to explains this well.

Are you using a 52840 dongle on one side & your 52840 custom board as the receiver?

Do you have any debugging logs that you can share? Have you tried taking a sniffer trace?

[Alan Ajit]

 Dongle works perfect in coded phy but my custom board not works with same application(chip used in custom board is nrf52840) 

debug the custom board (debuging application  program works fine(ie no hang in program) but dongle doesn't receive advertising from my custom board 

Test procedure:-

First procedure:-

2 dongle 1 as advertising other as receiver and works this setup fine one dongle advertising and other one receive this advertising

second procedure:- 

1 dongle as receiver and my custom board as advertiser but dongle doesn't receive advertising from my custom board(debug the application in custom board(its works fine and hope its advertising)

Third procedure :-

change phy in custom board to 1mb phy and smart phone as receiver its works fine smart phone get the advertising.

Note:- second and third procedure just change phy of application(ie my custom board works fine in 1mb phy when i changed to coded phy receiver doesn't get the advertising i don't know why reciver doesn't get advertising i

I need some help because i want to implement long range in my custom board

[Bjørn Kvaale]

Do you have any logging information? That would be very helpful. In addition, a sniffer trace could help too.

[Alan Ajit]

No i have no Log information i testing using  dongle (scanner)LED blinking if its capture advertising. i totally confused why custom board act like this.