LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Use 89600B VSA .NET API in LabView

Try the .\Interfaces3.5 directory instead of .\Interfaces

0 Kudos
Message 11 of 22
(1,995 Views)

Thank you LabVIEWFL,

 

I will try to rewrite the existing codes (use COM API ) to new codes using .NET API.

 

Phong

0 Kudos
Message 12 of 22
(1,980 Views)

Hi LabVIEWFL and everybody,

 

When I put the property node on Block diagram and select class---->.NET----->Agilent.SA.Vsa.Interfaces.dll,  I'm seeing the message:

 

"System.BadImageFormatException: Could not load file or assembly 'C:\Program Files\Agilent\89600 Software 19.0\89600 VSA Software\Interfaces\Agilent.SA.Vsa.Interfaces.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

<append><b>System.BadImageFormatException</b>.

 

Have you seen this problem before?

 

How to fix it? Does it have something to do with 32 bit or 64 bit CPU PC?

 

Thanks

 

Phong

 

Phong
0 Kudos
Message 13 of 22
(1,951 Views)

Hi LabVIEWFL and everybody,

 

When I put the property node on Block diagram and select class---->.NET----->Agilent.SA.Vsa.Interfaces.dll,​ I'm seeing the message:

 

"System.BadImageFormatException: Could not load file or assembly 'C:\Program Files\Agilent\89600 Software 19.0\89600 VSA Software\Interfaces\Agilent.SA.Vsa.Interfaces.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

<append><b>System.BadImageFormatException</b>.

 

Have you seen this problem before?

 

How to fix it? Does it have something to do with 32 bit or 64 bit CPU PC?

 

Thanks

 

Phong

 

Phong
Phong
0 Kudos
Message 14 of 22
(1,938 Views)

Hi Cole_R,

 

I have an issue with .NET CLR runtime version forward compatible.

 

   I'm using Labview .NET API to call components from 89600 VSA software application.

 

.NET assemblies from VSA software application have newer CLR runtime version.

 

Labview is compiled and loaded with an older .NET CLR runtime version

 

====>This won't let me to load the VSA assemblies to Labview based on below message:

 

"System.BadImageFormatException: Could not load file or assembly 'C:\Program Files\Agilent\89600 Software 19.0\89600 VSA Software\Interfaces\Agilent.SA.Vsa.Interfaces.dll' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

<append><b>System.BadImageFormatException</b>.

 

 

How do I fix this?

 

How can I check which .NET CLR runtime version Labview is compiled and loaded on my PC.

 

 

Thanks

 

Phong

 

Phong
0 Kudos
Message 15 of 22
(1,923 Views)

Hi Phong!

 

For checking the .NET version in your computer, you can follow the this link from Microsoft.

 

WenR

0 Kudos
Message 16 of 22
(1,907 Views)

Thanks WenR.

 

I've got the problem fix. I forced the LabView to use CLR version 4.0 to load 89600 VSA softare .NET 4.0 assemblies to my LabView application instead of LabView default CLR version of 2.0

 

Using the instruction as below:

 

Loading .NET 4.0 Assemblies in LabVIEW

If you want to use .NET 4.0 assemblies in LabVIEW, you must explicitly configure LabVIEW to use the Common Language Runtime (CLR) 4.0. However, consider the following caveats before installing the suggested configuration file:

  • LabVIEW does not support some .NET 4.0 features. Therefore, some .NET 4.0 assemblies might return errors in LabVIEW even if you configure LabVIEW to load them. Refer to the KnowledgeBase at ni.com for a list of unsupported .NET features in LabVIEW.
  • Assemblies that are targeted to earlier versions of the CLR might behave unexpectedly if you configure LabVIEW to load the CLR 4.0.
  • You must always use the CLR 2.0 to build a .NET interop assembly with LabVIEW.

Complete the following steps to force LabVIEW to load .NET 4.0 assemblies.

  1. Install the .NET 4.0 Framework on your development machine.
  2. Open a text editor and create a configuration file that contains the following text:

    <?xml version ="1.0"?>
    <configuration>
    <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0.30319"/>
    </startup>
    </configuration>
  3. Save this new configuration file in the same directory as LabVIEW.exe. Name the file LabVIEW.exe.config.
  4. Relaunch LabVIEW.



Thanks

 

Phong

Phong
0 Kudos
Message 17 of 22
(1,883 Views)

Hi LabVIEWFL,

 

Have you tried digital demodulation in 89600 VSA .NET LABVIEW property?

 

How do reference the assembly? Look like the digital demodulation is in different assembly

 

(Agilent.SA.Vsa.DigitalDemod.Interfaces Assembly) than the normal operation (Agilent.SA.Vsa.Interfaces Assembly)

 

 

Do you have any example?

 

 

Thanks

 

Phong

Phong
0 Kudos
Message 18 of 22
(1,847 Views)

Hi Guys,

 

How do I configure 89600B VSA software to digital demodulation using .NET API Labview property?
 
How do you change the measurement type from MeasSetup----->Measurement Type: Vector to Measurement Type: General Purpose-->Digital Demod using .NET API Labview property?
 
 
Thanks
 
Phong
Phong
0 Kudos
Message 19 of 22
(1,836 Views)

Hi Andy,

 

How do I configure 89600B VSA software to digital demodulation using .NET API Labview property?
 
How do you change the measurement type from MeasSetup----->Measurement Type: Vector to Measurement Type: General Purpose-->Digital Demod using .NET API Labview property?
 
 
Thanks
 
Phong
 
Phong
0 Kudos
Message 20 of 22
(1,816 Views)