Labview 2010 64 bit?

Hi everybody,
I want to know at how many bits the new Labview 2010 program works.
Is it possible to select if it works for a 32 bit or 64 system, or does it switch by itself to this mode?
I hope that someone can tell me more about it.
Regards,
Kenny

There is 2010 LabVIEW 32 bit and there is 2010 LabVIEW 64 bit. You can install both if you like if you have a 64 bit OS.
Unless you need the massive 64 bit address space (and you probably don't!), I would recommend you install LabVIEW 32 bit, because it is more universal and has better support for addons, drivers, and modules. Not all are available in 64 bit.
LabVIEW 32 bit works perfectly on a 64 bit OS.
See also:
LabVIEW 64-Bit vs. 32-Bit Applications FAQ
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

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.

LabVIEW 2010 64 bit Evaluation Download Error

After downloading the 890 MB file from NI, I ran the installer and received the following error:
Zip damaged: file c:\national instrument downloads\labview 64-bit\2010\products\labview64\part04\mib.cab: Bad CRC. Possible cause: file transfer error.
I repeated the download and got the same error.
Does NI know about this?
CB

StephanieO,
I am running a brand new installation of Windows 7 64-bit. I should have been clearer: the problem is not in the download process. It crops up during about 1/3 of the way through the unzip process for the downloaded file, 2010LV-64bit.exe.
The image is attached.
Thanks!
Attachments:
lv64 unzip problem.jpg ‏76 KB

Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

I build an application exe and then its installer along with run time environment.
The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: AGMS.exe
Application Version: 1.3.0.0
Application Timestamp: 4c24e8f5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.0.4033
Fault Module Timestamp: 4c9273f4
Exception Code: c0000005
Exception Offset: 00005310
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell System XPS L502X
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8106MB RAM
Page File: 3457MB used, 12753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: HuronRiver Platform
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 4010MB RAM
Page File: 1359MB used, 6658MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
Now as I see it, it could be a Run-time environment mis-match error.
For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
I checked DEP, for all 3 PCs and it was set to the following
Turn on DEP for essential Windows programs and services only (first option).
I am confused. I can not find a solution for this and it is really frustrating.

But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
Since from the picture you can see its including the support installers from '\Program Files (x86)\'
The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
Yes I did reboot every time after I ran the installation.
Still getting the same error.

Report Generation toolkit for labview 2010

H All.
I'm looking to download the report generation toolkit for labview 2010. When I proceed to download the toolkit from the national instrumnets website, it says that i need to labview 2011 or later in order to install it.
Is there a version of this report generation toollkit for labview 2010 and can someone provide a link maybe??.
Thanks for reading.
Solved!
Go to Solution.

Try this: [Link removed, NI software downloads can be found on ni.com/downloads, the LabVIEW 2010 Report Generation Toolkit is available to customers with Standard Service Program here: http://joule.ni.com/nidu/cds/view/p/id/3247/lang/en, other customers may contact NI directly]
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

LabVIEW 32 bit on Win7 OS vs. XP 32 bit

I need to know if it is at all possible to create an installer in LabVIEW 2010 32 bit Win7 that would work on a XP 32 bit target machine.
How do you guys work around this issue if it exists?
I thought I could do it by keeping an XP platfrorm available for development but now that has left me unfortunately due to (I believe)
some upgrades applied via the auto updater.
ALso what have I done to screw this up on XP. I cannot even get XP to create an installer that would work on XP anymore.
The error I get when I try to install the installer I just created on XP LV 2010 SP1 is
"You must install LabVIEW 2010 32 bit or later on the system before you can run this setup."
I have placed an installer on this machine before since the target executable still works on it but now I am locked out from making any improvements
to the executable. If I make an executable it compiles just fine but some of the math functions are lost
"An error occured loading NI_AALPro.lvlib:LinearFit.vi"
Boy I hope the solution is not to re-install LabVIEW on the XP machine. I just had to physically disable the ethernet port on this machine so that it can
never connect to the internet again and a win7 replaceent is months away.
I am open to any and all suggestions. If more info is needed please ask and I will try to provide it.
Thanks Guys.

Thank you Dennis,
The Dll file was not including that Vi for some reason, so that was a good help.
On the first issue I did try to remake an installer from an XP machine to an XP machine and did insure that switch "require labVIEW 2010 32 bit " was not checked. It went ahead and made the installer just fine, but now it appears that the new installer still has this issue of giving the same error as described above.
Fortunately, I found a way to work around this and am not totally stuck (Thank goodness.)
The only thing I can think of is the source XP machine was hooked up to the NI updater software and some updates were probably applied to this version of LabVIEW (2010) or something is amiss on the target machine(doubtful). However, the 'about LabVIEW' dialog on the source XP machine simply states the version as LabVIEW 2010 SP1 version 10.0.1 (32 bit) .
I have no courage to attempt an un-install of the support on the target machine because it is in production use.
I think this issue should be looked at by NI if possible. The switch for "requiring LabVIEW 2010 32 bit" seems to be doing something that cannot be reversed once set. I wish I could be more helpful.

How to get Point Grey Dragonfly firewire cameras to work with LabVIEW 2010

We recently got a new computer. The O.S. is Windows 7, 64-bit. It has LabVIEW 2010 (also 64-bit) and the Vision Development Module, as well as the Vision Acquisition Driver. We also have Point Grey Dragonfly Express cameras. The first trial of using LabVIEW to get images from one of the cameras yielded greyscale images (they are color cameras). We then installed the Point Grey drivers (flycapture2.1.3.4_x64). After installing the drivers, the camera was is no longer recognized in MAX. Does anyone have pointers or advice? Thanks.

It's been a bit since I've messed with camera settings. But I think LabVIEW requires the NI-IMAQdx driver and the greyscale was from not setting the bayer filter. I can't poke around my camera settings right now, so I can't double check.

3D graphs cause LabVIEW 2010 to hang

I've been using LabVIEW 2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work. Right-clicking on the window does not show a context menu. The main menu doesn't work. The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit. I have to kill the process in Task Manager.) It is the same story with just a plaing 3D picture indicator. Also, the solarsystem.vi example does not work either. The problems start as soon as I open the solarsystem.vi. After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7. I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion. The Mac drivers are all updated. Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
After searching the forums, I've tried all the other potential solutions I could find: 1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero.
Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.
Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed. The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
Solved!
Go to Solution.

Yep, it's the same virtual machine. I set it up almost 2 years ago and it has been extremely stable. Both LabVIEW 8.5 and 2010 have been perfectly happy on it. It's a great way to do LabVIEW on Win7. I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion. I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard. The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
I happen to have an XP virtual machine too, but I haven't installed LabVIEW there. Let me know if that would be a worthwhile test.
You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
The video card is the original stock:
NVIDIA GeForce GT 120:
Chipset Model: NVIDIA GeForce GT 120
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0640
Revision ID: 0x00a1
ROM Revision: 3386
Displays:
Cinema HD Display:
Resolution: 2560 x 1600
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Display Connector:
Status: No Display Connected

Fieldpoint and Labview 64 bit - why is the LabVIEW Support missing from MAX and the Measurement I/O Pallette?

I am running Labview 2010 on a Windows 7 virtual Machine, I have installed Fieldpoint 6.0.7 with all the appropriate support. The VIs are in vi.lib. BUT, MAX doesn't show the LabVIEW support as existing, and the Measurement I/O pallette doesn't have the Fieldpoint VIs linked into it.
Anyone out there with any idea what I might need to do to get these seen? I've uninstalled, re-installed, installed only sections, and so far - no sign of these VIs appearing.
So, any ideas?

Not quite. I can see Fieldpoint, but not the LabVIEW support section.
The first screenshot is from my 32-bit system, the second is the one from the 64-bit system.
Attachments:
Fieldpoint Screenshot 1.JPG ‏20 KB
Fieldpoint Screenshot 2.JPG ‏15 KB

Strange problem of calling library function node in labview 2010 and 2011

one year ago,I develop a program to usb device data and it works well,in labview 8.6 or 2009(win xp).Recently, When I test
the program in labview 2010 and labview 2011(win xp).,the program always crash immediately.I check the program and find main
problem is in call library function node. In my program,I use labview 2009 library for the USBExpress driver for
Silicon Labs USB MCU's from:https://decibel.ni.com/content/docs/DOC-9522,for example, 2 functions SI_OPEN and SI_READ
can not work well.
the header definition of SI_OPEN and SI_READ is:
SI_STATUS WINAPI SI_Open(
DWORD dwDevice,
HANDLE* cyHandle
SI_STATUS WINAPI SI_Read(
HANDLE cyHandle,
LPVOID lpBuffer,
DWORD dwBytesToRead,
LPDWORD lpdwBytesReturned,
OVERLAPPED* o = NULL
the SI_STATUS is equivalent to int type.
orignally, for HANDLE * in SI_Open, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass pointer to value.
for HANDLE in SI_Read, the parameter type in call library function node is numeric, data format is unsigned 32 bit integer ,and pass value.The program works well in labview 8.6&2009,however,crash in labview 2010 &2011.
later,I debug the program, for HANDLE *, I choose parameter type in call library function node as adapt to type, data format is point to Handles.for HANDLE, I choose parameter type in call library function node as adapt to type, data format is Handles by Value.Crash not happend in labview 2010&2011,however,it cannot read any data from from USB device correctly as before.I can not find the reason.
Dear friends,I need your help to answer the problem. Thank you.

Based on the help page it looks like it should execute asynchronously.
The thing in the description that leads me to believe they execute asynchronously is that you can configure the library to run as a multi-threaded operation.
Please take a look here to see the difference between synchronous and asynchronous execution.
Since the code even has the ability to be multi-threaded, you can consider it as running in parallel to your other code.
Any data returned is passed to the thread that called that function.
Cory K

LabVIEW 2010 SP1: "Controls" pop-up palette "Select a control..." bug?

I'm using LabVIEW 2010 SP1 (32-bit) and I noticed today that I cannot place my custom controls on a VI's front panel when I use the "Select a Control..." option on the "Controls" pop-up palette. I'm wondering if anyone else is having this same problem?
Steps to reproduce the problem:
1) Create a custom control, or download/save the attached custom control "Machine State.ctl" (< a strictly-typed enum control).
2) Open a VI (new or existing).
2.1) If the "Controls" palette is visible (pinned open), close it.
3) Right-click with the mouse on the VI's front panel window to display the "Controls" pop-up palette.
Note: DO NOT use the "Controls" option in the "View" menu here.
Note: DO NOT pin open the Controls pop-up palette at this point.
See my comments below in the "Notes" section.
4) "Controls" palette > "Select a Control..." option
5) Using the "Select the Control to Open" dialog, browse to, select and open the custom control file (e.g., "Machine State.ctl").
At this point the on-screen cursor should show the outline of an instance of the custom control I just opened, but for me that doesn't happen; all I see is the "+" crosshair cursor, and left-clicking with the mouse on the front panel does not place an instance of the custom control on the front panel.
Notes:
* In step 3) above, if I open the VI's "View" menu and select the "Controls" option, or if I pop-up the "Controls" palette and pin the palette to keep it open, I can successfully use the "Select a Control..." option to browse to, select, open, and place an instance of my custom control on the VI's front panel. The failure only occurs when I use the "Select a Control..." option on the pop-up (unpinned) version of the Controls palette.
* I can successfully drag-and-drop an instance of a custom control onto a VI's front panel from a Windows Explorer window, or from the LabVIEW project explorer window.
* The host computer is running Windows 7 Enterprise x64 w/ SP1.
Jim
Attachments:
MachineState.ctl ‏5 KB

