Open LabVIEW 8.0 files in LabVIEW 7.0

Hello,
I have developed an application in LabVIEW 8.0 and built a standalone executable just to realize that I have to deploy it in a Windows NT computer that is not compatible with LV Run Time Engine 8.0 that only supports Windows 2000 and XP. I have tried to open the labView files (*.vi) using LabVIEW 7.0 but it gives me an error. Is there any easy and clean solution to import these files in LV 7.0 in order to build a new excutable and make it compatible with Windows NT?
Regards,
Toni

The only way to convert these files to version 7.0 is to first save them as 7.1 and then open them up in version 7.1 which can then save them as 7.0. If you don't have a copy of 7.0, then if you post the VIs, someone may do the conversion for you. If you have used anything in the program that is not supported in an older version of LabVIEW, you will have to rewrite it. In the long run, it might be simpler to just upgrade the NT computer to something that LabVIEW (and Microsoft) supports.

Similar Messages

How can I enable Windows Explorer (Windows 7 64 bit) to open LabView 8.2.1 LLB files?

How can I enable Windows Explorer to open LabView LLB files? I am running LabView 8.2.1 on Windows 7 64 bit. The option “Enable Windows Explorer for LLB Files” in Tools/Options/Environment is unchecked and grayed out.

LabVIEW until 7.1 came with a shell extension that could display the content of an LLB in an explorer window.
That was removed in LabVIEW 8.x for a number of reasons.
- Shell extensions are pretty badly documented, tricky to implement right, and of very limited use since only Windows Explorer and a few explorer replacements can use them. It doesn't add any functionality for most other programs in Windows, since the shell extension are a Windows Explorer thing, and not a Windows core technology.
- With 8.x NI decided that LLBs were pretty old fashioned and their main feature of supporting file names longer than the DOS 8.3 naming was pretty much obsoleted by then, while they didn't allow for more than one level of directory hierarchy. So they decided to depreciate LLBs and declared them a legacy technology that should not be used for new development anymore.
- For the uupcoming 64 bit version of Windows a new shell extension would have been required to allow Explorer to use it.
For all these reasons the LLB shell extension was removed from the LabVIEW installation to further discourage the use of LLBs.
If you have a LabVIEW 7.0 or 7.1 installation on your computer and run 32 Bit Windows you can enable the shell extension in the LabVIEW Options dialog.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Opening nxt-g vi files in labview

Hey all,
Is it possible to open nxt-g vi files in labview? I'm using LV8.5 student edition, Errors (attached image of error message).
I'm specifically interested in how to communicate with the nxt 2 rgb light.
Cheers
Nick
Attachments:
VInotLoadable_Error.jpg ‏105 KB

Hey Nick,
If you are still having trouble opening that VI, check out this Knowledgebase discussing some additional avenue for seeking support for your NXT. In that knowledgebase, there is a link to"LabVIEW Add-ons for LEGO® MINDSTORMS® NXT" Do you have this toolkit installed? It could be a matter of simply installing this toolkit.
Hope this helps.
-Ben
WaterlooLabs

Opening a java jar file through a labview program

Hello,
I need to open a java jar file in labview........this jar file is a GUI with multiple frames and has buttons on each frame help navigate through between frames....i just require the program to open it and close it based on some signals so then i won't have to do it manually

LabVIEW doesn't have any control over what happens in a system exec, as you give the control to the system. You can, however, check the process list through .NET commands and kill the process (You should be able to stop it through "taskkill /F /im java.exe"). Not the prettiest solution, but should work.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

How to open labview program with Quit Labview function inside?

Hi Any idea how to open labview program with Quit Labview function inside?
I forgot to add and set the condition of the type for this program.
If the program is an application, it would close straight away.
If it is still labview work, it will go straight to editing program without closing.
So I need to recover, open it and make some changes.
Clement
Solved!
Go to Solution.

Put the VI in a project and open it from there, then it shouldn't autorun. You can use App.kind property of application to decide whether to close or not.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

Cannot open Labview 7 without "not enough memory" error

