Ultrasonic Sensing Forum - Recent Threads

MSP430FR6047: inconstant measurement period

Timon Burkard — Thu, 17 Sep 2026 07:58:14 GMT

Part Number: MSP430FR6047

We have two questions about the MSP430FR6047:

1.) Measurement Period

The TI MSP430UltrasonicLibrary (version 02_40_00_00) contains a function to implement the measurement period: USS_waitForAppTimerElapse()

Acc. to your example:

int main()
{
    // Init
    // ...
    gUssSWConfig.systemConfig->measurementPeriod = 32768; // 1 s
    USS_configAppTimerPeriod(&gUssSWConfig, gUssSWConfig.systemConfig->measurementPeriod);


    while (1) {
        // Perform data acquisition...
        // Perform signal processing...
        // ...
        USS_waitForAppTimerElapse(&gUssSWConfig,USS_low_power_mode_option_low_power_mode_3);
    }
}

This is how we use it too.

This should produce a constant measurement period of 1 s. However, we noticed that the period of the measurement cycle is not constant. The periods vary by +/- 30 us, which corresponds to one 32.768 kHz clock cycle.

To confirm, we also tried to reproduce it with the example from TI in the library. We added GPIO toggle:

And measured with PicoScope. The default version of the example shows:

--> constant measurement periods (< +/- 1 us)

However, we use channel swapping. Therefore, we tried to use channel swapping in the example too. Unfortunately the example is not compilable anymore, as soon as AP

PLICATION_ENABLE_CHANNEL_SWAP is set to true:

Seems expected? as version 02_30_00_03 changelog states:

> Removed USS_swapCaptureChannels API

So, as it was advised by TI in the past we re-added this function from version 02_20_00_18:

Like this, the example is compilable again.

Then, again we measured with PicoScope:

--> inconstant measurement periods (+/- 30 us)

Could you please check our setup? Maybe we are missing something?

How can we change the process to ensure USS_waitForAppTimerElapse() function produces constant measurement periods? -- Or one just needs to accept a jitter of +/- 32.768 kHz clock cycle?

2.) RTC keep-out window

The MSP430FR6xx user guide specifies for RTC_C:

128/32768 s = 4 ms

So we would expect the RTC to not be blocked for longer than 4 ms (i.e., time for which the CPU is not allowed to read out the RTC registers). However, we measured the time to be up to 8 ms with PicoScope.

So maybe we misunderstood the user guide specification and it is meant as follows?

"(...) centered approximately +/- 128/32768 s around the update transition, i.e., total duration of 256/32768 s. (...)"

Thank you very much!

RE: MSP430FR6047: inconstant measurement period

Timon Burkard — Wed, 30 Sep 2026 10:09:31 GMT

Hi Peter

1.

> our original demo code works fine with no issue but if you try to modify and enable the channel swapping which we remove it in the latest version, then the issue occur, is that correct?

--> Yes

> I think the timer function "USS_waitForAppTimerElapse()" here is just to make sure that the UPS0 to UPS1 gap is implemented properly and commonly not required high measurement accuracy, I wonder why do you need it measure so accurately and does it affect badly to your application?

--> Indeed, high accuracy usually not required. Still it is unexpected to see a jitter of +/- one 32 kHz cycle, in our opinion. Please could you try to reproduce?

> I would recommend please refer to them firstly to see if they could help you better understand it

Thanks, I read it. We do understand how the RTC functionality works. Our question is only about the user manual specification, which I think is not answered in the linked E2E threads.

RE: MSP430FR6047: inconstant measurement period

Peter Jiang — Tue, 29 Sep 2026 20:08:08 GMT

Hi Timon,

Thanks for the detailed testing information, sorry for the delay since there is a system issue that prevent us seeing this thread and I'm now on the holiday vacation.

Regarding your questions:

1. For the periods measurement jitter, I think your position for putting this function "USS_waitForAppTimerElapse()" in the main loop should be fine, let me clarify a little bit and please correct me if I misunderstand it, our original demo code works fine with no issue but if you try to modify and enable the channel swapping which we remove it in the latest version, then the issue occur, is that correct? if so, the issue seems point to this old function effect and we can try to dig more about it, since I'm now on the holiday until October 8th and no board on hand to reproduce it, kindly need your more patience to wait for the testing result on my side with this old function. In addition, I think the timer function "USS_waitForAppTimerElapse()" here is just to make sure that the UPS0 to UPS1 gap is implemented properly and commonly not required high measurement accuracy, I wonder why do you need it measure so accurately and does it affect badly to your application?

