programmatically get PXI-665x information

[quanqing]

Hi, I've seen that the information of DAQmx devices and modular devices can be obtained programmatically through property node or calling appropriate VIs, but how can I get the information, say, simply the resource name, of a PXI-665x board by coding? Thank you!

[Chris_R.]

Hi quanqing,

What type of information are you looking for?  Have you browsed the NI-Sync property node options?  You can find this by browsing the LabVIEW function palette to Measurement I/O>>NI-Sync.  This will provide some information for the PXI-665x boards programatically.  If this isn't what you need, please repost with the properties you are looking for.

Message Edited by Chris_R. on 11-14-2006 01:11 PM

[quanqing]

Thanks Chris!

What I would like to do is to detect which 667x cards exist in the PXI chassis and which slot they are plugged in. The niSync nodes need a resource name in the first place which I have to manually type in. Actually, I've searched around and come to the idea of using VISA resource finder to generate a list of VISA devices and check whether the card is a 667x model, it works great. I'm wondering if this method is valid for other types of PXI cards? Any limitations? Thank you very much!

[Chris_R.]

Hi quanqing,

As long as the device is a valid resource on your system and you are able to find it using the VISA Find Resource function, then you should be able to change any property, that the card allows, in that manner.  The limitations depend on the specific hardware and the driver the hardware uses.  What you are doing seems like a simply property change/request, so I suspect that you won't have any trouble.  If you do, or have any other questions, just let me know and I will find out what is going on.

Best of luck!!

[wired]

Unfortunately the developers of NI-Sync made a GLARING omission by not allowing us to get the DAQmx device name for ANY NI-Sync controlled device.  So, ANY NI-Sync VI requiring a board-specific terminal name (e.g. /PXI1Slot2/PXI_Trig0), such as  NiSync Connect Trigger Terminals , CANNOT be used with a programmatically determined terminal name, because the NI-SYNC boards do NOT show up as DAQmx devices when accessing the DAQmx System.DevNames property.  Ironically, if you create a constant from the terminal node, what shows up?... the DAQmx terminal names.  This has seriously hampered my efforts to create a program that does not require hard-coded device names.  I believe the NI-Sync products are the only ones that have this problem.  The current workaround (which I find unacceptable for the long term) is to programmatically generate an HTML MAX report and parse it to get the DAQmx information. NI provided me with a VI to do this, and I appreciate their efforts, but this is clearly not an acceptable alternative.

I SINCERELY hope this becomes a CAR and will be addressed SOON. Seeing a DAQmx device name in MAX, yet not being able to read it with the DAQmx property node, is rather frustrating (as well as having NI-Sync VIs that REQUIRE a DAQmx terminal name).

[Chris G in AE]

Howdy wired,

Thank you so much for posting this info. I will definitely be checking into the problem to see if I can reproduce it on our end.  If I can, I will file a Corrective Action Request (CAR for those interested) immediately, and I will also update on the forum when it is fixed.  I know this type of situation can be frutsturating and we will deal with it as quickly as possible.  Until then, thank you for posting the work around, even if it isn't acceptable for a longer term solution.  I will keep the forum updated with what progress has been made.  Thanks again.

[wired]

Hi Chris,

Jordan Dolman worked on getting me the workaround under SR#7201215, and I have made the product manager of the 6682 aware of it as well.  I'd just like to know if and when a CAR is issued so I can track it.

Regards,

Kevin

[Chris G in AE]

Howdy Kevin,

 I spoke with Jordan this morning and the Product Support Engineer this afternoon and I believe we have cleared up the issue.  Since NI-Sync and DAQmx are technically different drivers (even though the organizational structure in MAX would suggest otherwise), the property node for discovering the DAQmx Aliases will not work with NI-Sync devices.  However, because NI-Sync uses the VISA API, we can use the "VISA Find Resources" VI along with the "Get Model Names" VISA Property Node and get a list of installed NI-Sync hardware that way.  I have developed an example program that should clear up how to do this.  Please post back if you have any further questions about this solution and I'll be more than happy to clarify as needed.  Thanks for brining this to our attention; I hope it will work for you.  

[wired]

Chris - I don't see how knowing the model name will help me.  You can't use the model name as an input to the NI-SYNC VIs.  You need a fully qualified DAQmx name, for instance to do a Connect Clock Terminals function.

[Chris G in AE]

Kevin,

I've taken the VI that I posted yesterday and modified it to programmatically initialize an niSync session.  Basically, the VISA Resource can be used to open a session to NI-Sync, but the trick is finding which VISA Resource is linked to the 6682.  Using a simple search string function, we can determine what model name (NI-PXI-6682) contains the string 6682, and feed the associated session into the niSync Initialize VI.  From there, you can output the niSync session to your Connect Clock Terminals function.  Let me know if you've got any further questions, and have a great day!