I get the "not enough mempry to complete this operation" as Labview is opening. I have tried uninstalling everything and reinstalling. No good. There is 512 Mb in this system should be plenty to open Labview. Any ideas? Labview will also not open a vi. It says it cannot find it (the one I selected for it to open). It tries to load it and all subvi's but cannot get past the first vi.

I figure there are two possiblities. LabVIEW is poorly installed on your system causing the error or your VIs are corrupted. You can test the former by installing LabVIEW on another computer. If you can open the VIs there, consider contacting NI for ways to more throughly remove NI products from your machine. To test the latter, see if you can create new VIs in 7, save, close, and reopen them. You can also see if other VIs on your machine open. If your VIs are corrupted, then try to open them in your older LV, copy the Block Diagram over to a new VI, save, and open in LV 7.0. At the very least, you can get a screen shot of the diagram.
Good luck!!

Opening LabVIEW source code

Hi,
This year LabVIEW celebrates its 20th birthday. A development environment that started from a virtual instrument development tool has grown into an outstanding general purpose visual programming language. Troughout LabVIEW history it has beeen debated if LabVIEW is a general purpose programming language or not. It defenitely is a general purpose programming language but maybe not as general as it could be. Every LabVIEW power user knows that even though LabVIEW has very many outstanding features, it also have very many shortcomings not present in the main stream programming languages and development environments.
Requirements for LabVIEW functionality keep raising as the number of LabVIEW users constantly grows. During the history of programming we have seen that it indeed is quite challenging to develop an excellent programming language. All the most popular languages are developed as a joint effort of the computer science community. This ensures that the design decissions made are in agreement with the state-of-the-art techniques of the present time and that all the possible shortcomings are considered when these design decissions are made.
LabVIEW as a proprietary programming language doesn't have the power of the computer science community. It may be extremely hard to recruit the best minds of the community to work exclusively for National Instruments already for purely geographical reasons. As a result NI presumably cannot keep up with the pace required to keep LabVIEW a high quality general purpose programming language. Until now NI has had central pantets protecting graphical design of LabVIEW. The most central ones of these patents have expired or are soon to expire leaving the field of graphical programming languages open for competition.
From this perspective it would be very wise move from National Instruments to open the source code for LabVIEW programming language and releasing the patents protecting the language for the use of the community helping to develop LabVIEW. National Instruments should see this more as an opportunity than a threat.
Opening the source for LabVIEW would gather new free-of-cost developers for developing LabVIEW. LabVIEW would improve and gain more reputation as a general purpose programming language. Students and computer scientists arount the world would get acquainted with LabVIEW as the barrier of expensive licenses wouldn't be there. LabVIEW has many features that are expected to be in a future general purpose programming language as natural support for multithreading. However it lacks many features that are required from a future general purpose programming language. As an open source language, LabVIEW could develop towards a generally accepted programming language of the next decade.
As the LabVIEW user community grows, also NI could take advantage of its expertise in LabVIEW integration. The growth of LabVIEW user community means that the number of pontential customers for National Instruments measurement and automation products grows and NI can take full business benfit from it. NI can still sell proprietary Measurement and Automation software and hardware for integrating the NI hardware with LabVIEW, managing measurement data and managing other measurement and automation related tasks. Only LabVIEW as a general purpose programming language would no longer be a source of income. Still NI could go on selling development environment for LabVIEW.
Open LabVIEW would also open new opportunities to NI. It could benefit from its expertise of software and hardware integration in the field of embedded computing. The embedded computing is growing fast as every device around us gains a microprocessor. If LabVIEW would be used as a general and most popular programming language for embedded computing, it would allow NI to sell number of new products and solutions to this embedded computing industry.
Open soruce LabVIEW is an opportunity for the LabVIEW community, for the computer science community in general and last but not least for National Instruments. LabVIEW community get improved general purpose programming language with all the state of the art techniques and functionality. Computer science community gets the opportunity to start developing programming techniques and paradigms for visual programming and this way solving the shortcomings of text-based programming languages bringing the programming for everyone. National Instruments would gain major advantages from LabVIEW becoming generally accepted programming language. The increasing user base would get NI a number of new potential customers and opportunity to start selling new kinds of products and solutions. On the other hand, if NI will not open LabVIEW source and tries to keep its monopoly, I predict that it may be hard to keep up with the recent developments in programming language technology. General purpose programming languages will evetually offer all the benefits of LabVIEW and much more. NI will lose it's position not only in LabVIEW but also as a provider of measurement and automation hardware.
I'd like to hear what you, the community, think of this issue.
Regards,
Tomi
Tomi Maila

