<?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>How can i change NFC T4T library timeout variable</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/42461/how-can-i-change-nfc-t4t-library-timeout-variable</link><description>Hi to all, 
 i am developing a device based on nordic nrf52840 soc and i want use NFC tag type4 peripheral to implement a specific protocol. in normal condition all thing work well but in special condition when i need to done some process on the received</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 18 Jan 2019 14:19:09 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/42461/how-can-i-change-nfc-t4t-library-timeout-variable" /><item><title>RE: How can i change NFC T4T library timeout variable</title><link>https://devzone.nordicsemi.com/thread/166512?ContentTypeID=1</link><pubDate>Fri, 18 Jan 2019 14:19:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee286996-4095-4dd0-956b-97f8c22f1172</guid><dc:creator>alireza sadeghpour</dc:creator><description>&lt;p&gt;Hi and thanks for your response,&lt;/p&gt;
&lt;p&gt;i had set the FWI as you advised but it dose not has any impact on the nfc stack behaviour and again i receive 0x63 0x00 after 200ms in computer side. i am beginner in NFC and i want to know that this is standard behaviour? and there is any other option that i can try to solve the problem??&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How can i change NFC T4T library timeout variable</title><link>https://devzone.nordicsemi.com/thread/165566?ContentTypeID=1</link><pubDate>Mon, 14 Jan 2019 16:09:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43714acb-75e2-4d5c-8221-67c0a9a6827a</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We do not have an example.&lt;/p&gt;
&lt;p&gt;The FWI value is of type uint8_t, has a default value of 4, and a maximum value of either 4 or 7 depending on the SoC. Trying to set a too high value will give NRF_ERROR_INVALID_PARAM. You can see how FWI is converted to period here:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;#define NFC_T4T_FWI_TO_FWT(FWI)      (256u * 16u * (1 &amp;lt;&amp;lt; (FWI)))                /**&amp;lt; Macro for calculating FWT (in number of NFC carrier periods) from FWI parameter. */&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;I.e. the period will double for each FWI increment of one, and it will halve for each decrement of one. By that logic, a value of 6 would give 800 ms (if a value of 4 gives 200 ms).&lt;/p&gt;
&lt;p&gt;That means you should do something along the lines of:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;uint8_t new_FWI = 6;
ret_code_t err_code = nfc_t4t_parameter_set(NFC_T4T_PARAM_FWI, (void *) &amp;amp;new_FWI, sizeof(new_FWI));
app_error_check(err_code);&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>