• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 57 subscribers
  • Views 1581 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.

Can you use 64-bit IEEE adress to send unicast message?

DMMT
Intellectual 420 points
Other Parts Discussed in Thread: Z-STACK

Hi All,

I am trying to use the AF_ACK_REQUEST to receive an ack from my end device when I send a message.. however, I realized that it must be a unicast message.

In the Z-Stack API, under AF_DataRequest, it states that the address mode of the destination address must be either: afAddrNotPresent, afAddrGroup, afAddrBroadcast or afAddr16Bit.

It does not explicitly mention Addr64Bit, so I'm wondering if that is allowed?

Thanks so much.

  • 0
    Intellectual 355 points

    I'm just familiarizing myself with the Monitor and Test API (which I believe a serial IO version of much of the Z-Stack API) and I've run into the same problem. I think the idea is that you need to resolve your IEEE address into a 16 bit NWK address first, and then proceed with the AF_DATA_REQUEST with the 16 bit NWK address.

  • 0 in reply to Joe Desbonnet
    Intellectual 420 points

    Joe,

    I believe you are correct... I believe this is a function that obtains the 16-bit address based on a device's extended address... I am looking for that function now :-)

    Thanks.

  • 0
    TI__Mastermind 19350 points

    RE: Can you use 64-bit IEEE adress to send unicast message?

    No, but maybe yes.

    No, the ZigBee specification for any OA message requires the 16-bit network address, or one of the valid multi-cast or broadcast addresses.

    Maybe yes because when a message is sent to the Z-Stack with AF_DataRequest() and the 'afAddrType_t *dstAddr' parameter setup as a 'afAddr64Bit', the Address Manager in the APS layer will attempt to find the 16-bit Nwk Addr that corresponds to that 64-bit address. In the small, simple, one-hop networks that we almost always are using for testing and proof-of-concept, the Address Manager down in the APS layer will almost always have it. But eventually, the Address Manager won't have it on a sufficiently complex or large network, in which case the call to send the message will return a fail value and you will have to invoke the ZDO layer to do a NWK Address lookup based on the known IEEE address - take a look at ZDP_NwkAddrReq().

     

  • 0 in reply to Dirty Harry
    Intellectual 330 points

    Hi,

    I would like to send a message from the coordinator to the end-device. I have the IEEE address of the end-device (for example: 187500123181190), so I tried to use the function: APSME_LookupNwkAddr(). But it didn't work. Do I need to configure something before use this function? How can I do this?

    Cheers,

    Victor Farias.