BLE notification sending invalid data

RE: BLE notification sending invalid data

Edvin — Mon, 28 Mar 2022 06:52:44 GMT

[quote user="Keith V"]

my custom functions are listed in the message.

[/quote]

Yes, but not all functions that you have used to replicate the issue. Particularly the initialization of the service. Besides. I can set up a characteristic that sends this sort of data (or I can demonstrate it using the ble_app_uart example), but that will not replicate the issue that you are seeing.

[quote user="Keith V"]I did use a phone, what difference would a dev kit make?[/quote]

No difference. A phone should be fine.

[quote user="Keith V"]is there an example showing how to do this?[/quote]

How to do what, exactly? The ble_app_uart example is quite versatile, as you can use it to send a data array over BLE.

If you upload your project, so that I can simply compile it and run it to replicate the issue, I can have a look at what the issue might be. I can't tell from the snippets you have provided. But perhaps debugging can give a better idea.

Best regards,

Edvin

RE: BLE notification sending invalid data

Keith V — Fri, 25 Mar 2022 14:24:05 GMT

my custom functions are listed in the message.

LED_TIME_LENGTH is 5 yes

I did use a phone, what difference would a dev kit make?

is there an example showing how to do this?

it can't be a new idea

RE: BLE notification sending invalid data

Edvin — Fri, 25 Mar 2022 13:31:38 GMT

Hello,

I don't know what your custom functions do. All I can see is that you are sending LED_TIME_LENGTH bytes (I guess LED_TIME_LENGTH is 5, since you are receiving 5 bytes), and the first byte is the parameter "Type" = data = p_evt_write->data[0];

However, it looks like it should be correct from where you print using NRF_LOG_RAW_INFO().

Is it possible for me to reproduce this on a DK and a phone? If so, would it be possible to share the project?

BR,

Edvin

RE: BLE notification sending invalid data

Keith V — Thu, 24 Mar 2022 18:51:07 GMT

Thanks Edvin,

My device is the peripheral and nRFConnect ( desktop ) is the central

I print in 2 places, the on_write() and SendNotify(), the commas are not printed no, here's whats actually printed: I've changed the value 01f4 to 03E8 for other reasons....

nRFConnect should show "(0x) 01-07-D0-03-e8

<info> MTserv: BLE_GATTS_EVT_WRITE: 60<
<info> MTserv: LED Time, 1, 03E8, 07D0
Notify, 0, 0107D003E8

the data buffer looks correct ( same data as notify )

I'm using nRF connect on the PC, but tried it on my phone with the same results(0x) 00-04-00-20-81

This is from the PC

RE: BLE notification sending invalid data

Edvin — Fri, 18 Mar 2022 22:32:04 GMT

Hello,

So you are sending this data from a peripheral and receiving it on a central, the central is a computer or a phone?

Can you please try to debug, and compare the data buffers (length and actual data) when you send it and when it is received? I see that you are printing:

   NRF_LOG_RAW_INFO("Notify, %d, ", err_code);
   for(int i=0; i< len; i++)
   {
      NRF_LOG_RAW_INFO("%02x", data[i]); 
   }
   NRF_LOG_RAW_INFO("\n");

But you say that you see:

"02, 01F4, 07D0 ( as output by NRF_LOG_INFO() )"

Is that what the Notify print is printing? If so, shouldn't it just output hexadecimal values, and not the commas?

It is not clear to me where you see the. Is the 02, 01F4, 07D0 actually from the NRF_LOG_INFO()?

And when you say nRF Connect, is it the desktop app, or on a phone?

Best regards,

Edvin