2. For the RTC, I found we already have some discussions in the E2E threads about it, not sure if you have taken a look, if not, I would recommend please refer to them firstly to see if they could help you better understand it.
MSP430F6779: Questions about the RTCRDY time

MSP430FR5994: RTC interrupt vector priority

Thanks

Best Regards,
Peter

ADS52J90EVM: High Speed Data Converter Pro not support ADS52J90EVM

Mario D — Wed, 16 Sep 2026 14:45:16 GMT

Part Number: ADS52J90EVM

Hello,

I am working with the ADS52J90EVM connected to the TSW14J50EVM capture card.

I noticed that the latest version of High Speed Data Converter Pro (v5.31) no longer includes support or configuration files for the ADS52J90 in the device drop-down menu.

Could you please provide a download link for an older version of HSDC Pro that supports the ADS52J90 ?

Thank you in advance for your support

MSP430FR6047: [MSP430FR6047] Schematic Review: Ultrasonic Flow Meter with 8-MUX LCD and RS485 Modbus

Phuong Dang — Mon, 14 Sep 2026 07:22:10 GMT

Part Number: MSP430FR6047

Hi TI Support Team, Could you please help review the schematic for our new custom Ultrasonic Flow Meter design based on the MSP430FR6047?
Please let me know if you need any additional information or design files.
Thank you for your support!

MSP430-SDK: MSP430FR6043EVM: Single Transducer Pulse-Echo Setup for AdBlue Quality/Density Measurement in USS GUI

yusuf seçilmiş — Fri, 11 Sep 2026 04:56:44 GMT

Part Number: MSP430-SDK

Hi TI E2E Team,

I am working with the MSP430FR6043 Ultrasonic Sensing Evaluation Module (EVM) and the Ultrasonic Sensing Design Center (USS) GUI.

My goal is to measure the concentration / quality of AdBlue liquid using a single ultrasonic transducer operating in a pulse-echo mode (transmit signal -> bounce off a fixed reflector -> receive echo on the same transducer).

Since standard flow-metering examples rely on a dual-transducer bi-directional setup (upstream/downstream), I would like to get step-by-step guidance on setting up a single-transducer pulse-echo configuration:

1. Hardware Connections:
Which specific channel header/pins should I use for connecting a single transducer for both pulse transmission and echo reception? Are any jumper configurations required on the MSP430FR6043EVM?

2. USS GUI Configuration:
How should I configure the System Configuration in the USS Design Center GUI for single-transducer operation (e.g., channel selection, gain settings, and capture window timing for liquid reflection)?

3. Software / USS Library Configuration:
How can I adapt the demo firmware (or USS Library parameters) in Code Composer Studio (CCS) to execute a single-ended pulse-echo capture sequence without expecting a second channel?

Thank you for your guidance and recommendations.

Best regards,

RE: TX08DEVM: TX08DEVM Question

yin lu — Wed, 02 Sep 2026 03:27:15 GMT

The explanation above is clear. However, the only document currently available on your website is the TX08D_Datasheet_Short_sbasaw7a.pdf. Are there any other more detailed technical documents (such as a full datasheet) for the TX08D chip? Additionally, is the schematic for the TX08DEVM available? We would like to obtain these resources to facilitate our upcoming custom system PCB design.

TX08DEVM: TX08DEVM Question

yin lu — Mon, 31 Aug 2026 10:25:32 GMT

Part Number: TX08DEVM

Does TI provide a recommended reference design or interface/adapter board for connecting TX08D to an actual piezoelectric probe? 
For real transducer evaluation, should we design a separate TX08D board based on the EVM schematic rather than modifying the TX08DEVM? 
What output damping/matching/protection network does TI recommend between TX08D and a 4 MHz piezoelectric array element? 
How should the TX08D T/R switch interface with the receive AFE in a pulse-echo system?Also, please share the detailed specs of the main chip and the schematics for the TX08DEVM board so we can use them for future application development."

