time_to_expire wrong value in aging time out from 128min

[sirius12]

Hi,

I have a problem in parent node.

When I use gc_neighbor[i].u.base.time_to_expire for caculator time to expire in child node by:

zb_time_t exp_time = ZB_TIME_SUBTRACT(gc_neighbor[i].u.base.time_to_expire, ZB_TIMER_GET());
NRF_LOG_INFO("time to expire %d", ZB_TIME_BEACON_INTERVAL_TO_MSEC(exp_time) / 1000);

But when

gc_neighbor[i].u.base.nwk_ed_timeout = ED_AGING_TIMEOUT_128MIN

 or bigger, exp_time is not true.

What should I do in this case

Thanks.

[Edvin]

Hello,

Does it work if you set anything below ED_AGING_TIMEOUT_128MIN?

I am not sure exactly where you are setting this. Are you trying to change the timeout value for the other devices in the network? And what do you mean by "exp_time is not true"? Is it "false", or "incorrect"?

Best regards,

Edvin

[sirius12]

Hi,

It works if I set anything below ED_AGING_TIMEOUT_128MIN. I don't change the timeout for the other devices by ZC. 

The result of 

ZB_TIME_SUBTRACT(gc_neighbor[i].u.base.time_to_expire, ZB_TIMER_GET());

 is incorrect. In case ED_AGING_TIMEOUT_256MIN the result changes from about 2650 to 0 then increases to about 4500 and decreases to 0. It repeats until the total is 15360s is expire of 256min.

I hope the result is correct and does not repeats.

Thanks.