This is a demonstration of how to create a GATT service and characteristic.

Dependencies:   BLE_API mbed nRF51822

Fork of BLE_EvothingsExample_GATT by Austin Blackstone

Intro

This code demonstrates how to use the BLE_API to create a GATT service and characteristic to toggle a LED on / off.

Overview

This code is a demonstration of how to create a custom service (UUID=0xA0000) with two characteristics, a read only characteristic (UUID=0xA001) and a write characteristic (UUID=0xA002). What is written to the write characteristic will be copied across to the read characteristic and broadcast out. If a single byte is written it will be used to toggle the on board LED, if more than 1 byte is written the data will be written out to the terminal. The default max size is 10bytes.

Video

This is a video of how to use this example. Please note that in this video Android is used to read / write the characteristics. This could just as easily been done with the Evothings App listed below or an equivalent iOS app. Any app that can read/write characteristics could have been used.

Details

characteristic and service UUID's are initialized here

UUID's

uint16_t customServiceUUID  = 0xA000;
uint16_t readCharUUID       = 0xA001;
uint16_t writeCharUUID      = 0xA002;


We set up the list of available UUID's that will be advertised as part of the GAP advertising packet here. (it is good form to make this match the services you are actually advertising, so in this case we should set it to be 0xA000, but we are choosing to set it to 0xFFFF so it is easier to distinguish on the scanning app)

Set_ServiceID's

static const uint16_t uuid16_list[]        = {0xFFFF};
...
ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LIST_16BIT_SERVICE_IDS, (uint8_t *)uuid16_list, sizeof(uuid16_list)); // UUID's broadcast in advertising packet


Next we set up the characteristics and then put them together into a service. Notice that each characteristic has a maximum of 10Bytes of Value space, this can be expanded up to 512B.

Setup_Service_&_Characteristics

// Set Up custom Characteristics
static uint8_t readValue[10] = {0};
ReadOnlyArrayGattCharacteristic<uint8_t, sizeof(readValue)> readChar(readCharUUID, readValue);
 
static uint8_t writeValue[10] = {0};
WriteOnlyArrayGattCharacteristic<uint8_t, sizeof(writeValue)> writeChar(writeCharUUID, writeValue);
 
// Set up custom service
GattCharacteristic *characteristics[] = {&readChar, &writeChar};
GattService        customService(customServiceUUID, characteristics, sizeof(characteristics) / sizeof(GattCharacteristic *));


Next we setup the writeCharCallback() function that will be called when a BLE onDataWritten event is triggered (when someone writes to a characteristic on the device). This function will check to see what characteristic is being written to and then handle it appropriately. In this case there is only one writable characteristic so its redundant, but good form for more complex service/characteristic combinations.

On_Characteristic_written_to_callback

void writeCharCallback(const GattCharacteristicWriteCBParams *params)
{
    // check to see what characteristic was written, by handle
    if(params->charHandle == writeChar.getValueHandle()) {
        // toggle LED if only 1 byte is written
        if(params->len == 1) {
            led = params->data[0];
            ...}
        // print the data if more than 1 byte is written
        else {
            printf("\n\r Data received: length = %d, data = 0x",params->len); 
            ...}
        // update the readChar with the value of writeChar
        ble.updateCharacteristicValue(readChar.getValueHandle(),params->data,params->len);
    }
}
...
// register callback function
ble.onDataWritten(writeCharCallback);
...


The last thing to do is register the service with the BLE object so it is available.

Add_Service_to_BLE_Object

...
    // add our custom service
    ble.addService(customService);
...

Viewing Data

You can use either the LightBlue app on iOS or the nRF Master Control Panel application on Android to view the advertising data. Alternatively you can use a custom GATT Evothings App to view the data.

Evothings?

Evothings is a rapid prototyping environment that uses cordova to enable you to rapidly develop smartphone applications in Javascript. Please download the Evothings workbench to your computer and the Evothings client to your smartphone. The Evothings workbench will come with a program called "mbed Evothings GATT", this Evothings Smartphone program is meant to be used with the embedded mbed code. For instructions on how to use evothings please see the reference section below.

Reference

