• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 423 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-CC1310: wMBus -field is changed

Tommy Søborg
Prodigy 20 points
Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: WMBUS

Hi

We are collecting wMBus messages from a certain meter with the LaunchPad and the example from this forum thread, and we have come accross some odd behaviour:

We are using a iM871A-USB dongle to compare the telegrams received and the telegrams are almost identical with the exception of the L-field. With the dongle the L-field is correct and we can decode it, but with the LaunchPad the L-field has been incremented by 2:

Dongle:

3F442D2C7158857134048D20BF93725C21F1362835BD0FE1F4E05F164A0DBBCA29FB9B51DB9FFDDC2906DA4820A18AE8CDA6FED588B6C57538DAED60750F0611

LaunchPad:

41442D2C7158857134048D20BF93725C21F1362835BD0FE1F4E05F164A0DBBCA29FB9B51DB9FFDDC2906DA4820A18AE8CDA6FED588B6C57538DAED60750F0611

This only seems to happen when the preamble byte is 0x3d.

Does the radio driver change the L-field for some reason?

  • 0
    TI__Guru* 82531 points

    Hi Tommy,

    If I understand you correctly, you started with a prop rf example, took Siri's code for partial read. What RF settings are you using? 

    Cheers,

    Marie H

  • 0
    TI__Guru* 86771 points

    Hi Tommy

    I do not understand what you are testing and how.

    The example you link to simply shows how to use partial read entries and interpret  the 5th byte as a length byte and has nothing to do with wmbus.

    I am not familiar with the wmbus packet format and you are not even saying which wmbus mode you are using, so I cannot answer why you are receiving what you are receiving.

    Siri