LabVIEW
front panel
Hi Melikyan,
you should stay with my programming using 'states' (IMHO!).
See the comments in the block diagram.
Try to separate your dataflow into a producer/consumer pattern. In the producer loop you can handle the events, in the consumer you do the DAQ part. This will help you to better manage your code.
Or use an action engine with some states (like: 'first run', '2nd run', 'init' and 'reset'). Use subvis for the DAQ part...
you should stay with my programming using 'states' (IMHO!).
See the comments in the block diagram.
Try to separate your dataflow into a producer/consumer pattern. In the producer loop you can handle the events, in the consumer you do the DAQ part. This will help you to better manage your code.
Or use an action engine with some states (like: 'first run', '2nd run', 'init' and 'reset'). Use subvis for the DAQ part...
Hi Melikyan,
it's really easier to use a kind of state machine for your purpose! Read other forum threads about this!
You cannot rely on the the iteration count when it is changed in other events too...
And you have some clearly defined states in your program:
state 1) before 1st run: show "READY"
state 2) 1st run: do measurement, show "Finger", decide which way to go (to next state or back to start)
state 3) 2nd run: do measurement, show result
Again I changed your vi to show how to do this.
It's not a real state machine right now, only some case structures using the state that is kept in the shift register.
it's really easier to use a kind of state machine for your purpose! Read other forum threads about this!
You cannot rely on the the iteration count when it is changed in other events too...
And you have some clearly defined states in your program:
state 1) before 1st run: show "READY"
state 2) 1st run: do measurement, show "Finger", decide which way to go (to next state or back to start)
state 3) 2nd run: do measurement, show result
Again I changed your vi to show how to do this.
It's not a real state machine right now, only some case structures using the state that is kept in the shift register.
Message Edited by GerdW on 08-01-2007 09:26 AM
Hi Melikyan,
first: try to avoid sequence structures - and use flat ones when you really need a structure... (Use sequence locals to wire VISA resource name and error cluster from one frame to the next!)
There are 2 options for your question:
- wait until condition is met: put a while loop around the code in frame 1 and run the while loop as long as the condition is not met (and maybe include an error check as well as a "Break" button for the user)
- don't execute frame 2&3 when condition is not met: split your sequence into 2 parts (frame 0&1 and frame 2&3), put a case structure around the 2nd part
And remember: you can do all this without using sequence structure - all you need is the error cluster to assure a proper execution order
first: try to avoid sequence structures - and use flat ones when you really need a structure... (Use sequence locals to wire VISA resource name and error cluster from one frame to the next!)
There are 2 options for your question:
- wait until condition is met: put a while loop around the code in frame 1 and run the while loop as long as the condition is not met (and maybe include an error check as well as a "Break" button for the user)
- don't execute frame 2&3 when condition is not met: split your sequence into 2 parts (frame 0&1 and frame 2&3), put a case structure around the 2nd part
And remember: you can do all this without using sequence structure - all you need is the error cluster to assure a proper execution order
Hi Melikyan,
attached a slightly reworked vi
Using a subvi for the DAQ part could greatly clean up your code, as it seems you do the same kind of DAQ 3 times...
attached a slightly reworked vi
Using a subvi for the DAQ part could greatly clean up your code, as it seems you do the same kind of DAQ 3 times...
