Ni-can w/ labview 64-bit

Hi,
Can I use ni-can with labview 2012 64-bit?
I've installed ni-can 2.7.4f0, but during the installation I saw support options for 32-bit labview versions, but none for 64-bit versions. After the install when loading a .vi it can load ncWriteNet.vi. I've looked on a 32-bit installation and that file is in the labview install directory. I tried copying the files manually, but that just leads to other dll dependencies.
thanks,
Paul

Hi Paul,
Almost definitely not. I think the main landing page for NI-CAN 2.7.4 is pretty clear that you will need to use 32 bit LabVIEW.
Check it out for yourself: NI-CAN 2.7.4 Driver Page. Look under the "Supported Development Environments". Also, is there a problem using 32 bit LabVIEW?
NukeB | CLD

Similar Messages

Can I run 64 bit LabVIEW and 32 bit LabVIEW on the same machine?

If I have a 64 bit OS (Windows 7 64 bit or Server 2008 64 bit) can I install and run 32 and 64 bit LabVIEW on the same machine?
John

LabVIEW 64-Bit vs. 32-Bit Applications FAQ
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
The FAQ will likely answer other questions you have regarding the restrictions and issues you will have with having both versions and compiling in one vs the other.

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

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

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!"

How large can a LabVIEW Queue in elements and bytes?

How large can a LabVIEW Queue in elements and bytes?

rocke72 wrote:
How large can a LabVIEW Queue in elements and bytes?
In
elements it is likely something like 2^31. In bytes it is most probably
around the same number or better, depending how exactly the different
queue elements are stored. I think they are stored as independent
pointers so it would be theoretically better than those 2^31. In
practice however starting to allocated so much memory in LabVIEW will
always cause problems on nowadays computers. Without 64 bit CPU and OS
going above 2 GB of memory per application is very hard and as far as I
know not supported by LabVIEW.
Also allocating many chunks of memory (like a few million queue
elements holding strings) will definitely slow down your system tremendously eventhough
it will work but the OS memory manager will be really stress tested
then.
Rolf Kalbermatter
Message Edited by rolfk on 06-09-2006 12:24 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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

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

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.

I have 32 bit iTunes on a 64 bit Windows. Can't install 64 bit because the 32 bit will not uninstall (or run).

I have 32 bit itunes on a 64 bit Windows. Can't install 64 bit itunes because the 32 bit willl not uninstall.

Excellent news.
That one can sometimes hit people if they've used the PC Mover utility to transfer a 32-bit iTunes program onto a 64-bit system. Similar issues can arise if a 32-bit Bonjour or 32-bit AMDS get transfered across to a 64-bit system by PC Mover, so it might pay to keep a weather eye out for that (if you've used PC Mover).

Can no longer change bit rate in AAC custom import settings

I've been re-ripping all my CDs at the new higher bit rate. My import settings were AAC Encoder -- custom, originally set to 256 kbps, VBR, and auto for the other two settings. However, some CDs I wanted at a lower setting, so I would go change the bit rate to either 192 or 224 (just so I'd have more room on my ipod) and there wouldn't be a problem. But now it's stuck -- the pop-up box no longer opens when I choose import settings, AAC Encoder, Custom, so I can't change the bit rate or anything else, and it's stuck on 224 kbps. I can still change bit rate and other settings in the custom menus for MP3, WAV, etc., just not AAC. A repair install of iTunes did not fix the problem.

Hi, Ed. I am running iTunes 9.0.3.15. When I click custom, the settings description in the details box display what they were before this thing happened = 112 kbps (mono)/224 kbps (stereo), VBR, optimized for MMX/SSE2. The pop-up dialogue box that used to appear (where you could choose the specific bit rate from the drop down menu) does not appear at all.
However, when I choose anything other than AAC Encoder, and then pick custom, the pop-up box appears and I can choose the bit rate and adjust the other settings as usual. It's just not happening for AAC Encoder anymore. Since the total un-install (following Apple's specified order) and reinstall didn't work, I'm baffled how to fix this .... (If it makes a difference, I changed the bit rate in the custom box while a CD was being burned...Apparently that was stupid, but I had done it previously without incident.) Thanks.

Can I run 32 bit version of Oracle 10g grid on Linux x86-64?

Since Oracle did not release 64 bit version of Oracle 10g grid for Linux X86-64. Can I run 32 bit version of Oracle 10g grid on Linux x86-64? If so did anyone tried this? and also any known issues?

All I had to do was use the 32bit version of "/usr/bin/gcc" and "/usr/bin/g++" to run the installation
That is:
bin]# cp -p /usr/bin/gcc /usr/bin/gcc_old
bin]# mv /usr/bin/gcc /usr/bin/gcc323
mv: overwrite `/usr/bin/gcc323'? y
bin]# ln -s /usr/bin/gcc296 /usr/bin/gcc
bin]# cp -p /usr/bin/g++ /usr/bin/g++_old
bin]# mv /usr/bin/g++ /usr/bin/g++323
mv: overwrite `/usr/bin/g++323'? y
bin]# ln -s /usr/bin/g++296 /usr/bin/g++
AFTER INSTALLATION REMEMBER TO
move back the 64bit files to their former state.
bin]#rm /usr/bin/g++
bin]#rm /usr/bin/gcc
bin]#mv /usr/bin/gcc_old /usr/bin/gcc
bin]#mv /usr/bin/g++_old /usr/bin/g++

Ni-can w/ labview 64-bit

Similar Messages

Maybe you are looking for