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

Similar Messages

64-bit Labview 2013 Ni-845x = ?????

Rediculous....
If I have the following setup:
- Windows 7 64-bit
- Labview 2013 64-bit
- NI USB-8452
What driver do I use???????
v2.1.2 is 32-bit only...
v2.1 coverd 64-bits but not for Labview 2013, stops at 2012. Found this in a random compatibility chart no where near the damn driver or HW pages.
This is a maze of information, and digging for info like this should not be the norm.
My NI USB-8452 is glitchy when looking for it in NI Max. When I try to use the driver for I2C setup and immediately disconnects from USB (I hear the Window USB disconnect noise).
Has anyone had this problem? What driver do I use for Labview 2013 64-bit for the NI USB-8452.

My box is still not working.
I have:
NI USB-8451 (works fine)
NI USB-8452 (fails on ARG1 and I know it is right).
How can the same piece of cod work for one and not the other. It work previously, and now all of the sudden it's broken for the 8452 only.
See attached picture.
Please help me before I go insane.
Attachments:
WTF.png ‏19 KB

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, ?

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/

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Office Standard 2013 Key Management Service host 32-bit or 64-bit version ?

Hello,
I have a 2012 DomainController serving as our KMS host.
I need to activate 2013 Lync 32-bit clients so I will have to install the office 2013 KMS host.
The KMS host download is available in both 32-bit and 64-bit.
Should I download the 64-bit version because the 2012 OS is 64 bit or will I download the 32-bit host since the Office version we use is 32-bit?
BR
Sverre Amundsen

Hi,
Based on my understanding, I suppose that you want to activate 32-bit version of Lync 2013. Is it right?
If so, you can only install 32-bit version of Office 2013 on your PC. The 32-bit and 64-bit versions of Microsoft Office programs don’t get along, so you can only have one type installed at a time. If you mix 32-bit and 64-bit version installed
on the same PC, you might see some errors.
Reference about why can’t I install both the 32-bit and 64-bit versions of Office 2013:
http://office.microsoft.com/en-001/access-help/why-cant-i-install-both-the-32-bit-and-64-bit-versions-of-office-2013-HA103523746.aspx
By the way, there is an article about choosing 32-bit or 64-bit version of Office.
http://office.microsoft.com/en-001/support/choose-the-32-bit-or-64-bit-version-of-office-HA102840825.aspx
Best regards,
Greta Ge
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Experience on Labview and SUSE Linux Professional 64-bit

Hi!
Does anybody have any experience on running LabVIEW on SUSE Linux Professional 64-bit version? I'd appreciate any experiences about:
- installation
- development
- running applications
- compiling standalone applications
- etc
Regards.
Tomi
Tomi Maila

Hi Tomi,
There is currently no support for LabVIEW on 64-bit architectures, either on Windows or Linux. LabVIEW will still install and run properly if your operating system has a 32-bit compatibility mode.
The following is a KB that discusses the compatibility of NI products with 64-bit architectures with a Windows OS. Most of the statements will apply for a Linux OS as well.
KB 37NBEQSF: Are National Instruments Products Compatible with Windows XP 64-bit for AMD's x86-64 Te...
Hope this helps.
Kileen

Labview 2012 32bit running in 64 bit windows

Hello Sir/MAdam,
I have recently installed LabView 2012 on 64-bit windows 7. It seems LabView is 32-bit. When I run a simple code for reading digital inputs, it does not response while when I run this code on LabView 2010 running on a 32-bit PC it works!
Could this problem be because of 32-bit LabView 2012 running on my 64-bit windows. I also installed drivers which support 64-bit.
I attached the simple code I am using for reading digital inputs.
I appreciate in advance your kind help.
Thanks,
soroush.
Attachments:
read digital inputs.vi ‏44 KB

Soroush,
At this point it's still a little hard to say what may be causing this problem. Have you tried running any other I/O examples included with LabVIEW? Are these also unresponsive on the 64-bit machine running LabVIEW 2012?
Are you able to see any values using the Test Panels for the simulated cards in the Measurement & Automation Explorer (MAX)?
I don't think this is related to the 32- or 64-bit architecture of the computer, but hopefully we can help you figure something out.
Best regards,
Andy C.
Applications Engineering
National Instruments

