传感器论坛 - 最近的话题

IWR6843: Regarding the calculation issue of the pitch angle for IWR6843ISK

tianyu yin — Tue, 01 Sep 2026 08:43:00 GMT

Part Number: IWR6843

In the calculation of the pitch angle for IWR6843ISK, the phase difference method is used to calculate the target pitch angle. Should the antennas in the vertical direction be selected as 3 and 5 or 1 and 5? Is it because 3 and 5 have no horizontal difference but only height difference that they should be chosen?

LMP91000: LMP91000SD可以监测输出负电流的传感器吗？

pei fuhao — Tue, 01 Sep 2026 07:39:57 GMT

Part Number: LMP91000

传感器的参数如下图所示

MMWAVE-STUDIO-2G: 无法下载对应的mmwave studio 2G软件，权限遭拒

Li lan — Mon, 31 Aug 2026 15:52:32 GMT

Part Number: MMWAVE-STUDIO-2G

MMWAVE-STUDIO: mmwave studio download

Li lan — Sun, 30 Aug 2026 10:33:47 GMT

Part Number: MMWAVE-STUDIO

Why refuse my softwave download limitation?

TMAG5170: TMAG5170 unexpected behavio

zhenjun gao — Fri, 28 Aug 2026 12:33:18 GMT

Part Number: TMAG5170

Usage scenario: The TMAG5170 sensor board and ESP32‑C6 board are connected via approximately 10 cm ordinary wires. When a magnet with a magnetic‑field strength of about 60 mT is brought close to and moved away from the sensor standalone, magnetic‑field variations can be detected by the sensor. Overshoot is observed on the clock signal during tests, which is improved by adding a series‑connected 33 Ω resistor.

It is a 2‑layer PCB as shown in the figure below. Is the PCB layout unreasonable?

With the sensor board mounted between two magnets, the SPI SCLK is pulled down to around 1 V. No output is present on SPI MISO, whereas MOSI and CS waveforms look normal. See the figure below for the clock signal.

IWRL1432: 同一组adc数据，用hwa做fft的结果与matlab fft结果不一致。

user5977184 — Thu, 27 Aug 2026 07:46:25 GMT

Part Number: IWRL1432

同一组adc数据，红色是matlab fft DB图，蓝色是HWA的fft DB图。

做的是4096点fft。调节scale与butterflyScaling，可以得到以下两种。第一种是大部分曲线是重合的，但是个别处差的挺多。第二种是不重合，但曲线趋势一致。哪种曲线更好呢？

AWR1843AOPEVM: AWR1843AOPEVM 连接失败

longlong ma — Mon, 24 Aug 2026 12:34:42 GMT

Part Number: AWR1843AOPEVM
Other Parts Discussed in Thread: DCA1000EVM,

AWR1843AOPEVM 通过 mmWave Studio 和 DCA1000EVM 连接失败

我确认了我的设置和网络服务器设置都与与用户手册中的保持一致,PC也能正确读取设备串口,但是就是无法在 mmWave Studio 中连接
这个是错误代码!
[20:09:29] [RadarAPI]: ar1.Calling_IsConnected()
[20:09:29] [RadarAPI]: ar1.SaveSettings('C:\Users\think\AppData\Roaming\RSTD\ar1gui.ini')
[20:18:57] [RadarAPI]: Opening Gpio Control Port()
[20:18:57] [RadarAPI]: Status: Passed
[20:18:58] [RadarAPI]: Opening Board Control Port()
[20:18:58] [RadarAPI]: Status: Passed
[20:18:59] [RadarAPI]: ar1.FullReset()
[20:18:59] [RadarAPI]: Status: Passed
[20:19:00] [RadarAPI]: Closing Board Control Port()
[20:19:00] [RadarAPI]: Status: Passed
[20:19:00] [RadarAPI]: Closing Gpio Control Port()
[20:19:00] [RadarAPI]: Status: Passed
[20:19:00] [RadarAPI]: ar1.SOPControl(2)
[20:19:00] [RadarAPI]: Status: Passed
[20:19:01] [RadarAPI]: ar1.Connect(99,115200,1000)
[20:19:03] [RadarAPI]: Error: Connection failed: Calling_ConnectTarget returned 3
[20:19:03] [RadarAPI]: ar1.Calling_IsConnected()
[20:19:03] [RadarAPI]: ar1.SaveSettings('C:\Users\think\AppData\Roaming\RSTD\ar1gui.ini')

