• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 196 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.

Issue receiving advertise on all ADVERTISE channel

Sudeesh
Prodigy 160 points
Other Parts Discussed in Thread: CC2541, CC2590

Hi,

I am using CC2541 + CC2590 in my design and using simpleBLEPheripheral for the entire development. Most of the development is completed and recently i am noticing that there is a problem in receiving the advertise response on the android app. 

Initially advertise was on ALL channels and later was changed to individual channels to check the performance.

I have tested with 4-5 different makes of mobiles and found that the device listing during scan was delayed and sometimes it was not getting listed.

Later on after close observation I found that certain mobiles are not able to receive advertise MSG on CH# 37 and 38. Only able to receive on ch#39.

I know that this query is slightly off topic, but wanted to check if any one in this forum has faced similar issues.

Also wanted to know what will be the implications if advertise is fixed to a single channel rather than advertise on ALL channels.

Thanks

  • 0
    TI__Guru** 105180 points
    Hello,

    I am aware of some issues with establishing connections on certain OS versions, namely Android 5.x, but this is the first time I've heard of "blacklisting" specific Adv chans. Can you replicate this behavior with TI reference HW? Have you done RF-PHY testing on your product with a BLE RF tester? Is it possible there is interference on the other channels?

    In terms of the BLE spec, a scanner is supposed to listen on all three Adv channels, and the Advertiser should likewise transmit on all chans. You could only TX on one channel, but that may delay the establishment of a connection. The reason three chans are used it so increase the chances of a quick & successful connection establishment.

    Best wishes
  • 0 in reply to JXS
    Prodigy 160 points

    Hi JXS,

    Thanks for your prompt reply.

    Yes, the PHY has been tested for the entire 2.4ghz band and specific on ch 37,38 and 39. The POUT is a in the range of 8.4-8.7dBm with an offset of 9.8khz. So there is no problem on the Pheripheral side. 

    I have run this test multiple times on different makes of mobiles and handsets to reaffirm on the case. I am noticing this problem on Moto G and Moto G2 mobile running Android 5.x.x.

    I will definitely do the same test on the sensor tag and report on the observation.

    Any other pointers that needs to be tested.