"Class Not Registered" after switching from 32-bit to 64-bit LabVIEW.

I recently upgraded LabVIEW 2012 from 32-bit to 64-bit. Now I'm getting an error that says "Class not Registered". It still works just fine with the 32-bit version.

Thank you Nathan and Sunshine. The problem is I didn't build the program - it came with the instrument. As far as I can tell this is what's going on: The vi's are replete with these activeX objects - all communication with the instruments is done through invoke and property nodes. After switching to 64-bit the very first sub vi has an error at the very first command (Err (-2147221164)). It's a reference (seemingly to a class but I actually have no idea what that means) passed to the "Open Automation Function". I'll attach a screen shot for the sake of overkill.
Attachments:
labviewerror.png ‏20 KB

Labview 32-bit and 64-bit

i have a labview application built on a 32-bit XP. if it is running on a 64-bit system such as 64-bit xp or vista (i dont have the computer to test out, assume it will run on such systems), can it address more than 4GB of memory? or will it be running in emulated 32-bit environment in the 64-bit OS?
thanks,
Joe

It will run in an emulated 32 bit environment and because it is a 32 bit application will not be able to address more than 4GB of memory.

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

Report Generation Toolkit labview 2013 64bits?

Muy buenas tardes.
Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

Hola Antonio,
Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
Espero que por aqui lo puedas descargar,
saludos
Erwin Franz R.

LabVIEW 2013: An error occured trying to load the assembly

Hey all,
I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
I also tried importing the dll, but that gave errors too.
It's defintely a .NET 4.5 dll as the .NET reflector gives me
[assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
To try and get around the import issue, I added the following to my LabVIEW.exe.config file
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>
</configuration>
but it made no difference.
Any suggestions? All the things I've read so far are for 2010.
Solved!
Go to Solution.

Hornless.Rhino wrote:
Wart wrote:
I had the same issue a while back. Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link. It sounds like you've gone down the same road, but I figure every little bit helps:
http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
Thanks.
Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
We shall see...
So far no dice.
It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

Slow LabView 2013

Hi
I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
If I run for example, excel 2013 it does not seems slow.
Do you have any suggestions ?
Regards
Solved!
Go to Solution.

EDGAR_PLATRONICS wrote:
Hi Yamaeda:
I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
Actually it worked correctly in labview 8.5 but i converted to LV 2013.
I will research about transparent borders overlapping.
Hi Altenbach:
17% is overall. 3 cores are high % than others.
The problem is at edit mode and also when I run program.
Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
I am using 2 monitors in my PC. One to display LV panel and one for LV code.
I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Labview 2013 slow after building application

I have Labview 2013 with the DSC module installed.
I am running on Windows -64bit with 4 GB RAM
After I build my application, Labview slows to a crawl. There are no errors when I create my application and my application runs fine
All other programs run fine.
The windows task manager shows CPU use ranging from 2 to 20%
I have to shut down the computer and restart it. Then Labview is again running fine. Until I build my application again.
My application was originally developed in Labview 2012
I have not yet tried to create a new application to see if it is specific to my application or my Labview setup. I will try that next but I wanted to see if anyone else had this issue.
Thanks

Is this Windows 8, 7, Vista, etc?
Are you running 32-bit LabVIEW or 64-bit?
I would definitely recommend seeing if this problem happens when you try to build any application, or just your specific application?
Assuming the problem only occurs with your specific application, I would recommend that you try to build it on a different machine (assuming you have access to one) and see if LabVIEW behaves the same way on that other machine.
When you originally built your application in LabVIEW 2012, did you encounter this problem?
You could also try repairing both LabVIEW and the DSC Module to see if that makes a difference.
Regards,
Ryan K.

Labview 2013 (32 bit vs 64 bit)

Similar Messages

Maybe you are looking for