This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

using nRF5x with windows; how to get windows to accept parameters help

I am currently working with a the nRF5x bluetooth chip family and connecting to a windows 10 device as a central. I am using uart to get some visibility into what is happening and sadly it appears as if the central is refusing to accept the desired connection parameters. Has anyone had this issue before and been able to solve it?

Parents
  • Please add more details. What example or project you used (at least as baseline) on nRF5x, what exactly the debug says, what radio analyzer/sniffer logs say etc. If you read your question and inputs it's as vague as it could be (how do you find out that windows don't like the connection parameters? If windows are Central then they choose the parameters so it doesn't make sense... and if nRF5x FW doesn't like the parameters set by Windows peer that doesn't make sense either because all Nordic Peripheral examples work with pretty much any legal connection parameters, so it would mean your custom code is "refusing" the connection... overall not really clear what are you doing and what you see).

Reply
  • Please add more details. What example or project you used (at least as baseline) on nRF5x, what exactly the debug says, what radio analyzer/sniffer logs say etc. If you read your question and inputs it's as vague as it could be (how do you find out that windows don't like the connection parameters? If windows are Central then they choose the parameters so it doesn't make sense... and if nRF5x FW doesn't like the parameters set by Windows peer that doesn't make sense either because all Nordic Peripheral examples work with pretty much any legal connection parameters, so it would mean your custom code is "refusing" the connection... overall not really clear what are you doing and what you see).

Children
No Data
Related