| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| Try this. I suspect you were killing the other thread before the abort command could be sent. eventstructurestop3.vi: http://forums.ni.com/attachments/ni/...ucturestop3.vi |
|
#2
| |||
| |||
| Matt, Your solution doesn't work either. It looks like you wait statement in the one event. The problem is still what I stated in reply #2. (But I see you posted your reply at almost the same time as I posted mine.):smileywink: The attached works.Message Edited by Ravens Fan on 01-08-2008 07:29 PM eventstructurestopMOD.vi: http://forums.ni.com/attachments/ni/...turestopMOD.vi |
|
#3
| |||
| |||
| Ravens answer should get you going. ![]() The issue is dataflow, and it seems you have some general misconceptions. In your original VI, the big loop cannot go to the next iteration until all code in it has finished. Since your timed loop never finishes, your event structure only gets one shot. A good tool to see what is going on is execution highlighting. Try it! What is the purpose of the small sequence frame surrounding the "stop timed loop" function? Again it almost seems you are trying to make sure the loop stops before the event finishes. This is not needed. The event cannot finish until all code in it has finished so the sequence is completely irrelevant codewise. Your timeout case is unused. Still, can you tell us a little bit more about your application? What else is there in your real code? Do you need to stop multiple timed loops? If not, just place the stop button terminal in the timed loop and forget about all the rest. |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.