https://e2e.ti.com/support/sensors-group/sensors/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1666914/iwrl6432aopevm-pose_and_fall_detection-demo-project-go-into-debugp_assert-in-mmwave_gettemperaturereport/6432292Wed, 29 Jul 2026 03:05:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f8ec43c2-502f-427e-a64a-445966c49371Yuan Knoxyes， default code and iwrl6432aopevm, no any changeshttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1666914/iwrl6432aopevm-pose_and_fall_detection-demo-project-go-into-debugp_assert-in-mmwave_gettemperaturereport/6432283Wed, 29 Jul 2026 02:53:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:730f271e-0b94-4311-b6bd-845d508c0432Adam HuaKnox, Could you please reply to what Nafisi ask? [quote userid=&quot;519338&quot; url=&quot;~/support/sensors-group/sensors/f/sensors-forum/1666914/iwrl6432aopevm-pose_and_fall_detection-demo-project-go-into-debugp_assert-in-mmwave_gettemperaturereport/6430234&quot;]Are you running into this issue with default code and EVM? Or were there any changes before seeing this temp sensor error?[/quote] Regards, Adam Huahttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1668433/awr2188evm-awr2188evm-inquiry-regarding-purchase-availability-and-request-procedureWed, 29 Jul 2026 00:30:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:24e26aa3-0c3f-470a-b353-44adad6fc9f0jeong hoon ParkPart Number: AWR2188EVM Hello TI Support Team, We are developing a radar system and would like to purchase the AWR2188EVM for evaluation. Could you please guide us on: Current availability and lead time for the AWR2188EVM The process or requirements to place an order (or connect with a local sales rep) Thank you, and I look forward to your response. Best regards,Advanced Driver Assistance Systems (ADAS)AWR2188EVMhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1666352/dca1000evm-dca1000evm-failure----all-leds-blinking/6432182Wed, 29 Jul 2026 00:19:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:6e058404-ec18-4b21-ad62-231d341d3492David GuirgisHey Ethan, Are they maybe showing up in the unassigned Port section? Thank you, Davidhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1667538/ldc1612-nacks-final-config-byte-when-exiting-sleep-mode-despite-valid-id-and-reset-register-reads/6432141Tue, 28 Jul 2026 23:14:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:55e52d8b-583c-46e8-8f6c-475c9bd4473cChase GirardHi Nikolaus, I am still looking for the information you requested and I will provide it to you once I have located it. I would recommend always testing with the coils connected to prevent any unrelated issue. The Q factor and actual coil dimensions would be helpful as well. Also, please send me the scope captures for those signals. If you have any questions in the meantime, please let me know. Best regards, Chase Girardhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1668428/iwr6843aop-fov-origin-in-order-to-do-a-radomeTue, 28 Jul 2026 22:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2413ecaf-f7a4-48aa-9662-92755aff9794Rodrigo Lopes CattoPart Number: IWR6843AOP Hi, We are currently designing a protective radome around the IWR6843AOP and would like to ensure that the enclosure does not obstruct the antenna’s approximately 120&#176; &#215; 120&#176; field of view, disturb the radiation pattern, or introduce unwanted reflections. We are trying to determine the correct reference point—or apex—from which the specified field of view should be projected when defining the radome geometry and antenna keep-out region. We are currently considering two interpretations: The field of view originates from the center of the antenna array. The field-of-view boundaries are projected from the outer edges of the antenna array. The attached images illustrate these two approaches. Could you please clarify which method is recommended for mechanical and radome design? Is there a specific reference point, antenna aperture boundary, or keep-out volume that should be used when designing an enclosure around the IWR6843AOP? Any additional guidance regarding recommended clearances or radome geometry near the antenna would also be greatly appreciated. Thank you!IWR6843AOPhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1668237/fdc1004-q1-fdc1004-stable-liquid-level-measurement-under-mechanical-deformation/6432070Tue, 28 Jul 2026 21:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f73085bc-2a0d-4450-9594-bf2d8e620ad3Eddie LaCostHello Ansu, I am researching this topic. I will get back to you within 24hrs with what I find.https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1668131/pga970-technical-support-request-pga970-spi-miso-signal-inactive-flat-with-usb2any-interface/6432039Tue, 28 Jul 2026 21:26:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ae4f5aa1-46e4-4abc-8c6e-d2fdd30baf26Maggie LeeHi, The digital interface button should be active in the GUI for SPI communications: Thanks, Maggiehttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1666838/pga970-pga970-spi-communication-failure-and-request-for-dac-adc-configuration-guides/6432030Tue, 28 Jul 2026 21:20:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b37a4235-38cd-44a4-b879-39123609c6d5Maggie LeeHi, By default, when the device powers on, the SPI interface is enabled. So unless you have written any firmware to the device which overwrites this register on power-up, SPI will always be enabled when the device is power-cycled. The PGA970 has an internal microcontroller, which has two states, running or reset. When the device is halted, the user has access to the digital interfaces, including SPI, which are used to communicate with the device. In order to use SPI, you must write 0x03 to the following register: Thanks, Maggiehttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1668368/ldc2112-question-on-reset-timing/6431992Tue, 28 Jul 2026 20:42:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:046734a3-abd0-4f3c-82be-61b3dc0abda0Cameron PerlHi Amanda, Please do - it&#39;s confusing as FULL_RESET is not calling out that it is running a power-cycle. Can you also please confirm with them if the device is forcing itself into a register write cycle to modify its address when the ADDR pin is pulled high and that is what is causing the difference in how long it takes the device to reset? Thanks, Camhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1649996/tdc1000-c2000evm-tdc1000-c2000evm-only-read-31us/6431988Tue, 28 Jul 2026 20:38:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e08e22b5-1748-411c-8e71-4c3fa4d20316Fernando MoraesHi Amanda, One transducer. Purple is the COMPin signal. Yes Tx and Rx are in the same line. Thankshttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1649996/tdc1000-c2000evm-tdc1000-c2000evm-only-read-31us/6431972Tue, 28 Jul 2026 20:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:2d48c93c-1594-4db6-b29a-3fbdbfb6ba72Amanda RatliffThank you very much Fernando, Are you using two transducers currently? What is the purple signal probing? On a single transducer TX and RX would be on the same line? Best, Amandahttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1668368/ldc2112-question-on-reset-timing/6431971Tue, 28 Jul 2026 20:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0e330e5b-ca16-490f-ae0a-83e26f8d1a11Amanda RatliffHi Cam, Thank you for posting to the sensors forum! We do not currently have any collateral that outlines the duration of the FULL_RESET cycle, however this may be a good idea to publish in the future. Thank you for bringing this to our attention. Based on available documentation, it looks like your observations align with expected behavior. Based on the description included for FULL_RESET, the device will automatically reset to default configuration and return to normal operation once the ready status is set. The default configuration would be ADDR = 0x2a. Since ADDR = 0x2b is not a default configuration, the device would have to undergo additional steps outlined in the power on reset cycle to rewrite the register. I can reach out to our design team if necessary to confirm details of these two power cycle options. Best, Amandahttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1666874/iwrl6432aopevm-iwrl6432aop-mmwave-1d-sensing-user-guide-error-no-data-detected-on-com-port-read-timed-out/6431958Tue, 28 Jul 2026 20:12:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:24b7ebed-2aca-4d82-ab5e-6a9ca1df1398David CassityHi Eugene, The ERROR [gui_parser.py:190] only occurs when the device becomes disconnected from the visualizer. At the very beginning of the terminal when using the Industrial_Visualizer.exe, does it say something like this: INFO [gui_core.py:296] Data COM Port found: COM5 INFO [gui_core.py:287] CLI COM Port found: COM4 I can only assume it does because the terminal later says you are connected to a port, but I want to check all the boxes. I tested the switch settings of both images you sent, and both were able to run the 1D Sensing demo on the visualizer. Have you tried using a different USB cable? This is tricky since if both are behaving the same way, the likelihood both are broken is very unlikely unless they were both stored improperly or something to that effect. Best, Davidhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1665449/iwr6243-lo-power-requirements-for-iwr6243/6431953Tue, 28 Jul 2026 20:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3dbb8e90-198d-4410-abcd-583f53a4eb39David GuirgisHi Maximilien, The FM_CW_SYNCOUT (or FM_CW_CLKOUT) pins on the IWR6243 are designed as driver outputs. In a typical configuration they deliver about 7 dBm (≈5 mW) at 20 GHz. The FM_CW_SYNCIN pin, on the other hand, is a receiver input that is only rated for ‑40 dBm to +3 dBm. Because of that mismatch, the sync signal must be attenuated before it is fed back into the same device (or into another IWR6243). The attenuation does not have to be “heavy” in the sense of a large power loss – you just need to bring the level down by ≈ 4–6 dB to stay comfortably under the +3 dBm limit and give you some margin for board‑level variations. Thank you, Davidhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1667341/tusb7340-tusb7340-no-usb-activity-since-we-changed-batch-number/6431951Tue, 28 Jul 2026 20:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:a740227b-0cad-4692-85c6-d8a0741c29d2Vishesh PithadiyaHi, Are you able to perform an ABA swap one the working board to see if the issue follows PF0H devices?https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1663604/awr2188-access-request-for-awr2188-restricted/6431925Tue, 28 Jul 2026 19:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3eebf6e5-146d-481f-a528-4339409b29daDavid GuirgisHi Hayim, I just reached out I have not recieved any updates yet. I will let you know as soon as I hear a response from them, Thank you, Davidhttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1649996/tdc1000-c2000evm-tdc1000-c2000evm-only-read-31us/6431913Tue, 28 Jul 2026 19:35:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:ed0d7038-53a1-4fff-a82b-116d26732486Fernando MoraesYes, the green channel.https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1649996/tdc1000-c2000evm-tdc1000-c2000evm-only-read-31us/6431908Tue, 28 Jul 2026 19:32:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3513aba5-b526-453e-a838-d3b052a74bd7Amanda RatliffHi Fernando, Thank you for sharing. In the scope shot you sent just now is the probe directly on the transducer? Best, Amandahttps://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1664816/iwrl6432aopevm-raw-adc-fft-data-extraction-on-iwrl1432boost-bsd-and-iwrl6432aopevm/6431892Tue, 28 Jul 2026 19:15:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8d457577-08a4-45a8-9fb2-a8782fca74fdDavid CassityHi Morgane, Before running the spi_data_capture_tool.exe, make sure to press reset on the device. If you have previously sent a config to the device and you haven&#39;t power-cycled the device since, the device is still running in the background, so the sensor won&#39;t respond to a sensorStart command. This should fix the continuously running script and should help you along to the next part of the guide. For the FFT-range data on the 1432, we do more than just a 1D FFT to the data, so the TLV for the range profile won&#39;t be able to provide all the information you need. Theoretically, you could try to reverse-engineer the signal chain and processing we use on the 1432, but that would be a much more difficult undertaking than purchasing the converter cable. More information about the Rangeproc can be found at .../ti/MMWAVE_L_SDK_05_05_04_02/docs/api_guide_xwrL14xx/RANGEPROC_PAGE.html. At this time, there isn&#39;t a common way to extract the data without an excessive amount of labor. Best, David