<?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>NRF Open Mesh change PPI</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/12377/nrf-open-mesh-change-ppi</link><description>Hi, would there be any drawback in setting TIMER_PPI_CH_START to 11 to maximize the number of free PPI for application. 14-&amp;gt;15 should be free to use in timeslot and ppis are only used in timeslots for the mesh if I understand correctly.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Mar 2016 09:44:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/12377/nrf-open-mesh-change-ppi" /><item><title>RE: NRF Open Mesh change PPI</title><link>https://devzone.nordicsemi.com/thread/46797?ContentTypeID=1</link><pubDate>Tue, 08 Mar 2016 09:44:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ac08b61-2efa-4c25-8606-635efaf52f84</guid><dc:creator>Trond Einar Snekvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;As long as you keep track of the PPIs for your own application, and make sure there aren&amp;#39;t any conflicts, there shouldn&amp;#39;t be any problems with changing the PPI channels for the mesh timer. In fact, version v0.7.0 and up don&amp;#39;t use the PPI channels at all. They might be used in future releases though, so I wouldn&amp;#39;t start throwing them out completely unless strictly necessary.&lt;/p&gt;
&lt;p&gt;You&amp;#39;ll be fine moving them up to 11, now and in the future :) In fact, you can move them all the way up to 13, as the last slot is only used for timestamping, and cannot be assigned a PPI channel as the timer_control module is today. This is unlikely to change.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>