LAUNCHXL-CC1310: Sending broadcast messages using the TI 802.15.4 stack

I haven't try/test broadcast in beacon mode. You have to try/test this by yourself.

Hi AB, that is a great idea, since beacons are received by all nodes. I have looked into the code to see where to define the beacon payload and this is what I have deduced. Please, have a look and correct me if I am wrong.

COLLECTOR SIDE

In hmac_global.c there is a macBeaconPayload buffer and I guess that I need to insert its address and length into the macPibDefaults struct. Please, see my comments in the code.

Does this mean that, doing this, all beacons will be sent with the payload contained in macBeaconPayload? If so, I would just need to update the alarm status in macBeaconPayload to notify all the nodes

uint8 macBeaconPayload[MAC_PIB_MAX_BEACON_PAYLOAD_LEN] = {0};  // seems to be what I am looking for

/* PIB default values */
const macPib_t macPibDefaults =
{
  54,                                    /* ackWaitDuration */
  FALSE,                                 /* associationPermit */
  TRUE,                                  /* autoRequest */
  FALSE,                                 /* battLifeExt */
  6,                                     /* battLifeExtPeriods */

  &macBeaconPayload,                     /* *pMacBeaconPayload */ // <---- It is NULL by default, I guess I have to put here the address of the payload as shown?
  MAC_PIB_MAX_BEACON_PAYLOAD_LEN,        /* beaconPayloadLength */// <---- 0 by default, I guess I have to insert here the size of the beacon payload buffer

  /* more elements omitted for clarity */
}


/* PIB access and min/max table.  min/max of 0/0 means not checked; if min/max are
 * equal, element is read-only
 */
const macPibTbl_t macPibTbl[] =
{
  {offsetof(macPib_t, ackWaitDuration), sizeof(uint8), 54, 54},          /* MAC_ACK_WAIT_DURATION */
  {offsetof(macPib_t, associationPermit), sizeof(bool), FALSE, TRUE},    /* MAC_ASSOCIATION_PERMIT */
  {offsetof(macPib_t, autoRequest), sizeof(bool), FALSE, TRUE},          /* MAC_AUTO_REQUEST */
  {offsetof(macPib_t, battLifeExt), sizeof(bool), FALSE, TRUE},          /* MAC_BATT_LIFE_EXT */
  {offsetof(macPib_t, battLifeExtPeriods), sizeof(uint8), 6, 6},         /* MAC_BATT_LIFE_EXT_PERIODS */

  {offsetof(macPib_t, pBeaconPayload), sizeof(uint8 *), 0, 0},           /* MAC_BEACON_PAYLOAD */ // <-- should I modify this 0, 0 seems to mean read-only
  {offsetof(macPib_t, beaconPayloadLength), sizeof(uint8), 0, MAC_PIB_MAX_BEACON_PAYLOAD_LEN}, /* MAC_BEACON_PAYLOAD_LENGTH */

  /* more elements omitted for clarity */
}

SENSOR SIDE

In sensor.c, I will have to create a Beacon notify indication callback and add it here:

/*! API MAC Callback table */
STATIC ApiMac_callbacks_t Sensor_macCallbacks =
    {
      /*! Associate Indicated callback */
      NULL,
      /*! Associate Confirmation callback */
      NULL,
      /*! Disassociate Indication callback */
      NULL,
      /*! Disassociate Confirmation callback */
      NULL,
      /*! Beacon Notify Indication callback */
      NULL,                                      <-- add a pointer to my own callback where I will process the beacon payload

      /* more stuff omitted for clarity */
}

This callback will be called every time a beacon is received and I will be able to read the alarm notification sent by the collector.

If this works it would be great! we could broadcast any message in a very simple way, but would processing every beacon has a significant impact in power consumption and battery lifetime?

Thanks!

Javi