How to make 'without response' in nus rx characteristic?

RE: How to make 'without response' in nus rx characteristic?

Manuel Kwong — Sat, 11 Jun 2016 14:06:51 GMT

I think it answered my major question...that I was confused by so called rx... channel.

RE: How to make 'without response' in nus rx characteristic?

Carles — Mon, 17 Aug 2015 13:05:51 GMT

There are no "channel" but instead you have a characteristic, and notifications are used by a server to send updates to the client. If you want to instead be a client and send write without response to a server, your server (peer device) must have a characteristic that you can write to.

RE: How to make 'without response' in nus rx characteristic?

Manuel Kwong — Mon, 17 Aug 2015 11:15:30 GMT

May be simply to ask and worth to test with : How to change the rx channel in nRF51 device to "write without response"?

RE: How to make 'without response' in nus rx characteristic?

Manuel Kwong — Mon, 17 Aug 2015 11:15:19 GMT

May be simply to ask and worth to test with : How to change the rx channel in nRF51 device to "write without response"?

RE: How to make 'without response' in nus rx characteristic?

Hung Bui — Thu, 11 Jun 2015 10:39:28 GMT

@Manuel: Are you sure you used our nus service without notification ? In our implementation the server is on the nRF51. So when the iOS device wants to send data from the phone to the nRF51 it will do a write command (write without response) on the tx characteristic. When the device want to send data to the iOS device, it will do a notification.

Note that you can only do write without response from the client to the server. So if you want to do write without response from the nRF51 to the phone, you would need to implement the server on the phone.

RE: How to make 'without response' in nus rx characteristic?

Carles — Wed, 10 Jun 2015 12:04:41 GMT

Hi there,

Notifications and Write without Response follow the exact same flow control mechanisms, so the speed should be roughly the same.

I am not sure what is going on here, maybe someone from the SDK team will be able to take a look.

Carles