• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 369 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.

Zigbee network setup

supriya negi
Prodigy 10 points
Other Parts Discussed in Thread: Z-STACK

Hi all ,

I am trying to setup zigbee  network between cordinator and end devices. I have two end devices 1 light switch and another dimmer switch. The network is sucesfully established between cordinator and dimmer. And I am able to control dimmer levels. However I am not able to discover , bind to light switch.

Log for same as been showed below :-

root@arm:/zigbee# ./zigbee_test_app
OSAL_INTERFACE_INITTASKS
                 ================================


                 Home Automation Application
                 ================================

                 0: check zigbee running status

                 1: ALLOW JOIN
                 2: DISCOVER DEVICES
                 3: BIND Device
                 4: SET LIGHT ON
                 5: SET LIGHT OFF
                 6: DIMMER LIGHT On/Off
                 7: DIMMER LIGHT Level Controll
                 8: DETECT MOTION
                 9: DISALLOW JOIN
                 10: READ ATTRIBUTE STATUS
                 11: EXIT FROM APPLICATION

                 Enter Option :
INIT-BEINGosal_set_event

osal_msg_sendosal_set_event
osal_set_event
osal_set_event
devState is 0
Register application endpoint..
osal_set_event
devState is 0

osal_msg_sendosal_set_event
osal_set_event
ZigBee Coordinator
ZDO_UpdateNwkStatusZDO State Change

osal_msg_sendosal_set_event

osal_msg_sendosal_set_event

HA_eventHandlerosal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event
osal_set_event

osal_msg_sendosal_set_event

osal_msg_sendosal_set_event

HA_eventHandler
DEVICE ANNOUNCE
u16SrcShortAddr = fc55LIST IS EMPTYAdd new node for Dimmer
New Node added

Node  Details...

Node IEEE address : 137a000000ae5c
Node NWK address : fc55
-------------------------------------
osal_set_event

osal_msg_sendosal_set_event

osal_msg_sendosal_set_event

osal_msg_sendosal_set_event

HA_eventHandlerosal_set_event

osal_msg_sendosal_set_event

osal_msg_sendosal_set_event

Here the cordinator device is UP.  On connecting Light Switch I am getting continuous logs

osal_set_event
osal_set_event
osal_set_event

However When I connect Dimmer switch it displays its network and IEEE address.

DEVICE ANNOUNCE
u16SrcShortAddr = fc55LIST IS EMPTYAdd new node for Dimmer
New Node added

Node  Details...

Node IEEE address : 137a000000ae5c
Node NWK address : fc55

Why is Device one ie Light Switch not getting discovered. ??

Also will the both switch devices share same network (short address) ?? How are the devices assigned network address ??

 

Regards

 

  • 0
    TI__Genius 9325 points

    Hi Supriya,

    Just for clarification, are you using Control Bridge in Z-Stack Light 1.0.2?

    - Cetri

  • 0
    TI__Genius 9180 points

    This  log does not look like any sample application provided by TI and it also looks to be running in a Linux terminal. Can you elaborate on the product that this is based on? Is it using ZNP and a port of some TI ZigBee code to Linux?

    supriya negi said:
    Why is Device one ie Light Switch not getting discovered. ??

    From the log it is hard to see what is happening, I only see 1 end device announce, it would be good to have a packet trace to see if 2 devices did join the network.

    supriya negi said:
    Also will the both switch devices share same network (short address) ?? How are the devices assigned network address ??

    No each device will have a globally unique IEEE address and a unique (to that PAN) short address.

    Regards, TC.