sd_ble_gatts_hvx() return error :0x3401

RE: sd_ble_gatts_hvx() return error :0x3401

Stefan Birnir Sverrisson — Wed, 18 Mar 2015 12:36:53 GMT

This tutorial goes through the procedure in Master Control Panel in order to receive notifications from a server.

RE: sd_ble_gatts_hvx() return error :0x3401

Michael Theurl — Mon, 16 Mar 2015 09:24:03 GMT

Hy,

Can you show me an example i have the same issue, on the lbs example code.

RE: sd_ble_gatts_hvx() return error :0x3401

Ulrich Myhre — Thu, 05 Mar 2015 15:55:45 GMT

The system attributes consist of the CCCD values, i.e. the "preferences" for a peer. You are required to save these peer-specific values between connections if you are bonded, and the example Device Manager shows you how this can be done. Please refer to the GATTS documentation or header files for sd_ble_gatts_sys_attr_set(), *_get() and sd_ble_gatts_hvx() for lots of information on how these affect your program. In short, you have to detect that these are written to when WRITE events come, and only allow hvx() calls after they are enabled.

RE: sd_ble_gatts_hvx() return error :0x3401

mohBOSS — Thu, 05 Mar 2015 15:49:06 GMT

Hi Ulrich, please what are the system attributes ? Who get the access to them ?And how can I be awre if the GATT client has enabled the notification/indication ?

RE: sd_ble_gatts_hvx() return error :0x3401

Ulrich Myhre — Thu, 05 Mar 2015 15:42:27 GMT

If you look at the other examples, they change an internal state when the CCCD of the characteristic you want to indicate/notify is written to. Before restoring system attributes (sys_attr_get/set) or a write to the CCCD, all CCCD values are unknown. Attempting to call hvx() on a characteristic value where the CCCD is in an unknown state will return an error.

RE: sd_ble_gatts_hvx() return error :0x3401

mohBOSS — Thu, 05 Mar 2015 15:39:06 GMT

Hi all,

the problem is solved (Thank you God). In fact, the peripheral should enable the notification, and since I am testing with MCP as a peripheral, I have had to click on the " Enable Services" button. The BLE_EVT_TX_COMPLETE event was generated after calling sd_ble_gatts_hvx().

RE: sd_ble_gatts_hvx() return error :0x3401

Ulrich Myhre — Thu, 05 Mar 2015 15:36:40 GMT

What SoftDevice version is this? There are different error codes that could fit, depending on your version.

RE: sd_ble_gatts_hvx() return error :0x3401

mohBOSS — Thu, 05 Mar 2015 13:45:07 GMT

Hi Dan, in fact the GATT server (peripheral)needs to send rssi+MAC to a GATT client(central).When testing, I use the Dongle as a GATT client(with MCP).I dont know if the dongle is configured to accept async messages. The new problem is, as I edited in the question is the 0x3001 error.It is a BLE_ERROR_INVALID_CONN_HANDLE .I am using s130 in the GATT server.

RE: sd_ble_gatts_hvx() return error :0x3401

Dan Danknick — Thu, 05 Mar 2015 13:38:40 GMT

This code looks just like mine that works on multiple products. I would only point out that your Central may need to be configured to accept async messages (indications, notifications) though you haven't told us what that program is.

Also, you do mean to send 4 bytes back, right? Because that is what this bit of code compiles to when data_to_send is a pointer:

 uint16_t len = sizeof(data_to_send);

Best, Dan

RE: sd_ble_gatts_hvx() return error :0x3401

mohBOSS — Thu, 05 Mar 2015 07:08:07 GMT

All configurations that I did are in the attachement, I followed many similar examples. I don't know what I missed. Did you mean the GATT client, by saying Central ?

RE: sd_ble_gatts_hvx() return error :0x3401

Locky — Thu, 05 Mar 2015 03:59:17 GMT

Are you sure the Characteristic you have setup for this data transfer has Notifications? Is the Central enabling the Notifications?