Validating a DAQmx terminal after casting from a string

[eaolson]

I need to cast from a string to a DAQmx terminal, and then set that terminal as the source for a external trigger.  I would like to verify that the terminal actually exists and that an error was not made.  I can't find any way of determining if a specified terminal actually exists on a given device.  Even setting a non-existant terminal as the trigger source for a task doesn't seem to throw an error.  Nor can I find a way to get a list of all the available terminals on a given device to see if the specified terminal is in the list.  I'm using LabVIEW 7.1.1.

Any suggestions?

Message Edited by eaolson on 08-03-2006 11:44 AM

[eaolson]

I reposted this in the LabVIEW forum, as it's a software, not a hardware question.

[Jarrod_B.]

Hello eaolson,

I did see your post to the other thread in the LabVIEW forum.  Actually, for future reference, this would be the correct place to post that question to since it has to do with the NI-DAQmx driver, and not so much LabVIEW. 

After reading through your other post, it does look like some strange behavior.  I would be interested to see if it can be reproduced with NI-DAQmx 8.3, the most current version of the driver which just went live today.  If you are interesting in trying, you can download this version of the driver and see if the same thing happens when you run your code.  Let me know the outcome, and if need be, I can submit a corrective action request to R&D.

Best regards,