I must say that I disagree with this idea. One of the very fundamental -- and important -- aspects of LabVIEW is its internal consistency as well as its wide applicability. Having been an "old lline" Unix hack, I know the message and promise around open source; however, I also know the incredible shortcomings that have come out of many of those initiatives. We run our deployed product in Windows, as a develped LV app precisely so that I have a consisten, intuitive programming environment. All of my development headaches throughout the life cycle of this product have come not from LV code but from the limitations of text-based code developed outside of the LV environment -- entities that have to be included via DLL calls and such. That all works well enough but, when there are profound changes to those outside development environments, it greatly hampers the ability to maintain and expand the legacy code. I have spent many days and weeks having to rewrite VB and VC++ code so as to make for easier integration and upgrading capability. In particular the shift -- on Microsoft's part -- from WMP6x to later incarnations, forced a complete rewrite of some important multimedia components. Similarly, changes to the <vector> class with the move to Visual Studio Net forced similar problems.
Open source still holds great promise but also great peril. Too many cooks really can spoil the broth at times.

How to open a specific excel file by activex & overwrite by set_cell_value.vi

I've seen the 'Write Table and Chart to XL.llb', but how can i open an existing excel file/workbook/sheet and rewrite some of the data instead of open a new worksheet everytime? It may already shown in your examples somewhere, but since I'm new to activex/property node stuff, I can't figure it out. Your help is appretiated.
Thanks
Anthony

The process is very similar. Starting with the example, open the diagram and you'll see a VI labled "Open Book" (The name of the VI is actually "Open New Workbook.vi". Right click on it and select Replace/Select a VI...
Now navigate to \\Labview 7.0\examples\comm\excelexamples.llb and select the file "Open Specific Workbook.vi". This VI has an input for specifying a filename to open.
Likewise, the example also calls a VI named "Open a New Worksheet.vi" replace that with "Open a Specific Worksheet.vi" (found in the same place).
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Open an existing Excel file created by Report Generation Toolkit

How would I open an existing Excel file that has been created by the LabVIEW Report Generation Toolkit?
Let me explain my application. I have made a test program to collect data on a device. Each time I run the program I want it to append a new row onto an existing data file. Since the tests I do are sometimes over a period of days, I cannot keep the program open and running continuously. So I have to open an existing file and append the new data to it. In technical terms, what I need is to get the 'report out' reference to the existing Excel data file without losing the data that is already there.

For info on accessing Excel do a search in the examples for the word "Excel" you will get an example that shows how to open a spreadsheet and manipulate the data. This should get you started.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

How do i open a VERY big file?

I hope someone can help.
I did some testing using a LeCroy LT342 in segment mode. Using the
Labview driver i downloaded the data over GPIB and saved it to a
spreadsheet file. Unfortunately it created very big files (ranging from
200MB to 600MB). I now need to process them but Labview doesn't like
them. I would be very happy to split the files into an individual file
for each row (i can do this quite easily) but labview just sits there
when i try to open the file.
I don't know enough about computers and memory (my spec is 1.8GHz
Pentium 4, 384MB RAM) to figure out whether if i just leave it for long
enough it will do the job or not.
Has anyone any experience or help they could offer?
Thanks,
Phil

