Migrating labview 8.2 vi to labview 7.1

How do I convert a VI which was saved with LabVIEW version 8.2 so that it might open in LabVIEW version 7.1 for coding/editing? (I don't have LabVIEW version 8.0).
I'll be grateful for any/all advice/help!

Post the vi here in the forum. Somebody will convert it for you.

Similar Messages

Error migrating Labview 7.1 scf file to Lavbiew DSC 8.20

Hello,
I am trying to migrate a small .scf file (in annex of this note) coming from the tag engine of Labview DSC 7.1 to Labview 8.20 but get plenty of error messages as showed in annex of this note. I have got the DSC 8.20 version of August 2006. The only tags that can migrate are the 4 default tags showed when tag engine 7.1 is opened the first time.
Thank you to help me solving this weird problem,
Christophe
Attachments:
ErrorMigratingSCF.jpg ‏199 KB
default.zip ‏2 KB

Chris,
Did you resolve the migration issue? If you did, how did you do it? It has to do with the I/O server.
Roy L. Costa
Email: [email protected]
Catalyst Test Engineer
General Motors Warren Tech Center (R & D)

Seamlessly migrating Labview 6.1 to Labview 10

Hi,
My company have several legacy projects that were written in Labview 6.1.
We recently bought Labview 2010 and tried to convert the projects over and found several issues:
1) Report Toolkit changes
    Write PNG (word). vi
    Write JPEG (word) . vi
    were missing
2) Received the following warnings:
   Labview changed a constant that was wired to a Case Structure to a hidden control to maintain compatability with Labview 7.1 and earlier
Is there an easy way to port from Labview 6.1 to Labview 2010?
I am not a Labview developer myself so pardon me for any silly questions.
Thanks & Best Regards

Generally upgrading over 4 versions will result in some warnings and some things broken, as you have observed. First thing is to save the warnings to a file so you can go back through it as often as necessary.
Use the dialog which comes up when you try to run the broken (upgraded) VI. That will take you with one click to places where something is broken. Systematically work through those. Often replacing an obsolete subVI with one from the current palette takes care of most of the problem. You may need to reconnect wires if the connector pane is different. For some replacements you may need to change datatypes on inputs. Examples include arrays to waveform or numerics to enums. As you do this check the functionality of the replacements to see if anything has changed which will affect the performance of your program.
Then work through the warnings list. Verify that the warning does not cause undesired behavior in your program. If it does, then you need to change something. If it does not, make a note to consider modifications to get rid of whatever the warning was about after everything is fully functional.
Although it does not sound like this has occurred in your case, consider whether it would be better to use the old program as a guide to establish a test or performance specification. Use that to write a new program, probably with a better architecture and taking advantage of new features. For example the old program might use lost of sequence structures and local variables, making it difficult to modify or even to understand. The new one might be written using a Producer/Consumer architecture and LVOOP techniques. Rewriting may not take much longer than trying to "fix" the old program and results in a program which takes full advantage of new features and techniques.
I am planning a rewrite this summer or fall in LV 2010 or LV 2011, depending on timing, of a program whose ancestor was written in LV 1.2 in 1988-89. The kind of rewrite I described above has already been done twice on this program.
Lynn

Position for Programmer experience with DAQ and C++/Labview

We are company located in the Bay Area of California and looking for
a programmer experienced with programming (from scratch) DAQ boards for
signal generation (sine/triangle/sawtooth) waveforms as well as DAQ
digitizers, FFT, and data displaying.
You should be
able to program these cards using C++, but should have strong knowledge
of labview as well. You may be asked to translate and migrate labview
VI's to the C++ enviroment.
Job applicants from
the Bay Area, as well as abroad are welcome to apply.Those outside of
the Bay Area can develop code at your own home office and must have
C++/labview on a suitable computer for programming.
Applicants should apply by sending an email to: jobs at intereasemedical dot com and indicate IE002 as the job position code.
Do not post your resume as a reply to this forum post.
Do include your resume in PDF or DOC format
Do
include your billing rate and if you are authorized to work in the U.S
if located in the Bay Area. We do not provide H1B sponsorship.
Responses without the above information will not be considered.
Thank you!

