• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 308 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: connection monitor of CC2642

tiansheng shu
Prodigy 20 points
Part Number: CC2642R

Tool/software:

Now we want to implement the anchor point as a third-party monitor to obtain RSSI according to the master-slave Bluetooth connection for positioning.

The demo we want to refer to is the connection monitor file of CC2642.

Then we can obtain the relevant parameters during the master-slave connection process.

Power on direct monitoring

But where do you write these parameters to the connection monitor to skip the additional flow of the routine and direct monitoring?

Other additional flow is: passing parameters as scripts in the guide

  • 0
    TI__Mastermind 42100 points

    Hi,

    Thank you for reaching out to us. We will take a look at your question and get back to you as soon as possible.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 20 points

    What is the status now

  • 0 in reply to tiansheng shu
    TI__Expert 3561 points

    Greetings,

    I am not quite sure I follow what you mean by writing parameters to the connection monitor. How are you planning on providing the connection parameters to the CM in order for the monitoring to begin?

    Best,
    Achyut Ray

  • 0 in reply to Achyut Ray
    Prodigy 20 points

    One way to do this is to obtain the connection parameters between the master device and the slave device through the UART, and then write them in the connection monitoring demo as follows:

    Now that I have the connection data, I intend to do this and write parameters directly to the monitor demo, but the RF_getCurrentTime() and UB_MAX_MONITOR_DURATION parameters are not yet defined in the actual code (including the SDK).
    After forcibly writing, there is no reaction to run, where is the operation problem?

  • 0 in reply to tiansheng shu
    TI__Expert 3561 points

    Greetings again,

    Usually, the start monitoring happens when the relevant API is called, after all the information for the connection-to-be-monitored has been programmed. When using the GUI demo, the relevant API is triggered using NPI messages sent from a "master" device. I would recommend checking if the ubCM_startNewSession() API is getting called appropriately.

    Best,
    Achyut Ray