https://e2echina.ti.com/support/wireless-connectivity/other-wireless/zh-CNTelligent Community 13https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087526/tms3705-tms3705-2cm-13cm/3914750Fri, 07 Aug 2026 00:24:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:cc0a57cc-6783-4855-b994-f5280fc6b72aAlice您好， 天线及输出功率都会影响读取距离， 请参考链接文档了解天线设计 TMS3705: Methods to increase the read range of the receiver - Other wireless technologies forum - Other wireless - TI E2E support forums [Series 2000] Low Frequency RFID Readers (134.2 kHz), antenna design. - Other wireless technologies forum - Other wireless - TI E2E support forums 另外，这个导轨电源的85khz 800mv的干扰噪声是通过射频耦合的，那么可否从实施角度考虑给导轨电源外加屏蔽罩呢？https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087531/tms3705-tms3705-2cm-13cm/3914313Wed, 05 Aug 2026 06:00:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:e5ada446-2ca8-4b76-a6e2-d92e83d847bcFRANK1你看看调整下接收天线的角度和功率看看有没有改善。 (+) [Series 2000] Low Frequency RFID Readers (134.2 kHz), antenna design. - Other wireless technologies forum - Other wireless - TI E2E support forums 另外，导轨电源能不能加上屏蔽罩，会有效阻止频率干扰。https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087526/tms3705-tms3705-2cm-13cm/3914312Wed, 05 Aug 2026 05:41:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:1bba5049-06b9-47b4-a8ce-4f41b585a0b5Alice您好， 天线及输出功率都会影响读取距离， 请参考链接文档了解天线设计 TMS3705: Methods to increase the read range of the receiver - Other wireless technologies forum - Other wireless - TI E2E support forums [Series 2000] Low Frequency RFID Readers (134.2 kHz), antenna design. - Other wireless technologies forum - Other wireless - TI E2E support forums 另外，这个导轨电源的85khz 800mv的干扰噪声是通过射频耦合的，那么可否从实施角度考虑给导轨电源外加屏蔽罩呢？https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087526/tms3705-tms3705-2cm-13cm/3914268Wed, 05 Aug 2026 03:02:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:5411aef9-a386-4301-b26d-9ef5e31268a2Daniel您好 已经收到了您的案例，调查需要些时间，感谢您的耐心等待https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087531/tms3705-tms3705-2cm-13cm/3914259Wed, 05 Aug 2026 02:54:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:6bc137da-3d43-44fe-9fe5-8d3c7e1d2f5cFRANK1感谢您对TI产品的关注！ 关于你的咨询，我们正在确认您的问题，感谢您的耐心等待。https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087531/tms3705-tms3705-2cm-13cmWed, 05 Aug 2026 02:49:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:e1d5f188-551c-44f2-b405-4d22bcfd5716bo yangPart Number: TMS3705 尊敬的TI设计团队，您们好！ 我们在设计使用TMS3705设计低频读卡器的时候，在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。我们在工业现场做过一下验证，在工业现场使用读取距离只有2cm，后面用在工业现场那个电源把我们的读卡器拿到机房外面测试，读取距离回复正常。我们初步判断不是我们24V输入电源的影响。后面经过多方面测试和观察我们发现是工业现场的一个导轨电源发出了85k波形被我们天线接收都了影响了我们的读取距离。如下图所示的导轨电源，后面我们用示波器探头在空气测试中发现距离导轨电源越近这个85k干扰波形在空间中电压越大大概在800mv左右。而且我们的读卡器距离导轨电源越近基本上读取不到，距离他远一点距离会长一点，但是也只能有2cm无法到达10cm。像这种情况我们在使用TMS3705的设计的时候应该做哪些相关抗干扰设计和防护。以及现场这种情况有没有比较的解决方案，非常感谢了！机器人TMS3705https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1087526/tms3705-tms3705-2cm-13cmWed, 05 Aug 2026 02:44:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:8e5d2de4-e7a3-4af3-83ab-36eeea77f42ebo yangPart Number: TMS3705 尊敬的TI设计团队，您们好！ 我们在设计使用TMS3705设计低频读卡器的时候，在其中有个工业现场使用中读取距离变短到2cm，正常情况下读取距离13cm。我们在工业现场做过一下验证，在工业现场使用读取距离只有2cm，后面用在工业现场那个电源把我们的读卡器拿到机房外面测试，读取距离回复正常。我们初步判断不是我们24V输入电源的影响。后面经过多方面测试和观察我们发现是工业现场的一个导轨电源发出了85k波形被我们天线接收都了影响了我们的读取距离。如下图所示的导轨电源，后面我们用示波器探头在空气测试中发现距离导轨电源越近这个85k干扰波形在空间中电压越大大概在800mv左右。而且我们的读卡器距离导轨电源越近基本上读取不到，距离他远一点距离会长一点，但是也只能有2cm无法到达10cm。像这种情况我们在使用TMS3705的设计的时候应该做哪些相关抗干扰设计和防护。以及现场这种情况有没有比较的解决方案，非常感谢了！机器人TMS3705https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3868642Thu, 21 May 2026 20:05:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:c3dcff6e-812c-45de-8087-acfa319048c8Tarek D你好， 您如何验证有效载荷是否完整？ 此致， 塔雷克·DECTEhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead/3868180Wed, 20 May 2026 08:26:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:a09c576b-245a-43c1-a42f-4d8d35fcdfccQingtian Yang是否可以这样理解，在 SimpleLink LowPower F3 SDK 当中还未有完善的可用的DMP应用？https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3868179Wed, 20 May 2026 08:24:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:822bc9b5-94c2-418d-b001-49261456aabcQingtian Yang您好： 我已经能够成功发出了ble的广播包了，但是我的sniffer提示我：crc错误，但payload完整无误。但是我找不到在sysconfig当中设置他的地方，这些配置都被隐藏了吗。另外我使用的simplelink-lowpower-f3-sdk 8.10，我使用类似的代码在SDK 9.20上面是正确的，我找不到调试的方向，能否提供关于sysconfig配置Generic BLE的更多信息https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3866802Fri, 15 May 2026 14:48:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:45e1f60b-5562-4cf8-84d4-a732333e961bRyan Brown1你好， 您应该查阅 RCL API 指南 中的 BLE 命令处理程序 （例如 广播命令处理程序 ）和 BLE5 文件参考 。请注意，这需要使用自定义的 ti_radio_config.c/h 文件，因为 SysConfig 目前不支持自定义使用这些 RCL 命令。本质上，rfPacketTx 使用 BLE PHY，但并未公开所有 RCL 命令。您需要进一步研究文档，并尝试调整项目配置及其广播数据包结构，才能获得预期的输出。 问候， 瑞安ECTEhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overhead/3865942Fri, 15 May 2026 03:54:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:17668124-afee-4bd0-b31b-758953121f49AliceHello, We have received your post and the investigation will take some time. Thanks for your patience.https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073709/cc2340r5-cc2340-dmm-support-for-lightweight-multi-protocol-ble-802-15-4-proprietary-without-full-stack-overheadFri, 15 May 2026 02:13:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:d9ae8855-5d6f-45b9-bb21-e8037a7c4690Qingtian YangPart Number: CC2340R5 Hello TI , I am excited to see the DMM (Dynamic Multi-protocol Manager) solution implemented in the latest SimpleLink LowPower F3 SDK (v9.20.00.81) . I am currently working with the CC2340 series for an IoT project. Currently, I do not see any ready-to-use DMM examples specifically for the CC2340. Given this lack of reference, I am considering the following approach to implement a lightweight multi-protocol solution that fits within the 36KB/64KB RAM limit My specific requirements and pain points: Lightweight Coexistence: I do not necessarily need full-stack features (like a complete Zigbee mesh or high-level BLE profiles). My goal is to achieve basic packet transceiver (RX/TX) functionality across different protocols. Protocol Switching: Is it feasible to use DMM on CC2340 to switch between BLE (Low Level) , 802.15.4 (MAC layer only) , and Proprietary 2.4G (RF Driver/RAIL level) ? Basic Control: I only need to perform basic operations like changing frequencies/channels and sending/receiving raw data packets while maintaining a basic BLE connection for configuration. Demo Availability: Are there any "Lightweight DMM" or "DMM + RF Driver" demos available for the CC2340? Could you please provide guidance on how to implement such a "bare-metal style" multi-protocol switching using DMM on the CC2340? Or is there a recommended architecture for achieving low-level RF concurrency without the RAM overhead of full-featured stacks? Looking forward to your expert advice. Best regards!CC2340R5https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3865359Thu, 14 May 2026 02:30:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:86657ebd-3468-4127-8df6-fbeb3ed0e34aQingtian Yangstatic void ble_build_adv_pdu(void) { // --- PDU Header --- ble_pdu_raw[0] = 0x42; // ADV_NONCONN_IND (0x02) | TxAdd=1 (0x40) ble_pdu_raw[1] = 15; // Length: 6 (AdvA) + 3 (Flags) + 6 (Name) = 15 // --- AdvA: Random Static Address CC:66:55:44:33:22 (LSByte first) --- ble_pdu_raw[2] = 0x22; ble_pdu_raw[3] = 0x33; ble_pdu_raw[4] = 0x44; ble_pdu_raw[5] = 0x55; ble_pdu_raw[6] = 0x66; ble_pdu_raw[7] = 0xCC; // MSByte: bits 7:6 = '11' (Random Static).You can edit any byte of address except this bits 7:6! // --- AD Structure 1: Flags --- ble_pdu_raw[8] = 0x02; // AD Length ble_pdu_raw[9] = 0x01; // AD Type: Flags ble_pdu_raw[10] = 0x06; // LE General Discoverable | BR/EDR Not Supported // --- AD Structure 2: Complete Local Name "FG22" --- ble_pdu_raw[11] = 0x05; // AD Length ble_pdu_raw[12] = 0x09; // AD Type: Complete Local Name ble_pdu_raw[13] = '2'; ble_pdu_raw[14] = '3'; ble_pdu_raw[15] = '4'; ble_pdu_raw[16] = '0'; memcpy(ble_pdu_send+1,ble_pdu_raw,17); ble_pdu_send[0]=17; } /***** Callback Functions *****/ void defaultCallback(RCL_Command *cmd, LRF_Events lrfEvents, RCL_Events rclEvents) { if (rclEvents.lastCmdDone) { gCmdDone += 1; GPIO_toggle(CONFIG_GPIO_GLED); } } /***** Function definitions *****/ void *mainThread(void *arg0) { /* Initialize and open RCL */ RCL_init(); RCL_Handle rclHandle = RCL_open(&rclClient, &LRF_config); /* Set RF frequency */ rclPacketTxCmdGenericTx.rfFrequency = FREQUENCY; /* Start command as soon as possible */ rclPacketTxCmdGenericTx.common.scheduling = RCL_Schedule_Now; rclPacketTxCmdGenericTx.common.status = RCL_CommandStatus_Idle; rclPacketTxCmdGenericTx.config.fsOff = FS_OFF; // Turn off FS /* Callback triggers on last command done */ rclPacketTxCmdGenericTx.common.runtime.callback = defaultCallback; rclPacketTxCmdGenericTx.common.runtime.rclCallbackMask.value = RCL_EventLastCmdDone.value; /* Set RCL TX buffer packet to be packet buffer */ RCL_Buffer_TxBuffer *txPacket = (RCL_Buffer_TxBuffer *)&packet; GPIO_setConfig(CONFIG_GPIO_GLED, GPIO_CFG_OUT_STD | GPIO_CFG_OUT_LOW); GPIO_write(CONFIG_GPIO_GLED, CONFIG_GPIO_LED_OFF); ble_build_adv_pdu(); while(1) { /* Create packet with random payload */ uint8_t *txData; txData = RCL_TxBuffer_init(txPacket, NUM_PAD_BYTES, HDR_LEN, MAX_LENGTH); /* Zero out data in header before the length field */ // for (int s = 0; s < LEN_INDEX; s++) // { // txData[s] = 0U; // } /* Set the packet length */ // txData[LEN_INDEX] = ble_pdu_send[0]; memcpy(txData, ble_pdu_send, 17+1); /* Generate a random payload */ // for (int i = HDR_LEN; i < MAX_LENGTH; i++) // { // txData[i] = rand(); // } /* Set packet to transmit */ RCL_TxBuffer_put(&rclPacketTxCmdGenericTx.txBuffers, txPacket); rclPacketTxCmdGenericTx.common.status = RCL_CommandStatus_Idle; /* Submit command */ RCL_Command_submit(rclHandle, &rclPacketTxCmdGenericTx); /* Pend on command completion */ RCL_Command_pend(&rclPacketTxCmdGenericTx); usleep(PACKET_INTERVAL); } } This is part of my test code, based on the original rfPacketTx example. I only made some simple packet construction changes and modified: #define FREQUENCY (2402000000U) // set to BLE channel 37 I hope this helps clarify the issue I am trying to understand.https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettx/3865358Thu, 14 May 2026 02:25:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:0f0a816e-fb15-4f79-b4c5-ae568b6895a6LydiaHello, we have received your case and the investigation will take some time. Thank you for your patience.https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1073578/cc2340r5-cc2340r5-custom-ble-phy-how-to-transmit-raw-custom-ble-advertising-pdus-without-ble-stack-using-prop_rf-rfpackettxThu, 14 May 2026 02:22:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:de3985fb-5de5-4fee-a904-c98374eaa12bQingtian YangPart Number: CC2340R5 Other Parts Discussed in Thread: SYSCONFIG Hi, I am trying to use the CC2340R5 with the LP_EM_CC2340R5/prop_rf/rfPacketTx example as a starting point. My goal is: Use the Custom RF stack configuration with BLE PHY selected ( Generic 1 Mbps / 2 Mbps / Coded ) Transmit a fixed custom BLE advertising PDU Do not use the full BLE stack (GAP/GATT/LL) Later switch dynamically between BLE PHY and other PHYs for a multi-protocol application Currently I can run with the prop_rf example, but I cannot make a valid BLE advertising packet that can be detected by a phone or nRF Connect. I would like to understand: When using Custom -> BLE PHY in SysConfig, does the radio automatically handle: BLE Access Address (0x8E89BED6) CRC24 Data whitening BLE bit ordering Is it sufficient to provide only the BLE advertising PDU payload: Header AdvA AdvData or do I need to manually construct the full BLE over-the-air packet? Does the rfPacketTx example use a proprietary packet formatter that prepends packet length or uses a non-BLE packet structure? Is there an official example for transmitting raw/custom BLE advertising packets without using the BLE stack? My current intention is to transmit only on advertising channel 37 (2402 MHz) first. Thank you.SYSCONFIGCC2340R5https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1069985/sn74lvc1g66-q1-camds/3852187Thu, 23 Apr 2026 03:28:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:33966f9c-9f5d-45f4-b986-46d7eced8730Taylor您这个问题需要提到客服的质量组进行处理，请在下面链接选择相应项 联系我们 | 技术支持 | 德州仪器 TI.com.cnhttps://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1069985/sn74lvc1g66-q1-camds/3852186Thu, 23 Apr 2026 03:23:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:6a94dec0-cfd5-43c5-8446-530a139bff87Taylor您好， 已经收到了您的案例，调查需要些时间，感谢您的耐心等待。https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1069985/sn74lvc1g66-q1-camdsThu, 23 Apr 2026 03:18:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:1f799eb1-977e-40e2-b50e-076f6f6430b5Shibing WuPart Number: SN74LVC1G66-Q1 贵司之前提交的CAMDS已经失效了，请重新提交 MNN.04R0A.0089 IC SWITCH SPST SN74LVC1G66QDCKRQ1 CAR TI SN74LVC1G66QDCKRQ1 CAMDS失效的ID:CA_5_69980954/2SN74LVC1G66-Q1https://e2echina.ti.com/support/wireless-connectivity/other-wireless/f/other-wireless-technologies-forum/1033061/trf7970a-trf7970arhbr/3708207Tue, 21 Oct 2025 03:00:00 GMT91561404-af28-475a-b96b-cb6cbaadd097:afb2a3de-0e36-437a-a240-b96c52d98bcbKevin ChenI just want to know what material is used for THERMAL PAD and is this normal？