how to discovery 128bit characteristic UUID which is totally different form 128bit service UUIDhttps://devzone.nordicsemi.com/f/nordic-q-a/34561/how-to-discovery-128bit-characteristic-uuid-which-is-totally-different-form-128bit-service-uuidHi, I am trying to make nrf52832 as a UART certal. The service UUID and characteristic UUID of peripheral are shown as the following picture. They are all 128bit and quite different. In the example of &quot;ble_app_uart_c&quot; , the BLE_UUID_NUS_SERVICE, BLE_UUID_NUS_TX_CHARACTERISTICen-USTelligent Community 13Wed, 23 May 2018 07:27:03 GMTRE: how to discovery 128bit characteristic UUID which is totally different form 128bit service UUIDhttps://devzone.nordicsemi.com/thread/132882?ContentTypeID=1Wed, 23 May 2018 07:27:03 GMT137ad170-7792-4731-bb38-c0d22fbe4515:405088e4-bb37-4dd0-88f8-870d0aefd35bTurbo J<p>Unless I am mistaken, you need to add at least two vendor specific UUIDs using sd_ble_uuid_vs_add() API call.</p> <p>The primary service seems to use the base UUID from bluetooth standard, but the characteristics don&#39;t and they also seem to change the &quot;wrong&quot; byte(s) - that is why you need <em>two</em> uuids. Nordic softdevice only allows to &quot;re-use&quot; the same base UUID if byte 12 and 13 changes.</p><div style="clear:both;"></div>RE: how to discovery 128bit characteristic UUID which is totally different form 128bit service UUIDhttps://devzone.nordicsemi.com/thread/132863?ContentTypeID=1Wed, 23 May 2018 06:29:24 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7ed41123-18ed-4403-9bca-07fc0f8a616aBj&#248;rn Kvaale<p>I&#39;m a bit confused. Just to doublecheck: do you want to get the characteristic UUID of the uart central?</p><div style="clear:both;"></div>