Ultrasonic Sensing Forum - Recent Threads

RE: TMUX9832: TMUX9832 – Abnormal Output Signal Observed on Specific Channel

Nir Gilgur — Fri, 19 Jun 2026 15:08:41 GMT

Hello Sunmi,

I apologize for the late response, E2E tends to be buggy sometimes and some posts don't appear on my side.

Can you specify which channels you are seeing these abnormal signals?
Is the top picture shows a good signal and the bottom one a bad one?
Is there any difference in loadings between the channels? Is there a schematic you can share?

Can you also share waveforms of input vs output both for the "good" and "bad" channels?

Thanks,

Nir

TMUX9832: TMUX9832 – Abnormal Output Signal Observed on Specific Channel

sunmi yeo — Fri, 12 Jun 2026 01:02:21 GMT

Part Number: TMUX9832

Dear TI Support Team,

We are currently using the TMUX9832 (QFN package) in an ultrasound system and have observed abnormal output waveforms on some channels.

The input signal is normal, but the output signal from the TMUX9832 appears distorted on certain devices/channels.

We would appreciate your support in understanding the possible causes and recommended diagnostic tests before replacing or decapping the device.

RE: PGA460-Q1: PGA460 Q1 BOOSTXL circuit not getting Echo

Alicia Rosenberger — Mon, 15 Jun 2026 20:52:38 GMT

Hi Jaya,

Thank you for posting to the Sensors forum!

I am so sorry for missing this thread, I am not sure why I wasn't able to find it until now. But I saw your newer thread on this same topic and went ahead and replied to the newer thread.

I will go ahead and close this thread and we can continue the conversation on this topic there.

PGA460-Q1: Not getting echo

Best,

~Alicia

PGA460-Q1: PGA460 Q1 BOOSTXL circuit not getting Echo

Jaya Shree — Sun, 31 May 2026 09:33:55 GMT

Part Number: PGA460-Q1

Hello TI Support Team,

I am currently working with the PGA460-BOOSTXL EVM along with the transducer daughterboard. I have carefully followed the step-by-step instructions provided in the official TI setup video, but I am unable to receive any echo signal in the GUI.

Here are the details of my setup:

Hardware: PGA460-BOOSTXL Evaluation Module with the included Transducer Daughterboard.
Software: PGA460 EVM GUI.
Problem: The device does not register or display any echo data during a burst/listen command.

I have attached a screenshot of my GUI window showing my current register settings, thresholds, and the blank echo data plot for reference.

Could you please help me troubleshoot why the echo is missing? Let me know if you need me to verify specific jumper configurations, register values, or supply voltages.

RE: MSP430FR5043: Power supply and consumption questions for MSP430FR5043

Peter Jiang — Wed, 10 Jun 2026 03:03:03 GMT

Hi Anthony,

[quote userid="571160" url="~/administrators1/ultrasonic1/f/ultrasonic-sensing-forum/1651129/msp430fr5043-power-supply-and-consumption-questions-for-msp430fr5043"]ince the supply pins are recommended to be connected together, doesn't that mean that the DVCC and AVCC supply should also be 2.2 to 3.6 V?[/quote]

1. Yes, I think your understanding is correct, if connected together, it will also limit the DVCC and AVCC within the 2.2V to 3.6V. However, from another perspective, I think the reason why datasheet indicate two different range is that it wants to emphasize the different requirements between DVCC/AVCC and PVCC, since PVCC is specifically designed for USS modules, it has stricter requirements for the range of power supply variations, especially in some battery-powered scenarios application we should pay more attention to it. Therefore, the datasheet lists the actual spec of different type of power supply, however, for practical applications and to avoid erroneous writes to RAM and FRAM due to excessive differences between DVCC/AVCC and PVCC, we recommend connecting them together, this is a common and good practice.

[quote userid="571160" url="~/administrators1/ultrasonic1/f/ultrasonic-sensing-forum/1651129/msp430fr5043-power-supply-and-consumption-questions-for-msp430fr5043"]Are we missing something or is the MSP430FR5043 intended to be powered from 3.0 V to achieve the lower power consumption?[/quote]

2. Have you tried reducing your system's supply voltage down to 3.0V or 2.2V to measure the power consumption? Does the power consumption performance match the datasheet? If not, I would suspect that there is more likely you have missed something with the low power measurement condition settings, because commonly under the same configuration, the power consumption performance at 3.3V and 3V should not differ significantly. Based on the testing result provided in the datasheet as shown below, it can be seen that the power consumption between 2.2 and 3.3V should remain in the similar level.