RE: TX08DEVM: TX08DEVM Question

Roshan Divakar — Mon, 31 Aug 2026 17:27:09 GMT

Hi, no we don't have any reference design for connecting TX08D to a actual transducer. Ideally, our customers build their own system PCB which has the relevent HV Muxes and switches requried to map the TX08D channels to the transducer elements. As such, there is no damping or protection network requried. Regarding matching, the circuit will be highly dependent on the transducer load, and we don't have much exertise in the tuning circuits for the transducer. The TX08D has receive outputs which are the outputs of T/R Switch that can be connected to the AFE inputs.

TX08DEVM: TX08DEVM Troubleshooting

yin lu — Thu, 27 Aug 2026 01:34:38 GMT

Part Number: TX08DEVM

We are currently debugging the TX08D using the TX08DEVM.

The EVM powers up normally, the USB/GUI connection works correctly, and the initial diagnostics pass. However, when following the TX08DEVM User Guide (SBAU469) to generate both the built-in LIN waveform and a custom waveform, there is no LIN output, and the following errors are reported:

TX_START_ERR
LONG_TRAN_ERR_LIN

We have attached a short document including our test procedure, GUI settings, and oscilloscope waveforms.

Could you please help us check whether there is any issue with the configuration, synchronization/trigger settings, or operating sequence?

As we will continue developing with the TX08D, if possible, we would also appreciate being connected with a TI China technical support engineer/FAE. It would be very helpful if we could add each other on WeChat and create a small technical discussion group with our engineers for further debugging.

Thank you very much for your support.Waveform Troubleshooting Report.pdf

MSP430FR6045: Specifications for ultrasonic sensors used in ultrasonic water meters based on the MSP430FR6045

Kenichi Maruyama — Tue, 28 Jul 2026 06:02:04 GMT

Part Number: MSP430FR6045

Dear Sir or Madam,

I am currently considering the development of an ultrasonic water meter using the MSP430FR6045.

Could you please advise on the recommended ultrasonic sensor specifications required to achieve appropriate measurement performance when using the Ultrasonic Sensing Solution (USS) in the MSP430FR6045 for transit-time flow measurement?

In particular, I would appreciate any recommended values or acceptable ranges for the following parameters.

Information Requested

1. Recommended Center Frequency

Typical frequencies such as 1 MHz, 2 MHz, 4 MHz, etc.
Frequency ranges generally recommended for water meter applications

2. Sensor Capacitance

Recommended capacitance range
Capacitance range that can be supported by the USS circuitry

3. Electrical Characteristics

Impedance
Resonant frequency
Q factor
Recommended transmit voltage

4. Time Response Characteristics

Ring-down time (residual vibration decay time)
Impact on TOF (Time-of-Flight) measurement accuracy
Recommended values or limits

5. Sensor Configuration

Single-element transducer for both transmit and receive functions
Separate transmit and receive transducers
Recommended configuration

6. Experience in Water Meter Applications

Recommended sensor manufacturers
Recommended sensor part numbers
Sensors used in reference designs or evaluation platforms

7. Pipe Material Considerations

Any differences in recommended sensor specifications for metal and plastic pipe designs

Background

We are evaluating a transit-time ultrasonic flow measurement system based on the MSP430FR6045 USS. As part of our sensor selection process, we would like to understand the recommended transducer specifications from the microcontroller/system perspective.

If available, we would also appreciate information regarding sensor manufacturers and part numbers that have been successfully evaluated or used in similar applications.

Thank you for your support. We look forward to your guidance.

Best regards,

[Your Name]
[Company Name]
[Contact Information]

This wording is professional and is designed to encourage responses such as:

Recommended operating frequency (e.g., 1 MHz preferred)
Acceptable transducer capacitance range (e.g., 1–2 nF)
Maximum recommended ring-down time
Recommended or validated sensor manufacturers and part numbers (e.g., TDK, Prowave, Audiowell, etc.)
Sensors used in TI reference designs or customer applications.
In particular, we would appreciate it if you could recommend any ultrasonic sensors from Japanese manufacturers that are suitable for use with the MSP430FR6045.

