From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-15-2008 04:37 AM
05-15-2008 04:58 AM - edited 05-15-2008 04:59 AM
05-15-2008 07:10 AM - edited 05-15-2008 07:12 AM
Hi Sena,
If you used an Event Structure or a State Machine, you could implement a PAUSE feature quite easily. The reason I would lean towards the Event Structure is that it is easier to implement a solution which is less CPU intensive since it will wait until the Operator selcts RESUME with little loading on the CPU.
The Event Structure would appear inside the While Loop. I would not implement a Case Structure with a loop that does the waiting for you because it is CPU intensive. A State Machine would be my 2nd choice.
RayR
05-15-2008 07:26 AM
05-16-2008 04:11 AM
05-16-2008 07:14 AM
I didn't realize that you were monitoring a DAQ device.
How continuous will you be monitoring the DAQ device? Since it will provide a trigger for the Event Structure, it will be located outside it, probably in a State Machine. Depending on if you continously monitor it or not may affect the architecture.
RayR
05-17-2008 11:49 PM
05-18-2008 03:31 AM
05-19-2008 03:24 AM
05-19-2008 05:50 AM - edited 05-19-2008 05:51 AM
You only need a state machine. State machine is always in a loop.
Select , from the menu File..New..From Template..State Machine
You will give the names "Start", "Pause", "Stop" to the enum
How much simpler than that...
Use the highlite execution to help you understand