How to do a write request on a 20 bytes characteristic?

RE: How to do a write request on a 20 bytes characteristic?

JCombes — Mon, 22 Jul 2019 12:07:45 GMT

Hi,

The error was coming from the fact the write request was configured for the write of the CCCD.

I had this :

So there was problems when I tried to put a 20 bytes value in gattc_value.

Now I have this and it work :

Thank you for your help Havard.

RE: How to do a write request on a 20 bytes characteristic?

Håvard — Fri, 19 Jul 2019 16:13:44 GMT

Well, that certainly looks like error code 7 (NRF_ERROR_INVALID_PARAM).

It's hard from looking at these screenshots what happened to your variables. I would preferably step in the code with a debugger, or like you are doing, add more prints to figure out if you have any problems with pointers or scope of your variables.

RE: How to do a write request on a 20 bytes characteristic?

JCombes — Fri, 19 Jul 2019 13:19:43 GMT

Hi Havard,

I tried to write the characteristic with nrf connect and it worked.

I added logs in tx_buffer_process() so we can see what is happenning :

It gave me this result :

Here we can see the value I wented to write (05 00 33 79 81 02 36 11 11 11 11 11 11 11 11 01 00 00 00 00) and then we the variables used in sd_ble_gattc_write() . All the variables except the conn_handle are different than what I was expecting.

RE: How to do a write request on a 20 bytes characteristic?

Håvard — Thu, 18 Jul 2019 15:42:00 GMT

Hi,

Sounds cryptic that you can write 4 bytes but not more. In fact, vlen = 0 means that the length of the characteristic should always be 20 (CONCENTRATOR_FRAME_SIZE). In the "write" screenshot above I see that you are using CONCENTRATOR_FRAME_SIZE so if that is 20 then it should be fine.

Could you run the project in debug mode, and post the state of the variables just as you are calling sd_ble_gattc_write() from the central?

It may give us some useful clues.

Have you tried writing to this characteristic from other sources (nRF Connect for PC or mobile?) I just want to confirm that the problem is on the client-side where you are seeing the error code (and not the server-side).