我在按照手册进行了探索之后发现无法解决问题,
模块可以通过 mmWave_Demo_Visualizer 3.6.0 进行连接,硬件正常,没有损坏,这块DCA1000EVM 是全新的
希望技术团队能解答我的困惑,非常感谢!

TMAG5170: TMAG5170使用异常问题

zhenjun gao — Mon, 24 Aug 2026 08:46:56 GMT

Part Number: TMAG5170

您好，

使用TMAG5170，软件工程师使用官网驱动程序，三轴输出均为0mT，见下图：

单独测试SPI信号见附件:

测试SPI信号-2026.8.24.docx

本测试环节硬件连接：传感器板卡输出SPI信号经约10cm导线连接到同事开发板上，见下图：

请问出现此问题，是硬件问题吗，因为单独测试软件控制的时钟，片选和输入信号波形均正常，如何进行下一步排查问题，通过按键开关单独控制传感器的时钟，片选，看输出信号波形

请帮忙推荐合适排查方案。

谢谢！

OPT3007: lead frame 信息调查

chen yanru — Mon, 24 Aug 2026 06:29:37 GMT

Part Number: OPT3007

你好，

下表为我司购买贵司产品，现在想了解这些产品是否涉及lead frame，请帮忙解答。

以上，祝好。

物料信息调查-TI.xlsx

OPT3007: lead frame 信息调查

chen yanru — Mon, 24 Aug 2026 06:28:15 GMT

Part Number: OPT3007

你好，

下表为我司购买贵司产品，现在想了解这些产品是否涉及lead frame，请帮忙解答。

以上，祝好。

物料信息调查-TI.xlsx

LM335A: 如果存在反向电压，是否代表器件已经损坏

Aiwens Yuan — Mon, 24 Aug 2026 05:08:57 GMT

Part Number: LM335A

使用246pcs，其中58pcs发现存在0-2v的反向电压，这58pcs是否已经损坏了？我们提供的正向电压是3V

LM335A: 如果存在反向电压，是否代表器件已经损坏

Aiwens Yuan — Mon, 24 Aug 2026 05:07:20 GMT

Part Number: LM335A

使用246pcs，其中58pcs发现存在0-2v的反向电压，这58pcs是否已经损坏了？我们提供的正向电压是3V

TMAG5273: TMAG5273A1检测磁铁位移量

q q — Mon, 24 Aug 2026 02:32:34 GMT

Part Number: TMAG5273

请问原厂的技术支持们，有什么好的方法能够使用多个TMAG5273A1霍尔传感器等距沿直线分布时，磁铁正极正对霍尔X轴方向，磁铁沿霍尔Y轴方向上下移动，有什么方法能够精确检测磁铁的所在位置和位移量？

AWR2944: AWR2944 MCAN: TX buffer cancellation (TXBCR/TXBCF) never completes when CCCR.INIT is set while a transmission attempt is in progress — ECU hangs in Can_mcanStop

hui lu — Fri, 21 Aug 2026 10:48:21 GMT

Part Number: AWR2944

Part: AWR2944
SDK / MCAL version: 04.07.01.03
IP: Bosch M_CAN (MCAN peripheral)

=== 1. Setup ===

We are running a UDS 0x11 0x01 (ECU reset) stress test on AWR2944:
- Two MCAN controllers are active:
- MCAN1 @ 0x02040000 ("public" CAN, connected to the tester which ACKs)
- MCAN2 @ 0x03040000 ("private" CAN, no other node connected on this bench — dangling bus, no ACK)
- Auto retransmission is ENABLED (CCCR.DAR = 0).
- The application transmits periodic frames on the private CAN from early boot
(unconditionally, ~20 ms period).
- Consequence on the dangling bus: the first private-CAN frame fails with no ACK
and enters permanent retransmission; the controller goes error passive
(PSR: LEC=7 "no ACK", EP=1, BO=0) and TXBRP stays 0x1 indefinitely.

The MCAL Can driver's Can_mcanStop() performs, in this order:

1. MCAN_setOpMode(base, MCAN_OPERATION_MODE_SW_INIT); /* set CCCR.INIT */
2. poll MCAN_getOpMode() until INIT is reached;
3. read TXBRP, and for each pending buffer:
MCAN_txBufCancellationReq(base, bufIdx); /* write TXBCR bit */
poll until (TXBCF & bit) == bit; /* <-- wait loop */

