LabVIEW
Tab page not giving command if not selected
Solved!
A case structure is not a tool to organize the diagram. Learn about modular program design, create subVI, create independent while loops. As an ugly bandaid, you could leave the current case structure, but make sure that it iterates through all cases at all times. If a lot of things need to be done, the code cannot focus on only one thing.
You have an incredible amount of duplicate code. Also instead of all these individual scalars, you could use arrays or clusters in many places. This would reduce the code size by orders of magnitude!
altenbach wrote:You have an incredible amount of duplicate code. Also instead of all these individual scalars, you could use arrays or clusters in many places. This would reduce the code size by orders of magnitude!
For example, you get and format the current time 12x in parallel. Once is enough! Also, of you leave the input of get date/time unwired, it default to the current time. 24x too much code!!!
Now lets' look at your LED columns indicators. All you need is a tiny FOR loop and an array of LED (might need a few tweaks to get the exact same transitions, but I doubt lt it matters). Attached is a very simple comparison between the two methods. Mine uses 100x less diagram space. (image and attached code). All you need is the code in the yellow square!
Similar methods could be applied to most of your code!.
@Asif138 wrote:
can you tell me what is constant "4" in while loop?
There is no while loop, just a FOR loop and the 4 is outside the loop (but used inside the loop). The 4 tells how many bits to left-shift the number from the iteration terminal. A left shift by 4 (of a positive integer in a suitable range) is equivalent to a multiplication by 2^4, i.e. 16. You can just multiply by 16 instead, same difference.
