Sean Houlihane

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

9 years, 9 months ago.

How are UUIDs allocated - RedBear UART

I've been trying to OOB my RedBear BLE Nano, and after realising that the beacon example was actually working, moved on to nRF51822_SimpleChat. The nRF Toolbox application for Android reports 'The device does not have required services'. In desperation, I tried the BLE_LoopbackUART and that is correctly recognised. The two examples use differnet UUIDs:

713D0000-503E-4C75-BA94-3148F18D941E (hard coded in the SimpleChat example) 6E400001-B5A3-F393-E0A9-E50E24DCCA9E (the one that works)

Is 'SimpleChat' some made up service in this context? I genuinely have zero interest in the protocol - I just need (at this stage) a UART which is compatible with existing tools, and ideally an end to end IP connection.

Question relating to:

Last updated: 07 Jan 2016
This is a simple program to work with RedBearLab BLE Controller App. Type something from the Terminal to send to the BLEController App or vice verse. Characteristics received from App … BLE, nRF51822, RedBearLab

1 Answer

Sam Grove
9 years, 7 months ago.

I don't think you'll yet find an IP connection over BLE without some unintentional use of the protocol but here is a UART example that should get you going. HTH!

http://developer.mbed.org/teams/Bluetooth-Low-Energy/wiki/UART-access-over-BLE

Accepted Answer