In addition, if reference test data, expected performance metrics, or acceptance criteria are available for sensor and evaluation board combinations, please share them with us. Such information would be very helpful in establishing our evaluation and validation process.

RE: MSP430FR6045: Specifications for ultrasonic sensors used in ultrasonic water meters based on the MSP430FR6045

Kenichi Maruyama — Mon, 17 Aug 2026 00:54:46 GMT

Hello, Peter Jiang,

Thank you for your reply. I’ll use the information you provided to help me select a sensor.

TX08DEVM: Linamp not outputting signal on TX

Andrew Ouellette — Tue, 11 Aug 2026 19:08:36 GMT

Part Number: TX08DEVM

I've got the board setup as per the manual and can see an output on the HV Pulsar_Pat but nothing seems to be working in terms of the Lin_Amp_Pat section of the demo code.

Not sure if some enable box is missing somewhere along the setup process but I've tried most of the settings and have had no luck. All board diagnostics seem to be working.

RE: TX08DEVM: Linamp not outputting signal on TX

Roshan Divakar — Wed, 12 Aug 2026 04:48:35 GMT

Hello, that is expected as the latency to fetch the data from memory in Lin-Amp mode is longer than that of pulser. The latency details are mentioned in the datasheet which you can refer to.

RE: MSP430FR6045: Specifications for ultrasonic sensors used in ultrasonic water meters based on the MSP430FR6045

Peter Jiang — Wed, 12 Aug 2026 03:56:08 GMT

Hi Kenichi,

Sorry for the late reply since it might be some system issues that cause us missing this thread.

Based on the mass‑production experience together with our customers, we have included the transducer recommendations in the document FAQ on ultrasonic sensing technology(as shown below), Audiowell and Jiakang transducers are common, recommended choices and typically pair well with MSP430FR604x devices, the links in the document may not work but you can use the links provided below to view the recommended models. These models might be a bit outdated and of course, other new transducers from these recommended manufacturers with similar specifications can also be used.

JIAKANG 1MHz PSC1.0M020160H2AD0-B0

Audiowell Model：HS0003

Thanks

Best Regards,
Peter

RE: TX08DEVM: Linamp not outputting signal on TX

Andrew Ouellette — Tue, 11 Aug 2026 21:00:19 GMT

It appears the delay in the Linamp pulse relative to the trigger signal is significantly longer than in the regular HV pulsar.

MSP430FR6043: Design Review : Ultrasonic Water meter Using MSP430FR6043

Ezra Mohammed — Fri, 07 Aug 2026 21:55:01 GMT

Part Number: MSP430FR6043

Hi everyone,

We are currently working on a Smart Ultrasonic Water Meter using the TI MSP430FR6043 controller. Previously, we designed a two-layer board, but it barely functioned due to excessive noise. We have since redesigned both the PCB and the schematics. I would appreciate it if you could review our work and provide your feedback.
Smart Ultrasonic Water meter.pdf

TOP Layer SIgnal

2. Layer 2: GND

3: Layer 3: PWR + GND

Buttom Layer : GND
i splt the USS_GND and the GND and connect them by Net Tie

Thank you!
Ezra M.

TMUX9832: TMUX9832 Datasheet Request

Joshua M'Caw — Wed, 05 Aug 2026 08:21:34 GMT

Part Number: TMUX9832

Hi there,

I am looking to get access to the datasheet for the TMUX9832 chip. I submitted a request through the secure resources portal over a week ago, but have not heard anything back. Can anyone from TI help with this request?

MSP430FR5043: The transient abrupt change

Tommy — Tue, 04 Aug 2026 08:25:12 GMT

Part Number: MSP430FR5043

Hi E2E,

We measured the following data in the fluid laboratory:

What are some possible reasons for this data representation? What should we do?

AFE7960EVM-DOC-CERT: require python script bSocket.py

Russell Petherick — Tue, 28 Jul 2026 22:03:53 GMT

Part Number: AFE7960EVM-DOC-CERT

Hi.

I have the TX7516EVM kit and as part of my evaluation I need to control the Latte GUI from Matlab.

TI provides a python script to facilitate connection to the Latte server called 'bSocket.py' (see SBAA397)

can you please make this script available to me or provide documentation for the transmit header format so that I can implete my own script.

Thank you

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: 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

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: 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

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?