Part Number: CC1310
Other Parts Discussed in Thread: WMBUS
Hello
I'm developing a wm-bus collector on CC1310 Launchpad, trying to receive data from some wm-bus sensors in the building. (C mode packets one way, every 16 seconds) The goal is to use the provided wm-bus stack to receive and decrypt messages. (http://www.ti.com/tool/WMBUS)
For preliminary testing I applied the combined C/T mode patch (swra522d) through SmartRf Studio. Plugging in the C/T mode patch in to the rfPacketRx example works, i can see the packets from the sensors being received. There is a problem with SmartRf Studio, but the point is that the CC1310 radio and the sensors seems to work.
When running packet-RX in SmartRf Studio the packets received from the sensors includes the sync word 0x543D as the first two bytes in the packet. I also receive a lot of other packets which seems to be random data. Changing the sync word from 0x543d to 0x543D543D and the sync word length from 16 to 32 bit results in only sensor packets being received.
The problem is that the wm-bus stack does not seem to receive packets correctly. I modified the example project (APL Collector C2) to allow all new meters. The wmbus_apl_evt_newMeter callback is called, but far more often than the sensors are transmitting and the sensor data passed to the callback is not correct. I also tried adding one of the sensors to the meterlist and waiting on a breakpoint in the wmbus_apl_evt_tlgAvailable callback, but the breakpoint was never hit.
Has anyone had any luck using the wm-bus stack for receiving C-mode packets? Do I have to do further modifications to the example project to run it on CC1310?
Is there maybe a connection between the strange behavior in SmartRF Studio and not being able to receive packets when using the wm-bus stack?
Is there any common misconceptions or problems when using the wm-bus stack?
I'm happy to provide more details as needed.
Thank you.
