Any experts with BLE protocols?

[richardman]

Any experts with BLE protocols hanging around here? If so,please PM me?

Thanks

[alexanderbrevig]

Why not ask your question publicly so answers may benefit us all? I'm no expert but I've played around with Nordic nRF51 and 52 and the ble enabled psoc from cypress.
The specification is actually quite good when you over the first somewhat steep learning curve.

[richardman]

The question is very specific but you are right, I can cast it to a form that may benefit other people. What I want is to send multiple set of data between a smartphone and an embedded system using BLE - currently using the ST BlueNRG but that detail does not matter.

The data is bidirectional and varying in length. I know there's a bandwidth limitation with BLE and that each transaction is limited to just tens of bytes so I will have to break up the data into multiple chunks if necessary.

What I want to confirm is that once I get the phone and the embedded device handshaking and bounded, then I can just use a set of UUID that the phone app and the embedded code agree on, and then send the data between them, using my own protocol.

[janekm]

The question is very specific but you are right, I can cast it to a form that may benefit other people. What I want is to send multiple set of data between a smartphone and an embedded system using BLE - currently using the ST BlueNRG but that detail does not matter.

The data is bidirectional and varying in length. I know there's a bandwidth limitation with BLE and that each transaction is limited to just tens of bytes so I will have to break up the data into multiple chunks if necessary.

What I want to confirm is that once I get the phone and the embedded device handshaking and bounded, then I can just use a set of UUID that the phone app and the embedded code agree on, and then send the data between them, using my own protocol.

If I understand what you mean, then yes... BLE uses a system of Services & Characteristics to give structure to the data exchanged (to a point), but if you want you can just define a single service & characteristic and exchange the data over that, with your own internal format. BLE doesn't care what you actually transmit in each write to / notification from a characteristic. You can have a look at this "UART" service for an example: https://developer.mbed.org/teams/Bluetooth-Low-Energy/wiki/UART-access-over-BLE

[richardman]

If I understand what you mean, then yes... BLE uses a system of Services & Characteristics to give structure to the data exchanged (to a point), but if you want you can just define a single service & characteristic and exchange the data over that, with your own internal format. BLE doesn't care what you actually transmit in each write to / notification from a characteristic. You can have a look at this "UART" service for an example: https://developer.mbed.org/teams/Bluetooth-Low-Energy/wiki/UART-access-over-BLE

Exactly what I hope to hear. THANKS