LabVIEW 64-bit - Can I build a 32-bit exe

Hi Gary
Not at the moment - see here
You'll need to open your VI up in the 32 bit version and compile from there.
Kind Regards
Chris | Applications Engineer NIUK

Similar Messages

How can i build a manchester coding in labview signal processing?

how can i build a manchester coding in labview signal processing?
mean to say that how can i digitize my audio input.i waqnt to convert my audio input into manchester coded data format!!!
kindly post related VIs
regards
Solved!
Go to Solution.

idma-
Check out the LabVIEW FPGA example http://zone.ni.com/devzone/cda/epd/p/id/6126
Generate Manchester Signal
Basic example showing generation of a Manchester encoded data stream. The data to be sent is generated in one loop and passed to a FPGA FIFO. The subVI which generates the Manchester data stream reads the data bytes form the FIFO and passes them to the digital output. The subVI prepends a simple header to each data packet which allows a reader (see next example) to synchronize and acquire/parse the data. The header consists of a thee half bit pulse followed by a one half bit pulse. The three half bit pulse is not a valid component of regular Manchester encoding and can therefore be differentiated from the rest of the protocol. In addition it can be used by the receiver to to easily measure the bit rate of the protocol. By dividing the length of the three half bit pulse in half (3/4 of a bit), the receiver has a measure to differentiate between full and half bit pulses in the rest of the protocol.
Generate and Read Manchester Signal
An extension of the previous example which adds a Manchester receiver subVI. You must physically wire the digital output channel to your input channel to loop back the data outside the I/O connector of your FPGA R series card or C series module. The Manchester receiver subVI is expecting the data packet to be prepended by a header as explained in the previous section.
I will see if the is a more precise example but this should help
Sam S
Applications Engineer
National Instruments

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

Solidwork x64 and labview 32 bits compatibility?

Hello community.
I'm with a project where I want to make the connection with Labview 32 bit and 64 bit Solidwork to control motors with LabVIEW, I have been following many tutorials and I get to create everything you need but when you run the VI does not move nothing SolidWork thousand times and reviewed the steps and is desesperate. Ruling out any option and I wonder if these two shows are 32 and 64 bits can be the cause of not getting the communication with these two programs. I hope your help. regards
Es un placer echar una mano siempre( Base de una sana convivencia). Si mi respuesta te sirve por favor agradecemelo con un Kudo
Un especial saludo a mis hermanos latinos. Un mundo mejor es posible.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

Can I build an application for a linux machine from a windows machine?

Is it possible, with LV2012, to build an application for a target other than the the machine type that I am working on?
meaning, can I build an application to run on a linux machine from my development machine, which runs on windows?
alternatively, can I build an applications to run (natively, no WOW) on a 32-bit OS from a development machine that is a 64-bit OS and 64-bit labview?
Or does LV only build for similar targets as the development platform, and I would need to move the source code to another development machine to generate code for a different type of target machine?
Thank you!
Solved!
Go to Solution.

You can only do a build for the OS that you have a license for and for the OS bitness that you are using. In other words, you need LabVIEW for Linux or LabVIEW for Mac to build exe's for them and you need LabVIEW Windows 64-bit to build a 64 bit exe. It does require moving the source code to the other development systems.

Makepkg doesn't work - can't build new different pkgs.

I'm maintaining a pkg named firefox-optimized. Now after I change mozconfig and PKGBUILD, I can't build a different pkg.
All the pkgs I built are all the same except .PKGINFO.
I have disabled ccache, and delete all cached files, even try to login another user to build, but still don't work.
Last edited by coderoar (2008-10-16 13:25:27)

maybe it's me but could you please try to be a bit more explicit... what exactly does not work, what are you trying to do, what did you modify and what kind of error do you get please?
BTW, firefox-nightly is based on the mozilla binary so you do not need any mozconfig here i think.

Using both, LabVIEW 32-bit and 64-bit

