Bug #215

Number of attempts for retry comunication not used

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

Status:Closed Start date:08/29/2013
Priority:Normal Due date:
Assignee:Giancarlo Riolo % Done:


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


With the parameter it.cnr.isti.zigbee.driver.communication.retry.count the number of retries can be set in the configuration file.
Independent of the value of this parameter, the number of attempts is always 4.
(using revision 701)

Associated revisions

Revision 859
Added by Giancarlo Riolo almost 5 years ago

refs #215 . Test Made for communication.retry.count, updated while counters for readibility, updated test for DeviceBuilderThread.


#1 Updated by Stefano Lenzi about 5 years ago

  • Category set to zigbee.basedriver
  • Status changed from New to In Progress
  • Assignee set to Giancarlo Riolo
  • Target version set to org.aaloa.zb4osgi.zigbee.basedriver-1.X

#2 Updated by Giancarlo Riolo almost 5 years ago

Can't replicate. We made a test for it, and the test works. We also updated some while indexes for readibility sake.

#3 Updated by Han Alink almost 5 years ago

  • Status changed from In Progress to Closed

Yes, your right; the number is affected by the config item (In my application, the config files are read from another location, which I forgot to change while testing this config item). Sorry for the confusion. I close the item.

#4 Updated by Stefano Lenzi over 4 years ago

  • Subject changed from Detection of devices to Number of attempts for retry comunication not used
  • Target version changed from org.aaloa.zb4osgi.zigbee.basedriver-1.X to org.aaloa.zb4osgi.zigbee.basedriver-0.8.0

Preparing for release

Also available in: Atom PDF