Other Parts Discussed in Thread: Z-STACK
Hi ! In SWRA175A document, 6.3.12.2 description device state, but I can't find detail descip description. Who can tell me, Thanks.
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.
Other Parts Discussed in Thread: Z-STACK
Hi ! In SWRA175A document, 6.3.12.2 description device state, but I can't find detail descip description. Who can tell me, Thanks.
Good question. It seems to be missing from the document.
However, I had a look at the documentation for the SimpleAPI that comes with the Z-Stack, document called "Simple API for Z-Stack_..._.pdf". By assuming the software and interfaces have much in common and looking at documentation for the "zb_GetDeviceInfo" request with the "ZB_INFO_DEV_STATE" parameter, it may seem like the CC2480 ZB_GET_DEVICE_INFO request with parameter=0x00 (device state) share the same return values. And according to SimpleAPI for Z-stack the return value is defined to be:
Simple API for Z-Stack said:
The current state of the ZigBee
device. This can take one of the
values in the devStates_t
enumeration in ZDApp.h file.
... and by looking into that file, I see ...
ZDApp.h, Revision: 15800 said:
typedef enum
{
DEV_HOLD, // Initialized - not started automatically
DEV_INIT, // Initialized - not connected to anything
DEV_NWK_DISC, // Discovering PAN's to join
DEV_NWK_JOINING, // Joining a PAN
DEV_NWK_REJOIN, // ReJoining a PAN, only for end devices
DEV_END_DEVICE_UNAUTH, // Joined but not yet authenticated by trust center
DEV_END_DEVICE, // Started as device after authentication
DEV_ROUTER, // Device joined, authenticated and is a router
DEV_COORD_STARTING, // Started as Zigbee Coordinator
DEV_ZB_COORD, // Started as Zigbee Coordinator
DEV_NWK_ORPHAN // Device has lost information about its parent..
} devStates_t;
This means that *I think* the return values 0x00 = DEV_HOLD (the first value: initialized, not started automatically), ... etc ... and 0x10 = DEV_NWK_ORPHAN (the last value in list: device has lost info about parent).
Since I cannot confirm 100 % that this applies to CC2480 (it's just my educated guess) it would be nice if a TI-er with confident knowledge about this part can verify it.
Hi stole my lunch,
You are correct! Great answer. Yes, it is missing from the docs...
Hi,
These states also apply if you are using the ZDO callback ZDO_STATE_CHANGE_IND. It is a nice callback if you would like to know the state of CC2480. This is the ZDO IF command described in the section 6.5.32. You will get this callback if you use AF_REGISTER together with ZB_START_REQUEST for example.
LPRF_Rocks
Hello,
I have some CC2480 NOOB questions and hope this is the correct area for this post. I just got a eZ430-RF2480 Kit v1.1 and, as is my usual mode, am in a state of confusion. I would like to use the kit with the Z-Stack 2.1.0 and the Smart Energy Profile. What steps do I need to take to do this?
1) Is the latest 30 day eval for IAR EW for the TI MSP430 the correct dev toolset for the eZ430-RF2480 Kit?
2) How do I upgrade the kit for the latest Zigbee PRO Z-Stack 2.1.0 and Smart Energy?
3) Z-Stack downloads at the TI website seem to bee for the 2420, 3430.31 and 2520. Which one do I download for testing with the 2480?
Thanks,
David
.