[quote userid="571160" url="~/administrators1/ultrasonic1/f/ultrasonic-sensing-forum/1651129/msp430fr5043-power-supply-and-consumption-questions-for-msp430fr5043"]are the use of ferrite beads a good idea since they will add impedance to the supply line? [/quote]

3. I think your doubt is reasonable for the ferrite will increase the impendence, however, I believe that the designers of the EVM should also consider this point, and when using ferrite beads to isolate noise, they placed enough decoupling capacitors like C24,C23,C3,C4 to compensate for the high impedance introduced by the ferrite beads. Therefore, I think when testing under actual load conditions, as long as the voltage ripple and transient response on the power rail meet the required standards, this design can be adopted. Of course, you can also make adjustments based on your own design to ensure that it meets your actual requirements.

Best Regards,
Peter

MSP430FR5043: Power supply and consumption questions for MSP430FR5043

Anthony Davidson — Mon, 01 Jun 2026 14:01:27 GMT

Part Number: MSP430FR5043

We are working on an ultrasonic water flow design based on the MSP430FR503.

First, there seems to be some weirdness with the recommended operating conditions for the power rails. The datasheet recommends that the power supply pins be powered from the same source, that is, AVCC, DVCC, and PVCC should all be connected together. However, the supply range in Table 8.3 on page 30 says the recommended range for DVCC and AVCC is 1.8 to 3.6 V and the range for PVCC is 2.2 to 3.6 V. Since the supply pins are recommended to be connected together, doesn't that mean that the DVCC and AVCC supply should also be 2.2 to 3.6 V?

Next, all the power consumption data shown in the datasheet from page 31 to 35 are at a VCC equal to 2.2 V or 3.0 V. We are powering the chip at 3.3 V and not able to achieve power consumptions close to that shown in the datasheet. Are we missing something or is the MSP430FR5043 intended to be powered from 3.0 V to achieve the lower power consumption?

Next, the datasheet discusses appropriate decoupling for the power supply pins in Note 5 in Table 8.3. The datasheet does not make any recommendations for using ferrite beads to filter the power supply lines. However, the schematic for the evaluation board EVM430-FR6047 shows a ferrite bead being used to filter both AVCC and PVCC. Since the datasheet recommends 22 uF caps as close as possible to the PVCC supply pins, that suggests that the PVCC pins will draw relatively high pulsed current so my question is are the use of ferrite beads a good idea since they will add impedance to the supply line?

EVM430-FR6043: Unable to communicate

Kevin Jespersen — Tue, 05 May 2026 19:50:31 GMT

Part Number: EVM430-FR6043

For Mouser customer, Service Order 534128

I've been unable to successfully communicate with the board using TI's USS Design Center software. The software detects and connects to the board, but remains stuck at "Waiting for device" and does not proceed further. I've spent many hours reviewing Texas Instruments support documentation,
troubleshooting guides, and trying various connection methods, but have not been able to resolve the issue. As part of troubleshooting, I tested the board using TI's MSP430Flasher utility. The board is detected, but the tool returns "Unknown Device" when attempting to access the target device. I have a very technical hardware and software background and I feel that I have exhausted all recommended options."

RE: EVM430-FR6043: Unable to communicate

Peter Jiang — Tue, 26 May 2026 14:33:06 GMT

Hi Kevin,

"Waiting for device" is commonly caused by the following reasons:

1. Incorrect firmware, incompatibility with the GUI. Please make sure you have already flashed the device with the correct version of firmware before connecting to the GUI.

2. Incorrect Java version, please use the Java 8, instead of any other higher version.

So, could you please provide below information:

1. What version of firmware/project and GUI you are currently using? You can refer to the MSP-ULTRASONIC-DESIGN-CENTER to download the latest demo project and corresponding version GUI.

2. Please open the GUI and check the Java version in the “Help” -> “About” -> “System Information” as shown below. If you find that it's not the Java 8, please firstly uninstall the current Java version on your PC, then try to download and install the Java 8 in the below link https://www.java.com/en/download/, after installing the Java 8, please perform a PC restart and then try to connect the GUI again.

Best Regards,
Peter

EVM430-FR6043: Unable to Set UPS0 to UPS1 Gap Below 20 ms in USS GUI (Gas Mode)

Nilotpal Baruah — Fri, 15 May 2026 06:38:02 GMT

Part Number: EVM430-FR6043

Board:
EVM430-FR6043

GUI Version:
USS_02_30_00_03

Application Mode:
Gas Mode

Issue Description:
While optimizing the ultrasonic gas flow meter configuration for higher measurement rates (~100 Hz), I attempted to reduce the “UPS0 to UPS1 Gap” parameter below 10 ms. However, the USS GUI does not allow values lower than 20 ms to be entered or applied.

