From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

NIMAX/Labview IVI.NET Issue

Solved!
Go to solution

I bought a rohde&schwarz NGE103B Power supply and want to control it via IVI/Labview. Rohde&Schwarz offers a IVI.NET driver (RsHmc804x-ivi.net-x64-1_5_1_0.msi). After installation MAX lists the instrument driver module (see MAX1).

 

In MAX I added a IVI Logical name and a driver session which points to the instrument driver module. In Labview the logical name doesn't appear in the control when the class is set to "IviDCPwr". When no ivi class is selected the logical name appears. The reason for this is that there are no entries in the MAX for Published APIs. When I add a API for "IviDCPwr" (Version 1.0, IVI.NET) the logical name in labview appears when the class ist set to "IviDCPwr".

 

But when I try to initialize the device (see Labview1) I get a labview error:

"Error -1074134949 occurred at IviDCPwr Initialize With Options.vi

Possible reason(s):

Primary Error: (Hex 0xBFFA005B) File not found."

 

I'm using Labview 2017 and IVI Compliance Package 17.0.

 

Does labview support the use of IVI.NET drivers? Did I miss something?

 

0 Kudos
Message 1 of 10
(4,627 Views)
Solution
Accepted by topic author refi1

Hi ReinholdFink,

 

R&S IVI drivers are of .NET type. LabVIEW only works with IVI-C drivers. But.... there is a way... 🙂

You need to do 2 things:

- Install IVI.NET adapters from NI: http://www.ni.com/download/ivi.net-adapters-1.0/6239/en/

- Copy the attached manifest file (unpacked) to the folder where your LabVIEW.exe is, usually:

"c:\Program Files\National Instruments\LabVIEW 2017"

The manifest file tells LabVIEW to use the .NET assemblies built with the .NET framework 4.0 - all the R&S IVI.NET drivers are built with the .NET framework 4.0

 

Afterwards you can use our IVI.NET drivers in LV

 

Cheers

Message 2 of 10
(4,601 Views)

Hi MM_RohdeSchwarz,

 

thank you very much for the help. I can now communicate with the device over the ivi driver but now I have a new problem. The returned measure values are scaled wrong. When I have 11V as output voltage the device returns a measurement of 11e+6V the same happens for the current (100mA -> 100e+3A (measured)).

 

I think the problem is the decimal point but I can't change it because I only have access to the double value which is returend from the ivi VI.

0 Kudos
Message 3 of 10
(4,573 Views)

Hi

You can change the default in LabVIEW by setting use localized decimal point to False.

In options localized decimal point

greetings from the Netherlands
0 Kudos
Message 4 of 10
(4,568 Views)

Hi

I tried the localize decimal point option but unfortunately it didn't change the result.

0 Kudos
Message 5 of 10
(4,565 Views)

Did you see the * at the end of the text in the options.

This means that you have to restart LabVIEW before it is recognized....

greetings from the Netherlands
0 Kudos
Message 6 of 10
(4,562 Views)

Hi Albert Geven,

yes I restarted LabVIEW after enabling and disabling the option. I think the IVI DLL which returns the value is not effected by this option.

But thank you for your effort.

0 Kudos
Message 7 of 10
(4,544 Views)

I solved the problem by changing the windows 10 system decimal separator.

0 Kudos
Message 8 of 10
(4,541 Views)

Hi ReinholdFink,

 

glad to be of help. Regarding the decimal point - setting of the LabVIEW decimal point has no effect, since the value already comes as double from the driver itself. We will fix the driver to work correctly independently from the Windows regional settings. The fix comes out in the next 2-3 weeks.

 

 

Message 9 of 10
(4,533 Views)
0 Kudos
Message 10 of 10
(4,393 Views)