• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 426 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.

CC1310: TI15.4 Disable Beacons

Andrew Bakin
Expert 1665 points

Part Number: CC1310

Hi,

I'm using simplelink_cc13x2_26x2_sdk_4_10_00_78 and have an application based on the TI15.4 Collector using RTOS, no FH and in non-beacon mode.

According to IEEE 802.15.4 standard:

A device shall be permitted to transmit Beacon frames only if macShortAddress is not equal to 0xffff.

I have set:

devInfoBlock.devShortAddr = 0xFFFF;
ApiMac_mlmeSetReqUint16(ApiMac_attribute_shortAddress,devInfoBlock.devShortAddr);

but I still get a beacon, unless I power cycle. Is there something else I need to do to stop beacons being transmitted?

Thanks,

Andy

  • 0
    TI__Guru* 83901 points

    Hi Andy,

    Yes the device will not update the short address immediately.

    You can use the batteryLifeExt parameter in combination with the MAC_BATT_LIFE_EXT_PERIODS to stop beacons after a given number of transmissions, does thiw work with your use-case?

  • 0 in reply to Marie H
    Expert 1665 points

    Hi,

    Thanks for your reply. I'll mark the problem as solved, but I did it a different way. The problem I had was that if a Router is on the network, but then I perform I new network association attempt on that same router which clears all its data and sends a disassociation message, so that it is sitting off the network like it has just been flash programmed because the network was closed, it would still send out a beacon in response to a beacon request. Not using a short address, but using its extended address. The problem with this beacon, is that it could be sent with its permit flag set to true, causing a joining device to use that router to join through, but obviously failing because its' off the network. 

    I still get the extended address beacon, but I make sure the join permit flag is set to false at the disassociation stage.

    Thanks,

    Andy