Hello, I have much experience with DAQ, C++ and Labview. How to apply for this position?

Migrating code from windows to linux

Hi,
I am looking for a solution or method to migrate labview code developed in windows platform into Linux platform. The thing is we have developed instrument driver code in Windows platform and have used VISA as well for communication purposes. I've come to know about some method for such porting to follow as the project file of ours contains vi.lib stuff as well. We do have a license for both Windows and Linux versions of Labview.
Please suggest me any solution to do such porting into Linux platform if someboy have come across such things.
Thanks in Advance,
Vivek

Thanks guys for quick responses. I really appreciate your support. I tried the way you mentioned. I copied all my code into the linux system. Created new project file but again same problem occurs, labview is crashing because of VISA.
Why I am sure about the VISA is because I tried to open/create new VI in linux using VISA API's and all are creating trouble and further it leads labview to crash.
Rest all other functions in labview are working fine. Hope all my assumptions are correct and could blame VISA for creating problems.
Please do suggest us ...
Thanks in Advance,
Vivek

Migrating large project from DSC 7.1 to LabView 2009 Shared Variables ... What's the next step after recreating my variables?

I am in the process of migrating a large distributed (multi-workstation) automation system from the LabVIEW 7.11 DSCEngine on Windows XP to the LabVIEW 2009 Shared Variable Engine on Windows 7.
I have about 600 tags which represent data or IO states in a series of Opto22 instruments, accessible via their OptoOPCServer. There are another 150 memory tags which are used so the multiple workstations can trade requests and status information to coordinate motion and process sequencing. Only one workstation may be allowed to run the Opto22 server, because otherwise the Opto22 instruments are overwhelmed by the multiple communications requests; for simplicity, I'll refer to that workstation as the Opto22 gateway.
The LabVIEW 2009 migration tool was unable to properly migrate the Opto22 tags, but with some help from NI support (thank you, Jared!) and many days of pointing and clicking, I have successfully created a bound shared-variable library connecting to all the necessary data and IO. I've also created shared variables corresponding to the memory tags. All the variables have been deployed.
So far, so good. After much fighting with Windows 7 network location settings, I can open the Distributed System Manager on a second W7/LV2009 machine (I'll refer to it as the "remote" machine henceforth) and see the processes and all those variables on the Opto22 gateway workstation. I've also created a few variables on the remote workstation and confirmed that I can see them from the gateway workstation.
Now I need to be able to use (both read and write) the variables in VIs running on the remote workstation machine. (And by extension, on more remote workstations as I do the upgrade/migration).
I have succeeded in reading and writing them by creating a tag reader pointed at the URL for the process on the Opto22 gateway. I can see a way I could replace the old DSC tag reads and writes in my applications using this technique, but is this the right way to do this? Is this actually using the Shared Variable Engine, or is it actually using the DataSocket? I know for a fact that attempting to manipulate ~800 items via Datasocket will bog down the systems.
I had the impression that I should be able to create shared variables in my project on the remote workstation that link to those on the Opto22 gateway workstation. When, however, I try to browse to find the processes on that workstation, I get an error saying that isn't possible.
Am I on the right track with the tag reader? If not, is there some basic step I'm missing in trying to access the shared variables I created on the gateway workstation?
Any advice will be greatly appreciated.
Kevin
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

I have found the answer to part of my question -- an relatively easy way to create a "remote" library of shared variables that connect to the master library on my gateway workstation.
Export the variables from the master library as a csv file and copy that to the remote machine.
Open the file on the remote machine (in excel or the spreadsheet app of your choice) and (for safety's sake) immediately save it with a name marking it as the remote version.
Find the network path column (it was "U" in my file).
replace the path for each variable (which will be either a long file path or a blank, depending on the kind of variable) with \\machine\'process name'\variable name
where machine is the name or ip address of the master (gateway) workstation (I used the ip address to make sure it uses my dedicated automation ethernet network rather than our building-wide network)
and process name is the name of the process with the deployed variables visible in the Distributed System Manager on the gateway machine.
NOTE the single quotes around the process name; they are required.
The variable name is in the first ("A") column, so in Excel, I could do this for line 2 with the formula =CONCATENATE("\\machine\'process name'\",A2)
Once the formula worked on line 2, I could copy it into all the other lines.
Save the CSV file.
Import the CSV into the remote library to create the variables.
Note: at this point, if you attempt to deploy the variables, it will fail. The aliases are not quite set properly yet.
Open the properties for the first imported variable.
There is probably an error message at the bottom saying the alias is invalid.
In the alias section, you'll see it is set to "Project Variable" with the network path from step 4.
Change the setting to "PSP URL" with the same path and the error message should disappear.
Close the properties box, save the library, and then export the variables to a new CSV file.
Open the new CSV file in Excel, and scroll sideways to the NetworkrojectBound field.
You'll notice it is False for the first variable, and true for the rest. Set the field FALSE for all lines in the spreadsheet.
Scroll sideways... you'll notice there are two new columns between NetworkrojectPath and Network:UseBinding
The first one is NetworkingleWriter; it should already be FALSE for all lines.
The second one is Network:URL. That needs to be set equal to the value for each line of NetworkrojectPath.
You can accomplish this with a formula like in step 4. In Excel it was =U2 for line 2, and then cut and paste into all lines below it.
There is a third new field, Path, which should already be set to the location of the variable library. You don't need to do anything with it.
Save the edited CSV file.
Go back to the remote library, and import variables from the just-edited remote library CSV file.
Once you have imported them and the Multiple Variable Editor opens, click on done.
You should now be able to deploy the remote variable library without error. (Make sure to open the Distributed System Manager and start the local variable engine. It took me a few failures before I realized I had to do that before attempting a deployment).
Voila! You now have a "remote" library of shared variables that references all the shared variables on the master machine, and which should be deployable on other machines with very little difficulty.
It actually took longer to write out the process here than to perform these steps once I figured it out.
Kevin Roche
Advisory Engineer/Scientist
Spintronics and Magnetoelectronics group
IBM Research Almaden

LabVIEW DSC: Migration from 6.1 to 8.6 problems

Colleagues,
I need help from someone who experienced with LabVIEW DSC. I would like to recompile pretty old application written in LabVIEW 6.1/DSC 6.1 to LabVIEW 8.6, and got lot of troubles with this.
At the first I have tried to migrate my old scf file as described here: "Migrating from LabVIEW DSC 7.1 to 8.0".
Well, it seems to be OK, and LabVIEW.lvlib library with variables was created, but when I tried to double click on the some items, then exception occurred in LabVIEW (see dsc_exception.png in attachment).
Can you please open test project (attached to this post) and double-click on the Slave005_A0 Item? Is crash happened only by me or by someone else?
The second problem with understanding.
In LabVIEW DSC 6.1 I have used "Read Tag.vi" / "Write Tag.vi" vis for accessing the items. When my VI opened in LabVIEW/DSC 8.6, then these calls replaced with "legacy_Write_Tag_(analog)7x.vi" (see screenshot). I'm unable to found according VIs in DSC 8.6. How can I write/read my tags in the latest version? As far as I can understand, I can use Shared Variables directly. Is this correct? But then how can I read multiple tags? Through DataSocket VIs?
The same with "legacy_Get_Tag_List7x.vi". How can I get items list in DSC 8.6 programmatically?
Or should I leave all legacy* vis in my application?
thanks in advance and best regards,
Andrey.
Attachments:
dsc_exception.png ‏26 KB
dsc_legacy_Write_Tag.png ‏3 KB
TestProject.zip ‏4 KB

Hi Andrey,
Yes, my LabVIEW crashes as well. As you may have noticed, a lot has changed in LabVIEW 8.0 with regards to DSC, the most important being that tags are replaced with Shared Variables. I would recommend that you go through each variable and create them by yourself to ensure the most reliable performance.
If you are interested in reading 'tags', then you just need to drag the Shared Variable and place it on the block diagram (that's the direct way). If you are interested in doing this programatically, then have a look at the DSC Module -> Engine Control -> Variables & I/O Servers -> Get Shared Variable List palette on the block diagram. You can then use DataSocket to access the Shared Variables.
Don't leave the legacy VIs on your block diagram. Upgrade your whole project; shared variables are here to stay. Have a look at the following article to get a thorough understanding of them:
Using the LabVIEW Shared Variable
Let us know if you have more questions.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Labview 5 software migration to modern labview and pc

Hi,
I have been stuck with trying to move a labview software from an old windows 98 pc to a newer windows 7 32-bit pc. The old windows 98 pc was running labview 5 for this software and it uses a PCI-GPIB/+ card to send and read data to some camac modules. This software has a few packages that it depends on such as NI spy, NI 488.2 1.7, T&M explorer. Currently if I try to run the software with the converted VI's by using labview 8 as an intermediate step errors out on the initial part where it tries to find the 488.2 interface card. I have however installed the drivers for this newer version of labview 2014 32-bit but still no luck. Has anyone had a similar problem or has any advice on how I would migrate this software succesfully? I do not really want to re-do the entire program as there is no time for it. This is a really confusing issue for me since I never used such old hardware and software combination. Please let me know if you would like more information.
Kind regards.

Hi Dennis Knutson,
Thank you for getting back to me. I have attached the error message, I am currently using NI-488.2 14.0 for my GPIB solutions. I have also attached the VIs in a zipped folder with the required libraries. The main VI is banc-test-cables-Atlas-CERN-2006-02-21. Please let me know if you require more information.
Kind regards.
Attachments:
banc-test-cables-Atlas-CERN-2006-02-21 Folder.zip ‏752 KB

Migrating inspection from Vision Builder to Labview

When I migrate my inspection, which includes an Acquire Image function, from Vision Builder for AI 2.0 to Labview 7.0, it asks me to find a bunch of *.vi and *.ctl files such as "IMAQ Resource Manager.vi", "IMAQ Configure Buffer.vi", "IVB Image Providers Manager Function.ctl" etc. I cannot locate these files so I just hit "Cancel" when these messages pop up, and the migration is said to be successful but the resulting vi can not be run in Labview. What's wrong? I do have IMAQ Vision 7.0.1.

All of the Vision Builder AI generated VIs are typically installed in the following directory: C:\Program Files\National Instruments\Vision Builder AI 2.0\LV\SubVIs. Within that folder you should have approximately 25 VI libraries (such as Common.llb, IVB Match Pattern.llb, etc.) and several other VIs (i.e. Inspect Result.vi and Inspect Setup.vi, etc.).
Did you install Vision Builder AI to a different directory than the default location? Have you tried repairing/reinstalling Vision Builder AI?
Best regards,
Dawna P.
Applications Engineer
National Instruments

Vision builder migrating to labview... Many VI

Hi,
I am using the latest version of labview and NI vision builder. By using the Vision builder am getting the X and Y coordinates of the object in that area. I need to export this to labview. I tried by going to "migrate to labview" . Then I created a new folder, then I gave the name. When I click OK. It creates many VI's. I need this in single VI. When I open the "main.VI" i could only see "pass, start" ; when i check the block diagram.I couldn't find the programe that i needed for it.
Hope you have understood my question.
Can you please help me.
Thanks in Advance
Solved!
Go to Solution.

Another option, which could be used in conjunction with the API solution Christophe mentioned is to make your X/Y values shared variables that you update in your VBAI inspection and then read in your LV code. Here's a tutorial on using shared variables to communicate results to LV from VBAI:
http://digital.ni.com/public.nsf/allkb/D492139A746F91A8862576E80051BBCE
Here's a video of how to use the API that Christophe was mentioning:
http://zone.ni.com/wv/app/doc/p/id/wv-2424
Here's a video of using shared variables (demo shows using RT targets, but the same idea would work locally):
http://zone.ni.com/wv/app/doc/p/id/wv-2423

When I try to migrate vision builder to labview I get an error message

when I try to migrate vision builder to labview I get an error message "Error at Labview code creation step #6"

Does the error seem to be occurring at the same step in your Vision Builder AI script? See if you can determine if a certain step introduces the error by trying different modifications of your script and/or generating LabVIEW code from a Vision Builder AI example inspection. Also, are you using IMAQ Vision 7.0 for LabVIEW or a previous version of the Vision software?
Best regards,
Dawna P.
Applications Engineer
National Instruments

MIgrating to Mac Book from LabView 6i (Windows 98)

Hi ! I have a question about if its possible to migrate a project from LabView 6i running in a Windows 98 machine to a newer version of LabView and Mac OS X.
The project reads data from FP-AI-110 (http://sine.ni.com/nips/cds/view/p/lang/es/nid/2185)
The machine with Windows 98 connects to the FP-AI-110 using a RS-232 serial cable.
Thanks for your time !
Solved!
Go to Solution.

johnsold wrote:
I do not think there is any support for programming compact FieldPoint on the Mac. However you should be able to communicate via RS-232 from the Mac. No recent version of a Mac has an RS-232 port (I am not sure any Mac ever had a native RS-232 port). I have used USB to RS-232 adapters built around the FTDI chip with success on the Mac. I do not recommend adapters with the Prolific chip or drivers.
At least the Mac II series had (almost) all a serial port. Electrically it was actually RS-422 and physically it was a somewhat odd connector but with a little adapter cable it could usually be used as RS-232 too.
There used to be a VI library that implemented the Optomux or whatever it was called protocol of the serial interface on the FP modules. It was meant to allow access from RT targets back in the early days of LabVIEW realtime, when things were all not so much integrated as nowadays.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

VBAI 2011, possible to migrate directly to LabVIEW 8.6 code?

Hi,
Just wondering if VBAI 2011 can migrate inspections directly to LabVIEW 8.6 code. I have installed on my computer:
VBAI 2011
LabVIEW 8.6
LabVIEW 2010
LabVIEW 2011
NI Vision Development Module 2011
I don't see the option for LabVIEW 8.6 on my menu. Any suggestions?
John Wu
Riobotics Consulting
Solved!
Go to Solution.
Attachments:
problem.png ‏34 KB

I encourage you to look at the Vision Builder AI LabVIEW API, which is supported in LabVIEW 8.6.
This feature allow you to control Vision Builder AI from LabVIEW (open inspection, run once, get results etc.)
Unless your application requires really tight hardware integration, with hardware that you can only do in LabVIEW code, the code you're going to write with the API will be much cleaner than working with the code generated, which is somehow complex.
Look at the examples located here:
C:\Program Files (x86)\National Instruments\Vision Builder AI 2011\API Examples\LabVIEW Examples
Best regards,
Christophe

Migrated from VBAI to labview 8.2.

I’m fairly new at these vision programs and need some advise. I have migrated from VBAI to LabView 8.2. However I can’t seem to get the LV program to work like VBAI program works. The LV program gets stuck in a loop processing the same photo rather than the entire folder of 25. The other problems are: It will not show the photo; it will fail all photos, and will not log results.
I am running the LV 8.2, Vision Acquisition 8.2, and VBAI 3.0

Hi Davis,
I'm not experienced in VBAI and IMAQ, but in your code I couldn't find any function to load your JPG photos...
There's only an 'IMAQ Create' in the initialize-sequence, which generates an empty image. So it seems you have to attach your own code here ;-)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

LabVIEW 7 migration of Serial VI's from Philips Research

Hi
Has anyone "migrated" the Serial VI collection from Philips Research to
LabVIEW 7 (VISA).

added is a compatibility library that even has red crosses through the icons to stress that you should use VISA directly for future projects.
greetings from the Netherlands
Attachments:
nlserialLV7.llb ‏391 KB

Migrating labview 8.2 vi to labview 7.1

Similar Messages

Maybe you are looking for