• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 76 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2642R-Q1: CC2642R-Q1

xd z
Prodigy 20 points
Part Number: CC2642R-Q1

Tool/software:

Hi

  1. I am using the following program to implement the CM functionality:
    C:\ti\simplelink_cc13xx_cc26xx_sdk_7_41_00_17\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\connection_monitor.

  2. Our requirement is for the node running the connection_monitor to always identify and report the RSSI of data packets sent by the central.

  3. I have a question: how does the node running the connection_monitor program distinguish whether the received signal is sent by the central (e.g., a smartphone) or is a response packet from the peripheral?
    Is there a possibility of mistakenly identifying and reporting the RSSI of a response packet from the peripheral? If not, how is it ensured that the program executes correctly?

    Best
    xdz
  • 0
    TI__Expert 8305 points

    Hello,

    Due to the holidays, there will be some delay in our responses. This thread has been assigned and will be handled accordingly.

    Thank you for your patience.

    Best,

    Nima Behmanesh

  • 0 in reply to Nima
    TI__Expert 3580 points

    Hello xdz, 

    The connection monitor project uses two ways to determine the which packet the RSSI is measured from. Please see the attached section of micro_cm_app.c: 

    The connRole is checked from the connection information. Additionally, the time stamp is compared for the Central and peripheral vs. the lastStartTime, which is the last scan start time. If the time stamps are similar, and the connRole matches, then the corresponding device RSSI will be entered into the responderRssi variable. 

    Additionally, before these compares take place, the data is entered into the respective variables in micro_ble_cm.c. 

    cmCentral is initially set to TRUE. cmCentral will then continually change when each packet is received. Each time a packet is received, the data in connInfo struct is updated. The data is then used in the first image. 

    The RSSI can become mixed up, if packets are missed. When this occurs cmMissedEvents is added to, if this reaches a certain value, the connection monitor will stop. Additionally, the connection monitor app will keep track of the time missed when an event is missed, so the timestamps stay up to date. 

    Let me know if you have any questions!

    Thanks, 
    Isaac