• State Verified Answer
  • Replies 23 replies
  • Subscribers 64 subscribers
  • Views 6460 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 221380
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth not connecting

bscdb

Hi,

1. I tried flashing all ble codes to my nrf kit. It does not seem to connect on Windows machine but connects on Mac. My other nrf kit connects perfectly fine. What is the fix?

2. When my other nrf device is visible on Mac, it displays duplicate names, so its confusing which one to connect to?

Parents
  • 0
    bscdb said:
    does not seem to connect on Windows machine

    What "Windows machine" ?

    bscdb said:
    but connects on Mac

    So have you tried using the debugger in the two cases to see what's different / where it goes wrong ?

    bscdb said:
    When my other nrf device is visible on Mac, it displays duplicate names

    That is expected behaviour!

    The Mac only displays the name which the peripheral provides - so the only way around this is to give your peripherals distinct names.

    On Android, you can see the MAC address - but iOS does not allow this.

    Disappointed

  • 0 in reply to awneil

    1) Are you using Windows 8 or Windows 10? Which nRF5 example have you tested with?

    2) Are you connecting directly from the Mac or Windows Bluetooth settings to the nRF52 DK? When you change the device name of the nRF52, it may be that you need to clear bluetooth cache (just try turning Bluetooth off for about 10 seconds & then turning Bluetooth on again) on your Mac to see the updated device name.

    In general, we do not advise connecting from a computer (Windows or Mac) directly to an nRF52 DK device because the Bluetooth chip on your computer may have issues connecting to the nRF5 device.

    Update: Slightly misleading comment above. Thanks for picking it up ! You can connect some examples directly to a Windows computer (such as HID mouse), however most examples have not been tested directly with the computer's Bluetooth chip. If they have been tested with nRF Connect for Desktop, an nRF5 device was used as a connectivity chip in most examples.

    If possible, we recommend connecting your computer to an nRF52840 dongle for example (or an nRF5 DK) to use as a connectivity device between the computer <-> BLE <-> nRF52 DK. You can then easily test using nRF Connect for Desktop BLE app for example.

    Another thing you can test is to connect to the nRF52 DK via your mobile phone nRF Connect for Mobile app just to see that the connection to the DK is succesfull. If this is the case, the issue most likely lies on the Windows/Mac side.

  • 0 in reply to Bjørn Kvaale

    Hi Bjorn, I am using Windows 10. The advertising led on first nrf board glows at irregular intervals. I also tried connecting P21 to Vdd but that did not help. I tried all ble examples. The peripheral examples seem to work. But it connects to nrfConnect surprisingly. Also there is no problem in my Windows machine because the ble examples work on the other nrf board!

  • 0 in reply to bscdb

    again, have you tried using the debugger in the two cases to see what's different / where it goes wrong ?

  • 0 in reply to bscdb

    As suggests, I would try to debug the example. Also, maybe try changing the usb cable or usb port? Maybe you are not getting enough power to the nRF52 DK?

  • 0 in reply to bscdb

    First thing first, are both boards the same hardware. i.e same board revision ? Did you flash both boards with the same hex ? If not, try that first.  To eliminate the hardware issues.  After that you can debug the software.

  • 0 in reply to Nguyen Hoan Hoang

    Yes Nguyen, both are nrf52832 boards.

    1. I flashed both boards with same hex files.

    2. The one board which is not working seems to automatically connect to Windows' bluetooth and keeps switching from paired & connected statuses.

    3. I tried uninstalling the device on Windows but in vain.

    4. I tried assigning different bluetooth names as well.

    5. I tried erasing bond info in firmware but does not help.

Reply
  • 0 in reply to Nguyen Hoan Hoang

    Yes Nguyen, both are nrf52832 boards.

    1. I flashed both boards with same hex files.

    2. The one board which is not working seems to automatically connect to Windows' bluetooth and keeps switching from paired & connected statuses.

    3. I tried uninstalling the device on Windows but in vain.

    4. I tried assigning different bluetooth names as well.

    5. I tried erasing bond info in firmware but does not help.

Children
Related