Edit IVI Power Supply Missing IviDcPwr_Init function

[ChevyVolt1]

Hello all,

I am working with a project that uses TestStand 2017.  I'm running into problems configuring an IVI power supply (Agilent/Keysight N6952A. Got the IVI driver off NI.com at this link: http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=22530). 

I installed that driver and set it up via NI MAX.  However, when I try to configure (and init) this particular power supply in TestStand, I run into a "Session Manager: Could not find function 'IviDcpwr_init' in DLL (or external module) 'IviDcpwr.dll'. (-31619)" pop up.  See attached png.

I get the exact same message with another Agilent power supply -- the N87xx series (driver also obtained from NI.com).  I don't get this problem with a third Agilent Power supply, the N57xx series. 

The only difference between the N57xx (that worked) and N87xx/N69xx (which failed) drivers is that the N57xx series is using IviDcPwr 2.0.  N87xx and N69xx are using IviDcPwr 3.0. 

I already have the IVI Compliance Package 19.0 installed (this occurred with both ICP 18.0 and ICP 19.0).

What am I missing here?

Thanks

PS: Steps to reproduce:

1. Open up TestStand

2. Dragdrop Power Supply from the IVI Step Types folder to any of the sections (issue occurs anywhere)

3. Click on it, select Power Supply tab if not selected, and click on Edit IVI Power Supply

4. Select the logical name of the power supply set up via NI MAX, then Click on Validate

5. Click on Init and you'll get that pop up. 

All drivers were obtained through NI's 3rd party instrument drivers search/pages. 

[sarahmo]

Hi,

Check out this article and double check the file path of your dll.

Error -31619

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Ni3SAE&l=en-US

[ChevyVolt1]

Thank you for the link.  That was one of the first things I checked.  Here's what it looks like (after I made sure to save), see Capture.PNG.

Same problem.  I went ahead and converted the .fp to a C# wrapper and am using that for now since I'm under a deadline.  It appears that the IVI driver obfuscates a lot of the calls that we need.