CC2540 Data Throughput
This is example modification of CC2540 SimpleBLEPeripheral application to measure user data throughput. Initial testing shows we can reach 5.9K bytes per second. This is using a 10ms connection interval and 20 user data bytes sent in GATT notifications. 4 notifications are sent every 7ms, based on an OSAL timer. When sending the notifications, a check is made to see if a buffer is available. In all, 1000 notifications are sent. This is 20K bytes, which are sent over 3.35 seconds. __(from TI)
http://processors.wiki.ti.com/index.php/CC2540_Data_Throughput
In real case, it's not possible use 10 ms interval to transmit data, need to consider the UART interface.
My experience is about 40~ 60 ms and not including actual payload without header, checksum, packet bytes, etc.
https://learn.sparkfun.com/tutorials/bluetooth-basics
Other compare table is quite interesting from sparkfun.com.
| Name | Bluetooth Classic | Bluetooth 4.0 Low Energy (BLE) | ZigBee | WiFi |
|---|---|---|---|---|
| IEEE Standard | 802.15.1 | 802.15.1 | 802.15.4 | 802.11 (a, b, g, n) |
| Frequency (GHz) | 2.4 | 2.4 | 0.868, 0.915, 2.4 | 2.4 and 5 |
| Maximum raw bit rate (Mbps) | 1-3 | 1 | 0.250 | 11 (b), 54 (g), 600 (n) |
| Typical data throughput (Mbps) | 0.7-2.1 | 0.27 (TI package throughtput) | 0.2 | 7 (b), 25 (g), 150 (n) |
| Maximum (Outdoor) Range (Meters) | 10 (class 2), 100 (class 1) | 50 | 10-100 | 100-250 |
| Relative Power Consumption | Medium | Very low | Very low | High |
| Example Battery Life | Days | Months to years | Months to years | Hours |
| Network Size | 7 | Undefined | 64,000+ | 255 |
沒有留言:
張貼留言