Hello, I am new to TI & BLE Has anyone figured out how to set the Proximity Profile to work? I have read and tried to follow the Wiki (http://processors.wiki.ti.com/index.php/Category:KeyFobDemo) but have not been able to set ON the proximity profile. I know that the UUIDs have changed since the example and current proxreport.h have the following UUID, for which I have tried but was not able to turn on... Can someone shed some lights on this. I am probably missing something simple (which is always the case for me :)). // Proximity Profile Service UUIDs #define LINK_LOSS_SERVICE_UUID 0x1803 #define IMMEDIATE_ALERT_SERVICE_UUID 0x1802 #define TX_PWR_LEVEL_SERVICE_UUID 0x1804 // Proximity Profile Attribute UUIDs #define PROXIMITY_ALERT_LEVEL_UUID 0x2A06 #define PROXIMITY_TX_PWR_LEVEL_UUID 0x2A07 When I try to write "Characteristic Value Handle" for above UUIDs I get INVALID_HANDLE. I was able to write 01 to 0x2A06. Any help is appreciated and thanks in advance. Laith
Hi,
there is some info for you here:
http://e2e.ti.com/support/low_power_rf/f/538/t/134385.aspx
Please let us know. It is fairly easy to set up the proximity profile.
IMPORTANT NOTE: the USB has to be flashed with the HostTestRelease firmware AND the keyfob with the KEYFOB firmware. I'm not sure if the SimpleBLEPeripheral includes proximity features. Flash the keyfob with the KeyFob firmware.
Please click the Verify Answer button on a post if it answers your question! :)
Kazola, thanks for your reply.
I did try out the link you sent out. but that does not explain this though...in the code we have the following
// Proximity Profile Service UUIDs #define LINK_LOSS_SERVICE_UUID 0x1803 #define IMMEDIATE_ALERT_SERVICE_UUID 0x1802 #define TX_PWR_LEVEL_SERVICE_UUID 0x1804
but when I try to "Discover Characteristic by UUID" using the UUID 0x1802 to 0x1804 i get all the following which is not making sense.
0x1802
[1] : <Tx> - 12:16:56.259-Type : 0x01 (Command)-Opcode : 0xFD88 (GATT_DiscCharsByUUID)-Data Length : 0x08 (8) byte(s) ConnHandle : 0x0000 (0) StartHandle : 0x0001 (1) EndHandle : 0xFFFF (65535) Type : 02:18Dump(Tx):01 88 FD 08 00 00 01 00 FF FF 02 18 ------------------------------------------------------------------------------------------------------------------------[2] : <Rx> - 12:16:56.329-Type : 0x04 (Event)-EventCode : 0xFF (HCI_LE_ExtEvent)-Data Length : 0x06 (6) bytes(s) Event : 0x067F (GAP_HCI_ExtentionCommandStatus) Status : 0x00 (Success) OpCode : 0xFD88 (GATT_DiscCharsByUUID) DataLength : 0x00 (0)Dump(Rx):04 FF 06 7F 06 00 88 FD 00 ------------------------------------------------------------------------------------------------------------------------[3] : <Rx> - 12:16:58.281-Type : 0x04 (Event)-EventCode : 0xFF (HCI_LE_ExtEvent)-Data Length : 0x06 (6) bytes(s) Event : 0x0509 (ATT_ReadByTypeRsp) Status : 0x1A (The Procedure Is Completed) ConnHandle : 0x0000 (0) PduLen : 0x00 (0)Dump(Rx):04 FF 06 09 05 1A 00 00 00 ------------------------------------------------------------------------------------------------------------------------
0x1803-------------------------------------------------------------------
[1] : <Tx> - 12:17:26.324-Type : 0x01 (Command)-Opcode : 0xFD88 (GATT_DiscCharsByUUID)-Data Length : 0x08 (8) byte(s) ConnHandle : 0x0000 (0) StartHandle : 0x0001 (1) EndHandle : 0xFFFF (65535) Type : 03:18Dump(Tx):01 88 FD 08 00 00 01 00 FF FF 03 18 ------------------------------------------------------------------------------------------------------------------------[2] : <Rx> - 12:17:26.433-Type : 0x04 (Event)-EventCode : 0xFF (HCI_LE_ExtEvent)-Data Length : 0x06 (6) bytes(s) Event : 0x067F (GAP_HCI_ExtentionCommandStatus) Status : 0x00 (Success) OpCode : 0xFD88 (GATT_DiscCharsByUUID) DataLength : 0x00 (0)Dump(Rx):04 FF 06 7F 06 00 88 FD 00 ------------------------------------------------------------------------------------------------------------------------[3] : <Rx> - 12:17:28.430-Type : 0x04 (Event)-EventCode : 0xFF (HCI_LE_ExtEvent)-Data Length : 0x06 (6) bytes(s) Event : 0x0509 (ATT_ReadByTypeRsp) Status : 0x1A (The Procedure Is Completed) ConnHandle : 0x0000 (0) PduLen : 0x00 (0)Dump(Rx):04 FF 06 09 05 1A 00 00 00
-------------------------------------------------------------------0x1804-------------------------------------------------------------------
[1] : <Tx> - 12:17:50.370-Type : 0x01 (Command)-Opcode : 0xFD88 (GATT_DiscCharsByUUID)-Data Length : 0x08 (8) byte(s) ConnHandle : 0x0000 (0) StartHandle : 0x0001 (1) EndHandle : 0xFFFF (65535) Type : 04:18Dump(Tx):01 88 FD 08 00 00 01 00 FF FF 04 18 ------------------------------------------------------------------------------------------------------------------------[2] : <Rx> - 12:17:50.479-Type : 0x04 (Event)-EventCode : 0xFF (HCI_LE_ExtEvent)-Data Length : 0x06 (6) bytes(s) Event : 0x067F (GAP_HCI_ExtentionCommandStatus) Status : 0x00 (Success) OpCode : 0xFD88 (GATT_DiscCharsByUUID) DataLength : 0x00 (0)Dump(Rx):04 FF 06 7F 06 00 88 FD 00 ------------------------------------------------------------------------------------------------------------------------[3] : <Rx> - 12:17:52.445-Type : 0x04 (Event)-EventCode : 0xFF (HCI_LE_ExtEvent)-Data Length : 0x06 (6) bytes(s) Event : 0x0509 (ATT_ReadByTypeRsp) Status : 0x1A (The Procedure Is Completed) ConnHandle : 0x0000 (0) PduLen : 0x00 (0)Dump(Rx):04 FF 06 09 05 1A 00 00 00
-------------------------------------------------------------------
What am I doing wrong?
thanks
Laith
FYI, the link was very helpful.
I'm sorry, I'm on a trip so I cannot remember this things right now. But I remember that if you set "02" to 0x0022, you are going to put the keyfob in proximity alert loud mode ;) Bye!
Hello,
Also try sending a FindInfoReq and look at the handle <--> UUID pairs.
BR,
-Greg
I've made somebody in the lab check this since it is also interesting for me:
Within the result of the command GregS suggested there is...
Handle : 0x0022Data : 06:2A
Which you can see matches the values at the top of the thread. Please be aware "Alert" and "Service" UUIDs are different concepts. Bye.
Hi all,
While Discovering the characteristic of PROXIMITY_ALERT_LEVEL_UUID 0x2A06 , i could able to get two handles 0x0025 for Link loss alert and 0x0028 for path loss alert ,Upon setting 0x0025 to 02 ,whenever the timeout occur ,keyfob will beep ,because GAPROLE_WAITING_AFTER_TIMEOUT will occur .
But when I write the handle 0x0028 with value '02 ' ,immediately Keyfob will start beeping and whenever i restart my keyfob it will beep because GAPROLE_CONNECTED will occur ! But my question is ,when ever pathloss is enabled then Whenever the connection is about to leave the proximity ,it (keyfob )should give alarm !
Thanks in advance ,
Link loss is well understood ,but i need some help in understanding how path loss is working ??
my assumption : The Key fob will perform the Buzzer (for some time ) and led will glow till it is in the connection and when ever it is about to leave the proximity what is the expected output ??? when the connection is lost , LED will stop glow !
Thank you Sentil Kumar , I finally got the Proximity Alert working
Hi rutvik ,
Kindly press Verify Answer , if your question is answered !
Regards,
Senthil
NiceDay,