MAC V2.2 conversion to V3.1 mass compile cant find certain VIs

I have some MAC LabView 2.2 files that I need to convert to Labview 2012. I have started using the conversion tool to go to Version 3.1.
During the mass compiler process it tells me that it cannot find a lot of VIs such as “Open Folder”, “Open Files”, etc.
I am having the same problem as the person in this thread:
http://forums.ni.com/t5/LabVIEW/I-try-to-convert-LAbview-2-2-VI-to-Labview-3-1-for-MAc-using-the/td-...
I tried what Dennis’ suggested by saving files such as “Open File+.VI” from Version 3.1 as just “Open File.VI” but when I select the newly saved file it doesn’t take; it just re-prompts me for the VI again.
So can someone explain further what I need to do to find these VIs? Or get the ones from Version 3.1 to work?
Thanks
T

T,
The problem you run into in converting VIs that old is that some of the functions and VIs used in the older version simply do not have any direct equivalents in the newer versions. You have to go in and reprogram things to get the same functionality with the new VIs.
Do you have an old Mac on which to run the LV 2.2 version? If so, I would spend enough time with that version to document what the program does and then write a new program in LV 2012 with the same capabilities (plus all the new things someone will have decided to add). Make backups and print out all the diagrams. Just in case.
I am currently in the process of rewriting a program which is currently in LV5, LV6, and LV8.6 to LV 2012. This program started out in LV1.2 and was rewritten in 2.2.1 or 3 and then converted to 5 and upgraded a few times. Event though I was the programmer in all the versions, very little of the current version except for some user interface items will be carried forward to the new version.
Lynn

Similar Messages

How do I install gimp on my mac with OSX Mountain lion? It says it cant find X11.

How do I install gimp on my mac with OSX Mountain lion? It says it cant find X11.

Have a look in your Utilities folder - X11 should be there. Launch it and you'll be offered the option to install.

I try to convert LAbview 2.2 VI to Labview 3.1 for MAc using the conversion Kit. Labview 3.1 mass compile cannot find several VI like "open file, open folder, wait(ms), al_config"e.t.c. How can I manage this problem?

It looks like Labview 3.1 has different names for these VI.

