CC2530: Change from end device to router

How do I use ZAP-ZNP mode?

You have to use an extra MCU to act as ZAP and CC2530 as ZNP. You can refer to Z-Stack ZNP Interface Specification.pdf in Z-Stack document folder for details.

Why can't all this be done using only 1 MCU?

Everything is possible. You can try to run ZAP-ZNP on single MCU.

Hi,

In the out of box sample applications, run-time logical device type configuration is only available if the CC2530 is running the ZNP application. It may be possible to design your own logic in your application to modify the global zgDeviceLogicalType and set it based on the scenario you mention. You can search for this variable in the code to see what is happening but basically zgDeviceLogicalType needs to be set before you start network formation/joining (i.e. before ZDOInitDeviceEx() is called).

I can't guarantee this will work nicely because it hasn't been tested, but it is a starting point. I'd recommend you start with the Router build configuration in IAR and then add your logic into the sample application from there.

You cannot change role dynamically which would confuse whole mesh network. You should make device leave network first, and turn role to router to do a fresh joining process.

ZNP is not a device type, it is comparable to a sample application, like SampleLight. With SampleLight, you can have a device act as an end device, a router, or a coordinator. The difference with ZNP is that when you make a ZNP device on CC2530, you do not have to choose a build configuration at compile-time like you do with SampleLight. You know how in IAR for SampleLight you choose either coordinator, router, or end device before you build your code? You don't have to do that with ZNP, with ZNP you choose the logical device type at run-time (as opposed to compile-time). This is done by setting the value for zgDeviceLogicalType, and then calling the API ZDOInitDeviceEx() which starts network formation/joining (in Z3.0, that API is called by the BDB commissioning API).

One key point you have to understand about this is that you cannot "switch" device types after you have initialized your device as a single logical type. This is to say, after you set zgDeviceLogicalType for the first time and then initialize your device, you may not switch its type unless you factory reset the device.

My second point from above is that the sample applications like SampleLight are not designed to be able to configure logical device type at run-time, the sample applications only provide the means to set logical device type at compile-time, i.e. you must configure it in IAR before you build your application. I also mentioned that it may be possible to change it to a run-time configuration, but this is not supported by default in the out-of-box sample applications, you would need to implement it yourself. As for how to do that, refer to my previous post.

Maybe try to manipulate zgDeviceLogicalType in ZDAppDetermineDeviceType().

I tried setting zgDeviceLogicalType = ZG_DEVICETYPE_ROUTER in ZMain.c, but it didn't seem to change the config from end device to router. What else do you suggest?

You can't start with an end device project and turn it into a router by setting zgDeviceLogicalType to ZG_DEVICETYPE_ROUTER, the code that is required for the device to be a router will not be present in the build.

You may be able to start with a router project and turn it into an end device though. You may also need to change the libraries that are linked into the build, go to Project Options > Linker > Extra Options and change Router-Pro.lib to AllDevice-Pro.lib. Beyond that, I suggest you look into the ZNP project code to better understand how exactly it is able to have all three device types in one build configuration.

1. ZNP contains all ZC/ZR/ZED configuration and it depends on ZAP to assign which role it would run.
2. zclSampleLight_UpdateLedState is application code and there is no mapping function in ZNP.