When you open (and read) a file you usually move it from your hard disk (permanent storage) to ram. This allows you to manipulate it in high speeds using fast RAM memory, if you don't have enough memory (RAM) to read the whole file, you will be forced to use virtual memory (uses swap space on the HD as "virtual" RAM) which is very slow. Since you only have 384 MB of RAM and want to process Huge files (200MB-600MB) you could easily and inexpensively upgrade to 1GB of RAM and see large speed increases. A better option is to lode the file in chunks looking at some number of lines at a time and processing this amount of data and repeat until the file is complete, this will be more programming but will allow you to use much lass RAM at any instance.
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Opening a Somat .sie file in DIAdem takes forever

Hi All,
I'm new to DIAdem but know LabVIEW well. I am trying to open a Somat .sie file. I have the Somat .sie data plugin installed and DIAdem sees the file fine but it takes forever to load. The file opens fine using SoMat InField (and very quickly). I've attached a sample for you to take a look at.
Anyone who can pop it open straight away?
Thanks,
Phil

Oops. Never attached the file.
Change .txt to .sie.
Attachments:
edaq_test (1) - Copy.txt ‏4756 KB

Currently Have Photoshop CS3 & Adobe Bridge CS3 2.1.1.9. According to Adobe, Camera Raw 4.6 supports Nikon D810 NEF files. I have downloaded Camera Raw 4.6 Update. When I try to open Nikon D810 NEF files, I get photoshop error that says "cannot complete

Currently Have Photoshop CS3 & Adobe Bridge CS3 2.1.1.9.
According to Adobe, Camera Raw 4.6 supports Nikon D810 NEF files. I have downloaded Camera Raw 4.6 Update. When
I try to open Nikon D810 NEF files, I get photoshop error that says
"cannot complete request your because it is not the right kind of
document. These NEF files wont open in Bridge at all. What am I doing wrong?

Camera Raw plug-in | Supported cameras

Pages 08 won't open my old pages file

I just upgraded to Pages 08 and when I try to open the file I was working on yesterday, with the previous version of pages, it says "The document...couldn't be opened". How can I open the old pages file with the new version?

It may be useful to trash the preferences file:
<bootVolume>:Users:<yourAccount>:Library:Preferences:com.apple.iWork.Pages.plist
But I'm afraid that the document is corrupted.
Control click its icon then select the "Show package's contents" in the contextual menu.
The standard contents is:
Contents
QuickLook
index.xml.gz
The described message is displayed when there is no "index.xml.gz" (or "index.xml") file.
It is also displayed when the "index.xml.gz" (or "index.xml") is badly formed.
The index may be dropped when the documents where stored on an iDisk.
Yvan KOENIG (from FRANCE jeudi 28 août 2008 12:21:36)

How export to csv work in safari browser? In my application export to csv open like a raw data in new tab. But other browsers working great!. Need to open in a csv file or save it as a csv file.

How export to csv work in safari browser?
In my application export to csv open like a raw data in new tab.
But other browsers working great!.
Need to open in a csv file or save it as a csv file.
Please suggest me. Thank you in advance!.

Hi Adrian,
Why don't you try any another software for opening CSV files then Notepad ? According to my experience, you can use these softwares to open an CSV files and they are:-
Microsoft Excel
Open Office Calc
Google Docs
Also there is an additional tool available known as CSV viewer. You may try this, download it from here http://www.csvviewer.com/
I've never used Notepad for opening CSV files, because sometimes it contains some symbols which are not not at all compatibile with Notepad.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I'm trying to copy music from my PC to itunes. I open itunes, go to 'file', go to 'add folder to library', select the folder and nothing happens. What am I doing wrong?

I'm trying to copy music from my PC to itunes. I open itunes, go to 'file', go to 'add folder to library', select the folder and nothing happens. What am I doing wrong?

Hello there, gleab.
The following Knowledge Base article reviews the ways to import content into iTunes:
Adding music and other content to iTunes
http://support.apple.com/kb/ht1473
Also keep in mind which formats can be added:
You can add audio files that are in AAC, MP3, WAV, AIFF, Apple Lossless, or Audible.com (.aa) format. If you have unprotected WMA content, iTunes for Windows can convert these files to one of these formats.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Open LabVIEW 8.0 files in LabVIEW 7.0

Similar Messages

Maybe you are looking for