<?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>Impact of small maximum connection intervals and adherence to specification</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/68305/impact-of-small-maximum-connection-intervals-and-adherence-to-specification</link><description>I am working on a nRF52 device as a peripheral that is communicating with an Android tablet central, and have been doing some experiments with the connection interval parameters. 
 Currently our minimum is 100ms and our max is 200ms. I&amp;#39;ve tried lowering</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/68305/impact-of-small-maximum-connection-intervals-and-adherence-to-specification" /></channel></rss>