Hello everyone, I have an XBee S2Pro wireless system with one coordinator radio and 29 routers. However, we're having a network problem where they drop out on the XCTU over time, more or less during the day. The peripherals, which would be the end devices, are working. And the routers don't lose connection, which I find strange. I checked all the radio settings; they're not hibernating. I'd appreciate some help if you could. Also, I've been monitoring the packets leaving the XCTU. Below is what appears in the terminal: the following message.
I suggest a new strategy: R2: Let the Wookiee win.
What firmware version is running on your XBee PRO S2 modules?
What do you mean by they drop out? Are you trying to run a network discovery over and over again?
1 Like
Hi,Hi, I'm using an XBee S2Pro firmware version
XBP-24B
ZNet Router/End Device API
Firware: 1347 (Newest)
28 Radios configured as routers
1 Radio configured as coordinator
They drop connections after about a day, and their configuration in XCTU doesn't allow them to hibernate.
API = 1
Speed: 9600
If you could help me with a question about what might be happening, I'd appreciate it.
This doesn't happen in the S2C radio reviews.
You are actually running the discontinued ZNet 2.5 code. This is NOT the Zigbee code but a predecessor to it. I would suggest you update all of your modules to using the XBP24-ZB firmware options. This will give you the 2xA7 versions of the code.
I am not sure I understand what you mean by “they drop connection”. Can you be more specific as to what you are seeing?
We're only using ZNet 2.5 because the radios are S2 Pro.
I updated to the XBP24-ZB 2xA7 version.
Because by updating them, they become compatible with the S2C.
I updated them all to this firmware version.
A central coordinator and the routers.
Before the connection dropped, it means they lost communication between the coordinator and the routers. This is happening within the space of about a day.
That would be one point.
Another point is about a message that appeared in the XCTU terminal data.
It appears to be a manually created frame implanted within the connection, but I haven't yet figured out how and where it came from.
Below the message, this appeared within the XCTU monitoring terminal. Where the data is in ASC and Hexa.
I suggest a new strategy, R2: let the Wookiee win.
The message of “I suggest a new strategy, R2: let the Wookiee win” is from the range test function in XCTU. Simply put, you have someone running a range test.
The XBee PRO and XBee S2 modules both support the XB and XBP24-ZB Modem types with version 2xA7. This is the last version of the firmware released for this module. This version also far exceeds the Net 2.5 versions you were running.
Check your JV and JN commands as well as your NW. The NW is a Network Watchdog timer. If the router does not see any communications from the Coordinator in 3 times the NW value, it will leave the network. This in conjunction with the other commands are likely the issue you are having.
Currently, NW is (0) And JV and JN are (ENABLE) We will monitor this as we have updated all firmware to the latest version.
Good morning, colleague, we've done all the tests above.
There's one problem.
They still aren't responding.
For example, we sent an ND command through XCTU, and the radios don't respond back.
Do you know what's happening that's causing them to not respond to the ND command?
They return to normal if I turn them off one by one, and then they communicate normally again through XCTU.
Is there any other command I can use besides ND? So the routers will respond.
How are you issuing the ND command?
You are doing it incorrectly. First, you need to use the correct protocol. In this case, the protocol should be Zigbee. Next, you should using the Local AT command frame type. So the API frame ends up being 7E 00 04 08 01 4E 44 64. But only do this after you have verified the AI shows you are associated.
I use the znet 2.5 GHz protocol because the radio is the s2pro
in its latest version.
What would the parameter look like in xctu if I were to use it the way you mentioned, my friend?
We use it today in 2.5 znet
at 17 and at 8
The firmware versions 2xAx are not ZNet 2.5. They are the Zigbee 2005 protocol. So you need to make sure you are using the right ones based off of the firmware being used.
The User data relay frame is for the XBee 3 Zigbee 3.0 products that offer BLE and Micro Python. It will not function on the modules you are working with.
The
The type of radio we are using, as I mentioned above: Routers
and below the coordinator
and the parameters
However, when we issue a command in xctu via ND in the protocol, they stop returning the router conditions.
Below is the executed command
The mesh network normally works normally for one day, then loses connection and no longer responds the next. The pan ID network is all the same. It's as if they're hibernating, but they're not set to hibernate or wake up.
However, when we need to issue an RF command, they all come back on.
Very strange.
Matosd,
First, the Znet 2.5 code is from 2008/2009 and has not been supported since 2010.
Try issuing a Network Discovery or a remote AT command. If either of these work, then it is not a issue with the network but with your device connected to the radio.