how to select from a list of USB-8451 modules found

[KKW]

This knowledge base article shows how to find a list of USB-8451 modules attached.

http://digital.ni.com/public.nsf/allkb/D6A79640103C4E0E8625714D006A1E1E

However, how do you make the list available for selection by the user for use by "NI-845x Device Property Node"?

[PhillipBrooks]

You could add a menu ring control to your UI, then create a property node for it and wire the array of strings output from the example to the Strings[] property of the ring.

[KKW]

Thanks for the reply. But how do I convert the selection into a device reference for use by the NI-845x property node. I've attached the VI showing where my problem/question is.

[PhillipBrooks]

This device is interesting. I assumed it was a DAQmx compatible device, but I have questions now.

I installed the driver, and the 845X functions are installed under VISA I/O, not DAQmx. Since it's not DAQmx, you can't create a simulated device, or use the DIO portion as you would on a USB-6009.

If you query the DAQmx System DevNames, does the 8451 show up in the list? See attached VI.



Message Edited by Phillip Brooks on 03-18-2008 02:29 PM

[chris_amadasun]

Hello please take a look at my attached screenshot.

You can locate the 8451 property node by right clicking on your block diagram and selecting Instrument I/O > NI 845x

Let us know if this helps.

[PhillipBrooks]

I think this answers KKW's question. You simply pass the VISA query results to the Strings[] property of a menu ring.

If the VISA name is too confusing for the operator, the Serial Number could be extracted and used to "name" the device in the UI. The user would use the menu ring to select the device by serial number, and the code would use the menu ring index to select the full VISA name from the array.

The 8451 property node will not accept a string input, so you must typcast the string using an I/O constant as the prototype before setting the property node.

See if this example helps...

[KKW]

Phillip, thanks for you help.

Took you idea but changed the search mode to alias so that the device alias names would be returned rather than the cryptic numbers.