Example for testing process synchronization and the use of logic in RoboPro.
See also
This will run in the simulation mode, so no controller needed to see what is happening.
Notice the different in behavior in cases of option 1 and 2!
RoboPro file
Example of process synchronization
Forumsregeln
Bitte beachte die Forumsregeln!
Bitte beachte die Forumsregeln!
Re: Example of process synchronization
The question is: Will the test always work well?
My guess is not always.
The problem is the logic after the "and" operator.
Take in mind that this is workflow programming and in fact this is a fundamental issues.
What is the condition under which the "wait for 0->1" will work?
My guess is not always.
The problem is the logic after the "and" operator.
Take in mind that this is workflow programming and in fact this is a fundamental issues.
What is the condition under which the "wait for 0->1" will work?
Re: Example of process synchronization
In part 1 we have see a first solution for 3 parallel processes.
But this solution knows some problems.
Hereby an improved solution and the RoboPro file (simulation mode, no controller needed):
But this solution knows some problems.
Hereby an improved solution and the RoboPro file (simulation mode, no controller needed):
Re: Example of process synchronization
I discussed a similar solution on the Parallel Processing page and used it on Very Large Model: Defining the Processes.
Re: Example of process synchronization
Hi Rei,
Thanks for your contribution.
I guess that your "O" is the same as the "Y"?
You assume that during the initialisation of this subroutine a "0" has been send to all the "AND" inputs.
Has this been documented in the RoboPro help?
Otherwise local variables (start value 0 will resolve this) between the assignment elements and the AND element can help.
I would like have preference for a wait-element in the most left part, this to avoid a race condition.
The link to Michael's feedback is not valid anymore.
Kind regards,
CvL
Thanks for your contribution.
I guess that your "O" is the same as the "Y"?
You assume that during the initialisation of this subroutine a "0" has been send to all the "AND" inputs.
Has this been documented in the RoboPro help?
Otherwise local variables (start value 0 will resolve this) between the assignment elements and the AND element can help.
I would like have preference for a wait-element in the most left part, this to avoid a race condition.
The link to Michael's feedback is not valid anymore.
Kind regards,
CvL