Device Joining Network in ZStack 3.0

Forgot to add:

ProfileID = 0x104

DeviceID = 0x301

I tested PANID = 0xFFFF and an another random one.

(also: what is the concept of 'finding and binding' mechanism?)

Hi,

Thank you for your explanation.

I was using ZTool 2.0 to replicate a network formation, but when I run SYS_RESET it blocks and doesnt receive any response. 

Any idea?

HW: CC2531EMK witH ZStack 3.0

Regards,

Luca

Hi Luca,

From the Z-Stack MT API Guide: "This command will reset the device by using a hardware reset (i.e. watchdog reset) if ‘Type’ is zero. Otherwise a soft reset (i.e. a jump to the reset vector) is done. This is especially useful in the CC2531, for instance, so that the USB host does not have to contend with the USB H/W resetting (and thus causing the USB host to re-enumerate the device which can cause an open virtual serial port to hang.)"

So perhaps this description relates to the behavior you are observing.  You could also try using a CC-DEBUGGER to determine the state of the CC2531EMK ZNP after this command is sent.

Regards,
Ryan

Hi Ryan,

Thank you for your answer.

I'm following this guide: Sun May Sky: Use ZTool + Z-Stack 3.0 ZNP to set up a basic Zigbee 3.0 network

Is there any way to fix this? He receives a response, while in my case it blocks.

Regards,

Luca

YiKai Chen may have been using different ZNP images or CC253X devices to run his example.  Have you enabled the bootloader and does the ZNP eventually respond (after about a minute or so)?

Regards,
Ryan

ZNP answer to everything, but when it comes to reset it blocks. I waited 5 minute and still nothing ( ZTool loses connection to the dongle).

When I unplug the dongle and plug it back the LED is green, until I click the debug button.

It is kinda weird that ztool doesn't manage this, since in the example I linked it works,

I flashed the firmware from ZigBee2Mqtt Github repository ( without running the patches): GitHub - Koenkk/Z-Stack-firmware: Compilation instructions and hex files for Z-Stack firmwares

Regards,

Luca

If I run ZB_SYSTEM_RESET it works fine.

I don't know if ZB_SYSTEM_RESET and SYS_RESET do the same thing. I need to make sure that SYS_OSAL_NV_WRITE have effect

Once the network has been created, what ZTool packet I need to send to make an end device join?

I have a Danfoss radiator thermostat.

ZB_SYSTEM_RESET description from the MT API: "This command will reset the device by using a soft reset (i.e. a jump to the reset vector) vice a hardware reset (i.e. watchdog reset.) This is especially useful in the CC2531, for instance, so that the USB host does not have to contend with the USB H/W resetting (and thus causing the USB host to re-enumerate the device which can cause an open virtual serial port to hang.)"

Hence the HW reset is the issue, hence why I recommended the soft reset type as previously described.  YK's description most likely involved hardware that was not dependent on the USB peripheral.  However, I am glad to know that you found a path onward.

End devices are responsible for initiating the join by sending Beacon Requests after the network is formed and permit join is enabled (default 180 seconds once the network has started, otherwise perform BDB steering to restart the timer).

Regards,
Ryan

Danfoss send beacons but don't join network. Can't understand why.

Also: could you please tell me how BDB commissioning thing work? While forming a network you need to use "NETWORK FORMATION" and in case of a router "NETWORK STEERING"

this is the end device: AI319043912283en-030108.pdf (danfoss.com)

Danfoss zigbee specification: AM375549618098en-000101.pdf (danfoss.com)

Last question before marking the reply as solution.

The steps to do once the network is formed:

1) Set BDB Commissioning to STEERING

2) Set Permit Join to X seconds.

Once I receive a beacon: does ZTool tell me? Also: once permit join is active does zstack handle all the End Device joining?

Great: Is there a way to perform a network scan to search for end devices (beacons)?

Routing devices do not scan the channel to search for end devices.  Only end devices send Beacon Requests to find networks on the RF channel.  Coordinators and routers keep track of the end devices which have joined directly and will age out children who have not checked in consistently through data polling. https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_5_30_01_01/docs/zigbee/html/zigbee/z-stack-overview.html 

Regards,
Ryan

I can't seem to make the danfoss thermostat join :/

Regards, 

Luca

See whether any of these instructions help: https://www.zigbee2mqtt.io/devices/014G2461.html 

Not much more can be done without a sniffer log.

Regards,
Ryan

I would suggest you to setup sniffer to check what exactly happens over the air about danfoss thermostat not joining issue.