LabVIEW
Timer vi
We really need to see what you are doing with that missing subVI in order to give some real advice.
If you want multiple loops to be able to read the same timer value, then you could add in some intelligence into your FGV. Use Variant Attributes to hold the values for the timer and you can use a string input to write/read the values to/from the values in the shift register.
(Please don't maximize the fp and diagram to the screen, that's annoying.)
If the timer subVI should have several independent instances, it needs to be reentrant.
Your timer has 32 timer slots. If you want the two loops to use independent times, you need to wire a different "timer number". Since you don't have that input connected, they both use the same timer (0).
I don't understand the need for the non reentrant subVI wrapper. seems completely pointless. Just use the timer subVI directly in your code. (it is already non-renetrant).
Here's how it could look like.
In terms or architecture, your two event structures are just plain silly. Once they have fired once, they are no longer reachable by dataflow, so if you keep pressing these buttons, you'll queue up an infinite amount of events that can never execute. Seems pointless. All you need in each loop is a clean state machine.
I am sure you don't need nanosecond resolution consuming all CPU spinning the loop as fast as the computer allows, so put a small wait in each loop.
I assume that this timer is not your code. Where did you get it?
If the author is still around, there are some changes that would be good. For example I would use high resolution relative seconds because the output only cares about differences. Also, the terminals for "reset", "time target" and "auto-reset" belong on the toplevel diagram. They should not be buried deep inside inner structures (details). Otherwise, the code is pretty clean.
