LabVIEW
Timed loops
You have 16 x 0.5sec waits in all the sequences, which is 8 seconds. Your timed loop is programmed to repeat every 18 seconds. You don't have any wait programmed, so that 10 second extra wait assumes that the rest of your code does not use any time at all.
The only thing to check is if the timed loop executes every 18 seconds. Does it?
For some reason, your "loop condition" terminal is not wired, but you say "Run Continuously" in big red letters. How is the loop condition wired. Does the timed loop (1) keep spinning by wiring a "continue" to the terminal or do you (2) keep it running by pressing the "continuous run" button in the tool bar? Only if you do (1), your loop will behave as expected. If you do (2), you inter-loop timing will be meaningless.
I am not sure why you even use a 17 frame sequence, because except for a few booleans and constants, the code in each frame is absolutely identical. This calls for a FOR loop. With proper FOR loops, you need exactly one instance of Dbitout (and not 68!) and 2 instances of Dbitin (and not 52!) and you don't need any local variables. You have again your weird logical constructs that can be simplified (e.g. a "not equal false" is "same", and a "not equal true" is a "Not", right?).
I just spend 5 minutes to show how to simplify your diagram (LV7.1) without any loss in functionality (please double check. I cannot test because I don't have your subVIs)). The code is now less that 10% of your code, much more efficient, and easier to maintain. Let me know if you have any questions.
The only thing to check is if the timed loop executes every 18 seconds. Does it?
For some reason, your "loop condition" terminal is not wired, but you say "Run Continuously" in big red letters. How is the loop condition wired. Does the timed loop (1) keep spinning by wiring a "continue" to the terminal or do you (2) keep it running by pressing the "continuous run" button in the tool bar? Only if you do (1), your loop will behave as expected. If you do (2), you inter-loop timing will be meaningless.
I am not sure why you even use a 17 frame sequence, because except for a few booleans and constants, the code in each frame is absolutely identical. This calls for a FOR loop. With proper FOR loops, you need exactly one instance of Dbitout (and not 68!) and 2 instances of Dbitin (and not 52!) and you don't need any local variables. You have again your weird logical constructs that can be simplified (e.g. a "not equal false" is "same", and a "not equal true" is a "Not", right?).
I just spend 5 minutes to show how to simplify your diagram (LV7.1) without any loss in functionality (please double check. I cannot test because I don't have your subVIs)). The code is now less that 10% of your code, much more efficient, and easier to maintain. Let me know if you have any questions.
