<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Is there a change in the implementation of the connection interval update request between bare-metal SDKs v0.9.0 and v1.0.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128327/is-there-a-change-in-the-implementation-of-the-connection-interval-update-request-between-bare-metal-sdks-v0-9-0-and-v1-0-0</link><description>Hi, 
 
 I see the different behavior of the function sd_ble_gap_conn_param_update when connected to Windows integrated Bluetooth. 
 
 Using bare-metal SDK v0.9.0 it succeeds on the first call. 
 Using bare-metal SDK v1.0.0 it occasionnaly returns NRF_ERROR_BUSY</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 14 Nov 2017 10:43:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128327/is-there-a-change-in-the-implementation-of-the-connection-interval-update-request-between-bare-metal-sdks-v0-9-0-and-v1-0-0" /></channel></rss>