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.

CC1352P7: Rx of custom 15.4 async data message

Part Number: CC1352P7

Tool/software:

Hey,

We have a custom/proprietary 15.4 frame which we send asynchronously. While listening for this frame we temporarily set RxOnWhenIdle=1 in the MAC for the receiving device. The receiving device is not joined to any coordinator.

This is how the frame looks (863.125 Hz, 50 kBaud, LSbit first, IEEE whitening, 7 byte preamble):

55 90 4E 18 17 01 C1 9B 55 03 14 BD 25 00 4B 12 00 XX XX XX XX XX XX XX XX XX XX XX
Sync word Phy header Frame control field Source PAN ID/address Payload CRC

We are successfully able to receive this frame as an asynchronous data frame on Simplelink SDK version 4.30, but struggle on 5.20. I suspect this is due to stricter MAC filtering (possibly due to the WiSUN FAN features introduced in 5.20?).

Are there any configurations I can adjust to be able to receive this message also on the newer SDK? Or alternatively, are there changes I could make to the frame format (setting it as a command frame, beacon frame, etc)? 

In advance: thanks! And feel free to reach out if you need additional information.

EDIT: Frequency hopping is enabled (non-beacon). But the message is sent on a singular frequency, and `ApiMac_FHAttribute_unicastFixedChannel` is updated to be only that very same frequency

  • Hei Kim,

    If I understand correctly, the receiving device is running TI 15.4-Stack collector image. The only change from the SDK version is that you set RxOnWhenIdle=1 in the MAC while listening for this frame. 

     Did you test whether you can receive it with the newest SDK (8.30)?

    I don't believe the addition of the TI Wi-SUN FAN stack introduced big changes in the TI 15.4-Stack. However I will reach out to the SW RND team. But I don't expect feed-back from them until late next week.

    Cheers,

    Marie H

  • I'm sorry for the confusion. The receiving devices are running "sensor" images, and RxOnWhenIdle=1 with both SDK versions. Both devices are however running a common proprietary logical link controller, with common attributes written to the MAC. The issue is that one of the devices receives an (async) data indication callback from the MAC on the above mentioned frame, while the other doesn't. 

    I have not been able to test a newer SDK yet, as that would require porting existing devices, and/or integrating the new SDK with our existing code.

  • Hi Kim,

    I passed your message to the SW designers. I will let you know when I have their feedback, expected in one week.

    Cheers,

    Marie H

  • Hi Kim,

    Can you provide a sniffer log of this happening?

    Cheers,

    Marie H

  • Hi again.

    We managed to get things to work eventually. It seems the newer MAC versions filter away messages with frame version < 2 and no destination address (unless the receiving device is a coordinator). We solved this by setting frame version 2 in the frame control field.

    Thanks for the help,

    Kim