Part Number: CC1310 Other Parts Discussed in Thread: WMBUS , Hello,
I am having the same problem as a Gareth.
I am using CC1310 Launchpad and wmbus_cc13x0_rtos_2_0_0 ( OMS v. 4.1.2, based on SF stack).
Want to turn off the Extended Link Layer (starting with…
Part Number: CC1310 Other Parts Discussed in Thread: WMBUS , My customer is using CC1310 to develop a WMBUS application they have created another task besides the WMBUS stack task. When HwiP_disable() is called from their application task, there is a chance…
Part Number: CC1310 Hi team,
The customer is designing a WM-Bus module based on CC1310 and WMBUS-CC13X0. The module will communicate with the customer's smart meter over UART.
The WM-Bus module collects data from nearby WM-Bus gas and water meters…
Hi team,
does wmbus have an API that configures the sending time interval, such as when to what time it can be sent, or do I need to manually turn it on and off myself.
Part Number: LAUNCHXL-CC1310 Other Parts Discussed in Thread: WMBUS , CC1310 Hello forum
I want to create a wmbus application that can handle t1 and c1 modes on the cc1310 launchpad. I Have seen the stackforce implementation of the wmbus stack but i have…
Hi
As I do not have a wmbus sniffer, I asked SF for help and below are their response:
"So, we have downloaded the wmbus stacks from https://www.ti.com/tool/WMBUS . I see that the version is v.2.0.0.
Then, we run the following configurations on two…
Part Number: CC1310 Other Parts Discussed in Thread: WMBUS , I'm working on a project based on EasyLinkEcho (RX/TX) example (SimpleLink CC13x0 SDK v4.20.02.07 in CCS 12.0.0.00009). In parallel I'm using wMBus stack (wmbus-cc13xx-rtos-2.0.0 in CCS 8.1…
Part Number: LP-CC1312R7 Other Parts Discussed in Thread: WMBUS , , CC1312R7 , CC1101 , CC1200 Hi,
I have successfully performed rx measurements on Wmbus OTM sending packets either between 2 boards or between an ESG 4438C signal generator and a LP-CC1312R7…
Part Number: CC1310 Other Parts Discussed in Thread: WMBUS Hello,
I am having trouble talking to a third party device. I believe one possible cause is that the device may only support OMS v3.0.1. I notice that the WMBus stack adds the extended link layer…