Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

VI Initialize with OptionsString is missing the Resource Name field when created by the IVI Driver Generator LabView 8.6

Solved!
Go to solution

Hi Justin

 

I took your sugestion and zipped an llb VI package build with LabVIEW version 8.6.

I would like if is possible to get this package translated to LabVIEW version 7.1 and send it back.

I attached the zip package to this email.

 

 

Thanks in advance

 

Sorin Lazarescu

0 Kudos
Message 21 of 33
(2,463 Views)

Hey Sorin,

 

I've re-attached the library after saving it for LV 7.1. Let me know if this doesn't work, thanks!

Justin E
National Instruments R&D
0 Kudos
Message 22 of 33
(2,443 Views)

Hi Justin

 

I tried to open one VI from the LV71 package on another computer that has only LV 71 and I got this message

 

"An error occured loading VI 'jdMAP200_OPM Clear.vi'

LabVIEW load error code 9:

VI version (8.6) is newer than LabVIEW version (7.1)"

 

After I received from you this package I realized that there is more than a pure LLB conversion from 8.6 to 7.1 version.

Our LabVIEW driver that was created trough "LabVIEW Import Generator Tool version 1.2" has not only a LLB package but also install a list of icons and a report html all of them saved automatically in the instr.lib subfolder of the labVIEW 8.6 version.

 

As result of this exercise the LabVIEW Functions Pallette will display all the drivers LLB functions in separate icon that is part of Intrument Driver pallette.

 

So when thre transfer from LabVIEW 8.6 to LabVIEW 7.1 not only the LLB package but the full subfolder jdMAP200_OPM from the National Instrument instr.lib subfolder from LabVIEW 8.6 is totally transfered into LabVIEW 7.1 such that the user in LabVIEW 7.1 could open all these VIs directly from the Instrument Driver Functions Pallette in the same way as in LabVIEW 8.6

 

Lets see if that is possible?

 

Btw when I replaced the converted LLB LV71 into instr.lib subfolder of the LabVIEW 8.6 all icons of the Intrument Driver Functions Pallette became ? qusetion marks and could not be used as before.

So there must be a connection between menu icon files and LLB pacakge for the Function Pallette to show them properly in the Instrument Driver.

 

I zipped the full driver subfolder jdMAP200_OPM now that include not only the LLB package but also all menus icons associated to this LLB.

 

 

Thanks

 

Sorin

0 Kudos
Message 23 of 33
(2,438 Views)

First, those are mnu files, not icons and they are totally irrelevant to converting from one version to another.

 

Second, the VIs in the llb that Justin posted are all in version 7.1. If you are getting that message, it's because you moved the wrong llb to the 7.1 computer.

0 Kudos
Message 24 of 33
(2,431 Views)

Hi Dennis, Justin

 

You are right! I repeated the test on labVIEW 7.1 again on the second computer from the same zip file that Justin sent me and is working the way you said!!!

 

As a bonus I could see  even the VI menu icons inside the Instrument Driver Pallette with one small difference compared with version 8.6.

In labVIEW 7.1 they are all in one place under driver instrument root icon but in version 8.6 they are located in an hierarchy of menus that makes easier to get a specific function.

 

My assumption is that this lack of hierarchy is created by the fact that the menu files that I was talking previously are missing from this conversion.

 

This is not a big problem as all instrument driver VIs could be found inside the Instrument Driver Pallette under LabVIEW 7.1. 

 

Thansk again for your help

 

Sorin

0 Kudos
Message 25 of 33
(2,422 Views)

Hi Justin, Dennis

 

I have a bunch of LLBs that stores LV wrappers to one of our instrument IVI-C drivers build in LabVIEW 8.6 version.

We need to convert this package from LV 8.6 to LV 7.1 as a lot our customers still have LabVIEW versions 7.x.

 

Thanks

 

Sorin

0 Kudos
Message 26 of 33
(2,377 Views)
I can't but you can make it easier for anyone that volunteers to do so many. Use your 8.6 to save them as 8.0. Then, whoever does it only has to do a single conversion to 7.1.
0 Kudos
Message 27 of 33
(2,375 Views)

Hi Dennis

 

I tried in LabVIEW 8.6 to save my top-level VI from an LLB to LabVIEW 8.0 and is not working quite well.

In LV 8.6 I opened the top-level <jdCMR VI Tree.vi> then from <File->Save For Previous Version> selected LabVIEW version 8.0

accept the default destination folder <jdCMR VI Tree Folder> and let it run.  After processing the destination conversion forlder contained

the jdVMR.llb package but from a size of 579kB in LabVIEW 8.6 ended up in LabVIEW 8.0 with a size 1036 kB?

Something must be wrong if the size of the original llb in LV 8.6 almost doubled in LV 8.0? A previous conversion by Justin from 8.6 to 7.1 almost did not change the size of original LLB.

 

From NI zone I read that converting LLB from LabVIEW 8.6 to a lower version is not possible trough conversion of the top-level tree VI as  before but I must  use projects or project libraries that incorporates these LLBs plus other the other related dependencies...

 

Could you shed some light on this issue?

 

Thanks

 

 

Sorin

 

0 Kudos
Message 28 of 33
(2,363 Views)

Hi everybody

 

I saved all my IVI LabVIEW wrappers from LabVIEW 8.6 to version 8.0 zipped them and attach them here.

Is anyone willing to help and convert these LV wrappers from LV 80 to LV 71?

 

Thanks in advance

 

Sorin

0 Kudos
Message 29 of 33
(2,350 Views)

For whoever would like to convert these LLBs, here is a great Developer Zone Example that will do this :

http://sine.ni.com/devzone/cda/epd/p/id/2457

 

Justin E
National Instruments R&D
0 Kudos
Message 30 of 33
(2,336 Views)