ble_nus_c: the received packet is only 1 byte long while I send more than 1 byte

[Phan_hai_hust]

Hi nordic,

I send multiple bytes but always only receive packets of length = 1. For example in the picture, I sent 2 bytes 0x68, 0x69 ('DE') but only received the first value ('D'). I did not intentionally change the code of the file: ble_nus_c.h / .c (add only one line log_info as shown in the picture).
Maybe I accidentally fixed something that I didn't know. Please help me solve this problem.

I attached the link containing the file: ble_nus_c.h / c

sdk: 15.3.0

1drv.ms/.../s!Aj3liwrkan1lik6BnejCgL87glZN

[Phan_hai_hust]

My problem has been solved. Thank you.

[haakonsh]

Do you mind sharing your problem and your solution? It will help others in the future :)

[awneil]

Thanks for explaining.

So, for completeness, what application were you using?

[Phan_hai_hust]

Due to the above application, I will not trust non-popular applications :) . I tried to borrow another set to check. If you know any reliable peripheral simulation applications, can you suggest me :)

[awneil]

But what application was it?

Give a link!

Sending a single byte at a time is not "wrong" or "bad" as such - as with any tool, you have to understand what it does and how to use it.

nRF Connect can act as an 'Advertiser', if you run it on a suitable device. Never tried it myself, though.

[Phan_hai_hust]

play.google.com/.../details

[awneil]

Thanks.

I note that it says,

"This is an Android application that allow developer configure a BLE peripheral simulator. The application allow to profile multiple peripheral simulators. Possibility customization characteristic's handler, this would help you to build enough complexity simulator serve your software"

So it sounds rather like it's a basis for you to work from - rather than a complete & ready-to-use solution?