LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Analog Trigger cDaQ Error

Hi,

 

This may be a a rookie mistake but I'm, hoping to get a definite answer/solution here since I could not find one....

 

I am using a cDAQ-9174 with a NI9221 analog input module.

 

I am trying to set up an analog trigger following the tutorial here:

https://www.ni.com/en/support/documentation/supplemental/21/ni-daqmx-data-acquisition-triggering-tec...

 

As it was not clear to me what should be the string to use for 'trigger source', copied the physical channel name I want to use as trigger (here being cDAQ1Mod2/ai0) and create a VI as in the tutorial:

Analog_Start_Triggering_in_LabVIEW 

There is no errors (no broken arrow that is) but when I run it I get the following error:

Capture.PNG

Possible reason(s):

 

An attempt has been made to use an invalid analog trigger source.

 

Ensure that the trigger source you specify matches the name of the virtual channel in the task or matches the name of a non-scannable terminal that the device can use as an analog trigger source.

 

Property: Start.AnlgEdge.Src

Corresponding Value: cDAQ1Mod2/ai0

 

Valid Choices: none

 

Device: cDAQ1

 

Task Name: _unnamedTask<89>

 

If anyone could help me understand why I'm getting this error and the possible solutions to resolve it, it would be much appreciated! 🙂

0 Kudos
Message 1 of 4
(2,660 Views)

Hi sherzaad,

 

Have you checked that the module you are using actually supports analog triggering?  The DAQmx error messages are usually pretty good at telling you the valid parameters if you've got something wrong.  In this case, the "Valid Choices: none" message suggests analog triggering is not supported.

 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P6WTSA0&OpenDocument=&l=en-GB

 

PsyenceFact

Message 2 of 4
(2,635 Views)

you're probably right.

 

suspected that much as well but wanted to be sure! 😉

0 Kudos
Message 3 of 4
(2,625 Views)

@sherzaad wrote:

you're probably right.

 

suspected that much as well but wanted to be sure! 😉


You were right.

 

He was right

 

The manual was right.

 

The error was right

 

Are you sure yet?


"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 4
(2,611 Views)