Labview 64 or labview 32 bit?

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.

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.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Attachments:
Enable-Disable Seperate Compile Code.vi ‏25 KB
List Seperate Compile Code Setting.vi ‏24 KB

Similar Messages

Labview 2011 32-bit, Tescom ER3000, Windows 7 64-bit

I currently have Labview 2011 32-bit installed on a Windows 7- 64-bit machine. I am trying to run the VIs found in the attachment below, but I get the error that function called in the DLL has failed and that TESCOM.DLL may be in use. Any thoughts as to why this is happening? I've already checked to make sure the path referenced in the VIs' function call nodes is correct... any and all help is appreciated!!
~Avi
Solved!
Go to Solution.
Attachments:
ER3000.llb ‏139 KB

Greetings;
I have been reading up a bit on the company and the DLL itself, and are we sure it is supposed to work well with Win7? Would it be possible to try booting up LabVIEW in compatibility mode (XP) to try it out?
http://www.documentation.emersonprocess.com/groups/public/documents/data_sheets/der301767x012.pdf
Only mentions up to XP, hence the question.
National Instruments
Applications Engineer

Labview 2009 32 bit not running on xp 64 bit

Hi all,
I tried to upgrade to LabVIEW 2009 from LabVIEW 8.6 on 64-bit windows XP machine. Following about a 2 hour removal of 8.6 and subsequent installation of LV 2009 it turns out that the device drivers are not compatible with a 64-bit machine. On launching LabVIEW 2009 (32-bit) an error box appears stating that it is corrupt or missing files and to correct this using control panel etc. I have tried this and still the same error occurs and LV refuses to start.
All the license files are correct and the compnents are activated.
Anyone know how to fix this? Or should I go back to 8.6 and cancel my upgrade subscription?
Secondly, I am using a firewire camera and was informed that Ni-IMAQ legacy are no longer supported and to go to ni.com/ifo and enter legacy1394 to see how to download drivers etc for this. I end up on a page that says "not authorized".
Any help gratefully appreciated.
Solved!
Go to Solution.

Leeser wrote:
I agree that XP64 and LV 2009 are not compatible as I installed LV 2009 on another 32-bit machine with no problems. I was just surprised as there were no problems or issues that I came across for 8. on XP64. Ah well, a uninstallation and reinstallation lies in wait for me on Monday morning!!
As an aside why call it LV 2009 instead of LV 8.7 or even LV9.0...sounds reminiscent of an operating system!!
Regards,
Leeser
LabVIEW 2009 is according to the internal version scheme actually equivalent to LabVIEW 9.0. Why they changed the naming? I guess marketing told them to do so. Why then? Well marketing has some funny ideas sometimes. I guess since THE software provider in this world has started to do this since about Windows 2000 someone must have thought it to be the best idea since sliced bread and decided to do it for LabVIEW too.
Another guess is that in about 2010 there would have been something like 9.1, and 10.0 would then come out in 2011 and that sounded somehow to someone like a bad scheme so they decided to change it now. But maybe it will be forgotten and everybody returns to the old versioning at the begin of next year when 9.0.1 will come out, which would then otherwise be LV 2009.1??? Or maybe LV2009 SP1?
It has already happened with LabVIEW 6i (iMacs, iPhones, iAnything), LabVIEW 7 Express and LabVIEW 8.20 (following 8.0.1 and marking the 20th anniversary of LabVIEW, and being internally LabVIEW 8.2). All some marketing fun or hysteria.
Rolf Kalbermatter
Message Edited by rolfk on 08-17-2009 11:08 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Installing 64 bit version of toolkit and modules for Labview 2009 64 bit?

Hello I recently contacted NIabout installing Mathscript and Signal processing toolkits for my Labview 200964 bit that I am running on Windows 7. I was sent the following link as aresponse: http://zone.ni.com/devzone/cda/tut/p/id/10383. From this link it is my understanding that I cannot run any programs thatcontain an astrestik, since they only work for 32 bit version of Labview? In particular I really need to use Mathscript. Is there any workarounds? Do I have to also install the Labview 2009 32 bit version? Doesanyone know when Labview will allow me to run everything in the 64 bit versionof Labview? Thanks.
Kevin

Hello Kevin,
There is no workaround available, and there are no released dates as to if/when Windows 7 x64 support for the toolkits in question will be introduced.
The LabVIEW Mathscript RT Module is not supported in LabVIEW 64-bit as mentioned at the bottom of the following page: http://zone.ni.com/reference/en-XX/help/371361F-01/lvhowto/labview_mathscript/ .
Vivek Nath
National Instruments
Applications Engineer
Machine Vision

Labview 2010 64-bit property node setting

I am trying to set the selection start and selection size for an array in LabVIEW 2010 64-bit on a Windows 7 64-bit machine.
LabVIEW 2010 64-bit crashes and is shut down by Windows.
The call works fine in LabVIEW 2010 32-bit on the same machine.
The computer is a Dell Precision 3500 with 4 GB ECC memory, an Intel Xeon 3530 2.8 GHZ CPU, and a 320GB hard drive. I have LabVIEW 2010 Service Pack 1 installed.
Here is an example of code with just one property node call.
Is this a bug or something weird with my system.
Attachments:
Array Property Node Crash Example.png ‏24 KB

