LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error-200077 DAQmx start trigger analog window

I just wanted to setup the DAQmx Start Trigger.vi using the analog window, but I get Error-200077.

 

Why do I get this error?

 

(When you run the vi attachec, you must use controls to selectd physical channels.) 

 

Fred
*Kudos are appreciated.*
0 Kudos
Message 1 of 6
(3,696 Views)
What exactly are you trying to do over here? And, what hardware are you using? I would recommend having a look at the shipped DAQmx examples provide in LabVIEW (Help -> Find Examples). Also, you need to use the DAQmx Clear Task.vi after you are done with executing the task.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 2 of 6
(3,690 Views)

For the vi attached previously, I was using a virtual DAQ device.  I created the device using MAX.  What I really want to do is use an analog input line like a digital input line (i.e. if the analog input is above 2.2V then set a variable to 1, and if the analog input is less than 0.8V then set the variable to 0.)

Fred
*Kudos are appreciated.*
0 Kudos
Message 3 of 6
(3,682 Views)

You will need to software time the acquisition since I don't see the benefit of hardware timing it. Attached is a solution (replace the boolean with the number constant).

 

daq.png

Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
Message 4 of 6
(3,676 Views)

Thanks, that will work for the problem I mentioned.  I should have mentioned that time is critical in my case.  I was trying to use the "analog window" of the DAQmx Start Trigger.vi b/c I was hoping it would be fast.

 

This is just a portion of the code for the project.  This task we've been discussing needs to be done (along w/ some other tasks) in a timed loop executing at 1kHz.  I will try to see what results I can get by modifying the code.

 

Is there a reason you chose to include a 50ms wait?

Fred
*Kudos are appreciated.*
0 Kudos
Message 5 of 6
(3,672 Views)

Well, but why would you use the start trigger if you wanted to acquire the data continuously from the beginning. That's something I didn't understand.

 

The application should be able to work at 1Khz since you are using the DAQmx API to acquire only a single point.

 

No, there is no reason for the 50ms wait. You can choose whatever wait you want.

Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
0 Kudos
Message 6 of 6
(3,666 Views)