06-27-2022 12:45 PM
You still attached the LabVIEW 2021 version. The down-converted version (and its dependencies) should be in a similarly named new folder next to it.
06-28-2022 12:53 AM
Thank you for your patience. Now it is the right Version
06-28-2022 02:37 AM - edited 06-28-2022 02:55 AM
Sorry, I cannot efficiently analyze such an oversized diagram on my laptop screen, but the entire things is not really a state machine, but just a downhill spiral. As soon as the event fires once, you go to the instrument state and the table state can never be reached again. This entire things needs to be able to breathe!
A proper state machine needs to ensure that the UI is serviced several times per second.
You also have glaring race conditions due to the fact that your button (and other) terminals are not inside their respective event case. This means that inside the event, you get the values (probably all false/stale) that existed when the terminal was read, not the new values after the evet finally fires. Only if the terminal is inside the event case, the new state is read from the terminal.
Make sure you fully understand the magic of dataflow before doing any more work on this! There are tutorials. Play with some simple examples.
Maybe sit down and draw a full state diagram of all possible states and all possible transitions. Then change the program accordingly.