Sensors forum - Recent Threads

TMP112: What is the difference between these two components?

Mike Proscia — Wed, 14 Oct 2026 20:12:40 GMT

Part Number: TMP112

We have the Obsolete component listed, and we were attempting a drop in replacement. The alternate seems to be a drop-in replacement, but we cannot find information on the difference between the two.

OBSOLETE	ALTERNATE
TMP112AIDRLT	TMP112AIDRLR

What is the difference between the two listed components and can I use the Alternate as a drop-in repacement?

Thank you

IWRL1432BOOST-BSD: IWRL1432BOOST-BSD Error: mmWave factory calibration failed on EVK

manikandan k — Tue, 29 Sep 2026 05:38:07 GMT

Part Number: IWRL1432BOOST-BSD

Part Number: IWRL1432

Dear Team,

Hardware & Environment Details:
• Device / Board: IWRL1432 / IWRL1432BOOST-BSD
• SDK Version: MMWAVE_L_SDK_05_05_04_02
• CCS Version: 12.7.1.00001
• Radar Toolbox: 4.00.00.05
• Tested Binaries:
1. motion_and_presence_detection_demo.release.appimage (MMWAVE_L_SDK_05_05_04_02\examples\mmw_demo\motion_and_presence_detection\prebuilt_binaries\xwrL14xx-evm)
2. awrl1432_entry_level_blind_spot_detection (radar_toolbox_4_00_00_05\source\ti\examples\Automotive_ADAS_and_Parking\awrl1432_entry_level_blind_spot_detection\prebuilt_binaries)

Error Code -3141: MMWAVE_ERFSBOOTCAL (Factory Calibration Failure)
Error Code -3121: MMWAVE_ECALPERIOD (Calibration Periodicity / Timing Fault)

Debugging Steps & Observations:
1. Power Supply: Tested with an external 5V power supply to ensure sufficient current headroom during VCO/RF boot calibration bursts.
2. ATE Calibration Image Attempt: As part of debugging, we flashed the ATE Calibration image from SDK version MMWAVE_L_SDK_05_03_00_02 onto the board and executed readComPort.py. After switching back to Functional Mode and resetting the EVK, there was no response or UART output received from the device (verified the Application/User UART COM port and ensured no competing serial terminals were active).

Attached Log files.

profile_120m_40mpsec_bsdevm_16tracks.txt PresenceDetect Restore Disabled .txt PresenceDetect _Restore enable.txt

Thank you for your support.

Best Regards,

Manikandan K

RE: IWRL1432BOOST-BSD: IWRL1432BOOST-BSD Error: mmWave factory calibration failed on EVK

Josh Deardorff — Wed, 14 Oct 2026 18:07:47 GMT

Hi Manikandan,

Try the switch settings below, this is what I have on my EVM. DCA1000 is not required for debugging, so you should be good to go.

Switch	State
S1.1	On
S1.2	Off
S1.3	Off
S1.4	Off
S1.5	Off
S1.6	Off
S4.1	Off
S4.2	Off
S4.3	On
S4.4	Off

Here's the correct target config for xWRL1432 devices: e2e.ti.com/.../3542.AWRL1432.ccxml

There is no specific reset sequence required for debugging. However, try flashing the empty.release.appimage, found in <SDK_install_dir>examples/empty/xwrL14xx-evm/m4fss0-0_freertos/ti-arm-clang/, before starting the CCS debug session.

There also may be an issue connecting to the XDS110 probe with older versions of CCS. If the above doesn't help, try updating CCS to the latest version (CCS 21) and the XDS110 firmware that comes with it (emulation firmware v3.0.0.43), which should happen automatically.

Best,

Josh

RE: LDC5072-Q1-SENSOR-DESIGN-TOOL: LDC5072 Designer Workflow

Tyler Arsenault — Wed, 14 Oct 2026 17:43:14 GMT

Hey Chase, that had me up and running for a bit. I cleaned out the project, now I'm getting this cannot open EVM config file. It also beeps with some kind of windows error tone, but no indication why.

