Is there any equivalent to the SPP profile from Bluetooth Classic? I've always used this as a way to transmit custom data using Bluetooth, but I can't seem to find anything equivalent for BLE.
Is there any equivalent to the SPP profile from Bluetooth Classic? I've always used this as a way to transmit custom data using Bluetooth, but I can't seem to find anything equivalent for BLE.
Unfortunately, I can't really give any promises on schedule yet, especially not now in the time of holidays and variants.
In the mean time, this question, which I answered earlier may give some good hints: http://devzone.nordicsemi.com/index.php/what-is-the-most-efficient-way-to-transfer-data-over-ble The general tip is to structure things similar to the SDK services, make an init method that adds the service and all its characteristics, an event handler to handle events coming from the S110 and then all methods you need to do whatever is special for your service. As I said to the other person, the battery service is probably the simplest in the SDK, and should be a good starting point.
Thanks again for your prompt replies - they are incredible helpful :-)
I'll try to extend the battery service and see if I can make something useful out of it.
Hi Ole. Any news on that services app note? ;)
"application note explaining how to build a custom service for the S110"
This would be tremendously valuable. A basic example using the softdevice gatt functions would make this a lot easier. Although the BPS example is simple, it doesn't provide enough information to extrapolate the order of operations needed to setup the custom GATT details.
Any ETA? Shoot, a code snippit showing the services_init() function would probably be enough to help.
Very useful information. However - one of the reasons SPP is so attractive is on the host side (PC, smartphone,,): Here you don't need to use and know special libraries to get connected to SPP. Its the usually well known serial port library which is supported in all compilers and languages.
Can you comment what is needed on the host side for this BLE solution? I know this may be too broad a scope to answer. Personally I am in Windows.
Will this aspect be mentioned in the upcoming app note?