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:
Mon Mar 09 19:21:06 2015 +0000
Revision:
9:b33f42191584
Parent:
8:60ede963dfe2
Child:
10:6acaa9f0ef85
Final Publishable version;

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 BLEDevice ble;
mbedAustin 1:94152e7d8b5c 6 DigitalOut led(LED1);
mbedAustin 9:b33f42191584 7 uint16_t customServiceUUID = 0xA000;
mbedAustin 9:b33f42191584 8 uint16_t reachCharUUID = 0xA001;
mbedAustin 9:b33f42191584 9 uint16_t writeCharUUID = 0xA002;
mbedAustin 1:94152e7d8b5c 10
mbedAustin 7:f6814152873c 11 const static char DEVICE_NAME[] = "ChangeMe!!"; // change this
mbedAustin 8:60ede963dfe2 12 static const uint16_t uuid16_list[] = {0xFFFF}; //Custom UUID, FFFF is reserved for development
mbedAustin 1:94152e7d8b5c 13
mbedAustin 2:e84c13abc479 14 // Set Up Characteristics
mbedAustin 9:b33f42191584 15 static uint8_t readValue[10] = {0};
mbedAustin 9:b33f42191584 16 GattCharacteristic readChar(reachCharUUID, readValue, sizeof(readValue), sizeof(readValue),
mbedAustin 8:60ede963dfe2 17 GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_READ | GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_NOTIFY);
mbedAustin 2:e84c13abc479 18
mbedAustin 9:b33f42191584 19 static uint8_t writeValue[10] = {0};
mbedAustin 9:b33f42191584 20 GattCharacteristic writeChar(writeCharUUID, writeValue, sizeof(writeValue), sizeof(writeValue),
mbedAustin 8:60ede963dfe2 21 GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_WRITE | GattCharacteristic::BLE_GATT_CHAR_PROPERTIES_NOTIFY);
mbedAustin 2:e84c13abc479 22
mbedAustin 2:e84c13abc479 23 // Set up custom service
mbedAustin 8:60ede963dfe2 24 GattCharacteristic *characteristics[] = {&readChar, &writeChar};
mbedAustin 9:b33f42191584 25 GattService customService(customServiceUUID, characteristics, sizeof(characteristics) / sizeof(GattCharacteristic *));
mbedAustin 2:e84c13abc479 26
mbedAustin 2:e84c13abc479 27
mbedAustin 8:60ede963dfe2 28 /*
mbedAustin 8:60ede963dfe2 29 * Restart advertising when phone app disconnects
mbedAustin 8:60ede963dfe2 30 */
mbedAustin 1:94152e7d8b5c 31 void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason)
mbedAustin 1:94152e7d8b5c 32 {
mbedAustin 8:60ede963dfe2 33 ble.startAdvertising();
mbedAustin 1:94152e7d8b5c 34 }
mbedAustin 0:cd5b6733aeb1 35
mbedAustin 8:60ede963dfe2 36 /*
mbedAustin 8:60ede963dfe2 37 * handle writes to writeCharacteristic
mbedAustin 8:60ede963dfe2 38 */
mbedAustin 4:7ef90665b399 39 void writeCharCallback(const GattCharacteristicWriteCBParams *params)
mbedAustin 3:0fb60f81f693 40 {
mbedAustin 8:60ede963dfe2 41 // check to see what characteristic was written, by handle
mbedAustin 8:60ede963dfe2 42 if(params->charHandle == writeChar.getValueHandle()) {
mbedAustin 8:60ede963dfe2 43 // toggle LED if only 1 byte is written
mbedAustin 8:60ede963dfe2 44 if(params->len == 1) {
mbedAustin 8:60ede963dfe2 45 led = params->data[0];
mbedAustin 8:60ede963dfe2 46 }
mbedAustin 8:60ede963dfe2 47 // print the data if more than 1 byte is written
mbedAustin 8:60ede963dfe2 48 else {
mbedAustin 8:60ede963dfe2 49 for(int x=0; x < params->len; x++) {
mbedAustin 8:60ede963dfe2 50 printf("%x",params->data[x]);
mbedAustin 8:60ede963dfe2 51 }
mbedAustin 8:60ede963dfe2 52 printf("\n\r"); // print newline
mbedAustin 8:60ede963dfe2 53 }
mbedAustin 8:60ede963dfe2 54 // update the readChar with the value of writeChar
mbedAustin 8:60ede963dfe2 55 ble.updateCharacteristicValue(readChar.getValueHandle(),params->data,params->len);
mbedAustin 8:60ede963dfe2 56 }
mbedAustin 3:0fb60f81f693 57 }
mbedAustin 0:cd5b6733aeb1 58
mbedAustin 8:60ede963dfe2 59 /*
mbedAustin 8:60ede963dfe2 60 * main loop
mbedAustin 8:60ede963dfe2 61 */
mbedAustin 0:cd5b6733aeb1 62 int
mbedAustin 0:cd5b6733aeb1 63 main(void)
mbedAustin 0:cd5b6733aeb1 64 {
mbedAustin 8:60ede963dfe2 65 /* initialize stuff */
mbedAustin 8:60ede963dfe2 66 printf("\n\r********* Starting Main Loop *********\n\r");
mbedAustin 8:60ede963dfe2 67 led = 1; // turn LED off (led is inverted)
mbedAustin 2:e84c13abc479 68 ble.init();
mbedAustin 2:e84c13abc479 69 ble.onDisconnection(disconnectionCallback);
mbedAustin 4:7ef90665b399 70 ble.onDataWritten(writeCharCallback); //TODO: this is not correct, figure out correct syntax
mbedAustin 2:e84c13abc479 71
mbedAustin 2:e84c13abc479 72 /* setup advertising */
mbedAustin 7:f6814152873c 73 ble.accumulateAdvertisingPayload(GapAdvertisingData::BREDR_NOT_SUPPORTED | GapAdvertisingData::LE_GENERAL_DISCOVERABLE); // BLE only, no classic BT
mbedAustin 7:f6814152873c 74 ble.setAdvertisingType(GapAdvertisingParams::ADV_CONNECTABLE_UNDIRECTED); // advertising type
mbedAustin 7:f6814152873c 75 ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LOCAL_NAME, (uint8_t *)DEVICE_NAME, sizeof(DEVICE_NAME)); // add name
mbedAustin 7:f6814152873c 76 ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LIST_16BIT_SERVICE_IDS, (uint8_t *)uuid16_list, sizeof(uuid16_list)); // UUID's broadcast in advertising packet
mbedAustin 2:e84c13abc479 77 ble.setAdvertisingInterval(160); /* 100ms; in multiples of 0.625ms. */
mbedAustin 2:e84c13abc479 78
mbedAustin 8:60ede963dfe2 79 // add our custom service
mbedAustin 2:e84c13abc479 80 ble.addService(customService); // Add our custom service to device
mbedAustin 2:e84c13abc479 81
mbedAustin 7:f6814152873c 82 ble.startAdvertising(); // start advertising
mbedAustin 9:b33f42191584 83
mbedAustin 9:b33f42191584 84 // infinite loop waiting for BLE interrupt events
mbedAustin 2:e84c13abc479 85 while (true) {
mbedAustin 2:e84c13abc479 86 ble.waitForEvent(); //Save power
mbedAustin 2:e84c13abc479 87 }
mbedAustin 8:60ede963dfe2 88 }