Multiple timed loops issue?

[RnDMonkey]

I have noticed this a couple times: If I copy a VI (in windows explorer) that contains a timed loop then try to run it, the timed loop will not execute if the other VI (and its timed loop) is running. I figured this was because of a conflict in the processor assignment, so I set them to different processor cores but that did not work. This time I just wanted something that worked roughly so I replaced the timed loop in the second VI with a while loop and added a "Wait Until Next ms Multiple" to approximate what the timed loop would do. For some reason I decided to go back to the timed loop by selecting "Replace with timed loop" and lo and behold, it works now! I wonder if the processor assignment was not actually updated when I changed the constant wired to the input?

[AdnanZ · Accepted solution]

If I take a guess, it's probably because you have not changed the Loop name. You can access this by double-clicking on the timed loop itself. When you replace it with a while loop and then replace again with a timed loop, it will probably change the name. It's a good observation that should be looked into by the R&D dept.

[RnDMonkey]

I'm using LabVIEW 8.6, and I have no properties available to me for the timed loop. I do, however, find the Name input node. I'm guessing the name is generated from some seed when the timed loop is created, and it looks like you are correct. When those strings are different, they both work. It's not a glaring bug in the software, but it is not communicated to the user well at all, especially considering how quick LabVIEW is to tell you "Resource is reserved" in so many other cases.

[ColeTrain]

Ryan,

If you add an error wire and error handler to the outside of the timed structure that does not run, you will see error -808 which specifies that the loop name is already in use.