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

Sensor Demo application route discovery

satchi ragava
Prodigy 60 points

Other Parts Discussed in Thread: Z-STACK

Just a quick question, I am running sensor demo application on CC2530ZDK.

I have set up a coordinator and 2 routers connected to the coordinator.

What i understand from the sensor demo user guide is that, when the connection / link is too weak from the end device to a router, it will find another router within radio distance which has a better link cost.

Am I understanding this application correctly?

I tried this with a few set up but it doesnt seem to be behaving this way (route discovery). Is there any other changes in the application which needs to be done that i am not aware of?

Thanks in advance.

  • 0
    TI__Genius 10650 points

    Hello Satchi,

    A brief description of what will happen when the end device in the sensor monitor application losses connection to its parent (router in your implemetation) ->  End device's in the network, to send any packet, will forward that packet to thier parent who will take care of routing for the packet to the destination. When end-device losses connection with the parent then as explained in the Z-Stack Developer's Guide (included with Z-Stack install at C:\Texas Instruments\ZStack-CC2530-2.5.0\Documents section 7, Portable Devices), ZDO_SyncIndicationCB() will initiate a Rejoin process. In sensor demo application for CC2530ZDK the end device after loosing connection to the parent will initiate a rejoin and join to nearest router/coordinator.  After sucessfull connection it will recieve a ZDO state change indication and then application will do the binding and then start sending the periodic messages.

    To see this, you can make a setup with Coordinator, a router and an end-device. Intialize the network such that router is the parent of the end device (keep shorter distance between router and end-device than coordinator and end-device). Start the periodic transmissions of messages from end device to coordinator. You will see that end device sends the message to router which then sends it to the coordinator. Then switch off the power on the router. The end device will then start rejoin process and join to coordinator and start reporting the messages again.

    Regards,

    Suyash Jain

  • 0 in reply to Suyash Jain
    Prodigy 60 points

    thanks alot for that Suyash. you're the man !

    much better understanding the way it works now.

    cheers.