http://bugs.orocos.org/show_bug.cgi?id=829

Summary: Actual reporting frequency does not always correspond
to the period of the reporter activity
Product: Toolchain
Version: 2.2
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P3
Component: OCL
AssignedTo: orocos-dev [..] ...
ReportedBy: tinne [dot] delaet [..] ...
CC: orocos-dev [..] ...
Estimated Hours: 0.0

I noticed that the actual reporting frequency does not always correspond to the
period of the reporter activity.
When one of the components I report has a frequency of 0.001 (peer of the
reporter), the reporter starts reporting at 0.001. When I ask him his Period he
still shows the period I set in the deploy script.
Strangely I don't have any problems if I set the frequency of the component to
be reported to 0.01 or higher.

I also tested with toolchain 2.3 but still the same problems there ....

This is a sample of the deploy script:

import("force_registration_app")
import("krypton_component")
import("ni_6024E")

#Create the components we need
loadComponent("jr3","jr3::jr3")
loadComponent("ForceStamper","force_stamper::ForceStamper")
loadComponent("ni_6024E","OCL::NI_6024E")
loadComponent("Reporter","OCL::FileReporting")

#Set the components activity
setActivity("jr3",0.1,HighestPriority,ORO_SCHED_RT)
setActivity("ForceStamper",0,HighestPriority,ORO_SCHED_RT)
setActivity("ni_6024E",0.01,HighestPriority,ORO_SCHED_RT)
setActivity("Reporter",1.000,LowestPriority,ORO_SCHED_OTHER)

#add peers
addPeer("Reporter","jr3")
addPeer("Reporter","ForceStamper")
addPeer("Reporter","ni_6024E")

.....

# set reporter
Reporter.reportPort("jr3","sensor_0.wrench_filter_0")
Reporter.reportPort("ni_6024E","Analog_Input_Values")
Reporter.start()