You must develop a custom application to read and accept the data from an IoT device.\u00a0 This code includes the hooks or handles. Your specific approach including desired programming language and related software for this process varies widely based on your application, hardware and software systems.\u00a0 See Application Development<\/a> for more information.<\/p>\n For mLinux\u2122<\/sup>, one option is to write a C\/C++ application and use the BlueZ driver already provided on the device.\u00a0 Other options include writing a Python application and using the python gattlib<\/b> library.<\/p>\n NOTE:<\/strong>\u00a0For mLinux 3.x only, BLE does not work with Bluez 5<\/strong> on a PC in compatibility mode<\/strong>. \u00a0You must use Bluez 4<\/strong>.<\/p>\n BLE Setup and Start<\/b><\/p>\n 1. Make sure the RS9113 is started with a BLE compatible mode of: 8, 9, 12, or 14<\/b>. For this example, the choice is 14<\/b>. If you reboot the system, verify that \/etc\/default\/rs9113 still contains the correct value. NOTE<\/strong>: Once a WiFi connection is established, you cannot scan. Push the black plastic flap as seen here:<\/p>\n Photo of the Texas Instruments Sensortag CC2650 used in this BLE example.<\/i><\/p>\n For mLinux 4.x or higher<\/strong>, after step 1, follow these steps:<\/p>\n 2.Edit \/etc\/default\/bluetoothd<\/strong> and set BLUETOOTH_ENABLED=1<\/strong><\/p>\n 3.Start the bluetooth daemon:<\/p>\n To stop the bluetooth daemon (don’t do this if you wish to proceed on testing this):<\/p>\n 4.\u00a0Now use bluetoothctl<\/strong> to find the BLE device.<\/p>\n If the BLE device is advertising, you should soon see:<\/p>\n For mLinux 3.x<\/strong>, after step 1, follow these steps:<\/p>\n 2. Put the BLE device in discoverable mode. The green led starts to blink. \u00a0 \u00a0 The resulting output displays:<\/p>\n 4. Type <Ctrl-C> to end the scan.<\/p>\n Bring BLE up<\/b><\/p>\n To bring BLE up, enter the following command:<\/p>\n Bring BLE down BLE Reset<\/b><\/p>\n BLE resets automatically upon reboot.<\/p>\n Connect to the Sensor<\/b><\/p>\n Now you that you know the address of the BLE device (See BLE Setup and Start<\/b>), you can connect.<\/p>\n 1. To connect to the sensor, enter the following commands:<\/p>\n \u00a0<\/span><\/p>\n <\/p>\n 2. Once you connect, the blinking led stops. Enter the following command:\u00a0<\/span><\/p>\n \u00a0The resulting output displays:\u00a0<\/span><\/p>\n 3. To get a list of details of characteristics, use the char-desc<\/strong> command. When using this command , it displays the handle they are at and their UUID:\u00a0\u00a0\u00a0<\/span><\/p>\n The resulting output displays:<\/p>\n 4. To read the characteristics that are located at certain handle(s), enter the following command:<\/p>\n \u00a0<\/span><\/p>\n 5. You can also write characteristics that are located at certain handle(s): The first write command wakes up (activates) the humidity sensor on 01. The second write command puts the sensor to sleep on 00. The read commands is to simply confirm that the change happened.<\/p>\n \u00a0<\/span><\/p>\n 6. Enter the following commands to disconnect and exit. The green LED on the sensor starts blinking again:<\/p>\n \u00a0<\/span><\/p>\n 7. To save energy, turn off the sensor and the green light stops blinking.<\/p>\n For mLinux 5.x This example only applies to mLinux 5.<\/p>\n GATT servers are typically sensors that transmit data to clients using Bluetooth Low Energy.\u00a0 In mLinux 5, it is possible to write a GATT service that sends data collected by the device to a remote GATT client. There are many standard GATT services defined.\u00a0 Here is a list:\u00a0 https:\/\/www.bluetooth.com\/specifications\/gatt\/services<\/a><\/p>\n The sample server is only provided as a learning tool to demonstrate how to write a GATT server. Most GATT servers will need to read real sensors, most likely attached to the device.<\/p>\n https:\/\/github.com\/Jumperr-labs\/python-gatt-server<\/a><\/p>\n![\"\"](\"https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2017\/01\/cc2650-sensor-w-labels.jpg\")
<\/p>\nsudo \/etc\/init.d\/bluetooth start<\/pre>\n
sudo \/etc\/init.d\/bluetooth stop<\/pre>\n
sudo bluetoothctl\r\n[bluetooth]# power on\r\nChanging power on succeeded\r\n[bluetooth]# scan on\r\nDiscovery started\r\n[CHG] Controller 00:23:A7:EA:2E:D3 Discovering: yes<\/pre>\n
[NEW] Device B0:B4:48:C0:B0:82 CC2650 SensorTag<\/pre>\n
\n3. Enter the following commands:<\/p>\nmtcdt: hciconfig hci0 up\r\nmtcdt: hcitool -i hci0 lescan<\/pre>\n
#LE Scan ...\r\nB0:B4:48:C0:B0:82 (unknown)\r\nB0:B4:48:C0:B0:82 CC2650 SensorTag\r\n^C<\/pre>\n
mtcdt: hciconfig hci0 up<\/pre>\n
\n<\/b>
\nTo bring BLE down, enter the following command:<\/p>\nmtcdt: hciconfig hci0 down<\/pre>\n
mtcdt: gatttool -i hci0\u00a0 -b B0:B4:48:C0:B0:82 --interactive\r\n[ \u00a0 \u00a0 \u00a0 \u00a0 ][B0:B4:48:C0:B0:82][LE]> connect<\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]> primary<\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]>\r\nattr handle: 0x0001, end grp handle: 0x0007 uuid: 00001800-0000-1000-8000-00805f9b34fb\r\nattr handle: 0x0008, end grp handle: 0x000b uuid: 00001801-0000-1000-8000-00805f9b34fb\r\nattr handle: 0x000c, end grp handle: 0x001e uuid: 0000180a-0000-1000-8000-00805f9b34fb\r\nattr handle: 0x001f, end grp handle: 0x0026 uuid: f000aa00-0451-4000-b000-000000000000\r\nattr handle: 0x0027, end grp handle: 0x002e uuid: f000aa20-0451-4000-b000-000000000000\r\nattr handle: 0x002f, end grp handle: 0x0036 uuid: f000aa40-0451-4000-b000-000000000000\r\nattr handle: 0x0037, end grp handle: 0x003e uuid: f000aa80-0451-4000-b000-000000000000\r\nattr handle: 0x003f, end grp handle: 0x0046 uuid: f000aa70-0451-4000-b000-000000000000\r\nattr handle: 0x0047, end grp handle: 0x004b uuid: 0000ffe0-0000-1000-8000-00805f9b34fb\r\nattr handle: 0x004c, end grp handle: 0x0050 uuid: f000aa64-0451-4000-b000-000000000000\r\nattr handle: 0x0051, end grp handle: 0x0058 uuid: f000ac00-0451-4000-b000-000000000000\r\nattr handle: 0x0059, end grp handle: 0x0060 uuid: f000ccc0-0451-4000-b000-000000000000\r\nattr handle: 0x0061, end grp handle: 0xffff uuid: f000ffc0-0451-4000-b000-000000000000<\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]> char-desc<\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]>\r\nhandle: 0x0001, uuid: 00002800-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0002, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0003, uuid: 00002a00-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0004, uuid: 00002803-0000-1000-8000-00805f9b34fb\r\nhandle: 0x0005, uuid: 00002a01-0000-1000-8000-00805f9b34fb\r\n\r\n...\r\n\r\nhandle: 0x002f, uuid: f000aa22-0451-4000-b000-000000000000\r\n...<\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]> char-read-hnd 0x0001\r\n[CON][B0:B4:48:C0:B0:82][LE]>\r\nCharacteristic value\/descriptor: 00 18\r\n[CON][B0:B4:48:C0:B0:82][LE]> char-read-hnd 0x0002\r\n[CON][B0:B4:48:C0:B0:82][LE]>\r\nCharacteristic value\/descriptor: 02 03 00 00 2a<\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]> char-write-cmd 0x2f 01\r\n[CON][B0:B4:48:C0:B0:82][LE]> char-read-hnd 0x2f\r\n[CON][B0:B4:48:C0:B0:82][LE]>\r\nCharacteristic value\/descriptor: 01\r\n[CON][B0:B4:48:C0:B0:82][LE]> char-write-cmd 0x2f 00\r\n[CON][B0:B4:48:C0:B0:82][LE]> char-read-hnd 0x2f\r\n[CON][B0:B4:48:C0:B0:82][LE]>\r\nCharacteristic value\/descriptor: 00\r\n[CON][B0:B4:48:C0:B0:82][LE]><\/pre>\n
[CON][B0:B4:48:C0:B0:82][LE]> disconnect\r\n[\u00a0\u00a0 ][B0:B4:48:C0:B0:82][LE]> exit\r\nmtcdt:<\/pre>\n
\nUse the device as a server (not yet supported in mLinux 4.x)<\/b><\/h3>\n
\n<\/strong><\/p>\nExample GATT Server<\/h4>\n
Prerequisites for the GATT Sample Server<\/h4>\n