customer Long story made short… we got the kit working and spent time with it over the last 2~3 weeks. Using BTool, I got everything working except the accelerometer always gives 00. I understand that FW may not be final at the moment. However one of our prospective vendors mentioned that “The latest firmware in TI 2540 also has proximity profile. “After the dongle is paired with TI 2540, it indeed does not show up proximity profile.However, you can use it. “I will ask our engineering staff to capture the Windows frames and show you how to use the proximity profile on Friday…” While I wait for his engineers’ instruction, can you point me to the appropriate/latest FW for the fob in the dev kit? We have tried the HEX files in BLE-CC2540 & BLE-CC2540-1.1. The fob shows up as ‘Bluetooth Peripheral Device’, ‘Device Info’ & ‘TI FFE0’. The HEX file, cc2540_ble1.0_slave_keyfobdemo.hex, gives us Immediate Alert, Link Loss, TxPower as well as ‘TI FFC1’ & ‘TI FFC2’.
Long story made short… we got the kit working and spent time with it over the last 2~3 weeks. Using BTool, I got everything working except the accelerometer always gives 00. I understand that FW may not be final at the moment. However one of our prospective vendors mentioned that
“The latest firmware in TI 2540 also has proximity profile. “After the dongle is paired with TI 2540, it indeed does not show up proximity profile.However, you can use it. “I will ask our engineering staff to capture the Windows frames and show you how to use the proximity profile on Friday…”
While I wait for his engineers’ instruction, can you point me to the appropriate/latest FW for the fob in the dev kit?
We have tried the HEX files in BLE-CC2540 & BLE-CC2540-1.1. The fob shows up as ‘Bluetooth Peripheral Device’, ‘Device Info’ & ‘TI FFE0’. The HEX file, cc2540_ble1.0_slave_keyfobdemo.hex, gives us Immediate Alert, Link Loss, TxPower as well as ‘TI FFC1’ & ‘TI FFC2’.
This is the latest to date.
Unfortunately the serivce, "Alert me about changes to this product," on the product page for BLE-STACK does not work. In order to stay up to date, you will need to check back periodically to see if they have increased the revision of the download file. (At the moment the current file name is swrc207b.zip so the next revision would be swrc207c.zip.)
customer I got everything working except the accelerometer always gives 00.
I got everything working except the accelerometer always gives 00.
The accelerometer works on my CC2540DK-MINI. Let's find out what is different between your setup and mine. Here's what I did.
I wanted to know what the GATT_CLIENT_CHAR_CFG_UUID is for each axis of the accelerometer in the KeyFobDemo (project KeyFobDemo.eww) from BLE-STACK v1.1 (swrc207b.zip)
I wanted to configure the accelerometer on the CC2540DK-MINI to send notifications as described in, "Texas Instruments CC2540 Bluetooth® Low Energy Sample Applications Guide v1.1a," Document Number: SWRU297A (page 16 of 25).
When I read the characteristic descriptors from the following characteristic value handles, this is what I read:
Handle Value Description / D e s c r i p t o r---------------------------------------------------------0x0000 0x0001 0x0002 0x0003 C C 2 5 4 0 D K - m i n i K e y f o b0x0004 0x0005 0x0006 0x0007 0x0008 0x0009 0x000A 0x000B 0x000C 0x000D 0x000E 0x000F 0x0010 0x0011 0x0012 0x0013 M o d e l N u m b e r 0x0014 0x0015 S e r i a l N u m b e r 0x0016 0x0017 F i r m w a r e R e v i s i o n 0x0018 0x0019 H a r d w a r e R e v i s i o n 0x001A 0x001B S o f t w a r e R e v i s i o n 0x001C 0x001D M a n u f a c t u r e r N a m e 0x001E 0x001F 0x0020 0x0021 0x0022 PROXIMITY_ALERT_LEVEL_UUID for link loss alert level0x0023 0x0024 0x0025 0x0026 0x0027 0x0028 0x0029 0x002A 0x002B 0x002C 0x002D B a t t e r y L e v e l0x002E 0x002F 0x0030 B a t t e r y S t a t e0x0031 0x0032 0x0033 GATT_CLIENT_CHAR_CFG_UUID for Accel Enable0x0034 A c c e l E n a b l e0x0035 0x0036 0x0037 A c c e l R a n g e0x0038 0x0039 0x003A GATT_CLIENT_CHAR_CFG_UUID for Accel X-Coordinate0x003B A c c e l X - C o o r d i n a t e0x003C 0x003D 0x003E GATT_CLIENT_CHAR_CFG_UUID for Accel Y-Coordinate0x003F A c c e l Y - C o o r d i n a t e0x0040 0x0041 0x0042 GATT_CLIENT_CHAR_CFG_UUID for Accel Z-Coordinate0x0043 A c c e l Z - C o o r d i n a t e0x0044 0x0045 0x0046 0x0047 0x0048 K e y P r e s s S t a t e0x0049 0x004A 0x004B 0x004C 0x004D 0x004E 0x004F 0x0050 0x0051 0x0052 0x0053 0x0054 0x0055 0x0056 0x0057 0x0058 0x0059 0x005A 0x005B 0x005C 0x005D 0x005E 0x005F 0x0060 ---------------------------------------------------------
I wrote, "01 00," to the characteristic value handle, "0x003A," in an attempt to configure the Accel X-Coordinate to send notifications. This would be analogous to how it is described in the KeyFobDemo for BLE-STACK v1.0. The result was, "Success."
I wrote, "01," to the characteristic value handle, "0x0033," to enable the Accelerometer (Accel Enable).
Now when I move the key fob, I can see the notifications using BTool v1.10a
I repeated the equivalent procedure for the Y-axis and Z-axis.
customer “The latest firmware in TI 2540 also has proximity profile. “After the dongle is paired with TI 2540, it indeed does not show up proximity profile.However, you can use it. “I will ask our engineering staff to capture the Windows frames and show you how to use the proximity profile on Friday…”
The link loss service of the proximity profile works on my CC2540DK-MINI. Here's what I did.
I wanted to know what the PROXIMITY_ALERT_LEVEL_UUID is for link loss alert level in the KeyFobDemo (project KeyFobDemo.eww) from BLE-STACK v1.1 (swrc207b.zip) After learning that the default value for PROXIMITY_ALERT_LEVEL_UUID is, "00," I read the characteristic values from 0x0000 to 0x0060. At characteristic value handle 0x0022 the value is, "00," and this happens to be the PROXIMITY_ALERT_LEVEL_UUID.
I wanted to configure the keyfob from the CC2540DK-MINI to alarm when the link drops as described in, "Texas Instruments CC2540 Bluetooth® Low Energy Sample Applications Guide v1.1a," Document Number: SWRU297A (page 16 of 25 section 8.1.5). I observed this by writing ,"01," or, "02," to characteristic value handle 0x0022.
customer Now I have this (attached image). What is the difference between 'Link Loss' and 'TI Link Loss'? What is 'TI FFE0'?
Now I have this (attached image). What is the difference between 'Link Loss' and 'TI Link Loss'? What is 'TI FFE0'?
I just started playing with the KeyFobDemo application (BLE stack 1.2) . I seem to discover the fob OK and establish a link through the USB key.
At this point I'd like to test the GATT services as per SWRU297:
Device info
Link loss
Battery
Accelerometer
Simple keys.
Not quite sure as how to do that as I do not know what the Characteristic handle/ Characteristic UUID pairs for each service.
What are the steps that led you to displaying the values above?
Your response would be greatly appreciated.
The battery level UUID is 0x2A19. Not sure about the others. I'm not sure why the documentation on the wiki is wrong -- it needs to be updated.
I can't get proximity alerts to work. Btool responds with "WRITE_NOT_PERMITTED" for characteristic value handles 0x0011 (the demo says to use this value) and ox0022 (another thread says to use this value). My C:\Texas Instruments\BLE-CC254x-1.2\Projects\ble\Profiles\Proximity\proxreporter.h says #define LINK_LOSS_SERVICE_UUID 0x1803. It responds with "INVALID HANDLE" when I use 0x1803. Anybody got any other ideas?
0x1803 is the Characteristic UUID not the Handle , Handles can be obtained by Discover UUID characteristic in BTOOL
try setting 0025 lot value 02 to get the beep working
Jason Work customer Now I have this (attached image). What is the difference between 'Link Loss' and 'TI Link Loss'? What is 'TI FFE0'?
Hello,
How did you get these screens? I am not able to connect to KeyFob using USB dongle through Windows Bluetooth discovery though it works fine through BTool.
Thanks,
Ariel