I was able to reproduce the problem, also using LV2010 64-bit on Windows 7 64-bit. I tried various representations of the array data type as well as trying to not include the data type for the control reference as well as trying it via a property node in the calling VI. LabVIEW crashed each time. I'd say it's definitely a bug.

Why does labview 2009 32-bit closes up with no error message?

Hello.
I am developing an application using a PCI-6534 board, Windows XP SP3, and LabVIEW 2009 32-bits. In this application I am generating a 300 Hz signal using the P2.0 digital line. I am trying to make digital acquisition using the P0 port (8 bits), using N-sampling. The program that generates the 300 Hz clock, works with no problem. However, when I start running the program that performs the data acquisition, LabVIEW suddenly closes up with no error message. The LabVIEW windows just disappear from the screen.
As for me it looks like a LabVIEW bug.
In case anyone decided to help me, I could attach the programs so that you could check them.
What can I do to solve this problem?
Thank you.

I had the same problem with one of our applications. I supplied gigabytes of process monitor and desktop execution toolkit logs, but nothing was resolved. I upgraded from WS2003 and LV2009sp1 to W7 64b and LV2010, per NI's recommendation but the problem persists. I had the corresponding service ticket open for 3 months where NI said the application ran fine for them on W7 with 2010. (long story)
I understand your frustration, and I recommend getting your local application engineer involved as an advocate with application support.. If you pay for service, pound on them to provide it. My $0.02.

Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
Any suggestions?
Thanks

For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine. On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
This may not be a complete fix to the problem but at least in this one case it worked.

Restarting PXI RT from Labview 2011 64 bit

I have a customer trying to issue a restart command to a PXI-RT system from Labview 2011 64 bit. He says the command doesn't work.
I currently don't have 64bit so I can't test it very well right now.
Is this something anyone else has tried or experienced?
Thanks,
Josh
G Systems
Certified LabVIEW Architect

The real-time module is not supported for 64-bit LabVIEW. As a work around, you could install 32-bit LabVIEW onto your 64-bit OS. This should solve your customer's issue.
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98?OpenDocument
Ben D.
Applications Engineer
National Instruments

NI-USRP 14.0 driver ,and labview 2013 64 bit

Hi
Is it possible to use the NI-USRP 14.0 (64 bit driver) with Labview 2013 64 bit ?
have someone tried to install NI-USRP 14.0 drivers and then convert the driver ("instr.lib \niUSRP" directory) back to 2013 version ?
or do i need to purchase the 2014 version if i want to run 64 bit labview & USRP?
Thanks

Hi again
i installed the 32 bit verision of niusrp 14.0 driver (selected to install the driver for labview 2013 ,32 bit version)
& copied the installed files from 32 bit labview directories to the 64 bit version directories
, when opening a usrp vi (like "open rx session.vi" ) it says :
"error loading "niusrp.dll" A dynamic link library (DLL) initalization routine failed.
if i then try to point to another niusrp.dll like the one placed at C:\windows\SysWOW64\ , i got :
" the library selected is not valid for the current platform. for example ,you are running 64 bit labview and the library might be a 32 bit library"
where can i find the "right" niusrp.dll ?
so it seems that the niusrp 14.0 driver does not support labview 2013 64 bit version, ?

NI Labview 2012 64 bit incompatible

Hi guys,
i have a labview 2012 SP1 (32-bit) and labview 2013 (32-bit) installed on my PC.
My PC running on Windows 7 Ultimate.
i want to installed Labview 2012 SP1 (64-bit) but it give me this error (refer to picture attach)
i read on the http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
and it says
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
does anyone have the same problem?
Attachments:
NI Labview 2012 64 bit.png ‏41 KB

You also have to watch out for drivers. If you try to install the old drivers, they will not install. You will want to reinstall the newest drivers if you want to use them with your older version of LabVIEW (assuming the drivers are compatible with that version of LabVIEW).
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Usrp driver 1.3 do not support for Labview 2013 64 bit ??

Hello, dear all
Is anyone install the latest USRP driver 1.3 for LV 2013 64 bit ? I found there is no version for 64 bit LV 2013.

Currently the 1.3 driver supports only LabVIEW 2013 32 bit (even on 64 bit computers.)
The LabVIEW 2014 version will support 64 bit and will be available to download very soon.
Please check here within the next week or so: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/ssnav:drv/q/usrp/

Labview 2013 (32 bit vs 64 bit)

Hi,
I have subVI to read the current from the Keithley 2400.
1. When I run it under Labview 2013 (64 bit) is no error
2. When I run it under Labveiw 2013 (32 bit) is ERROR
Error Code ID = -201 - Invalid while in local
Error Code ID = -420 - Queary Terminated
How can I fix this subVI to run under Labview 2013 (32 bit) ?
Thanks
Khanh

Hi,
Error at GPIB Read:
Output of the GPIB Write is OK but output of the GPIB Read is error. But the same subVI, if I run by Labview 2013 (64 bit) no error, unfortunatly the rest of the program (other instruments communication) are running with Labview 2013 (32 bit). That's why I would like to fix this to run under Labview 2013 (32 bit).
Please help. Thanks

