Problem with WaitAndUpdateAll if a production node is created but not generating data

80 views
Skip to first unread message

Frederic Garcia

unread,
Dec 4, 2012, 5:33:42 AM12/4/12
to openn...@googlegroups.com
Dear all,

I've created a conetxt with three production nodes, depth, image and ir. As you may know, we cannot grab ir and image data at the same time. So, in order to switch between the two differents operating modes I'm stopping and starting generating data of the respective production nodes. The problem arises when updating the data from the sensor.

If I use WaitOneUpdateAll(depth), the system doesn't crash, however, I'm sure that the depth node contains good data while the image node may not. I'd like to use the command wait and update all, but the problem here is that the sensor waits data from all created nodes, even if they are not generating data. Is it normal? I thought that wait and update all was waiting data from only those nodes that are producing data...

Do you have any idea of how can I be sure that data in the nodes is updated at the same time and "new"? Or can I repeat the waitoneupdateall for all "active" production nodes?

Thanks,
Frederic
Reply all
Reply to author
Forward
0 new messages