<?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>CPS/SEN/SPE/BI-04-C [Procedure Already In Progress]</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/16442/cps-sen-spe-bi-04-c-procedure-already-in-progress</link><description>We are trying to complete Bluetooth qualification on our Cycling Power Service (CPS) against the Bluetooth Test Specification (Document Number CPS.TS.1.1.1). 
 We fail the test case: 
 CPS/SEN/SPE/BI-04-C [Procedure Already In Progress] 
 Verify that</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 16 Sep 2016 09:13:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/16442/cps-sen-spe-bi-04-c-procedure-already-in-progress" /><item><title>RE: CPS/SEN/SPE/BI-04-C [Procedure Already In Progress]</title><link>https://devzone.nordicsemi.com/thread/62945?ContentTypeID=1</link><pubDate>Fri, 16 Sep 2016 09:13:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1237cb44-5f31-4d71-8ca7-347e7b8ef59e</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi yes_you_do_need_a_user_name,&lt;/p&gt;
&lt;p&gt;Error code &lt;code&gt;Procedure Already in Progress (0x80)&lt;/code&gt; is a  &lt;em&gt;Attribute Protocol Application error code&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;These error codes fits inside BLE_GATT_STATUS_ATTERR_APP_BEGIN (0x0180) and BLE_GATT_STATUS_ATTERR_APP_END (0x019F).&lt;/p&gt;
&lt;p&gt;You should not use the BLE_GATT_STATUS_ATTERR_CPS_PROC_ALR_IN_PROG  (by coincident there is also a CPS here, but not the CPS you are testing, it&amp;#39;s Common Profile and Service )&lt;/p&gt;
&lt;p&gt;You should use BLE_GATT_STATUS_ATTERR_APP_BEGIN (since it&amp;#39;s 0x80) as the return code in the reply to the authorization write event.&lt;/p&gt;
&lt;p&gt;You can have a look at the ble_app_proximity example in SDK v12 where we reply with Application error : APP_FEATURE_NOT_SUPPORTED (0x82) = BLE_GATT_STATUS_ATTERR_APP_BEGIN+2 .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>