Use NI LabView and LabView RT with third party PXI chassis

I want to use NI LabView and LabView RT, some PXI chassis of N.I and
some PXI chassis of Third Party( not N.I ) for diversity, How I will Install
Pharlap ETS ( LabView RT ) on those third party PXI's.
More simply
Third party PXI chassis and controllers support LabView RT or not?
Note: Mark Andre Hary [email protected] of Sensing Systems LLC answer to this question as:
"You can't. I think NI bought Pharlap, and they do not offer board support packages (BSPs) for non-NI PXI controllers. There is no way to get LabVIEW-RT running on a controller not purchased from NI. You will have to use a standard RTOS like Linux,VxWorks, or QNX.
Regards

As described in the web links below, the only way to run LabVIEW Real-Time for ETS on a third-party system would be to follow the procedure for desktop PC computers. You may find that your third party PXI controller may meet the requirements listed in the below link and you will be able to run Real-Time on the controller. If you decide to do this, you will need to purchase the LabVIEW Real-Time Desktop Deployment license (also linked below). After purchasing the deployment license, you will be sent boot disks that will install the real-time OS onto your system. There is no need to purchase Pharlap ETS from Ardence directly.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/cb3434da94466dd286256e9e006bb775?OpenDocument
http://sine.ni.com/nips/cds/view/p/lang/en/nid/13751
Instead of using LabVIEW Real-Time for ETS, you could use LabVIEW Real-Time for RTX instead. This system allows you to run Windows and the Ardence Real-Time eXtensions (RTX) real-time kernel concurrently on one machine. Currently device support for LabVIEW RT for RTX systems is limited to RIO devices. This is all described in the below link.
http://zone.ni.com/devzone/conceptd.nsf/webmain/9cc60298315a687e86256e78007b3a96
I hope this answers your question.
Regards,
Kristi H - National Instruments

Send sms from Labview without LabVIEW 8.0 PDA module

Does anyone can send sms from Labview without LabVIEW 8.0 PDA module?

You can get a wireless (GSM) modem for the pc. There have been some discussions here that you can do search for. One is http://forums.ni.com/ni/board/message?board.id=170&message.id=142443&view=by_date_ascending&page=1.

Spartan 3E with Labview 2012 (32 bit) on WIndows 7 64-bit - Error Code: -310602 NI-COBS: Unable to communicate with device over communication cable.

Thanks for the info, Kyle. I will probably try to find an older 32-bit XP machine. VM is just not an option for me right now.

Hello everybody,
I am trying to use the DIgilent Spartan 3E board with Labvew 2012 SP1 32 bit. I am able to compile the example code for LED shift. I am however unable to transfer code to the FPGA. I get the following error message:
Error Code: -310602
NI-COBS: Unable to communicate with device over communication cable.
Please verify that the cable is connected to a supported device and that the appropriate drivers are installed.
My system configuration is as follows:
Windows 7 (64 bit) on Dell XPS laptop.
Labview 2012 SP1 (32 bit)
Labview FPGA 2012 SP1
Labview 2012 FPGA support for Spartan3E
Xilinx 13.4 tools
DEFB LV FPGA 2012sp1 support installer
Xilinx USB cable driver v1.3 installed.
I took all the precautions mentioned by others on this forum and others, mainly that the cable must be disconnected before installing the Xilinx cable driver. All software and drivers were installed correctly. I even uninstalled and reinstalled the entire Labview software set I had. I still get the same error.
A few other questions:
1. Is the Xilinx cable different from a regular USB cable of the same configuration ?
2. When I program the FPGA I only have the USB cable connected between my computer and the Spartan 3e board. Should any other cable be connected ?
3. What should be the correct jumper settings for J1 - JP30 (especially J30, J11, JP9, JP6, JP7, etc) ?
I have been at this or over 3 days trying to figure it out. Any help will be greatly appreciated.

LabView 2012 32-bit, creating an installer to run on Windows 7 64-bit

Hello I have the full development LabView system installed on a 32-bit PC running Windows XP. I'm trying to create in an installer that will be ran on a 64-bit machine running Windows 7. I'm able to create the installer, but when I try to run the installer I get on the Windows 7 64-bit machine I get:
"The version of this file is not compatible with the version of Windows you’re running. Check your computer’s system information to see whether
you need an x86 (32-bit) or x64(64-bit) version of the program, and then contact the software publisher."
I tried changing the compatibility mode under properties, without any success. What else can be causing this issue. Thanks.

There should be abolutely no problem installing or running a 32 bit LabVIEW executable in windows 64 bit. I do it all the time.
There must be something else. can you give a bit more details about your application? Are you including the runtime engine in the installer?
"I tried changing the compatibility mode under properties, without any success"
What exactly did you do here?
LabVIEW "full" does not allow building applications or installers unless you also have the application builder. I guess you have that.
LabVIEW Champion . Do more with less code and in less time .

Labview 64 or labview 32 bit?

Similar Messages

Maybe you are looking for