Committer:
mbedAustin
Date:
Sat Feb 14 15:43:55 2015 +0000
Revision:
5:d0548c64e2e7
Parent:
4:7ef90665b399
Child:
6:97b22b5bfbb8
added write characteristic handler.

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbedAustin 0:cd5b6733aeb1 1 #include "mbed.h"
mbedAustin 0:cd5b6733aeb1 2 #include "BLEDevice.h"
mbedAustin 1:94152e7d8b5c 3 #include "CustomService.h"
mbedAustin 1:94152e7d8b5c 4
mbedAustin 1:94152e7d8b5c 5
mbedAustin 1:94152e7d8b5c 6 // BLE object
mbedAustin 1:94152e7d8b5c 7 BLEDevice ble;
mbedAustin 1:94152e7d8b5c 8
mbedAustin 1:94152e7d8b5c 9 // LED object
mbedAustin 1:94152e7d8b5c 10 DigitalOut led(LED1);
mbedAustin 1:94152e7d8b5c 11
mbedAustin 1:94152e7d8b5c 12 const static char DEVICE_NAME[] = "MyDeviceName"; // change this
mbedAustin 1:94152e7d8b5c 13 static const uint16_t uuid16_list[] = {0xFF}; //Custom UUID, FF is reserved for development
mbedAustin 1:94152e7d8b5c 14
mbedAustin 2:e84c13abc479 15 // Set Up Characteristics
mbedAustin 2:e84c13abc479 16 static uint8_t readValue[1] = {0x00};
mbedAustin 2:e84c13abc479 17 GattCharacteristic readChar(0xAAAA /* read char UUID*/, readValue, sizeof(readValue), sizeof(readValue),
mbedAustin 2:e84c13abc479 18 GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_READ | GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_NOTIFY);
mbedAustin 2:e84c13abc479 19
mbedAustin 2:e84c13abc479 20 static uint8_t writeValue[1] = {0x00};
mbedAustin 2:e84c13abc479 21 GattCharacteristic writeChar(0xBBBB /*write char UUID*/, writeValue, sizeof(writeValue), sizeof(writeValue),
mbedAustin 2:e84c13abc479 22 GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_WRITE | GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_NOTIFY);
mbedAustin 2:e84c13abc479 23
mbedAustin 2:e84c13abc479 24 GattCharacteristic *characteristics[] = {&readChar, &writeChar};
mbedAustin 2:e84c13abc479 25
mbedAustin 2:e84c13abc479 26 // Set up custom service
mbedAustin 2:e84c13abc479 27 GattService customService(0x221D /*Service UUID*/, characteristics, sizeof(characteristics) / sizeof(GattCharacteristic *));
mbedAustin 2:e84c13abc479 28
mbedAustin 2:e84c13abc479 29
mbedAustin 1:94152e7d8b5c 30 // Restart advertising when phone app disconnects
mbedAustin 1:94152e7d8b5c 31 void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason)
mbedAustin 1:94152e7d8b5c 32 {
mbedAustin 1:94152e7d8b5c 33 ble.startAdvertising(); // restart advertising
mbedAustin 1:94152e7d8b5c 34 }
mbedAustin 0:cd5b6733aeb1 35
mbedAustin 3:0fb60f81f693 36 // This function is called whenever someone writes something to the writeCharacteristic
mbedAustin 4:7ef90665b399 37 void writeCharCallback(const GattCharacteristicWriteCBParams *params)
mbedAustin 3:0fb60f81f693 38 {
mbedAustin 3:0fb60f81f693 39 //TODO: when character is written here change the LED, update the read characteristic, and print out to console
mbedAustin 5:d0548c64e2e7 40 led = params->data[0];
mbedAustin 5:d0548c64e2e7 41 printf("LED Written To, value=%x",params->data[0]);
mbedAustin 3:0fb60f81f693 42 }
mbedAustin 0:cd5b6733aeb1 43
mbedAustin 0:cd5b6733aeb1 44 int
mbedAustin 0:cd5b6733aeb1 45 main(void)
mbedAustin 0:cd5b6733aeb1 46 {
mbedAustin 1:94152e7d8b5c 47 led = 0; // turn LED off
mbedAustin 2:e84c13abc479 48 ble.init();
mbedAustin 2:e84c13abc479 49 ble.onDisconnection(disconnectionCallback);
mbedAustin 4:7ef90665b399 50 ble.onDataWritten(writeCharCallback); //TODO: this is not correct, figure out correct syntax
mbedAustin 2:e84c13abc479 51
mbedAustin 2:e84c13abc479 52 /* setup advertising */
mbedAustin 2:e84c13abc479 53 ble.accumulateAdvertisingPayload(GapAdvertisingData::BREDR_NOT_SUPPORTED);
mbedAustin 2:e84c13abc479 54 ble.setAdvertisingType(GapAdvertisingParams::ADV_CONNECTABLE_UNDIRECTED);
mbedAustin 2:e84c13abc479 55 ble.setAdvertisingInterval(160); /* 100ms; in multiples of 0.625ms. */
mbedAustin 2:e84c13abc479 56 ble.startAdvertising(); // start advertising
mbedAustin 2:e84c13abc479 57
mbedAustin 2:e84c13abc479 58 ble.addService(customService); // Add our custom service to device
mbedAustin 2:e84c13abc479 59
mbedAustin 2:e84c13abc479 60 while (true) {
mbedAustin 2:e84c13abc479 61 ble.waitForEvent(); //Save power
mbedAustin 2:e84c13abc479 62 }
mbedAustin 2:e84c13abc479 63
mbedAustin 1:94152e7d8b5c 64
mbedAustin 1:94152e7d8b5c 65 // TODO: impliment the rest of triggering for LED based on Write of characteristic.
mbedAustin 1:94152e7d8b5c 66 // TODO: impliment a read characteristic that sends text back to app
mbedAustin 1:94152e7d8b5c 67 // take a look at http://developer.mbed.org/teams/Bluetooth-Low-Energy/code/BLE_GroveColourSensor/file/000c8f8c7f03/main.cpp for inspiration.
mbedAustin 0:cd5b6733aeb1 68 }