Just now I tried creating and using controls on five different computers, each running Windows 7 Enterprise x64 w/ SP1.
On three of the systems the problem did not occur; I was able to place a user-defined control on the front panel using the "Select a control..." option on the controls palette.
On two of the systems the problem still occurs. Upon further investigation, however, I learned that the hard drives in these two systems were cloned from a "master" hard drive image the IT department created. So I'm guessing there's some bad mojo on the master hard drive image, and that's what's caused this problem to show up on these two systems (and others).
So for now, I'm just going to put up with having to use the old "drag-and-drop" method for placing user-defined controls on the VIs. Thanks for your feedback and assistance with this.
Jim

LabVIEW 2010 in-placeness crash bug

[cross-posted to LAVA]
I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture
LabVIEW 2010 CRASH.vi (16.56K)

No crash on my system: LV2010, W7 64-bit, Pentium E5200
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

LabVIEW 2010 SP1 may not cleanly shut down

Occasionally LabVIEW 2010 SP1 (32-bit, running on Windows 7) will appear to "hang" when the "Getting Started" window is closed. The window disappears but the shortcut icon still appears in the Windows toolbar in the bottom of the screen. Right-clicking and selecting "Close Program" does not work and Windows seems to think any VIs that have been recently closed are still open. The program is still in the list in Task Manager and it can successfully be shut down all the way from there.
This is more of an annoyance than an operational issue (I think) - is there something I am doing (or failing to do) that causes this problem?
Thanks in advance.

