I've been thrust into the world of ZigBee for a project I'm doing for my employer. My goal is to use a Digi XBee Pro Series 2 (XBP24-27WIT-004) module to communicate with a TI CC2530 one. I have a testbed set up with the CC2530 Development Kit and several of the Digi modules in fixtures that allow me to use them with USB and serial ports on my computer.
I've successfully loaded the ZigBee stack and sample program into the CC2530 development kit and had the CC2530 router talk to the CC2530 coordinator. I've also flashed the DIgi modules as router and coordinator and have had them talk to each other. I've even had the CC2530 router use the XBP24 as its coordinator.
The problem I'm having is with the one configuration I actually need for my project -- where the XBP24 router uses the CC2530 as its coordinator. Using the Daintree sniffer with the CC2531 USB dongle, I think that I've isolated the problem, but I'm not sure whether to blame TI or Digi. There's a slight difference in the ZigBee NWK Beacon packet that the two coordinators emit in response to the XBP24's beacon request packet.
In the case of the XBP24 coordinator, the key part of the packet looks like this:
But in the case of the CC2530 coordinator the same response look like this:
I've boldfaced and underlined the difference. Basically, the TI part is reporting a stack profile of 0x01, whereas the Digi part is reporting a stack profile of 0x02. The latter seems more correct to me, because, as you can see from the protocol version, it is 0x02, but I really don't know what's correct.
I'm hoping that someone here with more experience can help me, and perhaps point me to the correct person at TI if it turns out to be something that they need to fix. I already have a contact at Digi to help me out.
Thanks in advance for any assistance!


