<?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>what is the propagation delay through ppi</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/16417/what-is-the-propagation-delay-through-ppi</link><description>Hi all, in my project I have a input pin and out pin whenever pulse is raised on input pin I need to set out pin exactly after 8.3ms. 
 For these I&amp;#39;m using ppi by configuring input pin response to ppi channel1 event and timer1 start to ppi channel1 task</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 14 Sep 2016 12:47:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/16417/what-is-the-propagation-delay-through-ppi" /><item><title>RE: what is the propagation delay through ppi</title><link>https://devzone.nordicsemi.com/thread/62837?ContentTypeID=1</link><pubDate>Wed, 14 Sep 2016 12:47:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0abe97ec-2893-47d9-a5a8-6d557b42d271</guid><dc:creator>Ole Bauck</dc:creator><description>&lt;p&gt;If you take the ppi delay alone it is about 1 clock cycle which equals 62.5ns. You can actually test this by using the code &lt;a href="https://devzone.nordicsemi.com/question/44628/maximum-clock-possible-on-gpio-pin-nrf51/?answer=44639#post-id-44639"&gt;here&lt;/a&gt; and compare the pulse when using ppi to clear the timer instead of shorts.&lt;/p&gt;
&lt;p&gt;If the peripheral you are using require some resources that are not on you will have to start these first. As the product specification says (part 3.4.2.2 System ON mode):&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;(…) The PPI task response will vary
depending on the resources required by
the peripheral where the task
originated. The resources that could
be involved are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;1V7 with the startup time t1V7&lt;/li&gt;
&lt;li&gt;1V2 with the startup time t1V2&lt;/li&gt;
&lt;li&gt;One of the following clock sources&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;ul&gt;
&lt;li&gt;RC16 with the startup time tSTART,RC16&lt;/li&gt;
&lt;li&gt;XO16M/XO32M with the startup time the clock management system tXO&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;
&lt;p&gt;but since you say that you don’t go into low power mode (__WFE() or sd_app_evt_wait) you should not need to worry about this.&lt;/p&gt;
&lt;p&gt;Since you are using pin in and out event, the impedance on the pin may also affect the response. Typical pin capacitance is 4pF and typical pull-up resistance is 13KOhm. This circuit will have a rise and fall time.&lt;/p&gt;
&lt;p&gt;What is the actual time you are measuring and how are you measuring it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>