Hello Unplugnow,
Deleting the .ini file will not cause any issues in terms of being able to reload Labview it will simply restore the default settings for Labview which will insure that there were be no data corruption issues. I have tried this procedure on my side with no issue although I would recommend copying the .ini file to another directory in case you need to recover this information at a later time.
To another note, does this issue arise when you are opening a particular VI, or does it occur when you are simply opening and closing Labview?
Best,
Blayne Kettlewell

Labview 2010 crashes XP while looking for webserver

Hi,
I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable. I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
I've gone into the Windows Event Viewer and there is an event that says "Labview information: Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL ."
I'm attaching a jpg of the Event in case I typed it incorrectly. There is another post that mentions this error but there is no resolution and the discussion went in a different direction: http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
Neither my Win 7 development laptop or my target Win XP system have this www folder.
Has anyone seen this before or know the cause? Thanks.
Steve
Attachments:
Event Viewer small.jpg ‏69 KB

Altenbach,
Thanks for the quick reply.
Yes, the time stamp of this error coincides with the crash. I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer. Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
This only happened on time and I have not been able to reproduce it again.
I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again. Do you have any suggestions? Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
Thanks.
Steve

Using LabVIEW 7.1 and LabVIEW 2010 on the same PC (Windows XP)

I have LabVIEW 7.1 on a Windows XP 32-bit PC and we plan to upgrade to LabVIEW 2010 soon. A lot of our software is using Traditional DAQ, DAQmx and DeviceNet. We need to use both versions of LabVIEW for some time on the same PC. Is this possible at all?
I installed an evaluation 2010 version and now I don't have DAQ and DeviceNet in LabVIEW 7.1. Any suggestions will be very helpful.
Thanks, Nick
Solved!
Go to Solution.

