YavannaKementari

Just so everyone is aware of what the conclusion of this was, and thank you everyone for your help here. After lots of discussion with our NI rep and R&D, it was determined that R&D purposefully did NOT implement any VISA capabilities for the NI PXIe-4080 DMM, even the ability to enumerate the device. They recommended these two things, neither of which are good options for our architecture or requirements: Use NI's proprietary System Config API to dynamically find the PXIe-4080 DMM. I don't want to transfer my entire framework to this proprietary approach (nor do I believe it would cover all the bases VISA Find does). That's what a standard like VISA is for, which any PXI device should support (at least VISA enumeration/find). Create an INI/INF file using the VISA Wizard (https://www.ni.com/docs/en-US/bundle/ni-visa/page/ni-visa/usingddwtoprogrampxipcidevice.html), however I don't have access to a Certificate Authority (CA) to make that installable on Win10, nor can I even install the Windows Driver Kit (WDK) on my machine due to IT Security restrictions without particularly difficult approval. NI R&D refused to do the (relatively small) work to create this set of files to fix this oversight. So at the end of the day, this PXIe device is not VISA capable at all, and they designed it that way. Our project is moving to swap what PXIe-4080 cards we already have to PXI-4070s (which do support VISA enumeration/find/etc.), and future PXI DMM purchases for our setups will likely be Keysight M918xA's, assuming they play nice with NI-VISA on an NI PXI chassis. I wanted to let folks know that this model isn't fully compliant to the PXI standard (although they tried to claim that they meet the letter of the requirements in a particularly lawyerly way, but certainly not the way any NI customer would read it), and I'm a bit concerned this may be the case with future cards - be aware with NI PXI devices that they might not support VISA anymore.

Shaun, thank you for that app note - it will be more good ammo for me for my discussion with R&D today. I'm also going to be referring them to the PXI standard, particularly PXI-2 Software Specification Rev. 2.6, Section 3.2 where it specifies support for VISA for PXI modules. (NI is a "Sponsor Member" of the PXI Systems Alliance) We did just try manually adding a VISA Alias to the visaconf.ini file. It worked for the PXIe-4353 card (which already works and has a VISA Properties tab in MAX), but it did not work for the PXIe-4080 DMM card, which does not have a VISA Properties tab in MAX. Here's what we added to the INI file: [ALIASES] NumAliases=2 Alias0="'Jimmy','PXI21::0::INSTR'" Alias1="'Jimmy1','PXI19::0::INSTR'"

NI Support is still firm with me that "they are no long using VISA to enumerate these devices" (their words). That's pretty concerning that PXI cards made by NI, to a standard they're supportive of (PXI), doesn't comply with VISA at all. I have a meeting with them tomorrow...

All PCI-to-PCI Bridges (there are several on the current PC setup) are working an enabled. Again, I can use the DMM cards just fine via their NI-DMM softpanel or the IVI niDMM type session, just not VISA itself. As you can see from my second post, there is no VISA properties tab for the DMM PXIe-4080 to even set an alias manually, unless you know of a different way of setting one up?

I just noticed you had asked this question as well Shaun. Thanks for your quick response. Yes, our PC is interfacing with a PXIe-1073 Chassis using a PCIe-8361 MXI card via an MXI x1 cable (the little DSUB one). The PXIe-1073 has the "baked in" MXI interface, since we always plan on these PXI chassis being remotely connected to a Windows PC.

I have read that manual, yes. We have also already tried re-installing NI-DMM, and tried my chassis connected to two (very different) PCs with no change in results. I need to clarify about what I meant by "once I configure NI-VISA in MAX" the "PXIe-4080 does not" show up. Both the 4071 and 4080 show up in MAX, but only the 4071 is found by VISA. NI-MAX (or the NI-DMM driver) doesn't seem to assign a Resource/Alias for the PXIe-4080. That's the issue. I can use the NI-DMM softpanel on all of the DMM models fine, and select all of the DMM models using the "DMM IVI I/O" control, but I CANNOT find JUST the 408x model with NI-VISA. I've attached a few more screenshots showing what MAX looks like on my setup with the PXIe-4080, and an older setup with a PXI-4065 DMM (which is found with VISA just fine). Hopefully that clarifies.