It has been a very long time since I worked with such an old version but version 3 was a major upgrade that made the MAC and Windows versions much more compatible. One of the changes was to make the VI names the same on both platforms and another was to make the locations the same (i.e. the name of the llb that the functions were stored in. You should be able to find the equivalent functions in 3.1. Open the app in 3.1 and when prompted to find a VI, browse around until you find it. If you have a list of the VIs that couldn't be found, before opening the old app, create a new VI. Use the palette to find the functions and place them on the diagram. Then, when you open the old VI, those functions with the same name will get replaced by the new ones. For ones w
hose name changed, you'll have to manually replace those one by one. I also seem to remember a compatibility llb that was available back then. It was a set of VIs that was not part of version 3. I have no clue as to whether it's still available from NI and whether it included everything you might need. The good news is that once you're past this conversion, upgrading becomes a lot easier.

Command line: Mass compile and LLB Conversion

Using LabView 8
Using a script (Perl or VBScript) I would like to extract some VI from our source control,
mass compile them to be to the current LabView version and then create a LLB from that directory.
The need for this is to have a synchonisation between 2 applications.
Since this needs to be done from a script, I need a way to perform this from the command line.
(The other solution we have, is to perform this manually every time a modification is made to the original files,
But sometimes memory can be defective and then .... )
Any suggestions, ideas...
Thanks
EricG

Eric,
That sounds like quite an undertaking, but I think you might be able to implement it (or at least most of it). LabVIEW does not have command line arguments for all that you want to do, so I would recommend building a VI that does what you want and then building that VI into an executable that utilizes command line arguments.
In this VI, opening VIs and mass compiling them can be accomplished through VI Server in the form of an Invoke Node -- these functions are methods under the Application class. Bear in mind that mass compiling can only bring VIs forward in versioning, not backward. For the LLB functions, you can use the Libraryn VIs that ship with LabVIEW -- they are "hidden" in the LabVIEW root directory under vi.lib/Utility/libraryn and are pretty intuitive. As far as the source code control, you are on your own, as that will be dependent on the specific SCC software you are using and will most likely require using ActiveX.
Once you have a VI built that does everything you want and you are ready to build it into an executable, you will want to configure it to accept command line arguments. There is a great online Knowledgebase on this subject, which I have linked here. And of course, if you run into any specific problems along the way you can get help from this great online community!
Best of luck!
E. Sulzer
Applications Engineer
National Instruments

Problems with mass compiling for LabVIEW 6.0.2

When mass compiling the LabVIEW folder after installing 6.0.2, I get a Log file telling me "Bad VI" for 8866 vi:s. Have looked specifically at two of them, and the broken arrows are fixed by pressing and clicking the broken arrow. Somehow I don't feel like doing this for 8866 vi:s.
What is wrong, and how do I fix it?
Attaching the Log.
//Martin
Attachments:
MassCompileLog ‏1263 KB

Yes, it definitely appears as though you need to reinstall NI-DAQ. You can receive this error when the VIs which are being mass compiled depend upon other VIs which are either not present or have been incorrectly updated. Make sure that you have installed NI-DAQ support for your new version of LabVIEW. This is separate from installed NI-DAQ by itself. You must install the LabVIEW support files also. You can get these off of NI's website.
Also, if you did a complete install of LabVIEW, you may have installed a newer version of NI-DAQ without realizing it. This could cause a problem if there are two versions of NI-DAQ on your computer. Make sure you only have one version.
J.R. Allen

Any way to mass compile to previous version?

I have 7.1.1 and want to mass compile a directory to 7.1.
Thanks.

JICHFI wrote:
«When you open a VI last saved in a previous version of LabVIEW, LabVIEW automatically converts and compiles the VI. You must save the VI in the current version of LabVIEW or the conversion process, which uses extra memory resources, occurs every time you access the VI.»
Read your quote and the question again. Your quoted section talks about what happens if you open a VI that has been saved in a previous version in the current version, i.e. open a lower version in a higher version.
This discussion talks about going from a higher version to a lower version. This is 180 degrees different.
The quote is not relevant to this discussion!
JICHFI wrote:
So I don't know who you are but I think that ...
I don't know who you are either except what is visible in your profile... It should not be relevant wo I am.
JICHFI wrote:
Save for Previous version does something with mass compile, this above VI opens recursively a bunch of VIs and save all of them to the desired version with the same filename.
Save for previous has nothing to do with masscompiling!
Masscompiling takes an existing folder full of VIs and converts them to the current version, overwriting the old versions in the process.
Save for previous creates a new folder containing new copies of all relevant VIs downconverted to the target version. Often, especially in order versions, the downconverted VIs need to be compiled again the first time they are opened in the old version (you would see something like "VI converted from 7.1 to 7.1"). They are NOT masscompiled. To fix this, you could use the previous version to masscompile the downconverted folder, or you could just do a "save all" the first time after opening in the old version. This has nothing to do with the question.
All this discussion is irrelevant because it is NOT possible to save as 7.1 from 7.1.1. They are fully compatible.
Since the original question does not make sense, we need further information from the OP.
LabVIEW Champion . Do more with less code and in less time .

I was doing some thing on my mac and the normal link to the applications folder from the bottom right hand corner disappeared, I cant find it anywhere, Can you help me?

I was doing some thing on my mac and the normal link to the applications folder from the bottom right hand corner disappeared, I cant find it anywhere, Can you help me?

Simple process. If an iPhone go to the Apple Store and not Verizon
the phone from Verizon will be a refurbished device and not new unless under the 14 day worry free guarantee
good luck

I have photoshop C6 on my MAC Pro and want to install it on my new MAC desktop. I sent the files with AirDrop but photoshop wont open I get an error message that it cant find the Library. Any thoughts?

I have photoshop C6 on my MAC Pro and want to install it on my new MAC desktop. I sent the files with AirDrop but photoshop wont open I get an error message that it cant find the Library. Any thoughts?

download the installation files and install using your serial number or adobe id,
Downloads available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 12 | 11, 10 | 9, 8, 7
Photoshop Elements: 12 | 11, 10 | 9,8,7
Lightroom: 5.5 (win), 5.5 (mac) | 5.4 (win), 5.4 (mac) | 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5
Contribute: CS5 | CS4, CS3
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

Hi! I need help, today I connected my mac Book Air to a tv for a presentation and as soon as I conected it the image on my screen went bigger. And I cant find the way to put it back as it was before. The Images are too big! heelp

Hi! I need help, today I connected my mac Book Air to a tv for a presentation and as soon as I conected it the image on my screen went bigger. And I cant find the way to put it back as it was before. The Images are too big! heelp

Morning DeeHutton,
Thanks for using Apple Support Communities.
For more information on this, take a look at this article:
iPhone: Hardware troubleshooting
http://support.apple.com/kb/ts2802
Best of luck,
Mario

Trying to connect a new printer to my Mac book, and it cant find the device any suggestions?

I have just bought a new printer a Canon MG5350 and my Mac will not connect to it. It wont find it through wireless and when i connect a printer cord, it recognises the printer but cant find any drivers to support it.
Has anyone got any suggestions?

Maybe, check their specs and read their reviews BEFORE purchasing.
No iOS device has been able to run Flash since the first iPhone was releasd. Here's why... http://www.apple.com/hotnews/thoughts-on-flash/

Cant find Mac OS boot after win 8.1 update.

Hi there,
Ive had a look around the net for a possible solution but no luck so far.
I recently installed Win 8.1 on a partition. My Macbook pro is a model A1398.
I was trying to create a shared partition. From Mac OS I made the new shared partition ex-FAT. I went into Win 8.1 reformatted it (cant remember if I left it at ex-FAT). In the process of restarting Win 8.1 was nice enough to download some updates and restarted itself.
From then on it doesnt see the Mac OS boot any more. Doesnt even boot into Windows! It has start up errors. I tried the command + R option and I cant do the following either:
1. I cant seem to do anything useful (unless Im missing something) with Disk Utility. Diagnostics show that the Mac OS X install is fine.
2. Cant re-install because it cant see any boot disk options to select from.
Right now Im screwed. Cant do anything with my "fancy pants" macbook pro. Any help would me much appreciated!
Cheers.

Had to revert to wiping everything out and starting from scratch. Didnt have a back up so thats the only way. Set the partition to GUID and Mac OS journalled.
Command + Option + P + R and then set it all to just one partition. Then re-install mac OS.
If the above start up option didnt work, try the command R then try the above option again.
Hoe this helps someone.

I tried to install windows 7 in my macbook pro late 2011 but i tried to create partions after it installed and it turn to dynamic disks and ican't access mac or win 7 what should I do i cant format it because i dont have a backup

I tried to install windows 7 in my macbook pro late 2011 but i tried to create partions after it installed and it turn to dynamic disks and i can't access mac or win 7 what should I do i cant format it because i dont have a backup

It's not that you can't format it because you have no backup, it's because you'll lose everything when you do. Lesson learned. Always have a backup.

Love Acrobat XI, but when I installed it became the default program to open all my photos. I'd like them to open in theirr native (JPEG, etc. format) How do I disable the PDF default conversion ? Cant' find anything in Preferences that works.

Love Acrobat XI, but when I installed it became the default program to open all my photos. I'd like them to open in theirr native (JPEG, etc. format) How do I disable the PDF default conversion ? Cant' find anything in Preferences that works.

Sounds like a file association issue in Windows. Right click on the files of interest and select Open With>Choose Default Program and select the program you want used (be sure the "always use" box is checked. The Acrobat installation should not have done this change, but this is the process to make the change on each file type.

LabVIEW classes and mass compile

Just wondering if anyone out there has found any problems mass compiling LabVIEW classes, as I am having what appears to be totally un-resolvable issues - I get a list of VIs that either say BadsubVI or BadVI all of which I have verified are error free.
The only thing I can round it down to is the use of the lvclasses, and in particular the fact that I'm making extensive use of the inheritance functionality, and also a few override vi's.
It wouldn't be such an issue except that I'm calling some of these vi's from TestStand, and am unable to get a deployment to work without a successful mass compile.
Appreciate any responses,
David Clark
CLA | CTA
CLA Design Ltd
Hampshire, England

I'm not sure if it's the same problem but I had a vi that would compile into an unrunable exe. I found the problem by mass compiling the project, which came up with a bad vi and bad subvi's that used that vi. Turns out my problem was that I had two classes with the same name (even though they were in separate lvlibs). And renaming one corrected my problem. LabVIEW 8.5 gives a warning and renames the compiled vi's (so if you could try 8.5, that might help you find the problem quicker assuming it's related). It seems to me that the name spaces provided by lvlibs go away when compiled into an exe or by the mass compiler (It may just affect lvlclasses).
Matt

Cant find instant message on my mac book pro

im running snowleopard on my mac book pro and i cant acess or find my instant messaging, no icon, and cant find it in finder or anywhere??? i bought it in 2011, its actually my sisters, my 2009 MBP works fine, any answers out there?

In answer to your second question, it wouldn't matter much on your sister's MBP, as Snow Leopard doesn't support iCloud for messaging (or for much of anything, though you can force a few things). Her iChat is limited to AIM instant messaging and such.
On your MBP, which according to your profile is running Lion (10.7.5), you also won't have access to iCloud messaging (iMessage) unless you installed the beta-test iMessages application and somehow kept it running. (I have heard it can no longer be installed and may no longer work at all. That's third-hand; I haven't tried it.) Your iChat will also be limited to AIM and such.
For those with iMessage-capable phones and computers, there is a choice to be made. Apple's apparent concept for iCloud would suggest that you would use a single iCloud account for all of the devices you individually own or use. (I do that; my wife does also, with her own ID.) That model works well when, for example, you want to receive all the same iMessages on all of your devices. Even if you don't, there are ways to keep them separate (e.g., use the phone number to send/receive iMessages on your iPhone while using an email address on the MBP).

MAC V2.2 conversion to V3.1 mass compile cant find certain VIs

Similar Messages

Maybe you are looking for