Bug #179

Timeout value

Added by Han Alink about 5 years ago. Updated almost 4 years ago.

Status:Closed Start date:02/01/2013
Priority:Low Due date:
Assignee:Stefano Lenzi % Done:

0%

Category:zigbee.basedriver Spent time: -
Target version:org.aaloa.zb4osgi.zigbee.basedriver-0.8.0
Has a patch:No Has license agreement signed:No

Description

I'm trying to overcome a timeout which generates the message: "Unable to send cluster on the ZigBee network due to general error - is the device sleeping?"
This message is generated about 3 seconds after a command is issued.
The default value (TIMEOUT in ZigbeeDeviceImpl.java) is 5000.
The timeout value is a configuration item which can be set in the configuration file (org.aaloa.zb4osgi.zigbee.basedriver.timeout=10000).
For some reason the timeout is not influenced by this setting (and is also shorter than the default value).

Associated revisions

Revision 625
Added by Stefano Lenzi about 5 years ago

Added a new timeout property zigbee.driver.ez430_rf2480.timout for CC2480 driver ( refs #179 )
Using a constant for setting default timeout on basedriver

Revision 627
Added by Stefano Lenzi about 5 years ago

Enable custom timeout, as for CC2480 driver see r625 ( refs #179 )

History

#1 Updated by Stefano Lenzi about 5 years ago

  • Category set to zigbee.ez430-rf2480.driver
  • Status changed from New to Resolved
  • Assignee set to Stefano Lenzi
  • Priority changed from Normal to Low
  • Target version set to org.aaloa.zb4osgi.zigbee.basedriver-0.7.0

You are right I have just figured out that there are two different timeout when sending cluster on the network, the first timeout was related to zigbee.ez430-rf2480.driver and it was fixed to 5000ms, while the other was related to the zigbee.basedriver and it is controlled by the property org.aaloa.zb4osgi.zigbee.basedriver.timeout. The problem was that when the first timeout fires the second one is not used at all.

Now you can control the first timeout with the System Property zigbee.driver.ez430_rf2480.timout and you should be aware that the default value has been decresed to 1000ms. Moreover, you should keep in mind that the actual timeout for cluster communication is the minimum between
org.aaloa.zb4osgi.zigbee.basedriver.timeout and zigbee.driver.ez430_rf2480.timout

I hope it can help, let me know if it works for you and close the ticket in case.

P.S.: Off course, I'm assuming that you are using the zigbee.ez430-rf2480.driver as ZigBee Interface Controller ( driver )

#2 Updated by Han Alink about 5 years ago

No Stefano, I'm using the CC2530!

#3 Updated by Stefano Lenzi about 5 years ago

I have updated the changes also to the zigbee.CC2530.driver, in this case the System Property to set is zigbee.driver.tsb.timout

Let me know if it works and close the ticket in case...

#4 Updated by Han Alink about 5 years ago

  • Status changed from Resolved to Closed

Yes, this solves the timeout problem. Closing the ticket

#5 Updated by Stefano Lenzi over 4 years ago

  • Category changed from zigbee.ez430-rf2480.driver to zigbee.basedriver
  • Status changed from Closed to Resolved
  • Target version changed from org.aaloa.zb4osgi.zigbee.basedriver-0.7.0 to org.aaloa.zb4osgi.zigbee.basedriver-1.X

#6 Updated by Giancarlo Riolo almost 4 years ago

  • Status changed from Resolved to Closed

#7 Updated by Stefano Lenzi almost 4 years ago

  • Target version changed from org.aaloa.zb4osgi.zigbee.basedriver-1.X to org.aaloa.zb4osgi.zigbee.basedriver-0.8.0

Preparing release

Also available in: Atom PDF