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.
02-22-2006 07:05 PM
02-22-2006 07:40 PM
02-22-2006 08:49 PM
@altenbach wrote:
Add an empty timeout case to the event structure and wire a small value to the timeout terminal.(your code has quite a few serious problems, for example you should make sure tha the VISA reference is wired across ALL event cases.).
02-22-2006 09:31 PM
02-22-2006 11:43 PM
@NewMachine wrote:
but like i said i tried the timeout event and it made my vi even worse...when i pressed a button to move the motor "forward continuous" the timeout made the motor stop and start every 100 milliseconds (or whatever constant i wired into the event). its like it sends an interrupt or something. is there any other way i could program the vi to make both things work? thanks!
02-23-2006 01:14 PM
@altenbach wrote:
@NewMachine wrote:
but like i said i tried the timeout event and it made my vi even worse...when i pressed a button to move the motor "forward continuous" the timeout made the motor stop and start every 100 milliseconds (or whatever constant i wired into the event). its like it sends an interrupt or something. is there any other way i could program the vi to make both things work? thanks!
I assume you have tried a 0ms timeout?
02-23-2006 01:22 PM
@felan wrote:
Well I think one way you can work around is by putting the event structure in a loop of it's own. I mean have two parrallel loops running.
---------------------------------------------------------
NI labview 8 tutorials available at www.fafiles.com
---------------------------------------------------------
02-23-2006 06:31 PM
Hello,
If you're communicating with your motor using VISA, you're likely using a serial port or GPIB, so your motors behavior and responsiveness is going to depend on the speed of those buses. As far as not having the event structure hold up other code, multiple loops is the way to go. If you need to have your continous (no event structure) loop communication or trigger events in the event handling loop, you can use User Events.
I hope this helps!
Best Regards,
JLS
11-21-2017 08:41 AM
I am having the same issue. I was following the instructions in the LabView tutorial. In the tutorial it says to put Event structures inside While loops. I did that, but the moment i put it in the while loop, the whole while loop only executes when the Event executes - I am trying to capture data only when a button is pressed, but I need the data to continuously be graphed in the while loop, and only capture it when the button is pressed. What really happens is contrary to instructed and what is expected to happen.
11-21-2017 08:49 AM - edited 11-21-2017 08:51 AM
This thread is very old. Please create a new thread and post your vi.
It's difficult to troubleshoot code on the basis of a description only.