Hi Guys,
I have a requirement where I have to interface with a camera using LabVIEW 64-bit (because the dll provided is for 64-bit system). At the same time, I have to communicate with several variables via OPC Server using LabVIEW DSC, which is only available in 32-bit. I was told that I cannot run one same program but utilizing LabVIEW 32 and 64 bit simultaneously. Hence, I would like some advice, especially on the architecture, on how should I approach this.
Advices are much appreciated.
Shazlan

Are you sure that you can't have a 32-bit compatible dll for your camera? It would really make your life easier.
Also if you only use the DSC module for the OPC function, maybe you could look for a different set of OPC functions that support 64-bit.
In the end if you really have not choice but to use DSC module and use the 64-bit dll for the camera, you will need to apps, one in LV32 and one in LV64 and you will have to decide which one is the main one and find a way to communicate between them, TCP comes to mind, also VIServer, I have never tried VIServer between a LV32 app and a LV64 app but my bet is that it should work seamlessly.
Good luck!
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Can I build website in MUSE and administrate in JOOMLA?

Can I build website in MUSE and administrate in JOOMLA?
Anybody know if this works together?

NorthCape1 wrote:
...I understand that I can export the site as html...
Abhishek Maurya misled you by saying that you can export "as HTML and then upload it on any web host using any FTP client". They apparently do not understand what Joomla is.
The HTML that you export from Muse is a bit of a mess. You would need to be an advanced web designer to make sense of Muse's output and modify it for use in Joomla or any other CMS.
NorthCape1 wrote:
I did mark it as helpful...
I was not fishing for you to mark my post as helpful or as an answer. I was just confused how Corey's post was flagged as the correct answer as soon as he posted it.

Reading fits files in labview 64 bit

