Home/Support/Support Forum/Xbee endpoints randomly stop transmiting

Xbee endpoints randomly stop transmiting

+1 vote
I have a network consisting of the coordinator, two routers under the coordinator and 9 endpoints under each router. The coordinator and endpoints have been programmed with pycharm, so they run my micropython code, while the routers function in the default mode with no custom programs.
The endpoints consist of an Xbee 3 Zigbee that is connected to a SHTC3 temperature and humidity sensor. The role of the endpoints is to send the measured temperature and humidity value to the coordinator once every minute.
The code on the coordinator is simply polling and checking if there are any packets to be received on the RF, while the endpoint code is comunicating with the sensor, reading the temperature and humidity values and sending them to the coordinator, after which it sleeps for 1 minute and then begins the cycle again.
The problem is that after 3 days of running, the endpoints under one of the routers stop transmitting, while the ones under the other router are fine, even if the routers are identically configured.
I can't figure out why this might be so any help will be greatly apreciated.

Thank you!
asked Nov 12, 2020 in XBee3 ZigBee by StfBbt New to the Community (1 point)

Please log in or register to answer this question.

2 Answers

0 votes
What firmware version are you working with?

Are you able to query any settings from the radio via a different radio?
answered Nov 12, 2020 by mvut Veteran of the Digi Community (14,874 points)
From what I recall, the Micro Python sleep function can tell the XBee to sleep as well.  See http://cms.digi.com/resources/documentation/digidocs/90002219/#reference/r_sleep_mp.htm?Highlight=sleep
Yes I was referring to the sleeping end device to run the discovery.
Yes, the function you linked is correct and is sleep_now. What I used, on the other hand, is sleep, which as far as I know is not initiating a 'real' sleep.
As the endpoints are not connected to any PC, I can't really see the result of the discovery function after it's called. I doubt just calling it will solve the problem so I suppose you are you suggesting to call it for debugging purposes to see if it sees the coordinator? In that case is it possible to save the output in file on the endpoint or something like that?
This is to determine where the actual issue is. Or if it is a broken link.
0 votes
An interesting situation, I want to model it for myself and check everything, then I can write a comment!
answered Dec 30, 2020 by liemmayer New to the Community (8 points)
From what I talked to support it seems that my micropython code on the endpoints is the cause, I will try to monitor it to see the error when it occurs.