On each ECU reset (warm reset), the next boot calls Can_mcanStop() again on both
controllers (communication bring-up does STOPPED -> STARTED). So every reset
cycle exercises this cancel path while the private-CAN frame is stuck in
retransmission.

=== 2. Phenomenon ===

Out of ~3000 reset cycles, ~40 runs (~1.3%) hang in the TXBCF wait loop of
Can_mcanStop() on the private CAN (0x03040000). After the hang the ECU never
finishes booting and the public CAN stays silent (the tester declares a failure
after 10 s of bus silence).

Paired logs — identical register state at stop entry, opposite outcomes:

FAIL (hang):
[CanStop ENTRY] base=0x3040000 TXBRP=0x1 TXBTO=0x0 TXBCF=0x0 LEC=7 BO=0 EP=1
cancel request for buffer 0 issued (TXBCR bit 0 written while in INIT mode)
-> TXBCF never sets, TXBRP never clears, loop spins forever

PASS (same bench, seconds later):
[CanStop ENTRY] base=0x3040000 TXBRP=0x1 TXBTO=0x0 TXBCF=0x0 LEC=7 BO=0 EP=1
cancel request for buffer 0 issued (TXBCR bit 0 written while in INIT mode)
-> TXBRP=0x0, TXBCF=0x1: cancellation completes immediately

The only difference between the two runs is the (invisible) internal state of
the TX buffer / message handler at the moment TXBCR is written.

=== 3. Our analysis (please confirm) ===

Per the M_CAN documentation, cancellation of a Tx buffer is DEFERRED until the
ongoing transmission attempt ends if the cancellation request hits a buffer that
is currently being transmitted. Setting CCCR.INIT freezes the CAN protocol
engine, so a transmission attempt interrupted by INIT never "ends".

Therefore we believe:
- If TXBCR is written while the buffer is merely PENDING ( arbitration not yet
won / attempt not started), the cancel is served even in INIT mode — matches
our PASS log (INIT clearly does not freeze the buffer manager itself).
- If TXBCR is written while the buffer is MID-TRANSMISSION-ATTEMPT, the cancel
is deferred "until the attempt ends", but INIT has frozen the protocol engine
so the attempt can never end -> TXBCF never sets -> indefinite wait.
- On a bus with a healthy ACKer this window is microseconds wide (rare hit);
on our no-ACK bus with auto-retransmission the controller is essentially
always inside a retransmission attempt, so the stop path faces this state
every single boot.

=== 4. Questions ===

Q1. Can you confirm the M_CAN behavior on AWR2944: after CCCR.INIT = 1, is a
cancellation request (TXBCR) for a buffer whose transmission attempt was
interrupted by INIT ever served? Is there any condition under which TXBCF
will set in this state, or is it a permanent deadlock?

Q2. What is TI's recommended sequence to stop/disable MCAN when Tx buffers may
be active — should all pending transmissions be cancelled (TXBCR + wait for
TXBCF, with a timeout) BEFORE setting CCCR.INIT? Is there an app note or
newer MCAL drop that reorders Can_mcanStop this way?

Q3. In INIT mode with auto-retransmission enabled and no ACK on the bus, is the
intended recovery path a peripheral reset (MCAN module reset via CTRL_MMR /
TopRCM), since software cannot force the deferred cancellation to complete?

Q4. Is this a known limitation/erratum of the M_CAN integration, and is there an
E2E thread or TI MCAL release note that documents the TXBCR/TXBCF/TXBRP
interplay with CCCR.INIT?

Any guidance is appreciated. We can provide the full paired logs and the exact
register readouts on request.

AWR2944: AWR2944 MCAN: TX buffer cancellation (TXBCR/TXBCF) never completes when CCCR.INIT is set while a transmission attempt is in progress — ECU hangs in Can_mcanStop

hui lu — Fri, 21 Aug 2026 10:47:34 GMT

Part Number: AWR2944

Part: AWR2944
SDK / MCAL version: 04.07.01.03
IP: Bosch M_CAN (MCAN peripheral)

=== 1. Setup ===

The MCAL Can driver's Can_mcanStop() performs, in this order:

=== 2. Phenomenon ===

Paired logs — identical register state at stop entry, opposite outcomes:

The only difference between the two runs is the (invisible) internal state of
the TX buffer / message handler at the moment TXBCR is written.

=== 3. Our analysis (please confirm) ===

