Memory Footprint for LabVIEW 7.1 Full Development System

Hello,
I would like to know the memory footprint for LabVIEW 7.1 Full Development System.Both during the installtion and for developing applications later.
Can someone help.Thank you.
Solved!
Go to Solution.

There isn't a single answer for that, as this varies considerably.
As far as disk space goes, if memory serves, the basic 7.x takes up a few hundred MB, but that could inflate considerably depending on which modules and drivers you add to it.
For RAM, I believe 7.0 used to take up ~20-50 MB immediately after being loaded, but that number would then also change a lot over time depending on what you do. Loading, editing and running code all regularly change the amount of RAM used.
Why are you asking? Also, are you aware that 7.1 is relatively old by now (came out 7 years ago)?
Try to take over the world!

Similar Messages

Labview Full Developement System 8.2 on Windows 7

Hi there,
I have a question about the compatibility of Labview Full Developement System 8.2 and Windows 7.
Is it possible to run this system without problems on a PC that is using Windows 7?
I am also using the Labview DSC module (version 8.2.1).
I'm just wondering if I will get problems when I am going to run programs that I made, in Windows 7.
Or is there a new version of Labview that is compatible with Windows 7?
If so, is it possible to use older versions of Labview in this new version (bij transfering the files).
I hope to hear soon from some of you.
Regards,
Kenny