Any ideas?

LDC5072-Q1-SENSOR-DESIGN-TOOL: LDC5072 Designer Workflow

Tyler Arsenault — Thu, 08 Oct 2026 18:50:18 GMT

Part Number: LDC5072-Q1-SENSOR-DESIGN-TOOL

I'm working with the LDC5072 Sensor Designer. I've got a couple issues:

I'm looking for a bit more status on the optimizer in teh reporting window. I've put my design considerations in, but am not getting much insight into whats happening behind the scenes.
I tried to save the design, it came up with the prompt to select the location and file name, I hit the save button, but no file was written. :-/

AWR2188EVM: Cascaded channels, range-dependent phase drift

Stefan Zechner — Wed, 19 Aug 2026 13:56:18 GMT

Part Number: AWR2188EVM

We configure the AWR2188 as a cascaded system with full MIMO using all 16 Tx and 16 Rx channels simultaneously. A strong corner reflector at 25 m is used for the 0° channel calibration.

The test target is another corner reflector at 0° at a distances of 30 to 50 m. To compensate for sub-degree positioning tolerances, we estimate the exact angle via beamforming and correct for it in the phase mismatch plots below.

The 256 virtual channels are extracted from the exact same frame used for the 0° calibration. They are ordered as 16 Tx × 16 Rx, with the Rx channels being the innermost dimension.

The colors represent the Tx-to-Rx chip correspondence:

Blue: Master -> Master
Yellow: Master -> Slave
Green: Slave -> Master
Red: Slave -> Slave

There is a systematic phase shift across the different inter- and intra-channel groups, and this phase shift scales with the distance to the corner reflector.

Additionally, we tried these modifications:

Deactivate boot-up calibrations (except APLL, VCO, and Phase Shifter)
Deactivate HPF Fast Init
Set Tx/Rx Cal Data Retain
Vary various modulation parameters (sampling frequencies, start frequencies, ramp slopes, ADC start times, idle times, HPF frequency)

However, none of these adjustments remove the phase shift.

Any ideas on how to fix this?

Regards,
Stefan

corner reflector 30m:

corner reflector 35m:

corner reflector 40m:

corner reflector 45m:

corner reflector 50m:

RE: AWR2188EVM: Cascaded channels, range-dependent phase drift

Shailesh Joshi — Wed, 14 Oct 2026 17:18:33 GMT

Hi Stefan,

Ah! Unfortunate that we also could not get back with the inputs long before. But glad that it got resolved after all. Closing this one.

Regards,
Shailesh

RE: TMP468: TMP468: Wiring question consultation

Meredith McKean — Wed, 14 Oct 2026 16:58:02 GMT

Hi Zhan,

I see that you are wanting to measure remote temperature on a separate board. I highly recommend protecting your D+ with shielded cables. Please read the following app note: Optimizing Remote Diode Temperature Sensor Design (Rev. A)

Our remote temperature sensors (TMP4x) are designed for on board temperature measurements. I recommend adding protection for the D+ and D- cables.

Best Regards,

Meredith McKean

TMP468: TMP468: Wiring question consultation

Chance Zhan — Wed, 14 Oct 2026 08:51:48 GMT

Part Number: TMP468

As shown in the figure, if a few channels of the TMP468 are connected to test board A and the remaining channels are connected to test board B, while the TD pins inside the TMP468 are all connected to the D pins, then the TD pins of test boards A and B will be connected together and tied to the D pins of the TMP468. Would this wiring affect the accuracy of the 468? Is there any recommended wiring or solution?

RE: AWR2188EVM: Cascaded channels, range-dependent phase drift

Stefan Zechner — Wed, 14 Oct 2026 16:20:50 GMT

Hi Joshi,

shame on me. Your point 1 was absolutely right. I mixed up the M and S antenna positions.
Now all channels are aligned.

Let me share my corrected antenna positions which might hopefully help others.
Data is normalized to wavelength, and in format [Master Channel 1-8, Slave Channel 1-8] x [X, Y, Z]:

pos_tx = np.array([
[ 0. , 16.5, 0. ],
[ 0. , 18.5, 0. ],
[ 0. , 20.5, 0. ],
[ 0. , 22.5, 0. ],
[ 0. , 28.5, 0. ],
[ 0. , 24.5, 0. ],
[ 0. , 26.5, 0. ],
[ 0. , 30.5, 0. ],
[ 0. , 2. , 1.5],
[ 0. , 4. , 1.5],
[ 0. , 6. , 1.5],
[ 0. , 8. , 1.5],
[ 0. , 14. , 1.5],
[ 0. , 10. , 1.5],
[ 0. , 12. , 1.5],
[ 0. , 16. , 1.5],
])

pos_rx = np.array([
[ 0. , 17. , 15. ],
[ 0. , 19.5, 15. ],
[ 0. , 22. , 15. ],
[ 0. , 24.5, 15. ],
[ 0. , 30. , 15.5],
[ 0. , 27.5, 15.5],
[ 0. , 32.5, 15.5],
[ 0. , 25. , 15.5],
[ 0. , 0. , 14.5],
[ 0. , 2.5, 14.5],
[ 0. , 5. , 14.5],
[ 0. , 7.5, 14.5],
[ 0. , 12. , 15. ],
[ 0. , 10.5, 14.5],
[ 0. , 14.5, 15. ],
[ 0. , 9. , 15. ]],
)

Regards,
Stefan

AWRL6432BOOST: PCB Layer Stackup Thickness Clarification (Finished vs. Base Copper)

Lina Kim — Wed, 14 Oct 2026 15:59:18 GMT

Part Number: AWRL6432BOOST

Hello Team,

Customer have a question regarding the Bare PCB material and layer thickness configuration of the AWRL6432BOOST EVM board.

He is comparing two sources of thickness information:

Image 1: Layer thickness data confirmed in the Altium design file (red box highlighted values)

Image 2: Layer stackup table from the EVM documentation

[ Question ]

Could you please confirm whether the thickness values highlighted in the red boxes (from the Altium file) represent the Finished thickness — meaning the final thickness after all metal plating processes have been completed?

Specifically, I would like to confirm this for the following layers:

| Layer | Thickness (mm) in Altium |
|-------|--------------------------|
| Top Layer| 0.0406 |
| L2_GND1 | 0.0305 |
| L3_SIG1 | 0.0305 |
| L4_PWR1 | 0.0305 |
| L5_PWR2 | 0.0305 |

[ Background / Concern ]

> We want to clarify whether these values represent:
> - (A) Base Copper thickness — the raw copper foil before plating, or
> - (B) Finished Copper thickness — the final thickness after electroplating and surface treatment processes

This distinction is particularly important for the outer layers (Top Layer / Bottom Layer), as electroplating typically adds additional copper thickness beyond the base copper value.

For inner layers (L2_GND1, L3_SIG1, etc.), we understand that plating is generally not applied directly, so the base and finished thickness may be approximately equal — but we would appreciate official confirmation.

Thank you in advance for your assistance.

Best regards,

Lina

DCA1000EVM: Troubleshooting on DCA1000EVM // S608788

Lucas Lim — Thu, 08 Oct 2026 09:38:03 GMT

Part Number: DCA1000EVM

Hi TI team,

Good day!

Our customer purchased a Part# DCA1000EVM, but feedback to us that they tried to input 5V and 2.5 A through power supply, but the board didn't work. Please review and advise to below attachment "power on".

Could you kindly assist us to verify and advise whether this issue is considered as defective part? If not, could you advise on the setup or share some relevant supporting documents (user manual/ procedure) of this part for customer production reference.

Part details: Supplier PO# 029-HF628 // Qty shipped: 1pc // COO: IN // Date code: 2614.

Regards,

Lucas

Mouser Electronics, Inc.

RE: DCA1000EVM: Troubleshooting on DCA1000EVM // S608788

