I have an additional data. I open the pxbee_update (the soft provided by Digi to update fw over the air) and sometimes it doesn’t work. It doesn’t detect the coordinator.
I open XCTU, detect coordinator and it works. Now i go back to the pxbee_update and everything is ok
mvut, thanks for your response. All the nodes in my network have to work in API mode, because it has to be mesh.
I understand that if i set the coordinator in AT mode, maybe i could send frames to any node (because i will send the right frame from the PC) but i’m not sure about receiving frames correctly from any node
API vs AT firmware versions has nothing to do with if it will work on a Mesh network or not. API vs AT only has to do with the interface from the device or PC and the radio via its UART.
Remember, we are not troubleshooting a network or Radio to radio communications. We are troubleshooting your PC’s ability to Open a COM port and communicate with the radio connected to it. The other question is, what is the XBee module mounted on or connected to that is connected to the PC?
This sounds like you are using a Programmable XBee module. What is the FULL part number on the Xbee module? That is the XBP24 number on the white label?
This is a Programmable module. You just don’t Open a port and and and receive data over it like you do with the standard XBee modules. This one has a 2nd processor installed that requires you to develop and upload an application to before you can do anything with it. This is why you are having issues accessing it and XCTU is able to. To resolve your issue you need to either upload the transparent application to the Freescale processor via a BDM programmer or switch to the Non programmable modules.