LabVIEW 2009 is the first LabVIEW version officially compatible with Windows 7 (see also)
Quote: Starting with 6.0.2, LabVIEW should run on newer, unlisted versions of Windows without error messages, but these are not officially supported.
(However, I was able to run LabVIEW 8.2 just fine under windows 7 64 bit. I don't know if there are potential DSC issues. Another option is the windows XP compatibility mode virtual PC available for some version of Windows 7).
LabVIEW 2009 and 2010 are fully compatible with Windows 7. You should be able to open your LabVIEW 8.2 files fin in any newer version. For details, have a look at the LabVIEW version compatibility matrix.
LabVIEW Champion . Do more with less code and in less time .

Signal Express not activated with Labview Full Development System Volume License

I'm using a volume license manager to generate license for disconnected machines. I just upgraded to Labview 2009. The license files work for labview but are not working for signal express. I have the Labview full development system which included signal express in the past. Both labview and signal express work fine on my computer that also has the volume licensing manager software installed. This computer is connected to the license server. I need to get signal express activated on my disconnected machines.

LabVIEW Full Development licenses still include Signal Express. Are you saying that whenever you are connected to the server you can run Signal Express just fine, but whenever you create a disconnected license Signal Express is not able to launch? Can you verify that you are, in fact, checking a license out from the server whenever you are connected to the network?
If you still have trouble I would recommend calling NI support so we could get more informatioin (such as your license file, contract ID, etc).

How to download LabVIEW Full Development System 7.1 and tool kit

I want to get the "LabVIEW Full Development System 7.1 and tool kit", Where Can I download it from?
TIA

LabVIEW 7.1 is ancient, LabVIEW 2011 is current. There is more than one "toolkit". What did you have in mind, exactly?
You can donwload an evaluation version of LabVIEW 2011 from here. Is there any specific reason you want to use 7.1?
If you have a valid license for LabVIEW 2011 you should be able to use it also for older versions. Contact your local NI representative. Are you on SSP?
LabVIEW Champion . Do more with less code and in less time .

LabVIEW Full Development System 7.1 and tool kit

hello, i am confusing about the LabVIEW Full Development System 7.1 product.
what is thats means? any different of standard Ni LabVIEW 7.1. Is the full development system is already includes a tool kit.
i want to open an example file from this page...(http://zone.ni.com/devzone/cda/epd/p/id/5146) , i am using LabVIEW 7.1 student edition. It say file not found...( http://forums.ni.com/attachments/ni/170/292574/1/file%20not%20found.JPG)
and also i would like to know about the tool kit from this page...(http://sine.ni.com/nips/cds/view/p/lang/en/nid/12855)
is this the reason why the file not found when i open the am_modulation.vi because i don't have this product? thanks
zull azym
research assistant
Tun Hussein Onn University of Malaysia

I have found your original question and the attached VI.
am_modulation.vi you have attached was saved in LV 8.0. You do not need the modulation toolkit to open the VI. I redownloded the VI from the NI web page and it was stored in LV 8.0 too. I made a comment on this on the page.
I have attached the converted VI.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions
Attachments:
am_modulation.zip ‏2535 KB

Recherche Labview Full Development System 8.2

Bonjour,
Je suis a la recherche de la version 8.2 de Labview Full Development System.
Quelqu'un peut-il m'indiquer ou la telecharger ?
Je ne parviens pas a la trouver sur le site de NI (version trop ancienne).
En vous remerciant par avance.
Bien cordialement.
J. C. Quantin

Pour la version de LabVIEW : http://www.ni.com/download/labview-development-system-8.2/3576/en/

Real Time Module, upgrading Labview 6.02 Base Development System?

Hi,
I have Labview 6.02 Base Development System but I need the Real Time module.
Would it be possible to get it upgrading the Labview 6.02? Is the full development systemm needed?
Which could be the cheapest way to get Real Time module?
Thanks.

You can upgrade to the latest version of LabVIEW Real-Time version 7.1 by upgrading both LabVIEW and LabVIEW Real-Time. You can all about the new features of LabVIEW Real-Time at the following link. For more information, please contact us at .
Regards,
Kristi H
National Instruments
>

Using full development system on customized test setup that normally uses run-time - How to do?

I have 8.2 Full Development System (2 copies as there are two of us who write code).
I develop testing systems, each on an individual computer, each customized with a custom built (by me) interface to test and measure perfomance of motors produced on the production line.
In order to modify the program and test it, I have to replace the production set-up computer with my developmental computer, make the changes (and check that they work) and then make the run-time version for the production computer. THEN switch computers. Since I have nearly a dozen different setups, I cannot just make two production test sets of each (one for development and one for production).
Is there an easier way?
Perhaps with HDD in a drawer? But then I'd have driver and version issues.
Is it possible to run the full development system remotely (from the production setup)?
What about a site-license?
Thanks,
Tim K

From the 8.2 Release Notes:
Single-Seat and Multi-Seat Licensing
LabVIEW supports both single-seat and multi-seat licenses. Single-seat
licensing is the use of LabVIEW on up to three computers but by only one
user. Multi-seat, or volume, licensing is the use of LabVIEW on several
computers or by several users. Each seat using LabVIEW must have a valid
license from a license server. Refer to the National Instruments Web site at
ni.com/license for more information.
You are permitted to install LabVIEW on the the pc with the hardware, do the changes and debug, and re-build the app for production.

Error 22A8 "Error requires full development system to be fixed"

Hello, I have successfully built my application with the application builder. The application is a plug-in architecture where I have paths to different .lvclass files internally in the .exe file which I have set to "always included" in the build. The different classes will be loaded dynamically
When I run the executable on my development machine it start up and everything works fine. But when I want to run in on another machine with only the LV runtime installed I get the following error:
Error 22A8 "Error requires full development system to be fixed"
How is that? anyone know what that mean? I don't find much information about this when I search on the internet so i'm kinda stuck now. Im using LV 2011 sp1.
Best regards
Thomas

Hi,
What is the runtime engine that you installed in the other computer? Does that computer have any LabVIEW installed as well?
May i have a screenshot of that error code again? I don't think the is such an error link error 22A8.
If you want to create an application (.exe) which is to be run on a computer that does not have any NI software installed. I suggest that you create an installer not an executable. You can build an installer using application builder. What it does is that it includes not only runtime engine but also other addons which is required due to the toolkits you may have used in your code.
You can learn about creating installers here:
http://www.youtube.com/watch?v=V_NsSOVx3wc
If the error still comes out, you can refer to the other discussions with the similar error message as yours:
http://digital.ni.com/public.nsf/allkb/F715F1ED66878F8E862574F8006AD6A1
http://www.ni.com/white-paper/13164/en/#212136_by_Category
http://forums.ni.com/t5/LabVIEW/A-full-development-version-of-labview-required-to-fix-the-errors/m-p...
Warmest regards,
Lennard.C
Learning new things everyday...

Looking for Labview programming jobs in embedded systems

I am a Canadian citizen graduated with Mechatronics degree from University of Waterloo, currently employed in Boston area as an Electrical Engineer until the end of my contract in August 2009. I have over 3 years of R&D experience in the high tech industries, mainly focus on embedded and electronic applications controlled through Xilinx FPGA programmed in Labview. I have extensive knowledge of digital and analog applications controlled by microcontrollers, FPGA, and microprocessors, as well as pragramming firmware interfaces on and off the circuit boards.
I require TN-1 visa sponsorship to work in the US, which is very easy to obtain. I am willing to relocate to many parts of USA to work full time or contract. Please contact me at [email protected] if a position becomes available.
David Zhou
Electrical Engineer
CIMIT/MGH
65 Landsdowne St, Cambridge, MA, 02139
p: 617-768-8759

You still around, contact [email protected]

Labview 10.0.1 development system has stopped working

I am getting this cryptic message when trying to build an EXE in windows 7.
It happens right at the end of the build process when the application builder message says "saving main.vi" where "Main.vi" is the primary.
It forces labVIEW to close.
Anyone have any experience troubleshooting an error like this?
Thanks -

I am experiencing the same issue. I am no longer able to build the Host exe (i.e. an exe under the My Computer target) for a certain project. I am able to build the RT exe under 2 different cFP-2220 targets in the same project. I am also able to build the Host exe in different, but very similar projects. I can also build the exe from this exact same project on different computers that have the same installation of labview. Creating a new project allowed me to build the host when only the host part was in the project - when I added the RT target, it failed. Cleaning the old build and trying again (and again..) does not help.
I was using LabVIEW 2011 SP1, but I just upgraded to the f2 patch (which did not help). Here are the series of error messages I get:
Step 1 try to build the exe, it gets almost to the end and then freezes up:
Clicking degug gives:
Debug...
Ok...
jeffneuner - did you ever find a solution?
Does anyone have any other suggestions for debugging or getting this to work?
I don't have any experience using the LabWindows/CVI debugger, maybe there is something I can do with this?
Thanks!
Lauren

Should my 7.1 full dev. system have Application Builder? I can't find it.

Hi NI,
I am interested in building a LabVIEW dll, and note that this requires Application Builder. Apparently this is included with the Professional Development System; my CD says LabVIEW 7 Express Full Development System Windows 2000/NT/XP, so should I be able to install the tool? If not, how do I obtain it?
Thanks in advance,
mallicos

Full Development is not the same as Professional Development. Only the Pro version includes the app builder. You can upgrade to the pro version or you can buy the app builder separately. Either can be done from http://www.ni.com.

"VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors"

Hi,
I had created an executable in LabVIEW 8.6 on a windows XP 32 bit PC. The application uses some Vision VIs. The executable runs in most of the PCs except one. the PC is a windows 7 64bit. Initially i got the error "Labview Load error code 3: could not load front panel". I fixed this by changing the source file settings in the application builder. Now i am getting the error "VI has error of type 1002288.The full development version of LabVIEW is required to fix the errors" and the exe shows a broken run button.
But if i build the exe in the same PC i get no errors and it works fine. Moreover i have tested this exe in a different PC with the same configuration, it works there. I have tried reinstalling labview in the PC the problem still persists.
Solved!
Go to Solution.

Hi Rajshekar.
> Which version of LabVIEW are you using on PC with Win7 64bit? would like to check if there are any issues with LV2009 32bit on 64bit OS..
- The version of Labview on the win7 64bit PC is also lv8.6 full development system.
> Do you get the same error on the other PC with same config(Win7) when running the .exe generated using LV 8.6 on WinXP 32bit? just to make sure the problem is with OS or LV..
- the same problem occured at one more PC with the same configuration. but when i tested in an another PC of the same config it worked i am not able to isolate and decide that the error is based on one particular PC config.
I have listed the environments in which application ran and how the application was put in to the PC.
I would also like you to know that i have created an installer for the exe. I am also using NI vision in my application and this is the error "An error occured loading VI 'IMAQ GetImagePixelPtr'. LabVIEW load error code 3: could not load front panel"....and rest is what i said in my previous post
1. Use the installer to install the application.
2. just copy the exe created in LV 8.6 into a PC that already has LV development system installed in it
3. The PCs might either be a blank one with no history of LV installed in them
4. The PCs might have diffrent versions of LV development systems installed in them (8.2,8.5,8.6,2009)
All PCs that have LV development system(s) installed in them, was able to run the application except the one with win7 64, where i have tried uninstalling all NI software and use only the installer to install, install LV 8.6 full development system and try runnning the exe, nothing works.
Thanks

Full production refresh to development systems and Charm?

Hi SDN Community,
Where I work we have a policy of refreshing the development systems (ECC, CRM, APO, BI, SRM) on an annual basis with full production system data, HR data is subsequently wiped clean from the development system.
For each of our systems we have a development system, a QA system and a production system.
The decision to do these full refreshes was taken to ensure that developers and configurers can do decent testing in the Dev environments - prior to transporting to our QA system - to ensure that we have a reasonably stable QA system. Prior to the refreshes - QA was considered too unstable by our business to be used as a good test platform - the full D refreshes solved this problem.
We have recently installed SAP Charm (Change request management) which is a solution manager based product that manages the transportation of objects in change requests - attached to maintenance cycles.
During our first development system refresh we discovered that all open Charm projects (maintenance cycles) were placed into an unuseable status due to the refresh. This means we had to rebuild all of the Charm projects after the refresh - which took a considerable amount of time + resources and delayed project work. We don't want to be in this situation again for our next refresh.
SAPs response to us has been that they have no other customer that does full Development system refreshes - and also has Charm. I wonder if this is accurate, I think what SAP are saying is that they don't have many Charm customers... Is refreshing Development so uncommon?
We are considering products like SAPs TDMS - and alternatives (eg gold client) - but most of these appear a little immature - for refreshing complex system landscapes - such as ours and keeping everything in synch after the refresh.
My questions to SDN -
What do you do - do you do full refreshes to your D systems?
If not - what are the arguments against refreshing D systems (is this considered bad practice)?
Are there any other Charm customers out there in a similar situation to us?
How do you manage the stability of your QA environments and stop the transport into QA systems of untested changes - if your D systems are not similar to you production system
(note we have some 300 active users in just our ECC development system)?
Any suggestions / recommendations as to how to best proceed would be greatly appreciated.
many thanks in advance,
Julian Phillips
Edited by: Julian Phillips on Nov 11, 2008 2:33 PM

Thanks Naushad for your reply,
I wonder if D refreshes are less common - more due to the additional hardware costs incurred (disk space needed to store full production data is usually pretty large) to do them - than due to avoiding disrupting development - probably a bit of both.
I did not mention this - but in our refresh we do reimport all transports that we open prior to the refresh - which used to solve our problems - in terms of restoring active changes - but with SAPs Charm system - this approach does not work as the Charm projects are left in an inconsistent status.
We are now leaning towards introducing a 4th set of systems into our landscape - so that we have the following platforms:
Development ---> Pre QA ---> QA ---> Production
This approach will allow us to keep both the Pre QA and QA systems refreshed every 6 months or so - and our new Dev system - we will refresh very infrequently (every 5 years perhaps) if at all. We will tie the Charm system to our new development - and this system will then not be impacted by refreshes. This approach means additional hardware cost - but as it happens we have a few spare boxes - so this maybe our best bet.
The core reason for our refresh is so that we will be able to preserve the stability of our QA test platform - which for us is the critical factor here. If QA has poorly tested work in it - we run a higher risk of disrupting other testing and also of this poorly tested work reaching production.
When we used to have a development system as you described and just the single QA box - we experienced frequent instability in our QA box - due to poorly tested working reaching it - and this delayed numerous projects.
Does anyone else have a 4 box setup like this? Anyone else encountered this on an SAP project anywhere? Pros / Cons of this approach?
//Julian
Edited by: Julian Phillips on Nov 12, 2008 8:08 AM
Edited by: Julian Phillips on Nov 12, 2008 8:18 AM

Please help suggestions for solving built-only compiler error: 'The VI is not executable. The full development version of LabView is required tofix this error.'

We have develoepd a software tool and build it on regular basis. It currently runs error free when compiled in the editor, but when we built it and run the executable stand alone we get the error.
'The VI is not executable. The full development version of LabView is required tofix this error.' plus a broeken error.
This menas an compiler error that is not present in the editor but in the stand alone version. We tried to identify errors as suggested in several posts in this forum, but so far unsuccesfull.
As the editor and its compiler do not see the error and are running fine and the stand alone version just syas 'find the error in the editor' in this case LabView is of no help.
Can anyone suggest a sensible or 'good practice ' way of searching for the source of this error?
Our project comprises hundreds of Vis over several libraries.
Thanks,
Chris

Thanks Craig for all your suggestions.
We seem to have located the problem in a new vi just added to the package causing conflicts by using the same vi names as other vis already present in the package. Excluding this vi removed the error.
It seems related to a conflict by having two vis with the same name, which was mentioned by LabView and interactively resolved when running the main vi from the editor. When successfully building the main vi the builder did not mention this conflict and reported a successful build, but when trying to run the executable it gave the cryptic error. The error caused us problems because there was no hint for the cause, just the suggestion to solve this in the editor, while at the same time in the editor the VI was running fine.
We will post about this in detail after we have positively proven that this actually was the case.
The .net version issue was already checked.
Performance was the same on all machines we tested on including the dev machine.
Debugging was tried nut did not help as the vi could not run (broken arrow). We assumed that debugging only helps in running faulty functioning vi''s. We did not check for broken arrows in sub-vis (after connecting), that could have helped, although our application has hundreds of our own vis.
In relation to your remark:
'Are you using many classes? Have you verified that the proper access scopes are set for functions calling those vis?'
Could you elaborate on setting access scopes. We were not aware of this option in LabView, although we realize this is a basic element of the underlying c code.
Ragrds,
Chris

Memory Footprint for LabVIEW 7.1 Full Development System

Similar Messages

Maybe you are looking for