Help on porting software from XBee API to TI Monitor and Test API

As discussed here:

http://e2e.ti.com/support/low_power_rf/f/158/t/127446.aspx

You can try using extended address in the AF data request.

For incoming messages, you get basically all of the packet details:

typedef struct
{
  osal_event_hdr_t hdr;     /* OSAL Message header */
  uint16 groupId;           /* Message's group ID - 0 if not set */
  uint16 clusterId;         /* Message's cluster ID */
  afAddrType_t srcAddr;     /* Source Address, if endpoint is STUBAPS_INTER_PAN_EP,
                               it's an InterPAN message */
  uint16 macDestAddr;       /* MAC header destination short address */
  uint8 endPoint;           /* destination endpoint */
  uint8 wasBroadcast;       /* TRUE if network destination was a broadcast address */
  uint8 LinkQuality;        /* The link quality of the received data frame */
  uint8 correlation;        /* The raw correlation value of the received data frame */
  int8  rssi;               /* The received RF power in units dBm */
  uint8 SecurityUse;        /* deprecated */
  uint32 timestamp;         /* receipt timestamp from MAC */
  afMSGCommandFormat_t cmd; /* Application Data */
} afIncomingMSGPacket_t;

But you want all of those details on an incoming packet for ZDO instead of the many notifications the Application gets from ZDO and the many ZDO callbacks for which the Application can register? Be carefull, but you have access to all of the ZDO source code here:

C:\Texas Instruments\ZStack-CC2530-2.4.0-1.4.0\Components\stack\zdo

Also, you can intercept the incoming ZDO messages here in afIncomingData() in AF.c. You could hijack the ZDO message and send it to yourself (not recommended). You could send the message to yourself in parallel to the ZDO in afBuildMSGIncoming(), and thereby you could sniff the stuff coming in without acting on it the way that ZDO has to.