topic Re: Error 1003 occured while craeting VI interface to LabWindows. in Instrument Control (GPIB, Serial, VISA, IVI)

Error 1003 occured while craeting VI interface to LabWindows.

vivekkde — Mon, 30 Mar 2009 13:48:15 GMT

Hi,

I am facing while creating labView VI interface to LabWindow/CVI Instrument Driver. I am getting an error code of 1003 which states :

Error 1003 occured at Invoke Node in Import Driver.vi -> Import Driver.vi.ProxyCaller

Possible reason(s):

LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>>Open and verify that it is runnable.

Method Name: Run VI

VI Path: C:\Program Files\National Instruments\LabVIEW 8.6\project\_DriverCtoLV\Interface\FC_Interface_Main.vi

I am using LabView 8.6 version and have installed Import Instrument Driver Wizard version 1.2.

Please do let me know if someone has already faced such situation and the remedy.

Thanks in Advance,

Vivek

Re: Error 1003 occured while craeting VI interface to LabWindows.

NathanT — Tue, 31 Mar 2009 12:58:27 GMT

Hello Vivek,

What CVI instrument driver are you attempting to run the tool on? Does it follow the VXI Plug and Play specifications? If possible, please post the CVI driver source code.

Cheers,

NathanT

Re: Error 1003 occured while craeting VI interface to LabWindows.

vivekkde — Tue, 31 Mar 2009 13:08:59 GMT

HI Nathan,

Basically we are working on Agilent Omnibar drivers that downloaded from this site : http://www.home.agilent.com/agilent/facet.jspx?cc=IN&lc=eng&k=J1409A&sm=g&t=80045.k.1 that I suppose follows .the VXI Plug and Play specifications.

But before we could have started working on this, our conversion thing didn't work. So looking for possible reason or any other version of the LabVIEW Instrument Driver Import Wizard.

Looking Forward.

Rgards,

Vivek

Re: Error 1003 occured while craeting VI interface to LabWindows.

vivekkde — Tue, 31 Mar 2009 13:20:03 GMT

May be my first post didn't classify my problem properly as I hadn't communicated very well. Sorry for the inconvenience.

Actually I have downloaded the available LabVIEW Instrument Driver Import Wizard(ver: 1.2) from ni.com. It enables the Create VI Interface to LabWindows/CVI Instrument Driver option in Tools >> Instrumentation menu that itself is a VI. I am going for that option in LabView 8.6 and finding it broken with an error message of error code 1003. Please find the description below: Error 1003 occured at Invoke Node in Import Driver.vi -> Import Driver.vi.ProxyCallerPossible reason(s):LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Open the VI in LabVIEW using File>>Open and verify that it is runnable.Method Name: Run VIVI Path: C:\Program Files\National Instruments\LabVIEW 8.6\project\_DriverCtoLV\Interface\FC_Interface_Main.vi I hope this time I haev communicated the issue well. Please do suggest any solution for this. Thanks in Advance,Vivek

Re: Error 1003 occured while craeting VI interface to LabWindows.

NathanT — Wed, 01 Apr 2009 15:09:03 GMT

Hello Vivek,

I ran the 1.0 version of the tool in LabVIEW 7.1 and have attached the wrapper (mass compiled in 8.2.1). Please take a look at the conversion report and address those issues as needed. I will try to reproduce the 1003 error you are seeing in LabVIEW 8.6.

Cheers,

NathanT

Re: Error 1003 occured while craeting VI interface to LabWindows.

NathanT — Wed, 01 Apr 2009 15:40:28 GMT

Hello Vivek,

I installed LabVIEW 8.6.1 on a clean image and then installed the 1.2 version of the conversion tool and it worked fine. I have attached the wrapper instrument driver. Do you have multiple versions of LabVIEW on your machine? Have you had the tool installed in a previous version of LabVIEW?

Cheers,

NathanT

Re: Error 1003 occured while craeting VI interface to LabWindows.

vivekkde — Thu, 02 Apr 2009 03:43:45 GMT

Yes Nathan, I also tried in same way. I uninstalled everything belonning to NI and install it back and now it's working fine. I don't know why the things didn't work that time(might be some versioning ismsues). Anyways thanx for your valuable suggestions and help.

Thanks a ton.....

Regards,

Vivek