I need to read fits data files in labview on a 64 bit machine. I developed an application in labview 2012 (32 bit version on a win 7 x32 machine). This vi will not run on a win7 x64 machine. The problem is with the gfitsio library I used to read the files (downloaded from http://heasarc.gsfc.nasa.gov/docs/software/fitsio/fitsio.html). It seems they will not work with labview x64. I installed labview 32 bit on the same machine & tried to run the vi with that, but no luck.
Any ideas would be appreciated,
Thanks,
Joe

It appears the FITS libraries are 32-bit, so they cannot be called from 64-bit LabVIEW. You should be able to call them from 32-bit LabVIEW on a 64-bit machine. The only difficulty you may run into is locating the DLL. 64-bit versions of Windows put DLLs in different places than 32-bit. Check you system path and make sure your DLL resides in the search path. You can also load the DLL explicitly using Windows Kernel32.dll calls before loading code which calls it. This is awkward, but works in some cases.
Since the source code is available, you may be able to create a 64-bit DLL that 64-bit LabVIEW could use. I am the wrong person to cousel you on how to do this, but it should be possible.
If you need more info, please ask.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Real-Time Module Labview 64 bit

I have installed labview 2009 64 bit version to my laptop. And, i want to instal the real-time modul to this labview, but i can not do this since it needs labview 32 bit installed. Is it possible for me to install real-time module to 64 bit labview? Please help me with this problem.

The LabVIEW RT application will most likely always have to remain 32 bit for now. Most of the RT targets are to resource constrained to gain anything from moving them to a 64bit RT OS, in fact in trying to move them to 64 bit they would loose quite a bit of performance. For the Desktop and PXI RT systems, the problem is that they are based on Pharlap ETS and that is a pure 32 bit solution with no plans of ever moving to 64 bit anytime soon, AFAIK. And NI is not likely going to port that to 64 bit themselves, aside from the question if they could technically do so (not sure they have access to all of the source code) and legally (their license most likely does prevent them from changing the ETS software to run under different target systems than the one it was originally purchased for).
The only thing you can expect to come from NI in the near future is that the RT system also installs into 64 bit LabVIEW, and the actual cross compilation that happens already will simply target the 32 bit RT target. That however means that the RT application itself is still limited by the 32 bit constraints. Maybe there are some plans to add a 64 bit RT system to the mix for the high end PXI controller. What OS that would use is quite unclear. Pharlap ETS seems out of question for that, VxWorks is probably not a favorite solution at the moment and an Linux RT based system has its own legal and technical challenges.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Motion control in LabView 64-bit

   I am trying to operate NI Motion with a PCI-7344 card inside LabView 64-bit on a WIN7/64 platform. At this point, NI Motion will only operate in LabView 32-bit independant of 32-bit or 64-bit OS. The reason for the 64-bit operation is a 3rd party function generator card that requires 64-bit LabView to work in conjunction with the 64-bit drivers for a WIN7/64 OS.
   Currently, a system has been configured for WIN7/32 but would like to be able to access the full memory (>4GB) for other data processing.
   Any suggestions?

I have about the same problem, I'd like to use the full memory because I use NI-Vision and NI-Motion but I can't. I really like that NI or anybody could help us on that.
Jean-Francois

Softmotion module only runs on labview 32 bit and not labview 64 bit

Good day everyone,
I downloaded the softmotion module for my Labview 2013 64 bit however when i try to create a new solidworks assembly there is no option for that.
But when I installed the 32 bit version of Labview 2013 I was able to see the option to create a new solidworks assembly.
Why can't I see the option for the Labview 2013 64 bit ?
P.S I am using Solidworks 2014 64 bit Premium .
Thanks
Below is the 64 bit
Below is the 32 bit
Solved!
Go to Solution.

The softmotion module is not supported for 64-bit LabVIEW. You can see what we support in the link below.
http://www.ni.com/white-paper/10383/en/
Matt J
Professional Googler and Kudo Addict
National Instruments

Labview 64-bit running with 32-bit addons

I ran into memory problem loading som data files, and I tried a workaround by installing Labview 64-bit, but found that the add-ons was not installed with it.
Now I needed to use sound and vibrations toolkit, so (being maybe a little too creative) I copied that toolkit over to the 64-bit Labview folder and everything seems to run.
I can load the files and do my data analysis with no errors.
Now the problem is that I don't really get how a 32-bit add-on can access the memory from the 64-bit core Labview. Does anyone have any ideas on why its running and why I don't get a memory access error.
The results looks ok, but I don’t really trust them, due to the above mentioned problem in accessing memory between 32-bit and 64-bit.
regards
Henrik
Solved!
Go to Solution.

Hi Henrik.
When using LabVIEW 32-bit on a 64-bit machine, all your VIs would run through the Windows-on-Windows emulation layer (WOW64) and this is also why we still have memory limitations on a 64-bit OS.
When you are using LabVIEW 64-bit, and using a 32-bit toolkit, what's actually happening is the 64-bit LabVIEW kernel is recompiling the 32-bit VI into a 64-bit VI. Doing this changes the inherent memory characteristics and performance of the Sound and Vibration VI's (and all 32-bit VIs, for that matter). The newly converted 64-bit VI's, then, are being executed in the native 64-bit LabVIEW kernel.
However, I would strongly advise you to install the toolkit the normal way. In the following document, you can see, that the Sound and Vibration Toolkit / Measurement Suite is in fact supported by a 64-bit version of LabVIEW.
National Instruments Product Compatibility for Microsoft Windows 7
After you install LabVIEW, you need to reinstall all your add-ons and drivers in order for that toolkit / driver to work with LabVIEW. When we install toolkits / driver, we only install support for the LabVIEW versions installed at that time.
I hope this helps.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect

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

Does LabVIEW 64 bit included in Developer suite ?

Does LabVIEW 64 bit included in Developer suite ?
George Zou
http://webspace.webring.com/people/og/gtoolbox
Solved!
Go to Solution.

The installer is not included in the Developer Suite Disks. But it uses the exact same license as the 32-bit. You can download the installers from NI's site.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

LabVIEW 64-bit - Can I build a 32-bit exe

Similar Messages

Maybe you are looking for