Part Number: TUSS4470
Please help me to know ,
what is the power consumption in listen mode of the TUSS4470 Driver?
How to calculate the power consumption of that driver?
When the TUSS4470 is in the active burst-listen mode, it draws approximately 11.5mA of current. The device offers a standby mode to reduce consumption to 1.5mA, and a sleep mode for 350uA. The differences between these modes is explained in section 7.4 Device Functional Modes of the datasheet.
You can use the TUSS Generation III EVM GUI software's built-in Power Budget Calculator to help you estimate the power consumption of the device when using the different power modes over time.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Akeem Whitehead:
thank you Akeem.Can you please give me the brief information of listen mode in TUSS4470Regards Mallikarjun
In reply to Mallikarjun Ratnakatti:
The current consumption of the device is still 11.5mA in listen-only mode, regardless if you are bursting or not. The bulk of the power consumption of the device is based on the requirement's of the analog front end processing of the received echo data (which includes a low noise amplifier and logarithmic amplifier gain stages). The device always start-up in the active listen mode, so the default current consumption is 11.5mA.
I am from the same team as Mallikarjun.
A follow up question on the listen mode. Is it necessary to provide VPWR/VDRV voltage if we intend to use only listen mode and never drive the transducer?
This would make our application simpler with only 3.3V provided for the whole circuit (controller + TUSS4470)
In reply to Chethan Shettar:
In short, yes, you can run the TUSS4470 exclusively from a 3.3V supply for a listen-only application.
However, instead of leaving VPWR/VDRV floating, I recommend that you tie your 3.3V signal to VDD, VPWR, and VDRV to ensure the driver block remains stable while inactive. This will avoid a potential device state where VDRV attempts regulate to VPWR (which may create internal switching noise if floating). Ideally, if VDRV is set to remain Hi-Z in software, this device state can be avoided, but best practice is to make VDD, VPWR, and VDRV common as a fail safe for listen only operation.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.