Konrad Banachowicz

I get the update on multi-camera problem from PTGrey support. They state that the problem have been fixed in 2.9.3.13 release. My initial testing with two Blackfly confirms that problem...

I can generate the error by running fallowing ops in deployer: ``` import("rtt_ros") import("rtt_roscomm") ros.import("rtt_controller_manager_msgs") ros.import("conman") ros.import("conman_ros") ros.import("conman_blocks") loadComponent("CM", "conman::Scheme"); setActivityOnCPU("CM", 0.1, 0, ORO_SCHED_OTHER, 3); CM.loadService("conman_ros"); CM.configure(); loadComponent("test1", "conman_blocks::VectorSum"); addPeer("CM",...

ping

The #31 fix the crash but some warnings remains: 3.248 [ Warning][ScriptingService] Extra argument discarded for OperationCallerC. 3.248 [ Warning][ScriptingService] Extra argument discarded for OperationCallerC. 3.248 [ Warning][ScriptingService] Extra argument...

It's beater but: .353 [ Warning][ScriptingService] Extra argument discarded for OperationCallerC. 1.353 [ ERROR ][ScriptingService] Constructing RemoteOperationCaller for getBlocks was not possible. 1.353 [ ERROR ][ScriptingService] Probable cause: Bad DataSource...

I was thinking about something similar. I would no like to define dependencies explicitly. Instead we can annotate the input port that they require data (>= 1 active writer) similarly...

I think that is possible. As it's configured on per port basis. Your example is already possible using only exclusivity mechanism. We can configure "position command" input port to be...