RTOS/CC2640R2F: Connection Monitor Example

Hi Thejas,
Which SDK version are you testing with?

Hi Joakim,

I am testing with SDK version 2.40.00.32. I am using the uNPI version of the connection monitor. I can see the connection get established, but the RSSI stream just does not come. (I have attached a screenshot) I did see it only once, when I waited for a long time, but it's not consistent.

Also, at what point do I expect the connection monitor to send an RSSI packet? Also, I notice that the master sleep clock accuracy has been hard coded to 90. Isn't that an important connection parameter - shouldn't it be the same that comes as part of the connection parameters at the time of connection establishment between the central and the peripheral? I am wondering if the hard coding of this value can affect the connection monitor's ability to catch all the packets that are getting exchanged. Your insight in this matter will help me a great deal. Thanks a lot in advance.

Regards,

Thejas

Hi Thejas,

Please see the known issues, and let me know if any of it helps you: e2e.ti.com/.../770218

Best regards,
Aslak

Hi Aslak,

Thank you very much for your response!

I tried item 3 in the FAQ list (Connection Monitor won't start when certain Connection Parameters are used)


I still seem to have the same problem. It worked only once in about 15-20 attempts.

Looking forward to your response. Thank you very much for your support.

Regards,

Thejas

Hi,

I have provided some test code for you to use on rtls_passive project. I was able to run it for over 30 mins without problem.(I have not had time to run it longer than that.)
Can you give it a try? If you have more question, please respond in the following post. I will close this one for now.
e2e.ti.com/.../2908702

Hi Christin,

I really appreciate your time and input. I will apply the patch and let you know how it goes.

I wrote this particular post regarding the connection_monitor example. Did you mean to say you ran connection_monitor for about 30 minutes and it worked fine for you? Can you please confirm if my understanding is correct? For me, the uNPI version of the example almost never works. It only worked for me once in about 30 attempts. Is there something I have to do with connection parameters? I feel there is something going wrong with the connection interval and sleep clock accuracy.

Once again, thank you so much for your time.

Regards,

Thejas

Sorry for not being clear. So I was able to get rtls_passive to report rssi on normal BLE connection and it has been running for half a day without issue.

I will spend time on connection monitor now, but please do give it a try using rtls_passive. They are using the same stack, just rtls_passive can also do AoA and ToF.

Hi Christin,

Thank you so much for taking time to help me out. The rtls_passive works well, thank you once again!

Also, it would be great if you could tell me if there are any extra steps to be followed to make connection_monitor with uNPI work over UART other than using the micro_ble_cm_app files and defining NPI_USE_UART symbol.

Appreciate your time and expertise.

Regards,
Thejas