https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/<p style="display:none;">blank</p>en-USTelligent Community 13https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691301/cc2662r-q1-unable-to-access-wbms-protocol-profiler-download-via-myti-secure-resources/6520001Fri, 23 Oct 2026 17:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4a16f997-1562-4bac-967b-53356f6384cdChad OuHi Barbara, I can access and download the file successfully now. Thanks for your help. Best regards, Chadhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691301/cc2662r-q1-unable-to-access-wbms-protocol-profiler-download-via-myti-secure-resources/6519986Fri, 23 Oct 2026 16:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0bb9773f-eaad-4a61-99c8-d6f3e5ad04b0Barbara WuHi Chad, Email just sent to you. Please check if you are able to receive it successfully. If so, please close this ticket. Thanks. Best Regards. Barbarahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688789/cc2662r-q1-cc2662r-q1-wbmsctrl_bqedgeframersp-field-sources-and-v-i-sync-statistics/6519918Fri, 23 Oct 2026 15:47:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9332aa96-fb90-404b-962f-391fd01e9601Chad OuHi Barbara, Thank you for the detailed clarification. Best Regards, Chadhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691301/cc2662r-q1-unable-to-access-wbms-protocol-profiler-download-via-myti-secure-resources/6519910Fri, 23 Oct 2026 15:43:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b7ce00cf-9270-495f-95e4-75031bad3b59Chad OuHi Barbara, Thanks for your response. My email address is ouyangchenghua@ttcble.com. Please let me know if you need any additional information. Best regards, Chadhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691301/cc2662r-q1-unable-to-access-wbms-protocol-profiler-download-via-myti-secure-resources/6519855Fri, 23 Oct 2026 14:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:fc151225-537b-4d7c-b8fe-13317d3df1b4Barbara WuHi Chad, We are in period of updating PP. Please share your email. Let us fix this offline. Thanks. Best Regards, Barbarahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6519706Fri, 23 Oct 2026 12:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:03b53a67-cd29-4139-9d84-2bbeb98c7015Hideraldo De FilippoHello Isaac, Do you have any updates regarding my issue? Thank you for your help. Best regards, Hideraldohttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688789/cc2662r-q1-cc2662r-q1-wbmsctrl_bqedgeframersp-field-sources-and-v-i-sync-statistics/6518713Thu, 22 Oct 2026 15:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4dace318-bd06-4b44-b754-c14f261531f5Barbara WuHi Chad Appreciated always open a new ticket for a new irrelevant question, and click &quot;resolved&quot; if existing ticket is closed. To your new question only this time: 1. Based on ideal laboratory conditions. 2. Rejoin happens only when network information has existed that is either network was formed in persistent mode, or network was formed in volatile mode but no reset performed after disconnection. But the data was based on persistent mode case which is the most common scenario. 3. 32 WDs is a MAC layer limitation that cannot be modified. Best Regards, Barbarahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688789/cc2662r-q1-cc2662r-q1-wbmsctrl_bqedgeframersp-field-sources-and-v-i-sync-statistics/6518410Thu, 22 Oct 2026 11:33:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:09dd20d2-4bb3-4dc4-a40c-986eade9c02bChad OuHi Barbara, We are currently evaluating the wireless performance of the WBMS solution based on SimpleLink WBMS SDK 3.20.02.05 . At this stage, we are focusing on wireless communication testing and have not yet integrated the AFE for actual battery monitoring. We would appreciate your guidance on the following questions: We have reviewed the benchmark data in the WBMS documentation. For a 1 WM + 32 WD network, should the published throughput/PDR performance be considered a practical target under normal deployment conditions, or are those results based on ideal laboratory conditions? Regarding the published Rejoin Time benchmarks, could you clarify what type of rejoin scenario was evaluated? We would like to align our test approach with the benchmark methodology and understand whether we are comparing against the same use case. We understand that the current SDK officially supports up to 32 WDs . Is this primarily a validated support limit or a fundamental system limitation? We would appreciate any guidance on how to position this to customers who are evaluating larger-scale deployments. Thank you for your support. Best Regards,https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691381/rf430f5978-comparison-between-rf430f5978-and-rf430f5144/6517225Wed, 21 Oct 2026 14:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:699e1030-be63-48a5-8e13-dad09249aaa6Rizwan MurjiHi Mikeda, I have sent you an email with the information. I will go ahead and close out this E2E thread. Thanks, Rizhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691381/rf430f5978-comparison-between-rf430f5978-and-rf430f5144Wed, 21 Oct 2026 06:22:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1dca8561-6fb1-47cc-b3f5-ec35969300daMikedaPart Number: RF430F5978 Hi TI team, My customer is considering using the RF430F5978. They previously used the RF430F5144 in their products. The datasheet for the RF430F5978 is available on TI&#39;s website, but since the RF430F5144 is an older product, its datasheet is no longer available. They want to compare the details of both two devices, so they&#39;re asking me to provide the RF430F5144 datasheet. Could you provide RF430F5144 datasheet? Thanks and Best Regards, MikedaRF430F5978https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691301/cc2662r-q1-unable-to-access-wbms-protocol-profiler-download-via-myti-secure-resourcesWed, 21 Oct 2026 01:52:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4afc519c-0d8a-450f-a3c7-2f9d44c33b0fChad OuPart Number: CC2662R-Q1 Hi, We have a question regarding the WBMS Protocol Profiler download. One of our colleagues is able to download the WBMS SDK successfully. However, when we open the SDK documentation and follow the Protocol Profiler &quot;Access&quot; link, after logging into myTI Secure Resources, the page shows &quot;There Was An Error Processing Your Request&quot; instead of the download resource. Could you please let us know if the Protocol Profiler requires additional access permissions, or if there is an updated download link available? Thank you for your help.CC2662R-Q1https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691062/tps62a02a-schematic-review/6515658Tue, 20 Oct 2026 10:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:56803544-dfe8-44fa-9f5d-c8990bf2e887Josef MarsmannHi William, I have reviewed the schematic and have some commends: In the thread you mentioned TPS62A02A (FPWM) but the schematic shows TPSA02DRLR(PFM/PWM). What is correct? This device in general is not designed for remote sensing so, the customer has to check the stability on their board. Everything else looks fine to me. Best regards, Sepphttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1691062/tps62a02a-schematic-reviewTue, 20 Oct 2026 09:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9360ec68-5349-48c0-942b-a9f5d2452226William Lai(CFAE)Part Number: TPS62A02A Hi Team, Could you please help to review the schematic (U7606,U7605,U7706,U7707,U7805)? I have attached the corresponding files for your reference. Covey_TI_0921 (003).pdf Thanks. Best Regards, William LaiPC &amp; NotebooksTPS62A02Ahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676697/cc3220s-launchxl-cc3220s-launchxl-cc3220s-sl_af_rf-sl_sock_raw-millisecond-rx-indication-latency-under-busy-rf-conditions/6514618Mon, 19 Oct 2026 14:27:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f2778e63-46d5-4997-9e69-9fdb896cab75Josh PrushingHi Ashot, Apologies for the delay in response, I have been OoO. While I am sad to hear that you have decided to move away from the CC3220S for this project, I&#39;m happy to continue to provide any information I can. [quote userid=&quot;580659&quot; url=&quot;~/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1676697/cc3220s-launchxl-cc3220s-launchxl-cc3220s-sl_af_rf-sl_sock_raw-millisecond-rx-indication-latency-under-busy-rf-conditions/6503029&quot;] If possible, I would appreciate one final clarification: does the same 3-frame / 1.2-ms pacing mechanism, and the approximately 2-ms worst-case estimate, also apply to RX indications for SL_AF_RF / SL_SOCK_RAW ? [/quote] It seems like the RX path is very similar, but has a separate mechanism for high priority frames to make them fire immediately. The lower priority frames will still have the 1.2 mSec timeout, but the number of frames threshold is set to 0, which means they should be fired immediately. Please let me know if you have any additional questions on the CC3220S. I will share your feedback on the limitations of CC3220S for your project with the team in order to see if there is anything we can work towards implementing in the future to cover this use case. Best Regards, Josh Prushinghttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688789/cc2662r-q1-cc2662r-q1-wbmsctrl_bqedgeframersp-field-sources-and-v-i-sync-statistics/6509872Wed, 14 Oct 2026 01:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:01cb4fe4-1d50-48ff-9ffc-6670bd8aad19Chad OuHi Barbara, Thank you for the clarification and the information. We will review the API documentation and apply for the latest SDK version 3.20.02.05. Best regards, Chadhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688789/cc2662r-q1-cc2662r-q1-wbmsctrl_bqedgeframersp-field-sources-and-v-i-sync-statistics/6509254Tue, 13 Oct 2026 15:11:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:72f912d2-6002-4351-aed2-4c9ed406115cBarbara WuHi Chad, For Edge, the statistic command is not used. Instead, each edge response will have stats which contains the numbers you need. Please check the API doc: TI Wireless Battery Management System (WBMS) Protocol: (0x0E) WBMS_CMD_WD_BQ_EDGE_RSP. (simplelink_wbms_sdk_3_20_02_05/docs/wbms/doxygen/html/group__WD__BQ__EDGE__RSP.html) I noticed that you are not on the latest release. Please do move to 3.20.02.05. Best Regards, Barbarahttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688460/launchxl-f28p65x-need-contact-person/6508100Mon, 12 Oct 2026 17:51:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f5daca78-de19-41ef-8f26-8f87298982bfPeter LuongHi Jay, Do you have a sales engineer assigned to your myTI account? What product lines are you specifically targeting? Regards, Peterhttps://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688789/cc2662r-q1-cc2662r-q1-wbmsctrl_bqedgeframersp-field-sources-and-v-i-sync-statisticsMon, 12 Oct 2026 11:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:95326dfd-d63f-4707-8fb4-a507495ad931Chad OuPart Number: CC2662R-Q1 Other Parts Discussed in Thread: TIDA-010976 , Hi TI team, We are using CC2662R-Q1 with SimpleLink WBMS SDK 3.20.00.07 and are aligning our test method with the PS and PDR results in the TIDA-010976 design guide. The V-I Sync documentation describes numTx , numTxAttempts , numRx , and numRetries . However, the corresponding members in WBMSCtrl_bqEdgeFrameRsp_t are commented out in the SDK header, and we cannot find a working SDK example that obtains or uses these values. Could you please clarify: Is numTx a WD-side counter for unique WD-to-WM packets, excluding retries? Or is it maintained by the WM from received packets? Is numRx maintained by the WM as the number of successfully received WD packets? If so, is it deduplicated from retransmissions? Does numTxAttempts include actual automatic MAC-layer RF retransmission attempts, including the initial transmission? If yes, which supported SDK API, callback, MAC statistic, or BQ Edge frame field provides the actual numTxAttempts and numRetries values to an application? Is WBMSCtrl_bqEdgeFrameRsp_t supported only for BQ Edge / V-I Sync traffic? Is there a supported example showing how to obtain these counters? We need the authoritative counter source and update method in order to calculate PDR and PS on the same basis as TIDA-010976. Thanks.TIDA-010976CC2662R-Q1https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1688460/launchxl-f28p65x-need-contact-person/6507211Sun, 11 Oct 2026 12:05:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:3d601216-1a7b-4248-a8a0-ec8dcc6fa84fStevan DuraskovicHi, I assigned thread to relevant expert please give some time for expert to respond back.https://e2e.ti.com/support/wireless-connectivity/other-wireless-group/other-wireless/f/other-wireless-technologies-forum/1673024/tms3705-tms3705-and-tms37145---communication-error/6506869Fri, 09 Oct 2026 20:04:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:65c08c65-99e2-406e-951a-744d59a49795Hideraldo De FilippoHello Isaac, Thank you in advance to you and your team for all the help and support you have been providing us. Regarding your questions: I extracted the SENSE and SFB signals again to confirm the signals that I previously provided. I am attaching the updated plots for your analysis. Regarding the UCC27424 driver, I am using it in both tests. In the successful reading configuration, the UCC27424 is connected directly to the LC circuit. In the unsuccessful reading configuration, the UCC27424 drives a full bridge, which is then connected to the LC circuit. The problem occurs specifically when this full bridge is introduced into the circuit. In both configurations, the transmission signal appears to be correct. However, when the full bridge is used, I am unable to obtain a valid signal on the receive side. The reason for using the full bridge is that it allows us to achieve significantly higher power in the transmission circuit. With the full bridge, we can reach approximately 630 V on the antenna. This higher transmission voltage is important for achieving the required FDX reading distance. For clarity: Successful reading: UCC27424 connected directly to the LC circuit. Unsuccessful reading: UCC27424 connected to the full bridge, with the full bridge connected to the LC circuit. Thank you again for your support. I look forward to your team&#39;s feedback on the waveforms. Best regards, Hideraldo