Ahanaf Ahmed — Wed, 14 Oct 2026 15:46:57 GMT

Hi Lucas,

This board seems to be defective. Please contact TI support for next steps!

Thanks,

Ahanaf

IWR6243: One of the Tx has low output power

Santhosh Nadig — Wed, 14 Oct 2026 09:45:33 GMT

Part Number: IWR6243

Hi,

We are testing our IWR6243 cascade system and have noticed that the output power of Tx2 of the slave device is lower (by 1.5 dB approx). Is this expected?

The procedure we use is as follows:
1. We do a initial RF calibration in an anechoic chamber (with no targets or disturbances present) and save the results to NVM.

2. We restart the device (when the RF calibration is restored from NVM) and transmit CW from one Tx at a time. The device is reset between switching Tx antennas.

3. We see that Tx2 of slave has approx. 1.5 dB lower output power.

4. In a previous firmware, there was a bug where the RF calibration data was only stored for the master device and was copied to both master and slave. In that case, the Tx2 power of slave was higher which was < 1 dB lower.

Can you please let us know if this is expected behavior or if there is something wrong with the procedure. Thanks!

BR
Santhosh

RE: IWR6243: One of the Tx has low output power

Cesar — Wed, 14 Oct 2026 15:38:06 GMT

Are you using mmwave_dfp_06_04_01_00?

Thank you
Cesar

IWR6243: Runtime calibration results in radar hanging

Santhosh Nadig — Thu, 27 Aug 2026 06:23:55 GMT

Part Number: IWR6243

We have implemented run time calibration of our two-chip cascaded IWR6243 system.

When temperature changes significantly, the following steps are performed:

1. Clear run time calibration status
2. Call rlRfRunTimeCalibConfig() with the following config:
calib_cfg.oneTimeCalibEnMask = PEAK_DET_CALIB;
calib_cfg.periodicCalibEnMask = 0U; // cascade: no automated periodic calibration
calib_cfg.calibPeriodicity = 0U; // one-time, not periodic
calib_cfg.reportEn = 1U; // emit RUN_TIME_CALIB_REPORT async event
calib_cfg.txPowerCalMode = 1U; // OLPC only, preserves cascade TX phase coherency
calib_cfg.CalTempIdxOverrideEn = 0; // use internal temp
calib_cfg.CalTempIdxTx = s.txIdx;
calib_cfg.CalTempIdxRx = s.rxIdx;
calib_cfg.CalTempIdxLodist = s.lodistIdx;

3. Wait for RL_RF_AE_RUN_TIME_CALIB_REPORT_SB or failure

We observe that:
1. We only get RL_RF_AE_RUN_TIME_CALIB_REPORT_SB from device 0 (master), but not from device 1.
2. These RL_RF_AE_RUN_TIME_CALIB_REPORT_SB messages come periodically (1 per second) even though periodic monitoring was not enabled (i.e., rlRfSetCalMonTimeUnitConfig was never invoked).

The result is that there is no ADC data. Could you help to resolve this issue?

Note:
Before the sensors are started, we apply one time RF calibration by setting temp bias to "Mid". This works and we do get RL_RF_AE_RUN_TIME_CALIB_REPORT_SB from both devices.

RE: IWR6243: Runtime calibration results in radar hanging

Cesar — Wed, 14 Oct 2026 15:36:58 GMT

Hi,

Still working on this with firmware team

thank you
Cesar

TMP112: SDA capability

Hanno Reimer — Wed, 14 Oct 2026 15:18:09 GMT

Part Number: TMP112

from my customer:

We are working on I2C/PMbus bus segmentation for our next version of HPM.

We need to balance rise-time, pullup strength and current draw.

I have some questions about the following TMP112 device SDA capability. Please direct to the relevant persons. We are on a tight timeline to finalise the board.

SDA drive capability for TMP112 is listed as 3mA. However this device is FM+ or better. Is this figure correct? 20mA is minimum in UM10204 specification for FM+ devices.

We are using this device at 3.3V.

