<?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>Bluetooth write problem</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/21854/bluetooth-write-problem</link><description>I started with the blu_app_template on a 52840. I have advertising working. I can see that from an iOS app. I can also see the details of the service. I see the characteristic on the iOS side. I am having a problem with writing data on the characteristic</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 12 May 2017 04:28:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/21854/bluetooth-write-problem" /><item><title>RE: Bluetooth write problem</title><link>https://devzone.nordicsemi.com/thread/85823?ContentTypeID=1</link><pubDate>Fri, 12 May 2017 04:28:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fee837fa-c636-400e-8e8a-0e3e5990939a</guid><dc:creator>EricY</dc:creator><description>&lt;p&gt;Not yet. I will try that next.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth write problem</title><link>https://devzone.nordicsemi.com/thread/85826?ContentTypeID=1</link><pubDate>Thu, 11 May 2017 08:49:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:95b8a89a-ece4-4b44-8c53-34a61a12f420</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Ok. Have you tried doing a sniffer trace?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth write problem</title><link>https://devzone.nordicsemi.com/thread/85822?ContentTypeID=1</link><pubDate>Wed, 10 May 2017 17:28:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b14eb0af-a4d9-4dd7-9f27-d0c2a22290bd</guid><dc:creator>EricY</dc:creator><description>&lt;p&gt;Yes, I have modified the ble_app_template. I now have two service uuids with only one active at boot. I am attaching the same characteristic to either service. I can see the service and characteristic with LightBlue on iOS. With my own iOS app, I am sure that I am writing to the value as I can change it&amp;#39;s properties and I see those changes in my iOS App. I am testing this by using my iOS and debugging the code on the 52840 with Eclipse.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth write problem</title><link>https://devzone.nordicsemi.com/thread/85824?ContentTypeID=1</link><pubDate>Tue, 09 May 2017 07:08:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6f0fd680-19af-4f39-b78b-d806eb06b3e6</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;Ok. Have you modified the ble_app_template? What app are you using on iOS? nRF Connect? Do you see the same behavior on Android? Are you sure that the write event you get are the write that you performed? How are you testing this? Calling sd_ble_uuid_vs_add() with the same base UUID shouldn&amp;#39;t be a problem, the base will only be added to the SoftDevice once, and the same type reference will be returned in both cases.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth write problem</title><link>https://devzone.nordicsemi.com/thread/85821?ContentTypeID=1</link><pubDate>Mon, 08 May 2017 16:30:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79bc0391-8700-47b5-94ae-2e4091f8c0a6</guid><dc:creator>EricY</dc:creator><description>&lt;p&gt;Both the value seems to be incorrect and the handle is incorrect. I get the handle 0x0d but I would have expected it to be 0x10. I can see this on the iOS side. If I change the properties to/from write/ write with response, I can see those effects on the iOS side. I also only have one writable value.  I think I may see an issue now. I am calling sd_ble_uuid_vs_add twice with the same base uuid, once for the service and once for the characteristic. Could that be the root of this issue?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth write problem</title><link>https://devzone.nordicsemi.com/thread/85825?ContentTypeID=1</link><pubDate>Mon, 08 May 2017 12:04:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4275352-9fb1-4b13-a181-060b54990cbd</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;So you get a write event, but the value and handle is incorrect? Or just the handle? What is the expected handle? Are you sure that the write event you get are the write that you performed? How are you testing this?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>