• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 445 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.

CCS/CC2642R: Connection Monitoring: discovering HopID, Hop interval, etc...

JCrash29V
Prodigy 85 points
Part Number: CC2642R

Tool/software: Code Composer Studio

Hello,

I am interested in TI's connection monitoring project to track and a Bluetooth connection.

The only problem is that the BLE device I want to track cannot be programmed to give me the HopID, Hop Interval etc... My understanding is that upon establishing a connection this data is shared. 

Does TI have an example project that would allow this data to be seen? I was thinking of using the BLE observer project to continually monitor BLE advertisments. But I don't know if this would detect a BLE Connection packet?

Any advice on retrieving this data would be very helpful.

Thanks,

John

  • 0
    TI__Guru 56590 points

    Hello,

    I have assigned an expert to comment.

  • 0
    TI__Guru** 101450 points

    Hi,

    A few remarks:

    • An observer is a device that can only receive the advertisements. An observer cannot enter a connection. You cannot monitor a connection using an observer.
    • The channel map, the hop value, the current channel... are pieces of information only accessible by the two connected devices. The two devices always have access to this data. If you want a third device to monitor the connection, one of the two connected has to share this information with the third device. (In other word, assuming A and B are connected and C is doing connection monitoring. A (or B) has to send the connection information (channel map, hop value, current channel, connection interval...) to C.)
    • TI provides a connection monitor example based on the micro BLE Stack (uBLE). As you can see in the documentation, the connection monitor will absolutely require to receive a few info at initialization time.

    To finish, within the RTLS example TI provides some code showing how to share the connection data between the rtls_master (central) and the rtls_passive (connection monitor).  (RTLS stands for Real Time Localization System)

    I hope this will help,

    Kind regards,