Smart Bluetooth Forum Discussions
I am experimenting with an application based on the 20732S, and looking at the power draw.
I've noticed that when the device is in a low rate advertisement state, the current gets down to around 60 microamps. But if i touch my finger on side 'C' of the chip (over the keepout area), the current starts ramping up to a much higher level in the mA range.
I wanted to ask if this is an expected behavior, or if this means there is something wrong with my layout?
I imagine that perhaps this messes up the antenna and causes the chip to react by ramping up power somewhere?
The final application will be in an enclosure that prevents this from happening but my concern was whether my board design is somehow making the system flaky.
Show LessIs there any API for retrieving the Tx power for current advertising or connection state?
From the comment of these 2 APIs in setting the Tx power.
Does it mean that controller will change the tx power by itself without over the maximum set by application?
Question 1. Any other API for retrieving the current Tx power?
Question 2. What's the default Tx power (4 dBm?) if application doesn't set it manually at all?
Question 3. What's the parameter to set Tx power to 4 dBm (if this is the default one) if the granularity of Tx power is 3, -1, -5 .... , -25 (in every 4 dBm) refer to 'Re: Power level granularity in blecm_setTxPowerInConnection() and blecm_setTxPowerInADV()'
////////////////////////////////////////////////////////////////////////////////
/// Sets the maximum TX power
///
/// \param maxTxPowerDb The max TX power allowed in dB.
////////////////////////////////////////////////////////////////////////////////
void blecm_setTxPowerInConnection(INT8 maxTxPowerDb);
////////////////////////////////////////////////////////////////////////////////
/// Sets the maximum TX power
///
/// \param maxTxPowerDb The max TX power allowed in dB.
////////////////////////////////////////////////////////////////////////////////
void blecm_setTxPowerInADV(INT8 maxTxPowerDb);
Show Lessusing SDK 2.0.1 with my new 20737TAG, i'm able to successfully build but not download a sample app....
output in the console window reports that No BCM20736 has been detected....
the drivers for the board's USB interface have been installed and (correctly) show two USB serial ports in the windows device manager....
all switches on the board have been verified as well....
the first (and perhaps most obvious) questions is: does the smart tag have an LED to indicator power??? at this point, the board is dark....
thanks
Show Less
Is it safe to ALWAYS do a STOP SCAN immediately just before doing a START SCAN?
That is,
Is it safe to STOP SCAN if scanning has already been stopped?
Show Less
After attempt to connect to a Bluetooth address for a peripheral that just powered off (battery died), central can no longer connect to any other powered-up peripherals. (This would occur if central scans for and detects peripheral, but peripheral then is powered off before central connects to it.)
Peripheral with Bluetooth address '000000000001' is powered on, and peripheral '000000000002' is powered off.
Central connects to P1 okay and gets notifications. Then disconnects.
Central tries to connect to peripheral '000000000002'.
Central disconnects.
Central tries to connect to '000000000001' again, but does not even get the connUp callback.
Why can't central re-connect with peripheral '000000000001' ?
Show Less
Hi ,
Its unclear from the datasheet for the BCM20732S, which pin is the RTS pin ?.
I see that CTS is pin 30 and in older datasheets RTS was pin 25.
Does a UART RTS pin exist for the BCM20732S.
Thanks
Mark
Show LessDoes a vendor service or vendor characteristic denoted by a 128 UUID actually need to be registered with the Bluetooth SIG?
My inclination is that it does not need to be …
But I would like to know definitively …
For example, your Hello Sensor app has a 128 bit vendor service/characteristic .. did the UUID that was used need to be registered by SIG?
Thanks
Show LessI have a custom board design based on the 20732S, which has a button that allows the system to wake up from HIDOFF mode if the button is held down for more than 3 seconds.
My application enters HIDOFF mode and I see a very low power draw (~2 microamps).
When I press the button briefly, the system wakes up, waits about a second, sees that the button is not pressed anymore, prints a BLE trace message, and re-enters HIDOFF mode.
About half the time, the device enters HIDOFF and the current goes down to 2uA again.
The other half of the time, the device still appears to enter HIDOFF mode (it stops operating) but the current draw rises to 3 MILLIamps and stays there permanently. If I press the button again to wake it up, it wakes up just as normal (a normal boot from HIDOFF) and operates as expected.
What could cause this behavior, and is there anything I can do to prevent it?
Could this be caused by some interrupt input occurring at a bad time when trying to go to sleep?
Show Less