nRF Connect PC Device Name String Limited to 22 Characters

[REckhardt]

I am using nRF Connect for desktop v2.6.0 with an nRF51 dongle. On my device, my Bluetooth Device Name String is 23 characters long. The string is too long to completely show in the advertised data on the right side of the screen, but when I connect to the device, the last character always displays as "7" or 0x37 even though it is not a "7".  If I make the string 24 characters long, the last two characters always display as "75" or 0x37 0x35.  This persists even when I read the name from the device again.

On my android phone the bluetooth data appears normal.  What could be causing this behavior?  If the Bluetooth on my phone can read the Device Name properly, why can't the nRF Connect software?

Thanks, Rocky

[REckhardt]

Apart from the Device Name, we also encode a byte of flags.  Total number of bytes = 28.  Here is the breakdown:

FLAGS:

Data type: 1 byte

Data Length: 1 byte

Flags: 1 byte

DEVICE NAME:

Data type: 1 byte

Data Length: 1 byte

Device name: 23 bytes

TOTAL: ble_advdata_encode() = 28 bytes

I'm still confused about how things work perfectly with my android phone, but fail with the nRF Connect software.

Thanks, Rocky

[AndreasF]

Hi.

Could you provide me with some screenshots? Of both the phone and nRF Connect Desktop software?

Best regards,

Andreas

[REckhardt]

Here are the two screen shots.  The last digit of the advertised name should be "8" instead of a "7" as the nRF Connect reports.

[AndreasF]

Hi.

Can you compare the names and take a screenshot when you connect to the device on your phone with the nRF Connect Application?

Best regards,

Andreas

[REckhardt]

Here is the screenshot.

I had only been looking at the advertised data without using the App on the phone.  Now that I am using the nRF Connect app, the last digit is wrong there as well.

It is apparent now that the advertised Device Name works fine, but explicit reads of the Device Name fail.

[AndreasF]

Hi.

Could you provide me with your code, so I can have a look?

I can make this case private in case you don't want your code shared public.

Best regards,

Andreas

[REckhardt]

Thank you for all your help Andreas.  We have figured out the problem is in the Bluetooth stack somewhere which is not a Nordic Semiconductor issue.  We should be able to track it down from here.

Thanks again,

Rocky

[AndreasF]

Hi.

Could you share the problem? In case other people have a similar issue.

I'm glad you figured it out, good luck.

Best regards,

Andreas