04-29-2012 06:46 PM
Ouadji, rather than trying to force data flow onto an anti-pattern, it is usually best to sit back and look at the architecture and see if it can be done better. Additionally, that is a lot of copy-pasted code, which resulted in that small error you picked up. Your code would be better created as re-entrant VIs (or class) with an initialising data set, and no redundant or copy-pasted code.
With regards the original question, I am certain there is a more elegant solution than performing a synchronous operation on two non-synchronous loops. Perhaps a bit more information, or a demo snippet or VI. Steve's snippet in post 3 looks good for the description of your problem.
05-02-2012 11:54 PM
Thank you everyone for giving your time to answer my query. I went forward and played with the data communication structures in the LabVIEW. So what I found was a "local variable". I could actually set this up to read the data from the required variable hence, was able to compare the data from both the loops. For those of you who wrote about the Global variable, from what I learnt, it is actually used to communicate between different VI's rather than variables in the same VI (please correct me if wrong). Both the loops were necessary in my program because each of them had a different timing intervals.
-Sanjog