nRF UART characteristic shown as a descriptor

[Zeo]

Hi,

I'm working on an embedded system using PAN1026 bluetooth. I want to use the nRF APP to communicate with the bluetooth module. Currently I have:

• Setup the UART service as a primary service with UUID 6E400001-B5A3-F393-E0A9-E50E24DCCA9E.

• Added Characteristic Rx with UUID 6E400003-B5A3-F393-E0A9-E50E24DCCA9E, properties as write with no response.

• Added the value for Rx characteristic as 0x0, 0x0, attribute permission as both readable and writable.

• Added Characteristic Tx with UUID 6E400002-B5A3-F393-E0A9-E50E24DCCA9E, properties as notify.

• Added the value for Tx characteristic as 0x0, 0x0, attribute permission as both readable and writable.

Using the nRF Master Control Panel APP, I see the service and the first characteristic shown as expected, but the second characteristic nested into the first characteristic as a descriptor. The order doesn't matter. i.e. If I define Rx first, Tx UUID shown as an unknown descriptor of Rx and vice versa. There appear to be an additional unknown descriptor with UUID "00002803-0000-1000-8000-00805F9B34FB". 0x2803 is for "GATT Characteristic Declaration" as from developer.bluetooth.org/.../DeclarationsHome.aspx.

It doesn't make sense to me why the second characteristic appear to be a descriptor of the first. I don't know what I'm missing. Any help is very much appreciated!

Thanks!

Here is the code: UART_svc_code.c

Here is a screenshot of the APP:

[RK]

Please post the code you're using to add the services and descriptors. There's a 'code post' button which just indents every line with 4 spaces which will make it look nice.