IBIS model for SDA_33 shows 13.0mA for worst-case at 400mV Vol.

Which figure is more representative of the hardware?

TMAG5230: The customized product for TMAG5230

Zhang Liang — Wed, 14 Oct 2026 08:41:36 GMT

Part Number: TMAG5230

Hi,

We consider to use TMAG5230J1ZYBKR but this is not the commen product part# and TI suggest us to contact TI local representativ, and we need to know that how to order this customized product, thanks.

RE: TMAG5230: The customized product for TMAG5230

Scott Bryson — Wed, 14 Oct 2026 14:42:53 GMT

Zhang,

I can forward the request to our planning team, but will need more insight into the needed timeline for product availability and expected volume. Can you provide any of these details?

Thanks,

Scott

RE: LDC1312: settlecout issue

Eddie LaCost — Wed, 14 Oct 2026 14:30:47 GMT

Hello Allen,

Setting SETTLECOUNT above the design-tool value does not break normal operation — it only lengthens sensor activation time and therefore reduces your update rate. The evidence found does not document any instability or data-corruption mechanism caused by a larger SETTLECOUNT. In fact, TI reference designs deliberately exceed the calculated minimum for margin: TIDA-00615 computed a minimum of 8.4 and used SETTLECOUNT = 12 (0x000C) 1.

Why it is unlikely to be your latency problem

Parameter	Role	Timing
SETTLECOUNT	Sensor activation/settling before each conversion	tS = (16 × SETTLECOUNT) / fREF 2
RCOUNT	Conversion (measurement) time — usually dominates	tC = (16 × RCOUNT + 4) / fREF 2

Total time per data update = settling + conversion + channel switch + I²C readback, and conversion time generally dominates while channel-switch delay is much smaller 2. At fREF = 20 MHz, SETTLECOUNT = 10 is only 8 µs 3 — negligible versus a typical RCOUNT.

The design-tool values are sized for a valid, stable measurement (minimum SETTLECOUNT ≥ Q × fREF / (16 × fSENSOR) 3); they are not inherently optimized for minimum latency. For reference, the TIDA-00615 configuration with SETTLECOUNT = 12 and RCOUNT = 0x0100 achieves ~4.9 kSPS across two channels 1.

Where to look for the slow update instead

RCOUNT — reduce it to shorten conversion time. Note the opposite failure mode: RCOUNT = 0xFFFF has been linked to zero data and a conversion timeout because the oscillation count was not reached in the allotted time 4.
Read timing / DRDY — poll the DRDY status bit rather than assuming a fixed interval; the device needs the full conversion to complete before DATA is valid 5. At 400-kHz I²C a single-channel read takes ~130 µs, which consumes a large fraction of the 250 µs budget at 4 kHz sampling 6.
Sensor drive current — if you also see data freezing, note that one reported case of data not updating was traced to excessive drive current producing ~2.0 Vpk-pk sensor oscillation, above the recommended range — not to SETTLECOUNT 7.

LDC1312: settlecout issue

Allen Chu — Wed, 14 Oct 2026 06:18:09 GMT

Part Number: LDC1312

Hello,

We are using LDC1312.

Can the given parameters in the file ensure stable and fast data collection for LDC1312 when using settlecout according to Inductive Sensing Design Calculator Tool the Excel parameters designed on the official website and given to the corresponding registers?

We are currently testing the target object and after analysis, we found that ldc1312 cannot immediately update the response data to the corresponding register after the target object changes.

Will setting the value of settling cout beyond the value given in the design Excel affect the normal operation of LDC1312?

RE: IWRL6432: Converting raw ADC samples to/from absolute RF signal levels at the RX input pin

Ankit Mohanty — Wed, 14 Oct 2026 13:30:12 GMT

Hi Lina,

I checked with our internal teams.

[quote userid="555065" url="~/support/sensors-group/sensors/f/sensors-forum/1684516/iwrl6432-converting-raw-adc-samples-to-from-absolute-rf-signal-levels-at-the-rx-input-pin/6496049"]Is there any documentation or characterization data available for the RX phase response across IF frequency?[/quote]

