mbed application to pair with Evothings App, demonstrates how to create a custom GAP advertising packet.
Dependencies: BLE_API mbed nRF51822
Intro
This code is meant to demonstrate how to use the GAP advertising layer to transmit data. Keep in mind you only have 26B of data in the Manufacturer data field to use.
Details
Fill in the data you want to transmit by changing the following line
/** You have up to 26 bytes of advertising data to use. Make up your own encoding for these 26bytes, send it across and decode it using the evothings app. */ const static uint8_t AdvData[] = {"ChangeThisData"}; // example of character data //const static uint8_t AdvData[] = {0x01,0x02,0x03,0x04,0x05}; // example of hex data
Name Device
Optionally you can give your device a name by uncommenting the following two lines
//const static char DEVICE_NAME[] = "ChangeMe!!"; // change this ... //ble.accumulateAdvertisingPayload(GapAdvertisingData::COMPLETE_LOCAL_NAME, (uint8_t *)DEVICE_NAME, sizeof(DEVICE_NAME));
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 Evothings App to view the data.
Add Disconnection Callback
This code is bare bones and as such does not restart advertising when disconnected from a device. To add this functionality into your code please add the following callback
// Restart advertising when phone app disconnects void disconnectionCallback(Gap::Handle_t handle, Gap::DisconnectionReason_t reason) { ble.startAdvertising(); }
and the following initialization to your main function
int main(void) { ... ble.onDisconnection(disconnectionCallback); ...
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. Then grab the code from the github page, drag and drop the index.htm file into Evothings workbench and run it on the Evothings client.
Reference
History
hotfix for changed API
2015-04-02, by mbedAustin [Thu, 02 Apr 2015 20:26:52 +0000] rev 12
hotfix for changed API
updated the libraries
2015-04-02, by mbedAustin [Thu, 02 Apr 2015 17:19:16 +0000] rev 11
updated the libraries
updated library that was causing a conflict
2015-03-18, by mbedAustin [Wed, 18 Mar 2015 21:02:22 +0000] rev 10
updated library that was causing a conflict
updated library revisions
2015-03-18, by mbedAustin [Wed, 18 Mar 2015 20:09:36 +0000] rev 9
updated library revisions
Added comments and disconnection callback option
2015-03-17, by mbedAustin [Tue, 17 Mar 2015 19:45:19 +0000] rev 8
Added comments and disconnection callback option
changed default advertising data as most phones display it in hex, not ascii
2015-03-10, by mbedAustin [Tue, 10 Mar 2015 22:42:14 +0000] rev 7
changed default advertising data as most phones display it in hex, not ascii
final commit
2015-03-10, by mbedAustin [Tue, 10 Mar 2015 21:52:58 +0000] rev 6
final commit
Added name service to make device easier to find in crowded room
2015-03-10, by mbedAustin [Tue, 10 Mar 2015 20:58:12 +0000] rev 5
Added name service to make device easier to find in crowded room
made device connectable instead of non-connectable, this is to allow iOS devices to connect and display the advertising info, because no iOS app will just show the advertising data, they have to connect... grrr....
2015-03-10, by mbedAustin [Tue, 10 Mar 2015 20:32:37 +0000] rev 4
made device connectable instead of non-connectable, this is to allow iOS devices to connect and display the advertising info, because no iOS app will just show the advertising data, they have to connect... grrr....
Publishing for use in Meetup;
2015-03-10, by mbedAustin [Tue, 10 Mar 2015 20:06:05 +0000] rev 3
Publishing for use in Meetup;