For what it is worth, I tried having multiple versions of LabVIEW on the same PC. If you are (very) careful, it is possible to do so, as long as you are only doing development work, i.e. you don't try and install LabVIEW drivers. However, as I've discovered to my great sorrow (which involved installing and removing various versions of LabVIEW on the same machine probably 5-8 times, eventually leading to wiping the machine and installing WinXP all over again, then only one version of LabVIEW), if you want to actually run your code, particularly if it does anything with hardware, you need to stick to one version!
There's another "gotcha" for those of us working with "older" versions (namely before 2009, though one can "trick" 8.6 if you're careful) -- Windows 7 doesn't "play well" with the older software!
So my development machine runs Windows 7. I have a VM of Windows XP in which I installed LabVIEW 7, which I use for my "legacy" work -- I use the Win 7 machine for LabVIEW 8.6, 2009, and 2010 development (and only development, see above).
The machine that got "rebuilt", where I wanted to run LabVIEW code for various hardware and potentially various LabVIEW versions, I did a really nutty thing -- I created a quadruple-boot PC! (It really is a triple-booter, as the Windows 7 system, which is the key step, is "hidden"). To make this work properly, I needed three hard drives in the machine (one for each OS -- I might have figured out how to put two XPs on a single drive, but since I already had the disks, one-OS-per-disk seemed easier). I'm using Windows 7's Boot Loader to give me the startup choice of which system to use (the message says something like "System for Hardware A", "System for Hardware B", "Test System"). True, you need to do a Restart, but since you're going to be collecting data, it's not such a bad idea to start with a "fresh machine".
[I did think about doing this with Virtual Machines, which would have been much simpler, but I didn't have "virtual drivers" for the hardware! One piece was actually a USB device, but the other was a proprietary device that plugged into my PC ...]

Labview 2010 64 bit?

Similar Messages

Maybe you are looking for