R&S ZNB 20 VNA Runtime error

[michele.santucci]

I'm experiencing a very strange behaviour with the instrument in subject.

I'm using LabView 2013 32bit.

I have installed the VNA LabView Driver (provided by R&S, version 2.20.1).

I'm connecting such device trough GPIB bus.

I can access VNA trough Keysight Connection Expert and niMAX.

Running the VI application in LabView everything works fine and the following VI specifically complete without any issue:

If I build an executable and run it; it just stops after VISA initialization with the following error:

The VNA resource string is the same provided when running it trough Dev. Env. 

The same error occours if the executable is installed and run into a PC without Dev. Env.

Best regards,

 Michele Santucci

[michele.santucci]

BTW the reported missing vi : rsvna_empty_WriteCallback.vi is correctly installed into:

C:\Program Files (x86)\National Instruments\LabVIEW 2013\instr.lib\Rohde&Schwarz Vector Network Analyzer\Private\callbacks

[GerdW]

Hi Michele,

---

@michele.santucci wrote:

BTW the reported missing vi : rsvna_empty_WriteCallback.vi is correctly installed into:

---

Is that VI also correctly included in the executable?

Where is this subVI loaded/called? Is is called dynamically by filepath?

[michele.santucci]

---

@GerdW  ha scritto:

Hi Michele,

---

@michele.santucci wrote:

BTW the reported missing vi : rsvna_empty_WriteCallback.vi is correctly installed into:

---

Is that VI also correctly included in the executable?

Where is this subVI loaded/called? Is is called dynamically by filepath?

---

Hi GerdW,

as reported in the message error it should be called dynamically I still haven't checked it but I got your point.. I tought every callable VIs was also automatically included into the executable by the application builder but in such a case of course none can predict which of the VIs can be called at runtime.

Anyway I fixed replacing the R&S Intialize with LabView VISA Open so I can mitigate this specific issue .

Searching inside my application I found  several calls to Open VI reference ALL of them are located into R&S VNA driver .... 

The more general point anwyay is open and bleeding... there's a way to check for such potential issues into code using third party API (like these R&S LV driver)? I mean something smarter than looking for other Open VI reference calls.

Best regards,

 Mike

[aeastet]

You will need to include this VI as part of your build. If you do not include the VI it will not know where to find the VI when the exe is started.

[MM_RohdeSchwarz · Accepted solution]

Hi Michele,

here's the R&S employee and the owner of the driver.

The driver you are using is more than 10 years old. At that time we still used dynamically called VIs. Later on we stopped that exactly because of the problems the customers were having building their executables.

What you need to do in your Application Builder spec, is described in the 1MA228 - 10 Tips & Tricks on how to use Rohde & Schwarz® LabVIEW drivers. Tip Nr. 10.

In short: Open your Project Build Specification and add the callbacks folder to the Always Included list:

Cheers,

Milo

[michele.santucci]

That's the perfect fix and also a precious lesson learned thnx..

BTW I needed to include also a lot more of R&S VIs but then it worked flaswlessly.