I'm using VISA Find Resource to determine what's on my system at the startup of my software. I've been successful using it for just about everything we have in the lab that isn't Ethernet, including recently with some PXI devices (we hadn't started using PXI systems in our lab specifically until just a few months ago with my current project). I have a Pickering Switch PXI card, an NI PXIe-4353 (Thermocouples card) and NI PXIe-4080 (DMM). The first two show up fine using the VISA Find Resource (with "?*INSTR" as the expression), once I configure NI-VISA in MAX to "Show all devices accessible to VISA" under "PXI/PCI Interfaces". But the PXIe-4080 does not. I had loaned a PXI-4071 DMM (an older NI model), and that one shows up fine. When we contacted NI support, they were initially confused, as if using VISA Find Resources for PXI devices was super weird or unheard of. Then they tried to claim that since the PXI 408x is completely a different product than the 407x under the hood, it cannot support VISA. We're not trying to take measurements over VISA, just find it, and get some interface information about it (we then plan on using the NI-DMM IVI). I've included a snapshot of a conglomeration of the functionality that we use to find, get information on, and then convert the VISA reference to the NI-DMM IVI ref specifically. Again, all this worked with the NI PXI-4071 DMM, but I have two NI PXIe-4080 DMMs now that both will not even show up in VISA in MAX. Has anyone else had this issue, or issues like this? It's totally reasonable to use VISA Find Resource for PXI devices, right?

Most of our company (if they're using any standard at all) for LabVIEW utilize templates quite similar to DQMH, that was started over a decade ago and refined/upgraded through the years. Of course, unlike the DQMH we don't have the level of documentation, scripting, and unit testing that the DQMH comes with... I did write a few examples though! 😏

Also going, ready as always to discuss and learn!

Well shoot. As soon as I posted that thought crossed my mind as well. Seems Firefox was causing some weird behavior. With Chrome it downloads fine!

Is there a way to download the video files? When I click on most of them, it says "Download", but then it starts streaming.

Thank you again Mark! Even though I attended this year, I still had a hard time choosing what to attend, there's almost always more sessions than there is time.

Thank you Mark! Very helpful for those of us unable to attend!

Agreed John Lokanis that all the good sessions seem to be in parallel, more so than last year. I have slots that I don't have interest really at all, and other slots with 3+ of interest...

Hey Mark - I worked with you a bit last year, as I recorded a few sessions as well. While I did manage to record a few, it turns out the "1080p" camera I was using wasn't the best... so this year I'll probably forgo trying to record sessions. I did find your recording very helpful to remember what was discussed, enabling me to better pass along the information to others at my company and beyond. Since you're taking requests... TS3285 - Creating Highly Innovative User Interfaces with LabVIEW TS3017 - LabVIEW Champions Live: From Specification to Design (since this one is mostly discussion, I thought it would benefit greatly to record, if allowed) TS4242 - Tips and Tricks for Highly Productive Programming in LabVIEW (The recording last year was really helpful due to his "show and tell" approach) TS4318 - LabVIEW OOP: Computer Science for the G Programmer TS3427 - Implementing Gang of Four Design Patterns in LabVIEW I also second crossrulz and Yair's suggestions. Thank you again for doing this!

Hi Tim_S, I have looked at that NI Community post. I don't think it answers the question about how, or if I can, get the paths to lvclasses inside an lvlib that is outside a built EXE. Is it possible? If so, how?

Hello LAVA! Long time lurker, first time poster. I had posted this question on the NI LabVIEW forum, but I would like to hear from you all as well. I have an array of lvclasses inside an lvlib, as shown in the attachments below. I'm looking to get the reference (path) to the individual lvclass I need dynamically, at run time. This lvlib is not inside the EXE. The goal is to be able to modifiy or add classes to this lvlib without having to change the rest of my code, or rebuild the EXE. Particularly, the code snippet that loads the lvclass will be from a built EXE. How do I dynamically call these lvclasses inside that lvlib?