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.

CC2640: HCI_ReadRssiCmd - Is there a penalty using it continuously?.

Part Number: CC2640

Hi,

My question is related to the use of HCI_ReadRssiCmd in a multi connection environment.

Would invoking this command periodically on numerours channels have a performance hit on connection handling\Stack\RF behavior?.

Does this command drain system resources?.

I would like to monitor RSSI on channels constantly. 

Thanks

Tamir

  • Hi Tamir,

    Yes, this does create a performance hit, as now messages will be passed up to the application layer consuming cycles/memory.

    And yes, you could do this for every connection handle to monitor RSSI on all channels.

    software-dl.ti.com/.../group___h_c_i.html

    Regards,
    Rebel
  • Thanks,

    I would like to sharpen my question.

    I am aware of the mesages being sent to the application layer via CB, that consume cycles/memory.

    I am more intereseted if this might have an implication on the BLE stack behavior causing it maybe to miss connection intervals in a multi connection environment.

    As I stated I am initiating multiple connections.

    I am calling HCI_ReadRssiCmd periodically(every min, not every connection interval.)

    Ofcourse waiting for it to complete, before invoking next call on next channel.

     

    Question

    Does this invocation use stack\RF core resources that might caues link termination in a multi connection environment?. 

    Thanks

  • The RSSI notification event is sent after the connection event closes, so there is no risk to connection stability.

    Best wishes
  • Thanks Rebel
    Thanks JXS