@jbm
In the debugging code snippet below the objective is to:
- Make sure the vision system has been started.
- Pause URSim at each popup in order to observe the state of the vision system, the xmlrpc server log and/or the URSim variables.
As shown in the image below, the first popup is being displayed, but the variables field shows that we are at the “3rd blob should be loaded” state (3.0 in the 2nd to last field). All the calls to the xmlrpc server have already been made and the last target data is now in memory. There was no opportunity to observe the intermediate behavior.
In actual production operation, if the operator had seen that the vision system had not been started, there would have been no opportunity to correct the situation. Instead the robot would have tried to go ahead anyhow -with unpredictable results.
I’m not sure whether this answers your timing-frame question.