This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CC2640: immediate alert

Part Number: CC2640
Other Parts Discussed in Thread: BLE-STACK,

Tool/software: Code Composer Studio

How should immediate alert be implemented on a BLE client device? I've seen keyfobdemo and proximity for BLE server in DK. Example code would be appreciated. Thanks.

  • You can revise key_fob example to send immediate alert when you detect something such as button press or GPI triggered.

  • Hi Will,

    I don't understand your question. Can you provide some more detail?

    1. What version of the BLE-Stack are you using?

    2. What example project have you based your application on?

    3. What do you specifically mean by immediate alert?

  • Hi Marie H.,

    Here are the responses to your questions:

    1) ble_sdk_2_02_02_25

    2) Proximity profile

    3) Immediate alert Service = IAS

    My device is a client (cc2640) that collecting measurements for a server (NRF52840). According to the developer of the server, AIS events are sent periodically to client device and I am not seeing them. So, I tried implementing code from the Proximity profile into the client: added callbacks, attributes, characteristic, etc and AIS events from the server are still being seen at the client.

    My next option is to have the serve to create a Generic Attribute Profile, and when the client sets CCCD = GATT_CLIENT_CFG_INDICATE send the AIS event (something of that nature).

    Am I making sense? What are your thoughts?

  • Hi Will,

    Thanks for sharing more details about your use-case. 

    Do you have a sniffer so you can see what's being sent from the client? 

    Thanks, 
    Elin

  • Will Baker said:

    My device is a client (cc2640) that collecting measurements for a server (NRF52840). According to the developer of the server, AIS events are sent periodically to client device and I am not seeing them. So, I tried implementing code from the Proximity profile into the client: added callbacks, attributes, characteristic, etc and AIS events from the server are still being seen at the client.

    My next option is to have the serve to create a Generic Attribute Profile, and when the client sets CCCD = GATT_CLIENT_CFG_INDICATE send the AIS event (something of that nature).

    Am I making sense? What are your thoughts?

    No, Immediate Alert should be like this. Why do you think you should use proximity profile for what you want to happen.

    -kel