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

orphan notification and Assoc cnf fail messages

Leila Keyvani
Expert 1090 points
Other Parts Discussed in Thread: CC2530, CC2530EM

Hi,

I am using GenericApp sample of Zstack on cc2530. modifications I  made are: channel number, PANID = 0x0001, unicast communication, destination short address = 0x0000, I have one end device and one coordinator. there is no binding. I have some issues with this communication,

1. when I use packet sniffer to track the packets, the first couple packets show correct source and destination address with packet payload, then "orphan notification" packet is broad casted from my end device, and then a beacon request is broad casted! what is going on in my application?!

2. mean while I got " Assoc cnf fail" message on the LCD of end device, which I have no idea why and what does that mean?

could you please share your ideas about this problem?

Thanks,

Leila

  • 0
    TI__Genius 9325 points

    Leila,

    It seems that your coordinator was dead or locked-up. If the end device fails to get acknowledges from its parent several times, it will start finding a new parent. In your case, the coordinator is not responding and there is no other router to be the new parent for your end device.

    Can you check in what state the coordinator was when the problem happened?

    - Cetri

  • 0 in reply to Cetri
    Expert 1090 points

    I think you are right. This happens whenever I run the packet sniffer, the chip turns on led number 2 and then when I restart the coordinator it cannot read the downloaded application from the memory. It does not receive any of the packets that was sent from the end device! How I can check the state of the coordinator?

    Leila 

  • 0 in reply to Leila Keyvani
    TI__Genius 9325 points

    Leila,

    Can you share the packet sniffer log here? I'm a little confused. In your first message, there was no mention about the restart of the coordinator. When did you restart the coordinator? What are you using as the packet sniffer?

    - Cetri

  • 0 in reply to Cetri
    Expert 1090 points

    7673.8_18test.psd

    is this what you are looking for?

    my packet sniffer is 2.15.2. so the story is like this. I start the coordinator, then end device. it joins the network. then I run the packet sniffer.( I could not repeat the same test which had orphan notification). then it shows the beacon requests forever. then I turn off the end device, led #2 of coordinator turns on, then I turn off the coordinator. after this when I turn on the coordinator again, there is nothing on the LCD about device info. no sign of my downloaded function.

    Thanks for your help,

    Leila

  • 0 in reply to Leila Keyvani
    TI__Expert 5255 points

    Sorry, but this might be a dumb question. Is the packet sniffer using the same HW as the Coordinator? That would explain the "no sign of my downloaded function", and the orphan joins by the ED -- the Coordinator code gets replaced by the sniffer code.

  • 0 in reply to xyzzy
    Expert 1090 points

     

    xyzzy said:

    Sorry, but this might be a dumb question. Is the packet sniffer using the same HW as the Coordinator? That would explain the "no sign of my downloaded function", and the orphan joins by the ED -- the Coordinator code gets replaced by the sniffer code.

     

    what do you mean by the same HW? should i use different HW to run the packet sniffer on that? 

    Leila

     

  • 0 in reply to Leila Keyvani
    TI__Genius 9325 points

    Leila,

    Yes you need a separate HW like CC2530EM+SRF05EB or CC2531EM to sniff packets.

    - Cetri 

  • 0 in reply to Cetri
    Expert 1090 points

    Good guess. I am powering my boards from the same PC as I am using the Packet sniffer. so now you are saying that if I want to sniff packets I should only connect a board that is meant to use for sniffing only  to my PC, Is that right?

    I will try again to see how things go with a different board.

    Thanks for the help.

    Leila

  • 0 in reply to Leila Keyvani
    TI__Genius 9325 points

    Leila,

    You can connect more than one device to your PC and select one among them as a sniffer. Please see below screen capture:

    - Cetri