A bug report of nRF Connect APP in Nordic UART Service

[conrad]

      I am developing my project in a nRF52832 custom board. I am working in SDK v12.2.0. My application program is based on ble_app_uart.

It seem a bug about the defined characteristic uuid of RX and TX. The definition in "ble_nus.c" is as the following:

     #define BLE_UUID_NUS_TX_CHARACTERISTIC 0x0002 /**< The UUID of the TX Characteristic. */
     #define BLE_UUID_NUS_RX_CHARACTERISTIC 0x0003 /**< The UUID of the RX Characteristic. */

But while I connect my board by nRF Connect APP in an android phone, the RX and TX characteristic uuid is not consistent with them 

defined in ble_nus.c. The TX uuid is 0003 and the RX uuid is 0002 instead. The version of nRF Connect APP is 4.19.2. This bug won`t

influence the operation of Nordic UART Service but just looks weird. 

[tesc]

Hi,

The UUIDs and names of the characteristics are correct in the nRF Connect app, and the functionality is correct both in the app and in the SDK. The variable names used in the SDK are wrong. (The correct naming of "TX" and "RX" is as seen from the device hosting the Nordic UART Service.) This was a bug in the SDK and it was fixed for SDK 13.0.0.

Please note that the NUS documentation on Infocenter for nRF5 SDK v12.3.0 and earlier is also wrong (although not exactly the same way as the code was wrong.) That as well was fixed for SDK v13.0.0.

(And yes, the line in the documentation that reads "This service exposes two characteristics: one for transmitting and one for receiving (as seen from the peer)" may easily mislead you into believing that the naming of those characteristics are as seen from the peer. They are not. The naming is as seen from the device, as is evident from the descriptions of the RX and TX characteristics following right after.)

Regards,
Terje

[conrad]

Hi Terje,

      Thanks for your reply! It is really helpful. 

      Best regards,

      Conrad