• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 53 subscribers
  • Views 505 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-CC1352R1: Issues with Receiving WMBUS Data on TI CC1352R1 Development Kit

NITISH KUMAR
Prodigy 80 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: WMBUS, CC1312R, CC1352R

Tool/software:

Hello,

I am working with the TI CC1352R1 Development Kit and encountering some issues with receiving WMBUS (Wireless M-Bus) data from a meter. I would appreciate any assistance or suggestions to resolve these issues.

  1. Configuration for Receiving WMBUS Data:

    • I have configured the CC1352R1 Development Kit to receive WMBUS data from a meter, but it is not receiving any data. Is there a specific configuration or setting that I need to apply to ensure proper data reception from the meter?

  2. CRC Errors in RF Studio:

    • In RF Studio, I am able to receive WMBUS meter data, but it comes with CRC errors. Can you explain why these CRC errors might be occurring and how I can resolve this issue to receive error-free data?

  3. Successful Transmission and Reception Between Two Kits:

    • When I use one TI CC1352R1 Development Kit as a transmitter (Tx) to send WMBUS frames and another kit as a receiver (Rx), the data transmission and reception work correctly. Given that the same configuration works for kit-to-kit communication, why isn't it working for receiving data from the meter? What might be the differences between the meter's transmission and the kit's transmission that could cause this issue?

Here are some additional details that might be relevant:

  • The configurations for the Tx and Rx kits are identical when testing kit-to-kit communication.
  • The meter's data is being received in RF Studio, but with CRC errors, indicating that some level of communication is occurring.

I would be grateful for any guidance on how to configure the CC1352R1 Development Kit to reliably receive WMBUS data from the meter and eliminate the CRC errors in RF Studio.

  • 0
    TI__Guru* 86731 points

    Hi

    SmartRF Studio are giving you the correct PHY configuration (data rate, frequency, deviation, RX BW etc.) to support wmbus, but it does not transmit real wmbus packets.

    That means that you can use SmartRF Studio to test the PHY and hence the RF performance, but you cannot send or receive real wmbus packet.

    When using SmartRF Studio with wmbus PHY, you will be able to receive something when transmitting real packets from a meter, since you are receiving on the correct frequency, using the correct data rate and are looking for the correct sync word.

    However, real wmus packets use a different format for length byte and CRC, so you will always get CRC errors.

    We do not have code examples showing how to receive proper wmbus packets, as this would reveal the packet format of the packets and you need to buy the standard to get info regarding how the packets look like.

    Siri

  • 0 in reply to Siri
    Prodigy 80 points

    Hi Siri , 

    let me explain my case again !

    1. Configuration for Receiving WMBUS Data:
     in this i have programmed TI CC1352R1 using code composer studio to receive WMBUS Data on T & C mode but it is not receiving any thing , is there i have to do any configuration changes while programing it in CCS ?

    & 

    second ,

    I also have the CHIPSET of CC1352R & CC1312R , using only this chipset how i can read/receive WMBUS Data ?
    1. i can directly read from UART to receive it ?
    2. i have to burn any program into this , if yes how i can do ?


    please reply point by point.

  • 0 in reply to NITISH KUMAR
    TI__Guru* 86731 points

    1) You say that you have programmed your device using Code composer Studio but you do not say what code you have used.

    Are you using the wmbus stack from stackforce or have you written your own code?

    If you are using the wmbus you should reach out to stackforce for support. They will need info regarding what HW you are using (not only the device but the board itself) and what configuration of the stack you are running

    If you have written your own code, you need to give me details on your code if I should be able to help you. As I wrote in my first post, we do not have any code example that shows how to receive wmbus packets, as the format of the packets are open information. To get this info, and be able to write RX code to receive proper wmbus packets, you need to buy the spesifications.

    For your second question, I have already answered this.

    If you have CC3152R LP or CC1312R LP, you can connect them to Studio and select the wmbus settings. this will allow you to find packets on the air, but they will always have CRC errors, as there are noe handling of wmbus packets in Studio.

    To receive wmbus packets you need to use the wmbus stack, or you need to write your own code, and for that you need to buy the specifications.

    The wnus stack from stackforce is availabe here:

    https://www.ti.com/tool/WMBUS

    Siri

  • 0 in reply to Siri
    Prodigy 80 points

    1 ) in code composer i only selecting PHY Type as WMBUS T mode , making build & flashing it into the CC1352R .

    you can see in this image.





    2) from this link https://www.ti.com/tool/WMBUS i have downloaded a zip , there is some hex files to flash , this is also not getting WMBUS Data from The Meters (Itron's WMBUS Water Meters)

    3) ("To get this info, and be able to write RX code to receive proper wmbus packets, you need to buy the specifications.") please explain me what specifications , i m not getting it.

  • 0 in reply to NITISH KUMAR
    TI__Guru* 86731 points

    I do not understand how I can explain this any clearer.

    1)

    The settings we provide for wmbus is the PHY settongs (Physical settings, like correct frequency, data rate, BW, deviation) etc. 

    It DOES NOT configure the correct packet format. That means that if you want to receive real wmbus packets, you need to implement the packet handling, length filtering CRC caluclation etc.) yourselves. It will not work to take the wmbus settings and import tham into any of our examples and expect to be able to receive wmbus packets.

    2)

    Like I said in my last post, if you have problems with the wmbus stack you should contack Stackforce directly for support. 

    You need to provide them more details than what you provide here. which hex file have you donwloaded, have you done any modifications to the code, which packest are your trying to receive etc.

    3)

    To write code that interprets a packet correctly, you need to know how the packet looks like. Is there length info in the packet? if, yes, where in the packet can that be found, what CRC is implement, where are the CRC bytes located etc.

    This information is part of the mbus specifications, and you need to buy the spec. To get this info. This is why TI does not have any open source code to show you how this can be done.

    If you use the wmbus stack, this packet interpretation is implemented in the stack (as lib files, not open source), so you do not have to do this, but you need to write the application that runs on top of the stack.

    SIri

  • 0 in reply to Siri
    Prodigy 80 points

    can we connect in a meeting ? , so that i can explain you well.

  • 0 in reply to NITISH KUMAR
    TI__Guru* 86731 points

    No, you will need to ask your question in the forum.

    Siri