HID Mouse/ HID Keyboard / NUS Connection parameters

RE: HID Mouse/ HID Keyboard / NUS Connection parameters

Petter Myhre — Wed, 28 Jan 2015 11:28:56 GMT

Great. That is exactly what I mean :)

RE: HID Mouse/ HID Keyboard / NUS Connection parameters

MANGO — Wed, 28 Jan 2015 11:08:15 GMT

Thanks for replying. You are right. I did merge HID and NUS together.

(The merged service which I made is following the NUS connection parameters.)

Using the nRF UART app, I tested both the volume key and the UART sending / recieving back and forth.

Both services did worked simultaneously.

One of the concerns is that, since each services (as you saw at each examples) are using different connection parameters, I wondered that the merged service would be fine or not. (because I thought each services worked at certain connection parameters.)

You mean regardless of the service I use or what mixed services is used,

the connection parameters doesn't have relationship with these services and

the parameters should follow the Bluetooth Core Specification, is it?

Anyways, I think your answer saved me. Thanks !!!

-Regards, Mango922

RE: HID Mouse/ HID Keyboard / NUS Connection parameters

Petter Myhre — Wed, 28 Jan 2015 10:09:50 GMT

They just do. These are examples, you can change the parameters to anything you want, as long as you follow the Bluetooth Core Specification (and the iOS guidelines, if you want to be able to connect to iOS devices).
If you are able to connect in the app it has nothing to do with the connetion parameters. It is just how iOS is. iOS devices will not show BLE devices in the Bluetooth Settings, so you have to use an app to be able to discover such devices.
I can't see why it should be possible to merge these services, but it isn't something I have done myself.