Labview failing to initialize an EMX-2500 through using IVI drivers

[JWH2]

Hello all, I am running into a frustrating issue. I have been tasked with updating some old software in my lab. The people who designed it no longer work here, and I know enough labview to probe and troubleshoot but clearly not the level of the person who made the software. We have the compiled software working on a W10 PC, but when we the OS to Windows 11 the software stopped working. We don't have a single development environment fully working, leaving me to try to patch it up before I can even start troubleshooting the transition to Windows.

I am developing on Windows 10 with Labview 2018 32 bit. We use IVI drivers to connect to an EMX-2500 in a chassis. I am running into an issue specifically when trying to call the .dll. We have other hardware that is able to succesfully initialize, but for some reason the 2500 won't. The VI seems to be a pre-built plug and play driver. Pics below of the block diagram and front panel.

Whenever I run the software, its at this block of code where it fails. I get a BFFA4000 error which in IVI documentation means "An internal error has occurred." I don't expect anyone will know exactly what my problem is, I may not even know what information to provide, but something may help push me in the right direction because I am out of ideas.

 

 

 

[billko]

Analogous to how you create a VISA alias to refer to an instrument's VISA resource name, you must create an IVI Logical Name in NI-MAX and associate that name with the IVI driver session, then use the Logical Name instead of the VISA resource name.

You have to configure the session. That's where you tell it what instrument to use, among other things. You can copy a session if you have more than one of the same instrument - e.g., you have two ABC Scopes. You can copy the session that refers to ABC scope and then specify the second ABS scope in the second session.

[JWH2]

So I have configured the session in Ni Max under IVI Drivers. Chose the hardware and the software. Looks like there was already a session configured for it, so that doesn't seem to be solution. Can you provide a little more detail on how to configure a session? Perhaps I did it wrong

[JWH2]

Actually looking at NI Max and the code, it seems like the sessions are already being configured properly. Though I don't know what the final problem is.

I can ?IDN query the module in NI Max and get a reply properly. The initialize VI I'm running is the VI provided for the EMX-4250 if that matters.