S130 general purpose application

RE: S130 general purpose application

Anders Strand — Tue, 19 Jan 2016 07:49:50 GMT

Are you trying to turn on notifications from the "top" central? Turning on notifications is essentially doing a write command to a descriptor (the cccd) of a characteristic. Your relay device must catch these write commands and create its own write commands for the peripheral devices. How are you implementing it? Please confirm that the write commands arrive at the peripheral devices, and that the write command is to the correct handles.

RE: S130 general purpose application

Charlie329 — Mon, 18 Jan 2016 21:31:01 GMT

I had problem with handle values but now everything is ok. Now I am facing problem with notofications. I can enable or disable them but I have no idea why I don`t get any BLE_GATTC_EVT_HVX event. Any advice? Oh, and thank you for previous answers.

RE: S130 general purpose application

Anders Strand — Fri, 15 Jan 2016 13:31:35 GMT

Note that BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST could mean both read and write. Are you separating the two events in your code?

RE: S130 general purpose application

Charlie329 — Thu, 14 Jan 2016 21:46:47 GMT

So, I managed to read values from peripheral through central/peripheral device, but there is a problem with writing values on peripherals. It seems ok, all error codes are "success" but when I am trying to read that value after writing it I always get original value - nothing changes on peripheral.

On my c/p device, after I get "BLE_GATTS_EVT_RW_AUTHORIZE_REQUEST" ,which is write request, I use "sd_ble_gattc_write()" to write proper value on peripheral. Then, after getting response from it - "BLE_GATTC_EVT_WRITE_RSP" I use sd_ble_gatts_rw_authorize_reply() to send reply to my central device (master control panel). Should I store some values somewhere? I do not do that. Can it be a problem?

RE: S130 general purpose application

RK — Mon, 11 Jan 2016 23:44:24 GMT

What is the 'problem of communication between them'? It seems pretty direct (although inefficient), when the central reads the value of one of your characteristics, you read it from the peripheral you're connected to and return it. if the central writes to you, you write to the peripheral, if the central subscribes to a characteristic, you subscribe to it on your connected peripheral and when you receive updates, you send them on, and when it unsubscribes again, you do likewise. All you do is mirror the calls the central makes to you.

What is the problem you're having doing that?