Labview 2013 (32 bit vs 64 bit)

[KPRO]

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

[altenbach]

As a first step, you could show us the subVI. Where did you get it? How are we supposed to know what it does? Could it be that it is calling a third party 64bit dll?

(These don't look like LabVIEW errors, so they are probably generated by a third party component)

[KPRO]

Hi,

Sorry, Attached is the subVI, I wrote it myself.

[DailyDose]

Code Note: The Sequence structure appears to be completely unnecessary.  Perhaps in the situation you wish to use your wait, make a separate sub VI.  But other than that, the error cluster is driving sequence.

Speaking of error cluster: have you tried some basic debugging to determine when the error occurs?  Place probes along the error cluster, create a conditional breakpoint, or even use highlight execution.  It's a little harder for us to reproduce the error of a subVI.

[KPRO]

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 

[billko]

I would have to say whatever is initializing the instruement is not able to do so.  Hence the "Error Code ID = -201 - Invalid while in local" error.  (It can't set the instrument to "Remote" mode.)  Furthermore, I would hazard a guess that this is due to what altenbach mentioned about the 64-bit dll.

Swapping between 64-bit and 32-bit anything - not just LabVIEW - can have unexpected results due to dll issues.

[billko]

I guess the summary is that you are looking in the wrong place.  Other than questionable LabVIEW practices, there is nothing really wrong with this VI.

[KPRO]

Hi,

Thank you all for your help. Now, I have both Labview 2013 (32 bit) and Labview 2013 (64 bit) in the same computer. How can I uninstall the Labview 2013 (64 bit) from the computer. Hopefully this will solve the problem.

[billko]

It won't.  You're very far off the mark.  It's the Keithely driver that you are sort of using, not LabVIEW.  It probably installed the 64-bit dll.  You'll have to find a way to install the 32-bit dll, either alongside or without the 64-bit driver.

[Dennis_Knutson]

There is a Keithley 2400 driver at http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=25B255F3AA83660EE0440003BA7CCD... that does not use a dll. Compatible with all versions of LabVIEW and any os.