There is no such documentation or CZ data for RX phase response across IF frequency.

[quote userid="555065" url="~/support/sensors-group/sensors/f/sensors-forum/1684516/iwrl6432-converting-raw-adc-samples-to-from-absolute-rf-signal-levels-at-the-rx-input-pin/6496049"]Is per-channel phase correction information provided (or measurable via SDK), for use in complex beat signal comparison across RX channels?[/quote]

RX phase calibration is already included in the low power SDK. However, not independently measurable/accessible for each RX channel by the customer.

Regards

Ankit

IWRL6432: Converting raw ADC samples to/from absolute RF signal levels at the RX input pin

Lina Kim — Wed, 23 Sep 2026 01:43:32 GMT

Part Number: IWRL6432

Hellon Team,

Customer is working on converting raw ADC samples to/from absolute RF signal levels at the RX input pin of the IWRL6432, and I have the following questions.

1. ADC Full-Scale Input Voltage

What is the full-scale input voltage of the radar ADC?

Is it specified as Vpeak or Vpp?
Is it referenced to a differential or single-ended basis?

2. 12-bit RDIF Output Encoding & DFE Scaling

What is the encoding format of the 12-bit RDIF output?
(e.g., two's complement, offset binary, etc.)
Are there any DFE gain, scaling factors, or bit shifts applied that affect the captured samples?

3. Relationship Between RF Input Power, RX Gain, and ADC Level

I need the complete relationship among:

RX input power at the pin [dBm]
Configured RX gain (including LNA gain, mixer conversion gain, and IF/BB gain)
ADC level [dBFS]

Specifically:

How is dBFS defined in the context of the IWRL6432 ADC?
(Peak-referenced? RMS-referenced? Based on full-scale code = 2047?)
What is the applicable IF frequency range over which this relationship holds linearly?

4. RX Phase Response / Channel Phase Correction

Is there any documentation or characterization data available for the RX phase response across IF frequency?
Is per-channel phase correction information provided (or measurable via SDK), for use in complex beat signal comparison across RX channels?

Additional Request

If possible, could you provide a worked numerical example using IWRL6432-specific values or point me to the relevant section in the IWRL6432 datasheet or technical reference manual?

Reference

I found a similar discussion for the AWR1243 which was helpful as a starting point:
AWR1243 – Receiver In-Band P1dB and RF Input to I/Q Output Gain

Any IWRL6432-specific clarification or pointers to relevant documents would be greatly appreciated.

Regards,

Lina

AWR2188EVM: Validated hardware and software combination

Daisuke Maeda — Fri, 09 Oct 2026 09:07:09 GMT

Part Number: AWR2188EVM

Our customer observes that both awr2188_single_chip_data_capture and awr2188_two_chip_cascade_data_capture get stuck in WAITING_FOR_DATA.

They used the following hardware and software combination:

mmWave Studio 4.5.4.0
GUI 4.5.4.0
Studiolink 4.0.6.2
Radarlink 4.0.6.2
PostProc 05.82

HW_VERSION: DCA2000EVM Rev A
SW_VERSION: 0.9.8.4a, 0.9.8.4b

cli_version 0.9.5

AWR2188EVM Rev.C
ES2.0

DFP 4.0.6.7

I have checked the posts below, but the recommended combination is not clear.

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1669358/awr2188evm-no-data-from-dca2000-waiting_for_data

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1666067/awr2188evm-error-timed-out-waiting-for-capture-to-complete-capture_status-was-no_capture

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1637914/awr2188evm-awr2188evm-stuck-in-waiting_for_data

It is mentioned that the recommended hardware combination for the AWR2188EVM Rev.C is the DCA2000EVM Rev.B. But the customer is using the DCA2000EVM Rev.A.

What is the recommended software combination for using the AWR2188EVM Rev.C with the DCA2000EVM Rev.A?

Best regards,

Daisuke