I cannot build an application, in C# VisualStudio environment .NET 4.0, that includes two references Agilent.SignalStudio.N7621.DLL and Agilent.SignalStudio.N7611.DLL, together for x64 Platform Target .
Unfortunately, at the moment KEYSIGHT doesn't provide an x64 N7611.DLL and N7621.DLL doesn't run on x86 Platform Target
Please, there is someone might suggest me how can I do?
Thanks
Marica
Thanks Pete,
Sorry for late of my answer.
I have already got N7621.dll for x32 and x64.
But, I need N7611B.ddl for x64.
Hi Marica,
I don't believe there is a 64 bit version of the N7611B application available. I sent a message to the development team to make sure.
Pete
Hi Marica,
The Development Team does not have a 64 bit version of the N7611B Application. They were trying to understand your use case. I'm not sure but I think you are accessing the 64 bit version of N7621B Multitone Distortion from a 64 bit version of LabVIEW and need the 64 bit version of N7611B to make it all work together. Did the 32 bit versions of N7621B and N7611B not work with the 64 bit version of LabVIEW?
Let me know if using the 32 bit versions of N7611B and N7621B work or if you really need a 64 bit version of the N7611B.
Pete
Hi Pete,
Thanks for your help and collaboration.
I will try to explain better the question.
First of all, I think that the problem is, during the C# development, in using of CLR 4.0 (.NET 4.5), instead CLR 2.0 (.NET 3.5) as required by Agilent.SignalStudio.N7611.dll.
Secondly, if it used x86 platform target and CLR 4.0, an exception happens when my application, in runtime, calls the Agilent.SignalStudio.N7611.BroadcastRadioProject download function. The $exception reads like this: {"Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information."}
Thirdly, impossible to use x64 platform target with Agilent.SignalStudio.N7611, independently of CLR 2.0 or CLR 4.0 runtime, because of the problem arises before the runtime, during the application building phase when error reads like this:
• “Referenced assembly 'Agilent.SignalStudio.N7611, Version=3.5.0.1, Culture=neutral, PublicKeyToken=null' targets a different processor”.
• A specific warning : “There was a mismatch between the processor architecture of the project being built "AMD64" and the processor architecture of the reference "Agilent.SignalStudio.N7611", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.”
So, at the moment I tried out and successfully developed a single stand-alone service application for Broadcast Radio in .NET 3.5, and unfortunately the N7611.Generate and N7611.Download executed functions (ex. FM_RDS 40KB WAV FILE about 200sec) are too slow (so Keysight BroadCast Application too) and impracticable for our operational purposes.
Finally, do you know if there are available SCPI Commands for the N7611 and N7621 features.
Thanks you very much.
Marica
Hi Marica,
I searched the N7621B help for LabVIEW and got this discussion about loading mixed mode assemblies. Not sure if this will help or not. There are no SCPI commands for N7611B or N7621B.
Pete
The .NET Framework 4.x allows you to load pure managed assemblies built in any version of the .NET Framework. However, for some Signal Studio applications, API usage involves assemblies that are not pure .NET CLR. In these cases, you must configure your program (e.g. User_App.exe) to load .NET mixed-mode assemblies using the following steps:
Open a text editor.
Copy the following text into the text editor:
<?xml version ="1.0" encoding="utf-8" ?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
</configuration>
Save this new configuration file in the same directory as User_App.exe. Name the file User_App.exe.config.
Re-launch User_App.exe.
The Microsoft.NET home page.
Developing Microsoft.NET Skills.
"Migrating Native Code to the .NET CLR," by Don Box.
Troelsen, Andrew. C# and the .NET Platform. New York: Apress, 2001.
Hi Pete,
Thank you very much.
I've already used your suggestion without success.
See you soon.
Marica
Hi Marica,
After downloading waveforms to the Arb, they can be copied to the internal hard drive. This way you would not have to repeatedly download the waveform, just recall them from the hard drive. Would this help mitigate the 200 s download time? Or will you not use the N7611B software. If you can accept the 200s download time, the R&D team thinks they can make a 64 bit version of the N7611B. If you cannot live with the 200 s download time there really isn't much point in doing a 64 bit version.
Let me know what you think.
Pete
Hi Pete,
after coping waveforms to the BBG, the process is very fast by only two SCPI Commands: ":RADIO:ARB:WAVEFORM <mywfm.wfm>" and "RADIO:ARB:STATE ON".
Furthermore, I used N7611C.dll and resolved the CLR 4.0 runtime problem.
So, I'm really happy.
See you
Marica
Hi Marica,
Thanks for letting us know that you got this all figured out.
You may want to copy your waveforms to the non-volatile memory (Hard Drive in the instrument) This way they will survive a power cycle. The BBG waveform memory is not preserved during a power cycle.
Pete
Hi Marica,
See if this will work for you.
https://www.dropbox.com/s/xqp9k1psflo9epw/N7621_Setup32Win7_3.1.20.0.exe?dl=0
Pete