Current Observation:

GUI restricts UPS0 to UPS1 Gap to ≥ 20 ms
Lower values cannot be typed or requested through “Request Update”
Timing diagram updates accordingly and prevents further reduction

Current Configuration:

Number of Pulses: 24
Search Range: 20
Signal Sampling Frequency: 1000 kHz
Capture Duration: 300 µs
Algorithm: Hilbert Wide
User Param #8: 384
Transducers: 200 kHz gas ultrasonic transducers

Objective:
Targeting approximately 100 Hz measurement rate for high-speed gas flow measurement experiments.

Questions:

Is there a firmware-level or GUI-level limitation preventing UPS0→UPS1 Gap below 10 ms?
Can this parameter be modified directly in source code or header configuration?
Is the limitation related to:
- USS processing time,
- transducer ringdown,
- GUI validation,
- or MSP430FR6043 hardware timing constraints?
What is the minimum achievable stable UPS0→UPS1 Gap for gas mode on EVM430-FR6043?

Additional Notes:
The ADC waveform is stable and frequency sweep optimization is currently in progress. The goal is to experimentally evaluate higher acquisition rates while maintaining acceptable DToF stability.

EVM430-FR6043: Unable to Set UPS0 to UPS1 Gap Below 10 ms in USS GUI (Gas Mode)

Nilotpal Baruah — Thu, 14 May 2026 11:43:52 GMT

Part Number: EVM430-FR6043

Board:
EVM430-FR6043

GUI Version:
USS_02_30_00_03

Application Mode:
Gas Mode

Current Observation:

GUI restricts UPS0 to UPS1 Gap to ≥10 ms
Lower values cannot be typed or requested through “Request Update”
Timing diagram updates accordingly and prevents further reduction

Current Configuration:

Number of Pulses: 24
Search Range: 20
Signal Sampling Frequency: 1000 kHz
Capture Duration: 300 µs
Algorithm: Hilbert Wide
User Param #8: 384
Transducers: 200 kHz gas ultrasonic transducers

Objective:
Targeting approximately 100 Hz measurement rate for high-speed gas flow measurement experiments.

Questions:

Is there a firmware-level or GUI-level limitation preventing UPS0→UPS1 Gap below 10 ms?
Can this parameter be modified directly in source code or header configuration?
Is the limitation related to:
- USS processing time,
- transducer ringdown,
- GUI validation,
- or MSP430FR6043 hardware timing constraints?
What is the minimum achievable stable UPS0→UPS1 Gap for gas mode on EVM430-FR6043?

RE: TMUX9832: Requesting TMUX9832 datasheet

Katy West — Thu, 07 May 2026 17:54:07 GMT

Hi Jason,

Have you submitted a request for the datasheet through our secure resources portal? You can find the "request more information" section on the product page!

Best,
Katy

TMUX9832: Requesting TMUX9832 datasheet

Jason Wright — Thu, 30 Apr 2026 20:00:31 GMT

Part Number: TMUX9832

Hi - I am looking to get access to the complete TMUX9832 datasheet, can anyone from TI help with this request?

TX75E16EVM: Problem running the Latte GUI

常雄川俣 — Fri, 01 May 2026 05:12:23 GMT

Part Number: TX75E16EVM

I want to use TX75E16EVM, but error ocurred.

I am using Windows 11, but is it unsupported?

EVM430-FR6043: Programming issue with EVM430-FR6043

Yash Gupta — Thu, 09 Apr 2026 09:16:28 GMT

Part Number: EVM430-FR6043

Hello,

I am facing an issue with my EVM430-FR6043 kit, After programming the kit once with custom USS_userConfig.h file, I have to reflash the evm kit board again with the code to get the results after a power cycle.

Step 1: Flash the board
Step 2: Getting the results of ultrasonic sensor
Step 3: Power cycle the board by removing the USB and reinserting back.

After this step 3 the board does not work or did not output until it is reflashed again.

What could be the possible cause for this ?

Regards,
Yash Gupta

RE: EVM430-FR6043: Programming issue with EVM430-FR6043

Yash Gupta — Fri, 10 Apr 2026 04:16:38 GMT

Waiting for response.

MSP430FR6047: Understanding and Customizing USS Library for MSP430FR6047 Ultrasonic Measurement

Shreya Vadla — Tue, 07 Apr 2026 09:21:18 GMT

Part Number: MSP430FR6047

Hi Team,

I am working on an ultrasonic flow meter using MSP430FR6047 and USS Design Center.
I am able to perform basic measurements successfully using the FR6047_USSSWlib_template example project.

