12-04-2013 01:22 PM
Hi, I have a new 6 bit pc and an old 32 bit pc and I have to use both of them. If I install on the 64 bit machine labview 64 bit, when I save a vi, can it be opened on the 32 bit machine?
With this kind of problem, do you suggest me to install labview64 or labview32 in the 64 bit pc?
Thanks
Solved! Go to Solution.
12-04-2013 01:28 PM
With very rare exceptions vi's created in LabVIEW 64 bit can be opened and run on with LabVIEW 32 bit and vice versa (I imagine if you are triing to access a few dozen Gbits you have other problems)
Toolkit and addon support for 64 bit has been lagging. Personally I run LabVIEW 32bit IDEs on Windows 7 x64 machines and this works well for my client's. FOR NOW- It will change in the future.
12-04-2013 01:32 PM
You can do development on x64 or x32 and then open with the other. You just have to make sure that any components used are in both Labviews. That is if you are using an instrument driver in LVx64 you must also have a copy in the x32 Instr.lib directory for the LVx32. I developing on both on the same computer and jump back and forth quite a bit. one thing to note, not all the toolkits and drivers exist for the x64 version yet. For instance the Database Connectivity and Report Generation toolkits do no work with LVx64. it's up to you and dependant on what tools you are using with Labview and if they are available for LVx64.
12-04-2013 01:36 PM
Here is the link to the NI page showing what is and is not supported by LV x64.
12-04-2013 01:37 PM
I would also recommend using source code control which will make switching between machines much easier. All of the code you check in should be marked to separate the complied code from the source. This should make the switch between the two systems very easy and seamless.
12-04-2013 02:26 PM
1) Sorry for my ignorance, but how can I select "source code control"? (I am using LV2012)
2) As far as I understood both 32 and 64 work on a 64 bit machine? Which is your suggestion?
12-04-2013 03:00 PM
For source code control I would use SVN. I have also heard some very good things about git. Both are open source and are independent of LabVIEW. A simple Google search will find the installs for both as well as information specific to using them with LabVIEW.
There is a setting in the options under the Environment section to configure LabVIEW to separate compiled code from new files. I have attached 2 VIs (very crude since these are just basic utilities and we did not make them pretty) which you can use to list the status of existing files or set the option.
As for which version of LabVIEW to use I am saying use both. As noted earlier you will need to have copies of whatever drivers you are using for both versions. For the code you develop you should be able to use it in either the 32 or 64 bit version and the seapration of the compiled code should mean that it will easily transfer between systems. Your source code control won't see the files as being changed, unless you actually do make a change, since the compiled code is actually cached on each PC. The source will be the same in either the 32 bit or 64 bit version.
12-04-2013 04:36 PM - edited 12-04-2013 04:59 PM
Please, from this page
http://download.ni.com/support/softlib/labview/labview_development_system/2012%20SP1/
could you say to me which is the official 64 bit version of labview 2012sp1?
Because there are 2 different files with 3 different downloader.
12-04-2013 07:39 PM
Start here as the downloads have info. http://www.ni.com/trylabview/
12-04-2013 08:23 PM