Connecting to nRF52480-Dk from Xbee3

RE: Connecting to nRF52480-Dk from Xbee3

ovrebekk — Mon, 11 Jan 2021 11:04:11 GMT

You welcome, the best of luck with your project 🙂

RE: Connecting to nRF52480-Dk from Xbee3

wz2b — Wed, 06 Jan 2021 22:44:17 GMT

Thank you very much for explaining ... I will do as you suggest and locate devices by the Service UUID.

RE: Connecting to nRF52480-Dk from Xbee3

ovrebekk — Wed, 06 Jan 2021 13:57:14 GMT

By default the SoftDevice will generate a static random address based on the DEVICEADDR registers in the FICR, which are random numbers programmed into each nRF device in production.

It is true that you should not use the BLE address to identify a device, unless it is a device you have already established a bonded relationship to. Most applications identify devices based on a service UUID, which is either a 16-bit number (for standard BLE services) or a 128-bit number (for proprietary services).

Best regards
Torbjørn

RE: Connecting to nRF52480-Dk from Xbee3

wz2b — Tue, 05 Jan 2021 15:03:29 GMT

Where is the default gap address set? I can't find any calls to sd_ble_gap_addr_set() in the project.

RE: Connecting to nRF52480-Dk from Xbee3

wz2b — Tue, 05 Jan 2021 14:55:00 GMT

OK. I figured this out. The problem was that I was making a connection using PUBLIC rather than RANDOM. This works:

conn=ble.gap_connect(ble.ADDR_TYPE_RANDOM, binascii.unhexlify("F64D1D24B0E6"), timeout_ms=5000)

I did not understand that PUBLIC and RANDOM are more or less two distinct addresses spaces. I don't know how the SDK chooses the 'random' address or if I need to be concerned about this. I don't want the device changing addresses. Is the idea that you aren't supposed to locate the device based on the address, but, rather, based on the services offered?

RE: Connecting to nRF52480-Dk from Xbee3

wz2b — Tue, 05 Jan 2021 13:01:02 GMT

No worries. Yeah, the connect code is trivial:

conn=ble.gap_connect(ble.ADDR_TYPE_PUBLIC, binascii.unhexlify("dc8ffb68a2dc"), timeout_ms=5000)
# returns: OSError: [Errno 7110] ETIMEDOUT

that binascii library call just turns the string into a "bytes" object. So using that, I can connect to many BLE devices around my house including my Anova precision cooker, my weather station, and others ... but not my nRF project. However, nRF tools can connect to my device just fine. So something about the Xbee is being fussy connecting to the nRF52480 project. I'm mainly looking for ideas on what my nRF project might be missing.

RE: Connecting to nRF52480-Dk from Xbee3

Henry_Chou — Tue, 05 Jan 2021 01:47:50 GMT

Xbee is the Zigbee end-device ,router or coordinator. Your code using NRF52840DK is the ble base of peripheral. How can a ble peripheral device connect to the Xbee(Zigbee)?

Sorry! After I search Xbee3 , I am wrong in my statement.The new one Xbee3 can support BLE by firmware. So.... I doubt that it's there any troubles in your Xbee3 code for central mode.