I see that the ultrasonic measurement functionality is implemented in a precompiled
library (.a file) inside the USS package.

I would like to better understand and customize the measurement process, specifically:
- ToF calculation (Tup, Tdwn processing)
- Signal processing flow inside USS library
- How algorithms are structured internally

My questions:

1. Is the source code for the USS library (.a file) available under any license or request?
2. If not, is there any detailed documentation explaining:
- Internal processing flow (capture → filtering → ToF calculation)
- Key APIs and their roles
3. Are there example projects that demonstrate:
- Direct API usage without relying on USS Design Center GUI
- Minimal implementation for custom firmware integration?

My goal is to integrate USS measurement into a fully custom application
and possibly modify parts of the measurement pipeline.

Current setup:
- Device: MSP430FR6047 EVM
- Medium: Water flow measurement
- Tool: USS Design Center
- IDE: Code Composer Studio (CCS)

Any guidance on how to work effectively with the USS library or extend its functionality
would be very helpful.

Thanks in advance!

EVM430-FR6043: HID Bridge connected waiting for device

Ralph Schenderlein — Fri, 13 Mar 2026 11:04:45 GMT

Part Number: EVM430-FR6043

When I start running my evm430-FR6043 I first have to connect the device (USB).

After selecting 'Connect' in the GUI the process is stuck with a message in the status line:

"HID Bridge connected waiting for device"

I see this effect since yesterday and do not know how to fix it.

Before, the system worked for more than a year.

Please give advice how to overcome this error.

MSP430FR6047: Is the msp430fr6047 series the latest and greatest

Garret Crisler — Tue, 10 Mar 2026 13:26:42 GMT

Part Number: MSP430FR6047

Are these chips the latest and greatest when it comes to ultrasonic water flow metering?? I have seen very little written about this series of chips in the last 5 years. Seems like all the literature is from around 2017 - 2019 indicating the product maybe be superseeded by a better product, is that the case?? And if so what should I be looking at when it comes to water flow metering??

Garret

RE: MSP430FR6045: Pin Status of Controller

HARSH PALIWAL — Mon, 23 Feb 2026 05:48:08 GMT

Hi,
Awaiting Response

MSP430FR6045: Pin Status of Controller

HARSH PALIWAL — Fri, 13 Feb 2026 16:49:25 GMT

Part Number: MSP430FR6045

Hi,
As mentioned in datasheet about status of unused pins of controller to be output low
1.Is there a particular reason to it?

2.If i am using Two modes and when am using the same pin in one mode and wont be using it second mode should i configure it still as output as it be unused during that time or can i keep it as input to reduce current consumption.

RE: MSP430FR6045: Pin Status of Controller

HARSH PALIWAL — Tue, 17 Feb 2026 16:08:16 GMT

Hi,
Awaiting Response

MSP430FR6043: Get Stuck in the USS Module Measurement Part and Debugging

yasanga Dharmarathne — Tue, 17 Feb 2026 04:12:18 GMT

Part Number: MSP430FR6043

Hello, I am working on designing a customized flow meter and I am stuck at the USS module part. I use TI demo code in the IAR Embedded Workbench for MSP430 and I have customized the TI Demo code(Not USS module part is customized since it seems almost the same). But when it comes to USS module and measurements I have got stuck. i tested the Tone generation using the function USS_message_code debugCode = USS_startPPGToneGeneration(&gUssSWConfig, USS_test_channel_0); and I get a square wave if the transducers are not connected and when they are connected a different shape of continued waveform I got. And I received some continuous waveform as well.

1MHz wave form I get when the transducers are not connected.

Received continuous waveform when the transducers are connected. Yellow - Transmitting Tone, and Blue - Receiving Signal waveform. Do they make sense? They seem to have a DC part, is it okay?

Then I got in to the design center mainloop, USSLibGUIApp_Engine(); and chose to go with removing __ENABLE_LPM__ and in the USS_startUltrasonicMeasurement(&gUssSWConfig, USS_capture_power_mode_low_power_mode_0); function.

As the TI family guide says, we can't debug the intermediate steps inside the USS module, we can not go to debuggermode without turning off the USS module working properly, so we need to go from start transmition to capture and convert the captured data straight without going to debugger, as per my understanding as TI says. (Am I correct in here?).

Since my customized bord don't have a HMI, I used UART and created a send error code function using UART, so the loop continuosly run and I can see the error code it is given using a receiving python script as well (Confirmed that error code by full cycle runnging one time using a breaking point at the end and using watch option for the error code in the debug mode).

