TIDA-00374: On Android application BLE SCAN and BLE Scanner - I Cannot see the TIDA-00374 device

Hello Tony,

Given the slow beacon interval can you try increasing the beacon ADV rate to 100ms to confirm if the phone is able to observe the broadcast? This will rule out the phone just not having it's receiver on at the broadcast time.

Best wishes

Could you tell us how we change the ADV rate to 100ms. We are using TI board www.ti.com/.../TIDA-00374

and we cannot find anywhere in software where we can change TPL5110 (nano system timer) to wakeup in 100ms interval.

Thanks for your help.

JXS,

Thanks for helping! I'm adding myself to the thread.

Respectfully,

Omid

Could we have someone on TI forum respond to our request

Let me summarize our ask again
(1) TIDA-00374 that is a BLE device with integrated sensors from TI. We are unable to see this device on popular android apps such as BLEScanner and BLE SCAN. We can see all our other BLE device in a controlled chamber enviornment but not the TIDA-00374.
(2) Someone on the forum suggested to reduce the beaconing time from default value of 1 minute in TIDA-00374 to something lower. We cannot find anywhere in TIDA-00374 software to change the TPL5110 (nano system timer) value to something lower/different.

Could someone respond to our ask.
Thanks

I checked the latest TIDA-00374 firmware (v1.3) and it uses a custom ADV payload which does not have the headers that mobile OS's require. This is fine for custom scanning applications. You can add the required header (tokens), refer to how this is done in the advertData[] from BLE-Stack simple_broadcaster project.

Your packet[] array in main.c will look like this:

 0x02,   // length of this data

 0x01, // GAP_ADTYPE_FLAGS,

 0x04, // GAP_ADTYPE_FLAGS_BREDR_NOT_SUPPORTED,

 0x07,  // length of this data including the data type byte

 0xFF, // GAP_ADTYPE_MANUFACTURER_SPECIFIC, // manufacturer specific adv data type

 03;  // start of original HDC data payload

 74;

 HDC_data[0],

 HDC_data[1],

 HDC_data[2],

 HDC_data[3]

Best wishes

Thanks a bunch for helping JXS!

JXS - Thanks a lot for the response. This is the frame format we have now based on changes you suggest. Could you please suggest how we can change the timer on TPL5110 for it to beacon more frequently.
 We searched through the source code to identify instances of TPL5110 but we couldn't find any.

Sincere thanks for your help.

Hi Tony,

Thank you for the update. Are you able to detect in your Android application?

To change the timer of the nano timer, you need to change the resistors. See the TPL5110 data sheet for computing the values.

Best wishes

JXS - Thanks for your pointers. Yes now we can detect in the Android application.

Looks like the only way to change the value is to change the resistors. Does any of the TIDA family of sensors allow us to configure using software.

Thanks for all your help.

Tony,

Great, glad to see you are able to detect the broadcast in your Android application!

Regarding programmable external timers, it may be best to connect with our experts in the Clock and Timing forum.

You can of course use the CC2640 / CC2650 / CC2640R2F with the BLE-Stack and internal RTC to control the wake up interval. Standby current is ~ 1uA when in this configuration.

Best wishes