=== 4. Questions ===

Q4. Is this a known limitation/erratum of the M_CAN integration, and is there an
E2E thread or TI MCAL release note that documents the TXBCR/TXBCF/TXBRP
interplay with CCCR.INIT?

Any guidance is appreciated. We can provide the full paired logs and the exact
register readouts on request.

AWR1843BOOST: 我使用 mmWave Studio + DCA1000 采集毫米波雷达数据，数据录制流程本身全部执行成功，但在自动触发 Matlab 后处理（PostProc）时抛出错误

HaoRan Zhang — Fri, 21 Aug 2026 04:48:57 GMT

Part Number: AWR1843BOOST

DRV401: check shelf life

Bao lina — Mon, 17 Aug 2026 09:23:38 GMT

Part Number: DRV401

Dear TI team,

Regarding the 'DC2624+5' noted in the attachment, does the '+5' imply a 5-year extended validity (shelf life)?

There used to be an explanation on the website regarding this 5-year extension, but I can no longer locate it. Could you kindly clarify the specific meaning of the '+5' suffix?"

Clara.luo@aurightec.com

DRV401: check shelf life

Bao lina — Mon, 17 Aug 2026 09:22:21 GMT

Part Number: DRV401

Dear TI team,

Regarding the 'DC2624+5' noted in the attachment, does the '+5' imply a 5-year extended validity (shelf life)?

There used to be an explanation on the website regarding this 5-year extension, but I can no longer locate it. Could you kindly clarify the specific meaning of the '+5' suffix?"

Clara.luo@aurightec.com

DRV401: check shelf life

Bao lina — Mon, 17 Aug 2026 09:17:37 GMT

Part Number: DRV401

Dear TI team,

Regarding the 'DC2624+5' noted in the attachment, does the '+5' imply a 5-year extended validity (shelf life)?

There used to be an explanation on the website regarding this 5-year extension, but I can no longer locate it. Could you kindly clarify the specific meaning of the '+5' suffix?"

Clara.luo@aurightec.com

TMP106: TMP106YZC丝印

tianda wu — Fri, 14 Aug 2026 05:53:32 GMT

Part Number: TMP106

最近在使用时，发现TMP106YZC丝印有两种：23MF7P和3CTF7P。请问丝印每位的含义是什么？这两款芯片是同一种吗？

IWR6843ISK: 关于IWR6843iSK直接通过ttl转usb烧录bin文件的问题

lou shengshu — Fri, 14 Aug 2026 03:45:45 GMT

Part Number: IWR6843ISK
Other Parts Discussed in Thread: UNIFLASH,

我现在想在TI官方的原理图上，修改IWR6843isk，从芯片上直接引出TX/RX信号，使用杜邦线和ttl转usb连接电脑，在供电和SOP模式正确的情况下，能否直接使用uniflash向板内烧录bin文件？目前iwr6843isk的usb转uart部分已经被删除。

IWR6843AOP: BSSFW能加载进去，MSSFW加载不进去，求解。

yang yun — Thu, 13 Aug 2026 08:17:49 GMT

Part Number: IWR6843AOP

TDC1000: TDC1000 RX接收回波后波形衰减，LNA和PGA失效分析

rongzhi yao — Tue, 11 Aug 2026 12:53:52 GMT

Part Number: TDC1000

不明白为啥经过TDC1000之后增益反而变差，麻烦帮忙分析一下，LNAOUT->PGAIN使用1nF电容连接

OPT4001: 焊盘脱落

switch — Tue, 11 Aug 2026 12:48:41 GMT

Part Number: OPT4001

Hi ti team,

这次一共生产了100PCS,出现1PCS光感不良，使用万用表量测光感4个PIN的二极管压降，确认是光感到FPC板子有1个Pin线路断开了，用手指轻轻一碰，光感就掉了，整个光感IC元件的4个焊盘都剥离到了FPC板上，请帮忙分析下原因及建议？Thanks！

HDC3022: HDC3022精度问题

zhao xiliang — Fri, 07 Aug 2026 07:51:28 GMT

Part Number: HDC3022

我做了两个传感器，每个传感器都集成了一个HDC3022和一个SHT45传感器，在同一环境进行测试（接近纯干），测量结果一个湿度为2.2左右，一个为7.6左右。在8个月前相同情况下的测试，两个传感器显示的湿度值都小于1% 。通的都是空气，我想请问这是什么原因。