my problem is I get stuck in void commonWaitForconversion(USS_capture_power_mode_option mode) and can't debug in the middle as I get the error message of stopped by the debugger. I normally debug the working of a code step by step, but can't do it in here. I wanted to first watch if the excitation occurs as it is defined in the TI demo code (20 excitation pulses with no stop pulses I guess). But can't even see it either. I am not sure whether it excites (Tone generation works though) because the power on register bit USSPWRUP can't monitored as well. (I am using IAR Embedded WorkBench for MSP430 and MSP430FR6043) What should I do, Could you please help me with this?

EVM430-FR6043: EVM430-FR6043: Connection Issue: Custom MSP430FR6043 PCB unable to handshake with USS GUI via EVM ezFET

Nilotpal Baruah — Fri, 13 Feb 2026 11:13:56 GMT

Part Number: EVM430-FR6043

Hello TI Team,

I am currently developing an ultrasonic flowmeter solution using the EVM430-FR6043 evaluation kit and the Ultrasonic Sensing Design Center (USS) GUI. I have developed a custom PCB based on the MSP430FR6043, which has been hardware-optimized (removal of headers, LCD, etc.) for size reduction.

I am encountering an issue where the USS GUI fails to detect my custom board, despite successful firmware flashing and verified hardware connections. Below are the specific details of my setup, the issue, and my troubleshooting findings.

The Issue

I have flashed the standard USS Gas demo firmware (downloaded from TI.com) onto both the EVM board and my custom PCB using Uniflash.

EVM Board: Connects to the USS GUI without issue.

Custom PCB: The USS GUI displays "HID Bridge Connected -- waiting for device" and fails to proceed.

I have attached the schematic of my custom PCB for your reference.

Hardware Configuration & Wiring

To program and communicate with the custom board, I am using the ezFET section of the EVM430-FR6043. I have removed jumpers J1, J2, and J3 to isolate the EVM MCU and established the following connections between the EVM ezFET headers and my custom board:

Comms: EVM (RXD/TXD on J3) → Custom Board (TP18 RXD / TP19 TXD)

I2C: EVM (SCL/SDA on J1) → Custom Board (SCL/SDA on J1)

Control: EVM (RST/TEST on J3) → Custom Board (TP1 Reset / TP20 Test)

Interrupt: EVM (IRQ on J1) → Custom Board (IRQ on J1)

Power: EVM (VCC/GND) → Custom Board (TP21 VCC / Pin 6 GND)

Key Observations & Anomalies

During troubleshooting, I observed a discrepancy regarding I2C addressing that may be the root cause:

I2C Address Mismatch: Despite flashing the exact same firmware image to both boards, an I2C scan reveals different addresses:

EVM Board: Detects at address 0x48.

Custom PCB: Detects at address 0x0A.

Question: How can the identical firmware result in different I2C slave addresses on the same MCU model?

Logic Analyzer Analysis:

I intercepted communication between the working EVM and the GUI. The GUI appears to perform Read/Write operations on address 0x0A.

When attempting the same with the Custom PCB, the bus shows 0xAA + NAK.

Verification Steps Taken

To ensure the custom hardware is functional, I performed the following standalone tests:

Basic Functionality: Flashed a simple LED blink code to both the EVM and Custom PCB. Both worked successfully.

I2C Hardware Check: Verified the physical I2C lines on the Custom PCB by communicating with an Arduino Uno. The hardware lines are functional.

Could you please assist in troubleshooting why the Custom PCB is rejecting the GUI connection or explain the I2C address discrepancy observed between the EVM and the custom hardware?

For your reference, I have attached the datasheet to this post.

Thank you.

Sch_Ultrasonic_Flow_Meter_Controller_20250922.pdf

RE: Ultrasonic AFE for Ultrasonic NDT device

Ankit Patel — Thu, 06 Jan 2022 12:10:15 GMT

Hi kalyan,

Yes it would be useful if ADC is integrated.

If you have any option without the integrated ADC do tell me.

Thanks,

Ankit

Ultrasonic AFE for Ultrasonic NDT device

Ankit Patel — Tue, 04 Jan 2022 13:16:44 GMT

Hello ,

I am Ankit .

I am looking for Ultrasonic AFE solution to develop an Ultrasonic NDT device.

I found this link for the concerned AFE solutions

[FAQ] Ultrasonic Sensors - Sensors forum - Sensors - TI E2E support forums

Here the TI picked device for Ultrasonic NDT is TUSS4440.

TUSS4440 can only support transducer frequencies upto 500Khz max.

But i need a device which can support transducer frequencies upto 20MHz.

Is there any other solution for this or any other way to use the device for the same.

Thanks in Advance