Hi guys, I am using the Ember Znet SDK V184.108.40.206 and I have already generated the examples such as Z3DimmableLight project and Z3ColorTempLight project, but when I try to build Z3DimmableLight project or Z3ColorTempLight project , then the console shows me the error. And what should I do next and fix the errors?
We have recently seen the following error twice on two different devices, connected to two different host machines. We receive a EZSP_ASH_NCP_FATAL_ERROR from the NCP, and then repeated attempts to initialize the NCP result in EZSP_NOT_CONNECTED. Power cycling the host machine (which also power cycles the NCP) fixed the problem. The problem also seemed to self correct after a few hours.
The NCP is running a custom build of xNCP. However, no additional functionality was added (we are using it as a workaround to a bug present in the 5.7 stack, see this post).
The host side used the Ember EZSP API, but does not use the Application Framework, or AppBuilder.
We are using EmberZNet 5.7.2.
Can I get the source code for the UG252: ZigBee Lighting Reference Design Demo Board Kit.
I am following UG129 reference design guide and have setup the gateway but on the page 10 of this guide it says that the rapsberry pi will publish access point and mobile or laptop can be connected but it does not. I can open local host on RPi and see that the gateway is running on RPi but the WiFi SSID is not showing anywhere
My protocol stack is zigbee 5.9
Now want to do tc swap out of the test
Test steps should be how to proceed?
I am performing partner link key exchange between two non trust center devices. As per Zigbee, The originating node would start this process by sending a bind request command with APS ack to the Key Establishment cluster of the destination device. If a bind confirm is received with a status of success, the initiating device will perform a request key of the trust center. The trust center will then send a link key to each device using the key transport. I am perfoming exact same steps and getting the binding response with a status of success.
But after the perfoming partner link key exchange devices are failing to communicate. I got error status: 0xA6. Verified the link key at both end it is identical.
Checked the binding table entry but it shows zero entry. This might be the reason why communication is not happening. So will the device add entry in binding table for key Establishment cluster automatically or it is to be done manually?
I am using BRD4150c(HOST-NCP Configuration, HOST-PC)and EmberZnet Stack 5.10.
I have a question about the MGM111 and MGM12P modules and hopefully you could help me with my question.
According to the datasheet the radio performance numbers are measured in conducted mode, my basic question is at which point(1 or 2 marked in the attached pictures) should I expect the same radio performance numbers as stated in the datasheet of MGM111/MGM12P?
Is there any document from you Silicon labs telling the impedance of point 1 and 2 shown in the attached pictures?
We are using MGM111 and MGM12P with integrated chip antennas. Can you share with me the specification of the chip antenna as well?
Thanks a lot for your support!
I have the EFR32MG12 radio with the WSTK, and the Border Router kit. I successfully built the Sensor-Actuator sample project in Thread 2.2, successfully built the Border Router, and they talk nicely. I commission my radios throught the Android app, have the radios join the network, they then say (in their console) that they are waiting on a subscriber and when I press Discover on my Border Router web UI, it subscribes and the sensor data appears fine. I can even change the code somewhat.
I then tried the same sample project provided in the Thread 2.4 SDK. It defaults to GNU toolchain, rather that IAR. It builds fine, but I can never get its data to be updated on the BR's web UI. And in the radio's console it never says that it is waiting for a subscriber, but it does say that it joined. Whenever I hit Discover on the BR's web UI, it does not discover any of the radios..
WHat am I doing wrong such that the Thread 2.4 vesion of this sample project works differently than the Thread 2.2. Is there an update to the BR code that I need? Both projects claim to use ZCL. I did notice that the ISC files are considerably different between the two wirth respect to the ZCL/IP and Plugins go.
We are working on Thread Stack v220.127.116.11 since last four months and our application is running fine with border router app and ip driver.
But in long run we see border router restart after crash. Do I need to dig into the issue? Is this version 18.104.22.168 is not stable enough?
What we need to prefer v22.214.171.124 OR v126.96.36.199 , which one is more stable.
We have developed our applicaiton using Out of Band commissioning.
Give us link , where version updgrade notes are available, need to figure out what enhancement have done on v188.8.131.52
i have EFR32MG1P132F256GM48 Chip connected with zero gecko through external debug option,how to start programming with this module ,from where i will get zigbee stack documentation and codes, currently we don't have mighty gecko starter kit ,we have only module and zero gecko starter kit, from where i will get zigbee stack binary files and documentation.
if someone have precompiled zigbee stack binary file please share me.