ni.com is currently experiencing unexpected issues.
Some services may be unavailable at this time.
09-18-2008 12:34 PM
09-18-2008 01:37 PM
09-18-2008 02:36 PM - edited 09-18-2008 02:37 PM
Also, be careful using the delay.
You only want to delay the output , you do not want a delay for all of your code,
or the program will run incorrectly
09-18-2008 02:47 PM
Thankyou for the help. Although I have explored this solution. It didn't seem to work properly when I placed it in the program. I have attached a screen shot of how I have incorporated the delay. It gives me an error code in the start.vi that the start.delay is not applicable.
09-18-2008 04:25 PM
09-18-2008 07:53 PM
09-18-2008 08:15 PM
09-18-2008 09:23 PM
09-18-2008 09:49 PM - edited 09-18-2008 09:49 PM
You don't stick a time delay function on a task/channel. You stick a DAQmx trigger delay property on an output task that is set for external triggering. A time delay function just goes between your code where you are detecting the correct logic level and where you have your DAQmx Write. I would recomend you use the error clusters to enforce data flow.
Functions such as the Time Delay are pretty basic LabVIEW. Have you had any training or tried the on-line tutorials?